BIR E-Invoice Data Fields are essential for meeting the technical requirements of the Philippine e-invoicing system. Businesses must understand which fields are required on each invoice, the correct data formats, record retention requirements, and procedures for cancelling or correcting invoices that have already been transmitted. These specifications are critical for ensuring that billing systems, accounting teams, and IT integrations process transactions accurately and support applicable BIR compliance requirements from go-live onward.
This article provides a complete technical reference for Philippine e-invoice data requirements under RMC 98-2026, explains how e-invoice records differ from scanned PDFs and traditional paper invoices, and gives step-by-step guidance on the cancellation and reissuance process. It is designed for finance managers, billing team leads, and IT integration specialists who need a definitive technical reference rather than a high-level overview.
Key Takeaways
- Every BIR e-invoice must include a defined set of mandatory data fields — buyer TIN is required on all VAT invoices, and missing required fields cause EIS submission rejection with no reference number issued.
- BIR e-invoices are transmitted in JSON format via REST API — they are not scanned PDFs, email attachments, or manual portal uploads; the data format is machine-readable and structured.
- An e-invoice is fundamentally different from a scanned or PDF invoice: the EIS-transmitted data record is the legal document, not the printed or emailed representation of it.
- BIR rules require e-invoice records to be retained for ten years — this applies to both the EIS transmission records and the invoice document copies, stored in a manner accessible for BIR audit.
- Invoice cancellations and reissuances must be processed through the EIS — a cancelled invoice is not simply voided in your own system; the cancellation must be transmitted as a separate EIS transaction referencing the original EIS reference number.
What Information Must a BIR E-Invoice Contain?
RMC 98-2026 specifies the mandatory data fields that every e-invoice must contain for EIS submission. These fields are validated by the EIS system, and a submission with any missing required field is rejected — no EIS reference number is issued, and the transaction is not recorded in the BIR system until a correct submission is made. The mandatory fields apply to both sales invoices (for goods) and official receipts (for services).
1. Taxpayer Identification Fields
BIR sales invoice mandatory information includes the seller’s TIN (with branch code, if applicable), registered business name, and registered business address, as required by applicable BIR regulations. These details should match the taxpayer’s BIR registration records to help prevent submission errors. Businesses should keep their registration information accurate and updated, particularly after changes to their registered business name or address, to support smooth e-invoice processing and compliance.
2. Invoice Reference Fields
Every e-invoice must include a unique invoice number from the taxpayer’s registered invoice series, the invoice date (in ISO 8601 format: YYYY-MM-DD), and the invoice type code (standard VAT invoice, zero-rated, exempt, credit note, or debit note). The invoice number must be sequential within the registered series and cannot duplicate any previously issued number. If your billing system generates invoice numbers automatically, confirm that the numbering logic produces unique, sequential numbers and that the series is registered with the BIR.
3. Buyer Information Fields
For VAT invoices (standard 12% VAT), the buyer’s TIN, registered business name, and registered address are mandatory fields. For retail transactions with non-business buyers who do not have a BIR TIN, the BIR provides a substitute identifier for retail customers. Confirm with your accredited provider the specific handling for non-TIN buyers in your industry. For zero-rated or VAT-exempt transactions, buyer information requirements are specified separately in RMC 98-2026.
4. Transaction Detail Fields
BIR E-Invoice Data Fields include a description of the goods or services, unit of measure, quantity, unit price, and line total for each invoice item. The invoice should also show the total amount before VAT, the applicable VAT amount broken down by rate when multiple rates apply, and the total invoice amount including VAT. Discounts should be itemized separately where applicable. PHP is the standard currency unless another currency is specified for foreign currency transactions. Businesses should verify the required fields and formatting against the latest applicable BIR technical specifications to support accurate invoice processing and compliance.
| Field Category | Mandatory Fields | Common Errors |
|---|---|---|
| Seller identification | TIN, registered name, address | Mismatch with BIR records; outdated address |
| Invoice reference | Invoice number, invoice date, invoice type | Non-sequential numbering; incorrect date format |
| Buyer information (VAT invoices) | Buyer TIN, registered name, address | Missing or unverified buyer TIN |
| Line items | Description, quantity, unit price, line total | Overly abbreviated descriptions; zero-quantity lines |
| Tax summary | Pre-VAT total, VAT amount by rate, total with VAT | VAT rate misclassification; arithmetic errors |
E-Invoice Data Formats and Technical Standards
BIR E-Invoice Data Fields must follow the BIR’s applicable technical specifications for structured invoice submissions. BIR e-invoices are transmitted in JSON (JavaScript Object Notation) format over HTTPS through a REST API. JSON is a structured, machine-readable format, not a word processing document, spreadsheet, or PDF. The BIR’s JSON schema defines field names, data types, and validation rules. Your integration must generate JSON that conforms to the applicable schema, with accurate field names, data types, and structures to help prevent validation errors and support successful invoice submission.
The BIR has published the JSON schema specification as part of RMC 98-2026 and as a technical annex available from the BIR website. Your accredited provider implements this schema on its API gateway, and the connector you use maps your system’s invoice data to the required BIR JSON fields. Ensure your integration is tested against the exact schema version your provider implements, as technical specifications may be updated through subsequent bulletins. Understanding the Philippines tax record retention period is also essential for compliance planning, helping businesses establish appropriate recordkeeping, secure storage, and retrieval procedures in line with applicable BIR requirements.
E-Invoice vs Scanned PDF vs Printed Invoice: What Is the Legal Difference?
This is one of the most misunderstood aspects of the mandate. Under RR No. 11-2025 and RMC 98-2026, the legal e-invoice is the EIS-transmitted data record — the JSON submission received and validated by the BIR EIS with an assigned reference number. The printed copy provided to the customer is a customer-facing representation of that record, rather than the underlying electronic record itself. Understanding BIR E-Invoice Data Fields helps businesses maintain accurate structured invoice data, preserve EIS reference numbers, and ensure their invoicing systems support applicable BIR submission and recordkeeping requirements.
A scanned PDF of a printed invoice is not an e-invoice in the BIR sense — it is a digital image of a paper invoice, fundamentally different from a structured data record transmitted to the BIR electronically. Covered taxpayers who generate PDF invoices and email them to customers without the required EIS transmission may not meet applicable compliance requirements. Similarly, a printed invoice booklet that has been photocopied and stored as a PDF does not qualify as a structured e-invoice. Review the BIR E-Invoicing Deadline to understand the applicable implementation timeline and prepare your business for compliance.
The practical implication is that your compliance is determined by whether your EIS transmission records are complete and match your sales activity — not by whether you have digital copies of your invoices in any other format. BIR auditors will examine EIS transmission records, not PDF files. Having complete EIS records protects you; having PDF scans of paper invoices with no EIS records does not.
E-Invoice Record Retention Requirements
BIR regulations require that e-invoice records be retained for ten years from the date of issuance. This retention requirement applies to both the EIS transmission records (which your accredited provider should maintain on their platform) and the invoice document copies (which your own systems should archive). For businesses transitioning from paper invoicing, ten years from the go-live date means some invoices issued in 2026 must be retainable until 2036.
Retention must be in a format accessible for BIR audits on demand. EIS records stored in a provider’s cloud platform may support retention requirements if the records remain accessible and meet applicable regulations. However, businesses should maintain an independent archive of EIS confirmation receipts, including reference numbers, transmission timestamps, and invoice data, in case provider access is disrupted due to provider failure, contract termination, or disputes. Archiving records in a local document management system or secondary cloud storage provider is a practical backup approach. Odoo e-invoice integration can help businesses streamline invoice generation, manage digital invoicing workflows, and organize invoice records for easier tracking and retrieval.
Credit Notes, Cancellations, and Reissuance Procedures
Errors on EIS-transmitted invoices cannot be corrected by simply editing the invoice in your own system — any correction must be processed through the EIS. For a cancelled invoice, a cancellation transaction referencing the original EIS reference number must be transmitted. For a corrected invoice (correcting a data error), a cancellation followed by a new invoice with the correct data must both be transmitted. For an adjustment to the invoice amount (common in services billing for scope changes), a credit note or debit note transaction is transmitted.
1. Invoice Cancellation
Submit a cancellation transaction to the EIS referencing the original invoice’s EIS reference number, invoice number, and date. Follow the applicable BIR cancellation deadlines and procedures, including any exceptions that may apply. The EIS records the cancellation against the original transaction. Update your accounting system to record the cancellation and reverse the associated revenue and VAT entries, where applicable. Romania Advintek can support businesses with e-invoicing integration, automated invoice processing, and digital compliance workflows to help streamline invoicing operations and prepare for applicable Romanian e-invoicing requirements.
2. Invoice Correction (Cancellation + Reissuance)
Cancel the incorrect invoice through the EIS (as above), then issue a new invoice with the correct data through the same EIS submission process. The new invoice has its own unique invoice number and EIS reference number. The buyer should be provided with the new correct invoice and notified of the cancellation of the previous one. Both the cancellation and the new invoice must be reflected in your VAT return for the period.
3. Credit Notes for Partial Adjustments
For partial adjustments (a discount applied after invoice issuance, a partial return of goods), issue a credit note referencing the original invoice’s EIS reference number. The credit note is transmitted to the EIS as a separate transaction type. The credit note amount reduces the buyer’s input tax entitlement and the seller’s output tax liability for the period in which the credit note is issued, not necessarily the period of the original invoice.
Conclusion
Getting the technical details right — mandatory data fields, JSON format, record retention, and correction procedures — is what separates a technically compliant e-invoicing implementation from a system that produces rejected submissions, incomplete records, and audit exposure. Invest in the data field mapping exercise, complete rigorous sandbox testing, and establish a formal correction procedure before go-live.
Nexright’s technical compliance team supports businesses through every aspect of BIR EIS integration, from data field mapping and sandbox testing to record retention design and correction procedure documentation. Contact us for a technical readiness assessment.
Frequently Asked Questions
1. What happens if I transmit an invoice to the EIS with a buyer TIN error?
The EIS validates buyer TIN data against BIR records. An invalid TIN — one that does not match a BIR-registered taxpayer — typically causes submission rejection. You will receive an error response indicating the TIN validation failure. Correct the buyer TIN in your system (verify directly with the buyer) and resubmit. Do not issue the invoice to the buyer until the EIS submission is successful and an EIS reference number is received.
2. Can I batch-submit invoices to the EIS at end of day rather than in real time?
RMC 98-2026 requires near-real-time transmission — invoice data should reach the EIS at the time of issuance, not in end-of-day batches. The BIR recognizes that some latency is technically unavoidable and does not require transmission to be literally instantaneous, but systematic end-of-day batch processing — where invoices are issued during the day and transmitted only at closing — is not consistent with the real-time model the EIS is designed to operate on. High-volume, time-critical situations (POS environments) may involve brief buffering; consult your provider on the approved approach for your use case.
3. How long do I have to cancel an invoice after it has been transmitted?
BIR rules require that cancellations be processed within the same reporting period (calendar month) as the original invoice where possible. Cancellations outside the original reporting period are technically possible but create more complex VAT period adjustment issues. Build your billing workflow so that errors are identified and cancellations are processed promptly — within the same month is the strong preference, and within the same business week is the operational best practice.
4. What is the BIR’s approach to invoice data privacy for buyer information?
Invoice data transmitted to the BIR EIS, including buyer TINs and business names, is subject to Philippine data privacy law under RA 10173. The BIR is a government agency with specific legislative authority to collect and maintain tax records, and the legal basis for data processing is compliance with BIR regulations. Taxpayers should ensure that their privacy notices to customers disclose that invoice data including TIN information is transmitted to BIR as required by law.
5. Does the retention period start from the invoice date or the transmission date?
The ten-year retention period runs from the invoice date (the date the transaction occurred and the invoice was issued), not from the transmission date. In practice, for real-time EIS transmission, the invoice date and transmission date are typically the same day. For downtime invoices transmitted retroactively, the invoice date (not the later transmission date) is the starting point for the retention period. Ensure your record retention system uses the invoice date field as the retention trigger.
6. Can I store EIS records outside the Philippines (e.g., in a global cloud data centre)?
Philippine data localization requirements under BIR and data privacy regulations should be reviewed carefully before storing EIS records exclusively in offshore data centres. The BIR requires that records be accessible for audit on demand — if offshore storage creates access delays or legal complications in the event of a BIR audit, it may not satisfy the retention requirement. Consult a Philippine data privacy and tax counsel on your specific storage architecture if you are considering non-Philippine cloud storage for EIS records.
7. What is the BIR’s definition of “e-invoice” for the purposes of buyer input VAT claims?
For buyer input VAT claim purposes, a valid e-invoice is one that has been transmitted to and validated by the BIR EIS, with a valid EIS reference number displayed on the invoice document. A buyer who receives an invoice from a covered Group 1 supplier that lacks an EIS reference number is receiving a document that does not meet the BIR’s definition of a valid invoice for input tax purposes. Such invoices can be expected to be disallowed in BIR audits.
Source by:
Image by Magnific
