`BR-CO-22` Taken individually, the reason (BT-104) and the reason code (BT-105) on the document level charge at charges[0] are both optional terms — which is why this constraint exists separately from BR-38: it is the co-occurrence rule that forbids the one combination the cardinalities allow, namely neither

Taken individually, the reason (BT-104) and the reason code (BT-105) on the document level charge at charges[0] are both optional terms — which is why this constraint exists separately from BR-38: it is the co-occurrence rule that forbids the one combination the cardinalities allow, namely neither. Supplying both is explicitly permitted and is usually the better answer, since the code is what a receiving system can act on automatically and the text is what a person reads.

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-104 / BT-105
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-CO-22",
  "field": [
    "BT-104",
    "BT-105"
  ],
  "severity": "fatal",
  "message": "Taken individually, the reason (BT-104) and the reason code (BT-105) on the document level charge at charges[0] are both optional terms — which is why this constraint exists separately from BR-38: it is the co-occurrence rule that forbids the one combination the cardinalities allow, namely neither. Supplying both is explicitly permitted and is usually the better answer, since the code is what a receiving system can act on automatically and the text is what a person reads.",
  "fix": "Add charges[0].reason, charges[0].reasonCode, or both. If no UNCL 7161 code fits what you are charging for, omit the code and write the reason as free text — the list has no \"other\" entry, and inventing a code fails BR-CL-20.",
  "example": "\"reason\": \"Freight service\", \"reasonCode\": \"FC\"",
  "xpath": "/ubl:Invoice/cac:AllowanceCharge[1]/cbc:AllowanceChargeReasonCode",
  "docsUrl": "https://attestwire.com/rules/BR-CO-22"
}

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

"reason": "Freight service", "reasonCode": "FC"

The fix

Add charges[0].reason, charges[0].reasonCode, or both. If no UNCL 7161 code fits what you are charging for, omit the code and write the reason as free text — the list has no "other" entry, and inventing a code fails BR-CL-20.

All 292 rules →

Nearby: BR-CO-23 — The reason (BT-139) and the reason code (BT-140) on the invoice line allowance at lines[0].allowances[0] are individually optional terms, and this constraint — separate from BR-42, which is the cardinality rule on the group — is what rules out the one combination those cardinalities would otherwise permit: neither present; BR-CO-21 — Taken individually, the reason (BT-97) and the reason code (BT-98) on the document level allowance at allowances[0] are both optional terms — which is why this constraint exists separately from BR-33: it is the co-occurrence rule that forbids the one combination the cardinalities allow, namely neither; BR-CO-24 — The reason (BT-144) and the reason code (BT-145) on the invoice line charge at lines[0].charges[0] are individually optional terms, and this constraint — separate from BR-44, which is the cardinality rule on the group — is what rules out the one combination those cardinalities would otherwise permit: neither present.

Check this rule against your invoice via the hosted API → https://api.attestwire.com/docs

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