Custom NLCIUS integration
Appfront builds integrations that create and read e-invoices in accordance with NLCIUS, the Dutch implementation of the European e-invoicing standard. NLCIUS is mandatory for invoices to the Dutch government and is increasingly requested between businesses. We make sure your own invoicing system produces an invoice that meets the rules, validates it before sending, and reads received e-invoices into your accounting system.
What is an NLCIUS integration?
NLCIUS is the Dutch implementation of the European e-invoicing standard, EN 16931. An invoice that follows NLCIUS is a structured file, usually in UBL, with fixed fields and rules: which data is mandatory, how it is recorded and how it is validated. NLCIUS is mandatory for invoices to the Dutch government, and it is increasingly requested between businesses too. Peppol is often used for sending; NLCIUS is about the content.
A standard accounting package often already produces e-invoices. But companies with their own invoicing system, their own ERP or an order platform often don't have that. An invoice to the government is then sent as a PDF and comes back rejected. Or an e-invoice is rejected because of a missing field, and nobody can see why. And on the receiving end, e-invoices are still opened as PDFs and retyped.
We build custom because the integration has to fit your system: where the data on an invoice comes from, which customers ask for e-invoices, which channel you use for sending, and where received invoices need to go. What the rules require for your invoices, we check against the NLCIUS validation rules.
Invoices that follow the standard
Invoices from your own system converted to UBL according to NLCIUS, with all mandatory data.
Checked in advance
Validation against the rules before sending, so an invoice isn't rejected by the recipient.
Received and processed
Received e-invoices loaded into your accounting or purchasing system, with no retyping.
How we build your NLCIUS integration
We start with your invoices: which system they come from, who asks for e-invoices, and how you currently send and receive.
Your invoicing system, the data on each invoice, your customers and the channel for sending.
Invoices converted to UBL according to NLCIUS, and checked against the validation rules.
Sending via Peppol or another channel, and loading received e-invoices.
Testing with real invoices and recipients, going live, and maintenance when new versions of the rules are released.
What an NLCIUS integration actually does
The components below appear in almost every NLCIUS integration. Which ones you need depends on your role.
Conversion
Invoices from your system converted to UBL according to NLCIUS.
Validation
Checks against the validation rules before sending.
Shipping
Sending via Peppol or the channel the recipient requires.
Receiving
Received e-invoices loaded into your accounting or purchasing system.
Notifications
A notification with the reason if an invoice is rejected.
Log
For each invoice, what was sent or received, and with what result.
Who we build an NLCIUS integration for
The integration is intended for organisations whose standard package doesn't produce e-invoices.
Government suppliers
Invoices to public sector organisations. An invoice that doesn't come back is the core problem.
Businesses with their own ERP
Invoices from an in-house system. Converting and validating matter most.
Organisations that receive invoices
Lots of purchase invoices. Loading them without retyping is what's needed.
Software suppliers
Invoicing within your own product. Support for the standard is the core need.
Technology and integrations
This page is about the content of e-invoices according to NLCIUS. For sending via the Peppol network, see our page on a Peppol integration, for accounting our page on an Exact Online integration, and for purchase invoices our page on accounts payable management. You can read about our approach on building custom software.
For orders, delivery notes and catalogues in UBL, alongside the invoice, see our page on a UBL integration.
Why Appfront for your NLCIUS integration?
A rejected invoice gets paid later. That's what we build around: invoices that follow the standard, checked before sending, and received invoices that flow into your accounts automatically.
Not rejected
Validation up front catches what the recipient would reject.
No retyping PDFs
Received e-invoices flow into your accounts automatically.
Ready for the government
Invoices to the government in the format that is required.
Security and privacy in an NLCIUS integration
The integration processes invoices containing customer, supplier and amount data. Access credentials for dispatch channels are stored encrypted and used only by the integration.
The integration runs in a European data centre, with encrypted storage, daily backups and a log of every invoice.
Frequently asked questions about an NLCIUS integration
Questions companies ask before getting started.
NLCIUS is the Dutch implementation of the European e-invoicing standard, EN 16931. It defines which data an e-invoice must contain and how that data is validated, usually in the UBL format. An NLCIUS invoice can be read automatically by the recipient, without anyone retyping a PDF.
NLCIUS is about the content of the invoice. Peppol is a network for sending e-invoices. The two are often used together: an invoice that follows the rules, sent via Peppol.
For invoices to the Dutch government, e-invoices that follow the standard are required. Between businesses it is not yet mandatory everywhere, but large customers increasingly ask for it. What applies to you is something to settle with your adviser.
Yes. Every invoice is checked against the validation rules before it is sent, with a clear message if something is missing or wrong, such as a missing VAT number, a customer order number or an error in the amounts. That way the mistake is fixed before the customer sees it.
Yes. Received e-invoices are read into your accounting or purchasing system, with supplier, amounts and lines, without retyping. Invoices that cannot be read are held for review, together with the reason.
Yes, that is exactly what this integration is for. We pull the data from your system and convert it. A standard accounting package often has this built in already. We look at which data from your system is needed and which is still missing in the first step.
The validation rules are occasionally issued in a new version. As part of maintenance, we update the integration accordingly so your invoices stay compliant.
E-invoices that never come back?
Tell us which system your invoices come from, who asks for e-invoices and how you currently send and receive them. We will show you what the integration would look like.