Poland's KSeF E-Invoicing Mandate Hits All Businesses April 1: What ERP Vendors Must Do Now

The clock is ticking. On April 1, 2026, Poland's Krajowy System e-Faktur (KSeF) becomes mandatory for all remaining VAT-registered entities — including SMEs and sole proprietors. If your ERP platform serves clients in Poland and you haven't finished your KSeF integration, you have just over two weeks to get it done.

Phase 1 went live on February 1 for large taxpayers (those with 2024 gross sales exceeding PLN 200 million), and early reports suggest the system is stabilizing after initial teething issues. Now, the floodgates open for everyone else.

What's confirmed and what's still uncertain

Confirmed:

The KSeF 2.0 mandate was signed into law by President Karol Nawrocki on August 27, 2025. The phased rollout is final and legally binding:

• February 1, 2026 — Large taxpayers (2024 turnover > PLN 200M) — already live
• April 1, 2026 — All other VAT-registered entities, including SMEs and sole proprietors
• January 1, 2027 — Micro-entrepreneurs with monthly sales under PLN 10,000

Still evolving:

While the law is settled, ANAF continues to release technical clarifications. ERP vendors should monitor the KSeF API documentation portal for any last-minute schema updates or endpoint changes.

The exact timeline you need to know

The Ministry of Finance has announced an 11-month penalty-free soft landing running through January 1, 2027. This means that while you must issue through KSeF from April 1, actual fines won't be imposed until 2027. However, this is not a reason to delay — the obligation to use KSeF is real, and non-compliant invoices will not be considered legally valid B2B invoices.

What ERP vendors need to implement

1. FA(3) XML format support

All invoices must conform to Poland's FA(3) XML schema, which is Poland's localized implementation of the EN 16931 European standard. Your ERP must generate invoices in this exact format — UBL or CII won't be accepted directly.

Key technical points:

• The FA(3) schema includes Poland-specific fields not found in the base EN 16931 standard
• Invoice validation is performed server-side by KSeF before an invoice number is assigned
• Rejected invoices must be corrected and resubmitted — your ERP needs error-handling workflows for this

2. KSeF API integration

Your system needs to connect to the KSeF platform via its REST API for:

• Submitting invoices — POST requests with signed FA(3) XML payloads
• Receiving invoices — polling or webhook-based retrieval of incoming invoices
• Status checking — monitoring whether submitted invoices were accepted or rejected
• Batch operations — the API supports batch submission, which is critical for high-volume clients

3. Authentication and authorization

KSeF uses a token-based authentication system. Your ERP must support:

• Qualified electronic signatures or qualified electronic seals for invoice signing
• Authorization token management (tokens have expiration windows)
• Multi-entity support if your clients operate multiple VAT registrations

4. Offline mode handling

When KSeF experiences downtime (which has happened during Phase 1), businesses can issue invoices offline. Your ERP must:

• Generate invoices with a QR code for verification
• Queue offline invoices for automatic upload when KSeF comes back online
• Ensure offline invoices are uploaded by the next business day

5. KSeF number integration

Every invoice processed through KSeF receives a unique KSeF number. From January 1, 2027, this number must appear in payment titles. Your ERP should start capturing and storing KSeF numbers now.

Common mistakes and how to avoid them

Mistake 1: Treating the soft landing as an extension. The April 1 date is real. The soft landing only defers penalties — it doesn't defer the obligation. Clients who continue issuing PDF invoices after April 1 are technically non-compliant, and their trading partners may reject non-KSeF invoices.

Mistake 2: Not testing with the KSeF sandbox. The Polish Ministry of Finance provides a test environment. If your ERP hasn't been validated against the sandbox, you're flying blind. Schema validation errors are the most common cause of rejected invoices.

Mistake 3: Ignoring the receiving side. Even if your client isn't required to send via KSeF yet (micro-entrepreneurs until 2027), all businesses must be able to receive KSeF invoices from February 1, 2026. Make sure your ERP can ingest and process incoming FA(3) XML invoices.

Mistake 4: Hardcoding authentication credentials. KSeF tokens expire and must be refreshed. ERP systems that hardcode credentials will break in production. Implement proper token lifecycle management.

Mistake 5: Not handling batch failures gracefully. In batch submissions, individual invoices can fail while others succeed. Your ERP must handle partial batch failures without losing data.

Technical readiness checklist

• FA(3) XML schema generation implemented and tested
• KSeF REST API integration complete (submit, receive, status check)
• Authentication flow working with qualified e-signatures/e-seals
• Sandbox testing completed with representative invoice samples
• Offline mode with QR code generation implemented
• KSeF invoice number capture and storage in place
• Error handling for rejected invoices (retry, correction workflow)
• Batch submission support for high-volume clients
• Receiving pipeline for incoming KSeF invoices
• Client-facing documentation and migration guides prepared
• Monitoring and alerting for KSeF API availability

Frequently asked questions

Do B2C invoices need to go through KSeF?

No. Invoices issued to private individuals (consumers) are not subject to mandatory KSeF clearance. Traditional invoicing and fiscal receipts continue to apply for B2C, although voluntary KSeF use is permitted.

What happens if KSeF is down when we need to send invoices?

Businesses can issue invoices offline during KSeF downtime. These invoices must include a QR code for verification and be uploaded to KSeF by the next business day after the system is restored.

Is there a faster VAT refund for KSeF users?

Yes. Businesses using KSeF are entitled to VAT refunds in 40 days instead of the standard 60 days. This is a significant cash flow benefit that can help justify the integration investment to your clients.

What are the penalties for non-compliance after January 2027?

While specifics are still being finalized, the law provides for financial penalties for failing to issue invoices through KSeF. The 11-month soft landing means enforcement begins January 1, 2027.

Can we use EDI instead of the KSeF API?

KSeF requires direct API integration — EDI is not a substitute. However, you can use EDI internally and translate to FA(3) XML at the KSeF submission layer.

What about credit notes and corrective invoices?

Corrective invoices must also be issued through KSeF using the same FA(3) XML format. The schema includes specific document type codes for corrections and credit notes.

What happens next

After the April 1 Phase 2 deadline, the focus shifts to:

• January 1, 2027: Micro-entrepreneurs join the mandate, and the penalty-free grace period ends for all taxpayers
• January 1, 2027: KSeF numbers become mandatory in payment titles
• 2030+: Poland will align with the EU ViDA framework for cross-border e-invoicing

Don't wait — act now

With 17 days to go, this is not the time for analysis paralysis. If your ERP integration is 80% complete, focus on the critical path: schema validation, API connectivity, and error handling. The sandbox is your best friend right now.

Invoice Navigator's compliance infrastructure handles the complexity of KSeF integration so your ERP doesn't have to. Our API translates your existing invoice data into compliant FA(3) XML, manages the KSeF submission lifecycle, and handles offline fallback — all through a single endpoint. Learn more about our Poland compliance tools →