Electronic invoicing: what it means and what it now requires

Electronic invoicing — e-invoicing — means issuing and receiving invoices in a structured, machine-readable format that the recipient's system can process without anyone retyping it. This is the part most businesses get wrong: emailing a PDF is not electronic invoicing in the regulatory sense, however electronic it feels. A PDF is a picture of an invoice; an e-invoice is data.

The distinction used to be a matter of efficiency. It is now, in a growing number of countries, a matter of law: public-sector suppliers have been required to send structured invoices in several jurisdictions for years, and mandates for business-to-business invoicing are being introduced on staggered timetables. What applies to you depends entirely on where you and your customers are.

The three things people call e-invoicing

• A PDF sent by email. Convenient, universally accepted between small businesses, and not a structured e-invoice.
• A structured e-invoice — an XML or similar file conforming to a defined standard — exchanged through a network or directly, and processed automatically by the recipient.
• A hybrid file, where a structured payload is embedded inside a PDF so a human and a machine can both read it. Common in some European markets.
• Alongside these: clearance models, where invoices must be submitted to or validated by a tax authority before or at the time of issue. This is a different obligation from format and exists in a number of countries.
• And the exchange layer: standardised networks through which structured invoices travel between suppliers and buyers.
• What matters practically is which of these your customers and your tax authority require of you, and by when.

Check your own obligations rather than generalising from an article. E-invoicing rules differ by country, by whether you sell to the public sector or to businesses, and by turnover threshold, and the timetables move. Your accountant or your national tax authority is the source; getting this wrong is not a formatting inconvenience but a compliance issue.

Getting ready without over-building

1. Find out what actually applies: your jurisdiction, your customers' jurisdictions, whether you supply public bodies, and the dates on the current timetable.
2. Ask your largest customers what they need. In practice their requirements often arrive before the legal ones, and they are more specific.
3. Get your invoice data clean first — consistent supplier and customer identifiers, tax treatment, sequential numbering, correct references. Structured formats fail on inconsistent data, and this work is useful regardless.
4. Decide the route: your accounting software's own support, a service provider that converts and transmits on your behalf, or a portal your customer offers.
5. Test with one customer before switching everything. Rejections are common at first and are usually about reference fields.
6. Keep the human-readable copy as well as the structured one for as long as your retention rules require.
7. Agree internally who fixes a rejected invoice, since a rejection means an unpaid invoice until someone acts.
8. Watch the timetable — mandates have moved repeatedly, in both directions.

The benefit, honestly stated

For a small business the compliance driver usually arrives before the efficiency benefit. The genuine gains are real but modest at low volume: no retyping at the other end, fewer disputes about what was sent, faster approval because the invoice enters the buyer's workflow automatically, and often faster payment as a result. If you issue thirty invoices a month, the case is compliance and customer requirement rather than saved effort — which is worth being clear-eyed about before buying anything.

In Ettex, invoices are created and issued through Ettex Invoices: line items with quantities, rates, multiple tax rates and discounts, notes and terms fields where PO and contract references belong, sequential auto-numbering with your own prefix, a client and supplier book so entity names and identifiers stay consistent between documents, and statuses from draft through paid. That consistency is the groundwork any structured format depends on. The ledger side sits in Ettex Books with bank reconciliation and multi-currency, delivery goes out through Ettex Mail, and the agreements setting payment terms are signed in Ettex Signature.

Stated plainly, because this one matters: Ettex does not issue structured e-invoices. There is no XML or UBL output, no Peppol or equivalent network connection, no tax-authority clearance submission, no e-invoice validation and no automatic archiving to a certified store. Ettex produces human-readable invoices with consistent data. If a mandate or a customer requires a structured format, you will need software or a service provider that supports it — and the clean data described above is what makes that transition straightforward.

Sending faster helps only if somebody reads the ageing. Aged debtors shows whether the gain in dispatch time turned into a gain in collection time, which it frequently does not.

Common misunderstandings

• Believing a PDF by email satisfies an e-invoicing mandate. It generally does not.
• Assuming the rules are the same across borders — they differ by country and by customer type.
• Leaving it until the deadline, when providers are busiest and testing takes longest.
• Inconsistent customer identifiers and tax numbers, which cause rejections that look mysterious.
• No owner for rejected invoices, so they sit unpaid and unnoticed.
• Discarding the human-readable copy, which is still what people query against.
• Buying a platform before establishing what is actually required of you.

Electronic invoicing means structured data, not a PDF. Find out what your jurisdiction and your customers require, clean your invoice data first, test with one customer — and treat the deadline as earlier than it looks.