OIOUBL BIS Reminder 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 Reminder business process differs from the invoicing process
-
Chapter 3 Provides special rules and considerations for specific data fields in the OIOUBL Reminder
-
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
Unlike previous versions of OIOUBL, OIOUBL 3 casts the Reminder as a replacement invoice, with a few restrictions or additional properties. Partly this is to reduce complexity, by allowing re-use of the invoice specification, and partly it is a reflection of the way reminders function in Danish practice.
For this reason, this BIS only lists the ways in which the Reminder deviates from an ordinary type of invoice it replaces. Where a feature is not mentioned in this BIS, it operates in the same manner as in an invoice of the invoice type code that it replaces.
| The schematron rules for Reminder follow 380:Commercial Invoice, regardless of the invoice type code of the underlying invoice. This means that special rules (e.g. PayeeParty being mandatory in a Factored Invoice) are not schematron-enforced in Reminders. Reminders should still adhere to these requirements, in order to be semantically valid. |
2. Business Processes
2.1. General reminder processes
The reminder differs from the invoice in that a reminder must always be based on at least one preceding invoice, which is unpaid, overdue and undisputed.
A reminder can consolidate several preceding invoices and/or credit notes, provided that:
-
Each invoice or credit note in the consolidation is a valid preceding invoice for a reminder.
-
All invoices or credit notes in the consolidation share all data points which can be provided only once in the invoice document type (e.g. a reminder cannot consolidate two invoices with different PayeeParty). Document type code is an exception to this, as the Reminder replaces the original invoice or credit note type code(s).
-
All invoices or credit notes in the consolidation have the same legal status in terms of debt collection proceedings (e.g. referred to debt collection).
3. Descriptions and Examples of Selected Elements of the Reminder
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:reminder_with_response:3
-
InvoiceTypeCode: 71
An Invoice Response that refers to an OIOUBL Reminder uses the same ProfileID, but does not have a distinct document type code.
3.2. ProfileID and InvoiceTypeCode
BillingReference is mandatory in the OIOUBL Reminder (i.e. cardinality is 1..n rather than 0..n).
3.3. PaymentDueDate
The PaymentDueDate of the reminder must be the date at which the creditor will take further action on the claim, not the original due date.
3.4. AllowanceCharge
Under certain circumstances, Danish law permits creditors to charge certain fees in connection with issuing reminders (rykkergebyr). Such fees should be indicated with document-level AllowanceCharges.
3.5. InvoiceLine
If the reminder is based on only one invoice, it is strongly recommended to enumerate the invoice lines in the same order and with the same IDs as in the original. Where the reminder consolidates (parts of) multiple invoices, this is obviously impractical, but it is recommended to order the lines in some structured manner (e.g. by prefacing the original invoice lines by '1' for the first invoice, '2' for the second, etc.).
3.6. Example of usage of reminder
<cbc:UBLVersionID>2.1</cbc:UBLVersionID>
<cbc:CustomizationID>urn:fdc:oioubl.dk:trns:billing:invoice:3.0</cbc:CustomizationID>
<cbc:ProfileID>urn:fdc:oioubl.dk:bis:reminder_with_response:3</cbc:ProfileID>(1)
<cbc:ID>R-202400095678</cbc:ID>
<cbc:IssueDate>2025-05-20</cbc:IssueDate>
<cbc:DueDate>2025-05-31</cbc:DueDate>
<cbc:InvoiceTypeCode>71</cbc:InvoiceTypeCode>(2)
<cac:BillingReference>
<cac:InvoiceDocumentReference>
<cbc:ID>2025-006</cbc:ID>
<cbc:IssueDate>2025-05-01</cbc:IssueDate>
</cac:InvoiceDocumentReference>
</cac:BillingReference>| 1 | Profile ID for Reminder |
| 2 | Invoice Type Code for Reminder - value 71 for Invoice Type Code |
3.6.1. Example of usage of reminder with reference to both invoice and credit note
<cac:BillingReference>
<cac:InvoiceDocumentReference>
<cbc:ID>2025-006</cbc:ID>(1)
<cbc:IssueDate>2025-05-01</cbc:IssueDate>(2)
</cac:InvoiceDocumentReference>
</cac:BillingReference>
<cac:BillingReference>
<cac:InvoiceDocumentReference>
<cbc:ID>2025-007</cbc:ID>
<cbc:IssueDate>2025-05-05</cbc:IssueDate>
</cac:InvoiceDocumentReference>
</cac:BillingReference>| 1 | Original invoice number |
| 2 | Original invoice issue date |