ISO 5909

FINAL DRAFT
International
Standard
ISO/FDIS 5909
ISO/TC 154
Business processes and data
Secretariat: SAC
interchange of electronic bill of
Voting begins on:
lading based on distributed ledger
2025-10-15
technology (DLT)
Voting terminates on:
2025-12-10
Processus dans le commerce, l'industrie et l'administration et
échange des données des connaissements électroniques basés sur
la technologie des registres partagés (DLT)
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
Reference number
ISO/FDIS 5909:2025(en) © ISO 2025

FINAL DRAFT
ISO/FDIS 5909:2025(en)
International
Standard
ISO/FDIS 5909
ISO/TC 154
Business processes and data
Secretariat: SAC
interchange of electronic bill of
Voting begins on:
lading based on distributed ledger
technology (DLT)
Voting terminates on:
Processus dans le commerce, l'industrie et l'administration et
échange des données des connaissements électroniques basés sur
la technologie des registres partagés (DLT)
RECIPIENTS OF THIS DRAFT ARE INVITED TO SUBMIT,
WITH THEIR COMMENTS, NOTIFICATION OF ANY
RELEVANT PATENT RIGHTS OF WHICH THEY ARE AWARE
AND TO PROVIDE SUPPOR TING DOCUMENTATION.
© ISO 2025
IN ADDITION TO THEIR EVALUATION AS
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
BEING ACCEPTABLE FOR INDUSTRIAL, TECHNO­
LOGICAL, COMMERCIAL AND USER PURPOSES, DRAFT
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
INTERNATIONAL STANDARDS MAY ON OCCASION HAVE
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
TO BE CONSIDERED IN THE LIGHT OF THEIR POTENTIAL
or ISO’s member body in the country of the requester.
TO BECOME STAN DARDS TO WHICH REFERENCE MAY BE
MADE IN NATIONAL REGULATIONS.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland Reference number
ISO/FDIS 5909:2025(en) © ISO 2025

ii
ISO/FDIS 5909:2025(en)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 The industry practice for paper-based B/L business process . 3
5.1 B/L classification .3
5.2 Paper-based B/L business process .3
6 The role of a digital platform and the process of eBL on it . 4
7 Data elements and structures . 6
7.1 General overview of the data structure .6
7.2 Overview of B/L body data elements and structure .7
7.3 B/L body data elements specification and alignment with UN/CEFACT eBL and
UNTDED/ISO 7372, and the structure .9
7.4 Generic eBL processing control and record on digital platform .42
Annex A (informative) UML for B/L data exchanging.48
Bibliography .53

iii
ISO/FDIS 5909:2025(en)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee
has been established has the right to be represented on that committee. International organizations,
governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely
with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are described
in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types
of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the
ISO/IEC Directives, Part 2 (see www.iso.org/directives).
ISO draws attention to the possibility that the implementation of this document may involve the use of (a)
patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent
rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a)
patent(s) which may be required to implement this document. However, implementers are cautioned that
this may not represent the latest information, which may be obtained from the patent database available at
www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions
related to conformity assessment, as well as information about ISO's adherence to the World Trade
Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 154, Processes, data elements and documents in
commerce, industry and administration.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.

