Rule reference

BR-49 The invoice carries a payment instruction group (BG-16), so it must specify the payment means type code (BT-81)

The invoice carries a payment instruction group (BG-16), so it must specify the payment means type code (BT-81). BG-16 is optional in core EN 16931 — but once present it has to be actionable, and the means code is the part a payment system reads. An IBAN with no means code does not tell the payer whether you expect them to push a credit transfer or whether you intend to collect by direct debit, which are opposite instructions.

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-49",
  "field": "BT-81",
  "severity": "fatal",
  "message": "The invoice carries a payment instruction group (BG-16), so it must specify the payment means type code (BT-81). BG-16 is optional in core EN 16931 — but once present it has to be actionable, and the means code is the part a payment system reads. An IBAN with no means code does not tell the payer whether you expect them to push a credit transfer or whether you intend to collect by direct debit, which are opposite instructions.",
  "fix": "Set payment.meansCode to a UNTDID 4461 code: \"58\" SEPA credit transfer, \"30\" credit transfer, \"59\" SEPA direct debit, \"48\" bank card, \"57\" standing agreement, \"97\" clearing between partners. If you did not mean to give payment instructions at all, remove the payment object.",
  "example": "\"payment\": { \"meansCode\": \"58\", \"iban\": \"DE02120300000000202051\" }",
  "xpath": "/ubl:Invoice/cac:PaymentMeans/cbc:PaymentMeansCode",
  "docsUrl": "https://attestwire.com/rules/BR-49"
}

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

Set payment.meansCode to a UNTDID 4461 code: "58" SEPA credit transfer, "30" credit transfer, "59" SEPA direct debit, "48" bank card, "57" standing agreement, "97" clearing between partners. If you did not mean to give payment instructions at all, remove the payment object.

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