Most e-invoicing projects fail on data rather than on technology. The mandate arrives, the software is bought, and then it emerges that a third of the customer master has no usable tax identifier, that nothing carries a unit of measure code, and that nobody can say which of the seven document types accounts receivable emits are invoices in the legal sense.
This section is about the work between the decision and the first live document, and it is written for whoever has to plan it: readiness assessment and why it should be keyed to stages rather than dates, master data remediation, redesigning accounts payable around a document that arrives already structured, onboarding suppliers and customers at a scale where a mail merge stops working, testing against the whole validation stack rather than a single validator, exception handling once volume is flowing, and the cost model that decides whether the work happens in the ERP, in a provider's platform, or in both. What the deadline actually is belongs to mandates and deadlines; what the document must contain is in standards and formats. The library lists everything on the site.
An e-invoicing readiness assessment worked in the order the answers bind: scope, documents, data, systems and the receiving side, ending in a defensible cost range.
The analysis underneath the anchor piece.
During a project, exceptions are worked by people with capacity and expertise. Three weeks after go-live they are not, and that is a capacity decision in technical clothing.
This gets framed as build or buy, and it is really a question about where knowledge sits. Most large businesses end up splitting it, and the split has a cost that nobody puts in the comparison.
These projects fail on data, not on technology. The fields a structured invoice makes load-bearing were decorative before, and the difference between present and correct is where the whole cost sits.
When the obligation to receive arrives, every supplier has to be able to reach you. Contacting them all and asking for their details does not survive contact with a supplier base of any size.
On the receiving side a mandate deletes steps rather than adding them, and the control that used to sit inside those steps has to be put back somewhere deliberately.
Four gates stand between a document and acceptance and only three are published. Passing the public ones and failing the fourth in production is the normal project outcome.
Licence and transaction fees are the visible cost and rarely the largest one. A business case built on price per document will be wrong in a direction that is discovered late.
