Most invoicing demos stop exactly where the hard part starts — at a clean form and a button labelled "Issue". Whether the document actually exists in the eyes of the Polish tax administration (accepted by the gateway, assigned a KSeF number, confirmed by a UPO) never makes it into the video.
So I recorded the whole path in one take, with a timer running in the corner: sign-up, company data from the business register, KSeF connection, counterparty, line item, issue, send, number, UPO. Seven minutes and change.
This matters on a deadline. KSeF (Poland's national e-invoicing system) has been mandatory for most VAT taxpayers since 1 April 2026, and the grace period ends on 31 December 2026 — per the Ministry of Finance, no penalties are imposed for KSeF failures between 1 February and 31 December 2026, while the penalty provisions (Article 106ni of the Polish VAT Act) take effect on 1 January 2027. If your Polish entity is still issuing PDFs, you have a few weeks of free rehearsal left.
Below: timecodes, the transcript, and an honest list of what the recording leaves out.
What the recording actually shows
One take, one company, one invoice. The timer was never paused.
Timecode Step What happens 0:00 Sign-up Email, password, confirmation. No card. 0:35 Company by tax ID I type the NIP; name, address, legal form and VAT status come from the Polish business register (GUS) 1:20 KSeF connection Pick the environment (test/production), authenticate, grant the permission 3:05 Counterparty NIP again; VAT standing checked against the official taxpayer list 3:50 Invoice line Service description, net amount, 23% VAT, GTU marker 4:40 Issue Number from the numbering template, XSD validation against the FA(3) schema 5:25 Send to KSeF Session opens, document submitted, status processing 6:10 KSeF number A 35-character identifier comes back — the invoice is now issued 6:40 UPO Official receipt confirmation downloaded as a file 7:05 Visualisation PDF with a verification code, emailed to the client
The proportions are the point. Writing the invoice itself — counterparty, line, amount — takes under two minutes. Everything before it is one-time setup you never repeat.
Recording conditions — what is not in the video
It was recorded on the KSeF test environment (api-test.ksef.mf.gov.pl), with a company created for the demo. Three things follow from that, and they should be said plainly:
Granting permissions is not always instant. If nobody at your company holds KSeF permissions yet, the first grant goes through a ZAW-FA notification filed with the tax office — a separate, administrative path. The demo company already had permissions; otherwise the timer would read in days, not minutes.
Invoices with attachments need separate consent from the tax administration; in production the answer can take up to three business days. The invoice in the video has no attachment.
The test gateway can be faster than production. In production, the wait between submission and the KSeF number can run tens of seconds longer, especially around the 25th of the month.
So seven minutes is time spent in the software, not time spent with the tax office. If your entity has nobody authorised in KSeF yet, start with ZAW-FA; the rest genuinely takes what the timer shows.
Transcript (abridged, with timecodes)
0:00 — "We start from an empty inbox. The account is created on an address the system has never seen, so there's no question of anything being prepared in advance."
0:35 — "I don't type the company name or address. I type the tax ID. The data comes from the GUS register. VAT status is checked separately against the taxpayer list. If something doesn't match reality, the register is out of date — not the form."
1:20 — "Now the one step that deserves attention: connecting KSeF. I choose the environment — test here. In production this is effectively irreversible, in the sense that anything you send there is a legally binding invoice. I authenticate the company, and from this moment Biurko acts as an authorised entity: it sends and receives documents on the company's behalf, strictly within the permission granted."
3:05 — "Counterparty: tax ID again, register again. Next to it you can see today's VAT standing from the official list. That isn't decoration — with an invoice issued outside KSeF, the buyer would be the one carrying the verification burden."
3:50 — "One line: development services, PLN 4,200 net, 23% VAT, GTU_12. The GTU marker is suggested, but the call belongs to the taxpayer — the software doesn't know your classification better than you do."
4:40 — "Issue. The document gets its number from the numbering template and is validated against the FA(3) schema. If the XML fails, you find out here, not from the gateway."
5:25 — "Send. A session opens, the document goes to KSeF, status processing. This is the only moment you wait."
6:10 — "There's the number:
6343060594-20260917-0A1B2C3D4E5F-7C
Thirty-five characters: seller's tax ID, date, document identifier, checksum. The invoice is issued as of this moment — not as of the moment I clicked Issue."
6:40 — "UPO. I download the file and keep it with the company's documents. It's proof of submission, and you cannot reconstruct it from a PDF."
7:05 — "Finally the visualisation — a PDF with a verification code — emailed to the client. The PDF is not the invoice. It's a picture of an invoice that lives in KSeF."
Three places where this breaks
1. Missing KSeF permissions. The most common cause of "the integration doesn't work". No software can grant itself access; the taxpayer does that on their own side, and where no primary permission exists, the path starts with ZAW-FA.
2. Schema rejection. An invoice that is correct to a human can be invalid against FA(3): a missing node, an unsupported combination of rate and exemption basis, a foreign counterparty without the right identifier. That is why validating before sending is worth the extra second — a gateway error code tells you less than a message next to the field.
3. Treating the PDF as the invoice. Once your entity is covered by the obligation, an emailed PDF is a visualisation, not an invoice. And from 1 January 2027 the KSeF number has to appear in the payment reference for transfers between active VAT taxpayers — which is hard to do if the number was never obtained.
Checklist: reproduce this on your own tax ID
Check whether anyone at your Polish entity holds KSeF permissions. If not, file ZAW-FA before configuring anything.
Start on the test environment. Issue three documents: a standard invoice, a correction, and an advance invoice.
Confirm you receive both the KSeF number and the UPO — and that you can still find them two weeks later.
Review the numbering template for January; numbering continuity is your obligation, not the software's.
Switch to production and issue one real invoice before the grace period ends, not in January.
Decide what happens during a gateway outage (offline24 mode) and rehearse it once, calmly.
Summary
Seven minutes isn't a marketing promise; it measures one thing — how long it takes to get from nothing to a document that has a KSeF number and a UPO. Everything else (corrections, advances, purchase-invoice import, VAT registers) starts after that point, and nothing starts before it.
To walk the same path on your own tax ID: create an account at biurko.io — 14 days free, with the KSeF test environment available from minute one. The recording and the full transcript are below the article.
3. FAQ
How long does the first KSeF invoice really take? Around seven minutes of work in the software, five of which are one-time setup of the company and the KSeF connection. Subsequent invoices take well under a minute. Administrative time — obtaining permissions via ZAW-FA — is separate and measured in days.
What is a KSeF number and where does it come from? A 35-character identifier assigned by the system once a document is accepted; it contains the seller's tax ID, the date, and a checksum. You never assign it yourself — it comes back from the gateway after submission, and from 1 January 2027 it also belongs in payment references between active VAT taxpayers.
Do I need the UPO if I already have the KSeF number? Yes. The number identifies the invoice; the UPO certifies that it was submitted and when. They are two different pieces of evidence, and keeping both is sensible even though KSeF stores the original.
Can a foreign parent company test KSeF safely? Yes. The Ministry of Finance's test environment is separate from production and documents issued there carry no tax consequences. On top of that, the transitional period without administrative penalties runs to 31 December 2026.
Is emailing a PDF enough for the client? It doesn't replace the invoice. Once the obligation applies, the legal document is the structured invoice inside KSeF; the PDF is a visualisation you send for the recipient's convenience, not instead of the e-invoice.