Automatic Order Invoicing to KSeF: A Guide

KSeF becomes mandatory in stages in 2026, and with several hundred orders a month, issuing invoices by hand stops being realistic. We show how to build an order→invoice→KSeF pipeline that works without retyping data.

Automatic order invoicing to KSeF — what it means and when it becomes mandatory

Automatic order invoicing to KSeF is a process in which order data (the buyer, line items, prices, VAT rates) flows into the invoice and into the National e-Invoicing System without manual re-keying — and the system assigns the invoice a KSeF number, which serves as its official confirmation. In practice it comes down to a single chain of events: a customer places an order on Allegro, Amazon, or your own WooCommerce or Shopify store, and the software creates an invoice in the FA(3) structure on its own, sends it to KSeF, and retrieves the confirming number.

Why has this suddenly become such a pressing topic? Because as of February 1, 2026, the KSeF e-invoicing obligation covers the largest taxpayers (turnover above PLN 200 million for 2024), and as of April 1, 2026 — all other businesses. This means that if you sell to companies on invoice, your B2B invoices must already pass through KSeF. With dozens or hundreds of orders a day, hand-keying invoices in the government panel is a road to nowhere — which is why an automated pipeline has stopped being a convenience and become a prerequisite for running sales smoothly.

Below we break this process down into its component parts: exactly what the deadlines say, what the data flow looks like step by step, when KSeF is mandatory and when it isn’t (B2B versus consumer sales), and what to do when the system doesn’t respond. At the end you’ll find a rollout checklist and a frequently asked questions section.

The KSeF 2026 timeline: who, what and from when

The most important distinction: the obligation to receive invoices in KSeF is one thing, and the obligation to issue them is another. Receiving became universal earlier than issuing did for smaller firms, so even a micro-business had to be ready to accept e-invoices from suppliers from the start of February 2026.

Two numbers are worth remembering: PLN 200 million in annual turnover as the entry threshold in the first wave, and PLN 10,000 as the monthly limit on invoices issued outside KSeF during the transition period for the smallest firms. The deadlines come from the act, but the technical details (API documentation, certificates) were published in stages by the Ministry of Finance — if you’re building the process yourself, always verify the current state on the official KSeF website. We cover the obligations themselves in more depth in KSeF 2026 for e-commerce sellers.

Why manually re-keying invoices is a dead end

Picture a typical day for a multichannel seller: 40 orders from Allegro, 15 from your own store, a few from Empik and Amazon. Some of the customers are companies that ask for an invoice with a NIP. Not long ago it looked like this: export from the marketplace panel, manually paste the data into the invoicing software, check the VAT rate, email the PDF. Now there’s another step — the same invoice has to reach KSeF in a structured format and come back with a number.

Doing this by hand at higher volume creates three costly problems:

• Data errors. A typo in the NIP, the wrong VAT rate, transposed groszy — with manual re-keying it’s a matter of when, not “if.” An invoice rejected by KSeF validation does not exist in the legal sense until you correct it and resend it.
• Time and cost. Even 3–4 minutes per invoice across 60 orders a day is 3 hours of human work — every day. That’s a full-time job whose only task is moving the same data between windows.
• Risk of delays. A B2B invoice has to be in KSeF — if it sits in the “I’ll do it tonight” queue, the risk grows that something slips through and a deadline is missed.

Automation solves this at the source: data entered once by the customer on the marketplace passes through the entire process without being retyped. It’s the same philosophy we describe in e-commerce order automation — the fewer human hands that touch the data, the fewer errors and the faster the handling.

The order → invoice → KSeF pipeline step by step

A well-designed flow has several distinct stages. Below we describe them in the order they actually happen, along with where things most often break.

1. Fetching the order. The integration with the marketplace or store pulls in the new order along with buyer data (individual or company, NIP, address) and the line items, prices, and VAT rates.
2. Identifying the buyer type. The system checks whether the customer provided a NIP and whether they requested an invoice. This determines whether the document has to go to KSeF at all (B2B) or is optional (consumer).
3. Mapping the data to the FA(3) structure. The order’s line items, rates, and amounts are translated into the structured format required by KSeF. Correct VAT rates and units of measure are crucial here.
4. Validation and submission to KSeF. The invoice is signed/authenticated and sent via the API. The system checks it for conformance with the schema.
5. Assigning the KSeF number. After successful validation, the invoice receives a KSeF number — official confirmation that the document exists in the system.
6. Delivering the invoice to the buyer. Companies will receive the invoice directly in KSeF. A retail customer can be sent a PDF visualization with a QR code leading to the document.
7. Recording and accounting. The invoice with its KSeF number returns to your system and goes into the records. Invoices issued in KSeF do not require separate JPK_FA reporting.

B2B and B2C invoices on marketplaces — when KSeF is mandatory

This question keeps the largest group of sellers up at night, because on Allegro or Amazon you have both companies and consumers in a single stream of orders. The rule, however, is fairly clear.

Three practical takeaways for a marketplace seller:

• The marketplace is only a channel, not the issuer. You issue invoices for your sales under your own NIP, and you are responsible for getting them into KSeF. The platform will not send your sales invoices to the system for you — built-in marketplace modules usually generate only a PDF. A separate matter is the invoices the platform itself issues to you for its commissions — those reach you via KSeF like any purchase invoice.
• A consumer doesn’t disappear from your VAT obligations. A B2C invoice doesn’t have to go to KSeF, but you still have to record it correctly in your ledger and JPK_VAT. If you issue an invoice against an earlier receipt, that has its own recording rules.
• Not every “business” customer wants a B2B invoice. It’s worth asking unambiguously during checkout whether the customer is buying for a business — because that determines the document’s path.

