## UN layout formatting specification for UBL Receipt Advice instances

Copyright © 2004 OASIS

$Date: 2004/10/22 15:12:47 $(UTC)

## 1. Receipt advice formatting specification

This formatting specification describes a rendering of the UBL Receipt Advice document model numbered according to the United Nations Layout Key for Trade Documents guidelines for application for the 632 Goods Receipt form:

- 632 Goods receipt: Document issued by a port, warehouse/shed, or terminal operator acknowledging receipt of goods specified therein on conditions stated or referred to in the document.

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 rendering

The following is an example rendering that illustrates the position and decoration of the information items found in an instance of the document type:

- PDF printable format (A4 page size)

  - `UN632ReceiptAdvice.Example-a4.pdf`

- PDF printable format (US-letter page size)

  - `UN632ReceiptAdvice.Example-us.pdf`

### 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:ra="urn:oasis:names:specification:ubl:schema:xsd:ReceiptAdvice-1.0"`

- `xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-1.0"`

- `xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-1.0"`

## 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
`/​ra:ReceiptAdvice/​ra:ID`
`/​ra:ReceiptAdvice/​cbc: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. Main document and 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
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:PartyName/​cbc:Name`
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:BuildingNumber`
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:StreetName`
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:CityName`
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:CountrySubentity`
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:Address/​cac:CountrySubentityCode`
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:Address/​cbc:PostalZone`
`/​ra:ReceiptAdvice/​cac:SellerParty/​cac:Party/​cac:Address/​cac:Country/​cbc: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.

Note that only one of `cbc:CountrySubentity` and `cac:CountrySubentityCode` need be used, with preference to `cbc:CountrySubentity` if it exists.

### 3.2. Receipt advice reference

Table 3. XPath information

XPath address
`/​ra:ReceiptAdvice/​ra:ID`

This number is a unique number assigned to the receipt advice by the buyer.

### 3.3. Despatch advice reference

Table 4. XPath information

XPath address
`/​ra:ReceiptAdvice/​ra:DespatchDocumentReference/​cac:ID`

This number is the unique number assigned to the corresponding despatch advice by the seller.

### 3.4. Date

Table 5. XPath information

XPath address
`/​ra:ReceiptAdvice/​cbc:IssueDate`

This field states the date of the receipt advice.

### 3.5. Despatch advice date

Table 6. XPath information

XPath address
`/​ra:ReceiptAdvice/​ra:DespatchDocumentReference/​cbc:IssueDate`

This field provides the date of the corresponding despatch advice.

### 3.6. Buyer's reference

Table 7. XPath information

XPath address
`/​ra:ReceiptAdvice/​cac:OrderReference/​cac:BuyersID`

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

### 3.7. Other reference

At this time this field is not being used in the receipt advice.

### 3.8. Consignee

Table 8. XPath information

XPath addresses
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:PartyName/​cbc:Name`
`/​ra:ReceiptAdvice/​cac:Delivery/​cac:DeliveryAddress/​cbc:BuildingNumber`
`/​ra:ReceiptAdvice/​cac:Delivery/​cac:DeliveryAddress/​cbc:StreetName`
`/​ra:ReceiptAdvice/​cac:Delivery/​cac:DeliveryAddress/​cbc:CityName`
`/​ra:ReceiptAdvice/​cac:Delivery/​cac:DeliveryAddress/​cbc:CountrySubentity`
`/​ra:ReceiptAdvice/​cac:Delivery/​cac:DeliveryAddress/​cac:CountrySubentityCode`
`/​ra:ReceiptAdvice/​cac:Delivery/​cac:DeliveryAddress/​cbc:PostalZone`
`/​ra:ReceiptAdvice/​cac:Delivery/​cac:DeliveryAddress/​cac:Country/​cbc:Name`

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

Note that only one of `cbc:CountrySubentity` and `cac:CountrySubentityCode` need be used, with preference to `cbc:CountrySubentity` if it exists.

### 3.9. Buyer

Table 9. XPath information

XPath addresses
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:PartyName/​cbc:Name`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:BuildingNumber`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:StreetName`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CityName`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CountrySubentity`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cac:CountrySubentityCode`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:PostalZone`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cac:Country/​cbc:Name`

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

Note that only one of `cbc:CountrySubentity` and `cac:CountrySubentityCode` need be used, with preference to `cbc:CountrySubentity` if it exists.

## 4. Additional document and party information

### 4.1. Freight forwarder

Table 10. XPath information

