E-invoicing: closing the loop from order to payment

A PDF invoice sent by email is an electronic document, but it is not an e-invoice. Someone still has to open it, read it and retype it. A true e-invoice is structured data that software can process on its own.

The standards behind it

Governments around the world are moving to structured e-invoicing. Saudi Arabia has a national e-invoicing system, the UAE is rolling out a national model, China is replacing paper tax invoices with fully digital ones, India requires e-invoices for larger taxpayers, and the US relies on standards and networks for federal and private exchange. The EU set a common semantic model, EN 16931, so that an invoice means the same thing in every system. The details differ by country, so always check the local rules, but the benefits are the same everywhere.

Peppol is one widely used network for exchanging them, now used well beyond Europe, including in Asia-Pacific. Where a national system is mandatory, you connect to that. Peppol works like email for business documents: you register once, get an address, and can send or receive invoices, orders and other documents with any other participant, regardless of which software each side uses.

What good looks like

In a well-run purchase-to-pay process, the chain is:

1. A purchase order is created and approved.
2. The supplier delivers and issues an e-invoice that references the order number.
3. Your system matches the invoice to the order and the goods receipt automatically (this is three-way matching).
4. Matches within tolerance go straight to payment. Exceptions go to a person.
5. Payment is scheduled to capture discounts or to land on the due date, not before.

Teams that reach this point often process the large majority of invoices without a human touching them. People spend their time on exceptions, which is where judgement is needed.

Benefits you can measure

• Lower cost per invoice. Manual handling is the biggest cost. Removing it is the biggest saving.
• Fewer errors and duplicates. Data is not retyped, so it is not mistyped.
• Faster payment to suppliers. This improves relationships and often improves price, because suppliers charge less to customers who pay on time.
• Better visibility. You can see liabilities before they are due, which helps cash planning.
• Audit trail. Every step is logged.

Getting started

1. Measure the current state. How many invoices per month, how many arrive on paper or PDF, and how long approval takes.
2. Fix purchase orders first. Automatic matching only works if invoices reference valid orders. "No PO, no pay" is a powerful policy.
3. Ask your top suppliers to switch. The top twenty usually account for most of the volume. Offer help and a clear date.
4. Choose an exchange route. Connect to Peppol directly or through a service provider who handles it for you.
5. Set tolerances. Decide what price and quantity differences can be accepted automatically.

Pitfalls

• Skipping master data clean-up. Duplicate supplier records and wrong bank details are the root of many payment errors and fraud attempts.
• Automating a broken approval chain. If invoices wait three weeks for a signature, an e-invoice will wait three weeks too.
• Forgetting small suppliers. Offer a simple web form for those who cannot send structured files.

Fraud and controls

Automation does not remove the need for control. Keep a rule that any change to a supplier's bank account is verified by a call to a known number. Structured data makes it easier to spot anomalies, such as an invoice from a new bank account, so use that.

The bottom line

E-invoicing is where procurement and finance meet. The technology is mature and the standards are settled. The remaining work is mostly process: clean orders, clear approvals and supplier onboarding. Do that work, and the payment end of procurement becomes the quietest part of your day.