You’ll find more on how to handle invoices in practice on Poland’s largest marketplace in KSeF and selling on Allegro — how to issue invoices.

What if KSeF doesn’t respond? The offline24 mode in online sales

Sales can’t grind to a halt when the Ministry’s system or your own tool has a temporary outage. That’s why emergency modes were provided, the most important of which for e-commerce is offline24.

In short: in offline24 mode you can issue an invoice outside the system and send it to KSeF by the end of the next business day at the latest. An invoice made available to the buyer before it’s sent to KSeF is marked with two QR codes — one giving access to the document in KSeF (the “OFFLINE” marking) and the other confirming the issuer’s identity (the “CERTYFIKAT” marking). Generating the latter requires an invoice issuer’s certificate; certificate applications could be submitted from November 2025, and they work in production from February 1, 2026.

The offline24 mode is a lifeline, not the default way of working. The document still has to reach KSeF within the set time — which is why an automated pipeline should queue invoices and retry submission once the system responds again.

From an online seller’s point of view, the most important thing is for the invoicing tool to handle the queue and retries on its own. Manually keeping track of which invoices “went through” and which didn’t is simply unrealistic across hundreds of documents.

How to prepare your store for automatic invoicing — a checklist

Before you turn on automation in production, go through this set of points. Skipping any of them usually ends in a series of rejected invoices at the worst possible moment.

• Clean up your product data. Every product should have an unambiguously assigned VAT rate and unit of measure. A rate dictionary is the foundation — the wrong rate is the most common cause of corrections.
• Enforce correct buyer data. In the cart and on the marketplace, ensure NIP validation and a complete address for business orders.
• Separate the B2B and B2C paths. Establish a clear rule: when a document goes to KSeF and when a consumer invoice is enough.
• Obtain a certificate and authentication. Make sure you have configured KSeF access (token/certificate) for your NIP and, if applicable, for your accounting office.
• Test on the test environment. Before you go live in production, run a dozen or so representative orders (various rates, foreign sales, a correction) through the KSeF test environment.
• Plan for handling rejections. Every invoice rejected by validation must go into a queue with an alert, not vanish in the background.
• Set a process for outages. Who uses offline24 mode and how, and where invoices awaiting resubmission go.
• Agree on the process with accounting. Determine who downloads invoices from KSeF, and what reconciliation and archiving look like.

That same discipline — clean data at the source and clear rules — pays off not only with invoices but across your entire order handling. If you’re only just setting up your multichannel sales processes, it’s worth starting with the article on order automation and treating invoicing as another stage of the same chain.

The most common mistakes when automating invoices to KSeF

From conversations with sellers and from what you can see in industry discussions, a few recurring pitfalls emerge:

• Treating the marketplace as the invoice issuer. The platform won’t take the obligation off your shoulders — your sales mean your NIP and your responsibility for KSeF.
• No handling of rejections. An invoice that failed validation doesn’t exist. Without an alert and a retry queue, it’s easy to forget about it.
• Neglected VAT rates. A single product with a default, wrong rate can generate dozens of corrections.
• Skipping the test environment. A first launch straight into production, at peak sales, is asking for trouble.
• Relying on a single mode in case of an outage. Without a planned offline24 and a retry queue, a system outage blocks document issuance.

In practice, most of these mistakes come down to one thing: the lack of a single, coherent flow from order to invoice. When data travels manually between several tools, every handoff is a chance for a mistake.

Automatic invoicing as part of a bigger puzzle

Invoicing to KSeF doesn’t live in a vacuum. It’s the last link in a chain that begins with stock synchronization and order handling and ends with the courier label and settlement. The better these elements play together — one set of order data serving the warehouse, shipping, and the invoice — the less manual work and the fewer places where something goes out of sync.

This is exactly the direction modern multichannel sales panels are heading, including Nimo, built with the Polish market in mind, where KSeF integration is meant to be a natural extension of order handling rather than a separate, manual chore. Regardless of which tool you use, though, the principle stays the same: data entered once, at the order stage, should make its way all the way to an invoice with a KSeF number on its own.

Frequently asked questions

Does every invoice from a store have to go to KSeF?

Not every one. The obligation applies to B2B invoices — issued to companies, sole proprietorships, and institutions. Invoices for consumers (individuals not running a business) can be issued in KSeF voluntarily. Always remember, however, to record the sale correctly in your VAT ledger, regardless of whether the document goes to KSeF.

Will Allegro or Amazon issue invoices in KSeF for me?

Not for your sales. The marketplace is a sales channel — you issue invoices for the goods you sell under your own NIP, and you are responsible for getting them into KSeF. Platforms’ built-in modules usually generate a PDF visualization rather than a structured e-invoice. Separately, the platform may issue you invoices for its commissions, and those reach you via KSeF as purchase documents.

What happens when an invoice is rejected by KSeF?

An invoice rejected by validation does not obtain a KSeF number and, in the legal sense, was never issued. You have to correct the error (e.g., the NIP or VAT rate) and resend it. That’s why an automated process should have a retry queue and an alert for staff, so that no invoice gets stuck unnoticed.

What should you do when KSeF is unavailable during sales?

Use offline24 mode: you issue the invoice outside the system and send it to KSeF by the end of the next business day at the latest. The document made available to the buyer is marked with QR codes (OFFLINE and CERTYFIKAT), and the latter requires an issuer’s certificate. A good tool queues such invoices on its own and retries submission once the system responds again.

From when do penalties apply for issuing invoices outside KSeF?

According to announcements, administrative penalties are set to take effect on January 1, 2027, after the transition period ends. The amounts cited (roughly up to 100% of the VAT amount or a portion of the invoice’s gross value) should be treated as figures to verify against current regulations — before making a decision, check the legal state of play at the source or with your accountant.