XPath addresses
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:PartyName/​cbc:Name`
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:Address/​cbc:BuildingNumber`
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:Address/​cbc:StreetName`
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:Address/​cbc:CityName`
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:Address/​cbc:CountrySubentity`
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:Address/​cac:CountrySubentityCode`
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:Address/​cbc:PostalZone`
`/​ra:ReceiptAdvice/​ra:FreightForwarderParty/​cac:Address/​cac:Country/​cbc:Name`

These fields are used to provide the name and address of the freight forwarder involved in the transaction.

Note that only one of `cbc:CountrySubentity` and `cac:CountrySubentityCode` need be used, with preference to `cbc:CountrySubentity` if it exists.

### 4.2. Country of origin of goods

At this time this field is not being used in the receipt advice.

### 4.3. Country of destination

At this time this field is not being used in the receipt advice.

## 5. Delivery and transport

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

### 5.1. Mode of transport

At this time this field is not being used in the receipt advice.

### 5.2. Date of despatch

At this time this field is not being used in the receipt advice.

### 5.3. Means of transport

At this time this field is not being used in the receipt advice.

### 5.4. Place of despatch

At this time this field is not being used in the receipt advice.

### 5.5. Vessel/flight no. and date

At this time this field is not being used in the receipt advice.

### 5.6. Port/airport of loading

At this time this field is not being used in the receipt advice.

### 5.7. Port/airport of discharge

At this time this field is not being used in the receipt advice.

### 5.8. Place of delivery

At this time this field is not being used in the receipt advice.

### 5.9. Delivery requirements

At this time this field is not being used in the receipt advice.

## 6. Consignment information

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

### 6.1. Shipping marks; container number

At this time this field is not being used in the receipt advice.

### 6.2. Number and kind of packages; description of goods

At this time this field is not being used in the receipt advice.

### 6.3. Total gross weight (kg)

At this time this field is not being used in the receipt advice.

### 6.4. Total cube (m3)

At this time this field is not being used in the receipt advice.

### 6.5. Total net weight (kg)

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 receipt advice.

### 7.1. Item / Packages

Table 11. XPath information

XPath addresses
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cac:ID`
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cac:OrderLineReference/​cac:BuyersLineID`
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cac:OrderLineReference/​cac:SellersLineID`

The item field is the identification of the receipt line according to the buyer's system.

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 12. XPath information

XPath address
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cac:OrderedItemIdentification/​cac:PhysicalAttribute/​cbc:Description`

This provides a free text description of the line item.

### 7.3. Received quantity

Table 13. XPath information

XPath address
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cbc:ReceivedQuantity`

This field provides the number of received item for the line item.

### 7.4. Short quantity / Rejected quantity

Table 14. XPath information

XPath addresses
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cbc:ShortQuantity`
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cbc:RejectedQuantity`

These fields provide the recipients response to the items received.

The recipient will confirm the number of missing items OR the number of rejected items.

### 7.5. Reject reason

Table 15. XPath information

XPath address
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cac:RejectReasonCode`

This field provides the reason for a rejection, the rejection reason code should be translated into text for clarity.

### 7.6. Action

Table 16. XPath information

XPath addresses
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cac:ShortageActionCode`
`/​ra:ReceiptAdvice/​cac:ReceiptLine/​cac:RejectActionCode`

These fields provide the action to be taken for missing or rejected items, the shortage action code OR the rejection action code should be translated into text for clarity.

## 8. Summary information

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

### 8.1. Notes

Table 17. XPath information

XPath address
`/​ra:ReceiptAdvice/​cbc:Note`

This notes field is used for any free text information that relates to the entire receipt advice.

### 8.2. Name of signatory

Table 18. XPath information

XPath address
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Contact/​cbc:Name`

This field provides the name of signatory in the receipt advice.

### 8.3. Place and date of issue

Table 19. XPath information

XPath addresses
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CityName`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cbc:CountrySubentity`
`/​ra:ReceiptAdvice/​cac:BuyerParty/​cac:Party/​cac:Address/​cac:CountrySubentityCode`
`/​ra:ReceiptAdvice/​cbc:IssueDate`

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

Note that only one of `cbc:CountrySubentity` and `cac:CountrySubentityCode` need be used, with preference to `cbc:CountrySubentity` if it exists.

### 8.4. Signature

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

## 9. Continuation page

The continuation page comprises only a copy of the document identification information described in Section 3, “Main document and party information” and room for additional line item entries described in Section 7, “Line item information”.