Invoicing in Poland, KSeF and the UPO, the ryczałt and the JPK files — written out step by step.
Invoicing in a foreign language is completely legal for B2B transactions in Poland, provided the VAT amount is shown in PLN. From 1 April 2026 most sole proprietorships must issue structured invoices via KSeF using the FA(3) schema.
A B2B developer in Poland must manage KSeF invoicing, ZUS and ryczałt tax by the 20th, and JPK_V7M by the 25th of each month. For monthly invoices exceeding PLN 10,000 gross, KSeF has been mandatory since 1 April 2026. Learn how to calculate your 12% flat-rate tax and health contributions.
Sending an invoice to KSeF is only the first step of your monthly routine. The invoice must be correctly recorded in your VAT registers with its KSeF number, and then reported in JPK_V7M, ryczałt tax and ZUS. Follow this practical guide for a sole trader to see how the systems interact.
Choosing the right tax structure in Poland for 2027 requires comparing ryczałt, linear tax, and the tax scale before the 22 February 2027 deadline (20 February is a Saturday). For a B2B contractor earning over PLN 15,000 monthly with low expenses, the 12% lump-sum tax yields the highest net income. However, high operational costs or qualifying for the 5% IP Box relief can make the 19% linear tax a more profitable alternative.
The whole path to a first KSeF invoice in Biurko: company from GUS, KSeF connection, counterparty, issue, send, KSeF number and UPO. With a clear line between what to practise on the demo and what is already a real invoice.
Poland's national e-invoicing system is entirely Polish-only, meaning that API errors and official receipts require translation. Using software with a multilingual interface helps foreign entrepreneurs avoid costly errors in tax fields and split payment settings. Biurko solves this by storing language preferences individually for each user.
The right e-invoicing tool must align with your operational processes. For inventory, payroll, or full statutory accounting, traditional ERP systems or comprehensive platforms are recommended. Biurko is designed specifically for direct KSeF integration, multi-entity management, and automated workflows.
Switching your invoicing tool mid-year does not require starting your numbering sequence from one. Polish regulations only demand chronological sequence and uniqueness. Sales history issued through KSeF can be pulled automatically into your new software at no extra cost.
The first login to KSeF (Poland's mandatory national e-invoicing system) trips up more people than issuing the actual invoice. The Taxpayer Application shows several authentication methods, and none of them explains which one is right for you. This is not a trivial choice. Since 1 February 2026, KSeF has been mandatory for the largest companies, and since 1 April 2026 for other businesses (Ministry of Finance timeline); the smallest ones join on 1 January 2027, and until 31 December 2026 taxpayers whose monthly gross value of B2B invoices covered by the obligation does not exceed PLN 10,000 may issue invoices outside KSeF. Without valid authentication you can neither issue nor receive a structured invoice.
An invoice issued in offline24 mode must reach KSeF (Poland's mandatory national e-invoicing system) by the end of the next business day. Nobody sends you a reminder. Biurko detects when the KSeF gateway stops responding, issues the invoice in offline mode with the required QR codes, holds it in a queue, and pushes it through the moment the system recovers. No clicking, no duplicates, full audit log.
A token carries permissions inside it. A certificate proves identity and nothing else. You cannot add the second offline QR code (KOD II) with a token, and you cannot even request a certificate while authenticated with one. In June 2026 Poland's Ministry of Finance proposed keeping tokens permanently. Our decision has not changed, and here is why.
You do the books for 30 companies. Every morning you open the KSeF Taxpayer App — KSeF (Krajowy System e-Faktur) is Poland's mandatory national e-invoicing system — switch the context to your first client, pull their invoices, switch to the second, pull again, switch again. Thirty times over. That isn't work. It's a penalty for having clients. Since 1 April 2026, KSeF has been mandatory for most companies in Poland (the smallest from 1 January 2027), so this stopped being a big-corporation problem — it's every accounting office's daily reality. The good news: you don't have to log in from scratch every time. The bad news: the free government tool wasn't built for someone juggling thirty NIPs (Polish tax IDs) at once. This guide covers why logging in client-by-client is a dead end, what KSeF itself says about permissions, certificates and tokens, and what working with many clients looks like in Biurko: one account, one-click switching between companies, and a separate KSeF connection for each company.
If your Polish company is owned or run from abroad, the permissions question in KSeF (Poland's national e-invoicing system) usually comes down to one form you can't avoid: the ZAW-FA. A Polish sole trader can skip it. A foreign-owned limited company almost always cannot. This matters because KSeF is already mandatory — since 1 February 2026 for the largest taxpayers and since 1 April 2026 for most remaining VAT payers (the smallest from 1 January 2027). Under the current act, penalties under Article 106ni of the VAT Act apply from 1 January 2027 and reach up to 100% of the VAT shown on the invoice. On 16 September 2026 the Ministry of Finance announced it will move them to 1 January 2028; that is a bill not yet passed, and it moves only the penalties, not the obligation to use KSeF. Getting access right for the people who actually issue and book your invoices is worth doing now, calmly. Below: who files ZAW-FA and when, how to designate your first user, and how to grant access to an employee or accounting office.
An email when we publish a new article — and nothing else.
We use only essential cookies. Visit statistics are kept on our server, with nothing saved on your device. Website Policy
