Each invoice line must contain an item net price

Why it fires on invoices that look fine

Almost nobody hits this rule because they forgot the field exists. They hit it because something between their system and the document dropped it, changed its shape, or filled it with a value that is right somewhere else. These are the causes worth checking first.

• Only the line total was sent, because the source system stores a total and no unit price.
• The price sent is the gross price before a discount, where the field takes the price actually charged.
• The price sent includes VAT. The field is the net price, and sending the gross one makes every downstream total disagree by exactly the VAT rate.

What to change

• Send the net unit price actually charged, after any discount that applies to the price rather than to the line.
• If you genuinely only have a total, send a quantity of 1 and the total as the price. That is honest and it satisfies the line arithmetic.

The validator runs in your browser. Nothing is uploaded, and you can confirm that yourself with the network panel open.

Rules you are likely to hit next

A document that breaks BR-26 usually breaks one of these too, because the same mapping gap tends to affect neighbouring fields.

• BR-27: item net price is not negative
• PEPPOL-EN16931-R120: line net amount agrees with quantity times item net price
• BR-24: line net amount

Questions people actually ask

What does BR-26 mean?

Every line carries the unit price of the item, excluding VAT.

Which field does BR-26 apply to?

BT-146, Item net price. That is the name the semantic model uses, which is what you search for in your own system's mapping when the identifier alone does not tell you which field to look at.

Does our validator check BR-26?

Yes. Paste your invoice data into the free validator and it reports this rule with the value it actually saw, without the document leaving your browser.