AURA

Invoices for private customers and KSeF: when it is voluntary and what about receipts with a NIP

B2C invoices in KSeF are voluntary, and a receipt with a buyer's NIP up to 450 zł counts as a simplified invoice through 2026. We show how to set one clear rule instead of guessing at every till.

Published
12 min read2319 words

AURA — a virtual business manager. Management on facts, not impressions. Who we are

Key takeaways

  • Issuing B2C invoices for consumers in KSeF is voluntary both before and after 1 February 2026.
  • An invoice for an already-issued receipt to a private person can also be issued in KSeF voluntarily, but it isn't mandatory.
  • Through the end of 2026, a receipt with the buyer's NIP up to 450 zł (or 100 euro) counts as a simplified invoice with no obligation to submit it to KSeF.
  • A KSeF invoice for a consumer with no account in the system reaches them in a way agreed with the seller, not automatically.
  • A private customer's data on an invoice should be limited to what's necessary — the GDPR data minimisation principle.

A few words that show up in this text

Explained in plain language — you do not need to know the trade to read on.

KSeF
Polish national e-invoicing system.
CRM
One place holding clients and enquiries: who asked, about what, and what happened next.

A customer at the till asks for an invoice made out to herself, not a company. The receptionist doesn't know whether that invoice has to go through KSeF, whether the old way still works — or whether the receipt already printed even counts.

This page shows what the KSeF portal actually says in this situation: when a consumer invoice in KSeF is voluntary, what happens with a receipt carrying a buyer's NIP up to 450 zł, and how to set this up once in the business so nobody has to guess at every transaction.

a small shop counter with a dark payment terminal with a green light, a cup of coffee and a wrapped pastry beside it, warm light
Most transactions at a service point are private customers — the invoice question comes up rarely, but you need a ready answer

The situation: a private customer asks for an invoice and you don't know which path applies

In a small service business — a salon, a clinic, a workshop — customers typically pay as private individuals and leave with a receipt. Every so often someone asks for an invoice made out to themselves, and less often a company with a NIP wants an invoice for its own books. Three situations call for three different answers, and mixing them up is the most common source of mistakes at the till.

Who is payingWhat documentWhat about KSeF
Private person, no NIPReceipt, invoice for the receipt on requestVoluntary
Private person, gives a NIP up to 450 złReceipt with a NIP as a simplified invoiceNot required through 2026
Company/sole trader with a NIP on the invoiceB2B invoiceMandatory from the statutory deadline

This page covers the first two rows — private customers and receipts with a NIP. B2B invoices have their own statutory deadlines and aren't the topic here.

When it's still worth issuing the invoice in KSeF

The KSeF portal directly answers whether consumer (B2C) invoices have to be issued in the system: "Both before 1 February 2026 and after that date, issuing B2C invoices (for private individuals — consumers) in KSeF is voluntary" (KSeF portal, Consumers and private individuals). In other words, there's no obligation approaching here the way there is for B2B deadlines — it's a choice the business makes once and sticks with.

An invoice for a receipt already given to a private customer

A separate question: what if the customer already got a receipt and then asks for an invoice for it? The KSeF portal answers exactly this case: "Issuing invoices in KSeF for consumers is not mandatory. However, if the taxpayer wishes to, they can issue such an invoice in KSeF, including an invoice for a receipt" (KSeF portal, KSeF 2.0 questions and answers). Issuing it in KSeF is therefore the business's option, not a condition for the document to be valid — an invoice for a receipt can just as well be issued outside the system.

The choice isn't a matter of regulations but of how the work is organised: one path for all invoices (everything through KSeF) is simpler for your accountant to check than two parallel ones — B2B through KSeF, B2C outside it. It's worth agreeing this with your accountant once, before the first customer request comes in. The receipt itself, and what has to add up at closing time, is covered separately: The Fiscal Till and the Daily Close in Poland — the till rules are the same regardless of industry.

A receipt with a NIP up to 450 zł as a simplified invoice

A separate situation: the customer gives their NIP at the till before the amount is even stated. The KSeF portal describes what happens then: through the end of 2026, it's possible to "issue invoices using cash registers, and fiscal receipts with the buyer's NIP are treated as simplified invoices (up to 450 zł or 100 euro)" (KSeF portal, Scope of mandatory KSeF). Such a receipt doesn't have to go into KSeF — it counts as a simplified invoice on its own, as long as the amount stays within the limit.

A simple script for reception or the till: if the customer gives a NIP before paying and the amount doesn't exceed 450 zł, the receipt with the NIP is enough — nothing extra needs to be issued. If the amount is higher or the customer wants a separate invoice, go back to the choice from the previous section. What happens to this limit after 2026 isn't specified by the portal today — there's no point guessing at a date that hasn't been announced yet.

How a private customer receives an invoice issued in KSeF

If a business does decide to issue consumer invoices in KSeF, a practical question comes up: a consumer usually doesn't have an account in the system and won't find the document the way a company with a NIP would. The KSeF portal confirms that in this case the seller "will deliver it to the buyer in a way agreed with them" (KSeF portal, KSeF 2.0 questions and answers) — meaning the delivery method has to be worked out separately; it doesn't follow automatically from issuing the document in the system.

This is a good moment to ask your accountant which delivery method — email attachment, printout, a link — fits your specific business. The portal doesn't dictate one path, so the decision stays with the business anyway.

a hand passing a canvas shopping bag across a bakery counter, close-up on hands and bag, soft morning light
A customer usually takes their purchase and leaves without asking about an invoice — the question only comes up sometimes

A private customer's data on the invoice: only what's needed

Along with the invoice question comes the temptation to record more of the customer's data "just in case" — a full address, a personal ID number, a phone number. A GDPR guide from Poland's data protection authority (UODO) cites Article 5 of the GDPR: personal data must be "adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed" (UODO, GDPR guide — data minimisation principle). For a private customer's invoice, the data required on the sales document is enough — nothing more.

What's not worth collecting "just in case"

A personal ID number, a full home address, or a customer's private phone number usually aren't needed to issue an invoice or a receipt — and every extra field is data you then have to protect and explain if it's lost. The rule is simple: if a field isn't required on the document or for contact about the order, there's no reason to collect it.

Splitting this without mistakes: one flow instead of guessing

Instead of deciding at every transaction from scratch, it's easier to set up one flow and stick to it: payment → the question "is an invoice needed?" → is there a NIP or not → choice of document → handover to the customer → a note in the customer's record.

Each step has a clear answer from the sections above, so nobody has to memorise the exceptions.

The most common mistakes at this boundary

In practice, three mistakes keep recurring: issuing an invoice to a company instead of a private person (or the other way around), a request for an invoice a week after the receipt, when the transaction details have to be reconstructed from memory, and two documents for one payment — for example an invoice for a receipt that was forgotten about, so a second one gets issued. None of these mistakes come from the regulations — all of them can be caught with a weekly comparison of the number of receipts, invoices, and payments.

a stack of gold coins beside a brass cash box on a dark wooden counter, crisp white light
Four hours a month of manual invoice handling isn't a big number — until someone actually counts it

How many hours a month this costs: an example on assumed numbers

12%
This is an example on assumed numbers — plug in your own data to see the real scale: with 500 payments a month, of which 12% of customers ask for an invoice, that's 60 invoices a month.

If issuing one invoice by hand (the conversation, entering the data, sending it) takes 4 minutes, then 60 invoices × 4 minutes = 240 minutes, or 4 hours a month of manual handling alone — without counting time spent correcting the mistakes from the previous section.

The calculation, step by step

This is still the same example on assumed numbers, just broken down step by step. Step one: number of invoices = monthly payments × share asking for an invoice = 500 × 0.12 = 60. Step two: total time in minutes = number of invoices × time per invoice = 60 × 4 = 240. Step three: time in hours = minutes ÷ 60 = 240 ÷ 60 = 4. Four hours a month isn't a figure from the regulations, just an order of magnitude to compare against your own numbers.

