Why BIR RELIEF SLSP Mismatches With Your Financial Statements Trigger a Letter Notice
When your Audited Financial Statements report a different purchases or sales figure than your RELIEF SLSP for the same period, the BIR’s third-party data matching under RMO No. 13-2012 can flag the gap and generate a Letter Notice (LN) — a computer-issued notice, not yet an assessment. This is a different failure mode than an internal mismatch between RELIEF SLSP and your own BIR Form 2550Q: it means an external cross-check — your own AFS, a counterparty’s SLSP, or Bureau of Customs data — disagrees with what you filed, which is precisely the discrepancy the BIR’s matching programs exist to catch.
Catch SLSP Discrepancies Before the BIR Does FREE →What makes an AFS-vs-SLSP mismatch different from a return-reconciliation mismatch #
A RELIEF SLSP that disagrees with your own BIR Form 2550Q is an internal filing error you can catch and fix before you submit anything — a RELIEF SLSP that disagrees with your Audited Financial Statements or a counterparty’s own filing is a discrepancy the BIR itself can catch, after the fact, through data it already has. The two problems look similar on a spreadsheet but sit in different risk categories.
Reconciling RELIEF SLSP against BIR Form 2550Q is entirely within a taxpayer’s control: both documents come from the same books, prepared by the same team, before either is filed. See RELIEF SLSP vs BIR Form 2550Q: How to Reconcile Your Sales and Purchases Listing for that internal check. An AFS-vs-SLSP mismatch is different because the Audited Financial Statements are prepared under accrual accounting for a full fiscal year and audited independently, while the RELIEF SLSP is a VAT-period, invoice-level listing — and because the BIR’s data matching also pulls in what other taxpayers reported about you. A gap here isn’t something you necessarily caught before filing; it’s something the BIR’s own systems surface afterward.
What triggers a Letter Notice when your AFS and RELIEF SLSP don’t tie #
A Letter Notice is generated when the BIR’s computerized third-party information matching finds that a taxpayer’s declared figures don’t tie to data reported by an outside source — and Audited Financial Statements are one of the reference points that data comparison can draw on, alongside counterparty SLSP filings and Bureau of Customs import records. RMO No. 13-2012 prescribes the revised guidelines for handling LNs generated through this matching, and covers the income, value-added, and percentage tax liabilities of taxpayers flagged under the BIR’s RELIEF, Bureau of Customs (BOC), and Tax Reconciliation System (TRS) third-party information programs.
For an LN that has been assigned to a revenue officer, RMO No. 13-2012 sets a firm internal clock. As the Order states:
“The RO assigned shall resolve the LN discrepancy within thirty (30) days from receipt of original assignment/referral.”
That 30-day window is the practical reason not to sit on a Letter Notice once it arrives — it is, in effect, also the taxpayer’s window to submit an explanation before the case can be escalated. For a full walkthrough of what an LN is, how it legally differs from a Letter of Authority, and what the Supreme Court has said about its limits, see What Is a BIR Letter Notice (LN) and How Is It Different From a Letter of Authority (LOA)? — that guide covers LN mechanics in general; this one focuses specifically on the AFS-and-third-party-data trigger.
Common causes of an AFS-vs-RELIEF SLSP mismatch #
Most AFS-to-SLSP gaps trace back to one of five patterns, and none of them automatically means either document contains an error — they mean the two documents were built on different logic and need to be reconciled line by line.
| Cause | What it looks like |
|---|---|
| Timing / accrual differences | The AFS books a purchase or sale in the period it was incurred under accrual accounting, while the counterparty’s RELIEF SLSP reports the same transaction in the invoice or reporting period — landing the two documents in different months or quarters |
| Counterparty reported it, you didn’t (or vice versa) | A supplier’s Summary List of Sales includes a transaction you never recorded as a purchase in that period, or your Summary List of Sales includes a sale a customer never reported as a purchase — a one-sided entry that the BIR’s cross-match will flag from either direction |
| Wrong or mismatched TIN | A transaction is reported under an incorrect buyer or supplier TIN, so the BIR’s system cannot match the two sides of the transaction to the same taxpayer pair even though both sides actually reported it |
| Branch-level reporting inconsistencies | A head office books a transaction that a branch also reports separately (or a branch transaction never rolls up to the head office listing), producing a total that doesn’t reconcile across the consolidated AFS |
| Rounding and currency differences | Small centavo-level rounding, or a foreign-currency transaction converted at different exchange rates in the AFS versus the SLSP, produces a discrepancy that is real on paper but immaterial in substance |
Worked example: tracing a ₱300,000 AFS-to-SLSP purchases gap #
A trading company’s Audited Financial Statements report ₱5,000,000 in purchases for the fiscal year, but its RELIEF SLSP Summary List of Purchases for the same period totals only ₱4,700,000 — a ₱300,000 gap that, left unexplained, is exactly the kind of discrepancy the BIR’s third-party matching is built to catch.
| Step | Finding |
|---|---|
| AFS purchases (fiscal year) | ₱5,000,000 |
| RELIEF SLSP purchases total (same period) | ₱4,700,000 |
| Gap | ₱300,000 |
| Trace | Two supplier invoices, dated December 28 and December 30, together totaling ₱300,000 |
| Root cause found | The company booked both invoices as December purchases in its AFS on the accrual basis — goods were received and the liability recognized before year-end. Both suppliers, however, reported the same invoices in their own January RELIEF Summary List of Sales, based on when they recognized the sale on their side |
| How it shows up in a BIR discrepancy report | The BIR’s matching compares the company’s declared full-year purchases (reflected in the AFS attached to the annual return) against the sum of RELIEF SLSP purchase data reported for the company across the relevant periods. Because the two December invoices land in the SLSP data for the following period rather than the AFS period, the comparison shows the company’s declared purchases exceeding the third-party-reported SLSP figure by ₱300,000 |
| Resolution if a Letter Notice arrives | The company pulls the two invoices, delivery receipts, and the accrual journal entries showing goods received in December, and submits a written explanation to the BIR office handling the LN: the ₱300,000 is a timing difference, not an unreported or overstated purchase — the transactions exist in both data sets, just in adjacent periods |
If the explanation and supporting documents hold up, the Letter Notice is typically closed without further action, because the underlying transactions are accounted for on both sides — they simply landed in different reporting periods. Had the ₱300,000 instead reflected a purchase the company recorded but a supplier never reported at all, the fix would run differently: verifying the transaction actually occurred, confirming the correct supplier TIN was used, and — if the supplier genuinely failed to report it — documenting that the gap is on the counterparty’s side, not the company’s own books.
How to respond if a Letter Notice cites an AFS-SLSP mismatch #
- Read the LN to identify the exact figure and data sources cited — whether it’s citing AFS purchases against SLSP purchases, a specific counterparty’s SLSP entry, or Bureau of Customs import data.
- Pull the underlying transaction records for the period involved: invoices, delivery receipts, accrual journal entries, and the AFS working papers that produced the reported figure.
- Identify the pattern: a timing difference between accrual booking and invoice-period reporting, a counterparty that reported (or failed to report) a transaction, a TIN error, a branch-consolidation gap, or a rounding difference.
- Trace the gap to specific transactions, not just the aggregate figure — a Letter Notice citing a peso amount is easier to resolve once broken down into the line items behind it. If your RELIEF SLSP itself was built with data-entry issues rather than genuine timing gaps, check Common RELIEF SLSP Upload Errors and How to Fix Them Before eSubmission for the usual culprits before assuming the mismatch is purely explanatory.
- Submit a written explanation with supporting documents to the BIR office handling the LN, within the resolution window the assigned revenue officer is working under.
- Keep a record of what was submitted and when, since an unresolved LN can still lead to a proper Letter of Authority covering the same period.
Do not treat the LN’s cited figure as an automatic tax bill — it isn’t one. But do not set it aside either; a mismatch left unexplained is exactly the kind of finding that can carry forward into a full audit.
Is your business even required to file RELIEF SLSP? #
Before any of this matters, confirm the filing obligation applies to your business in the first place — RELIEF SLSP is required from every VAT-registered taxpayer regardless of sales or purchase size, with no exemption for smaller volumes. See Who Must File RELIEF SLSP? VAT-Registered Taxpayer Rules Explained for the current eligibility rules, since a business that mistakenly believes it’s below an old peso threshold may be skipping a filing that third-party matching still expects to see.
Frequently asked questions #
Can a mismatch between my RELIEF SLSP and my Audited Financial Statements really trigger a BIR Letter Notice? #
Yes. The BIR’s third-party information matching under RMO No. 13-2012 cross-checks a taxpayer’s declared figures — including data drawn from the Audited Financial Statements filed with the return — against RELIEF SLSP data, Bureau of Customs import records, and Tax Reconciliation System data. A gap between the AFS purchases figure and the RELIEF Summary List of Purchases total for the same period is a data point that matching can flag, generating a computer-issued Letter Notice.
Is a Letter Notice for an AFS-vs-SLSP mismatch the same as a tax assessment? #
No. A Letter Notice only flags that two data sources don’t tie out; it is not found in the National Internal Revenue Code and does not by itself authorize an examination or demand payment. Only a Letter of Authority, naming a specific revenue officer and taxable period, gives the BIR the power to examine books and eventually issue an assessment.
What’s the most common reason AFS purchases don’t match RELIEF SLSP purchases? #
Timing differences are the most common cause. Audited Financial Statements are prepared on the accrual basis, so a December invoice gets booked as a December expense even if the supplier’s own RELIEF Summary List of Sales reports the same transaction in a later month based on invoice or reporting date — creating a gap that is real in both documents but doesn’t mean either one is wrong.
How is this different from reconciling RELIEF SLSP to my BIR Form 2550Q? #
Reconciling SLSP to BIR Form 2550Q checks that your own quarterly VAT return agrees with your own supporting DAT file — an internal consistency check you control entirely. An AFS-vs-SLSP mismatch involves the BIR comparing your figures against a separate document (your AFS) or against a counterparty’s own third-party filing, which is why it can surface a discrepancy your internal reconciliation never would.
What should I do first if I receive a Letter Notice citing an AFS-SLSP mismatch? #
Identify which specific transactions make up the cited gap, pull the underlying invoices and delivery or accrual records for those transactions, and determine whether the cause is a timing difference, a counterparty reporting error, a wrong TIN, or a genuinely unreported transaction — then submit a written explanation with supporting documents to the BIR office handling the Letter Notice within its resolution window.
Summary #
A RELIEF SLSP mismatch against your Audited Financial Statements is a different, higher-stakes problem than a mismatch against your own BIR Form 2550Q: it’s a discrepancy the BIR’s third-party data matching under RMO No. 13-2012 can catch on its own, after filing, using data from your AFS, a counterparty’s SLSP, or Bureau of Customs records — and it’s exactly the kind of gap that generates a Letter Notice. Most gaps trace back to accrual-timing differences, one-sided counterparty reporting, TIN errors, branch-consolidation issues, or rounding — not genuine unreported income. Responding well means tracing the cited figure to specific transactions, documenting the cause, and submitting an explanation within the resolution window RMO No. 13-2012 gives the assigned revenue officer. For LN mechanics generally, see What Is a BIR Letter Notice (LN) and How Is It Different From a Letter of Authority (LOA)?; for the internal RELIEF SLSP-to-BIR Form 2550Q check that should happen before you ever file, see RELIEF SLSP vs BIR Form 2550Q: How to Reconcile Your Sales and Purchases Listing.