BR-27:The Item net price (BT-146) shall NOT be negative.
The Item net price (BT-146) shall NOT be negative.. Review the `cbc:PriceAmount` element.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Seller company name
What is BR-27?
BR-27 is a fatal validation rule defined in the EN 16931 specification. It validates the RegistrationName element under PartyName > Name or cac:PartyLegalEntity 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: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name or cac:PartyLegalEntity/cbc:RegistrationName
Why This Error Matters
Invoice rejected. Negative prices are invalid - use credit notes or negative quantities for refunds.
BR-27 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-27
- ·Specification: EN 16931
How to Fix It
Add trading name
In PartyName/Name for trading name
Or legal name
In PartyLegalEntity/RegistrationName for legal name
Best practice
Include both for clarity
Before / After
<cac:Price> <cbc:PriceAmount>-100.00</cbc:PriceAmount> </cac:Price>
<cac:Price> <cbc:PriceAmount>100.00</cbc:PriceAmount> </cac:Price>
Technical Reference
XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name or cac:PartyLegalEntity/cbc:RegistrationNameCode Example
<cac:Party>
<cac:PartyName>
<cbc:Name>ABC Trading Ltd</cbc:Name>
</cac:PartyName>
<cac:PartyLegalEntity>
<cbc:RegistrationName>ABC Trading Limited</cbc:RegistrationName>
</cac:PartyLegalEntity>
</cac:Party>Common Causes
- ·Negative price entered in source system by mistake
- ·Credit adjustment applied at line level incorrectly
- ·Discount exceeds gross price creating negative net
- ·Currency conversion resulted in sign error
- ·Data import from legacy system with sign convention issue
Seeing this in production? The API handles BR-27 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
The seller must have either a trading name or legal registration name.
Add seller PartyName or PartyLegalEntity/RegistrationName. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-27 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.
Many instances of BR-27 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including seller trading name or legal name required.
BR-27 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-27 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.