BIR eAFS for a Business With Multiple Branches: One Consolidated Submission or One Per Branch?

A business with a head office and several BIR-registered branches under one Taxpayer Identification Number (TIN) submits one consolidated set of Audited Financial Statements (AFS) through BIR eAFS — covering the whole legal entity’s combined figures — not a separate AFS package for each branch. A branch is not a distinct taxpayer; it is an extension of the head office registered with its own branch code, and the eAFS system has no filing slot for branch-level submissions in the first place.

This is a companion to What Is the BIR eAFS System, and How Do You Submit Financial Statements Electronically?, which covers what eAFS does and the standing submission window, and Common BIR eAFS Upload Errors and How to Fix Them Before the Deadline, which covers why uploads get rejected. Neither post addresses the multi-branch question directly — this one does. It’s a different question from the one covered in How Do You File RELIEF, SAWT, or QAP When Your Business Has Multiple Branches? and RELIEF SLSP for a Business With Branches Under One Head Office TIN: those cover the DAT-file attachments to withholding and VAT returns, while this post covers the Audited Financial Statements attachment to the Annual Income Tax Return (AITR) itself.

Why is a branch not a separate filer for eAFS purposes? #

A branch exists for BIR purposes as a registered place of business under the head office’s TIN, not as a taxpayer in its own right — so it has no independent filing identity to submit an AFS under. The legal basis for this sits in the National Internal Revenue Code’s (NIRC) registration rules, which govern every BIR filing obligation that follows, including eAFS.

NIRC Section 236(A) requires “a person maintaining a head office, branch or facility” to register each location with the Revenue District Officer having jurisdiction over it — so a branch does get its own registration record and branch code. But Section 236(J) sets the limit that keeps all of those locations tied to a single taxpayer identity:

“Only one Taxpayer identification Number (TIN) shall be assigned to a taxpayer.”

That single sentence is why eAFS submission happens once per company, not once per branch. The TIN is the identifier the BIR’s systems — eAFS, eFPS, eBIRForms — use to recognize a filer, and Section 236(J) guarantees there is exactly one TIN per legal entity, however many branches it registers underneath that TIN. A branch’s registration adds a branch code suffix to the head office’s base TIN; it does not create a second TIN that could file a second, independent AFS.

This is the same principle this site’s RELIEF SLSP coverage traces through Revenue Regulations (RR) No. 11-2008, which requires a head office to be registered before any branch can be: “before a person can register a branch or facility, it should have registered first its Head Office.” A branch is always subordinate to, and dependent on, the head office’s registration — never a parallel, independent filer.

What does the eAFS system itself tell you about this? #

The eAFS filename convention the BIR prescribed in Revenue Memorandum Circular (RMC) No. 43-2021 only has room for the entity-level TIN — not a branch code — which confirms the system was built around one filer per TIN, not one filer per branch. Under that naming convention, as summarized by tax advisory firm Grant Thornton, the filename’s TIN placeholder is described as “the 9-digit Tax Identification Number (TIN)” — the base TIN alone, with no additional digits for a branch suffix.

Practically, that means there is no field in the eAFS filename, and no separate login tied to a branch, for a branch to submit its own AFS even if someone wanted to try. The AFS, the filed Income Tax Return copy, the Statement of Management Responsibility, and any other required attachment are all named and uploaded under the head office’s 9-digit TIN, once, for the taxable year — covering every branch’s activity folded into that single set of figures.

The AFS document itself reflects this structure before it ever reaches eAFS: an audited financial statement is prepared for the reporting entity as a whole — the corporation or sole proprietorship holding the TIN — with each branch’s revenue, expenses, assets, and liabilities already combined into one balance sheet and income statement by the company’s accountant or external auditor. There is no separate “branch AFS” document type for eAFS to receive, because standard financial reporting doesn’t produce one.

Which RDO gets the submission when branches sit in different RDOs? #

The Revenue District Office with jurisdiction over the head office receives the entire eAFS submission, regardless of how many RDOs the company’s branches are physically registered in. This follows directly from how the Annual Income Tax Return itself is filed: the AITR is a single, TIN-level return, and eAFS submission is tied to that return, not to each branch’s separate location.

