Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| Series ref. BR-47 | Fatal (error) | cac:BillingReference |
Schematron ID: ibr-055 | Field: cac:InvoiceDocumentReference/cbc:ID (Preceding Invoice reference, IBT-025) |
||
Classification
Contextual — the rule fires only when a Preceding Invoice reference group (IBG-03) is present. In UAE practice that group appears in two situations that matter: credit notes, and final invoices that follow an advance payment invoice.
What the Rule Is Checking
Wherever a cac:BillingReference block exists, it must contain a cac:InvoiceDocumentReference/cbc:ID — the identifier of the preceding invoice being referred to. The block cannot stand empty. A BillingReference that carries an issue date, or nothing at all, without the preceding invoice's ID fails validation.
Why This Rule Exists
The Preceding Invoice reference is the thread that ties correction and continuation documents back to the original transaction. A credit note that cannot name the invoice it corrects is unauditable: the recipient cannot match it, and neither party can demonstrate which original tax amount is being adjusted. The UAE jurisdiction layer leans on this structure directly — aligned rule ibr-055-ae makes the Preceding invoice reference group mandatory when the invoice type code (IBT-003) is 381 or 81, with an exception only where the credit note reason code is 'VD'. The base rule covered here guarantees that whenever the group is used, it carries the identifier that gives it meaning.
UAE Data Example
PASSES ✓: A final invoice following an advance carries <cac:BillingReference><cac:InvoiceDocumentReference><cbc:ID>ADV-001</cbc:ID><cbc:IssueDate>2026-05-01</cbc:IssueDate></cac:InvoiceDocumentReference></cac:BillingReference> — the exact structure the Guidelines V1.1 Appendix 5 advance-payment example uses.
FAILS ✗: A credit note's BillingReference block is generated by the ERP as an empty container because the reference document number was never captured when the credit was raised — the block exists, the ID inside it does not.
What Your ERP / IT Team Must Ensure
Make the original invoice number a mandatory capture field in every credit note and rebate workflow, enforced at entry rather than at transmission. Verify the e-invoicing extract omits the BillingReference block entirely when no reference exists, instead of emitting an empty one. Test the advance-payment flow described in Appendix 5 of the Guidelines V1.1 end to end, since the final-balance invoice is the scenario where a reference is expected but the billing document sits in a different document chain from a standard credit memo.
Related Rules
ibr-055-ae (UAE aligned layer) makes the Preceding invoice reference group mandatory for credit notes except reason code 'VD'. See also the Appendix 5 advance payments post, Advance Payments and Retention Under UAE E-Invoicing, for the business scenario that exercises this structure on invoices rather than credit notes.