iv
ISO/FDIS 5909:2025(en)
Introduction
This document has been developed collaboratively with the UN/CEFACT Transport and Logistics Domain,
reflecting a thorough open development process that involved experts from both the public and private
sectors within ISO and UN/CEFACT. This joint effort ensures the document is comprehensive, inclusive, and
aligned with international best practices.
The bill of lading (B/L) is the core document in relation to the carriage of goods by sea, and it has three main
functions:
— the goods receipt;
— the document of title;
— the evidence of the contract of carriage.
With the rapid advancement of computer technology, the Internet, and information and communication
technologies (ICT), the electronic bill of lading (eBL) has emerged as a key method of electronic data
interchange (EDI) in the global economy. In recent years, industry stakeholders have placed growing
emphasis on the need for tamper resistance and distributed verifiability in eBL systems. In response,
eBL solutions based on distributed ledger technology (DLT) have gained traction due to their inherent
features such as immutability, traceability, and reliability. DLT-based eBLs (DLT eBLs) are well-aligned
with traditional B/L processes and comply with relevant international regulations. By enabling secure and
efficient electronic data exchange in maritime shipping, DLT eBLs represent a transformative step forward
for the industry. Compared to conventional paper-based B/L, they offer numerous advantages, including
enhanced data accuracy, improved security, greater operational efficiency, and increased environmental
sustainability.
Traditionally, the issuance, transfer, and verification of B/L have been resource-intensive and time-
consuming processes, often involving multiple intermediaries and manual handling. However, the adoption
of DLT offers a transformative alternative. By enabling peer-to-peer transactions, DLT eBLs can significantly
streamline these operations while maintaining robust information security and preventing document
forgery. This decentralized and tamper-resistant approach not only enhances trust and transparency across
the B/L lifecycle but also promises substantial time and cost savings for all stakeholders involved in the
supply chain.
The B/L process involves a wide range of participants, including carriers, shippers [large companies and
small and medium-sized enterprises (SMEs)], endorsers, endorsees, consignees [large companies and
small and medium-sized enterprises (SMEs)], banks, freight forwarders, underwriters, terminal operators,
customs authorities, maritime regulators, and other relevant stakeholders.
This framework promotes collaboration among key stakeholders to support the development, adoption, and
integration of DLT eBL and its associated applications. By addressing existing inefficiencies and compatibility
challenges, this approach delivers substantial value across the entire B/L ecosystem.
a) Standardized business process for DLT eBL
This document defines a standardized business process for implementing eBL using a digital platform,
replacing traditional paper-based methods. It covers typical maritime B/L processes, including both straight
B/L and to order B/L.
The digital platform enables the electronic transfer and endorsement of B/Ls in a controlled, and traceable
manner. While the DLT eBL process follows the conventional B/L workflow, it enhances operational control
and provides end-to-end traceability throughout the distribution chain. This improvement supports secure
custodian and seamless transfer among shippers, resellers, banks, and consignees.
b) Data requirements and interoperability framework
This document specifies the data requirements for transitioning from paper-based to digital B/L processes,
in alignment with established industry standards. It also addresses the need for compatibility across
different eBL platforms by standardizing data structures, elements, and semantics.

v
ISO/FDIS 5909:2025(en)
In the context of DLT eBL, customized or proprietary access models are discouraged, as eBLs are exchanged
across diverse stakeholders and systems. Therefore, establishing consensus on data elements and their
codification is essential. This document presents data requirements from two perspectives (see Figure 6):
— Document structure view: defines nine segments designated (B1-B9) based on the layout of traditional
B/L (see Figure 7).
— Operational and functional views: includes the business operational view (BOV), which captures
foundational B/L information, and the functional service view (FSV), which defines data elements
required for platform-level services.
The semantic structure aligns with the UN/CEFACT "Buy-Ship-Pay" model and supports compliance with
the UNCITRAL Model Law on Electronic Transferable Records (MLETR). It is also harmonized with the
UN/CEFACT Global Bill of Lading (Waybill) subset within the Multi-Modal Transport Reference Data Model
(MMT-RDM). Any additional data elements identified will be fully integrated into the MMT-RDM to ensure
consistency and interoperability.
Data element mapping (refer to Clause 7) follows the terminology of the United Nations Trade Data Elements
Directory (UNTDED/ISO 7372) and the UN/CEFACT "Buy-Ship-Pay" framework, supporting cross-platform
eBL interoperability and providing a foundation for initiating eBL process on any compliant platform.
c) Trust framework and security mechanism
This document also outlines a trust framework for secure eBL exchange, leveraging DLT to ensure that access
and control are governed by the title owner. By utilizing DLT’s inherent capabilities, the system protects
sensitive information, such as customer data, cargo details, and logistics flows, from tampering during eBL
transfers.
Each eBL issued by a carrier is uniquely identifiable and fully traceable throughout its lifecycle. Blockchain, as
a DLT implementation, supports this by using unique data fields to broadcast and record routing information
across distributed ledgers during eBL processing. This ensures that the entire transaction remains under
the control of the sender, with access restricted to authorized participants within the eBL ecosystem.
See Annex A for UML for B/L data exchanging.

