KSeF in Restaurants: How to Prepare Invoices, Receipts and Multiple Locations

In gastronomy, KSeF changes not only the invoice format, but the point where sales from cash registers, POS systems, catering, delivery platforms and multiple locations reach accounting. A restaurant must distinguish a receipt, a receipt with NIP, a business invoice, a consumer invoice and a structured XML FA(3) invoice.

The largest risk appears in B2B sales: a company lunch, an event, catering, an invoice after shift closing, a correction after the number of guests changes, or a purchase invoice from a supplier. Each case needs a clear process: who collects data, who issues the document, who checks status and who watches UPO.

A good restaurant procedure starts with a document map. The location serves the guest and collects buyer data, headquarters or accounting controls KSeF, and the system should help validate XML, fetch purchase invoices and catch errors before submission.

A restaurant does not work like a service office that calmly issues a few invoices per month. Sales happen quickly, often at the cash register, during table service or after an event. Receipts, card payments, phone orders, delivery platforms, advance payments, corrections and supplier invoices all join the same process.

KSeF requires invoices covered by the obligation to be structured invoices, meaning XML files compliant with FA(3), accepted by the system and marked with a KSeF number. This is different from a PDF sent by email or a printout from a sales application.

In gastronomy the issue is not just clicking submit. The issue is whether the cashier knows when to collect the NIP, whether the manager knows what to do with an event invoice, whether accounting sees supplier invoices in KSeF and whether someone checks which documents have UPO.

Imagine a restaurant with three locations in one city. Each location has its own POS and fiscal cash register, but accounting is central. In the morning a location receives meat, vegetables and drinks. At noon it serves a company lunch, in the afternoon it accepts a catering order, and in the evening it invoices a closed event.

Before KSeF, some documents could live in emails, binders and POS exports. After mandatory KSeF, it is not enough for the manager to have a PDF. For invoices covered by the obligation, the team must know whether the XML reached KSeF, whether it has a KSeF number and whether accounting sees the sales or purchase document.

The key operational change is simple: a location should not be an island. It can serve guests and collect data, but headquarters needs one view of invoices, statuses, UPO, corrections and supplier purchase documents.

At 12:30, the city-center location serves a company lunch. The customer asks for an invoice for a company and provides a NIP. The employee should have a simple procedure: collect data before closing the sale, mark the order as business-related and send the document into the invoicing process instead of reconstructing details from memory hours later.

At 14:00, the second location accepts an advance payment for catering. Accounting needs to know whether the advance should be documented by an invoice, how it will be linked to the final settlement and who will handle a possible correction after the number of guests changes.

At 16:00, headquarters sees an invoice from a meat supplier. This is a purchase invoice, so the restaurant should receive it in KSeF, assign it to the right cost location and verify whether it matches the order and delivery.

At 23:00, the manager closes the day. The cash register report is useful, but it is not enough to control the full invoice flow. Accounting should see documents issued, pending, rejected, accepted and confirmed with UPO.

The most common restaurant scenario is only simple at first glance: a customer pays for a meal and asks for an invoice for a company. For the service team it is one conversation at the register. For KSeF, the restaurant must decide whether the document will be a receipt, a receipt with NIP temporarily treated as a simplified invoice, a full B2B invoice, or an invoice created later by accounting.

Until the end of 2026, the Ministry of Finance indicates transitional rules for invoices issued using cash registers and fiscal receipts with the buyer's NIP treated as simplified invoices up to PLN 450 or EUR 100. This should not become an excuse for having no procedure. The restaurant should know what to do below and above the limit, and when buyer data must go into a full invoice.

In practice, introduce a simple service rule: the question about invoice and NIP comes before the bill is closed, not after the document is printed. This reduces corrections, nervous data retyping and incomplete information arriving in accounting days later.

B2B catering is one of the clearest examples of why gastronomy needs its own KSeF scenario. An order can include an advance payment, a changed number of participants, extra drinks, transport, waiter service and a post-event discount. This is not a single receipt for lunch.

If the restaurant issues an invoice to a company, a document covered by the obligation should be prepared as XML FA(3), submitted to KSeF and confirmed with a KSeF number and UPO. If the service value changes after the event, a correction process may be needed instead of manually changing an old PDF.

A good catering procedure should cover order acceptance, buyer data, advance payment rules, the person approving the final invoice, how changes are documented and how to check whether the correction is linked to the right original invoice.

A restaurant does not only issue invoices. It also receives purchase invoices from food, beverage, packaging, utilities, marketing, equipment leasing and delivery-platform suppliers. From 1 February 2026, receiving invoices in KSeF is mandatory for domestic buyers with a NIP, with exceptions described by the Ministry of Finance.

This means that a purchase invoice may be available in KSeF even if the supplier still sends a PDF visualization by email. If restaurant accounting works only from emails, it may miss documents, duplicates or corrections visible in the system.

