After the mandate: archiving, audit and change

Most e-invoicing systems do not fail on day one. They fail in month ten, quietly.

The project closes, the team disperses, and whoever opened the rejection report every morning is moved onto something else. Then a format changes, or a certificate expires, or an item is added with no code — and nobody is looking.

This station is about making that not happen.

Three things that must not stop

What	How often	Who owns it
The rejection report	Daily	Finance
Reconciling books against what reached the authority	Monthly, before the return	Finance
Reviewing changes to the requirement	Quarterly	Finance with the provider

The third is the least obvious and the most neglected.

The requirement moves in three directions: thresholds fall and pull in entities that were out of scope; formats are updated; and waves widen, so a branch or a subsidiary you believed exempt is suddenly in scope.

Make it a standing item on a quarterly agenda, with one question: what has changed since the last review, and what does it do to us?

Archiving — and the question that exposes it

Authorities require electronic documents to be retained for defined periods. The period is not the problem; retrieval is.

One question exposes any archive in a minute.

Produce, now, the original approved document for a specific invoice issued eighteen months ago, with its stamp and its acceptance reference.

Anybody needing three days to answer does not have an archive. They have a backup. The difference between the two is the difference between a document you hand an auditor and a file you search.

Three conditions for a real archive:

• The original document as submitted, rather than its printed image.
• Search by identifier, invoice number, date and customer.
• Independence from the provider. If your archive exists only on their side, you are renting your own past. Pull it back into your own storage periodically, and test retrieval once a year.

What an auditor actually asks for

Not “show me the system”. Five things.

1. A sample of original documents with stamps and acceptance references.
2. A reconciliation between the return, the books and what reached the authority for a given period.
3. An explanation of every gap in the sequence — even a justified one.
4. The credit note register and the original document each one relates to.
5. Written, approved procedures: outage, correction and monitoring.

The fifth is what separates a disciplined company from a lucky one. A written, approved procedure changes how an auditor reads the same error: an error inside a disciplined system is an exception being managed; the same error with no procedure is evidence of disorder.

And what this means for the system decision itself

After the mandate a new line enters any evaluation of a new system, and it did not exist two years ago.

Four questions get added to every evaluation.

• What do you ship of the compliance layer in my country, and under which line on the quotation? — the gap between “we support it” and “it is included” is measured in tens of thousands a year.
• How many times have you updated the format in the last two years, and who paid?
• Show me a real electronic document issued by one of your customers in my country, not a slide.
• If I leave you, how does my electronic archive come out?

The third is the harshest and the most honest. A vendor with a live customer issuing accepted documents in your country answers in a day; one without talks about a roadmap.

The systems compared on that line specifically are in the ERP e-invoicing readiness table — the table to open before the demo rather than after it.

What changes in how you work

Three things do not go back, and all three are a gain.

One: no editing after issuance. Correction is a new document, a discipline that should have existed before the mandate.

Two: missing data stops a sale rather than deferring it. A customer with no tax number is no longer a problem to be tidied at month end. That raises your data quality by force.

Three: the authority sees what you see. The era of a gap between the books and the return is over. Anybody who was relying on that gap has a larger problem than a technical one.

What you actually do in this station

• Turn the daily watch into a written job role, rather than a project task.
• Test retrieval: request a document more than a year old and time it.
• Put “changes to the requirement” on a standing quarterly agenda.
• Assemble the audit file with the five items above before it is asked for.
• Revisit the ERP readiness table before any upgrade or system change.

The three commonest mistakes

One: closing the project without handing over the role. The daily watch disappears within two months.

Two: an archive held only by the provider. The price shows on the day you migrate or the day you disagree.

Three: assuming the requirement has settled. Thresholds fall and formats are updated, and anybody not reviewing finds out from a penalty.

The acceptance test for this station

1. Name the three things that must not stop, with their frequency and owner.
2. Run the retrieval test and state how long it took.
3. Name the three archive conditions and why independence from the provider is one.
4. Name the five things an auditor asks for.
5. Explain why a written procedure changes how an auditor reads the same error.

What comes next

The path is finished. The next step is a decision rather than learning: if your current system is what stands between you and compliance, start at the ERP e-invoicing readiness table, and from there the systems comparison with published prices and the date each was read.