Short answer
Check whether your accounting or invoicing system can create, send and receive e-invoices according to EN 16931, choose a delivery channel, clean up your customer and supplier details and try e-invoices with a few partners now. Then the switch by 1 January 2028 will happen without a rush.
Checklist
- System. Does your software create e-invoices in XML? Can it receive and automatically book incoming e-invoices?
- Channel. Which channel will you send and receive through — a Peppol access point, the e-address or another one agreed with your partners? See what is Peppol.
- Data. Are your customers’ and suppliers’ details correct and complete? Errors are more visible in e-invoices.
- Process. Who approves incoming invoices, and how? This is a good moment to automate approvals.
- Integrations. If invoices are issued by an online store, ERP or CRM, they must be able to create e-invoices or pass the data to accounting.
- VID. Plan how e-invoice data will be reported to VID.
Why not wait
- Partners and public bodies already ask for e-invoices.
- The switch takes time for adapting and testing the software.
- Automatic processing of incoming e-invoices saves time right now.
If your system is custom-built or doesn’t offer e-invoicing, it can be extended — see how to automate receiving and booking e-invoices.