KSeF Poland: controlling invoices after implementation
Reviewed: 13 October 2026 · Polish law and taxation
By October 2026, businesses operating in Poland need to assess how KSeF works in everyday invoicing. A successful software connection says little about whether rejected documents are resolved, overseas customers receive the right invoice or the accounting team can reconcile the records. For a CFO, the useful question is whether each sale leaves a reliable trail from commercial approval to payment.
Map the obligation to your actual transactions
Mandatory issuance through KSeF started in stages in February and April 2026. A transitional provision for invoices issued outside the system within a statutory monthly gross limit of PLN 10,000 remains relevant until year-end. Its conditions require separate monitoring. The Ministry of Finance explains the scope and exclusions.
An overseas customer's address does not, by itself, take an invoice outside KSeF. A Polish supplier within scope must also assess exports, intra-Community supplies and services to foreign businesses. The issuer's establishment, the involvement of a Polish fixed establishment and particular invoicing arrangements can affect the answer. A Polish VAT number alone does not settle those questions.
Reconcile invoice data across sales, KSeF and accounting
The first handover runs from the sales platform to KSeF. The monitoring report should distinguish preparation, submission, acceptance and rejection. Assign a named owner and an escalation time to every rejected document. An application message saying “sent” should not automatically close the accounting task.
The second handover connects invoice records with the ledger and VAT records. Reconcile invoice numbers, KSeF identifiers, customer details, currencies and amounts. Investigate mismatches rather than overwriting them. System acceptance does not confirm the correct VAT treatment or prove that the underlying supply took place. Commercial evidence therefore remains important.
The third handover concerns the customer. For recipients covered by Article 106gb(4) of the Polish VAT Act, the invoice must be provided through an agreed channel. For cross-border sales, document the delivery address, the required visual representation and responsibility for appropriate invoice markings. The official invoicing guidance distinguishes issuance in KSeF from making the invoice available to these recipients.
Illustrative example: the customer has an earlier version
A Polish manufacturer invoices a German buyer for machinery. The sales team emails a PDF before the KSeF workflow finishes. The submission is rejected, the accounting team fixes the data, and the buyer retains the earlier document. The example is hypothetical, but the control problem is straightforward: the two parties are working from different records.
A workable response connects customer delivery with the relevant invoice status and records which version was provided. Where an offline mode is used, the business needs a separate procedure consistent with that mode. Issuing another invoice for the same sale without assessing the consequences can compound the problem. Finance should also check whether payment allocation or a correction needs attention.
The PLN 10,000 limit and offline24: separate tests
Until the end of 2026, Article 145m’s PLN 10,000 gross limit concerns monthly sales documented by the specified electronic or paper invoices. The exception is lost from the invoice that exceeds the limit. Do not wait until month-end to check it.
Under offline24, the invoice must be submitted promptly to KSeF, and no later than the next working day after issue. When it is provided outside the system to the relevant recipients before submission, two verification markings are required: one for invoice data and one confirming the issuer through a certificate. System unavailability and failure modes have their own rules; do not apply the offline24 timetable to all of them.
A domestic taxpayer with a Polish NIP receives this invoice through KSeF. Before a KSeF number is assigned, a transaction confirmation may be provided; it is not a VAT invoice. Agreed delivery outside the system concerns recipients under Article 106gb(4), including the relevant foreign customers.
CFO checklist
- Have domestic sales, exports, services and self-billing arrangements been classified?
- Does each rejection have an owner, a deputy and a resolution deadline?
- Can the ledger be reconciled without booking the same invoice twice?
- Do foreign recipients receive the correct document through an agreed channel?
- Are employee and external accountant permissions reviewed periodically?
- Have corrections, system unavailability and withdrawal of access been tested?
What to do next
Select a sample from the latest closed month containing an accepted invoice, a rejection, a correction and a cross-border sale. Reconstruct who approved each step and what the recipient received. Turn the findings into a short remediation plan with responsibilities and completion dates. Before changing software settings, establish whether the issue comes from tax classification, source data or integration design.
TLP's VAT advisory work for businesses can help assess the Polish tax aspects of this review. Bring a process map, representative exceptions and a list of cross-border transaction types so that the review can focus on the points that actually need a decision.
Tax rulings and case law reviewed: 1 November 2026.
A post-implementation review needs to cover incorrect customer data, corrections and transactions documented outside the invoicing system. The cases below distinguish correcting a KSeF document from correcting the VAT period.
KSeF corrections, wrong tax IDs and indirect rebates: which documents apply?
One collective correction with increases and reductions: which VAT period applies?
In the ruling of 11 September 2026, 0113-KDIPT1-2.4012.549.2026.2.KT, KIS accepted one corrective invoice for electricity-sales intermediary fees containing increases and decreases. It had to satisfy VAT Article 106j and identify the invoices and transactions. This was not Article 106j(3)’s special period-rebate correction. KIS nevertheless rejected always reporting the net balance in the issue period: increases follow Article 29a(17) and the cause’s occurrence, while decreases follow the relevant paragraphs 13–13c and 14. Technical KSeF acceptance does not determine that classification.
One document can settle several items with different timing consequences. Identify the reason for each increase and apply the relevant reduction rules separately. A breakdown by correction type and VAT period preserves that distinction instead of allowing the document’s net balance to determine the tax period.
Wrong purchaser tax ID in KSeF: correct to zero or amend the details?
The ruling of 25 September 2026, 0114-KDIP4-3.4012.407.2026.1.AAR, addresses several correction types and is partly favourable, partly unfavourable. For an invoice accepted by KSeF but issued to the wrong purchaser, KIS required a zeroing correction for that counterparty and a new invoice for the actual purchaser. Under those facts both were reported in the original sale period because the error existed from the outset. Similarly, duplicate invoicing of the same service required zeroing one invoice. Do not extend that finding to returned advances or every other correction discussed in the ruling.
The error existed at the original sale: the transaction involved the correct customer, but the invoice named another entity. A zero correction and replacement invoice reconstructed the same sale, explaining the original-period treatment. A duplicated invoice similarly requires removing duplicated turnover rather than recognising another sale.
A manufacturer’s indirect rebate: accounting note or KSeF invoice?
In the ruling of 15 October 2026, 0114-KDIP1-1.4012.565.2026.2.EW, a manufacturer paid bonuses to customers buying its goods from independent distributors. Recipients supplied no marketing or other services in return. KIS treated the bonus as an indirect rebate documented by a reliable accounting note, rather than a recipient’s invoice or structured KSeF invoice. There was no direct manufacturer-to-recipient sale or original invoice between them. The rebate could adjust the manufacturer’s output VAT, but the note generated no deductible input VAT. A bonus actually remunerating advertising, display or another service requires a fresh assessment.
The customer purchased from a distributor, while the manufacturer funded the bonus. There was no sale between the bonus parties to correct and no service supplied in return. Those two features explained the accounting note. Payment for advertising or display would instead introduce a different service and documentation basis.
Numerical example: one document, two VAT periods
Our model, not figures from the ruling. An online combined corrective invoice issued in November includes a PLN 20,000 net increase whose subsequent cause arose in October and a PLN 10,000 net decrease covered by the November structured correction. Assume 23% VAT, correct classification and no Article 29a(13a–13c) exceptions.
| Item | Net change | VAT change | Period |
|---|---|---|---|
| Increase | +PLN 20,000 | +PLN 4,600 | October: cause of increase |
| Decrease | −PLN 10,000 | −PLN 2,300 | November: stated correction assumptions |
| Document balance | +PLN 10,000 | +PLN 2,300 | Does not assign one period to both events |
Reporting only PLN 2,300 net VAT in November would omit the PLN 4,600 increase attributable to October. A different issue mode or a cause already existing when the original invoice was issued requires reassessment. Record each item’s cause and dates, not just “accepted in KSeF”.
Invoice errors, VAT deduction and penalties: what follows from CJEU judgments?
In Senatex, C-518/14, 15 September 2016, the CJEU rejected denying retroactive effect to an invoice correction concerning a tax identification number for VAT deduction. The taxpayer already held invoices; the case did not concern having no invoice at all. It informs analysis of corrected particulars and deduction timing, rather than authorising disregard of KSeF issue or submission duties.
Barlis 06, C-516/14, 15 September 2016, concerned overly general service descriptions and performance periods. A formal defect alone could not justify refusal of deduction where the authority had information to verify substantive conditions; additional taxpayer evidence also mattered. This does not validate arbitrary invoice contents. The taxpayer still has to establish an actual purchase and its connection to taxable activities.
In Grupa Warzywna, C-935/19, 15 April 2021, the CJEU opposed an automatic 20% penalty on an overstated refund insofar as it prevented consideration of the error’s nature, absence of fraud and lack of revenue loss. This concerned the then additional VAT liability, not Article 106ni’s KSeF penalty. Proportionality matters when reviewing penalties, but the judgment neither cancels every penalty in advance nor decides the proposed 2028 postponement.
These judgments provide context for invoices, evidence and sanctions; none directly decides the current KSeF bill. Separate the actual transaction, invoicing duty, system-processing result, VAT period and possible liability basis. Another taxpayer’s ruling identifies issues but gives no individual protection to a business with different facts.
Frequently asked questions
Does a foreign buyer remove an invoice from KSeF?
Not by itself. Establish the issuer's obligation, transaction type and exceptions. Issuing through KSeF and providing the invoice to the foreign customer are separate steps.
Does KSeF acceptance confirm correct VAT treatment?
No. Technical acceptance does not determine the place of supply, rate or actual transaction. Reconcile the data with VAT records, accounts and business evidence.
Where should a review of the working process start?
Select accepted invoices, rejections, corrections and foreign sales. Trace statuses, responsibility and the version delivered to the customer; examine offline procedures separately.
Discuss your Polish tax or legal question
Briefly describe your business in Poland, the decision you face and the countries involved. We will agree the scope, consultation language and information needed before the analysis.
Write to us
- Supply chain, countries involved and invoice workflow.
- The issue, relevant period and sample KSeF statuses or documents.
Sources and further reading
- Polish VAT Act — art. 145m, 106gb — Dz.U. 2026, poz. 1263; consolidated text
- Polish Ministry of Finance — KSeF — scope of mandatory KSeF
- Polish Ministry of Finance — KSeF — issuing and receiving invoices
- Polish Ministry of Finance — KSeF — offline24 mode
Information material. An assessment of a particular situation requires its facts and the rules applicable to the relevant period.
