One Company, Different Invoicing Systems: Do You Need Multiple PTIs Under the BIR E-Invoicing Rules?

Executive Summary

A company may use more than one system to issue invoices. One branch may use a POS system, another may use an ERP, while online transactions may pass through a separate invoicing platform.

This creates an important compliance question:

Does one company need only one Permit to Issue Electronic Invoice (PTI), or can separate invoicing systems require separate PTI treatment?

Under BIR RMC No. 110-2026, a PTI Electronic Invoice is the authority granted by the BIR allowing a taxpayer to issue electronic invoices through a duly registered and/or approved invoicing system. The Circular also distinguishes the PTI from a Permit to Use or Acknowledgement Certificate covering a CAS.     

However, the official BIR materials discussed here do not establish a simple blanket rule that every corporation receives only one PTI regardless of how many invoicing systems it operates, nor do they expressly state that every separate system automatically requires a separate PTI.

The safer approach is therefore to examine each invoicing setup, its registration, and the PTI authority attached to it before issuing electronic invoices.

What Is a PTI Electronic Invoice?

A Permit to Issue Electronic Invoice, or PTI, is specifically connected with a taxpayer's authority to issue electronic invoices.

RMC No. 110-2026 describes it as the authority granted by the BIR to a taxpayer to issue e-invoices through the prescribed and duly registered or approved invoicing system.  

This makes the invoicing system important.

The PTI should not be viewed simply as a general corporate permit that can automatically be assumed to cover every platform, branch configuration, POS environment, or future invoicing system operated under the same TIN.

One Company Can Have More Than One Invoicing Setup

Modern businesses rarely operate through a single accounting platform.

A company may use an ERP for head-office transactions, POS terminals in retail branches, a separate online invoicing platform for e-commerce, and another application for a specific business division.

From an operational perspective, all these systems belong to the same taxpayer.

From a BIR compliance perspective, however, the important question is whether each system forms part of the registered or approved invoicing arrangement covered by the taxpayer's authority to issue electronic invoices.

That distinction is why businesses should avoid assuming either extreme:

One TIN does not automatically mean one PTI covers everything.

At the same time:

Multiple software applications do not automatically mean multiple PTIs are required.

The actual BIR registration and system configuration must be reviewed.

When Might Separate PTI Treatment Become Relevant?

Separate PTI review becomes particularly important where the company operates genuinely different invoicing systems rather than merely multiple users or terminals within one approved environment.

For example, a company may have one electronic invoicing solution for physical stores and another for online sales.

Another company may maintain a legacy CAS for one business unit while implementing a new cloud-based invoicing solution for another.

RMC No. 110-2026 requires an Electronic Invoicing Service Provider to facilitate the application, issuance, or updating of its client-taxpayer's PTI through the BIR-prescribed procedure.     

The express reference to updating the PTI is important. It indicates that changes in the taxpayer's electronic invoicing arrangement may require regulatory action rather than simply being implemented internally without reviewing the existing BIR authority.

Step-by-Step Guide: How to Review Multiple Invoicing Systems

Step 1: List Every System That Issues Customer Invoices

Start by mapping where invoices actually originate.

Do not limit the review to the company's main accounting system.

Include branch POS systems, ERP modules, e-commerce platforms, third-party invoicing applications, and any separate system capable of issuing invoices to customers.

Step 2: Identify the BIR Registration Covering Each System

For every invoicing platform, determine what registration or approval currently exists.

Check whether it is covered by a Permit to Use, Acknowledgement Certificate, POS registration, or another BIR registration.

Remember that these registrations should not automatically be treated as PTI authority.

RMC No. 110-2026 expressly provides that a PTI is distinct from a PTU or Acknowledgement Certificate for CAS.    

Step 3: Determine Whether the Systems Are Truly Separate

A company using ten terminals connected to one centralized invoicing solution is different from a company operating two completely independent invoicing platforms.

The compliance analysis should focus on the underlying invoicing solution, registration, configuration, and BIR authority not simply the number of computers, terminals, or branches.

Step 4: Review the Existing PTI

If the company already has a PTI, determine what system or invoicing configuration it covers.

Do not assume that an existing PTI automatically extends to a newly implemented platform.

If another invoicing solution is added, the company should determine whether the existing PTI must be updated or whether a separate PTI process applies.

Step 5: Coordinate Before the New System Goes Live

Where the company uses an accredited Electronic Invoicing Service Provider, RMC No.

110-2026 places responsibility on the provider to facilitate the PTI application, issuance, or updating process for its client-taxpayer.    

This should be addressed during implementation not after the new system has already started issuing invoices.

Does Every Branch Need Its Own PTI?

Not necessarily.

The number of branches alone does not establish the answer.

For example, several branches may operate through the same centralized approved electronic invoicing solution.

In another case, different branches may operate completely separate POS or invoicing environments.

The relevant question is therefore not simply:

