The transition is no longer a future boardroom discussion. Poland’s National e-Invoicing System (KSeF) is now live, forcing an immediate operational shift for building materials merchants across the supply chain. Under the legal framework of the Act of August 5, 2025, the rollout has moved forward in strict phases [1]. Large merchants with a 2024 sales value exceeding PLN 200 million were required to begin issuing structured KSeF invoices on February 1, 2026 [1], [4], which is also the date the mandatory obligation to receive invoices in KSeF took effect [3]. For small and medium-sized merchants, the mandatory issuance obligation began shortly after, on April 1, 2026 [1], [8].

This leaves merchants sitting in a difficult position. As intermediaries buying from large manufacturers and selling to contractors, they must ingest highly structured data from suppliers while ensuring their own sales systems can output compliant files.

This raises immediate operational questions for commercial and procurement directors. How do you handle a delivery dispute when the tax office bans unstructured PDFs? What happens to your cash flow if your ERP system fails to embed a split-payment code directly into the XML payload? And how do you prepare your trade desk for the hard expiration of transitional safety valves on December 31, 2026 [1], [4]?

The technical transition has been abrupt. The previous FA(2) logical structure was retired on January 31, 2026, making the rigid FA(3) schema the sole binding template for all structured invoices and corrective invoices issued from February 1, 2026 [2]. According to reports by the technology firm Comarch, this transition was accompanied by a complete system migration: the Ministry of Finance shut down the KSeF 1.0 production environment on January 26, 2026, initiating a scheduled technical maintenance blackout period until January 31, 2026, before launching the KSeF 2.0 environment on February 1, 2026 [7].

For merchants, this means legacy ERP systems that were patched to handle FA(2) are now obsolete. The FA(3) logical structure, available at the official URL https://crd.gov.pl/wzor/2025/06/25/13775/, requires deep data integration [2]. The main schema structure includes elements such as Naglowek, Podmiot1, Podmiot2, Podmiot3, PodmiotUpowazniony, Fa, Stopka, and Zalacznik [2].

The operational challenge lies within the Fa element. It contains specific sub-elements including FaWiersz (invoice line), Rozliczenie (settlement), Platnosc (payment), WarunkiTransakcji (transaction terms), Transport, and Zamowienie (order) [2]. This is no longer just an accounting task; it is a real-time mapping of logistics and commercial terms. If your warehouse management system does not automatically feed the Transport or Zamowienie data directly into the ERP’s XML generator, the invoice cannot be issued.

Furthermore, the tax implications are tightly coupled with this data. The advisory firm Kordecki & Partners notes that under KSeF, mandatory split payment (MPP) annotations can no longer be added manually to an invoice printout [5]. Instead, they must be embedded directly within the structured invoice data itself [5]. If a merchant sells heavy materials that fall under mandatory split-payment rules, the ERP must automatically identify the product category and hardcode the MPP flag into the XML payload before transmission.

Building materials merchants routinely handle complex logistics documents. A single delivery to a job site might require a delivery note, an acceptance protocol, a material specification, and a signed receipt from the contractor. Historically, these were scanned and attached to a digital invoice as a PDF.

Under KSeF, this workflow is blocked. The advisory firm Koda Advisory reports that while the FA(3) schema introduces an optional “Zalacznik” (Attachment) node to submit attachments directly within the e-invoice XML, the technical constraints are severe [6]. Koda Advisory notes that these attachments must be in a highly structured data format consisting strictly of blocks and tables with descriptions [6]. Unstructured documents—such as work schedules, cost estimates, acceptance protocols, or handwritten specifications of completed work—are strictly prohibited [6].

To use this technical node, merchants must submit a prior declaration of intent via the e-Tax Office [6]. Additionally, Comarch reports that Polish authorities established a new notification requirement on January 14, 2026, for taxpayers intending to utilize these technical attachment nodes within the FA(3) XML structure [7].

This creates a severe operational dilemma. If a contractor refuses to pay an invoice until they see the signed delivery note, but the merchant cannot attach that delivery note to the KSeF invoice, how does the merchant prove delivery? Merchants must now build parallel, secure digital portals to share unstructured logistics documents with their customers, completely separate from the tax-reporting stream, while ensuring the KSeF XML invoice references the correct transaction terms.

Currently, merchants are operating under a temporary safety valve. Until December 31, 2026, taxpayers obliged to issue structured invoices may continue to issue electronic or paper invoices using cash registers, and fiscal receipts with the buyer’s NIP (Tax ID) up to PLN 450 (or EUR 100) will still be recognized as simplified invoices [4].

Furthermore, the requirement to provide the KSeF invoice number during payments between active taxpayers is deferred until December 31, 2026 [1]. To ease the transition, the Ministry of Finance has confirmed that no penalties or sanctions will be imposed for errors committed while using the KSeF system during the 2026 transition year [3]. Additionally, businesses with monthly gross sales documented by invoices under PLN 10,000 are exempt from KSeF issuance until January 1, 2027 [3], [4].

However, this leniency is a double-edged sword. It allows merchants to delay necessary IT upgrades, but the cliff edge on January 1, 2027, is absolute. On that date:

Merchants who rely on the 2026 transition rules to avoid ERP integration are simply accumulating technical debt that will disrupt their cash flow when the penalties and payment-matching mandates take effect.

To protect margins and maintain supply chain continuity, procurement and commercial directors must take immediate action:

The operational burden of KSeF is undeniable. It requires significant investment in ERP upgrades, staff training, and data management. The risk of system downtime, blocked invoices, and administrative penalties is real for those who fail to adapt.

However, the transition also offers a major structural opportunity. By forcing the digitization of invoice lines (FaWiersz), payment terms (Platnosc), and order data (Zamowienie), KSeF provides merchants with highly structured, real-time commercial data [2]. Merchants who successfully integrate these fields can automate their three-way matching processes—aligning purchase orders, delivery notes, and supplier invoices instantly. This reduces administrative overhead, eliminates billing disputes with contractors, and accelerates cash conversion cycles. The merchants who master this data standard will secure a significant competitive advantage in the European supply chain.

[1] ksef.podatki.gov.pl — https://ksef.podatki.gov.pl/informacje-ogolne-ksef-20/podstawy-prawne-oraz-kluczowe-terminy/ [2] ksef.podatki.gov.pl — https://ksef.podatki.gov.pl/media/gtjhkeek/information-sheet-on-the-fa-3-logical-structure-04032026.pdf [3] ksef.podatki.gov.pl — https://ksef.podatki.gov.pl/wyjasnienia/drugi-etap-wdrozenia-krajowego-systemu-e-faktur/ [4] ksef.podatki.gov.pl — https://ksef.podatki.gov.pl/informacje-ogolne-ksef-20/zakres-obowiazkowego-ksef/ [5] kordeckipartners.com — https://kordeckipartners.com/en/insights/vat-split-payment-when-mandatory-for-poland-companies-4/ [6] koda-advisory.pl — https://koda-advisory.pl/blog/2025/04/29/attachments-in-ksef-an-useful-feature-but-not-for-everyone/ [7] comarch.com — https://www.comarch.com/trade-and-services/data-management/legal-regulation-changes/ksef-updates-in-poland-attachment-notifications-and-production-environment-shutdown/ [8] parp.gov.pl — https://www.parp.gov.pl/component/parpevents/event/3795