In practice, build a rhythm: daily or every few days, import purchase invoices from KSeF, assign them to a location, check the supplier and quickly clarify invoices that the location manager does not recognize.

Not every gastronomy document needs the same procedure. Some sales remain consumer sales, some require a B2B invoice, and some are purchases on the restaurant side. The table below separates the cases that most often cause mistakes.

A receipt with NIP is one of the most sensitive topics for gastronomy because it touches work at the cash register. Until the end of 2026, the Ministry of Finance describes transitional rules for electronic or paper invoices issued using cash registers and fiscal receipts with the buyer's NIP treated as simplified invoices up to PLN 450 or EUR 100.

This does not mean the restaurant should leave the topic to chance. Staff must know when a receipt is enough, when to collect NIP, when the amount or transaction type requires a full invoice, and who owns the document after the shift closes.

The safest staff training should start not from legal theory, but from cash-register scenes: a private customer, a company customer with NIP, a company lunch for PLN 380, an event for several thousand PLN, and a request for an invoice the next day. Only then should these scenarios be connected to the KSeF procedure.

A restaurant chain needs simple roles. The location should know what data to collect and who receives the issue. Headquarters should see which invoices have been issued, which are pending, which have errors and which have UPO. Accounting should see both sales and purchase invoices.

In KSeF, the internal invoice number, KSeF number, session or package number and UPO all have different meanings. If every location keeps its own spreadsheets, chaos appears quickly. It is better to define one operational numbering logic, one way to mark a location and one place for status control.

Permissions should also be defined in advance. One person may accept order data, another may issue invoices, another may approve corrections and another may download and archive UPO. Without that split, the first errors will appear during a larger event or a correction after month end.

First, walk through a real working day in the restaurant and list documents that are created or received. Do not start with software selection. Start with who touches invoice data in the location and where that data goes next.

Then check the POS and cash register: whether they collect NIP before the bill is closed, export data needed for an invoice, separate locations, reconstruct an event order and offer a KSeF-ready process from the system provider.

Finally, write a short procedure for five situations: a company invoice at the register, an invoice after an event, an advance invoice for catering, a correction after an order change and a purchase invoice from a supplier. These are the cases that will return every week.

KSeFGPT does not replace procedures in the restaurant and is not a government service. It can, however, help organize the technical part of the process: XML validation, error control, invoice preview, handling many documents and work with incoming and outgoing invoices.

For a restaurant, the KSeF XML validator is especially useful when you want to check a file before submission or catch a data problem. With a larger document volume, invoice modules, statuses, UPO and working on many documents without manual retyping also matter.

If you run several locations, think of KSeFGPT as an organizing layer between operations and accounting. The location still has to collect correct data, but the system can help check the document, monitor status and find invoices that need action faster.

The first mistake is treating a PDF as a KSeF invoice. A PDF can be a visualization or supporting document, but a structured invoice in KSeF is XML compliant with FA(3). Read more in Can a PDF be sent to KSeF?.

The second mistake is failing to distinguish B2C and B2B sales. Consumer invoices are not covered by mandatory KSeF, but invoices for domestic buyers with NIP require a separate issuance and control process.

The third mistake is correcting an invoice without a correction procedure. If an invoice has been accepted by KSeF and has a KSeF number, it should not be overwritten or resent as the same document. In typical cases, a corrective invoice in KSeF is needed.

The fourth mistake is no UPO control. For restaurant accounting, what matters is not only that someone clicked submit, but whether KSeF accepted the document. See UPO in KSeF.

If you run a restaurant or handle accounting for several locations, do not start with a general KSeF training. Start with five real cases: a customer asks for an invoice at the register, a company orders catering, a supplier issues a purchase invoice, an event requires a correction, and headquarters closes the month and checks UPO.

Only then choose tools and integrations. A good gastronomy process should say who collects NIP, who issues the invoice, who controls the KSeF number, who downloads UPO and who handles corrections. Without this, even the best application becomes another place where documents can get stuck.

Further reading: XML and FA(3) format in KSeF, Can a PDF be sent to KSeF?, Corrective invoice in KSeF and UPO in KSeF.

KSeF rules and legal provisions, Ministry of Finance - mandatory KSeF dates, PLN 200 million threshold, PLN 10,000 limit, invoice receipt and sanctions from 2027.

KSeF 2.0 implementation stages, Ministry of Finance - KSeF 2.0 roadmap.

Issuing and receiving invoices, Ministry of Finance - invoice receipt rules, visualizations, QR codes and invoices for buyers with NIP.

Structured invoice and FA logical structure, Ministry of Finance - definition of a structured invoice and XML format.

Scope of mandatory KSeF, Ministry of Finance - exclusions and transitional rules for cash-register invoices and receipts with NIP.

FA(3) logical structure, Ministry of Finance - FA(3) structure applicable from 1 February 2026.