BR-PL-02:Invalid KSeF invoice type
Polish KSeF invoices must use valid invoice type codes.
Engine Classification
Financial or legal field · Modification blocked by policy
Reason: KSeF (Polish National e-Invoice System) only accepts specific invoice type codes. The invoice type must be changed in your source system to a KSeF-compatible code before submission.
What is BR-PL-02?
BR-PL-02 is a fatal validation rule defined in the ksef specification (POL national rules). It validates the KodFormularza element under Faktura > Naglowek in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: XPath: /Faktura/Naglowek/KodFormularza
Why This Error Matters
KSeF validates invoice type for proper processing and archival.
BR-PL-02 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-PL-02
- ·Specification: ksef
How to Fix It
Check type
FA for standard invoice, KOR for correction
Set correctly
In KodFormularza header
Match content
Correction must reference original
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Triggers validation error --> <KodFormularza></KodFormularza>
<!-- Corrected --> <KodFormularza>VALID_VALUE</KodFormularza>
Technical Reference
XPath: /Faktura/Naglowek/KodFormularzaCode Example
<Naglowek>
<KodFormularza kodSystemowy="FA (2)">FA</KodFormularza>
</Naglowek>Common Causes
- ·Wrong type code
- ·Using old version
- ·Type mismatch with content
Seeing this in production? The API handles BR-PL-02 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Polish KSeF invoices must use valid invoice type codes.
Use correct KSeF invoice type code. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.
Yes, BR-PL-02 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.
BR-PL-02 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.
BR-PL-02 is commonly seen in exports from Polish KSeF systems. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Content
Last updated: 3 March 2026
Detect BR-PL-02 Before Submission
This error involves a financial or legal field that cannot be auto-modified. The compliance engine flags it immediately with a clear diagnosis so your team can fix it at the source.