vi
FINAL DRAFT International Standard ISO/FDIS 5909:2025(en)
Business processes and data interchange of electronic bill of
lading based on distributed ledger technology (DLT)
1 Scope
This document outlines the business processes and data requirements for the implementation of electronic
bill of lading (eBL). Its primary focus is the secure digital transfer of title documents via a trusted platform.
Additionally, it specifies optional data elements that are essential for leveraging distributed ledger
technology (DLT) to support the eBL workflow.
2 Normative references
There are no normative references in this document.
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
bill of lading
B/L
document which evidences a contract of carriage by sea and the taking over or loading of goods by the carrier
(3.3), and by which the carrier undertakes to deliver the goods against surrender of the document
Note 1 to entry: A provision in the document that the goods are to be delivered to the order of a named person, or to
order, or to bearer, constitutes such an undertaking (United Nations Conference of the Carriage of Goods by Sea).
Note 2 to entry: In certain countries, e.g., Canada and the United States of America, the term “bill of lading” is used to
represent a “negotiable bill of lading”.
[SOURCE: United Nations Convention on the Carriage of Goods by Sea (Hamburg, 31 March 1978); UNECE/
TRADE/377/Rev.3, 2019, 59]
3.2
holder
party for the time being in possession of the B/L (3.1)
Note 1 to entry: A holder can be:
a) A person that is in possession of a negotiable transport document; and
1) if the document is an order document, is identified in it as the shipper (3.8) or the consignee (3.4), or
is the person to which the document is duly endorsed; or
2) if the document is a blank endorsed order document or bearer document, is the bearer thereof; or
b) the person to which a negotiable electronic transport record has been issued or transferred in accordance with
the procedures (Rotterdam rules).

