The UBL does not provide an explicit syntax for

1. Delivery Note Document Reference

2. Delivery Note Document Line Reference

Which is likely to become part of the core of the European e-invoice norm EN16931.

In [Code List 1001](https://service.unece.org/trade/untdid/d24a/tred/tred1001.htm), the following two codes are mentioned, which are synonyms used in the EN16931-1 core invoice:

• *270 Delivery note*
  Paper document attached to a consignment informing the
  receiving party about contents of this consignment.

• *351 Despatch advice*
  Document/message by means of which the seller or
  consignor informs the consignee about the despatch of
  goods.

A representative of the German automotive industry stated, the following cardinalities occur for the above documents:

• *270: Delivery note* has a cardinality of *1..n*
• *351: Despatch advice* has a cardinality of *0..1*

Note: The following was translated automatically from German and will be double-checked in the future to ensure the right terminology was used - I suspect Consignment should be used.

• 1 transport (loading list) contains 1..n shipments (each shipment has a DESADV if EDI is implemented).
• 1 shipment has 1..n delivery notes, and 1 delivery note can have 1..n line items.

For example, if a shipment contains 5 different part numbers, we may find — depending on the ERP system — either 1 delivery note with 5 line items, or 5 delivery notes each with one line item.
Also, the *Delivery note* is usually taken to match the invoice.

While there were motions that instead of the *Delivery note, the **Despatch advice* should be taken for BT-198, and extension might require the correct differentiation of both, therefore, clean semantics are a base requirement for the core.