BIR E-Invoice Unique ID Philippines 2026: Format, Generation & Validation Guide

Every e-invoice you send to the BIR carries a Unique ID, and it's what separates one document from millions of others in the system. With covered taxpayers having until 31 December 2026 to set up the electronic invoicing requirements, getting this ID right is an important part of preparing your system. Get it wrong, and the EIS rejects your submission before it goes anywhere.

Key Takeaways

• The Unique ID is a mandatory field in the BIR's JSON invoice schema.
• Your invoicing system/EIS generates it. The BIR doesn't issue it to you.
• No two documents can share an ID across any year or any branch.
• The EIS checks it on arrival and bounces duplicates straight back.
• Corrections reference the original ID, so a bad one breaks your audit trail.

What is a BIR e-Invoice Unique ID?

A BIR e-Invoice Unique ID is the Philippine e-invoice unique reference number that marks out a single electronic document within the Electronic Invoicing System. It sits inside the JSON payload alongside your invoice data, and no other document you ever transmit can share it.

Under RR No. 11-2025, issued on 27 February 2025 under the CREATE MORE Act, every covered taxpayer in the Philippines must generate and transmit e-invoices through the BIR's Electronic Invoicing System (EIS), and the Unique ID is the field that makes each document traceable within that system.

People often mix this up with the invoice number printed on the document. They aren't the same thing. Your invoice number is what your customer sees and what your books run on. This BIR invoice reference ID is what the system uses to track that document internally.

Who Needs a BIR e-Invoice Unique ID?

The Unique ID applies to every business covered by the e-invoicing mandate. Under RR No. 26-2025, which extended the deadline to 31 December 2026, the covered groups are:

• E-commerce and internet-transaction taxpayers, whether classified as Small, Medium or Large. Micro taxpayers in this group are exempt.
• Taxpayers under the BIR's Large Taxpayers Service (LTS).
• Large Taxpayers as classified under RA 11976 (the Ease of Paying Taxes Act) and RR No. 8-2024.
• Users of a Computerised Accounting System (CAS), Computerised Books of Accounts (CBA) with electronic invoicing, or other invoicing software.

Head offices and all branches of a covered taxpayer are included. Micro taxpayers, meaning those with gross annual sales under PHP 3 million, are exempt from the mandate. They can still opt in, and if they do, they can claim the setup cost deduction.

Why the BIR Unique ID is Important

There are four reasons why you should use the Unique ID-

• It prevents duplicates- The EIS matches every incoming ID against what it already holds. Send the same one twice and the second transmission fails.
   
• It links your corrections- When you issue a credit note or debit note, the JSON spec requires you to name the document you're correcting through the field referencing the original document's Unique ID.  field. Without an accurate original ID, that link breaks.
   
• It supports your audit trail- The BIR cross-checks transmitted sales data against your VAT filings. The unique ID is the thread that ties an individual document to what you declared.
   
• It's a legal requirement- RR No. 11-2025 requires every e-invoice transmitted to the EIS to carry a unique document identifier. Without it, your invoice isn't compliant.

Structure and Format of the BIR e-Invoice Unique ID

The official reference is the BIR's EIS JSON File Format v2.01 (dated 25 March 2022), alongside the EIS e-Invoice API Development Guide v2.2 (September 2022). Always build against the current version of these documents on the EIS Certification Portal, since the BIR can revise them.

Under that specification, the Document ID is defined simply as a string: a unique identifier linked to the underlying transaction. The schema does not prescribe a fixed internal layout for it. In practice, the system generates a 24-character EisUniqueId, combining the issuance date, the EIS certificate ID, and a control value.

Because the schema only requires uniqueness, most EIS-compliant systems build the ID from elements that guarantee it. It is a common design pattern, not a BIR-mandated format:

Combine enough elements that a collision becomes impossible, even across branches issuing documents at the same moment.

If you operate multiple branches, give each one its own prefix or code within the ID. Two branches generating from the same sequence is one of the fastest ways to produce duplicates.

How BIR EIS Validates the Unique ID

Validation happens when your document reaches the EIS, and it runs through several checks.

1. Schema check - does the ID match the format the schema demands?
2. Uniqueness check - has this ID already been received?
3. Signature check - does the JSON Web Signature verify against your registered key?
4. Field completeness - are all mandatory fields present alongside it?

Pass all four, and the BIR returns an acknowledgement. Fail any one, and you get a rejection notice telling you what went wrong. Nothing is stored until it passes.

Remember that transmission isn't open-ended. Sales data must reach the EIS within three calendar days of the transaction, so a rejection you don't notice quickly can turn into a late submission.

How Businesses Use the Unique ID

The Unique ID is the backbone of invoice tracking in the Philippines. Here's how businesses put it to work day-to-day.

• Tracking a document through transmission, acknowledgement and archive.
• Referencing originals when raising credit or debit notes.
• Reconciling transmitted invoices against your books each period.
• Answering BIR queries during an audit, where the ID locates the exact record.
• Verifying authenticity, since a document with no valid, acknowledged ID was never properly transmitted.

Keep your acknowledgements as well as your invoices. The BIR expects electronic records retained for ten years from the day following the return-filing deadline for the taxable year of the last entry, with printed backups for the first five.

Common Unique ID Errors & How to Fix Them

Conclusion

Getting the Unique ID right comes down to preparation. Before your deadline, put your setup through end-to-end checks covering schema validation and transmission. Finding a sequencing fault once you're in production is far harder to fix, and the cost is real. Under Section 264-A of the Tax Code, failing to transmit sales data draws a penalty of PHP 10,000 or 1/10 of 1% of your annual net income, whichever is higher, for each day of failure. Past 180 days of violation in a year, the BIR can order permanent closure.