ISO/FDIS 5909:2025(en)
[SOURCE: United Nations Convention on Contracts for the International Carriage of Goods Wholly or Partly
by Sea (New York, 11 December 2008); UNECE/TRADE/377/Rev.3, 2019, 539]
3.3
carrier
party by whom or in whose name a contract of carriage of goods by sea has been concluded with a shipper
[SOURCE: United Nations Convention on the Carriage of Goods by Sea (Hamburg, 31 March 1978), modified —
"any person " has been replaced by "party"]
3.4
consignee
party to whom goods are shipped
[SOURCE: ISO 24533-2:2022, 3.15, modified — "person or organization" has been replaced by "party".]
3.5
electronic bill of lading
eBL
electronic document that transmits B/L (3.1) information by electronic data interchange and represents the
legal and functional equivalent of the paper B/L
Note 1 to entry: to entry: eBL is one type of electronic transferable records (ETR), and it complies with the UNCITRAL
Model Law on Electronic Transferable Records (MLETR), if applicable.
3.6
endorsee
party in whose favour a negotiable B/L (3.1) is endorsed
3.7
freight forwarder
party arranging the carriage of goods, including connected services and/or associated formalities, on behalf
of a shipper (3.8) or consignee (3.4)
[SOURCE: ISO 24533-2:2022, 3.23, modified — "consignor" has been replaced by "shipper".]
3.8
shipper
party which, according to the booking instructions stated on the B/L (3.1), by contract with a carrier (3.3),
consigns or sends goods with the carrier, or has them conveyed by the carrier, and has the right to require
the carrier to issue the B/L and undertake corresponding obligations
[SOURCE: ISO 24533-2:2022, 3.17, modified — The preferred term "consignor" has been removed; "according
to the booking instructions stated on the B/L" and "and has the right to require the carrier to issue the B/L
and undertake corresponding obligations" have been added.]
3.9
title owner
party who holds the title of goods under the B/L (3.1)

ISO/FDIS 5909:2025(en)
4 Abbreviated terms
BOV business operation view
DLT distributed ledger technology
DLT eBL electronic bill of lading based on distributed ledger technology
eBL electronic bill of lading
EORI economic operators registration and identification number
FSV functional service view
MLETR Model Law on Electronic Transferable Records
MMT Multi Modal Transport
MMT-RDM Multi Modal Transport Reference Data Model (of UN/CEFACT)
SMDG Ship Message Design Group
SMEs small and medium-sized enterprises
UN/CCL United Nations Core Components Library
UN/CEFACT United Nations Centre for Trade Facilitation and Electronic Business
UNCITRAL United Nations Commission on International Trade Law
UNECE United Nations Economic Commission for Europe
UN/EDIFACT United Nations/Electronic Data Interchange for Administration, Commerce and Transport
UNID Unique UN Assigned ID
UNLK United Nations Layout Key
UNLOCODE United Nations Code for Trade and Transport Locations
UNTDED United Nations Trade Data Elements Directory
USCI Unified Social Credit Identification
5 The industry practice for paper-based B/L business process
5.1 B/L classification
In general, there are two typical types of B/L issued by ocean carrier, one is a straight B/L on which the
consignee is printed as a specific, and the other is a to order B/L on which the consignee is printed as "to
order” or “to order of xxx”.
5.2 Paper-based B/L business process
The process of handling a straight B/L is relatively simple, as illustrated in Figure 1. In traditional maritime
shipping, once the goods have been loaded on board, the carrier issues the B/L at the request of the shipper.
The shipper then receives the original B/L and transfers it to the consignee. After the consignee obtains
the original B/L and completes the payment, they present and surrender the original B/L to the carrier. In
return, the carrier issues a delivery order, allowing the consignee to take delivery of the goods.

ISO/FDIS 5909:2025(en)
Figure 1 — Straight B/L process
The process for a to order B/L differs from that of the straight B/L after the shipper receives it from the
carrier, as illustrated in Figure 2. In this case, the shipper can endorse the B/L to an endorsee—typically
a bank or a reseller of the goods. This endorsement transfers the title owner of the goods to the endorsee.
The endorsee may then further endorse the B/L to another party, continuing the chain of title transfer. This
process can be repeated multiple times until the final endorsee chooses not to endorse the B/L further. At
that point, the final endorsee becomes the rightful recipient of the goods. The process of claiming the goods
from the carrier against the B/L remains the same as in the straight B/L process.
Figure 2 — To order B/L process
6 The role of a digital platform and the process of eBL on it
The life cycle of an eBL begins when the carrier issues the eBL to the shipper and ends when it is surrendered
back to the carrier. Throughout this process, three core actions replace traditional paper-based methods, as
illustrated in Figure 3: transfer, endorsement, and escrow.
To support these actions, the platform should ensure the authenticity and uniqueness of eBL at every stage.
It should also maintain a clear record of both the title owner and holder of the eBL during each transaction,
as shown in Figure 4 and Figure 5.
An equally critical function of the platform is to guarantee traceability of all records while upholding
data privacy and security. This includes protection against counterfeiting, tampering, data leakage, and
repudiation.
ISO/FDIS 5909:2025(en)
Given these requirements, a DLT platform, built on trusted and secure infrastructure, is particularly well-
suited for managing the complete eBL process and ensuring the integrity of all associated records.
Key
a
The carrier typically uses standard formats like EDIFACT, ANSI, or other industry protocols to input the data onto
the platform.
b
Types of eBL processing:
1) In the process of transfer, the shipper can transfer the title to the named consignee if the B/L is a named B/L.
2) In the process of endorsement, for a to order B/L, the title can be continuously transferred via continuous
endorsement.
3) Escrow authorizes a party such as a bank as the B/L holder for the custodian of the B/L, and further processes
the eBL according to the escrow instruction, but does not transfer the title to the B/L holder.
c
The title owner is always the B/L holder. However, the B/L holder can act only as a custodian rather than the title
owner itself.
d
When the eBL is surrendered to the carrier, the title transfer is deemed terminated, and the carrier is requested to
deliver the goods against the B/L.
Figure 3 — Generic process of eBL title transfer on a digital platform

ISO/FDIS 5909:2025(en)
Figure 4 — Straight eBL transfer process and the record on a digital platform
Figure 5 — To order eBL endorsement and the record on a digital platform
7 Data elements and structures
7.1 General overview of the data structure
This document specifies the data elements from two perspectives (see Figure 6). The first perspective
specifies the data elements of the B/L body, which include nine segments from B1 to B9 based on the B/L
document layout (see Figure 7). The second perspective focuses on eBL processing requirements, including
basic B/L information (BOV) and additional data elements required by platform service functions (FSV). For
DLT platform implementation, only the additional digital asset data elements (FSV) are required.

