Polish clearance XML · active

KSeF FA(3)

The binding Polish structured invoice logical structure used by KSeF 2.0 from 1 February 2026.

FA(3) XMLKSeF response and UPO data

Current version and implementation status

Version noteFA(3), binding from 1 February 2026
Statusactive
Reviewed2026-08-02
FamilyPolish clearance XML
Open official technical source

How to recognize the profile

Do not rely on the file extension alone. Inspect the root namespace, customization/profile identifiers, version values and authority-specific envelope.

  • FA(3) namespace
  • NrKSeF
  • Podmiot1 and Podmiot2

Production validation stack

  1. 1
    FA(3) XSD

    Confirm that the document is well formed and structurally compatible with the intended FA(3) syntax.

  2. 2
    KSeF logical constraints

    Apply semantic and business-rule checks rather than accepting a file merely because it parses.

  3. 3
    Tax and identifier rules

    Validate currencies, countries, tax categories, units, payment means and other controlled values against the correct release.

  4. 4
    Submission response handling

    Apply the national, network or authority restrictions that narrow the base syntax.

EInvoiceLab’s browser tools provide detection, inspection and technical preflight. A profile is only production-valid after applying the correct official artefacts and obtaining the required network or authority outcome.

Common errors and corrective action

!
FA(2) file used after transition

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Invalid NIP

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Incorrect tax summary

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

!
Rejected logical structure

Locate the relevant field and rule, correct the source mapping, rerun every validation layer, then preserve the final response.

Countries using or referencing this profile

Questions people ask

What is FA(3)?

The binding Polish structured invoice logical structure used by KSeF 2.0 from 1 February 2026.

How is FA(3) validated?

A production check normally applies FA(3) XSD, KSeF logical constraints, Tax and identifier rules, Submission response handling. Local browser preflight cannot replace the official validation artefacts or authority outcome.

Which version should I use?

The current research note is: FA(3), binding from 1 February 2026. Confirm release notes at the official source before production deployment.

Practical tools

Inspect and prepare FA(3) files