Introduction to digital trade

Background

Contemporary manufacturing often involves large manufacturers dealing with a small number of risk-sharing partners who co-design and deliver key subsystems of the customized product. These partners sub-contract the supply of key systems to their suppliers which results in a vast network of collaboration activities throughout the supply chains involving companies of all sizes. The “digitization” of production and logistics provides a number of significant, new advantages to modern supply chain management in the so-called Industry 4.0 concept. Industry 4.0 concept embraces the Internet of Things, Internet of Services and Cyber-Physical Systems to bring the new design for modern manufacturing. Design features of Industry 4.0 are Interoperability, Virtualisation, Decentralisation, Real-Time Capability, Service Orientation, and Modularity.

The rise of Industry 4.0 is driven by the need to support the rapid formation of partner collaborations, the ability to respond to fast-changing market needs and the capacity to quickly respond to new business opportunities. SMEs in collaborative networks focus on their core competencies and try to find complementary partners to compensate for the lack of competencies and cooperate to fit to tender or to run new product development

The main motivation behind this project is to support small and medium-sized enterprises (SMEs) so that they can fully participate in Industry 4.0 emergent collaborations. Its main focus is in the area of business document exchanges between collaborating partners. In particular, SMEs need a cost-effective solution that is both open and flexible. This way, they can better leverage their existing assets, use components from different vendors and be in control of the evolution of their e-invoicing solutions.

The Universal Business Language (UBL)

Introduction

One of the most respected, non-profit standards bodies in the world, OASIS Open (Organization for the Advancement of Structured Information Standards) offers projects—including open source projects—a path to standardization and de jure approval for reference in international policy and procurement. The consortium has more than 5,000 participants representing over 600 organizations and individual members in 65+ countries. http://www.oasis-open.org .

Defined by OASIS Open, UBL, the Universal Business Language, defines a royalty-free library of standard XML business documents supporting the digitization of the commercial and logistical processes for domestic and international supply chains such as procurement, purchasing, transport, logistics, intermodal freight management, and other supply chain management functions. UBL has also become foundational to a number of efforts in the transport and logistics domain, including the European Common Framework (European Commission), DTTN (Port of Hong Kong), TradeNet (Port of Singapore), Electronic Freight Management (US), and Freightgate (globally). In 2014 the European Commission declared UBL 2.1 was officially eligible for referencing in tenders from public administrations (one of the first non-European standards to be so recognized).

Details about the UBL standards are available from the UBL Web site, arranged into different version. For example, version 2.1 is available here: Universal Business Language Version 2.1

In the rest of this section, we summarize the main features that are required for the project. Most of the information is contained in this document:

Information exchanges business processes

UBL assumes business processes are arranged into these categories:

Plan (out of scope in this project)
Procurement
Deliver
Pay

Under each category are several business processes. We provide additional information and examples of business processes in each category that is in the scope of this project.

Procurement category

Procurement involves a contract between a buyer party and a preferred seller party for the delivery of a product or service. There are many business processes related to creating the contract (pre-award) and ordering the goods/services (post-award). Many of these processes are defined using the BPML language. For example, the ordering processing (see page 48) is defined as described in the figure below:

The document types in these processes are Order, Order Response, Order Response Simple, Order Change, and Order Cancellation. An example of an Order will be given later in this document.

Deliver category

Delivery processes involve the collaboration in which the goods and services are transferred from the Despatch party to the Delivery party. There are many processes and scenarios and document types used in these processes are Despatch Advice, Receipt Advice, Order Cancellation, Order Change, and Fulfilment Cancellation.

The Despatch Advice is of most interest to us. This document is generated as a response to an Order document and has business rules defined as shown in the figure below (page 60):

Pay category

In this category, a request is made for payment for goods and services that have been ordered, received or consumed. The processes involve the following document types: Invoice, Credit Note, Debit Note, and Application Response. The Invoice document (or e-invoice) is of most interest to us.

