For most of the history of accounting software, the data going into the ledger has been a mess. PDFs. Photos of receipts. Emails that say 'invoice attached' with nothing attached. The reason finance ops is so labour-intensive is not that the logic is hard; it is that the inputs are unstructured and someone has to structure them by hand.
That is changing, and not because software vendors asked nicely. Tax authorities are mandating it.
What is actually happening
- India requires e-invoicing with a government-registered IRN for businesses above a turnover threshold, and the threshold has been lowered repeatedly. Every qualifying B2B invoice is structured JSON reported to a portal before it is valid.
- The EU's ViDA package moves member states toward mandatory structured e-invoicing for cross-border B2B, with national mandates (Italy, Poland, Germany, France, Belgium) arriving on their own schedules.
- Brazil, Mexico, Chile, and much of Latin America have run clearance-model e-invoicing for years. Invoices are validated by the tax authority before they exist.
- Saudi Arabia, Egypt, Malaysia, and others have launched or are phasing in mandates.
The motive is tax collection. The effect is that a large and growing share of the world's B2B invoices now exist as structured, validated, machine-readable records with a government-assigned identifier — before they reach anyone's ledger.
Why this matters for agents
An agent acting on a company's books needs to know what is true. An invoice that exists as a validated structured record with buyer, seller, line items, tax, and an authority-issued ID is something an agent can reason about precisely. A PDF attachment with a handwritten note is something it has to guess about.
Structured invoices make three jobs dramatically easier:
- 01Payables capture. The bill is already structured. No extraction, no guessing at the tax line, no duplicates that differ by a scan artefact.
- 02Reconciliation. Portal data and ledger data can be matched exactly. Input-credit mismatches surface as a list, not a hunt.
- 03Collections. The customer's own reporting confirms they received and accepted the invoice. 'We never got it' stops being an argument.
Regulation is doing the data cleaning that software vendors never managed to sell.
The other side: compliance is now a workflow
The same mandates create work. Invoices must be validated before they are sent. Portal data must be reconciled to the ledger. Deadlines multiply. For a small business with an outsourced accountant, this arrives as a monthly scramble; for the accountant, it arrives forty times.
That is also agent work. Validate the invoice fields before sending. Pull the portal data and match it. Draft the return workings from the ledger. Track the acknowledgement. None of it requires judgment about tax law — that stays with the accountant — but all of it requires diligence on a schedule, which is exactly what humans are worst at and agents are best at.
There is a second-order effect worth noticing. Once the invoice is structured at the source, the distinction between 'compliance data' and 'operating data' collapses. The same record that satisfies the tax authority is the record the collections agent chases, the record the close agent matches, and the record the cash agent forecasts from. One structured invoice, four jobs. That is a very different economics from four people re-keying the same PDF.
What to do about it
If you run a business in a jurisdiction with an e-invoicing mandate, or sell into one, the practical advice is simple. Treat the mandate as an opportunity to make your invoicing structured everywhere, not just where it is required. Once your invoices are data, everything downstream — collections, reconciliation, forecasting — becomes automatable in a way it was not before.