Philippines — BIR EIS: e-invoicing mandate by waves (2022-2026)

The Philippines is rolling out a national e-invoicing system run by the Bureau of Internal Revenue (BIR) through its Electronic Invoicing System (EIS), entering pilot on 1 July 2022 under the TRAIN Law (Republic Act 10963 of 2017). The format is a proprietary BIR JSON submitted over a REST API, with phased enrolment by taxpayer segment continuing through 2026.

Regulatory timeline

19 December 2017 — Republic Act 10963 (TRAIN Law). Section 237-A introduces the obligation for Large Taxpayers, exporters and e-commerce platforms to issue invoices and receipts electronically within five years.
30 June 2022 — Revenue Regulations 8-2022. Sets the operational framework for the EIS: mandatory fields, REST API, optional Phase 1 electronic signature, 10-year archival.
1 July 2022 — EIS Phase 1 pilot launch. First batch of 100 Large Taxpayers (LT); BIR live environment on eis.bir.gov.ph with a parallel sandbox.
5 July 2022 — Revenue Regulations 9-2022. Spells out penalties (PHP 1,000 per missing invoice, capped at PHP 25,000 per day) and accreditation rules for software vendors (Permit to Use, PTU).
2024 — Waves 2 and 3. Extension to remaining Large Taxpayers and VAT-registered exporters (12% rate).
2025-2026 — Waves 4 to 6. Roll-down to Medium and Top 20,000 taxpayers; schedule released through BIR communiqués (RMC — Revenue Memorandum Circular).

Technical schema

The format is a proprietary BIR JSON exposed by the EIS API. There is no direct UBL/CII mapping: the structure is derived from the BIR 2550M/Q VAT form, with three main document types:

Sales Invoice (SI) — sale of goods, triggers VAT.
Sales Receipt (SR) — supply of services.
Credit/Debit Note (CN/DN) — corrections.

Minimal Phase 1 Sales Invoice example:

jsonbir-eis-sales-invoice.json

{
  "documentType": "SI",
  "documentNumber": "SI-2026-0000423",
  "documentDate": "2026-05-19",
  "seller": {
    "tin": "000-123-456-000",
    "registeredName": "Ediverse Demo Philippines Corp",
    "address": "5F BGC Corporate Center, Taguig City",
    "vatRegistration": "VAT"
  },
  "buyer": {
    "tin": "000-789-012-000",
    "registeredName": "Customer Demo Inc",
    "address": "Makati Avenue, Makati City"
  },
  "lineItems": [
    {
      "description": "Cloud subscription May 2026",
      "quantity": 1,
      "unitOfMeasure": "EA",
      "unitPrice": 50000.00,
      "amount": 50000.00,
      "vatRate": 12.0,
      "vatAmount": 6000.00
    }
  ],
  "totalSales": 50000.00,
  "totalVat": 6000.00,
  "totalAmountDue": 56000.00,
  "currency": "PHP"
}

The document number must respect the series control approved by the BIR via the ATP (Authority to Print) permit or its electronic equivalent for accredited software vendors.

Submission flow

The seller submits in near real time via POST /api/v1/invoices. The EIS validates schema, TIN, sequencing, then returns an internal identifier and the reception timestamp. The visual representation (PDF + BIR QR Code) is generated seller-side from the accepted payload.

textbir-eis-flow.txt

┌──────────────┐    ┌──────────────────┐    ┌──────────────┐
│ Seller PH    │───>│ BIR EIS API      │───>│ Buyer PH     │
│ (ERP, JSON)  │    │ eis.bir.gov.ph   │    │ (PDF + QR)   │
└──────────────┘    └────────┬─────────┘    └──────────────┘
                             │
                             ▼
                  ┌───────────────────┐
                  │ EIS assigns       │  ← 7-day rejection
                  │ DocumentID + ts   │     window for resubmit
                  └───────────────────┘

The post-rejection resubmission window is 7 calendar days. Beyond that, the invoice is treated as undeclared and the corresponding VAT is not deductible buyer-side.

Validation

EIS portal: eis.bir.gov.ph — production with eFPS (Electronic Filing and Payment System) login.
Sandbox: sandbox-eis.bir.gov.ph — test environment for vendors applying for a PTU.
Technical documentation: JSON schemas, code lists and a Postman collection published through the BIR-EIS developer portal.
Permit to Use (PTU): every system emitting to the EIS must obtain a PTU issued by the BIR Computerized Systems Evaluation Team (CSET).

Common pitfalls

TIN with branch. The Philippine TIN is made of a 9-digit root + a 3 to 5-digit branch suffix. Integrations that ignore the branch code surface reconciliation gaps on multi-branch buyer sides.
PTU required before production. Going live without an issued PTU exposes to RMC penalties: PHP 25,000 + PHP 1,000 per invoice issued without PTU. CSET instruction time is 6 to 12 months.
Numbering series. Each branch is granted its approved number range by the BIR; sequence gaps automatically trigger an alert that may block subsequent submissions until reconciled.
VAT-exempt vs zero-rated. Exporters are zero-rated (0%) with input VAT credit, while VAT-exempt transactions (PEZA, BOI incentives) must carry a distinct exemptionCode. Frequent confusion leading to costly retroactive adjustments.
BIR QR Code on the visual. The QR Code must encode the DocumentID returned by the EIS and the SHA-256 hash of the submitted payload. PDF generators that hash a reformatted version (spacing, field order) produce an invalid QR.

Cross-links

Singapore — InvoiceNow, alternative APAC approach (PEPPOL PINT vs proprietary BIR JSON).
Vietnam — hóa đơn điện tử, comparable wave-based roll-out.
Indonesia — e-Faktur DJP + CoreTax, neighbouring universal mandate.
Article — APAC e-invoicing mandate tracker.
Official sources: bir.gov.ph — Electronic Invoicing System, Republic Act 10963 — TRAIN Law.

Foundations

Standards

Flagship messages

Tools