UN layout formatting specification for UBL Invoice instances

$Date: 2003/11/18 15:40:44 $(UTC)


Table of Contents

1. Invoice formatting specification
1.1. Status
1.2. Example renderings and implementations
1.3. Layout order and information
1.4. Namespaces
2. Miscellaneous information
2.1. Document header information
3. Party information
3.1. Seller
3.2. Invoice number
3.3. Invoice date (tax point)
3.4. Seller's reference
3.5. Buyer's reference
3.6. Purchase order date
3.7. Consignee
3.8. Buyer
3.9. Country of origin
3.10. Country of destination
4. Delivery and transport
4.1. Mode of transport
4.2. Date of despatch
4.3. Means of transport
4.4. Place of despatch
4.5. Place of loading
4.6. Place of discharge
4.7. Place of delivery
5. Financial information
5.1. Buyer's bank
5.2. Terms of payment
5.3. Currency of payment
5.4. Seller's bank
5.5. Sort code
5.6. Account number
5.7. Account name
6. Consignment information
6.1. Shipping marks
6.2. Container nr.
6.3. Number and kind of packages; description of goods
6.4. Total gross weight (Kg)
6.5. Cube m3
7. Line item information
7.1. Item / References
7.2. Description
7.3. Country of origin
7.4. Commodity code
7.5. Quantity U/M
7.6. Unit price
7.7. Amount
8. Summary information
8.1. Invoice clauses
8.2. Total amount
8.3. Total tax amount
8.4. Total amount due
8.5. Name of signatory
8.6. Place and date of issue
8.7. Signature

1.  Invoice formatting specification

This formatting specification describes a rendering of the UBL Invoice document model according to the United Nations Layout Key for Trade Documents guidelines for application for the 380 invoice form:

  • 380 Commercial Invoice: Document claiming payment for goods supplied under conditions agreed between seller and buyer.

For a list of all formatting specifications and an overview of the documentation conventions, please visit the formatting specification home page.

1.1.  Status

This specification has no formal status at this time. It should not be considered a reference interpretation of UBL documents. Feedback is sought from users of stylesheets that implement this formatting specification regarding suggestions for change for consideration by the OASIS UBL committees for incorporation into these formatting specifications.

Presentational semantics may never be formalized or normative in the UBL project due to differing international requirements and conventions for the presentation of information found in business documents. This document contains only examples from a few of what will probably be many available UBL stylesheet libraries.

1.2.  Example renderings and implementations

Example renderings:

1.3.  Layout order and information

Items in this formatting specification are ordered roughly from the laid out fields on the form in the order left-to-right, top to bottom.

Certain descriptions are verbatim quotes from the United Nations guidelines document.

Important: the rendering of a number of fields is very simplified, reflecting a Western European interpretation of a subset of fields (as in names and addresses). User requirements need to be better understood for the level of granularity in these formatting specifications.

1.4.  Namespaces

The following namespaces are mapped to the prefixes in the expressions below:

  • xmlns:in="urn:oasis:names:tc:ubl:Invoice:1:0-beta"

  • xmlns:cat="urn:oasis:names:tc:ubl:CommonAggregateTypes:1:0-beta"

2.  Miscellaneous information

The following information is unrelated to the visible fields of the form.

2.1.  Document header information

Table 1. XPath information

XPath addresses
/​in:Invoice/​cat:ID
/​in:Invoice/​cat:IssueDate

This information shows up in the window-title bar of the HTML browser, and in the document title supported by some XSL-FO processors.

3. Party information

Header information is associated with the form as a whole, not to the individual items of goods.

3.1. Seller

Table 2. XPath information

XPath addresses
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:PartyName/​cat:Name
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Address/​cat:StreetName
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Address/​cat:CityName
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Address/​cat:CountrySubentity
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Address/​cat:PostalZone
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Address/​cat:Country/​cat:Name

This field is intended to show the name and address of the sender of goods or the originator of the documents, as the case may be.

3.2. Invoice number

Table 3. XPath information

XPath address
/​in:Invoice/​cat:ID

This number is a unique number assigned to the invoice by the seller.

3.3. Invoice date (tax point)

Table 4. XPath information

XPath address
/​in:Invoice/​in:TaxPointDate