The introduction of e-invoicing legislation across Europe in particular has greatly boosted the number of companies wishing to be able to exchange UBL structured electronic invoices. In 2014, the European Commission declared UBL 2.1 was officially eligible for referencing in tenders from public administrations (one of the first non-European standards to be so recognized). In Australia, all New South Wales state government agencies will have to UBL invoices for goods and services valued at up to AUD 1 million from 2022.
The most common pay process uses the Invoice document in conjunction with the with Credit Note document, as shown in the diagram below (page 83):

UBL document formats

Introduction to UBL XML

As we have seen so far, UBL defines a number of business documents in XML to support the business processes. The figure below is a subsection of the UBL invoice:

In this example, each number on the image represents:

Invoice type code 380 indicates it is an invoice.
The charge amount is negative to correct the original invoice.
All document-level (LegalMonetaryTotal) amounts are negative.
Start of invoice line 1.
The price amount must always be positive and is not changed.
Start of invoice line 2.

More information about UBL XML can be found here https://www.xml.com/articles/2017/01/01/what-is-ubl/

Validating UBL documents

The content of each document is defined using a number of UBL XSD schemas that can be used for the purposes of XML document validation and conformance. All of the UBL XSD schemas are contained in the xsd subdirectory of the UBL release package.

For each document type, the following information is provided:

Processes Involved	Which business process uses this document
Submitter Role	The role of the sender of this document
Receiver Role	The role of the receiver
Schemas	Normative and Runtime XSD schemas for validating the document
Summary Report	An HTML description of the document
Example instance	An XML example of the document

For example, in the Invoice document type, each core element of an e-invoice is part of the EN16931 semantic data model, established as a European Standard. EN16931 includes only the essential information that an e-invoice needs to ensure legal compliance.

Each country can make specific adjustments to the standard. For example, for Australia and New Zealand, material related to the Invoice document can be found in https://github.com/A-NZ-PEPPOL/A-NZ-PEPPOL-BIS-3.0. Samples can be accessed from this folder https://github.com/A-NZ-PEPPOL/A-NZ-PEPPOL-BIS-3.0/tree/master/Message%20examples

Document Formats used in the project

In this project we will focus on the following messages:

Order: details in Section 3.2.47 Order Schema (page 111)
Despatch advice: details in 3.2.20 Despatch Advice Schema (page 103)
Invoice: details in 3.2.44 Invoice Schema (110)

Some examples that can be downloaded from this repository: https://github.com/Tradeshift/tradeshift-ubl-examples are presented in Appendix A.

Project requirements

Phase 1: Developing an API

What is SaaS ?

Software as a Service (SaaS) is a concept that pushes software away from local computers into Web services. This means users no longer buy software to install locally but instead buy the right to use the software over the Internet. SaaS providers maintain the hardware, perform upgrades, backup your data (sometimes), and otherwise perform all of the “keep the lights on” services and activities required to keep the software running. [1]

The first phase of the project is to introduce students to the concept of SaaS by considering each team as a company that performs the following:

The company creates a software product (referred to as a service as it is accessible via a REST API) and hosts it on a cloud server.
Customers can subscribe to the service as soon as it is operational, giving feedback to the company
The company makes both major and minor updates to the software, and the customers automatically get those updates as part of their subscriptions.

We will only be concerned with the technical aspects of SaaS in this project (the building and deployment of the software product) rather than other aspects like charging etc.

[1] Software as a Service Vs. Software as a Product - Pragmatic Institute

Towards a SaaS ecosystem for integrated digital trade

An ecosystem of services consists of SaaS services that can be composed, configured and customised according to different contexts in accordance with Service-Oriented Architecture (SOA) and Business Process Modelling (BPM) principles. Each service is providing a particular functionality in the-invoicing services ecosystem, can potentially be provided by a different vendor, is available via an API and is available on a pay-by-use basis. Companies (and in particular SMEs) can create flexible, open and multi-vendor solutions in the form of document exchange workflows that enforce business document exchange processes that are applicable in a certain context.

