Custom UBL integration development
Appfront builds integrations with UBL, the international standard for business documents such as orders, order confirmations, delivery notes, catalogues and invoices. Many trading partners, government bodies and platforms require UBL. We make sure your own system creates and reads those documents: importing customer orders, sending back confirmations and delivery notes, supplying catalogues and processing supplier invoices.
What is a UBL integration?
UBL, Universal Business Language, is an international standard for business documents in XML. It covers not just the invoice, but also the order, the order confirmation, the delivery note, the catalogue and more. Many agreements build on it: the Dutch e-invoicing rules use UBL, and the Peppol network also sends UBL documents, for invoices and increasingly for orders.
For a company with its own order system, that means this: a large customer sends orders in UBL, and they are currently entered by hand. The customer asks for an order confirmation and a delivery note in UBL, and they never arrive. A platform wants a catalogue in UBL. And on the purchasing side, suppliers send invoices in UBL that get opened as PDFs and retyped. Each document is a different type, with its own rules per trading partner.
We build custom integrations because the integration has to fit your systems and partners: which documents you exchange, with which customers and suppliers, which agreements they have on top of UBL, and through which channel. There are separate pages for invoices under the Dutch rules and for sending via Peppol; this page is about UBL as a format for all documents between you and your trading partners.
All documents
Orders, order confirmations, delivery notes, catalogues and invoices in UBL, from and to your own system.
Per trading partner
The agreements per customer or supplier on top of UBL are recorded, so every document is correct for the recipient.
Checked in advance
Validation against UBL and the agreements before sending, and clear notifications when something goes wrong.
How we build your UBL integration
We start with your documents: which types, with which partners, through which channel, and where retyping happens now.
Which documents, with which trading partners, which agreements and which channel.
Documents from your system into UBL, and received UBL documents into your system.
Validation against UBL and the agreements per partner, with notifications when errors occur.
Testing with real partners, going live partner by partner, and ongoing management as new agreements come in.
What a UBL integration actually does
The components below appear in almost every UBL integration. Which ones you need depends on your partners.
Orders
Customer orders in UBL imported into your system.
Confirmation and delivery note
Order confirmations and delivery notes in UBL sent back to the customer.
Catalogues
Products and prices as a UBL catalogue for customers or platforms.
Invoices
Creating sales invoices and importing purchase invoices in UBL.
Validation
Validation against UBL and the agreements per partner.
Log
For each document, what was sent or received, and with what result.
Who we build a UBL integration for
The integration is intended for organisations whose system doesn't speak UBL.
Wholesalers
Orders from large customers in UBL. Importing without retyping is the core.
Manufacturers
Delivery notes and confirmations requested. Sending them back matters most.
Government suppliers
Orders and invoices via Peppol. What's needed is UBL from your own system.
Purchasing organisations
Invoices from many suppliers. Importing into the accounts is the core.
Technology and integrations
This page is about UBL as a format for business documents. For e-invoices under the Dutch rules, see our page on an NLCIUS integration; for sending via the network, our page on a Peppol integration; and for purchase invoices, our page on accounts payable. You can read about our approach on building software.
If you receive or send UBL invoices via Peppol, read more about our software for invoice flows via Peppol.
Why Appfront for your UBL integration?
An order that gets retyped is an order that can go wrong. That is what we build on: documents in the format your partners ask for, sent from and to your own system, and checked before they are dispatched.
No retyping
Orders and invoices arrive directly in your system.
Happy partners
Confirmations and delivery notes in the requested format.
Fewer rejections
Pre-checks catch errors per partner.
Security and privacy in a UBL integration
The integration handles orders, prices and invoices: confidential data belonging to you and your partners. Credentials for channels are stored encrypted and used only by the integration.
The integration runs in a European data centre or in your own environment, with encrypted storage, daily backups and a log of every document.
Frequently asked questions about a UBL integration
Questions companies ask before getting started.
Universal Business Language is an international standard for business documents in XML, such as orders, order confirmations, delivery notes, catalogues and invoices. Many e-invoicing rules and the Peppol network build on it.
UBL is the format. NLCIUS sets out the Dutch rules for e-invoices, usually in UBL. Peppol is a network for sending documents. This page covers UBL for all documents; NLCIUS and Peppol have their own pages.
The documents you exchange with your partners: orders, order confirmations, delivery notes, catalogues, invoices and credit notes. We usually start with the document that takes the most retyping, often the order or the purchase invoice.
Many partners have agreements on top of UBL, such as mandatory references or their own codes. We record these per partner, so every document is correct for that recipient. Adding a new partner is then simply a matter of adding agreements. This way the integration grows with the number of partners, without having to rebuild the foundation.
Yes. Every document is checked against UBL and the partner's agreements, with an alert if anything is missing or incorrect. The error is fixed before the partner ever sees it.
Via Peppol, a customer's platform, a portal or any other channel the partner requires. The integration can use several channels side by side. For each partner, the channel and agreements that apply are recorded, so every document takes the right route.
Yes, that is exactly what this integration is for: systems that don't speak UBL themselves. Standard packages often have it built in already.
Orders and invoices in UBL, without retyping?
Tell us which documents you exchange, with which partners and which system you use. We will show you what the integration looks like.