OIOUBL BIS Self-Billing with Response
v3.0.0 RC
The Business Interoperability Specification, called the “OIOUBL BIS” from here on, has been developed by the Danish Business Authority.
1. Document Structure
This document is structured as follows:
-
Chapter 1 Describes the structure of the document, and its interaction with OIOUBL BIS Billing with Response
-
Chapter 2 Describes the ways in which the Self-Billing business process differs from the invoicing process
-
Chapter 3 Provides special rules and considerations for specific data fields in the OIOUBL Self-Billing document
-
Chapter 4 Statement of license and copyright
-
Chapter 5 Link to the main site for additional documentation.
1.1. Interaction with OIOUBL BIS Billing with Response
The Self-Billing Invoice is based on the BIS Billing with Response. For this reason, the BIS only lists the ways in which the Reminder deviates from the OIOUBL BIS Billing with Response. Where a feature is not mentioned in this BIS, it operates in the same manner as in an invoice of the relevant invoice type code.
2. Business Processes
2.1. Self-Billing invoicing processes
The ordinary invoicing process has a seller or creditor sending an invoice document to the buyer or debtor. Upon receipt of this document, the buyer/debtor may issue an invoice response document, indicating their acceptance, rejection or reservations with respect to the received invoice.
The Self-Billing process is the same, save that it is the buyer/debtor who generates the invoice document and sends it to the seller/creditor.
3. Descriptions and Examples of Selected Elements of the Self-Billing Invoice
In the subchapters below you find examples of selected elements of the transaction. As elsewhere in this BIS; only the ways in which the usage differs from the Invoice BIS are covered here.
3.1. ProfileID and InvoiceTypeCode
The Reminder uses the following identifiers:
-
ProfileID: urn:fdc:oioubl.dk:bis:selfbilling_with_response:3
-
InvoiceTypeCode: 389
-
CreditNoteTypeCode: 261
An Invoice Response that refers to an OIOUBL Reminder uses the same ProfileID, but does not have a distinct document type code.