The categories of services in the ecosystem are listed in the following table:

SaaS Category

Description

Customization Points

Order Creation

Creates a standardised UBL Order document from user-provided data

Get data from an established contract (e.g. product type)

Despatch Advice Generation

Creates a standardised UBL Despatch Advice from an Order Document and other user-provided data

Get data from an established contract (e.g. delivery address)

Automatically determine some fields (e.g. delivery date)

Invoice Generation

Creates a standardised UBL Invoice from an Order Document and other user-provided data

Get data from an established contract (e.g. prices)

Apply additional validation rules

General guidelines

Student teams will develop an information exchange application in two phases. In phase 1, you need to develop a SaaS API to perform a UBL Document creation function in the ecosystem according to one of the categories listed earlier. The API must be deployed and made available for other teams to use.

The notes below are applicable to all 6 categories. There are some general suggestions on what you should consider when designing your service.

Design your service: For each of the categories, except being specified by this spec, you should consider and decide what input your service requires, then design what the output should look like.
Consider the cost of usage: Since your services may be required by other teams in stage 2, it is essential that you make your service easy to be used as a module by others, including providing documentation, supporting multiple formats of input and output, having reasonable performance, etc.
Start simple: It is hard to cover all possible formats of input and output for each of the services in this given time frame. It is important for each group to prioritise the functionalities of the service and deliver the most important functions first. You should consider starting from a very basic service, and then keep iterating the service.
Things can change. Mentors will constantly give additional details which may change the spec during the project to add new information, answer FAQs etc. It is important that you reflect/document these changes continuously in your deployed version.
Understand the standard. By recommended standardised format, we mean UBL 2.1 XML format. This format and associated sample files are described in a separate document.
Implement health check endpoint. When implementing your service, please implement an endpoint that indicates the aliveness of your services if your service is stateful. A simple success response is sufficient, but some running statistics of your service is preferable. This is to let a developer check if your service is still alive.

Phase 2: Developing the front-end application.

In phase 2, you need to develop an application that provides one or more of the following functions for a part involved in a supplied chain. Here are some other ideas for possible platforms:

An information system for generating orders based on established contracts
An information system that generates despatch advices based on orders
An information system that sends invoices to customers when deliveries are made
An information system for buyers that processes received invoices for payment
An analytics system that can be used to provide invoices statistics for buyers/sellers
A tracking dashboard that shows different invoices at different stages in the system

Depending on the use cases selected by a team, appropriate APIs will be integrated. These could be APIs from other teams or external APIs. The teams have the flexibility to select the scope of their platform, what users they are targeting, and what business value they deliver. It is expected that teams will be delivering unique solutions at the end of the workshop.

APPENDIX A - Example of UBL Documents

These are from GitHub (using an older version of UBL).

Example 1: Order

