E-Invoicing in Poland: A Complete How-To Guide

Europe is increasingly moving toward a tax-policy of real-time e-invoicing, and Poland is one of the most advanced countries in Europe when it comes to this real-time tax control. As of April 1, 2026, its national e-invoicing system, KSeF, is now mandatory for most businesses. If you sell to Polish customers or operate in Poland, here is everything you need to know.

What E-Invoicing In Poland Means Today

An e-invoice (short for electronic invoice) is a structured digital process where all invoices sent by a business are submitted to a government platform, validated, assigned a unique reference number, and then made available to the buyer. An invoice is not legally issued until Poland’s KSeF validates it.

KSeF stands for Krajowy System e-Faktur aka the National e-Invoicing System and is the Polish e-invoicing platform. KSeF is a centralized platform managed by the Polish Tax Administration for the issuance and receipt of structured invoices. Every invoice must be submitted in XML format, following a specific government-defined schema called FA(3). The system will validate the content and assign a unique identifier called a KSeF ID. Only after validation is the invoice considered officially issued.

Sometimes called clearance e-invoicing, this process gives tax authorities real-time visibility into every transaction occurring in the country.

The History of E-Invoicing in Poland

Poland was an e-invoicing early adopter. Since 2019, public entities in Poland have been mandated to receive and process e-invoices through the PEF platform. That early B2G e-invoicing (business-to-government) system laid the groundwork for today’s e-invoicing mandate.

KSeF became available for voluntary use on January 1, 2022, with incentives like faster VAT refunds to encourage early adoption from businesses. The mandatory rollout was originally planned for July 2024, but was delayed after technical and readiness concerns were raised by businesses.

On August 27, 2025, Poland's President signed into law the amendment to the Value-Added Tax Act, establishing KSeF as a mandatory national e-invoicing system, effective from February 1, 2026. The KSeF 2.0 update introduced improvements to the schema, new authentication methods, and a permanent offline mode for connectivity disruptions.

Poland’s 5-Corner Clearance Model

Most e-invoicing frameworks use a 4-corner model. The supplier sends an invoice to their Access Point, which routes it to the buyer's Access Point, which delivers it to the buyer. Poland adds a fifth corner: the tax authority itself.

The KSeF platform has additional e-invoicing requirements. It operates on a clearance model, meaning that invoices must be submitted to and validated by a central government platform before being considered legally issued and delivered. This system effectively combines e-invoicing with real-time e-reporting, providing tax authorities with immediate, granular transaction data. 

In Poland's 5-corner model, KSeF sits in the middle of every transaction. The seller's system sends the invoice to KSeF. KSeF validates it. Then the buyer retrieves it from KSeF. And, crucially, the government sees everything.

Which Companies Need To Comply In Poland Right Now

Domestic B2B Invoicing For Polish Companies

The KSeF mandate currently covers domestic business-to-business (B2B) e-invoicing for businesses established in Poland.

This means all taxable persons (VAT taxpayers) who are required to issue invoices under Polish VAT law, with very limited exceptions, are required to issue e-invoices. All VAT-registered businesses in Poland, including corporations, SMEs, micro-businesses, and sole proprietors, fall into this category.

Large taxpayers with 2024 turnover exceeding PLN 200 million must begin issuing e-invoices via KSeF 2.0 as of February 1, 2026. The mandate then extends to all other VAT-registered businesses as of April 1, 2026, excluding micro-entrepreneurs.

If your business is established in Poland and issues VAT invoices to other businesses, you are almost certainly in scope.

Who Does Not Fall Under The Current Scope

Not every transaction goes through KSeF.

Domestic B2C transactions are excluded from mandatory e-invoicing because private consumers typically cannot access KSeF. Businesses continue using cash register receipts or traditional invoices for B2C, though voluntary KSeF use is permitted.

VAT registration alone does not trigger the obligation. Polish legislation states that the taxpayer must have either a registered office or a permanent establishment in Poland that participates in the transaction to fall under mandatory KSeF. Foreign entities that are VAT-registered in Poland but have no physical establishment there may not be required to use KSeF, depending on the nature of their transactions.

The Exemptions Regulation also identifies specific transactions exempt from structured e-invoicing due to technical constraints, such as highway tolls, passenger transportation tickets, and certain financial or insurance services.

What In-Scope Companies Need To Do Right Now