Do it yourself: a checklist for reception or the till

  1. Agree one rule with your accountant: all invoices through KSeF, or only B2B — and write that rule down somewhere visible to staff.
  2. Prepare one question sentence about the invoice, asked at every payment, instead of waiting for the customer to bring it up first.
  3. Note where in the till system or CRM the customer's NIP gets entered if they give it before paying.
  4. Agree with your accountant on the form in which a KSeF invoice reaches a private customer who has no account there.
  5. Once a week, compare the number of receipts, invoices, and payments — this catches the mistakes from the previous section before they grow into a problem.
  6. Check what data about private customers is actually reaching the system, and remove fields that aren't needed for the document or for contact.

This checklist is one of four thresholds worth starting from when tidying up processes in a small business — we cover the rest here: Where to start automation in a small business: four thresholds instead of general analysis.

What it looks like when a system keeps track of this

Instead of relying on the memory of whoever is at the till, the invoice question and the document choice can be built into the customer-handling process itself, so the data lands in one place instead of a separate sticky note.

Finance shows revenue, costs and margin as they happen instead of in a spreadsheet closed once a month. CRM and automations keeps customer data in one place, so an invoice request can be noted on the customer's card instead of being searched for in an inbox. Integrations connect the till to the accounting system so receipt data doesn't have to be retyped into an invoice by hand. Where invoice requests arrive by email or through a form, Request automation routes them straight to the right person instead of a shared inbox. Dashboards show the monthly count of consumer invoices issued next to the number of receipts — exactly the figure we counted by hand in the example above.

A related question — what an invoicing automation system even needs to handle with respect to KSeF — is covered separately: Invoicing Automation and KSeF: What Your System Must Be Able to Do. We apply the data minimisation principle from this page more broadly here too: Automation and GDPR: where your customer data physically ends up. The decision about which path to use for invoicing private customers is always made by the business together with its accountant — the system's job is just to make sure a rule, once set, doesn't slip at the next transaction.

Frequently asked questions

Does an invoice for a private customer have to go through KSeF?

No. Both before 1 February 2026 and after that date, issuing B2C invoices — for private individuals, i.e. consumers — in KSeF is voluntary. A business can do it if it wants to, but doesn't have to.

What about an invoice for a receipt already issued to a private person?

The KSeF portal explicitly allows this document: issuing invoices for receipts to consumers in KSeF isn't mandatory, but the taxpayer can do it if they want to — including an invoice for a receipt.

Does a receipt with the customer's NIP need to be reported to KSeF separately?

Not through the end of 2026. Fiscal receipts with the buyer's NIP up to 450 zł (or 100 euro) count as simplified invoices and can be issued through cash registers without an obligation to submit them to KSeF.

How does a private customer with no KSeF account receive their invoice?

The seller delivers such an invoice to the buyer in a way agreed with them — the portal doesn't dictate a single form, so it's worth settling this in advance with your accountant instead of improvising at the first request.

What customer data is it allowed to record when issuing an invoice?

Only what's adequate, relevant, and limited to what's necessary to issue the document — the GDPR data minimisation principle. Data like a personal ID number or a full address usually isn't needed for that.

What will change with NIP receipts after 2026?

The KSeF portal doesn't specify this today. It's not worth assuming a specific date or rule until one is officially announced — until then, the limit and rules described above apply.

Who writes this

See your business as a system.

Aura is a virtual business manager: management on facts, not impressions. For a company that wants a system running its processes instead of the owner’s memory.

The website, CRM, admin panel and automations are modules of the same system. We are not a website agency.

Look at my business

You will land on the home page. Give a company name — Aura looks at it in public data and shows what a client sees before calling you. No promises of a result.

See what we do

Related services

Read next Scroll for more

Let us look at your numbers

Tell us how enquiries are handled today — how many there are, who picks them up, where they get lost. Aura walks the process with you and shows what can be taken off a person, and what is better left alone.

Talk to Aura

The home page with Aura opens. Give a company name — she looks at it in public data and shows what a client sees. No promises of a result.

Prefer to write? marketing@auraglobal-merchants.com

Next step

Let us check whether Aura fits your place

We do not take everyone: first we look at your processes, sales and current systems and tell you honestly whether it makes sense for us to come in. A few questions, about five minutes.

Take the assessment →