EN 17017-1:2025

Electronic Public Procurement - Fulfilment - Part 1: Choreographies

This choreographies document describes the exchange of information in the Fulfilment phase between seller and buyer where the seller wants to announce delivery of the ordered goods or services. The purpose of the fulfilment it is to monitor the executions of the contract. This process is the process between the ordering process and the billing process. The billing process can start when fulfilment has been initiated. The business value for this is:
—   To prepare the buyers organization for the physical delivery;
—   To enabling an automatic check of delivery for the buying organization before paying the received invoice;
—   To match the ordered products with the physical deliveries, such as serial numbers, lot identifiers and other information that might not be present at the time the goods were ordered;
—   The assist in getting an accurate calculation of the environmental footprint of the goods by including the emission during the transport;
—   To feed data into the logistic process, so no retyping is needed during the transport of the goods.
The identifier of this set of choreographies is EN 17017-1:2025
How to claim conformance to a choreography variant defined in this document is described in 4.2.3.

Elektronisches öffentliches Beschaffungswesen - Erfüllung - Teil 1: Choreographien

Dieses Choreographiendokument beschreibt den Austausch von Informationen in der Erfüllungsphase zwischen Verkäufer und Käufer, in der der Verkäufer die Lieferung der bestellten Waren oder Dienstleistungen ankündigen will. Der Zweck der Erfüllungsphase ist es, die Ausführung des Vertrags zu überwachen. Dieser Prozess ist der Prozess zwischen dem Bestellprozess und dem Abrechnungsprozess. Der Abrechnungsprozess kann beginnen, wenn der Erfüllungsprozess eingeleitet wurde. Der geschäftliche Nutzen besteht in:
-   der Vorbereitung der Käuferorganisation auf die physische Lieferung;
-   der Ermöglichung einer automatischen Überprüfung der Lieferung für die einkaufende Organisation vor der Bezahlung der erhaltenen Rechnung;
-   der Abgleichung der bestellten Produkte mit den physischen Lieferungen, z. B. Seriennummern, Loskennungen und anderen Informationen, die zum Zeitpunkt der Bestellung der Waren möglicherweise nicht vorhanden waren;
-   der Unterstützung bei der genauen Berechnung des ökologischen Fußabdrucks der Waren durch Emissionen während des Transports;
-   der Einspeisung der Daten in den logistischen Prozess, so dass während des Transports der Waren keine erneute Eingabe erforderlich ist.
Der Identifikator dieser Choreographienreihe ist EN 17017 1:2025.
Wie die Conformance mit einer in diesem Dokument definierten Variante der Choreographie beansprucht wird, ist in 4.2.3 beschrieben.

Passation électronique des marchés publics - Exécution - Partie 1 : Chorégraphies

Le présent document sur les chorégraphies décrit l'échange d'informations dans la phase d'exécution entre le vendeur et l'acheteur lorsque le vendeur souhaite annoncer la livraison des biens ou des services commandés. L'objectif de l'exécution est de contrôler la réalisation dans le cadre du contrat. Cette procédure intervient entre les procédures de commande et de facturation. La facturation peut démarrer dès le lancement de l'exécution. La valeur métier correspondante est la suivante :
—   préparer l'organisation de l'acheteur en vue de la livraison effective ;
—   permettre un contrôle automatique de la livraison auprès de l'organisation acheteuse avant d'acquitter la facture reçue ;
—   comparer les produits commandés et les livraisons effectives, tels que les numéros de série, l'identification des lots et d'autres informations susceptibles de ne pas être disponibles au moment de la commande des marchandises ;
—   inclure les émissions induites par le transport pour permettre l'obtention d'un calcul précis de l'empreinte environnementale des marchandises ;
—   intégrer des données dans le processus logistique, afin d'éviter d'avoir à ressaisir les informations lors du transport des marchandises.
Cet ensemble de chorégraphies est identifié dans l'EN 17017-1:2025.
La manière de revendiquer la conformité à une variante de chorégraphie définie dans le présent document est décrite en 4.2.3.

