QAP DAT File Accepted on eSubmission — Why Did BIR Flag It Months Later?

BIR’s eSubmission system accepting a QAP (Quarterly Alphalist of Payees) DAT file only confirms the file passed a format and structure check at the moment of upload — it is not a substantive clearance of the figures inside it. A QAP that uploads cleanly, with no TIN, ATC, or layout errors, can still be flagged months or years later once BIR’s own data-matching tools compare it against what a payee separately reports, surfacing as a Letter Notice and, if unresolved, a Notice of Discrepancy.

This guide covers the difference between what eSubmission checks at upload and what BIR checks afterward, how a clean QAP still ends up flagged, the notice sequence that follows, and a worked mismatch example.

Why “accepted” at upload isn’t the same as “cleared” #

eSubmission’s confirmation that a QAP DAT file was received and accepted means the Validation Module found no structural problems with the file — it does not mean BIR has checked the figures inside it against anything else. The acceptance step runs automated checks on the file itself: correct record layout, valid TIN format and checksum, recognized ATC codes, internally consistent totals. None of that touches whether the amount a withholding agent reports paying a given payee actually matches what that payee reports having received.

This is a genuinely different failure stage from the pre-upload errors covered in Common QAP DAT File Errors — an invalid TIN or unrecognized ATC code stops a file from being accepted at all, while the issue this guide covers happens to a file that was already accepted without any such error.

What BIR checks later: third-party data matching #

Once a QAP is accepted, it becomes raw data BIR can later cross-check against other filings reporting the same transactions — most directly, the SAWT a payee files to claim credit for the same withholding the agent reported. QAP and SAWT describe the same underlying payments from two different sides, as this series covers in QAP vs SAWT: What’s the Difference Between These BIR Alphalist Attachments? — a withholding agent’s QAP row for a payee should line up with that payee’s own SAWT row for the same withholding agent and quarter. A gap between the two is exactly the kind of thing BIR’s computerized third-party matching is built to surface.

This isn’t a theoretical risk. In Commissioner of Internal Revenue v. Philippine Daily Inquirer, Inc. (G.R. No. 213943, decided March 22, 2017), the deficiency assessment at the center of the case originated years after the original tax year, when BIR ran a computerized comparison of the taxpayer’s declared purchases against third-party data and flagged a large discrepancy — illustrating how a filing accepted at the time it was made can still surface in a BIR matching exercise long afterward, well outside the original filing window.

From a flagged mismatch to a Notice of Discrepancy #

If an examiner’s investigation of a matching-flagged QAP mismatch finds the withholding agent liable for a deficiency, the next taxpayer-facing step is a Notice of Discrepancy (NoD), the written notice Revenue Regulations No. 22-2020 put in place of the old Notice of Informal Conference. RR No. 22-2020 describes the step this way:

“the taxpayer shall be informed, in writing, by the Revenue District Office or by the Assessment Division/Regional Investigation Division, as the case may be (in the case of Revenue Regional Offices) or by the Chief of Division concerned (in the case of the BIR National Office) of the discrepancy or discrepancies in the taxpayer’s payment of his internal revenue taxes, for the purpose of the ‘Discussion of Discrepancy’”

— Revenue Regulations No. 22-2020, amending Section 3 of RR No. 12-99

A taxpayer generally has five days from receiving the NoD to appear and discuss the finding, with up to thirty days to submit supporting documents if more time is needed — the same window covered in full in What Is a BIR Notice of Discrepancy? A QAP-related NoD names the specific payee, quarter, and amount the matching exercise flagged, which is exactly the information needed to start reconciling before the case moves any further.

Worked example: a QAP figure that doesn’t match the payee’s SAWT #

Meridian Trading Corp. files its Q2 2026 QAP showing ₱500,000 paid to Apex Supplies, Inc., with ₱10,000 EWT withheld at 2% (ATC WC120). The file uploads and is accepted with no validation errors. Separately, Apex Supplies files its own Q2 2026 SAWT claiming credit for ₱13,000 in tax withheld by Meridian Trading — corresponding to ₱650,000 in payments, ₱150,000 more than Meridian reported.

