ubl:Invoice

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. Identifying the customization/implementation guide/contextualization of the syntax message and its extension that applies to the invoice transaction, enables the receiver to apply the correct validation to the received document as well as to route the document to an appropriate service for processing.

Example value: urn:www.cenbii.eu:transaction:biitrns010:ver2.0:extended:urn:www.peppol.eu:bis:peppol5a:ver2.0:extended:urn:www.difi.no:ehf:faktura:ver2.0

Profile identifier
Identifies the BII profile or business process context in which the transaction appears. Identifying the profile or business process context in which the transaction appears enables the buyer to direct the message to an appropriate service as well as controlling its relation to other documents exchanged as part of the same process.

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

Invoice identifier
An invoice instance must contain an identifier. An invoice identifier enables positive referencing the document instance for various purposes including referencing between documents that are part of the same process.

Example value: 123456

Issue Date
The issue date of an invoice is required by EU directives as well as country laws. An invoice must therefore contain the date on which it was issued. Format YYYY-MM-DD.

Invoice type code
A code that identifies the functional type of the invoice instance, such as commercial invoice, pro-forma invoice, final invoice. A code that identifies that the invoice is a commercial invoice.

Example value: 380

Note
The textual note provides the seller a means for providing unstructured information that is relevant to the invoice. This can be notes or other similar information for which the invoice specification does not contain suitable qualified elements. Information given in as textual notes is mainly intended for manual processing. When “invoice clauses” or “declarations” are used they should be stated in full in the note element.

Example value: Bestilt pr. telefon

Tax point date
The date applicable VAT.

Document currency code
The currency in which the monetary amounts are stated must be stated in the invoice. Code from ISO4217.

VAT currency code
Currency code for VAT in local currency, must be filled if the invoice currency is not NOK.

Accounting cost
The invoice may contain a reference to the buyer's accounting code applied to the invoice as a whole, expressed as text rather than a code in order to facilitate automation in booking into accounts following an order to invoice transformation.

Example value: Project cost code 123

Period
For invoices that charge for services or items delivered over a time period, such as subscriptions or metered services, an invoice may contain information about the date period to which the invoice applies.

Order
An association to order reference.

Contract
Reference to contract or framework agreement.

Additional document reference
Reference to additional documents.

Supplier
Organisation or person responsible som delivering the goods and services.

Customer
Customer party.

Payee
An association to the Payee. Used for factoring invoices.

Tax representative
Information regarding the tax representative of the supplier.

Delivery
Delivery details

Payment means
Details regarding how the invoice will be payed

Payment terms
Description of payment terms.

Allowance charge
Description of allowances and charges on document level.

Tax exchange rate
Exchange rate for calculation of tax in home currency, mandatory if DocumentCurrencyCode is not = NOK.

Tax total
Specification of tax total and tax per tax category.

Totals
Specifications of monetary totals.

Invoice line
An association to one or more invoice lines.