errorpeppol-bis-3
BR-14:Invoice line net amount required
Each invoice line must have a net amount (LineExtensionAmount).
Fix this in your source system
MANUALLine amounts require manual verification. Changes affect tax calculations and invoice totals. Verify the correct values in your invoicing system before correcting.
See the step-by-step instructions below to fix this error manually.
Why This Error Matters
Invoice rejected. This is the amount the buyer will pay and must be present for payment processing.
How to Fix It
1
Calculate line total
Quantity × Price per unit
2
Apply discounts
Subtract any line-level allowances
3
Set amount
Place result in LineExtensionAmount with currency
Code Example
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>
<cbc:LineExtensionAmount currencyID="EUR">100.00</cbc:LineExtensionAmount>
<!-- Price per unit: 10.00 -->
</cac:InvoiceLine>Technical Details
XPath: /Invoice/cac:InvoiceLine/cbc:LineExtensionAmountCommon Causes
- Tax inclusive amount not calculated by source system
- TaxInclusiveAmount field not mapped in export
- Export template missing final gross amount
- Tax calculation not completed before export
- Rounding differences caused amount validation failure
Commonly Seen In
All invoicing software
Frequently Asked Questions
Each invoice line must have a net amount (LineExtensionAmount).
Add LineExtensionAmount = Quantity × UnitPrice. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-14 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-14 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invoice line net amount required.
BR-14 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Last updated: 18 January 2026
Share this guide: