ubl:OrderResponse

UBL VersionID
Identifies the UBL version on which the transaction instance is based.

Fixed value: 2.1

Customization identifier
Identifies the specification of content and rules that apply to the transaction.

Example value: urn:www.cenbii.eu:transaction:biitrns076:ver2.0:extended:urn:www.peppol.eu:bis:peppol28a:ver1.0:extended:urn:www.difi.no:ehf:ordrebekreftelse:ver1.0

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

Example value: urn:www.cenbii.eu:profile:bii28:ver2.0

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: 12

Order response issue date
The date on which the transaction instance was issued. Format YYYY-MM-DD

Example value: 2012-10-01

Order response issue time
The time assigned by the buyer on which the order was issued.

Example value: 12:00:00

Response code
A code that indicates whether the referenced order as whole is Accepted or Rejected or, alternatively, Accepted with change. If response code is Accept or Reject there may not be any response lines. Valid codes are: 29 (Accepted), 27 (Rejected) and 30 (Accepted with change).

Example value: 30

Response clarification
Clarification of the suppliers decision.

Example value: Endring på 2 linjer.

Document currency
The default currency for the offer.

Example value: NOK

Order reference
Order reference information.

Seller
Information about Seller.

Buyer
Information about Buyer.

Deliver
Delivery information.

Order line
Order lines are only sent if Action code on header level is Accepted with change.