<?xml version="1.0" encoding="UTF-8"?>
<Order xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns="urn:oasis:names:specification:ubl:schema:xsd:Order-2">
	<cbc:UBLVersionID>2.0</cbc:UBLVersionID>
	<cbc:CustomizationID>urn:oasis:names:specification:ubl:xpath:Order-2.0:sbs-1.0-draft</cbc:CustomizationID>
	<cbc:ProfileID>bpid:urn:oasis:names:draft:bpss:ubl-2-sbs-order-with-simple-response-draft</cbc:ProfileID>
	<cbc:ID>AEG012345</cbc:ID>
	<cbc:SalesOrderID>CON0095678</cbc:SalesOrderID>
	<cbc:CopyIndicator>false</cbc:CopyIndicator>
	<cbc:UUID>6E09886B-DC6E-439F-82D1-7CCAC7F4E3B1</cbc:UUID>
	<cbc:IssueDate>2005-06-20</cbc:IssueDate>
	<cbc:Note>sample</cbc:Note>
	<cac:BuyerCustomerParty>
		<cbc:CustomerAssignedAccountID>XFB01</cbc:CustomerAssignedAccountID>
		<cbc:SupplierAssignedAccountID>GT00978567</cbc:SupplierAssignedAccountID>
		<cac:Party>
			<cac:PartyName>
				<cbc:Name>IYT Corporation</cbc:Name>
			</cac:PartyName>
			<cac:PostalAddress>
				<cbc:StreetName>Avon Way</cbc:StreetName>
				<cbc:BuildingName>Thereabouts</cbc:BuildingName>
				<cbc:BuildingNumber>56A</cbc:BuildingNumber>
				<cbc:CityName>Bridgtow</cbc:CityName>
				<cbc:PostalZone>ZZ99 1ZZ</cbc:PostalZone>
				<cbc:CountrySubentity>Avon</cbc:CountrySubentity>
				<cac:AddressLine>
					<cbc:Line>3rd Floor, Room 5</cbc:Line>
				</cac:AddressLine>
				<cac:Country>
					<cbc:IdentificationCode>GB</cbc:IdentificationCode>
				</cac:Country>
			</cac:PostalAddress>
			<cac:PartyTaxScheme>
				<cbc:RegistrationName>Bridgtow District Council</cbc:RegistrationName>
				<cbc:CompanyID>12356478</cbc:CompanyID>
				<cbc:ExemptionReason>Local Authority</cbc:ExemptionReason>
				<cac:TaxScheme>
					<cbc:ID>UK VAT</cbc:ID>
					<cbc:TaxTypeCode>VAT</cbc:TaxTypeCode>
				</cac:TaxScheme>
			</cac:PartyTaxScheme>
			<cac:Contact>
				<cbc:Name>Mr Fred Churchill</cbc:Name>
				<cbc:Telephone>0127 2653214</cbc:Telephone>
				<cbc:Telefax>0127 2653215</cbc:Telefax>
				<cbc:ElectronicMail>fred@iytcorporation.gov.uk</cbc:ElectronicMail>
			</cac:Contact>
		</cac:Party>
	</cac:BuyerCustomerParty>
	<cac:SellerSupplierParty>
		<cbc:CustomerAssignedAccountID>CO001</cbc:CustomerAssignedAccountID>
		<cac:Party>
			<cac:PartyName>
				<cbc:Name>Consortial</cbc:Name>
			</cac:PartyName>
			<cac:PostalAddress>
				<cbc:StreetName>Busy Street</cbc:StreetName>
				<cbc:BuildingName>Thereabouts</cbc:BuildingName>
				<cbc:BuildingNumber>56A</cbc:BuildingNumber>
				<cbc:CityName>Farthing</cbc:CityName>
				<cbc:PostalZone>AA99 1BB</cbc:PostalZone>
				<cbc:CountrySubentity>Heremouthshire</cbc:CountrySubentity>
				<cac:AddressLine>
					<cbc:Line>The Roundabout</cbc:Line>
				</cac:AddressLine>
				<cac:Country>
					<cbc:IdentificationCode>GB</cbc:IdentificationCode>
				</cac:Country>
			</cac:PostalAddress>
			<cac:PartyTaxScheme>
				<cbc:RegistrationName>Farthing Purchasing Consortium</cbc:RegistrationName>
				<cbc:CompanyID>175 269 2355</cbc:CompanyID>
				<cbc:ExemptionReason>N/A</cbc:ExemptionReason>
				<cac:TaxScheme>
					<cbc:ID>VAT</cbc:ID>
					<cbc:TaxTypeCode>VAT</cbc:TaxTypeCode>
				</cac:TaxScheme>
			</cac:PartyTaxScheme>
			<cac:Contact>
				<cbc:Name>Mrs Bouquet</cbc:Name>
				<cbc:Telephone>0158 1233714</cbc:Telephone>
				<cbc:Telefax>0158 1233856</cbc:Telefax>
				<cbc:ElectronicMail>bouquet@fpconsortial.co.uk</cbc:ElectronicMail>
			</cac:Contact>
		</cac:Party>
	</cac:SellerSupplierParty>
	<cac:OriginatorCustomerParty>
		<cac:Party>
			<cac:PartyName>
				<cbc:Name>The Terminus</cbc:Name>
			</cac:PartyName>
			<cac:PostalAddress>
				<cbc:StreetName>Avon Way</cbc:StreetName>
				<cbc:BuildingName>Thereabouts</cbc:BuildingName>
				<cbc:BuildingNumber>56A</cbc:BuildingNumber>
				<cbc:CityName>Bridgtow</cbc:CityName>
				<cbc:PostalZone>ZZ99 1ZZ</cbc:PostalZone>
				<cbc:CountrySubentity>Avon</cbc:CountrySubentity>
				<cac:AddressLine>
					<cbc:Line>3rd Floor, Room 5</cbc:Line>
				</cac:AddressLine>
				<cac:Country>
					<cbc:IdentificationCode>GB</cbc:IdentificationCode>
				</cac:Country>
			</cac:PostalAddress>
			<cac:PartyTaxScheme>
				<cbc:RegistrationName>Bridgtow District Council</cbc:RegistrationName>
				<cbc:CompanyID>12356478</cbc:CompanyID>
				<cbc:ExemptionReason>Local Authority</cbc:ExemptionReason>
				<cac:TaxScheme>
					<cbc:ID>UK VAT</cbc:ID>
					<cbc:TaxTypeCode>VAT</cbc:TaxTypeCode>
				</cac:TaxScheme>
			</cac:PartyTaxScheme>
			<cac:Contact>
				<cbc:Name>S Massiah</cbc:Name>
				<cbc:Telephone>0127 98876545</cbc:Telephone>
				<cbc:Telefax>0127 98876546</cbc:Telefax>
				<cbc:ElectronicMail>smassiah@the-email.co.uk</cbc:ElectronicMail>
			</cac:Contact>
		</cac:Party>
	</cac:OriginatorCustomerParty>
	<cac:Delivery>
		<cac:DeliveryAddress>
			<cbc:StreetName>Avon Way</cbc:StreetName>
			<cbc:BuildingName>Thereabouts</cbc:BuildingName>
			<cbc:BuildingNumber>56A</cbc:BuildingNumber>
			<cbc:CityName>Bridgtow</cbc:CityName>
			<cbc:PostalZone>ZZ99 1ZZ</cbc:PostalZone>
			<cbc:CountrySubentity>Avon</cbc:CountrySubentity>
			<cac:AddressLine>
				<cbc:Line>3rd Floor, Room 5</cbc:Line>
			</cac:AddressLine>
			<cac:Country>
				<cbc:IdentificationCode>GB</cbc:IdentificationCode>
			</cac:Country>
		</cac:DeliveryAddress>
		<cac:RequestedDeliveryPeriod>
			<cbc:StartDate>2005-06-29</cbc:StartDate>
			<cbc:StartTime>09:30:47.0Z</cbc:StartTime>
			<cbc:EndDate>2005-06-29</cbc:EndDate>
			<cbc:EndTime>09:30:47.0Z</cbc:EndTime>
		</cac:RequestedDeliveryPeriod>
	</cac:Delivery>
	<cac:DeliveryTerms>
		<cbc:SpecialTerms>1% deduction for late delivery as per contract</cbc:SpecialTerms>
	</cac:DeliveryTerms>
	<cac:TransactionConditions>
		<cbc:Description>order response required; payment is by BACS or by cheque</cbc:Description>
	</cac:TransactionConditions>
	<cac:AnticipatedMonetaryTotal>
		<cbc:LineExtensionAmount currencyID="GBP">100.00</cbc:LineExtensionAmount>
		<cbc:PayableAmount currencyID="GBP">100.00</cbc:PayableAmount>
	</cac:AnticipatedMonetaryTotal>
	<cac:OrderLine>
		<cbc:Note>this is an illustrative order line</cbc:Note>
		<cac:LineItem>
			<cbc:ID>1</cbc:ID>
			<cbc:SalesOrderID>A</cbc:SalesOrderID>
			<cbc:LineStatusCode>NoStatus</cbc:LineStatusCode>
			<cbc:Quantity unitCode="KGM">100</cbc:Quantity>
			<cbc:LineExtensionAmount currencyID="GBP">100.00</cbc:LineExtensionAmount>
			<cbc:TotalTaxAmount currencyID="GBP">17.50</cbc:TotalTaxAmount>
			<cac:Price>
				<cbc:PriceAmount currencyID="GBP">100.00</cbc:PriceAmount>
				<cbc:BaseQuantity unitCode="KGM">1</cbc:BaseQuantity>
			</cac:Price>
			<cac:Item>
				<cbc:Description>Acme beeswax</cbc:Description>
				<cbc:Name>beeswax</cbc:Name>
				<cac:BuyersItemIdentification>
					<cbc:ID>6578489</cbc:ID>
				</cac:BuyersItemIdentification>
				<cac:SellersItemIdentification>
					<cbc:ID>17589683</cbc:ID>
				</cac:SellersItemIdentification>
			</cac:Item>
		</cac:LineItem>
	</cac:OrderLine>
