ARLing

E-invoice / Rules / BR-33

E-invoice rule EN 16931 schematron

BR-33: The allowance on document level needs a reason

The allowance on document level needs a reason. Add cbc:AllowanceChargeReason (text) or cbc:AllowanceChargeReasonCode (code).

Check your own file (free) Create an e-invoice

Original wording of the rule

[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).

Source of the quotation: EN 16931 schematron (ConnectingEurope/eInvoicing-EN16931, licence EUPL 1.2)

How to fix it

  1. Open the XML file and find the element cac:AllowanceCharge/cbc:AllowanceChargeReason.
  2. Add or correct the element the way the wording of the rule above asks for.
  3. Save the file and check it again with our checker. It runs in your browser, the file is never uploaded.

A correct UBL 2.1 snippet

<cac:AllowanceCharge
    xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
    xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:AllowanceChargeReason>Zlava za objem</cbc:AllowanceChargeReason>
</cac:AllowanceCharge>

The snippet is only the part of the document the rule is about. Put it in the right place inside your invoice; the namespaces are written here only so that the snippet reads on its own.

When it is reported

Profile: EN 16931, Peppol BIS Billing 3.0, XRechnung 3.x

How we rate it: error

UBL elements: cbc:AllowanceChargeReason, cbc:AllowanceChargeReasonCode

Where we point in the file: /Invoice/cac:AllowanceCharge[1]

Related rules

Our check is not complete: we do not check the XSD schema and we do not implement every rule, and a file that passes says nothing about whether the buyer or the Peppol network will accept it. Licences for the quoted wordings are listed in our sources.