Both filings were accepted on eSubmission at the time they were made — neither one had a format or validation error. Eighteen months later, BIR’s matching exercise flags the ₱150,000 gap and issues a Letter Notice to Meridian Trading. Pulling the actual invoices and BIR Form 2307 copies resolves which figure is correct — in this case, Meridian had omitted a ₱150,000 progress billing paid to Apex late in the quarter from its QAP, a late-posting error rather than fraud — and Meridian amends its QAP and 1601-EQ to match before the matter ever reaches a Preliminary Assessment Notice.

What to do if your accepted QAP gets flagged #

Start from the specific payee, quarter, and amount named in the notice, not from the whole quarter’s filing — a matching flag almost always points at one relationship, not the entire QAP.

1. Pull every BIR Form 2307 issued to that payee for the quarter named, plus the underlying payment ledger or disbursement entries.
2. Reconcile those records against both your own QAP row and, if you can get it, the payee’s SAWT figure for the same quarter.
3. Identify whether the gap is a late-posting timing difference, a duplicate entry, a wrong amount on one side, or a payee reporting a transaction with a different withholding agent entirely.
4. Prepare the reconciliation before the scheduled Discussion of Discrepancy, so it can be presented at the NoD stage rather than carried forward unresolved into a PAN.
5. Amend the QAP and the related 1601-EQ if your own filing turns out to be the one that’s wrong, following the correction steps in Common QAP DAT File Errors.

Frequently asked questions #

Does BIR’s eSubmission acceptance mean my QAP DAT file is fully cleared? #

No. eSubmission’s acceptance confirms only that the DAT file passed the Validation Module’s format and structure checks — correct record layout, valid TINs and ATC codes, consistent totals. It is not a substantive review of whether the amounts reported match what your payees independently report, and it does not prevent the BIR from flagging the same filing later through other means.

How does BIR find a QAP discrepancy after the file has already been accepted? #

Mainly through computerized third-party data matching, cross-checking what one taxpayer reports against what a related taxpayer reports for the same transaction — for example, a withholding agent’s QAP figures against the SAWT a payee files claiming credit for the same withholding. A mismatch surfaced this way can trigger a Letter Notice and, if an examiner’s investigation finds a deficiency, a Notice of Discrepancy months or years after the original QAP was accepted.

What is a Notice of Discrepancy, and how does it relate to a flagged QAP? #

A Notice of Discrepancy (NoD), introduced by Revenue Regulations No. 22-2020, is the written notice the BIR issues once an examiner’s investigation of a flagged return — including one surfaced through QAP/SAWT mismatch matching — finds the taxpayer liable for a deficiency. It gives the taxpayer five days to appear and discuss the finding before the case can move toward a Preliminary Assessment Notice.

What should I do if my accepted QAP gets flagged later? #

Pull the underlying records for the specific payee and quarter named in the notice — the BIR Form 2307 issued, the payment ledger, the bank or cash disbursement entry — and reconcile them against both your own QAP and the payee’s SAWT before the scheduled discussion. A documented reconciliation presented early, at the Notice of Discrepancy stage, resolves far more cases than waiting until a Preliminary Assessment Notice is already in hand.

Is a post-acceptance QAP flag the same thing as a pre-upload validation error? #

No, they are different failure stages entirely. A pre-upload validation error — an invalid TIN, an unrecognized ATC code, a malformed record — stops the file from being accepted in the first place and must be fixed before eSubmission will take it. A post-acceptance flag happens to a file that was already accepted and relates to the substance of the figures reported, not the file’s format.

Summary #

Passing eSubmission’s upload check only means a QAP DAT file is structurally sound — it says nothing about whether the figures inside it match what a payee separately reports on its own SAWT. That second, substantive check happens later, through BIR’s computerized third-party data matching, and can surface as a Letter Notice followed by a Notice of Discrepancy under RR No. 22-2020 long after the original QAP was filed and accepted without incident. Reconciling QAP and SAWT figures proactively, before BIR’s matching does it for you, is the difference between a quick correction and a drawn-out notice sequence. See QAP vs SAWT for how the two filings should line up, and What Is a BIR Notice of Discrepancy? for what happens if a mismatch turns into a formal finding.