Philippines software compliance

BIR rules require POS and CAS software to gain accreditation and generate primary invoices with full tax details. Systems must maintain non-resettable grand totals, tamper-evident audit logs, and 5-year e-journals while transmitting JSON payloads to the EIS within 3 days. Adjustments require dedicated credit notes.

Under Bureau of Internal Revenue (BIR) regulations, software used to operate Point-of-Sale (POS) terminals, Cash Register Machines (CRMs), Computerized Accounting Systems (CAS), and other invoicing solutions must support the Philippines’ invoicing, registration, record-retention, and audit requirements. However, the applicable registration procedure depends on the type of system involved.

For CRM/POS machines and sales receipting software, the BIR maintains an accreditation and registration framework through its Enhanced Electronic Accreditation and Registration (eAccReg) System. Suppliers of POS/CRM machines and relevant sales software are subject to BIR accreditation requirements, while each machine used by a taxpayer must be properly registered before use. A compliant registered POS/CRM is associated with a Machine Identification Number (MIN) and Permit to Use (PTU) information. The BIR’s post-evaluation procedures also allow tax officers to extract information from the electronic sales journal and Z-readings to verify that recorded sales correspond with the taxpayer’s accounting records.

The position is different for Computerized Accounting Systems (CAS). Under the simplified registration procedure introduced by RMC No. 5-2021, businesses using CAS, computerized books of accounts, or their components register the system with the relevant BIR office and receive an Acknowledgement Certificate (AC). A separate Permit to Use is no longer required for a newly registered CAS under this procedure. The BIR may nevertheless conduct a post-evaluation to determine whether the registered system complies with the applicable standards, and significant system upgrades or changes affecting financial functionality may require a new registration.

From an invoicing perspective, software must also reflect the changes introduced by the Ease of Paying Taxes Act. An invoice is now the primary document for both sales of goods and supplies of services, replacing the previous framework under which official receipts commonly served as primary documents for service transactions. POS, CAS, and invoicing software should therefore be configured to issue an invoice as the principal sales document rather than relying on an official receipt for a service sale.
The invoice must contain the information prescribed by the BIR. This includes the seller’s registered name, VAT or non-VAT status, TIN and branch code, registered business address, invoice terminology, transaction date, serial number, description of the goods or services, quantity, unit cost, and total amount. For VAT-registered sellers, the VAT amount must be separately shown. Software must also provide for buyer information where required. However, for ordinary B2C transactions, the buyer’s business address and TIN are not required, so retailers should not configure these fields as universally mandatory for every consumer transaction.

The software environment must also preserve a reliable audit trail. BIR requirements for POS systems include the generation of an electronic sales journal and Z-readings, while system functionality must not be manipulated in a way that prevents or suspends the proper recording of sales. Reprinted transaction documents must also remain identifiable as reprints so that duplicate printing does not affect stored sales information.

Record retention is another important software consideration. Under RR No. 7-2024, books of accounts and other accounting records must generally be retained for five years. For computerized books and records, preservation may be in electronic form. The concept of accounting records includes supporting documents such as invoices, receipts, vouchers, and other source records. Consequently, retailers should ensure that their POS, ERP, and CAS environments can preserve historical transaction data in an accessible form throughout the applicable retention period.

Corrections, returns, cancellations, and other adjustments must likewise remain traceable. Credit memos, debit memos, and similar documents can be used as supplementary documentation, while the relationship between an adjustment and the original transaction should remain identifiable in the accounting records. For software developers, this means that transaction corrections should not simply overwrite or erase the original sale. The system should preserve sufficient information to reconstruct the original transaction and subsequent adjustment during a BIR inspection or audit.

A further technical layer is being introduced through the Philippines’ transition toward electronic invoicing and electronic sales reporting. RR No. 11-2025 requires covered taxpayers to issue electronic invoices containing structured invoice data that can be electronically extracted and made ready for transmission to the BIR. A document is therefore not considered an electronic invoice merely because it was generated by a POS or accounting program and then printed. The underlying system must have the required electronic-data capability.

For taxpayers already operating under the existing Electronic Invoicing and Sales Reporting System (EIS) framework, communication with the BIR is based on system-to-system transmission. Taxpayer-developed middleware is subject to BIR certification, and the EIS certification process provides for issuance of a Permit to Transmit (PTT) for the required sales data. Current EIS architecture includes an API transmission service.

The existing EIS technical model uses structured transaction data, including JSON-based transmission, and the earlier EIS rules established transmission in real or near-real time, generally within three calendar days. However, this requirement should not be interpreted as meaning that every POS retailer currently has to transmit each transaction in JSON format within three days. The expanded electronic invoicing and sales-reporting framework is being implemented progressively.

Under RR No. 26-2025, the December 31, 2026, electronic-invoicing deadline applies to specified taxpayer groups, including small, medium, and large taxpayers engaged in e-commerce or internet transactions; taxpayers under the Large Taxpayers Service, taxpayers classified as Large Taxpayers under the EOPT framework; and taxpayers using CAS, computerized books with electronic invoicing, or other invoicing software.

Importantly for the retail sector, businesses that fall within the rules solely because they use a POS system are treated separately. RR No. 26-2025 provides that POS users will become subject to mandatory electronic invoicing once the BIR establishes the necessary system and issues separate implementing revenue regulations. Therefore, it would be too broad to state that every Philippine retailer must complete EIS API integration by December 31, 2026.

Based on the current Philippine requirements, it is our opinion that software compliance should be approached as a combination of correct BIR registration, compliant invoice generation, secure record retention, reliable audit trails, and preparation for electronic data transmission. Retailers should also determine whether they fall within the December 31, 2026, taxpayer categories before implementing EIS integration solely on the basis that they operate a POS system. Where BIR accreditation, registration, or EIS middleware certification is required, businesses and software vendors should follow the formal BIR process rather than relying on internal or self-certification alone.

Is your software system aligned with the BIR’s technical and transmission mandates?

Businesses covered by the December 31, 2026 deadline should review their invoicing architecture early, including their CAS, ERP, e-commerce platform, middleware, and other invoicing software, to ensure that structured invoice data can be produced and that the system can support the applicable BIR electronic-invoicing requirements.

Here you can find the Revenue Memorandum Circular No. 5-2021. Source

Ljubica Blagojević, Junior Legal Research Specialist at Fiscal Solutions

Linkedin profile