Copyright © 2003 OASIS
$Date: 2003/10/24 01:33:53 $(UTC)
Table of Contents
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.
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.
Example renderings:
PDF printable format (A4 page size)
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 stylesheets.
The following information is unrelated to the visible fields of the form.
Header information is associated with the form as a whole, not to the individual items of goods.
Table 2. XPath information
| XPath addresses |
| /po:Invoice/cat:SellerParty/cat:PartyName/cat:Name |
| /po:Invoice/cat:SellerParty/cat:Address/cat:Street |
| /po:Invoice/cat:SellerParty/cat:Address/cat:CityName |
| /po:Invoice/cat:SellerParty/cat:Address/cat:CountrySub‑EntityCode |
| /po:Invoice/cat:SellerParty/cat:Address/cat:Country/cat:Code |
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.
The reference number is a number or designation preferably common throughout each set of documents.
If not otherwise specified, "date" means the date of issue of the document in which it appears.
May reference any contract that covers this order
Table 7. XPath information
| XPath addresses |
| /in:Invoice/cat:Quote/cat:ID |
| /in:Invoice/cat:Contract/cat:ID |
May reference any contract or quote that covers this invoice
The field for the name and address of the consignee has been located in conformity with international postal specifications so as to allow the use of window envelopes.
The contents of this field is the same as the Section 3.8, “Buyer” field.
Table 8. XPath information
| XPath addresses |
| /in:Invoice/cat:BuyerParty/cat:PartyName/cat:Name |
| /in:Invoice/cat:BuyerParty/cat:Address/cat:Street |
| /in:Invoice/cat:BuyerParty/cat:Address/cat:CityName |
| /in:Invoice/cat:BuyerParty/cat:Address/cat:CountrySub‑EntityCode |
| /in:Invoice/cat:BuyerParty/cat:Address/cat:Country/cat:Code |
The field for the name and address to which documents are sent (buyer).
Transportation fields that are header-like and not generally applicable to the invoice.
Line item information is associated with the individual items of the goods in the invoice
At this time this field is not being used in the Invoice.
This is the reference to the Invoice line.
One of these exists for each Line item.
One of these exists for each line item.
Summary information is associated with the form as a whole, not to the individual items of goods.
Table 18. XPath information
| XPath addresses |
| /in:Invoice/cat:PaymentTerms/cat:ID |
| /in:Invoice/cat:PaymentTerms/cat:Note |
| /in:Invoice/cat:PaymentTerms/cat:FromEventCode |
| /in:Invoice/cat:PaymentTerms/cat:SettlementDiscountRateNumeric |
| /in:Invoice/cat:PaymentTerms/cat:PenaltySurchargeRateNumeric |
| /in:Invoice/cat:PaymentTerms/cat:SettlementPeriod/cat:StartDateTimeDate |
| /in:Invoice/cat:PaymentTerms/cat:SettlementPeriod/cat:EndDateTimeDate |
| /in:Invoice/cat:PaymentTerms/cat:SettlementPeriod/cat:DurationMeasure |
| /in:Invoice/cat:PaymentTerms/cat:SettlementPeriod/cat:DescriptionCode |
| /in:Invoice/cat:PaymentTerms/cat:PenaltyPeriod/cat:StartDateTimeDate |
| /in:Invoice/cat:PaymentTerms/cat:PenaltyPeriod/cat:EndDateTimeDate |
| /in:Invoice/cat:PaymentTerms/cat:PenaltyPeriod/cat:DurationMeasure |
| /in:Invoice/cat:PaymentTerms/cat:PenaltyPeriod/cat:DescriptionCode |
Section 6.1, “Invoice clauses” - Note
How should multiple invoice clauses be formatted?