Office-oriented formatting specification for UBL Invoice instances

Author: G. Ken Holman
Date: $Date: 2003/02/10 22:19:55 $(UTC)

Copyright © 2003 OASIS

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 Header information
3.1 Invoice number
3.2 Invoice Issue Date
3.3 Taxpoint Date
3.4 Order No.
3.5 Order Response No.
3.6 Issue date
3.7 Buyer
3.8 Seller
3.9 Contact
3.10 Billing Contact
3.11 Delivery address
3.12 Requested Delivery Date
4 Line item information
4.1 Line no.
4.2 Part number
4.3 Description
4.4 Quantity U/M
4.5 Unit price
4.6 Amount
5 Summary information
5.1 Tax Regime
5.2 Tax Type
5.3 Tax Rate
5.4 Tax Amount
5.5 Total
5.6 Payment Terms
5.7 Settlement Period
5.8 Period Event

1: Invoice formatting specification

This formatting specification describes a rendering of an instance of the UBL Order document model according to a conceptual office-oriented layout.

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:

Note the above examples are produced using Crane's XSLT and XSL-FO stylesheets. The HTML and XSL-FO are created by running the Saxon XSLT processor http://saxon.sourceforge.net/. The PDF is created by running the Antenna House XSL Formatter Version 2.3 http://www.AntennaHouse.com (with their gracious permission) to produce PostScript from XSL-FO and GhostScript AFPL http://www.GhostScript.com to distill PDF from the PostScript.

Example implementations:

These implementations must not be considered as reference implementations of UBL formatting specifications or as normative components of the UBL delivery; they are merely examples from what will probably be many available UBL stylesheet libraries.

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.

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.

1.4: Namespaces

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

2: Miscellaneous information

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

2.1: Document header information

Path
/​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: Header information

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

3.1: Invoice number

Path
/​in:Invoice/​cat:ID

3.2: Invoice Issue Date

Path
/​in:Invoice/​cat:IssueDate

3.3: Taxpoint Date

Path
/​in:Invoice/​in:TaxPointDate

3.4: Order No.

Path
/​in:Invoice/​cat:ReferencedOrder/​cat:BuyersOrderID

3.5: Order Response No.

Path
/​in:Invoice/​cat:ReferencedOrder/​cat:SellersOrderID

3.6: Issue date

Path
/​in:Invoice/​cat:ReferencedOrder/​cat:IssueDate

3.7: Buyer

Path
/​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
/​in:Invoice/​cat:BuyerParty/​cat:Address/​cat:PostalZone

3.8: Seller

Path
/​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
/​in:Invoice/​cat:SellerParty/​cat:Address/​cat:PostalZone

3.9: Contact

Path
/​in:Invoice/​cat:BuyerParty/​cat:BuyerContact/​cat:Name

3.10: Billing Contact

Path
/​in:Invoice/​cat:Quote/​cat:ID
/​in:Invoice/​cat:Contract/​cat:ID

May reference any contract or quote that covers this invoice

3.11: Delivery address

Path
/​in:Invoice/​cat:InvoiceLine/​cat:ReferencedOrderLine/​cat:DeliveryRequirement/​cat:DeliveryToAddress
/​in:Invoice/​cat:InvoiceLine/​cat:ReferencedOrderLine/​cat:DeliveryRequirement/​cat:DeliveryToAddress/​cat:Street
/​in:Invoice/​cat:InvoiceLine/​cat:ReferencedOrderLine/​cat:DeliveryRequirement/​cat:DeliveryToAddress/​cat:CityName
/​in:Invoice/​cat:InvoiceLine/​cat:ReferencedOrderLine/​cat:DeliveryRequirement/​cat:DeliveryToAddress/​cat:CountrySub-EntityCode
/​in:Invoice/​cat:InvoiceLine/​cat:ReferencedOrderLine/​cat:DeliveryRequirement/​cat:DeliveryToAddress/​cat:Country/​cat:Code
/​in:Invoice/​cat:InvoiceLine/​cat:ReferencedOrderLine/​cat:DeliveryRequirement/​cat:DeliveryToAddress/​cat:PostalZone

3.12: Requested Delivery Date

Path
/​in:Invoice/​cat:InvoiceLine/​cat:ReferencedOrderLine/​cat:DeliveryRequirement/​cat:DeliverySchedule/​cat:RequestedDeliveryDate

4: Line item information

Line item information is associated with the individual items of the goods in the order.

4.1: Line no.

Path
/​in:Invoice/​cat:InvoiceLine/​cat:Item/​cat:BuyersItemIdentification/​cat:ID

4.2: Part number

Path
/​in:Invoice/​cat:InvoiceLine/​cat:Item/​cat:SellersItemIdentification/​cat:ID

4.3: Description

Path
/​in:Invoice/​cat:InvoiceLine/​cat:Item/​cat:Description

4.4: Quantity U/M

Path
/​in:Invoice/​cat:InvoiceLine/​cat:InvoicedQuantity

4.5: Unit price

Path
/​in:Invoice/​cat:InvoiceLine/​cat:BasePrice/​cat:PriceAmount/​@currencyID
/​in:Invoice/​cat:InvoiceLine/​cat:BasePrice/​cat:PriceAmount

4.6: Amount

Path
/​in:Invoice/​cat:InvoiceLine/​cat:LineExtensionAmount/​@currencyID
/​in:Invoice/​cat:InvoiceLine/​cat:LineExtensionAmount

5: Summary information

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

5.1: Tax Regime

This field is not filled in at this time.

5.2: Tax Type

Path
/​in:Invoice/​cat:TaxTotal/​cat:TaxTypeCode

5.3: Tax Rate

Path
cat:TaxTotal/​cat:CategoryTotal/​cat:RatePercentNumeric

5.4: Tax Amount

Path
/​in:Invoice/​cat:TaxTotal/​cat:TaxAmounts/​cat:TaxAmount/​@currencyID
/​in:Invoice/​cat:TaxTotal/​cat:TaxAmounts/​cat:TaxAmount

5.5: Total

Path
/​in:Invoice/​cat:LegalTotals/​cat:ToBePaidTotalAmount/​@currencyID
/​in:Invoice/​cat:LegalTotals/​cat:ToBePaidTotalAmount

5.6: Payment Terms

Path
/​in:Invoice/​cat:PaymentTerms/​cat:Note

5.7: Settlement Period

Path
/​in:Invoice/​cat:PaymentTerms/​cat:SettlementPeriod/​cat:DescriptionCode

5.8: Period Event

Path
/​in:Invoice/​cat:PaymentTerms/​cat:FromEventCode

Office-oriented formatting specification for UBL Invoice instances
G. Ken Holman
Copyright © 2003 OASIS
$Date: 2003/02/10 22:19:55 $(UTC)