ubl:OrderResponse

Specification identification
BEAst: This document describes the BEAst profile, and how BEAst's order response messages, version 3.1, for NeC, Rental and Material are linked to the Peppol structure. Peppol: Identifies the specification of content and rules that apply to the transaction.

Example value: urn:fdc:peppol.eu:poacc:trns:order_response:3

Business process type identifier
Identifies the BII profile or business process context in which the transaction appears.

Fixed value: urn:fdc:peppol.eu:poacc:bis:ordering:3

Order response identifier
BEAst: T3345, Order response number. Peppol: A transaction instance must have an identifier. The identifier enables referencing the transaction for various purposes such as from other transactions that are part of the same process.

Example value: 101

Sales order reference
BEAst: T6099, Supplier's Order number. Peppol: An identifier of a referenced sales order, issued by the Seller.

Example value: 101-111

Order response issue date
BEAst: T6325, Document Date/Time. Peppol: The date on which the transaction instance was issued.

Example value: 2021-07-01

Order response issue time
BEAst: T6325, Document Date/Time. Peppol: The time on which the transaction instance was issued

Example value: 06:10:10

Response code
BEAst: T6114, Order response status. Peppol: A code that indicates whether the referenced order has been received and not yet processed, or is Accepted or Rejected as whole, alternatively, Accepted with change or already delivered.If response code is Accept or Reject there may not be any response lines.

Example value: CA

Response clarification
BEAst: T6008 and T6038, Transport information or Supplier's remark. Peppol: Clarification of the suppliers decision.

Example value: Response message with amendments in the details

Document currency
BEAst: T6018, Order Currency. Peppol: The default currency for the offer.

Example value: EUR

Buyer reference identifier
BEAst: T6004, Project number. Peppol: An identifier assigned by the Buyer used for internal routing purposes.The identifier is defined by the buyer (contact ID, department, office id, project code), but provided by the seller in the order response.

Example value: ABC-123

Order reference
BEAst: The order response message always is preceeded by an order message. If the order response is a confirmation of something ordered by telephone, in a shop or a supplier portal, the Peppol message OrderAgreement should be used instead.

Seller information

Buyer information

Delivery information
BEAst: Confirmation of delivery dates are always at line level, not here.

Specification of order lines
BEAst: Orderlines should be included in the order response only when the OrderResponseCode is "CA" (Conditionally Accepted). For all other codes only the document header should be sent. When the order is Conditionally Accepted, all orderlines shall be included, not only those that are changed.