Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| Series ref. BR-92 | Fatal (error) | cac:Delivery |
| Schematron ID: ibr-108 | Field: ibt-070 — Deliver to party name | ||
Classification
Transaction Data — the deliver-to party is usually copied from a sales order or despatch note, and duplication here reflects how those documents were merged.
What the Rule Is Checking
Within the delivery group, cac:DeliveryParty/cac:PartyName/cbc:Name may occur at most once. The deliver-to party is the entity that physically receives the goods or services, which is frequently not the buyer named on the invoice — a site, a branch, a customer's customer under a drop-ship arrangement, a bonded warehouse operator.
Why This Rule Exists
The recipient of a supply is evidence. Where a UAE supplier zero-rates an export, or applies the place-of-supply rules to a cross-emirate delivery, the deliver-to party is part of what supports that treatment. A field carrying two names does not support anything — it raises the question of which entity actually took receipt.
The common cause is well worth naming: teams use the second name element as a free-text carrier for a site reference, a store code or a contact person, because the address block feels too rigid. UBL provides deliver-to location identifier (ibt-071) and the address lines for exactly that. Overloading the party name field pushes operational detail into a field that a receiving system reads as a legal identity.
UAE Data Example
PASSES ✓ — a branch receiving delivery, with the site reference in the field designed for it:
<cac:Delivery>
<cac:DeliveryLocation>
<cbc:ID schemeID="0088">6291041500213</cbc:ID>
</cac:DeliveryLocation>
<cac:DeliveryParty>
<cac:PartyName><cbc:Name>Al Manara Retail LLC – Sharjah Warehouse</cbc:Name></cac:PartyName>
</cac:DeliveryParty>
</cac:Delivery>FAILS ✗ — the receiving entity and the site handled as two name elements:
<cac:PartyName><cbc:Name>Al Manara Retail LLC</cbc:Name></cac:PartyName>
<cac:PartyName><cbc:Name>Sharjah Warehouse – Gate 3</cbc:Name></cac:PartyName>What Your ERP / IT Team Must Ensure
- Concatenate entity and site into one name string at the mapping layer if both are needed for the buyer to route the goods, rather than emitting two elements.
- Move location codes into the deliver-to location identifier (ibt-071), which is scheme-qualified and machine-readable, and route contact details to the delivery contact fields.
- Audit ship-to master records where the name is stored across two or three lines — that storage pattern is what produces repeated name elements in the output.
- For export and e-commerce transactions, confirm the deliver-to party and the address fields required by ibr-152-ae and ibr-142-ae describe the same recipient, since these are the documents most likely to be examined.
Related Rules
ibr-107 permits only one delivery group per document, which is the container this rule operates inside. ibr-057 requires a country code on every deliver-to address. ibr-sr-56 caps the delivery postal address line at one occurrence. ibr-073 governs the format of the actual delivery date (ibt-072) in the same group.