Elektronska javna naročila - Izpolnitev - 1. del: Koreografije

Ta dokument o koreografijah opisuje izmenjavo informacij v fazi izpolnitve med prodajalcem in kupcem, pri čemer želi prodajalec naznaniti dobavo naročenega blaga ali storitev. Namen izpolnitve je spremljanje izvrševanja pogodbe. Gre za postopek med postopkom naročanja in postopkom zaračunavanja. Postopek zaračunavanja se lahko začne, ko se prične izpolnitev. Poslovna vrednost tega postopka: – priprava organizacije kupca na fizično dobavo; – omogočanje samodejnega preverjanja dobave za organizacijo kupca pred plačilom prejetega računa; – usklajevanje naročenih izdelkov s fizičnimi dobavami, kot so serijske številke, identifikatorji serij in druge informacije, ki morda niso bile prisotne v času naročila blaga; – pomoč pri natančnem izračunu okoljskega odtisa blaga z vključitvijo emisij med prevozom; – vnos podatkov v logistični proces, da med prevozom blaga ni potrebno ponovno vnašanje. Ta sklop koreografij je opredeljen v standardu EN 17017-1:2025. Dokazovanje skladnosti z različico koreografije, opredeljeno v tem dokumentu, je opisano v točki 4.2.3.

General Information

• Status: Published
• Publication Date: 19-Aug-2025
• ICS: 35.240.63 - IT applications in trade
• Technical Committee: CEN/TC 440 - Project Committee - Electronic Public Procurement
• Drafting Committee: CEN/TC 440/WG 7 - e-Fulfillment
• Current Stage: 6060 - Definitive text made available (DAV) - Publishing
• Start Date: 20-Aug-2025
• Due Date: 21-Apr-2025
• Completion Date: 20-Aug-2025
• Ref Project: SIST EN 17017-1:2025 - Electronic Public Procurement - Fulfilment - Part 1: Choreographies

Overview

EN 17017-1:2025 - Electronic Public Procurement: Fulfilment, Part 1 (Choreographies) is a CEN standard that defines the information exchanges (choreographies) occurring in the fulfilment phase between buyer and seller after an order has been placed. Its purpose is to monitor contract execution and bridge the ordering and billing processes. The standard supports automation of delivery announcements, delivery verification, and logistical data exchange to reduce manual re‑entry and improve procurement transparency.

Key topics and technical requirements

• Choreographies and business goals: Defines the set of business processes (choreographies) with shared goals for fulfilment and monitoring contract execution.
• Business process variants: Specifies multiple fulfilment variants (documented as variants A, B and C in the standard), including:
  • Variant A - Despatch only
  • Variant B - Advanced fulfilment
  • Variant C - Receipt advice only These variants address different collaboration and messaging patterns between buyer and seller.
• State machines and business rules: Includes state diagrams and rules to model transitions during fulfilment (informative diagrams and example scenarios are provided).
• Transactions and messages: Identifies the transactions involved (e.g., send despatch advice, send receipt advice) and references EN 17017-2 for transaction-level definitions and syntax bindings.
• Conformance: Instructions on how to claim conformance to a choreography variant are provided (see clause 4.2.3).
• Derivative use: The document participates in a CEN derivative‑use pilot; specified subclauses may be reused in implementations under defined conditions.

Practical applications and users

Who will use EN 17017-1:2025:

• Public authorities and procurement teams implementing automated eProcurement workflows to coordinate deliveries, inspections and billing.
• Software vendors and integrators building eProcurement, ERP and logistics solutions that need standardized fulfilment choreographies.
• Logistics and supply chain operators that require structured transport and tracking data to feed into delivery processes.
• Auditors and compliance teams verifying that fulfilment messaging supports invoice reconciliation and environmental reporting.

Key practical benefits:

