Electronic invoicing is not a PDF by email. The distinction matters increasingly, because a growing number of countries now mandate the structured version.
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.
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.
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.
Issuing and receiving invoices in a structured, machine-readable format that the recipient's system processes automatically — not a PDF attached to an email.
Generally no, in the regulatory sense. A PDF is an image of an invoice; a structured e-invoice is data conforming to a defined standard.
It depends on your country, your customers and sometimes your size, and the timetables change. Public-sector supply has required it in several jurisdictions for years, with business-to-business mandates rolling out. Check with your tax authority or accountant.
Establish what applies to you and ask your largest customers what they need, then clean your invoice data — identifiers, tax treatment, references — before choosing any tooling.
Modest but real: no retyping at the buyer's end, fewer disputes, faster approval and often faster payment. At low volume the driver is usually compliance or a customer requirement.
No. It produces human-readable invoices with consistent data; structured formats and network transmission require software or a provider built for that.
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.
Credit control is the set of decisions made before an invoice exists — who gets terms, how much, and what happens when they slip. Chasing is what you do when those decisions were never made.
AP automation is sold as one product, but it is four separate jobs with very different payback. Capture and matching are where the software earns its price; approval and payment are mostly a question of whether anyone wrote the rules down.
Dynamic pricing in retail means moving prices with demand, stock and competition. It reliably raises margin and just as reliably damages customer trust when the rules behind it are not defensible.