RELIEF SLSP for a Business With Branches Under One Head Office TIN: One Consolidated Filing or Separate Filings Per Branch?

A head office and its branches file one RELIEF Summary List of Sales and Purchases (SLSP), not one per branch — because RELIEF SLSP is a VAT obligation tied to the taxpayer’s Tax Identification Number (TIN), and every branch operates under the same TIN as its head office. A retail chain with five branches consolidates all five branches’ VAT-relevant sales and purchases into a single quarterly SLSP DAT file filed under the head office’s VAT registration, not five separate filings.

Why branches don’t get their own RELIEF SLSP #

RELIEF SLSP attaches to BIR Form 2550Q, the Quarterly VAT Return, and VAT registration is granted to a TIN, not to an individual branch — so the filing unit for RELIEF SLSP is the TIN, with branch-level detail collapsed into one list. A branch is an extension of the same taxable person for VAT purposes; it does not hold a separate VAT certificate of registration independent of the head office.

This is confirmed by how branch registration itself works. Under Revenue Regulations (RR) No. 11-2008, a taxpayer must register its head office before it can register any branch, and a branch is registered with the Revenue District Office (RDO) that has jurisdiction over the head office — not over the branch’s own physical location in every case. As the regulation’s text puts it:

“It should be noted however that before a person can register a branch or facility, it should have registered first its Head Office.”

— Revenue Regulations No. 11-2008

That subordination carries straight through to VAT reporting: because every branch’s TIN is the head office’s TIN with a different branch code appended, there is only ever one VAT-registered taxpayer for RELIEF SLSP purposes, however many physical locations it operates.

What a multi-branch taxpayer actually files #

A multi-branch VAT-registered taxpayer files exactly one Summary List of Sales and one Summary List of Purchases per quarter, each one aggregating every branch’s qualifying transactions under the head office’s TIN. The branch code on each line item identifies which location the sale or purchase came from, but it does not create a separate filing obligation.

1. Collect sales and purchase records from every branch for the quarter, including point-of-sale exports, invoices, and official receipts
2. Tag each transaction with its branch code so the source location stays traceable within the consolidated file, even though all branches land in one SLSP
3. Merge all branches into one dataset before converting to the DAT file format — do not generate separate DAT files per branch and submit them individually
4. Validate the merged file against the BIR’s record layout before eSubmission, since a file assembled from multiple branch exports is more prone to column-mapping and duplicate-header errors than a single-location file
5. Submit the one consolidated SLSP to the RDO with jurisdiction over the head office, by the same deadline as the related BIR Form 2550Q

Under Revenue Regulations No. 1-2012, which made quarterly Summary List submission mandatory for VAT-registered taxpayers, the filing obligation runs to “all persons liable for VAT,” a category defined at the registrant level — the regulation does not create a parallel branch-level filing requirement anywhere in its text.

Worked example: three branches, one SLSP #

A fictional VAT-registered hardware retailer, Ferro Builders Supply Corp., operates a head office in Quezon City (RDO jurisdiction: RDO 40) and two branches — one in Cebu City and one in Davao City — all under the same TIN with branch codes 0000 (head office), 0001 (Cebu), and 0002 (Davao).

Rather than filing three separate Summary Lists of Sales, Ferro Builders Supply Corp. merges all three branches’ sales ledgers into a single spreadsheet, tags each row with its branch code, converts the merged sheet into one SLSP DAT file, and submits that one file to RDO 40 — the RDO with jurisdiction over the Quezon City head office — together with the consolidated BIR Form 2550Q covering all three locations’ output VAT. The Cebu and Davao branches never file anything separately with their own local RDOs for this purpose.

Summary #

RELIEF SLSP follows the taxpayer’s TIN, and a branch never has a TIN of its own — it inherits the head office’s TIN with a distinct branch code, a subordination RR No. 11-2008 makes explicit in how branches are registered in the first place. A multi-branch VAT registrant therefore consolidates every branch’s qualifying sales and purchases into one Summary List of Sales and one Summary List of Purchases per quarter, filed with the RDO that has jurisdiction over the head office, as in the fictional three-branch example above. Build the merge from branch-tagged source data rather than reconciling separate branch DAT files after the fact, and see RELIEF SLSP vs QAP and What Is RELIEF SLSP? for the filing’s broader mechanics and legal basis.