ISO/FDIS 5909:2025(en)
Key
a
For semantics and detailed structure, see Table 1 to Table 10.
NOTE 1 There are several standard formats (syntax) for B/L issuance. Thus, this document focuses on the semantics
of eBL data and the FSV component for standardizing the elements and structure related to eBL processing.
NOTE 2 The DLT asset ID is unique when implementing eBL on a DLT platform, as compared to asset IDs on other
digital platforms.
Figure 6 — Overview of the data structure
7.2 Overview of B/L body data elements and structure
The B/L document layout is widely aligned with UNLK in the industry. Thus, the data elements and structure
are also standardized. However, the maritime industry has developed into various segments, which cause
barriers to semantic consistency across different sea transportation modes, such as bulk, tank and container
shipping. Moreover, container as the transportation equipment supports ocean shipping based multimodal
transportation, new data elements are required for its B/L in compared to other ocean shipping segments.
This standard is compatible with all types of ocean transportation and is aligned with UN/CEFACT and
MMT-RDM standard, which means it applies to intermodal transportation as well.

ISO/FDIS 5909:2025(en)
Key
B1 B/L basic information
B2 parties
B3 external references
B4 transportation information
B5 declared value of goods
B6 general goods description information
B7 goods item details
B8 freight & charges
B9 terms information/Remarks
NOTE 1  In practice, the endorsee and endorsement information are on the back of the B/L when the paper-based B/L
is endorsed.
NOTE 2  The elaboration on B/L body data elements is based on the B/L layout in practice which is widely used and
aligned with UNLK in the industry.

ISO/FDIS 5909:2025(en)
NOTE 3  A sea waybill can also be issued by the sea carrier to the shipper. Its layout is the same as B/L, but the document
type “sea waybill” is clearly printed on the body. Additionally, since it is not a negotiable document, there is neither
endorsement on the back nor an “original” mark on the face.
NOTE 4  UNTDED 1001 document name code is as follows
705 Bill of Lading
Negotiable document/message which evidences a contract of carriage by sea and the taking over or loading of goods by
carrier, and by which carrier undertakes to deliver goods against surrender of the document. A provision in the document
that goods are to be delivered to the order of a named person, or to order, or to bearer, constitutes such an undertaking.
706 Bill of Lading Original
The original of the B/L issued by a transport company. When issued by the maritime industry it could signify ownership
of the cargo.
710 Sea Waybill
Non-negotiable document which evidences a contract for the carriage of goods by sea and the taking over of the goods by
the carrier, and by which the carrier undertakes to deliver the goods to the consignee named in the document.
Figure 7 — Overview of B/L body data elements and structure
7.3 B/L body data elements specification and alignment with UN/CEFACT eBL and
UNTDED/ISO 7372, and the structure
In this subclause, eBL data elements and structures are defined, elaborated and mapped to standardized
directories, namely UNTDED/ISO 7372 and UNID UN/CCL (see Table 1 to Table 9).
The mapping process ensures that each eBL data element is referenced using a unique identifier from UN/
CCL and UNTDED. The code lists used are the same as those in UN/EDIFACT. The underlined UNIDs and
UNTDED/ISO 7372 references in the following table indicate that data alignment has been verified.
By mapping to UNTDED and UN/CCL identifiers, the alignment of eBL data elements and structure across
different standards developed by various organizations or systems is ensured through these critical
directory IDs.
ISO/FDIS 5909:2025(en)
Table 1 — B/L basic information (B1)
Occur- UNTDED /
Object name Field name Type M/O Description UNID
rence ISO 7372
B/L basic in-
Object M 1.1
formation
The type of the document being exchanged, for eBL, the rele-
vant code could be selected from UNTDED 1001, here below
are some of the examples:
704 Master Bill of Lading
A bill of lading issued by the master of a vessel (in actuality
the owner or charterer of the vessel). It could cover a number
of house bills.
705 Bill of Lading
Document which evidences a contract of carriage by sea and
B/L basic in-
Document type String M 1.1 the taking over or loading of goods by the carrier, and by UN01002491 1001
formation
which the carrier undertakes to deliver the goods against
surrender of the document.
707 Bill of Lading copy
A copy of the bill of lading issued by a transport company.
710 Sea Waybill
Non-negotiable document which evidences a contract for the
carriage of goods by sea and the taking over of the goods by
the carrier, and by which the carrier undertakes to deliver
the goods to the consignee named in the document.
B/L number, the unique identifier assigned by the carrier to
the shipment when making the B/L. Its meaning is totally
different from the booking reference number assigned when
B/L basic in-
cargo space is reserved. However, from an operation per-
B/L number String M 1.1 UN01004164 1065
formation
spective, it may be same as the booking reference number or
totally different, depending on operation requirements.
This is the “carrier assigned ID” in UN/CCL.
B/L basic in- Original B/L version, provided by the carrier triggered from
Document version String M 1.1 UN01003573 1057
formation issuing the final original B/L in their in-house system.
B/L basic in-
B/L set Integer M 1.1 Total number, in figures, of the originals of B/L issued. UN01003559 1067
formation
B/L basic in-
B/L total pages Integer M 1.1 Total number of pages in a document. UN01003577 1046
formation
Reference number assigned by a carrier or its agent to identi- UN01001577
B/L basic in- Carrier booking num- Array of
O 0.n fy a specific consignment such as a booking reference number + 1016
formation bers string
when cargo space is reserved prior to loading. UN01003991

