PDFPipe

BR-CO-21 to BR-CO-24: every allowance and charge needs a reason

Four rules with one requirement over the four allowance and charge groups. Each must contain a reason or a reason code, and may contain both. The four cover the document level allowance (BG-20), the document level charge (BG-21), the invoice line allowance (BG-27) and the invoice line charge (BG-28). Where both are given, the agreement between them is checked separately, by BR-CO-05 to BR-CO-08.

BR-CO-21

Each Document level allowance (BG-20) shall contain a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98), or both.

Severity
Rejects the invoice
Applies to
CII, UBL
Family
BR-CO
  • BT-97
  • BT-98
  • BG-20

BR-CO-22

Each Document level charge (BG-21) shall contain a Document level charge reason (BT-104) or a Document level charge reason code (BT-105), or both.

Severity
Rejects the invoice
Applies to
CII, UBL
Family
BR-CO
  • BT-104
  • BT-105
  • BG-21

BR-CO-23

Each Invoice line allowance (BG-27) shall contain an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140), or both.

Severity
Rejects the invoice
Applies to
CII, UBL
Family
BR-CO
  • BT-139
  • BT-140
  • BG-27

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.

Severity
Rejects the invoice
Applies to
CII, UBL
Family
BR-CO
  • BT-144
  • BT-145
  • BG-28

About the BR-CO family

Calculation and consistency rules. These check that the totals on the invoice add up and agree with the line items and VAT breakdown.

Related rules

A validator reports one code at a time. These check the same fields, so they are the ones most likely to fire on the same invoice.

  • BR-33 Each Document level allowance (BG-20) shall have a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98).
  • BR-CO-05 Document level allowance reason code (BT-98) and Document level allowance reason (BT-97) shall indicate the same type of allowance.
  • BR-51 In accordance with card payments security standards an invoice should never include a full card primary account number (BT-97). At the moment PCI Security Standards Council has defined that the first 6 digits and last 4 digits are the maximum number of digits to be shown.
  • BR-38 Each Document level charge (BG-21) shall have a Document level charge reason (BT-104) or a Document level charge reason code (BT-105).
  • BR-CO-06 Document level charge reason code (BT-105) and Document level charge reason (BT-104) shall indicate the same type of charge.
  • BR-42 Each Invoice line allowance (BG-27) shall have an Invoice line allowance reason (BT-139) or an Invoice line allowance reason code (BT-140).
  • BR-CO-07 Invoice line allowance reason code (BT-140) and Invoice line allowance reason (BT-139) shall indicate the same type of allowance reason.
  • BR-44 Each Invoice line charge (BG-28) shall have an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145).
  • BR-CO-08 Invoice line charge reason code (BT-145) and Invoice line charge reason (BT-144) shall indicate the same type of charge reason.

Others in the BR-CO family:

Check your own invoice

Drop a Factur-X, ZUGFeRD, XRechnung, or Peppol file in and see every rule it breaks, not just this one. Free, no signup.

Open the validator

Rule text comes from the EN 16931 validation artefacts published by CEN/TC 434 and the European Commission, used unmodified under the European Union Public Licence v1.2. The artefacts are available from the upstream repository.
Factur-X, ZUGFeRD, XRechnung, and Peppol are trade marks of FNFE-MPE, FeRD, KoSIT, and OpenPeppol AISBL respectively, and are used here only to identify the invoice formats this tool reads. PDFPipe is not affiliated with, endorsed by, or certified by any of them, nor by CEN or the European Commission.