KSeF impact on merch
A Poland operations guide on KSeF impact on merch invoicing — what the Krajowy System e-Faktur mandatory regime from 1 February 2026 means for merch supplier invoicing, the VAT 23% recovery chain, the NIP mapping the buyer has to set up, the ERP integration that bridges a merch supplier and a buyer's AP system, the common failure modes and the defensive disciplines.
What KSeF actually changes for merch invoicing in Poland
KSeF (Krajowy System e-Faktur) is the National e-Invoicing System operated by Krajowa Administracja Skarbowa (KAS). It is mandatory for B2B invoices from 1 February 2026, and it changes three things for merch invoicing: the invoice format becomes a structured XML delivered through the KSeF platform rather than a PDF or paper invoice, the invoice must be issued within a defined window, and the invoice must carry the right schema elements or it is rejected at issuance.
The operational consequences for a merch programme are not small. Every merch supplier that issues an invoice to a Poland-based B2B buyer has to be enrolled in KSeF as an issuer. Every merch buyer has to be enrolled in KSeF as a receiver. The invoice flow goes: supplier → KSeF platform → buyer AP system. The PDF or paper invoice flow that existed before 1 February 2026 is no longer valid for B2B merch transactions.
This piece is the operations view from both sides: what the supplier has to do, what the buyer has to do, what happens when either side gets it wrong, and what the defensive disciplines are.
The KSeF invoice structure for merch
A KSeF invoice for merch carries the standard Polish VAT-invoice elements plus the KSeF-specific schema. The structural elements that matter for merch invoicing are six.
Supplier's NIP (Numer Identyfikacji Podatkowej). The supplier's 10-digit tax identifier. The NIP must match the supplier's registered business in the KAS database, and the NIP must match the contracting entity. For a multi-entity supplier (a group with several Polish subsidiaries) the invoice must carry the NIP of the entity that is actually contracting with the buyer, not the group's central NIP. We have seen merch group assets fail to recover VAT 23% in 2024-2025 because the group issued the invoice under the central NIP rather than the contracting-entity NIP.
Buyer's NIP. The buyer's 10-digit tax identifier. The buyer's AP team has to map the receiving NIP in the KSeF account, and the mapped NIP has to match the NIP of the contracting entity on the buyer side. For a multi-entity buyer (a group with several Polish subsidiaries, common at companies like PKO BP, Pekao, ING Hubs Poland, ORLEN, PZU) the mapping has to be per receiving entity, not per group.
Invoice date. The date the invoice was raised through the KSeF platform. The merch programme typically needs the invoice within 30 days of the delivery; KSeF issues the invoice with a near-real-time timestamp, and the date on the receipt should match the date the supplier issued the invoice. Out-of-window invoices break VAT recovery for the period.
VAT line per item. Standard 23% VAT applies to every line item in a merch invoice. The 8% reduced rate applies to a narrow set of printed books and children's items; the 5% rate applies to basic foodstuffs. Neither applies to typical corporate merch. The KSeF schema validates the VAT rate against the item category at issuance, and a wrong rate is rejected.
Item description. Free text on what the item is. The KSeF schema does not enforce a standard merch vocabulary, but the description is what the buyer's AP system reads when it matches the invoice against the receiving warehouse confirmation. Good practice is to use the kit spec's item name (bottle 500ml, notebook A5, USB-C cable 1m, etc.) on every line.
Quantity and unit price. The number of items and the per-item net price in PLN. The KSeF schema validates that quantity × unit price equals the line net total, and that line net total × VAT rate equals the line VAT total. A mismatch is rejected at issuance.
The supplier-side operational disciplines
A merch supplier in Poland that sells to B2B buyers has to do five things to be KSeF-compliant by 1 February 2026.
1. Enrol in KSeF as an issuer. The supplier's tax representative enrols through the KAS portal and obtains a KSeF token. The token authorises the supplier's invoicing software (or ERP) to issue invoices through the platform. The supplier's invoicing software has to support the KSeF schema, which most major Polish accounting software packages do by 2026 (Enova, Symfonia, Sage, Comarch ERP, IFS, SAP with the local KSeF add-on).
2. Map the contracting-entity NIP. For multi-entity suppliers, each contracting entity has its own NIP and its own KSeF enrolment. The supplier's invoicing system has to be configured to issue invoices under the right NIP per buyer.
3. Validate the KSeF schema before issuance. The supplier's invoicing system has to validate every invoice against the KSeF schema before pushing it to the platform. Common rejections: VAT rate mismatch with item category, line-total arithmetic mismatch, missing required schema elements, buyer's NIP not enrolled as a receiver.
4. Issue within the standard window. The standard window for merch invoicing is 30 days from delivery. The supplier issues the invoice through KSeF and receives a KSeF-issued invoice number (the standard Polish invoice numbering convention applies, but with the KSeF prefix). The buyer receives the invoice in their KSeF account within seconds of issuance.
5. Reconcile the KSeF invoice against the merch delivery. The supplier's fulfilment team confirms the delivery to the buyer's warehouse, and the supplier's finance team issues the KSeF invoice. The two are reconciled in the supplier's internal system.
The buyer-side operational disciplines
A merch buyer in Poland that procures from B2B suppliers has to do five things to be KSeF-compliant by 1 February 2026.
1. Enrol in KSeF as a receiver. The buyer's tax representative enrols through the KAS portal and obtains a KSeF token. The token authorises the buyer's AP system to receive invoices through the platform. The buyer's AP software has to support the KSeF schema, which most major Polish ERP packages do by 2026.
2. Map the receiving-entity NIP. For multi-entity buyers, each contracting entity has its own NIP and its own KSeF receiver enrolment. The buyer's AP system has to be configured to receive invoices under the right NIP per supplier per contracting entity.
3. Validate every KSeF invoice on receipt. The buyer's AP team validates every KSeF invoice against the receiving warehouse confirmation. The matching has to be at the line-item level: quantity, item description, unit price. A mismatch is flagged for the supplier's correction.
4. Recover VAT 23% through the standard mechanism. The input VAT 23% is recoverable for the buyer through the standard JPK_V7 declaration, which the buyer's AP system submits monthly or quarterly depending on the buyer's filing frequency. The KSeF invoices are pulled into the JPK_V7 automatically through the AP system's KSeF integration.
5. Retain the KSeF invoice file for the standard 5-year window. KAS can request the KSeF invoice file at any point within the standard 5-year retention. The buyer's archive has to retain the KSeF invoice in its original schema, not as a printed PDF. A PDF print of a KSeF invoice is not the KSeF invoice for retention purposes.
Common failure modes we have seen in Poland
Three failure modes show up often enough that they are worth naming here.
The first is the wrong-NIP invoice. The supplier issues the KSeF invoice under the group's central NIP rather than the contracting entity's NIP, or the buyer's AP team has the receiving entity's NIP mapped incorrectly. The KSeF schema accepts the invoice at issuance (because the NIP is a registered NIP), but the JPK_V7 reconciliation breaks because the contracting-NIP-to-receiving-NIP pair is wrong. The fix is to map NIPs at the contracting-entity level on both sides and to validate the pair before the invoice is issued.
The second is the out-of-window invoice. The merch delivery happens on 15 March; the supplier's finance team issues the KSeF invoice on 20 April, 36 days later, missing the standard 30-day window. The buyer's VAT 23% recovery for the March-April transition period breaks for that line item. The fix is to set the supplier's internal SLA at 7 days from delivery to invoice issuance, with an automated flag at 21 days.
The third is the schema rejection. The supplier's invoicing system pushes the invoice to KSeF and the platform rejects it because of a schema mismatch (typically the VAT rate against item category). The supplier's finance team re-issues the invoice manually, but the manual re-issue happens outside the standard window and breaks the buyer's recovery chain. The fix is to validate every invoice against the KSeF schema before pushing to the platform, not after.
The KSeF and VAT 23% recovery chain
KSeF and the VAT 23% recovery chain are the same chain in 2026, but they used to be two separate chains. Before 1 February 2026, the merch invoice could be a PDF or paper, the buyer recovered VAT 23% through the standard JPK_V7 declaration based on the invoice data, and KAS could audit the invoice file at any point. After 1 February 2026, the merch invoice must be KSeF-structured, the buyer's AP system has to be integrated with KSeF, the JPK_V7 declaration pulls from KSeF automatically, and KAS can audit the KSeF invoice file directly.
The chain breaks at three points. The supplier is not enrolled in KSeF and the invoice is not issued through KSeF: the buyer's VAT 23% recovery breaks for that line item. The invoice is issued under the wrong NIP pair: the buyer's VAT 23% recovery breaks for that line item. The invoice is issued outside the standard window: the buyer's VAT 23% recovery breaks for that line item. Each break is recoverable but adds administrative overhead, and the cumulative break rate across a 12-month merch programme is the operational metric that matters.
The ERP integration mechanics
For a Poland-based merch programme with monthly merch spend above zł50,000 net, the KSeF integration with the buyer's AP system is the operational backbone. The integration typically goes through one of three routes.
Native KSeF integration. Major Polish ERP packages (Enova, Symfonia, Sage, Comarch ERP, IFS, SAP with the local KSeF add-on) have native KSeF integration by 2026. The AP system reads KSeF invoices directly, validates against receiving confirmations, and posts to JPK_V7 automatically.
KSeF API integration. For ERPs without native KSeF integration, a middleware layer sits between KSeF and the AP system. The middleware reads KSeF invoices through the KSeF API, translates them to the AP system's expected schema, and posts the data. The middleware has to maintain its own KSeF token and validate its own schema mapping.
Manual download. For small spend or low invoice volume, the buyer's AP team downloads KSeF invoices manually from the KAS portal and enters them into the AP system. This is the lowest-cost route but the highest-error route, and it does not scale above 50-100 invoices per month.
FAQ
When does KSeF become mandatory for B2B merch invoices?
From 1 February 2026, KSeF is mandatory for all B2B invoices in Poland, including merch invoices. Suppliers must be enrolled as KSeF issuers and buyers as KSeF receivers. PDF and paper invoices are no longer valid for B2B merch transactions.
What is the standard VAT rate on a merch invoice?
23% per line item. The 8% reduced rate applies to a narrow set of printed books and children's items; the 5% rate applies to basic foodstuffs. Neither applies to typical corporate merch. The KSeF schema validates the VAT rate against the item category at issuance.
What is the standard invoicing window for merch?
30 days from delivery to invoice issuance. Out-of-window invoices break the buyer's VAT 23% recovery for that period. The defensive discipline is to set the supplier's internal SLA at 7 days from delivery to invoice, with an automated flag at 21 days.
How does KAS audit KSeF invoices?
KAS can request the KSeF invoice file at any point within the standard 5-year retention window. The buyer must retain the KSeF invoice in its original schema, not as a printed PDF. A PDF print of a KSeF invoice is not the KSeF invoice for retention purposes.
What happens when the supplier issues an invoice under the wrong NIP?
The KSeF schema accepts the invoice at issuance because the NIP is registered, but the JPK_V7 reconciliation breaks because the contracting-NIP-to-receiving-NIP pair is wrong. The buyer's VAT 23% recovery breaks for that line item. The fix is to map NIPs at the contracting-entity level on both sides.
What is the typical KSeF integration model for a large merch programme?
Native KSeF integration through the buyer's ERP (Enova, Symfonia, Sage, Comarch ERP, IFS, SAP with the local KSeF add-on) for spend above zł50,000 net per month. Middleware KSeF API integration for ERPs without native support. Manual download for small spend or low invoice volume.