ISO/FDIS 5909:2025(en)
Table 1 (continued)
Occur- UNTDED /
Object name Field name Type M/O Description UNID
rence ISO 7372
B/L basic in- Transport service Reference number identifying a transport service contract
String O 0.1 UN01015088 1296
formation contract number that this shipment is additional to.
B/L basic in- Office location where the original B/L was issued, recom-
Place of issue Object M 1.1 UN01004018 3410
formation mend using location structure at UN/EDIFACT.
Location identifier of terminal in port, or smaller location,
such as terminal depot, rail ramp, e.g., SMDG
Place of issue Location code String O 0.1 UN01003680 3225
Recommend to use UNECE Recommendation 16: UNLOCODE.
Place of issue Location name String M 1.1 Name of the location. e.g., Shanghai. UN01003681 3224
B/L basic in-
Date of issue String M 1.1 B/L issue date. Reference to ISO 8601-1. UN01002493 2007
formation
B/L basic in- Date laden on board the main carriage vessel (sea going ves-
Date laden on board String M 1.1 UN01015089 2347
formation sel or ocean vessel). Reference to ISO 8601-1.
The endorsement on the B/L. In paper it's endorsed on the
B/L basic in- back of the bill of lading and can be zero when the B/L is
Endorsement Object O 0.n
formation named B/L, or it can be one to multiple when the B/L is to
order, depending on the trade requirement.
See 3.6
Endorsement Endorsee Object M 1.1
Party in whose favour a negotiable B/L is endorsed.
A unique identifier of this trade party. Usually, it’s a unique
Endorsee Party ID String O 0.1 registration code or global identifiable code assigned in an ID UN01004595 3039
scheme.
Endorsee Party name text String M 1.1 Name of a party. UN01004598 3036
Party platform iden- The unique ID specifying the identity of a party in the eBL
Endorsee String M 1.1
tifier platform.
Party contact including contact ID, name, and department
Endorsee Contact Object O 0.n UN01004602
name.
The unique identifier for this contact. The unique ID in the
Contact Contact ID String O 0.1 system or B/L to identify the contact, like the state ID, or UN01001641 3413
other global identifiable ID assigned in an ID scheme.
Contact Contact name String O 0.1 The name, expressed as text, of this contact person. UN01001642 3412
The name, expressed as text, of the department to which this
Contact Department name String O 0.1 UN01001643 3412
contact belongs within an organization.
To identify a department or employee ID in the context of the
Contact platform
Contact String O 0.1 party where has belonged to. The unique ID assigned in the
identifier
eBL platform.
ISO/FDIS 5909:2025(en)
Table 1 (continued)
Occur- UNTDED /
Object name Field name Type M/O Description UNID
rence ISO 7372
Including phone, fax, e-mail, postal address and/or reference
Contact Communication Object O 0.1
of the contact.
A telephone communication for this party. Telephone number,
Communica- including country and/or city code as required, for voice
Contact phone String O 0.1 UN01004564 3155+3148
tion or data transmission by telephone beyond the border of a
country.
Fax communication information for this location party.
Communication service involving teletypewriter machines
Communica-
Contact fax String O 0.1 UN01004567 3155+3148
connected by wire or electronic transmission media. Tele-
tion
typewriter machines are the devices used to send and receive
signals and produce hardcopy from them.
Communica- The Uniform Resource Identifier (URI), such as a web or an
Contact email address String O 0.1 UN01004569 3155+3148
tion email address, for this universal communication.
Endorsee Postal address Object O 0.1 The postal address for this trade party.
Array of
Postal address Address description O 0.1 To specify the name/address and their related function. UN01004603
string
Postal address Postcode String O 0.1 Code specifying a postal zone or address. UN01004535 3251
Specification of the postal delivery point such as street and
Postal address Street name String O 0.1 UN01004543 3042
number or post office box.
Postal address City name String O 0.1 Name of a city. UN01004544 3164
Country subdivision
Postal address String O 0.1 Name of a country subdivision. UN01004549 3228
name
Identification of the name of the country or other geographi-
Postal address Country code String O 0.1 UN01004546 3207
cal entity. Reference to ISO 3166-1.
Postal address Country name String O 0.1 Name of the country or other geographical entity UN01004547 3206
Reference of that party, e.g., USCI and EORI. Consider using
Party external refer-
Endorsee Object O 0.n the repeatable UN/CCL party identifier structure (ID, identi-
ences
fication scheme, identification scheme agency)
Party external
Tax authority ID String O 0.1 Party identifier for tax authority. UN01004487 3446
references
Party external
Customs ID String O 0.1 Party identifier for customs. UN01004595
references
ISO/FDIS 5909:2025(en)
Table 1 (continued)
Occur- UNTDED /
Object name Field name Type M/O Description UNID
rence ISO 7372
Reference type, it is recommended to use the UNECE code
list. The reference may not be a document, for example, a bulk
carrier can use this field to identify the B/L related to a voy-
age charter party. (For UNTDED for associated documents
Party external
shall be made here)
Reference type String O 0.1 UN01006036 1153
references
1153 Reference code qualifier, code qualifying a reference.
e.g.,
RF Export reference number, reference number given to an
export shipment.
Identifies a reference.
Party external
Under the circumstance that the voyage charter party needs
Reference number String O 0.1 UN01003991 1154
references
to be incorporated into the B/L, the date to identify the voy-
age charter party under which the B/L is issued.
The date in which endorsing has occurred to the party from
Endorsement Endorsement date String M 1.1
the previous holder.
ISO/FDIS 5909:2025(en)
Table 2 — Parties (B2)
UNTDED /
Object name Field name Type M/O Occurrence Description UNID
ISO 7372
Parties Carrier Object M 1.1 See 3.3 UN01004214 3126
A unique identifier of this trade party. Usually, it’s a unique regis-
Carrier Party ID String O 0.1 UN01004595 3039
tration code or global identifiable code assigned in an ID scheme.
Carrier Party name text String M 1.1 Name of a party. UN01004598 3036
Code specifying the identity of a party.
Party platform identi-
Carrier String M 1.1
fier
The unique ID in the eBL platform.
Carrier Contact Object O 0.n Party contact including contact ID, name, and department name. UN01004602
The unique identifier for this contact. The unique ID in the system
Contact Contact ID String O 0.1 or B/L to identify the contact, like the state ID, or other global iden- UN01001641 3413
tifiable ID assigned in an ID scheme.
Contact Contact name String O 0.1 The name, expressed as text, of this contact person. UN01001642 3412
The name, expressed as text, of the department to which this con-
Contact Department name String O 0.1 UN01001643 3412
tact belongs within an organization.
Contact platform iden- To identify a department or employee ID in the context of the party
Contact String O 0.1
tifier where has belonged to. The unique ID assigned in the eBL platform.
Including phone, fax, e-mail, postal address and/or reference of the
Contact Communication Object O 0.1
contact.
A telephone communication for this party. Telephone number,
Communication Contact phone String O 0.1 including country and/or city code as required, for voice or data UN01004564 3155+3148
transmission by telephone beyond the border of a country.
Fax communication information for this location party.
Communication service involving teletypewriter machines con-
Communication Contact fax String O 0.1 UN01004567 3155+3148
nected by wire or electronic transmission media. Teletypewriter
machines are the devices used to send and receive signals and
produce hardcopy from them.
The Uniform Resource Identifier (URI), such as a web or an email
Communication Contact email address String O 0.1 UN01004569 3155+3148
address, for this universal communication.
Carrier Postal address Object M 1.1 The postal address for this trade party.
Postal address Address description Array of string M 0.1 To specify the name/address and their related function. UN01004603
Postal address Postcode String O 0.1 Code specifying a postal zone or address. UN01004535 3251
Specification of the postal delivery point such as street and number
Postal address Street name String O 0.1 UN01004543 3042
or post office box.
Postal address City name String O 0.1 Name of a city. UN01004544 3164
Country subdivision
Postal address String O 0.1 Name of a country subdivision. UN01004549 3228
name
Identification of the name of the country or other geographical
Postal address Country code String O 0.1 UN01004546 3207
entity. Reference to ISO 3166-1.