</Order>

Example 2: Despatch Advice

<?xml version="1.0" encoding="UTF-8"?>
<DespatchAdvice xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns="urn:oasis:names:specification:ubl:schema:xsd:DespatchAdvice-2">
	<cbc:UBLVersionID>2.0</cbc:UBLVersionID>
	<cbc:CustomizationID>urn:oasis:names:specification:ubl:xpath:DespatchAdvice-2.0:sbs-1.0-draft</cbc:CustomizationID>
	<cbc:ProfileID>bpid:urn:oasis:names:draft:bpss:ubl-2-sbs-despatch-advice-notification-draft</cbc:ProfileID>
	<cbc:ID>565899</cbc:ID>
	<cbc:CopyIndicator>false</cbc:CopyIndicator>
	<cbc:UUID>88C7280E-8F10-419F-9949-8EFFFA2842B8</cbc:UUID>
	<cbc:IssueDate>2005-06-20</cbc:IssueDate>
	<cbc:DocumentStatusCode>NoStatus</cbc:DocumentStatusCode>
	<cbc:DespatchAdviceTypeCode>delivery</cbc:DespatchAdviceTypeCode>
	<cbc:Note>sample</cbc:Note>
	<cac:OrderReference>
		<cbc:ID>AEG012345</cbc:ID>
		<cbc:SalesOrderID>CON0095678</cbc:SalesOrderID>
		<cbc:UUID>6E09886B-DC6E-439F-82D1-7CCAC7F4E3B1</cbc:UUID>
		<cbc:IssueDate>2005-06-20</cbc:IssueDate>
	</cac:OrderReference>
	<cac:DespatchSupplierParty>
		<cbc:CustomerAssignedAccountID>CO001</cbc:CustomerAssignedAccountID>
		<cac:Party>
			<cac:PartyName>
				<cbc:Name>Consortial</cbc:Name>
			</cac:PartyName>
			<cac:PostalAddress>
				<cbc:StreetName>Busy Street</cbc:StreetName>
				<cbc:BuildingName>Thereabouts</cbc:BuildingName>
				<cbc:BuildingNumber>56A</cbc:BuildingNumber>
				<cbc:CityName>Farthing</cbc:CityName>
				<cbc:PostalZone>AA99 1BB</cbc:PostalZone>
				<cbc:CountrySubentity>Heremouthshire</cbc:CountrySubentity>
				<cac:AddressLine>
					<cbc:Line>The Roundabout</cbc:Line>
				</cac:AddressLine>
				<cac:Country>
					<cbc:IdentificationCode>GB</cbc:IdentificationCode>
				</cac:Country>
			</cac:PostalAddress>
			<cac:PartyTaxScheme>
				<cbc:RegistrationName>Farthing Purchasing Consortium</cbc:RegistrationName>
				<cbc:CompanyID>175 269 2355</cbc:CompanyID>
				<cbc:ExemptionReason>N/A</cbc:ExemptionReason>
				<cac:TaxScheme>
					<cbc:ID>VAT</cbc:ID>
					<cbc:TaxTypeCode>VAT</cbc:TaxTypeCode>
				</cac:TaxScheme>
			</cac:PartyTaxScheme>
			<cac:Contact>
				<cbc:Name>Mrs Bouquet</cbc:Name>
				<cbc:Telephone>0158 1233714</cbc:Telephone>
				<cbc:Telefax>0158 1233856</cbc:Telefax>
				<cbc:ElectronicMail>bouquet@fpconsortial.co.uk</cbc:ElectronicMail>
			</cac:Contact>
		</cac:Party>
	</cac:DespatchSupplierParty>
	<cac:DeliveryCustomerParty>
		<cbc:CustomerAssignedAccountID>XFB01</cbc:CustomerAssignedAccountID>
		<cbc:SupplierAssignedAccountID>GT00978567</cbc:SupplierAssignedAccountID>
		<cac:Party>
			<cac:PartyName>
				<cbc:Name>IYT Corporation</cbc:Name>
			</cac:PartyName>
			<cac:PostalAddress>
				<cbc:StreetName>Avon Way</cbc:StreetName>
				<cbc:BuildingName>Thereabouts</cbc:BuildingName>
				<cbc:BuildingNumber>56A</cbc:BuildingNumber>
				<cbc:CityName>Bridgtow</cbc:CityName>
				<cbc:PostalZone>ZZ99 1ZZ</cbc:PostalZone>
				<cbc:CountrySubentity>Avon</cbc:CountrySubentity>
				<cac:AddressLine>
					<cbc:Line>3rd Floor, Room 5</cbc:Line>
				</cac:AddressLine>
				<cac:Country>
					<cbc:IdentificationCode>GB</cbc:IdentificationCode>
				</cac:Country>
			</cac:PostalAddress>
			<cac:PartyTaxScheme>
				<cbc:RegistrationName>Bridgtow District Council</cbc:RegistrationName>
				<cbc:CompanyID>12356478</cbc:CompanyID>
				<cbc:ExemptionReason>Local Authority</cbc:ExemptionReason>
				<cac:TaxScheme>
					<cbc:ID>UK VAT</cbc:ID>
					<cbc:TaxTypeCode>VAT</cbc:TaxTypeCode>
				</cac:TaxScheme>
			</cac:PartyTaxScheme>
			<cac:Contact>
				<cbc:Name>Mr Fred Churchill</cbc:Name>
				<cbc:Telephone>0127 2653214</cbc:Telephone>
				<cbc:Telefax>0127 2653215</cbc:Telefax>
				<cbc:ElectronicMail>fred@iytcorporation.gov.uk</cbc:ElectronicMail>
			</cac:Contact>
		</cac:Party>
	</cac:DeliveryCustomerParty>
	<cac:Shipment>
		<cbc:ID>1</cbc:ID>
		<cac:Consignment>
			<cbc:ID>1</cbc:ID>
		</cac:Consignment>
		<cac:Delivery>
			<cac:DeliveryAddress>
				<cbc:StreetName>Avon Way</cbc:StreetName>
				<cbc:BuildingName>Thereabouts</cbc:BuildingName>
				<cbc:BuildingNumber>56A</cbc:BuildingNumber>
				<cbc:CityName>Bridgtow</cbc:CityName>
				<cbc:PostalZone>ZZ99 1ZZ</cbc:PostalZone>
				<cbc:CountrySubentity>Avon</cbc:CountrySubentity>
				<cac:AddressLine>
					<cbc:Line>3rd Floor, Room 5</cbc:Line>
				</cac:AddressLine>
				<cac:Country>
					<cbc:IdentificationCode>GB</cbc:IdentificationCode>
				</cac:Country>
			</cac:DeliveryAddress>
			<cac:RequestedDeliveryPeriod>
				<cbc:StartDate>2005-06-20</cbc:StartDate>
				<cbc:StartTime>10:30:47.0Z</cbc:StartTime>
				<cbc:EndDate>2005-06-21</cbc:EndDate>
				<cbc:EndTime>10:30:47.0Z</cbc:EndTime>
			</cac:RequestedDeliveryPeriod>
		</cac:Delivery>
	</cac:Shipment>
	<cac:DespatchLine>
		<cbc:ID>1</cbc:ID>
		<cbc:Note>Mrs Green agreed to waive charge</cbc:Note>
		<cbc:LineStatusCode>NoStatus</cbc:LineStatusCode>
		<cbc:DeliveredQuantity unitCode="KGM">90</cbc:DeliveredQuantity>
		<cbc:BackorderQuantity unitCode="KGM">10</cbc:BackorderQuantity>
		<cbc:BackorderReason>lack of stock as explained on telephone today</cbc:BackorderReason>
		<cac:OrderLineReference>
			<cbc:LineID>1</cbc:LineID>
			<cbc:SalesOrderLineID>A</cbc:SalesOrderLineID>
			<cac:OrderReference>
				<cbc:ID>AEG012345</cbc:ID>
				<cbc:SalesOrderID>CON0095678</cbc:SalesOrderID>
				<cbc:UUID>6E09886B-DC6E-439F-82D1-7CCAC7F4E3B1</cbc:UUID>
				<cbc:IssueDate>2005-06-20</cbc:IssueDate>
			</cac:OrderReference>
		</cac:OrderLineReference>
		<cac:Item>
			<cbc:Description>Acme beeswax</cbc:Description>
			<cbc:Name>beeswax</cbc:Name>
			<cac:BuyersItemIdentification>
				<cbc:ID>6578489</cbc:ID>
			</cac:BuyersItemIdentification>
			<cac:SellersItemIdentification>
				<cbc:ID>17589683</cbc:ID>
			</cac:SellersItemIdentification>
			<cac:ItemInstance>
				<cac:LotIdentification>
					<cbc:LotNumberID>546378239</cbc:LotNumberID>
					<cbc:ExpiryDate>2010-01-01</cbc:ExpiryDate>
				</cac:LotIdentification>
			</cac:ItemInstance>
		</cac:Item>
	</cac:DespatchLine>
