Blog

KSeF 2026 for Transport: What Freight Forwarders Must Prepare

KSeF 2026 for transport and freight forwarding is not "yet another accounting system to roll out someday". It is a legal obligation: once it takes effect, all B2B invoices must be issued through KSeF (the Polish National e-Invoice System). For freight forwarding companies this means concrete changes in document flow, TMS integration with KSeF and the way transport jobs are booked into accounting.

If you run a transport or freight forwarding company and have not managed to roll out KSeF yet, this guide shows what you need to do, what the realistic deadlines are, how long deployment takes and the most common mistakes made by dispatchers who waited until the last minute.

What is KSeF and why does it concern freight forwarding?

KSeF is the Polish National e-Invoice System, a central platform run by the Ministry of Finance for issuing, receiving and archiving structured invoices in XML format. Every B2B invoice gets a KSeF number and is available in one place for both seller and buyer. For the freight industry three aspects matter most: faster counterparty verification, shorter payment terms and a full audit trail for every transport.

KSeF timeline for transport companies

  • Stage 1. Large companies (sales above PLN 200 million per year): obligation from Q1 2026
  • Stage 2. Other active VAT payers: obligation from April 2026
  • Stage 3. VAT-exempt companies: obligation from January 2027
  • Consumer B2C invoices: still optional, outside KSeF
The dates given reflect the current legal status. The Ministry of Finance may introduce changes. Always check the current effective date in official communications before deployment.

What a freight forwarding company must do: checklist

  1. 1Create an account on the KSeF portal and generate an authentication certificate (token).
  2. 2Check whether your TMS or accounting system supports invoice submission in the FA(2) format.
  3. 3Set document numbering compliant with the KSeF schema (number + sequence).
  4. 4Map VAT, tax, issue date, sale date and invoice line items to the XML structure.
  5. 5Configure automatic data validation before submission (empty VAT numbers are the most common error).
  6. 6Train the dispatcher and accountant on the new flow (who approves, who sends).
  7. 7Launch real-time status monitoring (UPO confirmations, rejection errors).
  8. 8Configure e-invoice archiving in line with the 10-year retention requirement.

TMS and KSeF integration: how to make it painless

Freight forwarding is specific: the transport invoice is generated based on an order in the TMS, with a defined route, driver, loading and unloading dates and attached CMR documents. A good TMS should generate the e-invoice directly from the order, without re-entering data into a separate accounting program. This reduces errors and speeds up the flow.

Sokar Logistics has native KSeF integration from day one: order in TMS = automatic VAT and data validation, generation of FA(2)-compliant XML, submission to KSeF, UPO monitoring, 10-year archiving. The dispatcher does not need to know XML structures: the system does it for them.

If your current TMS does not natively support KSeF, you have two options: (1) integration via API with a middleware service (e.g. Comarch), (2) migration to a TMS with native support (e.g. Sokar). The first option is cheaper, the second faster and less error-prone.

Most common mistakes when rolling out KSeF in freight forwarding

  • No VAT validation before submission: invoices get rejected, the customer waits longer for payment
  • Incorrect numbering (gaps, duplicates): rejection by the KSeF gateway
  • Missing the "Sale date" field: in transport this is usually the unloading date, not the issue date
  • Wrong mapping of the transport service to PKWiU/CN codes
  • No UPO monitoring: the dispatcher assumes "submitted = delivered"
  • Numbering not synchronised between the accounting system and the TMS

How long does KSeF deployment take in a freight forwarding company?

Small company (1 to 5 dispatchers)
With a native TMS: 3 to 7 days. With an integrator: 2 to 3 weeks.
Medium company (5 to 20 dispatchers)
Typically 2 to 4 weeks including team training.
Large company (over 20 dispatchers)
4 to 8 weeks including migration of historical documents and ERP integration.
First month after go-live
On average 5% of invoices need correction (typos, wrong VAT), then it stabilises.

KSeF and CMR documents and transport orders

KSeF covers invoices: it does not replace the CMR, the consignment note or the transport order. These documents stay in circulation as attachments or links in the TMS. Good TMS systems store the CMR (scan or e-CMR) and the linked order alongside the issued e-invoice, the whole package as a single transport record ready for audit.

Is your TMS ready for KSeF? Find out within 24 hours: we will help you map your current document flow and identify gaps before the mandatory deadline.

Check your KSeF readiness