Electronic Invoicing: The Calendar Was the Easy Part
The deadline is the simple bit. The real work is tracing where every invoice actually comes from before you connect anything.
The invoice nobody can quite trace
A finance manager at a 40-person distribution company sat down to prepare for electronic invoicing and assumed the hard part was behind her: she knew the deadline, she'd picked a platform, she'd told her team to get ready. Then she asked a simple question — where does every invoice we issue actually come from? — and nobody in the room could answer completely.
Some invoices were generated by the ERP. Some were built in Excel by a sales rep who exported a template nobody else used. Some came from a shipping module that talked to accounting through a CSV file dropped in a shared folder once a week. Credit notes followed a different path entirely, handled manually because the volume was low and nobody had bothered to automate it. The company had, without ever deciding to, built four invoicing processes instead of one.
This is the normal state of a PME that has grown by adding tools rather than redesigning how data moves. Each addition solved a problem at the time. None of them were built with the idea that one day everything would need to flow through a single mandatory channel. The calendar tells you when you have to be ready. It says nothing about what "ready" requires.
Why the deadline distracts from the real work
A date is reassuring because it looks like a finish line. Pick the software, train the team, flip the switch on the right week. That framing works for a feature update. It doesn't work for a plumbing change, and electronic invoicing is a plumbing change: it reroutes the pipes that carry financial data between your systems and a government platform that will not tolerate ambiguity.
The risk isn't missing the date. The risk is connecting a messy set of flows to a strict system and discovering, invoice by invoice, every exception nobody mapped. A format mismatch here, a missing tax code there, a credit note that was never meant to be machine-readable. Each of these is small on its own. Together, during a transition period, they slow down cash collection and generate support tickets instead of invoices.
The companies that get through this without friction are the ones that treated the mapping as the project, and the connection to the platform as the last step of that project, not the first.
How to map your invoicing flows before you connect anything
- List every system, spreadsheet, or manual process that currently produces or touches an invoice — including the ones nobody thinks of as "the invoicing system," like a shipping tool or a subscription manager.
- For each flow, write down where the data starts, what transforms it along the way, and who owns that step. If the answer is "nobody, it's just always worked," flag it; that's where things will break first.
- Check which flows already produce structured data (ERP exports, API feeds) versus which ones rely on a human re-typing or reformatting something. The second category is where the real integration work lives.
- Identify every exception case separately: credit notes, corrections, intra-group invoices, foreign clients. These are usually handled outside the main flow and get forgotten until they fail.
- Decide, flow by flow, whether to fix it, merge it into an existing system, or retire it entirely. Not every process deserves to survive the transition; some only existed because nobody had time to consolidate them.
This audit takes longer than picking a software provider, and it should. It's also the only part of the work that actually reduces risk, because the connection itself is mostly a technical formality once the data behind it is clean.
What tells you the mapping actually worked
You'll know the work paid off when invoices move from issuance to validation without anyone manually re-entering data, when exceptions are handled by a defined process instead of an improvised one, and when a finance team member can trace any single invoice back to its source system in under a minute. If that tracing still takes a phone call to someone who "knows how it works," the mapping isn't done — it's just been postponed.
Get your invoicing flows mapped before you connect to anything
ArkonLabs builds the custom software and integrations that sit behind this kind of transition — tracing how data actually moves across your systems, consolidating the flows that need it, and connecting what's left cleanly. If your invoicing setup has grown the way most PMEs' do, get in touch through www.arkon-labs.com before you pick a connection date.