How Do You File RELIEF, SAWT, or QAP When Your Business Has Multiple Branches?

A business with several BIR-registered branches under one head office Taxpayer Identification Number (TIN) files one consolidated RELIEF, SAWT, or QAP DAT file per return period — not a separate DAT file for each branch. Branch-level detail lives inside the file, in the TIN/branch code field on each row, not in the number of files submitted.

This guide covers how branch codes work inside a single consolidated filing, which RDO the filing goes to, and a worked two-branch example. It’s part of this site’s DAT file coverage — see What Is a BIR DAT File? for the format itself, and How to Register a New BIR Branch for what a new branch needs separately from this filing question.

Why is filing consolidated at the TIN level, not per branch? #

A withholding tax return or VAT return is a single filing tied to the taxpayer’s TIN, and RELIEF, SAWT, and QAP are attachments to that return — so they follow the return’s TIN-level structure, not a branch-by-branch one. Practitioner commentary on multi-branch filing for a single proprietorship or professional practice describes the underlying principle this way:

“For individuals operating multiple branches of a sole proprietorship or professional practice, the law treats the entire enterprise as a single taxable entity under one Taxpayer Identification Number (TIN). The existence of multiple branches does not create separate filing obligations; instead, the taxpayer files a single consolidated return.”

This site relied on secondary tax-practice commentary for that passage, as it addresses the general multi-branch filing principle rather than quoting a single specific BIR regulation section — the underlying legal basis is the TIN-centered registration and return structure under NIRC Section 236 and its implementing regulations, and businesses should confirm any branch- or industry-specific filing nuance with their RDO before assuming this template applies without exception.

How does the branch code work inside the file? #

Each TIN in the DAT file’s structure is split into a nine-digit base number plus a branch code suffix, so a single consolidated file can still show exactly which registered location a transaction belongs to. A head office is conventionally branch code 0000 (sometimes shown as 00000 depending on the template), with subsequent branches numbered sequentially (0001, 0002, and so on).

This is why consolidation doesn’t mean losing branch-level detail — it means one submission carries all the detail, correctly tagged, instead of the BIR receiving several partial, branch-specific files for the same TIN and period that then have to be reconciled against each other.

Which RDO receives the consolidated filing? #

Filing goes to the RDO or Large Taxpayers office with jurisdiction over the withholding agent’s or VAT taxpayer’s own registration — typically the head office or principal place of business — not separately to each branch’s local RDO. This matters operationally: a business with, say, a head office in Quezon City and branches in Cebu and Davao does not file three separate sets of QAP or RELIEF attachments with three different RDOs. It compiles one file covering all three locations’ relevant transactions and files it once, through the jurisdiction tied to the TIN’s registration.

Branch registration itself is a separate matter — each branch still needs its own BIR Form 2303 and invoicing setup under NIRC Section 236(A), as covered in How to Register a New BIR Branch. Having a properly registered branch and consolidating that branch’s transactions into the head office’s DAT filing are two different compliance steps that both need to happen, not substitutes for each other.

Worked example: a two-branch retail business #

A retail business with a Quezon City head office and a Cebu branch consolidates both locations’ withholding transactions into one QAP DAT file for the quarter, filed with the RDO covering the Quezon City head office.

Both branches’ payee rows go into the same QAP DAT file for the quarter, each carrying its own branch code, and that single file is submitted once through the head office’s registered RDO alongside the consolidated BIR Form 1601-EQ. The Cebu branch does not separately submit its ₱180,000 in payee data to a Cebu RDO.

Frequently Asked Questions #

Do I file a separate RELIEF, SAWT, or QAP DAT file for each branch? #

No. A business with multiple branches under one head office TIN generally files one consolidated RELIEF, SAWT, or QAP DAT file per return period, covering all branches’ relevant transactions, submitted through the RDO or Large Taxpayers office with jurisdiction over the withholding agent’s or VAT taxpayer’s registration — not one file per branch.

How does the DAT file distinguish which branch a transaction belongs to? #

The DAT file’s TIN field carries the branch code as its final digits appended to the nine-digit base TIN — for example, a head office is typically branch code 00000 and subsequent branches carry sequential codes. Each transaction row in the file reflects the TIN and branch code of the party (or the reporting entity’s own branch, depending on the schedule) so downstream BIR systems can still trace activity to a specific registered location within one consolidated submission.

Which RDO do I file with if my branches are in different regions? #

Filing is generally made with the RDO or Large Taxpayers office that has jurisdiction over the withholding agent’s or VAT taxpayer’s own registered address — typically the head office or principal place of business — rather than separately with each branch’s local RDO, since the return itself (BIR Form 1601-EQ, 2550Q, etc.) is a single TIN-level filing.

Does each branch need its own BIR Certificate of Registration? #

Yes — branch registration and DAT file consolidation are two different things. Under NIRC Section 236(A), each branch or place of business generally needs its own BIR Form 2303 (Certificate of Registration) and Authority to Print/invoicing setup, even though the withholding tax and VAT returns — and the RELIEF, SAWT, and QAP attachments tied to them — are filed once at the TIN level covering all branches together.

What if two branches accidentally submit separate DAT files for the same period? #

Duplicate or conflicting DAT files for the same TIN and period create a reconciliation problem the BIR eSubmission system does not resolve automatically. The practical fix is to consolidate all branch data into a single file before submission, and if a duplicate was already submitted, correct and resubmit under this site’s guide to How to Correct and Resubmit a RELIEF, SAWT, or QAP DAT File After eSubmission.

Summary #

Multiple branches under one TIN mean one consolidated RELIEF, SAWT, or QAP DAT file per period — not one per branch — filed through the RDO with jurisdiction over the taxpayer’s own registration, with each row’s branch code preserving location-level detail inside that single file. Branch registration itself still happens separately for each location. Start with What Is a BIR DAT File? and How to Register a New BIR Branch.