If your business is in scope, here is what tax compliance with e-invoicing looks like in practice.

You need to connect your ERP or billing system to KSeF through an e-invoicing provider. Your invoices must be generated in the FA(3) XML schema, validated by KSeF, and retrieved by your buyer through the same system. The invoice should be sent on an ongoing basis or at the latest the next working day. In the event of KSeF failure, the deadline for sending the invoice is seven working days from the resolution of the failure.

All businesses, regardless of size, were required to be ready to receive invoices via KSeF starting February 1, 2026. This means that even companies not yet required to issue through KSeF still need to be set up to receive from it.

How The KSeF Workflow Actually Works

The Seller to KSeF to Buyer Workflow

The operational flow in KSeF is fairly straightforward once you understand the 5-corner structure.

The seller's ERP or accounting system generates the invoice in the FA(3) XML format. That invoice is then sent to an e-invoicing provider, which submits it to KSeF via API. KSeF validates the invoice and, if it passes, assigns a unique KSeF ID number. The invoice is then stored in KSeF, where the buyer can retrieve it from their own KSeF account.

The entire process of sending, verifying, and making the invoice available to the customer takes only a few seconds. It is therefore no longer necessary to send invoices to customers via PDF in an email.

XML, Validation, and Invoice Clearance

On May 8, 2025, the Ministry of Finance published the draft FA(3) schema, which officially replaced the FA(2) schema as of January 2026. The FA(3) schema (invoicing process) introduces new mandatory and optional fields, strengthens validation controls, and improves consistency between tax and accounting data.

All statutory invoice elements must be populated in structured fields, including supplier and customer identifiers, dates, invoice numbering, itemized transaction details, VAT rates and amounts, totals, currency, and any legally required remarks such as reverse-charge indicators. 

Once the invoice is validated, KSeF assigns a unique reference number. That number becomes critical not just for the invoice record itself, but for what happens downstream in VAT reporting.

KSeF is also designed to store all invoices sent to the system for a period of 10 years from the end of the year in which they were issued. Taxpayers are therefore not required to archive invoices sent via KSeF themselves.

Why this Impacts VAT Reporting

KSeF is not just an invoicing change. It also directly affects how VAT returns are filed in Poland.

With the implementation of the KSeF system in 2026, VAT reporting in Poland will be based on e-invoicing. This means the data in your e-invoices and the data in your VAT returns need to match perfectly. If they come from separate systems, reconciliation becomes a significant risk.

What Mandates Are Coming Next In Poland

2026 Rollout Milestones

The phased KSeF rollout is already underway. Here is the timeline:

• February 1, 2026: E-invoicing mandatory for large taxpayers with 2024 gross sales exceeding PLN 200 million. 
• April 1, 2026: E-invoicing mandatory for all other VAT-registered entities, including SMEs and sole proprietors. 
• January 1, 2027: E-invoicing mandatory for micro-entrepreneurs with monthly sales under PLN 10,000.

To support businesses during this transition, the Ministry confirmed that no penalties will be imposed for errors in KSeF usage throughout 2026. That grace period ends on January 1, 2027, when enforcement begins in full.

Penalties may reach up to 100% of the VAT amount shown on an invoice issued outside KSeF. That is a serious financial risk for any business that waits too long to get compliant.

The obligation to include the KSeF number in bank transfers, including payments with a split payment mechanism, will apply to payments made from August 1, 2026

Future Scope Expansion

Poland is also aligning KSeF with broader EU digitization goals.

The EU's VAT in the Digital Age (ViDA) initiative might require e-invoicing for cross-border transactions by July 2030. The Polish Ministry of Finance is ensuring KSeF aligns with these potential future requirements. As EU-wide mandates come into effect, Poland's system is designed to expand to cover more transaction types, including cross-border flows.

The convergence of e-invoicing and VAT reporting is not unique to Poland. It is the direction the entire EU is heading.

Who Will Need to Comply Next

The next group entering scope is micro-entrepreneurs, defined as businesses with monthly sales below PLN 10,000, starting January 1, 2027. There is no blanket exemption based on size or sector beyond these phased thresholds. Micro-taxpayers receive temporary deferrals, not permanent exemptions. 

Businesses currently relying on cash register receipts or simplified invoices also need to plan. Taxpayers who issue simplified invoices for low amounts up to PLN 450 per invoice or PLN 10,000 per month may continue to use the current format until September 30, 2026. After that, they fall under the standard KSeF requirements.

