Electronic invoicing rarely comes alone
Luxembourg is preparing a new stage in the wider adoption of electronic invoicing. Bill 8815, submitted to the Chamber of Deputies on 30 July 2026, provides for extending the obligation to domestic commercial transactions between businesses established in Luxembourg and sets out a phased implementation between 2028 and 2029. The timetable may still change. But treating this development as a mere change of format would already miss what it can actually transform.
A compliant electronic invoice is not simply a PDF sent through a different channel. It is based on structured data designed to be transmitted, received and processed automatically. The Luxembourg proposal provides for a common delivery network and envisages that, over time, this infrastructure could also carry other documents linked to the purchasing and invoicing process.
In other words, what is being prepared is not merely the digitisation of a document. It is the possibility of a much more continuous flow of information between systems.
The software reflex
Faced with this deadline, many businesses will naturally start with one question: will our software be compliant? It is a necessary question. It is simply not sufficient.
Software sees only part of the problem. An invoice can be perfectly structured and still enter an organisation that continues to require printing, approval by email, duplicate data entry, manual reconciliation, or a succession of interventions by people whose roles overlap.
In that case, the pipe will have been modernised without really reconsidering what flows through it.
Technology can speed up transmission. It can automate a control. It can reconcile data. It cannot decide for the business why an approval exists, whether it still adds value, or who should take ownership of an exception when a control fails.
The invoice is only the middle of the process
Looking at an invoice makes it easy to forget everything around it. Before it, there is often an order, a commercial agreement, a delivery, a service or time data. After it come accounting, the due date, payment, customer-account monitoring, and sometimes a dispute or a reminder.
The invoice is therefore less a starting point than a passage between several decisions.
This is precisely why a move to electronic invoicing can be useful beyond compliance. It forces an organisation to describe a process that habit has often made implicit.
Who creates the information? Who checks it? At what point does it become reliable? Which data prevails when two systems tell different stories? Who knows that an invoice is blocked? Who can unblock it? When do sales, accounting or finance learn that a payment may not arrive?
These questions existed before electronic invoicing. They will simply become much more visible when the chain is automated.
The time an invoice does not show
An invoice shows an issue date and a due date. It reveals far less about the time lost before it is issued or while an exception is being resolved. Yet this is often where the real cost of the process is hidden.
A few minutes of re-keying, an approval waiting in an inbox, a discrepancy handled by three people: each item looks minor in isolation. Repeated hundreds of times, these micro-frictions become a characteristic of how the business operates.
Structured exchange therefore creates an opportunity to look less at the volume processed and more at the time between the economic event and invoicing, the frequency of interventions, the duration of blocks, and the delay until cash is collected. That is where one can see whether the process has actually improved.
Automate what deserves to be automated
The word automation can give the impression that the objective is to remove people from the process. That is probably not the most useful way to frame it.
A robust process distinguishes three categories instead. First, what is repetitive, deterministic and reliable enough to automate. Second, what still requires a human decision. Finally, exceptions: situations where the normal process is no longer enough and someone must clearly take ownership.
It is often in this third category that organisations lose the most time. An invoice does not match the purchase order. A reference is missing. The price differs. The customer disputes a line. The service has not been formally approved. The system detects the discrepancy, but nobody knows exactly who is responsible for deciding.
Automation can detect the exception faster. It does not resolve ambiguity over responsibility.
Use the deadline
As filed, Bill 8815 provides for a gradual implementation between 2028 and 2029. The timetable may still change, but the direction is clear enough for the issue to be more than theoretical.
Two years may seem like a long time to change a format. It is much less time when the work involves cleaning data, reviewing responsibilities, connecting several applications, removing unnecessary steps and testing a process that must run without permanent intervention.
The most useful preparation may therefore start before the IT project: by observing the process as it actually works.
A small sample of invoices is often enough to reveal duplicate entry, approvals that prevent nothing, accumulating interventions, and moments when information simply waits without a clear owner. This diagnosis already says a great deal about what should be kept — or removed — once the new framework is in place.
Compliance is not the target
A regulatory obligation often creates a minimum target: be ready by the required date. That is normal. But this target can become dangerously comfortable.
Being compliant means that the process follows the rule. It does not mean that it is fast, reliable, understandable or well governed.
Electronic invoicing can therefore be treated as a compliance project. The software will be adapted, the exchange tested, and the business will check that invoices are sent and received correctly.
Or it can be used as a much rarer opportunity: to reopen the invoice-to-cash cycle and decide what should no longer exist after the transition.
What technology does not decide
Organisations sometimes ask tools to solve problems that are actually problems of choice. Who decides? Based on which information? Within what timeframe? Under what exception rule?
A good system can make those decisions visible. It cannot invent them.
That may be the real opportunity created by electronic invoicing: not simply to transmit an invoice better, but to force the business to examine the process that produces it and the process that ultimately turns it into cash.
Compliance sets the deadline. Technology provides the means. Governance decides which process is worth keeping.