Regulations June 5, 2026 11 min read

Poland's KSeF E-Invoicing Mandate: Complete Compliance Guide

Poland's Krajowy System e-Faktur (KSeF) is one of Europe's most ambitious CTC e-invoicing platforms. With large enterprises live since February 2026 and all businesses joining by April 2026, here is everything you need to comply.

InvoStaq Regulatory Team

Central European e-invoicing compliance

Poland's KSeF (Krajowy System e-Faktur — National e-Invoice System) represents the next generation of Continuous Transaction Controls (CTC) in Europe. Unlike network-based models (Belgium's Peppol) or format-based approaches (Germany's XRechnung/ZUGFeRD), Poland's CTC model requires every B2B invoice to be submitted to and validated by the government platform before it becomes legally valid.

After a notable postponement in 2024, KSeF went live for large enterprises in February 2026 and will cover all businesses by April 2026. The platform is operated by the KAS (Krajowa Administracja Skarbowa) — Poland's National Revenue Administration.

Feb 2026

Large enterprises (>PLN 200M)

Apr 2026

All businesses

FA(3)

Required XML schema

CTC

Continuous Transaction Control

KSeF Overview

KSeF is a government-operated central platform that acts as the single point of truth for all B2B invoices in Poland. The workflow is fundamentally different from post-audit or network-based models:

Pre-Clearance Model

The seller submits the invoice XML to KSeF via API. KSeF validates the structure and content in real-time. If valid, KSeF assigns a unique KSeF number and the invoice becomes legally binding. If invalid, the invoice is rejected and must be corrected before resubmission. No invoice exists legally until KSeF approves it.

Central Storage

KSeF stores all validated invoices centrally for 10 years. Both seller and buyer can retrieve invoices from KSeF at any time via API. This eliminates the need for bilateral invoice exchange — the buyer doesn't receive the invoice from the seller directly; they pull it from KSeF.

Authentication & Authorization

Access to KSeF requires qualified electronic signatures or trusted profiles (Profil Zaufany). Businesses authenticate via OAuth 2.0 tokens issued after identity verification. Role-based permissions control who can submit invoices, retrieve them, or manage company-level settings.

Real-Time Tax Visibility

Because every invoice flows through KSeF, the Polish tax authority (KAS) has real-time visibility into all B2B transactions. This enables automated VAT cross-checking, significantly reduces the VAT gap (estimated at PLN 24 billion), and allows KAS to detect fraud patterns immediately.

POLAND KSEF — CONTINUOUS TRANSACTION CONTROL ARCHITECTURESELLER FLOWYour ERP / Billing SystemSAP · Dynamics 365 · Odoo · ComarchKSeF API GatewayREST API · OAuth 2.0 · FA(3) SchemaKSeF Central PlatformValidation · Numbering · StorageTax Authority (KAS)Real-time VAT data · AnalyticsBUYER FLOWKSeF assigns unique numberInvoice becomes legally validBuyer pulls invoice from KSeFAPI download · Batch retrievalBuyer ERP processes invoiceAutomated posting · 3-way matchKSeF = Krajowy System e-Faktur · CTC model · FA(3) XML schema · Real-time validation

Timeline & Phases

Poland's KSeF rollout was originally scheduled for July 2024 but was postponed after scalability concerns emerged during stress testing. The revised timeline splits the mandate into two phases:

KSeF Mandate Timeline

2022KSeF launched as a voluntary system — early adopters could use it optionally
Jul 2024Original mandatory go-live date — postponed due to scalability concerns after stress testing
Feb 1, 2026Phase 1: Mandatory for enterprises with annual revenue exceeding PLN 200 million
Apr 1, 2026Phase 2: Mandatory for ALL remaining VAT-registered businesses — no exceptions
Jul 2026Full enforcement begins — penalties for non-submission to KSeF

The PLN 200 million revenue threshold for Phase 1 means approximately 2,000–3,000 of Poland's largest enterprises went live first, serving as a real-world stress test for the platform. Phase 2 brings in the remaining ~2.3 million VAT-registered businesses. The three-month grace period (April–July 2026) allows businesses to correct initial errors without penalties.

Technical Requirements

Integrating with KSeF is a technical undertaking that requires API connectivity, schema compliance, and authentication infrastructure. Here are the core requirements:

FA(3) XML Schema

All invoices submitted to KSeF must conform to the FA(3) schema — Poland's national e-invoice structure. This is NOT the same as UBL 2.1 or CII used in other EU countries. The FA(3) schema defines mandatory fields including NIP (Polish tax ID) for both parties, line-item detail with PKWiU codes (Polish classification), VAT rates, and payment terms. Your ERP must generate this specific XML format.

REST API Integration

KSeF exposes a REST API for invoice submission, retrieval, and status checking. The API uses OAuth 2.0 for authentication and supports both synchronous (single invoice) and asynchronous batch (up to 100 invoices per request) submission modes. Rate limits apply — currently 500 requests per minute per taxpayer.

Authentication Options

Three authentication methods are supported: (1) Qualified Electronic Signature (kwalifikowany podpis elektroniczny), (2) Trusted Profile (Profil Zaufany) — Poland's national digital identity, or (3) Authorization token issued by KSeF after initial identity verification. Most automated systems use tokens for machine-to-machine API calls.

Real-Time Validation

KSeF validates each invoice in real-time (target: under 2 seconds). Validation checks schema conformance, NIP validity, VAT calculation correctness, and mandatory field presence. Invalid invoices receive an error response with specific error codes. The invoice only becomes legally valid when KSeF assigns its unique KSeF number.

Storage & Retrieval

KSeF stores all validated invoices for 10 years. Buyers retrieve invoices via API using their NIP and date range queries. Sellers can check delivery status and download sent invoices. The platform supports both pull (buyer-initiated) and notification (webhook) models for new invoice alerts.

Compliance Checklist

Whether you're a Polish business preparing for the April 2026 mandate or an EU company with Polish trading partners, use this checklist:

1
Register for KSeF Access

Register your company on the KSeF platform using your NIP (Numer Identyfikacji Podatkowej). Set up authentication — either a qualified electronic signature or generate an authorization token via Trusted Profile. Assign roles to staff who will manage invoice submission and retrieval.

2
Map Your Invoices to FA(3) Schema

Audit your current invoice templates and map every field to the FA(3) schema. Pay special attention to Polish-specific fields: NIP format validation, PKWiU product codes, GTU codes (Grupy Towarów i Usług), and the specific VAT rate encoding expected by KSeF. Missing or incorrect mappings are the #1 cause of rejection.

3
Implement API Connectivity

Build or configure your KSeF API integration. Options include direct API integration (for custom ERP systems), ERP vendor modules (SAP, Comarch ERP, Sage Symfonia have released KSeF modules), or a compliance middleware platform like InvoStaq that handles API connectivity, schema mapping, and error management.

4
Test in KSeF Test Environment

KSeF provides a dedicated test environment (środowisko testowe) where you can submit test invoices without legal consequences. Run at least 200 test invoices covering your full scenario range — standard invoices, credit notes (faktura korygująca), advance invoices (faktura zaliczkowa), and self-billing scenarios.

5
Set Up Buyer-Side Retrieval

If you receive invoices from Polish suppliers, implement KSeF retrieval automation. Configure your system to poll KSeF for new invoices (or set up webhook notifications), download them in FA(3) format, convert to your ERP's native format, validate, and post to accounts payable.

6
Configure Error Handling & Monitoring

Build robust error handling for KSeF rejections. Common errors include NIP validation failures, schema violations, and rate limit hits during peak periods. Set up dashboards to monitor submission success rates, average validation times, and rejection patterns. InvoStaq's Traffic Light Protocol provides instant visual feedback.

Common Challenges

Early adopters and Phase 1 enterprises have already surfaced the most common challenges with KSeF:

FA(3) schema strictness: KSeF validation is significantly stricter than most businesses expect. Fields that were optional in paper/PDF invoicing are mandatory in FA(3), and data types are enforced rigidly. A NIP with hyphens instead of plain digits will be rejected.
Credit note complexity: Corrective invoices (faktury korygujące) in KSeF must reference the original KSeF number of the invoice being corrected. This creates a dependency chain — if the original was never submitted to KSeF, you cannot issue an electronic correction.
Platform downtime handling: When KSeF is unavailable (planned maintenance or unexpected outage), businesses must follow specific offline procedures. Invoices issued during downtime must be submitted to KSeF within 7 days of service restoration. The offline workflow requires careful tracking to avoid missed submissions.
Cross-border invoice handling: Foreign businesses selling to Polish buyers are currently NOT required to use KSeF, but the Polish buyer will expect to find the invoice in KSeF. This creates tension — some Polish buyers are requesting foreign suppliers to register and submit through KSeF voluntarily.
Performance at scale: Large enterprises processing 10,000+ invoices daily reported initial throughput challenges with KSeF's API rate limits. Batch submission (asynchronous mode) is essential for high-volume issuers. Sequential single-invoice submission is too slow for enterprise volumes.
ERP integration timeline: Major Polish ERP vendors (Comarch, Asseco, Sage Symfonia) released KSeF modules, but international ERPs (SAP, Dynamics 365, Oracle) required longer adaptation periods. Businesses using non-Polish ERPs should budget 3–6 months for integration, not weeks.

Penalties for Non-Compliance

Starting July 2026, businesses that fail to submit invoices through KSeF face penalties of up to 100% of the VAT amount on non-compliant invoices. Additionally, invoices not submitted through KSeF will not be considered legally valid for VAT deduction purposes — meaning the buyer cannot deduct input VAT on invoices received outside the KSeF system. This creates strong incentives for both sellers and buyers to ensure full KSeF compliance.

KSeF Integration in Days, Not Months

InvoStaq's certified KSeF connector handles FA(3) schema mapping, API authentication, submission, and retrieval — connecting your ERP to Poland's mandate without a full system overhaul.