BR-PL-01:Polish NIP number required
Fix: Add NIP number with PL prefix. Provide the required value in the free validator.
Polish invoices must include the NIP (tax identification number) for seller and buyer.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Polish NIP Number
What is BR-PL-01?
BR-PL-01 is a fatal validation rule defined in the peppol-bis-3 specification (POL national rules). It validates the CompanyID element under Party > PartyTaxScheme in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID
Why This Error Matters
NIP is mandatory for KSeF (Polish e-invoicing system) and B2B transactions.
BR-PL-01 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Rejected by PEPPOL Access Points
- ·Error returned: BR-PL-01
- ·Specification: peppol-bis-3
How to Fix It
Get NIP
10-digit Polish tax number
Format with prefix
PL + 10 digits (e.g., PL1234567890)
Add for both parties
Required for seller and buyer in B2B
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Missing or empty element triggers cbc:CompanyID error --> <cbc:CompanyID></cbc:CompanyID>
<!-- Provide the required value --> <cbc:CompanyID>VALID_VALUE</cbc:CompanyID>
Technical Reference
XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyIDCode Example
<cac:PartyTaxScheme>
<cbc:CompanyID>PL1234567890</cbc:CompanyID>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:PartyTaxScheme>Common Causes
- ·Missing PL prefix
- ·Invalid NIP format
- ·Inactive NIP number
Seeing this in production? The API handles BR-PL-01 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Polish invoices must include the NIP (tax identification number) for seller and buyer.
Add NIP number with PL prefix. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, BR-PL-01 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-01 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
BR-PL-01 is commonly seen in exports from Comarch, Sage Symfonia, Insert, Subiekt. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Related Content
Last updated: 3 March 2026
Validate your invoice
Drop your XML here to check for BR-PL-01
Fix BR-PL-01 with guided input
Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.