"How many branches do we have?"

It is:

"How many distinct invoicing systems or approved configurations are actually being used, and what does our existing BIR authority cover?"

Businesses with complex branch structures should have this confirmed before rollout.

Does Every POS Terminal Need a Separate PTI?

Businesses should also distinguish between a terminal and an invoicing system.

Having dozens of terminals does not necessarily mean the taxpayer operates dozens of independent invoicing solutions.

If the terminals are all part of one registered and approved system architecture, the compliance treatment may be different from a situation where several independent POS solutions are being operated.

The BIR issuances reviewed here do not provide a universal rule stating that one PTI must be secured for every physical terminal.

Risks of Assuming One PTI Covers Everything

The biggest risk is expanding an invoicing system without reviewing whether the existing BIR approval still corresponds to the system actually being used.

A corporation might secure a PTI for one invoicing setup and later:

Add a separate online invoicing platform;

Replace its ERP;

Migrate to a cloud system;

Engage a different Electronic Invoicing Service Provider; or

Operate another invoicing application for a new business line.

If those changes affect the registered or approved invoicing arrangement, the PTI may need to be reviewed or updated.

RMC No. 110-2026 also requires the appropriate PTI Electronic Invoice Number to be reflected on electronic invoices when required by applicable BIR issuances and technical specifications.  

Using an incorrect or outdated PTI reference could therefore create compliance and audit issues.

Practical Example 1: One ERP, Multiple Branches

ABC Corporation has 15 branches, but all invoices are generated through one centralized ERP.

The branches access the same invoicing environment and use the same approved configuration.

ABC should not automatically assume that 15 branches mean 15 PTIs.

Instead, it should confirm that the existing PTI properly covers the centralized invoicing arrangement and the branches operating under it.

Practical Example 2: ERP for Corporate Sales, Separate POS for Retail

XYZ Corporation uses an ERP for business-to-business transactions but operates a separate POS platform for its retail stores.

Because the systems are distinct, XYZ should review the BIR registration and PTI treatment of each invoicing environment.

It should not automatically assume that the PTI connected with its ERP also covers the separate POS solution.

Practical Example 3: Adding a New E-Commerce Platform

DEF Corporation already issues electronic invoices through its existing system.

It later launches an online store using another third-party platform that will independently generate customer invoices.

Before activating invoice issuance through the new platform, DEF should review whether its existing PTI covers the new arrangement or whether an update or additional PTI process is required.

Practical Example 4: Changing Electronic Invoicing Providers

A company moves from one Electronic Invoicing Service Provider to another.

Even though the taxpayer itself has not changed, the invoicing solution, interfaces, infrastructure, or system configuration may be different.

RMC No. 110-2026 recognizes that material changes to an electronic invoicing solution can require BIR evaluation or approval.     

The company should therefore review its PTI as part of the migration.

Frequently Asked Questions

Does one corporation automatically need only one PTI?

The BIR materials reviewed here do not establish a blanket "one taxpayer, one PTI regardless of systems" rule.

The PTI is tied to authority to issue electronic invoices through a duly registered or approved invoicing system. Businesses operating several distinct systems should therefore review the coverage of their existing authority.

Does every invoicing system automatically require a separate PTI?

The official materials reviewed here likewise do not expressly state a universal "one system, one PTI" rule.

The correct treatment should be determined from the taxpayer's actual invoicing architecture, registration, and BIR-prescribed PTI procedure.

What if we simply add more branches to the same system?

If the additional branches operate within the same registered electronic invoicing solution, that does not necessarily mean a completely separate PTI will be required.

However, the company should confirm that its registration and PTI continue to cover the expanded setup.

What if we replace our invoicing software?

A change in invoicing solution should trigger a compliance review.

RMC No. 110-2026 expressly contemplates the updating of PTIs, and significant system changes may also have registration consequences.    

Can our e-invoicing provider decide whether we need another PTI?

The provider may assist with the technical and PTI process, but the taxpayer remains responsible for its own BIR compliance.

Businesses should obtain confirmation based on the applicable BIR procedure rather than relying solely on a software provider's commercial representation.

The Key Question Is Not How Many Systems You Own But What Your PTI Actually Covers

For businesses with complex accounting environments, the safest approach is not to begin with a fixed assumption about the number of PTIs required.

Begin with the system architecture.

Identify every platform that issues invoices. Determine how each system is registered.

Review which configuration is covered by the existing PTI. Then determine whether a new system requires an update, additional application, or other BIR action before it begins issuing electronic invoices.

This approach is particularly important for businesses with multiple branches, separate POS systems, several ERPs, online sales platforms, or third-party e-invoicing providers.

Need Help Reviewing Multiple Invoicing Systems?

Aureada CPA Law Firm can assist businesses in reviewing their existing CAS, ERP, POS, and electronic invoicing arrangements to determine how their current BIR registrations and PTI requirements interact.