CFOtech Australia - Technology news for CFOs & financial decision-makers
Australia
What Europe's e-invoicing mandates teach finance teams

What Europe's e-invoicing mandates teach finance teams

Wed, 18th Nov 2026 (Today)
Timo Kleemann
TIMO KLEEMANN Founder BillingEngine

In Australia, e-invoicing over the Peppol network is available, with the Australian Taxation Office acting as the Peppol authority, but it remains voluntary for business-to-business invoices, and most of them are still PDFs sent by email. Much of Europe has stopped treating that as normal. Belgium, Poland and France have introduced mandates in 2026, and Germany is phasing one in. Australian finance teams are not bound by any of this. The experience is still useful, because the problems show up in the same places, and they show up in the finance team before anyone else notices.

Receiving comes before sending

Germany is the clearest example. Since January 2025 every business there must be able to receive structured e-invoices. Issuing them is required from 2027 for companies with more than EUR 800,000 in annual turnover, and from 2028 for all others. The order was deliberate. A business cannot be expected to send what its customers cannot yet read, so the law began with the receiving side.

For a finance team, the lesson is to start with accounts payable. Suppliers choose their own timing, and some will send structured invoices before any rule requires it. An inbox that only handles PDFs will either reject those files or leave a person to key in the data by hand.

The invoice becomes data

A structured e-invoice, for example XRechnung or Peppol BIS Billing, is a file that software reads field by field. A hybrid format such as ZUGFeRD or Factur-X wraps a readable PDF around an embedded XML file, and the XML is what counts. There is no longer a document that a person glances at before approving it. Which supplier, which tax treatment, which purchase order, which amount: each is a field, and each is checked.

That changes what a finance team spends its time on. Fewer invoices need to be typed in. More of them arrive with a problem that has a name: a missing purchase order reference, a VAT identification number that does not match the supplier record, a unit price that differs from the order by a few cents. In a PDF workflow these discrepancies were absorbed by whoever was processing the invoice. In a structured workflow they are rejections, and rejected invoices are paid late.

Where the data problems sit

The technology for structured invoices is mature. The master data usually is not. Customer and supplier records often carry old legal entity names, tax numbers entered with spaces or in the wrong format, and several addresses for the same company. Purchase order numbers live in the procurement system but not in the billing system, so the reference a customer requires is simply not available when the invoice is created.

None of this is new. It was always untidy and always cost time. What the mandates changed is that the untidiness can no longer be corrected by a person at the end of the chain. It has to be fixed where the data originates.

What a finance team can do now

None of the following depends on a mandate, and each step is useful on its own.

First, map the invoice flows. Where are invoices created, in which system, and by whom? Often the answer is two or three tools and a spreadsheet that nobody owns.

Second, check the master data of the largest customers and suppliers: legal name, tax number, address, the reference fields the counterparty requires. A short list of 20 to 30 accounts usually covers most of the invoice volume.

Third, ask the biggest suppliers and customers what they plan. Large buyers in Europe already instruct their suppliers on format and delivery channel, and the same questions apply to any company that does business with them. Australian exporters to Europe are the obvious case.

Fourth, test before it matters. Structured invoices can be validated against the published rules, and a free e-invoice validator is enough for spot checks. A failed test costs nothing. A failed invoice in a customer's payables queue costs weeks.

What to expect

Australian businesses can take two things from the European experience. A mandate is rarely the real trigger. The trigger is the first customer or supplier that asks for a structured invoice, and that request can arrive before any law does. And the work is mostly about data quality, which is slow to fix and cheap to start.

Finance teams that begin with receiving, clean their master data and test a few invoices will meet a later mandate, or a customer's request, with little extra effort. Those that wait will be doing the same work under a deadline.