• Prepares buyer organizations for physical delivery and reduces surprises at receipt.
• Enables automated delivery checks before invoice payment.
• Supports matching ordered items with delivered goods (serial numbers, lot identifiers).
• Improves environmental footprint calculations by including transport emissions.
• Reduces manual retyping across procurement and logistics systems.

Related standards

• EN 17017-2:2025 - Electronic Public Procurement - Fulfilment - Part 2: Transactions (transaction definitions and syntax bindings)
• Other CEN/TC 440 series documents on eProcurement architecture, ordering and catalogues (see CEN TC 440).

Keywords: EN 17017-1:2025, electronic public procurement, eProcurement, fulfilment, choreographies, despatch advice, receipt advice, business process variants, CEN, public procurement standards.

Standards Content (Sample)

SLOVENSKI STANDARD
01-november-2025
Elektronska javna naročila - Izpolnitev - 1. del: Koreografije
Electronic Public Procurement - Fulfilment - Part 1: Choreographies
Elektronisches öffentliches Beschaffungswesen - Erfüllung - Teil 1: Choreographien
Passation électronique des marchés publics - Exécution - Partie 1 : Chorégraphies
Ta slovenski standard je istoveten z: EN 17017-1:2025
ICS:
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 17017-1
EUROPEAN STANDARD
NORME EUROPÉENNE
August 2025
EUROPÄISCHE NORM
ICS 35.240.63
English Version
Electronic Public Procurement - Fulfilment - Part 1:
Choreographies
Passation électronique des marchés publics - Exécution Elektronisches öffentliches Beschaffungswesen -
- Partie 1 : Chorégraphies Erfüllung - Teil 1: Choreographien
This European Standard was approved by CEN on 2 June 2025.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2025 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 17017-1:2025 E
worldwide for CEN national Members.

Contents Page
European foreword . 4
Introduction . 5
1 Scope . 6
2 Normative references . 6
3 Terms and definitions . 6
4 Business Environment and high-level business requirements . 8
4.1 Choreography (business) Goals . 8
4.2 Business environment . 8
4.2.1 Introduction . 8
4.2.2 Business context . 9
4.2.3 Positioning in EIRA . 9
4.3 Organization and business partners involved . 10
4.4 High Level Business process requirements . 11
4.4.1 High level business requirements . 11
5 Processes . 12
5.1 Introduction . 12
5.2 Business process variants. 13
5.2.1 Introduction . 13
5.2.2 High level business process variants requirements . 13
5.2.3 Claiming compliance . 13
5.3 Business process variant A — Despatch only . 14
5.3.1 Business process variant A requirements . 14
5.3.2 Despatch only state machine diagram [Informative] . 14
5.3.3 Business process variant A Despatch Only . 14
5.3.4 Business Process variant A - Delivery with despatch only . 15
5.3.5 Business process variant A business rules . 15
5.3.6 Business process variant A key examples [Informative] . 16
5.4 Business process variant B — Advanced fulfilment . 17
5.4.1 Business process variant B requirements . 17
5.4.2 Business process variant B state machine diagram [Informative] . 18
5.4.3 Business process variant B definition . 18
5.4.4 Business process variant B Scenario . 19
5.4.5 Business process variant B business rules . 20
5.4.6 Business process variant B key examples . 20
5.5 Business process variant C — Receipt advice only . 21
5.5.1 Business process variant C requirements . 21
5.5.2 Receipt advice only state machine diagram [Informative] . 21
5.5.3 Business process variant C definition . 21
5.5.4 Business process variant C Scenario . 22
5.5.5 Business process variant C business rules . 22
5.5.6 Business process variant C key examples . 22
6 CEN TC 440 Transactions involved . 23
6.1 Summary . 23
6.2 Basic collaborations . 24
6.3 Send Despatch advice . 24
6.4 Send Receipt Advice . 25
Annex A (informative) Overview of the clauses and subclauses that fall under derivative
use . 27
Bibliography . 28

