ATW-CREDIT-NOTE-DUE-DATE-UNBOUND — E-Invoice Validation Rule & Fix

Fixture ID: creditNoteDueDateUnbound · XPath: /ubl:CreditNote/cac:PaymentMeans/cbc:PaymentDueDate

1. Why This Rule Triggers (Diagnostic Message)

This credit note states a payment due date (BT-9 = "2026-09-08") and no payment instructions (BG-16). A UBL CreditNote has no cbc:DueDate element: EN 16931 binds BT-9 to cac:PaymentMeans/cbc:PaymentDueDate on that document, and UBL's PaymentMeans requires a payment means code (BT-81), so without BG-16 there is no lawful element to carry the date. It will be **absent from the generated UBL document**. In CII the same input is unaffected — BT-9 has its own element there — so this finding is about the UBL binding, not about your data.

2. How to Fix ATW-CREDIT-NOTE-DUE-DATE-UNBOUND

Supply payment instructions: `payment: { meansCode: "58", iban: "…" }` for a SEPA credit transfer, or "1" if the code is genuinely unknown. XRechnung requires BG-16 anyway under BR-DE-1, so a document that hits this finding is usually one field short of two rules at once. If the credit note is settled by netting rather than by payment, drop dueDate — a date nobody will pay on is worse than no date.

3. Valid Code / Payload Example

"dueDate": "2026-09-08", "payment": { "meansCode": "58", "iban": "DE02120300000000202051" }