ISO/FDIS 5909:2025(en)
Table 2 (continued)
UNTDED /
Object name Field name Type M/O Occurrence Description UNID
ISO 7372
Postal address Country name String O 0.1 Name of the country or other geographical entity. UN01004547 3206
Reference of that party, e.g., USCI and EORI. Consider using the
Party external refer-
Carrier Object O 0.n repeatable UN/CCL party identifier structure (ID, identification
ences
scheme, identification scheme agency).
Party external
Tax authority ID String O 0.1 Party identifier for tax authority. UN01004487 3446
references
Party external
Customs ID String O 0.1 Party identifier for customs. UN01004595
references
Reference type, it is recommended to use the UNECE code list. The
reference may not be a document, for example, a bulk carrier can
use this field to identify the B/L related to a voyage charter party.
Party external
(For UNTDED for associated documents shall be made here)
Reference type String O 0.1 UN01006036 1153
references
1153 Reference code, qualifier code qualifying a reference. e.g.,
RF Export reference number, reference number given to an export
shipment.
Identifies a reference.
Party external
Under the circumstance that the voyage charter party needs to be
Reference number String O 0.1 UN01003991 1154
references
incorporated into the B/L, the date to identify the voyage charter
party under which the B/L is issued.
see 3.8.
Party which, according to the booking instructions stated on the B/L,
Parties Shipper Object M 1.1 UN01004212 3336
by contract with a carrier, consigns or sends goods with the carrier,
or has them conveyed by the carrier, and has the right to require the
carrier to issue the B/L and undertake corresponding obligations.
A unique identifier of this trade party. Usually, it’s a unique regis-
Shipper Party ID String O 0.1 UN01004595 3039
tration code or global identifiable code assigned in an ID scheme.
Shipper Party name text String M 1.1 Name of a party. UN01004598 3036
Code specifying the identity of a party.
Party platform identi-
Shipper String M 1.1
fier
The unique ID in the eBL platform.
Shipper Contact Object O 0.n Party contact including contact ID, name, and department name. UN01004602
The unique identifier for this contact. The unique ID in the system
Contact Contact ID String O 0.1 or B/L to identify the contact, like the state ID, or other global iden- UN01001641 3413
tifiable ID assigned in an ID scheme.
Contact Contact name String O 0.1 The name, expressed as text, of this contact person. UN01001642 3412
The name, expressed as text, of the department to which this con-
Contact Department name String O 0.1 UN01001643 3412
tact belongs within an organization.
Contact platform iden- To identify a department or employee ID in the context of the party
Contact String O 0.1
tifier where has belonged to. The unique ID assigned in the eBL platform.

ISO/FDIS 5909:2025(en)
Table 2 (continued)
UNTDED /
Object name Field name Type M/O Occurrence Description UNID
ISO 7372
Including phone, fax, e-mail, postal address and/or reference of the
Contact Communication Object O 0.1
contact.
A
...