European foreword
This document (EN 17017-1:2025) has been prepared by Technical Committee CEN/TC 440 “Electronic
Public Procurement”, the secretariat of which is held by DIN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by February 2026, and conflicting national standards
shall be withdrawn at the latest by February 2026.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through decision 37/2019). For more information about the implementation of
derivative use in CEN/TC 440, see: https://www.cencenelec.eu/areas-of-work/cen-
cenelectopics/public-procurement/cen-tc-440-electronic-public-procurement/.
This document is part of a series of multi-part documents prepared, or under preparation, by CEN/TC
440:
— 17011-series: eProcurement Architecture, providing a set of specifications outlining different
aspects of the eProcurement architecture for Business Interoperability Specifications.
— 17015-series: eCatalogue Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the catalogue process.
— 17016-series: eOrdering Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the ordering process.
— 17017-series: eFulfilment Business Interoperability Specifications, providing a set of specifications
outlining business choreography, transaction, syntax binding specifications and guidelines required
to support the fulfilmet process.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the
United Kingdom.
Introduction
Derivative use pilot
This publication falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through decision 38/2019).
CEN has the copyright to all CEN publications, including their entire content and associated metadata,
as described in CEN-CENELEC Guide 10 “Policy on dissemination, sales and copyright of CEN-CENELEC
Publications”. However, through the derivative use pilot, CEN gives permission to the copying,
replication and translation of content from a CEN/TC 440 deliverables in specific circumstances.
Under the derivative use pilot, specific sections of CEN/TC 440 publications may be copied, replicated
and translated in cases, where this is a necessary condition for the meaningful implementation of the
publication. The sections which fall under derivative use will typically be elements, such as semantic
definitions and rules related to the use of information elements, and the name, definition and
description of processes and transactions, which are needed in software solutions, whether intended
for sale in the private market or for use in the public sector, and documents guiding the implementation
and use in specific countries and/or business sectors.
Under derivative use, any use of content, which has been copied, replicated, or translated from a
CEN/TC 440 publication, should comply with the intended use of the publication. Derivative use cannot
be applied in use cases other than those the publication is intended to support. The intended use of this
publication is set out below.
Intended use of this publication:
This document has been developed for any organization looking for guidance on the implementation
and use of electronic procurement deliverables as well as for organizations developing or implementing
software applications related to electronic procurement, such as software providers, business entities
and national authorities. These software applications should be in conformance with this publication.
Parts of the document to which derivative use apply:
Each subclause, which falls under derivative use, will be clearly marked with a note. The degree to
which the specific content can be modified, is defined in CEN/TS 17011-3 Electronic Public Procurement
– Architecture – Part 3: Customization Guideline.
Annex A provides an overview of the line number references to all subclauses of the publication which
fall under derivative use.
1 Scope
This choreographies document describes the exchange of information in the Fulfilment phase between
seller and buyer where the seller wants to announce delivery of the ordered goods or services. The
purpose of the fulfilment it is to monitor the executions of the contract. This process is the process
between the ordering process and the billing process. The billing process can start when fulfilment has
been initiated. The business value for this is:
— To prepare the buyers organization for the physical delivery;
— To enabling an automatic check of delivery for the buying organization before paying the received
invoice;
— To match the ordered products with the physical deliveries, such as serial numbers, lot identifiers
and other information that might not be present at the time the goods were ordered;
— The assist in getting an accurate calculation of the environmental footprint of the goods by
including the emission during the transport;
— To feed data into the logistic process, so no retyping is needed during the transport of the goods.
The identifier of this set of choreographies is EN 17017-1:2025
How to claim conformance to a choreography variant defined in this document is described in 4.2.3.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 17017-2 , Electronic Public Procurement — Fulfilment — Part 2: Transactions
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https://www.iso.org/obp/
— IEC Electropedia: available at https://www.electropedia.org/
3.1
agent
person, organization, or system that act in procurement or have the power to act in procurement
[SOURCE: eProcurement Ontology]
3.2
business process
sequence or network of activities and Collaborations between two or more agents