This field states the date of the invoice for tax purposes

3.4. Seller's reference

Table 5. XPath information

XPath address
/​in:Invoice/​cat:OrderReference/​cat:SellersID

This field provides a seller assigned reference to the order corresponding to this invoice.

3.5. Buyer's reference

Table 6. XPath information

XPath address
/​in:Invoice/​cat:OrderReference/​cat:BuyersID

This field provides the buyer's reference to the original order.

3.6. Purchase order date

Table 7. XPath information

XPath address
/​in:Invoice/​cat:OrderReference/​cat:IssueDate

This fields provides the issue date of the original order

3.7. Consignee

Currently the contents of this field is the same as the Section 3.8, “Buyer” field.

3.8. Buyer

Table 8. XPath information

XPath addresses
/​in:Invoice/​cat:BuyerParty/​cat:Party/​cat:PartyName/​cat:Name
/​in:Invoice/​cat:BuyerParty/​cat:Party/​cat:Address/​cat:StreetName
/​in:Invoice/​cat:BuyerParty/​cat:Party/​cat:Address/​cat:CityName
/​in:Invoice/​cat:BuyerParty/​cat:Party/​cat:Address/​cat:CountrySubentity
/​in:Invoice/​cat:BuyerParty/​cat:Party/​cat:Address/​cat:PostalZone
/​in:Invoice/​cat:BuyerParty/​cat:Party/​cat:Address/​cat:Country/​cat:Name

These fields are used to provide the name and address of the buyer of the goods involved in the transaction.

3.9. Country of origin

At this time this field is not being used in the invoice.

3.10. Country of destination

At this time this field is not being used in the invoice.

4. Delivery and transport

Transportation fields are header-like information and are applicable to the entire order.

4.1. Mode of transport

At this time this field is not being used in the invoice.

4.2. Date of despatch

At this time this field is not being used in the invoice.

4.3. Means of transport

At this time this field is not being used in the invoice.

4.4. Place of despatch

At this time this field is not being used in the invoice.

4.5. Place of loading

At this time this field is not being used in the invoice.

4.6. Place of discharge

At this time this field is not being used in the invoice.

4.7. Place of delivery

At this time this field is not being used in the invoice.

5. Financial information

The financial information provides details of the buyer and seller account details.

5.1. Buyer's bank

Table 9. XPath information

XPath addresses
/​in:Invoice/​cat:PaymentMeans/​cat:PayerFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Name
/​in:Invoice/​cat:PaymentMeans/​cat:PayerFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:StreetName
/​in:Invoice/​cat:PaymentMeans/​cat:PayerFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:CityName
/​in:Invoice/​cat:PaymentMeans/​cat:PayerFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:CountrySubentity
/​in:Invoice/​cat:PaymentMeans/​cat:PayerFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:PostalZone
/​in:Invoice/​cat:PaymentMeans/​cat:PayerFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:Country/​cat:Name

These fields provide the name and address of the buyer's bank.

5.2. Terms of payment

Table 10. XPath information

XPath addresses
/​in:Invoice/​cat:PaymentTerms/​cat:PenaltyPeriod/​cat:DurationMeasure
/​in:Invoice/​cat:PaymentTerms/​cat:PenaltyPeriod/​cat:DurationMeasure/​@unitCode
/​in:Invoice/​cat:PaymentTerms/​cat:PenaltyPeriod/​cat:StartDateTime
/​in:Invoice/​cat:PaymentTerms/​cat:Note

These fields provide information relating to the payment terms.

5.3. Currency of payment

Table 11. XPath information

XPath address
/​in:Invoice/​in:InvoiceCurrencyCode

This specifies the payment currency for the entire invoice.

5.4. Seller's bank

Table 12. XPath information

XPath addresses
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Name
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:StreetName
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:CityName
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:CountrySubentity
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:PostalZone
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:FinancialInstitutionBranch/​cat:FinancialInstitution/​cat:Address/​cat:Country/​cat:Name

These fields provide the name and address of the seller's bank.

5.5. Sort code

Table 13. XPath information

XPath address
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:FinancialInstitutionBranch/​cat:ID

This field contains the sort code for the seller's bank.

5.6. Account number

Table 14. XPath information

XPath address
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:ID

This field contains the seller's account number.

