Rule reference

BR-36 The document level charge at charges[0] has no usable charge amount (BT-99): you supplied missing

The document level charge at charges[0] has no usable charge amount (BT-99): you supplied missing. Each BG-21 group must have one, because it is the only figure that actually moves money — the percentage (BT-101) and base amount (BT-100) are documentation of how the figure was reached, not substitutes for it, and BT-108 is the sum of these amounts under BR-CO-12.

This rule is implemented and its error payload below is real, but the long-form write-up — normative text, worked example, divergence note — is not written yet. Everything the library knows about this rule is on this page. Ask and we will prioritise it.

Business term
BT-99
Severity
fatal

What the library returns

The exact object in result.errors when this rule fires. Generated by running @attestwire/en16931, not transcribed:

TeachingError
{
  "rule": "BR-36",
  "field": "BT-99",
  "severity": "fatal",
  "message": "The document level charge at charges[0] has no usable charge amount (BT-99): you supplied missing. Each BG-21 group must have one, because it is the only figure that actually moves money — the percentage (BT-101) and base amount (BT-100) are documentation of how the figure was reached, not substitutes for it, and BT-108 is the sum of these amounts under BR-CO-12.",
  "fix": "Set charges[0].amount to a positive number of EUR — always positive, even for an allowance: it is the array the entry sits in, not its sign, that decides whether the figure is deducted or added.",
  "example": "\"charges\": [{ \"amount\": 25.00, \"vatCategory\": \"S\", \"vatRate\": 19, \"reason\": \"Freight\" }]",
  "xpath": "/ubl:Invoice/cac:AllowanceCharge[1]/cbc:Amount",
  "docsUrl": "https://attestwire.com/rules/BR-36"
}

xpath locates the element in the generated UBL document, which is where a KoSIT or Peppol validator will report the same problem.

A passing value

the shape this field expects
"charges": [{ "amount": 25.00, "vatCategory": "S", "vatRate": 19, "reason": "Freight" }]

The fix

Set charges[0].amount to a positive number of EUR — always positive, even for an allowance: it is the array the entry sits in, not its sign, that decides whether the figure is deducted or added.

Arrived from a stack trace? The docsUrl on every error links straight here. Something wrong on this page — tell us.