Under preparation. Stage at the time of publication: prEN 17017-2:2025
3.3
business process variant
specification of a Business Process belonging to a Choreography
Note 1 to entry: Different variants may support different electronic information exchange or collaborations.
Agents may publicly advertise their capability to support one or more variants in an automated fashion.
3.4
choreography
set of Business Processes having the same goals
3.5
collaboration
interaction between two or more agents that result in the exchange of data between the agents involved
as part of a business process
3.6
role
part played by an agent in a particular business process, including its responsibilities (options and
obligations) to perform certain activities and collaborations in that business process
Note 1 to entry: The role is used to show the division of labour and responsibility amongst the agents involved in
the process or within the organization of an Agent.
[SOURCE: eProcurement Ontology]
3.7
state
set of options and obligations of the participating agents at a defined step in a business process to
perform specific activities and collaborations
Note 1 to entry: An activity of an agent or a collaboration may cause the transition of one state to another in a
predefined set of next steps.
3.8
transaction
content of data exchanged or shared between the agents in a collaboration
Note 1 to entry: A transaction is the atomic unit that leads to a synchronized state in the information systems of
collaborating agents. It is the basic building block to define the choreography between agents. When an agent
recognizes an event that changes the state of a business object within a business process, it uses a transaction to
synchronize with the collaborating agent. A transaction therefore changes the state of a business process. It
carries the intention of the initiating agent and is represented by a data structure that is defined by a data model.
The exchange of a transaction may alter legal obligations between business partners.
3.9
despatch advice
message which enables a consignor to provide information about the content of a shipment to a
receiver
3.10
receipt advice
message which enables the consignee to inform the consignor about status of received goods or
services
4 Business Environment and high-level business requirements
4.1 Choreography (business) Goals
The business goals supported by implementing this choreography are:
Table 1 — Business goals
ID Description
Enable trading partners to communicate without a previous bi-lateral
G-17017-1:2025-1
setup or agreement. Be the basis of an EDI agreement.
G-17017-1:2025-2 To prepare the buyers organization for the physical delivery
Enable an automatic check of delivery for the buying organization before
G-17017-1:2025-3
paying the received invoice
To match the ordered products with the physical deliveries, such as serial
G-17017-1:2025-4 numbers, lot identifiers and other information that may not be present at
the time the goods were ordered.
To assist in getting an accurate calculation of the environmental footprint
G-17017-1:2025-5
of the goods by including the emission during the transport.
G-17017-1:2025-6 To cater sufficient information to initiate the logistics process.
To assist in tracking of goods, e.g. by providing the lot ID and other
G-17017-1:2025-7
relevant information.
The main business benefits to be gained by implementing this choreography are:
Table 2 — Main business benefits
ID Description
Realize significant savings both by customers and suppliers through
G-17017-1-1:2025-8 automating and streamlining in-house processes of managing the delivery
of goods or services.
To support a faster delivery process by connecting the procurement
process into the logistics process and by that enable just in time supply
G-17017-1-2:2025-9
chain management. Having the flow of information digitized is a
prerequisite for a fully automated supply chain.
4.2 Business environment
4.2.1 Introduction
The intended scope for these choreographies includes public procurement, but the choreography may
also be used in Business to Business (B2B) relations. The choreographies are intended to support
transmission of electronic documents for processing in (semi-) automated processes. The legal
requirements that were taken into account are requirements from European legislation, particularly the
EU directives, as mentioned in the bibliography section of this document. The list of the transactions
being part of this choreography is defined in Clause 4.5.4.
4.2.2 Business context
The choreographies specified in this document belong to the pre- and post-award area as shown in
Figure 1:
Figure 1 — Position of the Fulfilment Choreography in the e-Procurement process
4.2.3 Positioning in EIRA
EIRA provides a reference model that enables architects to position the IOP specifications. This
document provides a domain-specific IOP specification to which any SBB implementing the ABB should
be compliant to. The positioning of this document in the EIRA context is described in Table 3.
IoP specifications provide a valuable source of information to formulate requirements during
architecture development and solution development. By identifying architectural building blocks
through a common terminology, it:
— helps reuse of cross domain building blocks such for instance e-Signature Verification and
Validation Service, and e-Timestamp Creation Service;
— helps synchronisation and alignment with large scale pilots such as eSense, or European solution
such as CEF eDelivery;
— and will provide guidance in using them to provide the prescribed capability enabling, thus
managing and rationalizing IT portfolios.
Table 3 — Position in EIRA
EIRA ID Title Domain Interface Scope Modality
FprEN 17017:2025-1: Electronic Public Procurement Machine ·e-procurement Endorsing
2022 Procurement — /Customer extension of
Fulfilment — ABB176
Machine
Choreograhies Organisational
/Supplier
Interoperability
Specification
·e-procurement
extension of ABB12
Business
Capability,
·e-procurement
extension of
ABB170 Exchange
of Business
Information
4.3 Organization and business partners involved
The following business partners participate in this BII Choreography, acting in the roles as defined in
Table 4 and Figure 2 below.
Table 4 — Roles
Key Role Description
A role of an agent that awards a contract and/or purchases goods and
Buyer Party
services.
A role of an agent legally responsible for providing goods and services
Seller Party
bought by a Buyer.
A role of an agent responsible for delivering the purchased goods or
Consignor
services on behalf of the seller. The role is also known as Despatch Party.
A role of an agent responsible for receiving the purchased goods or
Consignee
services. The role is also known as Delivery Party.