5.7. Account name

Table 15. XPath information

XPath address
/​in:Invoice/​cat:PaymentMeans/​cat:PayeeFinancialAccount/​cat:Name

This field contains the seller's account name.

6. Consignment information

The consignment information holds generic details and totals relating to all the goods items in the invoice.

6.1. Shipping marks

At this time this field is not being used in the invoice.

6.2. Container nr.

At this time this field is not being used in the Invoice.

6.3. Number and kind of packages; description of goods

At this time this field is not being used in the Invoice.

6.4. Total gross weight (Kg)

At this time this field is not being used in the Invoice.

6.5. Cube m3

At this time this field is not being used in the Invoice.

7. Line item information

Line item information is associated with the individual item of goods in the invoice

7.1. Item / References

Table 16. XPath information

XPath addresses
/​in:Invoice/​cat:InvoiceLine/​cat:OrderLineReference/​cat:BuyersLineID
b/​in:Invoice/​cat:InvoiceLine/​cat:OrderLineReferenc/​cat:SellersLineID

The first reference is the buyer's assigned reference to the line item.

The second reference is the seller's assigned reference to the line item.

7.2. Description

Table 17. XPath information

XPath address
/​in:Invoice/​cat:InvoiceLine/​cat:Item/​cat:Description

This provides a free text description of the line item.

7.3. Country of origin

Table 18. XPath information

XPath address
/​in:Invoice/​cat:InvoiceLine/​cat:Item/​cat:OriginCountry/​cat:Name

This field is used to provide to country of origin for the line item.

7.4. Commodity code

Table 19. XPath information

XPath address
/​in:Invoice/​cat:InvoiceLine/​cat:Item/​cat:CommodityClassification/​cat:CommodityCode

This field is used to provide the commodity code for the line item.

7.5. Quantity U/M

Table 20. XPath information

XPath address
/​in:Invoice/​cat:InvoiceLine/​cat:InvoicedQuantity

This fields states the number of items invoiced for the line item.

7.6. Unit price

Table 21. XPath information

XPath address
/​in:Invoice/​cat:InvoiceLine/​cat:Item/​cat:BasePrice/​cat:PriceAmount

This field is used to specify the unit price of the line item.

7.7. Amount

Table 22. XPath information

XPath address
/​in:Invoice/​cat:InvoiceLine/​cat:LineExtensionAmount

This field states the actual line item amount which will be quantity mutiplied by the unit price, the result is not calculated it will be transmitted.

8. Summary information

Summary information is associated to the entire invoice and not to any individual line item.

8.1. Invoice clauses

Table 23. XPath information

XPath address
/​in:Invoice/​cat:Note

This notes field is used for any free text information that relates to the entire invoice, for specific invoice clauses or declarations.

8.2. Total amount

Table 24. XPath information

XPath addresses
/​in:Invoice/​in:InvoiceCurrencyCode
/​in:Invoice/​cat:LegalTotal/​cat:LineExtensionTotalAmount

Two data fields populate this one form field: the currency and the total amount.

NB The total amount is the total of all the individual line items and is not calculated it will be transmitted

8.3. Total tax amount

Table 25. XPath information

XPath address
/​in:Invoice/​cat:TaxTotal/​cat:TotalTaxAmount

This fields provides details of any tax associated to the entire invoice, this amount will not be calculated it will be transmitted

8.4. Total amount due

Table 26. XPath information

XPath addresses
/​in:Invoice/​in:InvoiceCurrencyCode
/​in:Invoice/​cat:LegalTotal/​cat:ToBePaidTotalAmount

Two data fields populate this one form field: the currency and the total amount.

This fields specifies the amount to be paid and will not be calculated it will be transmitted.

8.5. Name of signatory

Table 27. XPath information

XPath address
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Contact/​cat:Name

This fields identified the name of the signatory.

8.6. Place and date of issue

Table 28. XPath information

XPath addresses
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Address/​cat:CityName
/​in:Invoice/​cat:SellerParty/​cat:Party/​cat:Address/​cat:CountrySubentity
/​in:Invoice/​cat:IssueDate

The above fields provide information relating to the date and place of issue of the invoice.

8.7. Signature

This field is not currently being filled automatically as it is a manual entry.