• A head office registered in RDO 039 (Quezon City) filing its AITR and AFS attachments does so through that RDO’s jurisdiction, even if it operates branches registered in RDO 25A (Zamboanga City) or any other RDO.
• A branch’s own RDO does not separately receive or process an AFS filing for that branch — a branch’s RDO relationship is about that location’s Certificate of Registration, invoicing, and books of accounts, not about the company’s consolidated income tax reporting.
• If the head office itself transfers RDO jurisdiction (for example, after relocating its principal office), the eAFS and AITR filings follow the head office’s new RDO going forward — branches don’t trigger a filing-jurisdiction change on their own.

This mirrors the rule this site’s RELIEF SLSP guide already documents for VAT: “the Revenue District Office with jurisdiction over the head office receives the consolidated RELIEF SLSP… regardless of how many branches operate in other RDO jurisdictions.” eAFS follows the identical logic because both are attachments tied to a TIN-level return, not a branch-level one.

Worked example: a retail chain with a head office and four branches #

Cebu Fresh Mart Corporation registers its head office in Cebu City (RDO 081) and operates four branches: one each in Mandaue City, Lapu-Lapu City, Talisay City, and a fourth in Davao City — a province outside its head office’s RDO entirely. Each branch has its own BIR Certificate of Registration and branch code (00001 through 00004), its own point-of-sale system, and its own set of books for day-to-day bookkeeping.

What actually happens at Annual Income Tax Return time:

What a business owner might wrongly assume — and shouldn’t do: there is no step where the Davao City branch separately scans and uploads “its own” AFS, and no step where RDO handling the Davao branch’s Certificate of Registration expects a filing from that branch for income tax purposes. The four branches’ figures already live inside the one consolidated AFS the head office submits; attempting a second, branch-level eAFS submission would not match any taxpayer record the BIR’s system recognizes under that branch’s code, and would create a duplicate-filing problem rather than extra compliance.

Frequently asked questions #

Does each branch of a company submit its own Audited Financial Statements through BIR eAFS? #

No. A branch is not a separate taxpayer — it is registered under the head office’s Taxpayer Identification Number (TIN) with its own branch code. Because eAFS submissions are made once per TIN, the head office submits one consolidated set of Audited Financial Statements covering the entire legal entity, including every branch’s figures, rather than a separate AFS package for each branch.

Which RDO receives the eAFS submission for a company with branches in different RDOs? #

The Revenue District Office with jurisdiction over the head office receives the eAFS submission, because the Annual Income Tax Return and its attachments are filed under the head office’s registration regardless of how many branches operate in other RDO jurisdictions. A branch’s own RDO does not receive a separate AFS filing for that branch.

Do the Audited Financial Statements need to show branch-by-branch figures? #

The Audited Financial Statements themselves present the company’s financial position and results as a single reporting entity, consistent with how the company’s books are consolidated for financial reporting purposes. They are not broken out by branch inside the eAFS submission; branch-level detail exists in the company’s underlying accounting records, not as a filing requirement of eAFS itself.

Does the BIR eAFS filename include the branch code? #

No. Under Revenue Memorandum Circular No. 43-2021’s naming convention, the eAFS filename embeds the taxpayer’s 9-digit Tax Identification Number only, without a branch code suffix — because the system identifies the filer by TIN at the entity level, not by individual branch.

If a branch is in a different region from the head office, does that branch still need its own BIR registration? #

Yes. Branch registration and eAFS submission are two separate compliance obligations. Each branch still needs its own BIR Certificate of Registration and invoicing setup under NIRC Section 236, even though the Audited Financial Statements and ITR attachments covering that branch’s activity are filed once, at the head office level, through eAFS.

Summary #

A business with a head office and multiple registered branches under one TIN files a single, consolidated set of Audited Financial Statements through BIR eAFS — not a separate AFS package per branch — because NIRC Section 236(J) assigns only one TIN to a taxpayer, and eAFS, like the Annual Income Tax Return it attaches to, is a TIN-level filing. The eAFS filename convention under RMC No. 43-2021 reinforces this: it has room for the entity’s 9-digit TIN alone, with no branch-code digit, because the system was never built to accept a branch-level AFS submission. The company’s consolidated AFS already folds every branch’s figures into one set of financial statements, uploaded once, under the head office’s RDO. Branch registration itself remains a separate, genuine requirement — each location still needs its own Certificate of Registration under NIRC Section 236 — but that obligation runs in parallel with, not instead of, the single eAFS filing. For the DAT-file attachments that follow the same TIN-level logic for withholding and VAT returns, see How Do You File RELIEF, SAWT, or QAP When Your Business Has Multiple Branches? and RELIEF SLSP for a Business With Branches Under One Head Office TIN.