Invoicing in Poland, KSeF and the UPO, the ryczałt and the JPK files — written out step by step.
We write about invoicing in Poland — what belongs on a document, how to fix a mistake, and what exactly changed when the rules did. More and more often about the tax side of a B2B contract too: the ryczałt, the revenue ledger, the monthly advance and the annual JPK_EWP. And about running a firm day to day, with the paperwork finally out of the foreground. KSeF as well, but it is only one of the topics.
inFakt is a mature Polish accounting ecosystem with a free KSeF plan. If you run a single Polish entity and want the cheapest way to issue invoices, inFakt is hard to beat, and we will say so plainly. Biurko.io solves a different problem: many companies in one panel, certificate-based KSeF authentication instead of tokens, readable KSeF error messages, and a Ukrainian-language interface. Here is how to tell which one you need.
Browse every article and guide we have written.
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.
The mandatory split payment mechanism applies to B2B invoices exceeding PLN 15,000 gross that contain at least one item from Annex 15 of the VAT Act. Failure to comply triggers a 30% VAT penalty, income tax cost disallowance, and personal fiscal-penal liability. Learn how to handle MPP transfers and KSeF requirements.
Choosing the right KSeF software requires analyzing your document volume and accounting integration. While free government tools are sufficient for micro-businesses, growing companies need advanced multi-entity support. Ensure your system supports certificate authentication before 2027.
Heavy Polish ERP systems are designed for inventory management, payroll, and statutory books. If your business sells services, has no stock, and outsources bookkeeping, a lightweight invoicing tool is a more cost-effective way to achieve KSeF compliance. It eliminates complex implementation projects and per-document communication fees.
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.
inFakt and Biurko address fundamentally different business needs. inFakt provides online bookkeeping with an optional dedicated accountant for a single company. Biurko serves as a multi-company KSeF, invoicing, and VAT register layer designed to manage multiple entities under one subscription.
Self-billing in KSeF requires a valid contract, an agreed approval procedure, and a technical permission granted in the system. Without the system permission, KSeF will reject the invoice. Discover how to structure the workflow to protect your right to deduct input VAT.
Split payment (MPP) in Poland becomes compulsory for B2B invoices exceeding PLN 15,000 gross that document goods or services listed in Annex 15 to the VAT Act. Omitting the required annotation exposes the seller to an additional tax liability of 30% of the VAT on those sensitive items. The buyer faces the same 30% penalty and loss of tax-deductible costs if they pay via ordinary transfer.
Foreign currency conversion on a Polish VAT invoice requires using the average NBP rate from the last business day preceding the tax point or issue date. For VAT purposes, only NBP table A is correct. The KSeF transmission date does not alter this anchor if the invoice is treated under offline24 rules.
Linking advance and final invoices under the KSeF FA(3) schema requires precise field mapping. The settlement invoice ROZ must carry the full order values in its lines, while field P_15 holds only the remaining balance. You must link the documents using the mandatory KSeF identifier of the advance invoice.
A collective correcting invoice in KSeF must carry the details of every corrected original invoice inside the structured XML file. The FA(3) schema does not support loose spreadsheet attachments. Read how to handle bulk volume rebates and populate the required elements correctly.
The repeal of Article 106k on 1 February 2026 ended the use of corrective notes by buyers. Sellers must now correct a wrong buyer NIP by issuing a zero correction invoice followed by a new original invoice.
A rejected invoice never receives a KSeF number, meaning it was never legally issued and cannot be corrected. You must fix the XML file and resend it under the same invoice number. Learn the technical reasons behind validation failures and how to resolve them.
Manual data entry and invoice creation can consume over 10 hours of business time every month. With the mandatory KSeF system arriving in Poland, standardisation under the FA(3) schema makes automated invoicing highly efficient. Discover how automatic submission and retrieval can streamline your business operations.
An email when we publish a new article — and nothing else.
Essential ones keep the service running. The rest only with your consent. Cookie Policy
