ATW-CREDIT-NOTE-PROJECT-REFERENCE-UNBOUND — E-Invoice Validation Rule & Fix

Fixture ID: creditNoteProjectReference · XPath: /ubl:CreditNote

1. Why This Rule Triggers (Diagnostic Message)

This credit note states a project reference (BT-11 = "PRJ-ERECHNUNG-2026"), and a UBL CreditNote cannot carry one. cac:ProjectReference is not in UBL-CreditNote-2.1.xsd at all — it exists on Invoice and on nothing else — so the reference will be **absent from the generated UBL document**. This is a hole in the syntax rather than in this library or in EN 16931: the CII binding has ram:SpecifiedProcuringProject and keeps it, so generateCii on this same input loses nothing.

2. How to Fix ATW-CREDIT-NOTE-PROJECT-REFERENCE-UNBOUND

Drop projectReference, or move the project identifier somewhere the document can hold it: buyerAccountingReference (BT-19, the buyer's cost centre) is the usual home, and contractReference (BT-12) or invoicedObjectIdentifier (BT-18) fit some processes better. If the project reference is load-bearing for your buyer, emit the credit note as CII instead — profile "xrechnung-cii" keeps it.

3. Valid Code / Payload Example

"buyerAccountingReference": "PRJ-ERECHNUNG-2026"