If your company issues or receives B2B invoices in Poland – through a subsidiary, a local supplier, or a customer relationship – the rules just changed.
As of April 1st, 2026, KSeF (Krajowy System e-Faktur), Poland’s national e-invoicing platform, is mandatory for all B2B transactions in the country.
For international companies with Polish operations, this mandate affects every invoice you issue or receive. Non-compliance carries financial penalties, and the grace period runs only through December 31, 2026.
Here’s what your finance and compliance teams need to know and what ‘being ready’ actually requires.
Key compliance dates
| Date | Requirement | Who it affects |
|---|---|---|
| February 1, 2026 | Receiving KSeF invoices mandatory | All companies operating in Poland |
| April 1, 2026 ✓ NOW LIVE | Sending KSeF invoices mandatory | Medium & small companies |
| January 1, 2027 | Full mandate including micro-businesses, cash register integration & KSeF invoice numbers | All remaining businesses |
Note: A grace period with no financial sanctions runs through December 31, 2026, but operational readiness cannot wait that long. B2C transactions may go through KSeF but are not required to. Paper and PDF remain permitted for B2C. All invoices, regardless of format, must be archived for five years.
How Poland’s KSeF mandate evolved and what changed in 2026
Poland’s path to mandatory e-invoicing has been gradual. Since 2019, all Polish public administrations have been required to accept electronic invoices, but issuance wasn’t mandatory. Businesses could still issue paper or PDF invoices, as long as a complete audit trail was maintained.
On the B2G side, voluntary e-invoicing was handled through PEF – Poland’s central government platform – using the Peppol BIS 3.0 UBL format or its Polish variant. PEF is directly connected to the broader European Peppol network.
The 2026 mandate changes everything for B2B transactions. KSeF is now the only permitted channel for B2B invoicing in Poland, running on the FA(3) XML format – a structured standard that is not interchangeable with Peppol or PDF.
For B2G transactions, suppliers may still choose between PEF – in Peppol BIS 3.0 or KSeF – in FA(3), but for B2B, KSeF is the only option.
What is KSeF and why does it matter for international companies?
KSeF is Poland’s centralized invoicing platform, operated directly by the Ministry of Finance. Every B2B invoice issued in Poland must be submitted to, validated by, and retrieved from this government system. There are no exceptions and no workarounds.
For Polish businesses, this has been on the radar for years. For international companies with subsidiaries, suppliers, or customers in Poland, it’s easy to underestimate how different this model is.
This is not about converting a PDF into a new file format. KSeF operates in real time. If your invoicing workflow isn’t integrated with KSeF, you’re not just non-compliant – your invoices are invisible to your Polish counterparts. Transactions cannot be processed, payments may be delayed, and your VAT position becomes exposed.
Already operating in Poland? |
Talk to us about your KSeF readiness. We can map your current invoicing setup against the mandate requirements and tell you exactly what needs to change. |
FA(3) format: the technical requirements for KSeF compliance
The KSeF mandate is built around the FA(3) data model – a structured semantic XML format that goes well beyond a standard invoice layout.
Semantic parsing means understanding what each field in the FA(3) structure actually represents, not just reading the data into your system. The format carries detailed information about parties, line items, tax classifications, and payment terms in a way that tax authorities can validate automatically.
Getting this right requires three distinct capabilities:
- Semantic parsing of FA(3). Your system needs to understand the meaning of each field, not just its position in the XML. Errors in field mapping can cause validation failures at the KSeF platform before an invoice is even accepted.
- Bidirectional integration with KSeF. You need to both submit outgoing invoices and retrieve incoming ones through the government platform – in real time, not via batch uploads.
- Party identification and VAT compliance checks. Every transaction in KSeF is tied to validated business identifiers. VAT compliance in Poland requires ongoing verification against local statutory registers – not a one-time check at onboarding. Getting this wrong has direct tax consequences.
That last point catches many international teams off guard. Supplier VAT status can change. If you’re not continuously verifying against current Polish registers, you carry the compliance risk.
How Profluo handles KSeF compliance end-to-end
Profluo’s platform is fully operational for KSeF compliance. Here’s how it addresses each of the technical requirements above.
- FA(3) semantic parsing
Profluo covers the complete FA(3) data model with full semantic parsing, meaning the platform understands what the data means and handles it accordingly, rather than treating it as raw XML to be mapped field-by-field.
- Bidirectional KSeF integration
Invoices flow out and invoices flow in, staying in continuous sync with the Ministry of Finance platform without manual intervention. No batch windows, no missed updates.
- Automated party and VAT verification
Profluo connects directly to Polish statutory registers to handle party identification and VAT compliance checks automatically. Your team isn’t manually verifying supplier registrations every time a new invoice lands.
- Intelligent invoice processing
On top of the compliance infrastructure, Profluo’s agentic AI layer automatically analyzes incoming invoices in context – cross-referencing against your records, flagging anomalies, and routing for approval – rather than landing them in someone’s inbox to wait.
- Contract and commercial verification
Profluo’s AI agents check whether invoices align with agreed terms and contracts, catching discrepancies before they become disputes or delayed payments.
- Configurable approval workflows
A flexible automation engine lets you configure approval flows, confidentiality rules, and notifications to match your actual organizational structure. For international businesses where approvals cross teams, entities, and time zones, this makes a meaningful operational difference.
Where AI-assisted automation makes the real difference
Manual compliance processes were already under strain before KSeF came along. The mandate adds a new layer: real-time interaction with a government system, on top of everything else your finance team is managing.
The most effective use of automation here isn’t about replacing accountants; it’s about giving them better information faster. Instead of someone manually cross-referencing an incoming invoice against purchase orders, contracts, and supplier records, an AI agent does that work in the background and surfaces only the exceptions that genuinely require human judgment.
The accountant’s job becomes decision-making, not data entry.
We’re already seeing international finance teams treat KSeF readiness as a Q1 priority. Not because the grace period is ending, but because the operational risk of running a manual process against a real-time government platform is simply too high.
KSeF compliance checklist: what being ready actually requires
Compliance with KSeF is an ongoing operational capability, not a one-time implementation. Here’s what that means in practice:
- Real-time connectivity. Your systems need to communicate with KSeF continuously. Invoices must flow in and out on the platform’s timeline, not via scheduled batch uploads.
- Accurate, current party data. Every transaction is tied to validated business identifiers. Outdated VAT numbers or incomplete supplier records become compliance problems immediately.
- Audit-ready internal processes. KSeF provides the government with full transaction visibility. Your internal processes need to match – approvals documented, exceptions logged, nothing falling through the cracks.
- An adaptable technical solution. Polish tax regulations continue to evolve, as they do across the EU. Whatever you put in place needs to be maintainable and updatable without requiring a full overhaul when requirements change.
Poland is the preview, the rest of Europe follows
Poland’s KSeF mandate is part of a broader European shift toward centralized e-invoicing and real-time tax reporting. Italy has operated a similar system since 2019. France and Germany are moving in the same direction under the EU’s VAT in the Digital Age (ViDA) initiative.
What’s happening in Poland today is a preview of what finance and compliance teams across the continent will be navigating over the next three to five years.
For international businesses, the cost of fragmented, country-by-country compliance approaches is rising fast. Building the capability to handle structured e-invoicing mandates – with AI-assisted workflows that make them manageable – isn’t just about Poland. It’s about being structurally ready for what comes next.
The mandate is live. Is your operation ready?
The grace period (no financial sanctions) runs through December 31, 2026, after which penalties apply. If your operations aren’t aligned with the requirements, now is the time to act.
Book a 30-minute KSeF readiness call with our team. We’ll walk you through exactly what compliance looks like for your invoicing setup.
