EazLink guide

Is a PDF invoice an electronic invoice under RR 11-2025?

Why buyer delivery format and structured, extractable invoice data are two different parts of the Philippine definition.

Updated 2026-09-06 by the EazLink team. Editorial review: EazLink Editorial Team.

PDF vs electronic invoice shown through the EazLink Philippine e-invoicing workflow

Direct answer

A system-generated invoice may be delivered electronically, including as a PDF attachment or through an application, but RR 11-2025 also requires structured invoice data that can be extracted and readily transmitted. A photo or scanned copy of a paper invoice is expressly not an electronic invoice. A PDF by itself does not prove that the underlying structured data exists.

What to remember

  • Delivery to the buyer and structured data readiness are separate questions.
  • A scan of paper is not an electronic invoice under the regulation.
  • A PDF can accompany a system-generated electronic invoice.
  • The system must preserve extractable fields and a consistent document identity.

Common invoice outputs

The file extension does not settle the compliance answer.

OutputStructured source dataRR 11-2025 concern
Scanned paper invoiceNoExpressly excluded from the definition
PDF exported from a systemMaybeCheck whether structured data can be extracted and transmitted
JSON or XML record plus buyer copyYes, if correctly producedStill subject to content and process requirements

Ask how the PDF was created

A system can render a PDF from a structured invoice record. In that case, the PDF is one presentation of data that also exists in fields.

A scan is different. Optical character recognition may recover some text later, but the original transaction was not created as structured invoice data.

Keep one document identity

The buyer copy, accounting record and transmitted record should point to the same invoice. If totals or identifiers diverge, reconciliation becomes difficult.

Version the rendering and mapping rules so a correction can be traced to the exact source event.

How middleware helps

EazLink receives the structured record rather than scraping the buyer PDF. It can validate fields, create the configured external payload and return the result.

The buyer-facing document can remain part of the business system's normal workflow.

Invoice format check

  1. Identify the system-generated source record.
  2. Confirm required fields are stored separately.
  3. Link the buyer copy to the same invoice ID.
  4. Test extraction without OCR.
  5. Review the result against current BIR rules.

Quick questions

Is emailing a scanned invoice enough?

No. RR 11-2025 says a photo or scanned copy of a paper invoice is not an electronic invoice.

Can a buyer still receive a PDF?

The regulation describes electronic delivery formats that can include PDF. The underlying structured data requirement still matters.

Should middleware read invoice PDFs?

A direct structured-data feed is more reliable. PDF parsing loses context and creates avoidable validation problems.

Continue the preparation

Sources and verification

Check the current BIR rules and portal notices before making a compliance decision.