SearchStart a task
Guides›fundamentals
fundamentals

What is a structured electronic invoice?

Understand why a PDF attachment alone is usually not a structured e-invoice and how machine-readable business terms enable automation.

structured electronic invoicee invoice vs PDFmachine readable invoice

What it means

A structured electronic invoice stores business terms as machine-readable fields rather than only positioning text on a page.

The recipient can import supplier, buyer, line, tax, total and payment data without manually retyping the document.

A PDF can be part of a hybrid invoice, but a standalone visual PDF is normally not the structured payload required by an e-invoicing mandate.

Implementation method

  1. 1
    Identify the semantic model and syntax required by the recipient or authority.
  2. 2
    Map accounting fields to explicit business terms and controlled codes.
  3. 3
    Validate the structure and business rules before delivery.
  4. 4
    Preserve both the authoritative source and a readable rendering.

Common mistakes

!
Treating an emailed PDF as a compliant structured invoice

Build an explicit control or test case for this condition.

!
Using XML without the required profile identifiers

Build an explicit control or test case for this condition.

!
Dropping purchase-order, exemption or payment references during export

Build an explicit control or test case for this condition.

!
Assuming a file that opens successfully is legally accepted

Build an explicit control or test case for this condition.

Questions and answers

Is every XML file an electronic invoice?

No. The XML must follow the required syntax, semantic model, profile and business rules for the transaction.

Can a human-readable PDF still be useful?

Yes. It helps review and archiving, but it should be linked to the authoritative structured document.

Can EInvoiceLab officially certify structured electronic invoices?

No. EInvoiceLab can inspect, prepare and explain technical data, but official conformance, delivery or acceptance depends on the active authority, network, accredited provider and validation artefacts.

Should I keep the original structured file?

Yes. Preserve the original XML or JSON, its hash, every validation report and the final authority or network response. A readable PDF should not replace the source document.