Attestwire

Rule reference

BR-DE-1 XRechnung requires payment instructions (BG-16) with a payment means type code (BT-81)

XRechnung requires payment instructions (BG-16) with a payment means type code (BT-81). Core EN 16931 leaves this optional, but the German CIUS makes it mandatory so that a public-sector payer can settle the invoice without a phone call.

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
BG-16
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-DE-1",
  "field": "BG-16",
  "severity": "fatal",
  "message": "XRechnung requires payment instructions (BG-16) with a payment means type code (BT-81). Core EN 16931 leaves this optional, but the German CIUS makes it mandatory so that a public-sector payer can settle the invoice without a phone call.",
  "fix": "Set payment.meansCode to a UNTDID 4461 code: \"58\" SEPA credit transfer, \"30\" credit transfer, \"59\" SEPA direct debit, \"48\" card, \"57\" standing order, \"97\" clearing between partners. For a credit transfer also set payment.iban.",
  "example": "\"payment\": { \"meansCode\": \"58\", \"iban\": \"DE02120300000000202051\", \"accountName\": \"Acme GmbH\" }",
  "xpath": "/ubl:Invoice/cac:PaymentMeans",
  "docsUrl": "https://attestwire.com/rules/BR-DE-1"
}

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", "accountName": "Acme GmbH" }

The fix

Set payment.meansCode to a UNTDID 4461 code: "58" SEPA credit transfer, "30" credit transfer, "59" SEPA direct debit, "48" card, "57" standing order, "97" clearing between partners. For a credit transfer also set payment.iban.

All 58 rules →

Nearby: BR-DE-2 — XRechnung requires the seller contact group (BG-6), and requires it complete: contact point (BT-41), telephone number (BT-42) and email address (BT-43) are each individually mandatory under BR-DE-5, BR-DE-6 and BR-DE-7; BR-CO-26 — In order for the buyer to automatically identify you, the invoice must carry at least one of the seller identifier (BT-29), seller legal registration identifier (BT-30) or seller VAT identifier (BT-31); BR-DE-3 — XRechnung requires the element "Seller city" (BT-37).

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.