What causes the BR-CO-24 error?

BR-CO-24 occurs when an invoice line has a charge (surcharge) in BG-28 but neither the reason text (BT-144) nor reason code (BT-145) is provided. EN16931 requires at least one of these fields.

How do I fix BR-CO-24?

Add either an AllowanceChargeReasonCode (BT-145) like ABK for Miscellaneous, or an AllowanceChargeReason (BT-144) text description, or both. Invoice Navigator can auto-fix this by adding the default code ABK.

Is BR-CO-24 a critical error?

Yes, BR-CO-24 is an error that will cause invoice rejection. EN16931 requires every line charge to have either a reason code or reason text to explain the surcharge.

Can BR-CO-24 be automatically fixed?

Yes. Invoice Navigator can automatically add the default reason code ABK (Miscellaneous) to line charges missing a reason. This is a safe, non-financial fix that simply adds explanatory metadata.

Error codes · EN 16931

BR-CO-24In your invoicing software

Invoice Line Charge Reason Required

This is the rejection, word for word: „[BR-CO-24] Each Invoice line charge (BG-28) shall contain an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145), or both.“

XPath: /Invoice/cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator='true']/cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doInvoice Navigator automatically fixes this issue by correcting the `cac:AllowanceCharge` element in your Invoice (BR-CO-24).

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<cac:InvoiceLine>
  <cac:AllowanceCharge>INVALID_CODE</cac:AllowanceCharge>
</cac:InvoiceLine>

After

<cac:InvoiceLine>
  <cac:AllowanceCharge>VALID_CODE</cac:AllowanceCharge>
</cac:InvoiceLine>

Element order is part of the rule: if the element sits in the wrong place, the validator rejects with BR-CO-24.

What the finding looks likeExample

FindingStructure invalid · BR-CO-24

Location//cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator='true' and not(cbc:AllowanceChargeReason) and not(cbc:AllowanceChargeReasonCode)]/cbc:AllowanceChargeReasonCode

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

BR-CO-23Invoice Line Allowance Reason Required