What Is SLSP and Why VAT Businesses Need It

The Summary List of Sales and Purchases (SLSP) is the per-transaction-partner detail that sits behind your VAT return. Where the 2550Q reports your VAT in totals, the SLSP breaks those totals down by customer and by supplier — name, TIN, and amounts — so the BIR can cross-match what you reported against what your trading partners reported. It is submitted as a DAT file, and for a VAT business it's not optional paperwork: it's the evidence that your VAT figures are real and consistent.

The short answer

The SLSP is two lists: a Summary List of Sales (your VATable sales, broken down by customer) and a Summary List of Purchases (your VATable purchases, broken down by supplier), each carrying the partner's name, TIN, and the net and VAT amounts. VAT-registered businesses prepare it to accompany their VAT return, the totals must tie to the 2550Q and the books, and it's submitted to the BIR as a DAT file. Its whole reason for existing is cross-matching — your output is someone else's input.

Who this guide is for

• VAT-registered businesses and freelancers who must prepare the SLSP alongside their VAT return.
• Bookkeepers assembling the per-partner detail and reconciling it to the 2550Q.
• Owners who've heard the SLSP is now a DAT file and want to understand what that changes.
• Anyone whose SLSP totals don't match their VAT return and needs to find the gap before filing.

What the SLSP actually is

Think of the SLSP as the subsidiary ledger of your VAT for the period. The VAT return tells the BIR how much output and input VAT you have; the SLSP tells it with whom you transacted to get there. It comes in two parts:

Because every VATable transaction has two sides, the SLSP lets the BIR run a cross-match: the output VAT you declare on a sale to a customer should appear as input VAT on their purchase list, and vice-versa. That mutual reporting is precisely what makes the SLSP powerful — and why an inaccurate one draws attention.

Who files it

The SLSP is fundamentally a VAT-business requirement — it's the supporting detail for the VAT return, so it follows VAT registration. The specific rules on who must file, and any thresholds that scope it, are set by the BIR and have changed over time, so confirm your own obligation. If you're Non-VAT, you generally have lighter support-file requirements and typically won't file an SLSP — but always verify what your particular registration requires rather than assuming.

What it must contain

An SLSP isn't a lump total — it's a line per trading partner (or per the BIR's required grouping), and each line generally needs:

• The customer's or supplier's registered name, matching how they're registered with the BIR.
• Their TIN — the key the BIR uses to cross-match, so accuracy here is critical.
• The net (VAT-exclusive) amount of the transactions with that partner.
• The VAT amount — output VAT for sales, input VAT for purchases.
• Any classification the form requires, such as the nature of the purchase or the VAT treatment.

How it reconciles to the 2550Q and your books

This is the discipline that keeps you out of trouble: the SLSP and the 2550Q must agree. The sum of the sales on your Summary List of Sales should equal the taxable sales the 2550Q reports, and the output VAT should match; the same goes for purchases and input VAT on the buy side. And both should foot back to the books — the SLSP is just your VAT ledger detail re-cut by partner.

If the three don't tie out — books, 2550Q, and SLSP — you have a reconciliation problem to solve before submission, not after. The most common cause is the same one that breaks VAT returns generally: inconsistent gross-vs-net recording, so the per-partner amounts don't sum to the declared totals. See how to prepare for the 2550Q for the reconciliation order.

Why it's a DAT file

The SLSP is submitted to the BIR as a DAT file — a specifically formatted data file the BIR's validation tools read, rather than a free-form spreadsheet or PDF. That means the SLSP has to be correct on two levels: the numbers must reconcile, and the file format must conform to the BIR's required layout. A perfectly accurate SLSP in the wrong format won't validate, and a well-formatted file with wrong totals won't reconcile.

Producing the DAT file by hand from a spreadsheet is where many businesses lose time and trip over format errors. For the broader DAT picture see the BIR DAT file guide, and for the specific format pitfalls see common SLSP DAT file errors.

1. 1

   Keep clean partner master data

   Capture each customer's and supplier's correct registered name and TIN once, so every SLSP line draws on accurate details.

2. 2

   Record VATable sales and purchases per line

   Split each line into net + VAT against the right partner, so the per-partner detail exists in the books from the start.

3. 3

   Build the two summary lists

   Group your VATable sales by customer and purchases by supplier, each with name, TIN, net, and VAT.

4. 4

   Reconcile to the 2550Q and the books

   Confirm the SLSP sales and purchases totals equal the figures on your VAT return and foot back to the ledger.

5. 5

   Generate and validate the DAT file

   Produce the SLSP in the BIR's required DAT format, run it through the validation tool, and fix any format errors before submitting.

How this connects to your books

The SLSP is not a separate document you build from scratch each period — it's your VAT detail re-cut by trading partner. If every VATable line is recorded net + VAT against the right customer or supplier, with clean names and TINs in your master data, then the SLSP, the VAT return, and the books all reconcile by construction, and producing the DAT file is a generation step rather than a rebuild.

Common mistakes

• Wrong or missing TINs. The TIN is the cross-match key — a wrong one breaks the match and flags the entry.
• Names that don't match registration. A partner's name must match how they're registered, or the BIR can't reconcile it.
• SLSP totals that don't tie to the 2550Q. The two must agree; a mismatch is visible and avoidable.
• Treating it as a spreadsheet job. The SLSP must be a valid DAT file — right numbers and right format.
• Assuming Non-VAT businesses must file it. The SLSP follows VAT registration; confirm your own obligation rather than guessing either way.