Parsing Polish KSeF FA(2) and FA(3) XML files locally
Poland’s National e-Invoice System (Krajowy System e-Faktur) exchanges B2B invoices as structured <Faktura> XML files rather than human-readable PDFs. Under the Polish Ministry of Finance KSeF Downloads Guide, businesses transitioning to mandatory structured invoicing need a reliable way to inspect raw XML tags, verify VAT totals, and print clean copies for internal workflows.
As a free KSeF XML viewer without login, this tool lets Polish teams run a local KSeF XML preview (podgląd or podglad KSeF XML) and structured invoice visualization (wizualizacja faktury KSeF, faktura ustrukturyzowana PDF) with 0 bytes uploaded. If you need to analyze line items across many XML files in a spreadsheet, extract structured KSeF XML elements into Excel tables using the tabular converter.
Decoding UTF-8, ISO-8859-2, and Windows-1250 character sets
While modern KSeF exports use UTF-8, legacy Polish ERP systems occasionally emit XML headers declared as ISO-8859-2 or Windows-1250. The reader inspects the XML encoding declaration in the first 200 bytes and selects the matching TextDecoder so Polish characters (ą, ć, ę, ł, ń, ó, ś, ź, ż) render without mojibake.
| KSeF XML element | Mapped invoice meaning | Viewer check or display |
|---|---|---|
Podmiot1 / Podmiot2 |
Seller and buyer legal parties | Validates 10-digit Polish NIP Mod-11 checksums |
P_9A / P_9B |
Net or gross unit line price | Extracts unit pricing and recalculates line totals |
P_13_1 / P_14_1 |
Standard 23% (or 22%) VAT base and tax | Displays standard-rate VAT summary |
P_13_2 / P_14_2 |
Reduced 8% (or 7%) VAT base and tax | Displays reduced-rate VAT summary |
P_13_3 / P_13_6–P_13_10 |
5%, 0% WDT/EX, zw exempt, oo reverse charge |
Maps zero, exempt, and reverse-charge categories |
Adnotacje / P_18A |
Split payment (MPP) flag (1) |
Displays Mandatory (P_18A = 1) badge |
Exporting clean A4 readable PDFs in a Web Worker
Click Save as PDF to convert the parsed <Faktura> structure into a clean, printable A4 document named after your source XML file. You can also click Full preview to inspect the rendered PDF before saving, or Download the XML to keep a local copy.
How do KSeF VAT buckets, P_18A split payment, and NIP checks work?
KSeF XML separates net taxable amounts (P_13_*) and VAT amounts (P_14_*) into numbered rate buckets while flagging mandatory split payment (P_18A) and validating 10-digit Polish NIP numbers with Modulo-11 arithmetic. Checking these elements locally catches arithmetic discrepancies and mistyped tax IDs before booking an invoice.
Mapping P_13 and P_14 buckets across Polish VAT rates
The parser reads P_13_1 and P_14_1 for 23% VAT, P_13_2 and P_14_2 for 8%, and P_13_3 and P_14_3 for 5%, plus P_13_4 and P_14_4 for 4% and 3% flat-rate buckets. It also maps P_13_5 through P_13_10 for 0% domestic, intra-Community WDT, export, exempt (zw), and reverse-charge (oo) supplies.
This clear presentation supports readability principles under EU VAT Directive 2006/112/EC and helps accountants spot mismatched tax buckets before booking.
Validating 10-digit seller and buyer NIPs with Mod-11 weights
Every Podmiot1 seller NIP and Polish Podmiot2 buyer NIP is checked against the official 9-weight vector [6, 5, 7, 2, 3, 4, 5, 6, 7] modulo 11. If an invalid Polish NIP checksum error appears in the Checks panel, verify the 10-digit tax ID before posting. To verify lists of Polish vendor tax IDs outside an XML file, use the Polish 10-digit NIP Mod-11 validator directly.
Comparing KSeF FA(2) and FA(3) against Peppol BIS 3.0 UBL
Poland’s national KSeF <Faktura> schema uses Ministry of Finance XML tags rather than the European UBL 2.1 syntax used in Peppol cross-border procurement. Understanding the differences prevents schema mismatches when trading with both Polish and EU counterparties.
Key additions in the 2026 FA(3) logical structure
Knowing what the difference is between KSeF FA(2) and FA(3) prevents rejected submissions after the mandatory February 2026 cutover. Key FA(2) versus FA(3) differences include expanding bank account fields to 34 characters for full IBANs, adding an employee (Pracownik) party role, and supporting structured attachments up to 3 MB inside the XML.
When cross-border buyers require Peppol UBL instead of KSeF
When billing EU public authorities or cross-border buyers outside KSeF, counterparties typically require OpenPeppol BIS Billing 3.0 Specification UBL XML rather than Polish <Faktura> tags. You can prepare cross-border EU invoices in EN 16931 UBL format in the dedicated generator.
Formal KSeF validation scope and zero-upload privacy
As outlined in European Commission eInvoicing in Poland documentation, official KSeF submission and UPO clearance require authenticated Ministry of Finance APIs. Running checks locally in a Web Worker keeps confidential supplier pricing and buyer NIPs private with 0 bytes transmitted.
Inspecting line-item totals and tax rate buckets offline before booking vendor invoices helps finance teams catch discrepancies early without exposing sensitive commercial data to external web viewers.
Tip: Check the Checks card above the invoice preview before archiving a vendor XML; any
KSeF-NIPor VAT rounding warning highlights fields worth verifying against your supplier’s official UPO.
To verify the 34-character Polish IBAN bank account printed on FA(3) invoices before releasing payment, use the IBAN checker. This visualizer is provided for informational and operational convenience rather than certified tax or accounting advice; confirm KSeF XSD compliance and statutory filing rules with a qualified Polish accountant or the Ministry of Finance.