Note that business to consumer (B2C) companies are not currently required to comply with the KSeF e-invoicing requirement as long as they only sell to consumers and not other businesses or the government. 

What Future In-Scope Companies Should Do Now

Prepare ERP and Finance Systems Early

The best time to start preparation and automation is before your compliance deadline arrives. The steps are technical, and they take time.

Start by auditing your current invoicing setup. Identify how your ERP or billing system generates invoices today and what it would take to output the FA(3) XML format. Then select an e-invoicing provider that can connect your system to KSeF via API.

You will also need to handle authentication. Entities other than natural persons may authenticate in the system using a qualified electronic seal, a token available until the end of 2026, or a KSeF certificate.

Map your existing invoice data to KSeF's required fields. The data that taxpayers have previously shown on their invoices must be mapped to the relevant fields of the KSeF invoice structure, so that the system can correctly generate an XML file in the format required by the Ministry of Finance.

Test your setup in the KSeF sandbox environment well before your go-live date. Do not wait until the last few weeks to streamline your e-invoicing compliance or you may find yourself missing the deadline and dealing with penalties.

Avoid Separate Invoice and Tax Data Systems

This is the operational decision that carries the most risk for finance teams.

When you use one provider for e-invoicing and a different provider for VAT returns, you create a reconciliation problem. Your VAT return now requires KSeF ID numbers that only exist in your invoicing system. If those two systems do not share the same underlying data, someone on your team has to manually bridge the gap every filing period.

The updated JPK_VDEK schema requires new, mandatory invoice reference data, and returns will be rejected if this data is missing. That means errors in your e-invoicing data can cause your VAT return to fail, even if every other part of the return is correct.

Businesses that run e-invoicing and VAT reporting through a single, unified data model avoid this problem entirely. Those running two separate systems will need to invest in integration work and ongoing reconciliation to keep both in sync.

How Sphere Simplifies E-Invoicing In Poland

Native Poland E-Invoicing Support in Q2 2026

Sphere is launching native e-invoicing functionality for Poland in Q2 2026. This support is purpose-built for KSeF workflows, meaning it handles the FA(3) XML schema, KSeF submission, validation, and ID retrieval as part of a single compliance workflow. There is no need to bolt on a separate invoicing tool or manage two vendor relationships.

One Shared Data Model for Invoices and Returns

Sphere's core differentiator in Poland is a shared data model for both e-invoicing and tax returns.

When your KSeF e-invoices and your VAT return filings live in the same system, the KSeF ID from every validated invoice flows automatically into the correct field of your JPK_VDEK return. There is no reconciliation step. There is no data mapping exercise at month-end. The source data for your e-invoices is the same source data that builds your VAT return.

This is a genuine advantage. In Poland's new compliance environment, the integrity of your VAT return depends on the accuracy of your invoice data. A shared data model makes that integrity automatic.

Why this Matters for Finance Teams 

Finance teams running two separate systems for invoicing and VAT filing face a specific and growing set of risks:

• KSeF ID mismatches cause VAT returns to be rejected outright
• Month-end close is delayed by manual reconciliation between invoice and filing data
• Audit exposure increases when invoice data and return data cannot be quickly verified against each other
• Penalty risk rises after January 1, 2027, when the full enforcement regime kicks in

Sphere eliminates all of these risks by keeping invoice data and filing data in one place.

Ready to simplify e-invoicing in Poland before the 2026 rollout?

Schedule a demo with Sphere today.

Book a Call

E-Invoicing In Poland Works Best When Invoice Data And VAT Returns Stay Unified

Poland's KSeF mandate is already in effect for large taxpayers, with the requirement expanding to all VAT-registered businesses in April 2026 and micro-entrepreneurs in January 2027.

The practical lesson from how KSeF works is this: e-invoicing in Poland is not a separate process from VAT reporting. The KSeF ID assigned to every invoice is a required field in your VAT return. That means your invoicing system and your tax return system are now the same system, whether you set it up that way or not.

Sphere is one of the only providers on the market that combines native e-invoicing and tax return filing in a single, unified data model. For finance teams managing Polish compliance, that means no reconciliation risk, no data mismatches, and no last-minute scramble to get two systems talking before a filing deadline.