Figure 2 — Roles involved in the Fulfilment use case
4.4 High Level Business process requirements
4.4.1 High level business requirements
Based on the goals and scope of this choreography the following set of high-level requirements is
identified. Each requirement is connected to a goal.
Additionally, requirements of major business processes that are frequently supported within fulfilment
are listed.
These requirements are relevant for all variants depicted within this choreography and described in
Table 5.
Table 5 — High level business requirements
Req. ID Requirement statement Ref. to goal
A despatch party (seller) submits a despatch
advice to a Consignee (Buyer) to tell them that
HLR-17017-1:2025-1 G-17017-1:2025-1
the goods are about to be delivered or that
service has been received.
When a seller submits a despatch advice
regarding service, this acts as a proof of delivery,
HLR-17017-1:2025-2 G-17017-1:2025-3
so the invoice can be issued to the customer for
the service.
A buyer can issue a receipt advice to the seller to
HLR-17017-1:2025-3 G-17017-1:2025-4
state what has been received.
For despatch advice and receipt advice, the
listed items in each document refer to the order
HLR-17017-1:2025-4 G-17017-1:2025-4
lines and states what is sent respectively being
received.
A receipt advice send by the Delivery Party can
G-17017-1:2025-3
HLR-17017-1:2025-5 act as a response to a despatch advice and state
G-17017-1:2025-4
missing or damage goods in the despatch advice.
A despatch advice can tell how the ordered items
are shipped by referring ids of the shipment,
HLR-17017-1:2025-6 G-17017-1:2025-2
consignments and the physical packaging, e.g.
container numbers, seals and packing labels.
A despatch advice and a receipt advice can
HLR-17017-1:2025-7 contain information about the physical instances G-17017-1:2025-4
of the items being delivered.
A Despatch advice can point to a previous
HLR-17017-1:2025-8 G-17017-1:2025-4
delivery.
A Delivery Party can decline a delivery if it is not
HLR-17017-1:2025-9 G-17017-1:2025-1
delivered in the right sequence as specified.
Structured Fulfilment: The despatch transaction
HLR-17017-1:2025-10 should support multiple deliveries for a single G-17017-1:2025-4
order.
A despatch advice or a receipt advice may
HLR-17017-1:2025-11 G-17017-1:2025-2
support
...