The payment instructions are missing
An XRechnung invoice must carry the `PAYMENT INSTRUCTIONS` group (BG-16), so at minimum the payment means type code (BT-81).
Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.
The message your validator prints
Copied verbatim from the sealed artefact: this is the exact sentence the check prints when this rule fails.
[BR-DE-1] Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16) enthalten.
Quoted from schematron-xrechnung 3.0.2, licensed under Apache-2.0.
Common searches around this code
These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.
Test your file with this error in mind
Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.
To automate this check in an ERP flow, call the validation API and link every returned code to its public page.
Why this error happens
EN 16931 leaves this group optional; the German CIUS requires it. A generator tuned for another country therefore produces XML that is perfectly valid in European terms and refused by a German recipient. It is the most common gap on a first move to XRechnung, because it comes from an extra requirement rather than from a mistake.
How to fix it
Fill the payment means in from your invoicing system. Factlint writes no payment details, not even partial ones: it is a financial field, and the policy refuses it whatever is asked (rule 1).
XML correction example
<!-- ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans absent -->
<ram:SpecifiedTradeSettlementPaymentMeans><ram:TypeCode>58</ram:TypeCode>