Does each branch of a business file its own RELIEF SLSP DAT file?

No. RELIEF SLSP is filed at the TIN level, not per branch — a business with multiple branches consolidates all of them into one DAT file under the head office's single Taxpayer Identification Number, with each branch's 3-digit branch code preserved in the relevant field rather than used to split the filing into separate submissions.

What's the most common mistake when merging multiple branches' Excel data?

Column misalignment — one branch's spreadsheet has an extra or reordered column, or uses a slightly different header name for the same field, so a straight copy-paste merge shifts data into the wrong columns for some rows without triggering an obvious error until the DAT file fails validation or produces silently wrong figures.

How should branch codes be entered when merging workbooks?

Keep the branch code as its own consistent column across every branch's data before merging, formatted as text (not a number, to preserve leading zeros), and verify each branch's code matches its registered BIR branch code rather than an internal store number the business uses informally.

What happens if the same transaction gets counted in two branches' Excel files?

A duplicated transaction — common when a head office also reports supplier purchases a branch already recorded locally — inflates the consolidated RELIEF SLSP total above actual sales or purchases, creating a mismatch against the VAT return and the business's own financial statements that the BIR's reconciliation can flag.

Can BIR Online Tools combine several branches' uploads into one DAT file automatically?

Yes — the RELIEF module accepts the combined, cleaned-up workbook (or sequential uploads that append to the same filing) and converts the full multi-branch data set into one DAT file keyed to the single company TIN, rather than requiring a separate conversion run per branch.

Excel to BIR DAT File: Merging Multiple Branches' RELIEF SLSP Workbooks Into One Filing

A business with several branches files one RELIEF SLSP DAT file under its single head-office TIN — never a separate DAT file per branch — which means the real work happens before conversion, merging each branch’s Excel sales and purchase data into one clean, consistently structured workbook. Get the merge wrong and the DAT file converts without error while still carrying duplicated rows, misaligned columns, or inconsistent branch codes.

Merge and Convert Your Branches in One Pass FREE →

Why does this even need merging instead of filing per branch? #

The underlying legal structure treats a business as one taxpayer under one TIN, regardless of how many physical branches it operates, so its tax returns — and the RELIEF SLSP attached to them — follow that same single-TIN structure. Practitioner commentary on multi-branch filing describes the 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.”

The same consolidation logic applies to a multi-branch corporation. Each branch still carries its own distinct 3-digit branch code for internal tracking and BIR registration purposes, but that code is a field inside one consolidated filing, not a basis for splitting the RELIEF SLSP into several independent DAT files.

What goes wrong when branches’ Excel files get merged carelessly? #

The three most common failure points are column misalignment, inconsistent branch codes, and duplicated transactions — and all three can pass DAT conversion cleanly while still producing a materially wrong filing.

Problem	What it looks like	Why it’s dangerous
Column misalignment	Branch B’s sheet has an extra column, shifting TIN/amount data one column over for some rows	Converts without error; produces wrong TINs or amounts tied to real transactions
Inconsistent branch codes	One branch uses its internal store number instead of its registered BIR branch code	DAT file’s branch field doesn’t match BIR records, complicating reconciliation
Duplicated transactions	Head office re-lists a purchase a branch already recorded locally	Inflates the consolidated SLSP total above actual sales/purchases

A merge checklist that catches these before conversion #

Standardize column headers and order across every branch’s workbook first — don’t rely on a merge tool to guess that “Buyer TIN” and “TIN of Buyer” are the same field.
Format the branch-code column as text, not a number, in every branch’s file to preserve leading zeros, and verify each code against the branch’s actual BIR registration.
Sort and scan the combined workbook for duplicate invoice numbers or buyer/amount pairs before conversion, especially where a head office and a branch might both record the same cross-branch transaction.
Total each branch’s contribution separately after merging, and reconcile that subtotal against the branch’s own sales/purchase books before trusting the consolidated figure.
Convert the final merged workbook once, rather than converting each branch separately and trying to combine DAT files afterward — DAT format doesn’t concatenate cleanly by hand.

Worked example: a three-branch retail chain’s Q3 RELIEF SLSP #

RetailCo operates three branches, each keeping its own local sales log in a slightly different Excel layout.

Branch	Rows before cleanup	Issue found	Rows after cleanup
Branch 001 (head office)	420	None — reference layout	420
Branch 002	310	“Buyer TIN” column one position to the right of Branch 001’s layout	310 (realigned)
Branch 003	265	14 transactions also appeared in Branch 001’s head-office purchase log (inter-branch transfers double-counted)	251 (14 duplicates removed)

RetailCo’s bookkeeper standardizes all three layouts to match Branch 001’s column order, removes the 14 duplicated inter-branch rows, and converts the resulting 981-row workbook into a single RELIEF SLSP DAT file under RetailCo’s one TIN.

How does this fit with the rest of the site’s coverage? #

This merge step happens upstream of the filing obligations covered in Multi-Branch RELIEF/SAWT/QAP Filing, and uses the same record-layout discipline covered in Excel to DAT File: Record Layout Mistakes. See Excel to BIR DAT File: RELIEF SLSP for the conversion mechanics themselves.

Summary #

A multi-branch business converts one merged Excel workbook into one RELIEF SLSP DAT file under its single TIN — the branch code is a field inside that filing, not a reason to file separately. Standardizing column layout, verifying branch codes, and screening for duplicated cross-branch transactions before conversion avoids a DAT file that converts cleanly while still being wrong. See Multi-Branch RELIEF/SAWT/QAP Filing for the filing-obligation side of this same structure.