Rule reference

BR-CL-16 The payment means type code (BT-81) must come from UNTDID 4461, but "999" is not in that list

The payment means type code (BT-81) must come from UNTDID 4461, but "999" is not in that list. The code is what tells the payer's system how the money is meant to move; free text such as "bank transfer" or an invented code is not resolvable.

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-81
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-CL-16",
  "field": "BT-81",
  "severity": "fatal",
  "message": "The payment means type code (BT-81) must come from UNTDID 4461, but \"999\" is not in that list. The code is what tells the payer's system how the money is meant to move; free text such as \"bank transfer\" or an invented code is not resolvable.",
  "fix": "Use \"58\" SEPA credit transfer (the default for euro-area invoices), \"30\" credit transfer, \"59\" SEPA direct debit, \"48\" bank card, \"57\" standing agreement, \"97\" clearing between partners, or \"1\" instrument not defined. Note that XRechnung then requires the matching payment group: BG-17 for 30/58, BG-18 for 48/54/55, BG-19 for 59.",
  "example": "\"payment\": { \"meansCode\": \"58\", \"iban\": \"DE02120300000000202051\" }",
  "xpath": "/ubl:Invoice/cac:PaymentMeans/cbc:PaymentMeansCode",
  "docsUrl": "https://attestwire.com/rules/BR-CL-16"
}

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
"payment": { "meansCode": "58", "iban": "DE02120300000000202051" }

The fix

Use "58" SEPA credit transfer (the default for euro-area invoices), "30" credit transfer, "59" SEPA direct debit, "48" bank card, "57" standing agreement, "97" clearing between partners, or "1" instrument not defined. Note that XRechnung then requires the matching payment group: BG-17 for 30/58, BG-18 for 48/54/55, BG-19 for 59.

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