An electronic invoice is invoice data created, transmitted and received in a structured digital format that software can process. It is not simply a paper invoice saved as a PDF. A PDF may be readable on screen, while a structured e-invoice carries defined fields that accounting, tax or procurement systems can validate and post.
What information does an electronic invoice contain?
The required fields depend on the transaction and applicable rules, but the operating record commonly includes:
- Supplier and buyer legal details and tax identifiers
- Invoice number, issue date and relevant supply or tax date
- Purchase order, contract or delivery references
- Line descriptions, quantities, units, prices and discounts
- Tax categories, rates and amounts
- Currency, totals, payment terms and payment instructions
How does electronic invoicing work?
- The supplier creates invoice data from the approved order, delivery or billing event.
- The sending system validates required fields and converts the record to the accepted schema.
- The invoice travels through the required network, portal or authorized channel.
- The receiving system validates the structure and business rules before posting or routing an exception.
- Status messages, approvals, adjustments and payment references remain linked to the invoice.
Electronic invoice vs. PDF invoice
A PDF invoice preserves a visual document but usually requires extraction or manual entry before another system can use its fields. A structured electronic invoice is designed for machine processing. Some regimes use a hybrid document with both a human-readable rendering and embedded structured data; the presence of a PDF alone does not establish that the invoice meets an e-invoicing requirement.
What should be verified?
Confirm the permitted format, transmission channel, tax treatment, required identifiers, signature or clearance rules where applicable, and the treatment of credit notes and corrections. These requirements differ by jurisdiction and transaction type. Keep the original structured record and validation response rather than relying only on a rendered copy.
How does it fit the payment workflow?
An accepted e-invoice can reduce rekeying and make matching easier, but acceptance does not prove delivery, approval or payment. Link the invoice to its purchase order, receipt or service evidence, approval history and final payment reference.
