ERP integration: the invoice is the easy part

Integration work is mostly data: TRNs in the vendor master, tax categories mapped per line, and a receiving path that can accept structured invoices.

5 documents free. PDF, photo or XML — data out as CSV, Excel or JSON.

Outbound: what the ERP must produce

A structured invoice with PINT AE fields: both TRNs, invoice number and date, line items with tax category, totals per category.

If master data is incomplete, validation fails at the access point — not in your system, which makes it look like a provider problem.

Many projects automate issuing and leave receiving as «someone reads the email».

Structured invoices arriving with no reader pile up, and the team falls back to retyping.

5% standard rated, zero rated and exempt are separate categories. If the ERP collapses them into one tax code, reports stop matching declarations.

Map once, test with a real invoice per category.

Send one invoice, receive it, read it, post it — end to end.

Then test a rejection: what does a failed validation look like in your process?

Usually not: most work is master data and mapping, plus a receiving tool.

The access point validates structure; correctness of amounts stays your responsibility.