A mid-sized Polish manufacturing company – with over 200 suppliers and a complex intercompany billing structure – received a notice from its ERP provider in late 2025. The message was blunt: the system would not be ready for the National e-Invoice System (Krajowy System e-Faktur, KSeF) by the statutory deadline. The finance director had 90 days to find a solution. That is a tight window when structured invoicing processes, transfer pricing documentation, and internal approval chains are all in play.
Poland's KSeF obligation applies in two waves. Large taxpayers – those whose annual turnover exceeded PLN 200 million in the prior tax year – must issue invoices exclusively through KSeF from 1 July 2026. All remaining VAT-registered businesses follow on 1 January 2027. Failure to comply triggers financial penalties of up to PLN 100 per non-compliant invoice, and the National Revenue Administration (Krajowa Administracja Skarbowa, KAS) has confirmed it will enforce the regime from day one.
This case study traces how one Polish manufacturer restructured its invoicing operations in time. It covers the background challenge, the compliance strategy adopted, the implementation process, and the lessons that apply to any business – domestic or foreign – facing the same countdown.
What was the compliance challenge?
The company operated across three legal entities registered in the National Court Register (Krajowy Rejestr Sądowy, KRS). Each entity issued invoices under a different template and approval workflow. Some invoices were generated by the ERP system; others were produced manually in spreadsheets and signed off by regional managers. The mix created an immediate problem: KSeF requires every B2B invoice to carry a unique KSeF identification number issued in real time by the Ministry of Finance (Ministerstwo Finansów) system. Manual workarounds are not permitted.
Intercompany transactions added a further layer. The group had transfer pricing arrangements in place, and each intragroup invoice had to reflect agreed arm's-length pricing. Any mismatch between the invoice amount logged in KSeF and the transfer pricing documentation could attract KAS scrutiny. The finance team had never mapped this exposure before. Identifying it took three weeks alone.
The company also held an IP Box election – a preferential 5% corporate income tax rate on qualifying intellectual property income. IP Box calculations depend on precise cost allocation, which in turn depends on accurate invoicing records. A disrupted invoicing chain risked corrupting the cost basis and invalidating the IP Box position for the 2026 tax year.
How did the compliance strategy address each risk?
The strategy rested on three parallel workstreams, each with a fixed owner and a hard internal deadline 30 days before the statutory KSeF go-live date. That buffer was non-negotiable. A last-minute system failure with no fallback would mean non-compliant invoices from day one – an irreversible consequence given that KSeF numbers cannot be retroactively assigned to invoices issued outside the system.
First, the legal team mapped all invoice flows against the KSeF invoice schema published by the Ministry of Finance. The schema specifies over 400 data fields, of which roughly 30 are mandatory for standard B2B transactions. Every existing invoice template was audited against this list. Templates that could not be adapted were retired. The company consolidated from eleven templates to four.
Second, transfer pricing documentation was reviewed alongside the invoicing audit. We secured a formal alignment between the group's transfer pricing policy and the revised invoice fields – ensuring that the arm's-length price, the cost allocation code, and the entity identifier all appeared consistently. This work, completed for a manufacturing group in the Mazowieckie region in winter 2025–2026, prevented what could have been a six-figure transfer pricing adjustment.
Third, the IP Box cost allocation model was rebuilt around the new invoice structure. The revised model used KSeF-generated invoice numbers as the primary reference for qualifying expenditure. That change made the IP Box calculation auditable from the source document – a significant improvement over the prior spreadsheet-based approach.
What did the implementation process involve?
Implementation ran across eight weeks. The timeline was tight but achievable because the legal and technical workstreams ran in parallel rather than sequentially. A common failure in KSeF projects is treating legal compliance and IT integration as separate phases. That approach typically adds six to eight weeks – time most companies do not have.
Week one through three focused on data mapping and ERP configuration. The ERP provider – once given a precise field-by-field specification – was able to adapt the invoice module within the agreed timeline. The key was specificity: vague requests produce vague outputs. The legal team's schema audit translated directly into a technical brief the IT team could action.
Week four and five covered internal testing. The company submitted test invoices to the Ministry of Finance sandbox environment and resolved four structural errors before any live invoice was at risk. One error involved an incorrect tax identification number (NIP) format for a foreign supplier. Under KSeF rules, invoices with an invalid NIP are rejected outright – there is no grace period for format errors.
Weeks six through eight were used for staff training and a parallel-run period. During parallel running, invoices were issued both through the legacy system and through KSeF. Discrepancies were logged and resolved. By the end of week eight, the company had processed over 1,400 test invoices with a 99.3% acceptance rate from the KSeF system.
- Legal schema audit against Ministry of Finance field requirements
- Transfer pricing and IP Box alignment before go-live
- ERP configuration based on a precise technical brief
- Sandbox testing with error resolution before live submission
- Parallel-run period to validate acceptance rates
For businesses with cross-border invoicing exposure, the KSeF implementation raises additional questions about how Polish obligations interact with foreign VAT regimes. Our earlier analysis of what KSeF means for businesses in Cyprus sets out how the system affects companies with Polish-Cypriot structures. The KSeF deadline timeline for companies in Switzerland addresses similar questions for Swiss-headquartered groups with Polish subsidiaries.
One practical note on cost recovery: where KSeF non-compliance leads to disputed invoices and subsequent litigation, the question of who bears legal costs becomes relevant. Polish civil proceedings have specific cost recovery rules that affect how disputes are resolved. Our guide on cost recovery rules in Polish civil proceedings provides a useful reference for any business facing that scenario.
Your company's specific KSeF exposure depends on turnover, entity structure, and invoicing complexity. Delaying the assessment forfeits the buffer period that makes orderly implementation possible. To discuss how the KSeF timeline applies to your structure, email info@kordeckipartners.com.
What lessons transfer to other businesses facing the KSeF deadline?
Four lessons emerge from this matter. They apply whether a company is a large taxpayer facing the 1 July 2026 deadline or a smaller business preparing for 1 January 2027.
The first lesson is that the legal audit must precede the IT project. Companies that start with ERP configuration before mapping their invoice flows against the KSeF schema typically discover structural problems mid-implementation. Fixing schema errors after ERP configuration has begun doubles the cost and compresses the testing window. Start with a field-by-field legal audit. That document becomes the IT brief.
The second lesson concerns connected tax positions. KSeF compliance is not a standalone VAT project. It touches transfer pricing (through invoice fields that carry pricing data), IP Box (through cost allocation references), and potentially other tax positions that depend on invoice-level data. A tax advisor Warsaw-based or otherwise should review all connected positions before go-live, not after.
The third lesson is that the sandbox environment is not optional. The Ministry of Finance testing environment exists precisely to catch format errors before they affect live invoices. Companies that skip sandbox testing and go live directly face rejection rates that can paralyse invoicing operations. One rejected invoice does not trigger a penalty; a pattern of rejections does.
The fourth lesson is about the family foundation question that occasionally arises in this context. Where a Polish family foundation holds shares in an operating company subject to KSeF, the foundation itself may have invoicing obligations depending on whether it conducts economic activity. That question requires a separate legal assessment – it is not resolved by the operating company's KSeF implementation alone.
For businesses that have not yet begun their KSeF assessment, the window is narrowing. The 1 July 2026 deadline is a hard statutory date. Polish tax law does not provide for individual extensions. Personal liability of management board members for tax compliance failures is a real risk under Polish corporate legislation – and KSeF non-compliance falls within that framework.
Frequently asked questions
Q: Does KSeF apply to invoices issued to foreign buyers?
A: KSeF applies to invoices issued by Polish VAT-registered businesses for transactions subject to Polish VAT. Invoices for intra-EU supplies and exports – where Polish VAT does not apply – are currently outside the mandatory KSeF scope. However, the Ministry of Finance has indicated that voluntary KSeF use for these invoices is possible, and the rules may be extended. Businesses with significant cross-border invoicing should monitor guidance from the Polish Financial Supervision Authority (Komisja Nadzoru Finansowego, KNF) and the Ministry of Finance for updates.
Q: How long does a realistic KSeF implementation take for a mid-sized company?
A: For a company with multiple legal entities and a mixed invoicing environment, eight to twelve weeks is a realistic minimum. That assumes the legal schema audit is completed before ERP configuration begins. Companies that start the legal and IT workstreams simultaneously can compress the timeline, but only if communication between the two teams is structured and daily. Businesses starting after April 2026 for the July deadline should treat the timeline as a serious risk.
Q: Is there a common misconception about KSeF penalties?
A: Yes. Many finance teams assume that KSeF penalties apply only to wilful non-compliance. That is incorrect. Under Polish tax law, the penalty of up to PLN 100 per invoice applies to each invoice issued outside the KSeF system after the mandatory deadline, regardless of intent. A technical failure on the issuer's side – such as an ERP outage – does not automatically exempt the business. The law provides a narrow offline mode exception, but it has strict conditions and time limits that must be met in advance, not at the moment of failure.
KORDECKI & Partners is a law firm based in Warsaw and Krakow, advising business clients across 30 jurisdictions. Our team combines expertise in Polish and international law with a practical approach to KSeF compliance, VAT advisory, and tax structuring. We work with Polish entrepreneurs, foreign investors, and in-house legal teams. To discuss your situation, contact info@kordeckipartners.com.
Disclaimer: This publication is provided for informational purposes only and does not constitute legal advice. The information herein should not be relied upon as a substitute for professional legal counsel tailored to your specific circumstances. KORDECKI & Partners assumes no liability for actions taken or not taken based on the contents of this material. For advice regarding your particular situation, please contact info@kordeckipartners.com.