UBL Despatch Advice: repair an order line reference

Find the missing link to the order

Goods receipt often needs more than a product identifier. The receiving ERP must know which purchase order and which order line the despatch line relates to. Our independent preflight requires a nonempty LineID in each supplied OrderLineReference. It also needs an unambiguous order ID, either in that reference’s OrderReference or in one document-level OrderReference. This is a practical matching preflight; it does not establish the full official profile.

The fictional reference error leaves LineID blank at line 17. DESPATCH-ORDER-LINE identifies /p:DespatchAdvice[1]/p:DespatchLine[1]/p:OrderLineReference[1]. Correct the generator to carry the receiving order’s intended line identifier. The despatch line’s own ID is a separate identifier and should not be substituted automatically. In the positive fictional example both values happen to be one, but real exports can number these lines differently.

Resolve multiple orders deliberately

One header order reference can provide context for a line that does not repeat the order number. With several header orders, a bare line number is ambiguous because different orders can each have a line one. In that case provide the explicit order reference under the line reference. When a line declares an order that is absent from a supplied header list, the tool reports DESPATCH-ORDER-MISMATCH for review and correction. An empty reference ID is also rejected.

Several references on one despatch line may represent a workflow this partial tool cannot allocate. The references are inspected for nonempty identifiers, but remaining-quantity arithmetic is skipped. Repeated references across despatch lines likewise prevent a naive subtraction of each delivered quantity from the same original balance. Use a complete integration-specific reconciliation to distribute those amounts rather than treating an unexecuted comparison as a successful match.

Separate references from profile identifiers

OrderReference and LineID identify business documents and lines. ProfileID identifies the intended exchange process; CustomizationID identifies the transaction specification. This validator has separate diagnostics for the selected BIS Despatch Advice 3.1 process and transaction values. Correct order references do not repair an unknown profile, and changing a profile identifier does not identify the purchase order.

The factual process value is urn:fdc:peppol.eu:poacc:bis:despatch_advice:3. The transaction value is urn:fdc:peppol.eu:poacc:trns:despatch_advice:3. These values were checked in the primary publication on 6 November 2026. A custom or unknown profile stays unverified, even when all independent matching checks pass. The UBL document name is DespatchAdvice; DispatchAdvice is a different spelling and is rejected as the wrong root.

Trace the mapping through your ERP

1. Find the order number and source order-line identifier expected by the receiving system.
2. Check whether the exporter uses header context or explicit line-level order references.
3. Export a fresh fictional test shipment after correcting the mapping.
4. Recheck references before comparing remaining quantities with complete history.

For several files, existing Pro and Team batch limits apply with separate outcomes for broken documents. JSON and CSV reports retain source paths, line numbers, rule version, selected profile and execution scope. A report is an aid to repair; it cannot confirm that a receiving warehouse matched or accepted the announced goods.

Where the reference structure is defined

The official OASIS DespatchAdvice XSD imports common UBL components for order and line references. The UBL 2.1 publication explains this schema architecture. The current BIS Despatch Advice 3.1 documentation provides the process context and identifier values. These primary sources were reviewed again on 6 November 2026; no protected publication or Schematron text is reproduced in this guide.

The full schema chain includes separately originating signature components. This release has no established distribution grant for the ETSI imports, so it publishes independent checks rather than a full official pack. An authorised complete local package can be supplied with per-file provenance, notices and concrete rights. The local rule adapter accepts only self-contained XPath 1.0 assertions and leaves unsupported packages unexecuted. Neither that adapter nor a reference match proves complete BIS conformity or a Peppol network connection.