</DespatchAdvice>

Example 3: Invoice

<?xml version="1.0" encoding="UTF-8"?>
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
	xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
	xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:ID>123</cbc:ID>
  <cbc:IssueDate>2011-09-22</cbc:IssueDate>
  <cac:InvoicePeriod>
    <cbc:StartDate>2011-08-01</cbc:StartDate>
    <cbc:EndDate>2011-08-31</cbc:EndDate>
  </cac:InvoicePeriod>
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cac:PartyName>
        <cbc:Name>Custom Cotter Pins</cbc:Name>
      </cac:PartyName>
    </cac:Party>
  </cac:AccountingSupplierParty>
  <cac:AccountingCustomerParty>
    <cac:Party>
      <cac:PartyName>
        <cbc:Name>North American Veeblefetzer</cbc:Name>
      </cac:PartyName>
    </cac:Party>
  </cac:AccountingCustomerParty>
  <cac:LegalMonetaryTotal>
     <cbc:PayableAmount currencyID="CAD">100.00</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>
  <cac:InvoiceLine>
    <cbc:ID>1</cbc:ID>
    <cbc:LineExtensionAmount currencyID="CAD">100.00</cbc:LineExtensionAmount>
    <cac:Item>
       <cbc:Description>Cotter pin, MIL-SPEC</cbc:Description>
    </cac:Item>
  </cac:InvoiceLine>
</Invoice>

Integrated Digital Trade Project(25T1)