What is the EIS — and why a PDF isn't an e-invoice
Plenty of agencies already email PDF invoices and assume they're “doing e-invoicing.” They're not. The BIR's Electronic Invoicing System (EIS) is about structured data, not digital paper — and the distinction is the whole point.
What the EIS is
The EIS is the BIR's platform for receiving invoice data electronically. Under the EOPT Act and CREATE MORE, covered taxpayers must issue invoices as structured, machine-readable data — in the BIR's prescribed JSON format — that can be validated automatically and, when the system is fully live, transmitted for electronic sales reporting.
Structured vs unstructured
| Aspect | PDF / scanned invoice | Structured e-invoice |
|---|---|---|
| What it is | A picture of an invoice | Invoice data (JSON fields) |
| Machine-readable | No — needs OCR guesswork | Yes — parsed and validated |
| Numbering | Whatever you typed | System-controlled sequence |
| Meets the mandate | No | Yes |
Why a PDF fails
A PDF can be a perfect human-readable copy of an invoice and still not satisfy the mandate, because the BIR needs the underlying data — line items, amounts, tax fields — in a form it can validate without a human retyping anything. A scanned image is even further away: it's pixels, not fields.
What agencies actually need
- A billing system that emits invoices as structured data with controlled SI- numbering.
- Correct tax treatment on the service fee — 12% VAT and 2% EWT — computed, not typed.
- The ability to register that billing module as a CAS component per client / RDO.
- A human-readable copy (PDF is fine here) alongside the structured record — not instead of it.
Issue structured invoices, not PDFs.
NexusWorkforce generates EIS-ready service invoices as structured data from your DTR — with a clean PDF copy alongside, never instead of, the real record.
Book a demo