ubl:OrderResponse

Specification identification
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
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: or0987

Sales order reference
An identifier of a referenced sales order, issued by the Seller.

Example value: 112233

Order response issue date
The date on which the transaction instance was issued.

Example value: 2018-05-15

Order response issue time
The time on which the transaction instance was issued

Example value: 09:23:56

Response code
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: AP

Response clarification
Clarification of the suppliers decision.

Document currency
The default currency for the offer.

Example value: EUR

Buyer reference identifier
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: abc123

Order reference

Seller information

Buyer information

Delivery information

Specification of order lines