> This page is for Product Documentation.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Set up OIO UBL

> To send sales invoices, credit memos, finance charge memos, and reminders to the Danish public sector electronically, you first need to perform certain configurations in Business Central.

1. Search for **Document Sending Profiles**, and select the related link.
2. Open the **OIOUBL** profile, and select **Through Exchange Service** in the **Electronic Document** field.
3. Navigate to the **NP OIOUBL Setup** administrative section.

> **Note:** When the **Enabled** toggle switch is disabled, the files will be downloaded instead of being sent to the public sector. The file will also never be sent on the Demo, Test, and Sandbox environments - it will always be downloaded in the browser.

4. Open the **Actions** dropdown, click **Setup Pages**, followed by **Electronic Document Formats**.
5. Set the necessary codeunit - 6060015.

![oio\_ubl\_codeunit](/_fern-img/8ec19726f51abb4817a9def515221c20b3335e24d5e6b2900d3dcb72e7cc806f.webp)

6. Open the **Customer Card** used for sending the documents with the OIO UBL extension.
7. Populate the following fields:
   * **Document Sending Profile**
   * **VAT Registration No.** in the following format: \[DK]\[VAT registration number] e.g. *DK123121562*
   * **GLN**
   * **Profile Code**
8. Enable the **Use GLN in Electronic Documents** toggle switch.
9. Navigate to the **Profile List**, and create a profile with the **BILSIM** code.
10. Navigate to the **Currencies** administrative section, and make sure the currencies you're using have the OIO UBL **Currency Code** filled in.

![oio\_ubl\_currencies](/_fern-img/4a8dbe5e0a35005fda8854701ee77bd813fd87963369ac93bc121c980e4e9595.webp)

11. If you're sending sales documents, make sure the following fields are populated in them: **External Document**, **VAT Number** and **Contact**.\
    If some of these are missing, an error will occur.
12. Once everything is set correctly, send the documents with the **Post & Send** action.
13. Confirm the destination to which the document is about to be sent.

## Next steps - checking the file validity

If the OIO UBL function is disabled, the invoice will be posted, and the XML will be downloaded in the browser. If you wish to check whether the file is correct, you can import it into an online OIO UBL validator or check the **Activity Log** on a **Posted Sales Invoice**.

![oio\_ubl\_file\_validity](/_fern-img/e5362f92ba8a20746e73b310fbed650f0a0a58b55c51dd0eb15f517604d2997a.webp)

The **Activity Log** shows the status of sending the invoice. If some of the data for the invoice was incorrect, there's an option in the **Posted Sales Invoice** section to correct the data on the customer, and update the posted document with the **Update OIOUBL fields from Customer** function.

![oio\_ubl\_posted\_sales\_invoice](/_fern-img/9f8dcda2c58e9f58813f6d27f4a186e6ab8c08f2834a17d9ae367767032127ae.webp)

All data from the **Customer Card** is retrieved as a result, and the fields in the **Posted Sales Invoice** are updated.