Common QAP DAT File Errors and How to Fix Them Before eSubmission

Most QAP DAT file errors come from five places: a malformed payee TIN, an ATC that does not match the income remitted, incomplete payee names, tax-withheld amounts that do not reconcile to the quarterly remittance, and a return period that does not match BIR Form 1601-EQ or 1601-FQ. Each one can stop the Alphalist Data Entry and Validation Module from issuing a zero-error report under the electronic alphalist rules in Revenue Regulations (RR) No. 1-2014, so the DAT never should have been emailed for eSubmission.

This guide walks through each failure mode and how to fix it. For what QAP is, see What Is QAP?; for conversion columns, see How to Convert Excel to BIR DAT File for QAP.

Why does the Validation Module reject a payee TIN? #

A QAP TIN error means the payee identification number is the wrong length, contains non-digit characters, lost a leading digit in Excel, or uses a placeholder the module rejects. The BIR’s Alphalist Data Entry and Validation Module expects digits only in the TIN field, with branch code tracked separately — the same structural discipline used across other alphalist DAT filings under RR No. 1-2014.

Typical causes:

• TIN pasted with dashes or spaces (123-456-789 instead of digits only)
• Excel Number format dropping a leading zero or truncating the value
• Branch code merged into the base TIN field
• Placeholder 000000000 left on a row “to fill later”

Fix: format the TIN column as text before entry, strip non-digits, keep branch code in its own field, and never ship a placeholder TIN.

Why do ATC codes fail on an otherwise complete QAP? #

An ATC mismatch means the alphanumeric tax code on the QAP row does not describe the income type and payee category actually withheld and remitted for that line. The Validation Module checks codes against the current ATC table; a code that is merely “close” still fails if it is wrong for a corporate versus individual payee or for the withholding category used on BIR Form 2307.

Fix: copy the ATC from the same source used for remittance and for BIR Form 2307 issuance for that payment — not from memory or from last year’s spreadsheet template.

Name, address, and identity gaps #

A QAP row can fail even with a perfect TIN if the registered name (or required individual name fields) is blank, truncated, or inconsistent with how the payee appears on remittance schedules. Address fields, where required by the layout, must also be present in the expected structure; empty mandatory string fields are treated as structural errors, not cosmetic ones.

Fix:

• Corporate payees: full registered name as used on BIR registration / invoices
• Individual payees: complete last name and first name fields the layout requires
• Avoid nicknames, trade names alone, or “TBD” placeholders

Amount vs remittance mismatches and wrong period #

Tax-withheld totals on the QAP should reconcile to what the withholding agent remitted on BIR Form 1601-EQ or 1601-FQ for the same quarter, and every detail row must carry the same correct return period. A file can look structurally valid while still creating a BIR matching problem if QAP withheld tax is ₱11,500.00 and the return remitted ₱12,000.00 for the same payees.

Wrong-period rows — for example, March payments left in a Q2 file — are especially costly because they both fail consistency checks and distort the following quarter’s listing. Deadline context is in QAP Filing Deadlines.

A defective or missing alphalist is treated as a failure to file a required information return under Section 250 of the NIRC — ₱1,000 per failure, capped at ₱25,000 per calendar year — with compromise-penalty practice under RMO No. 7-2015, on top of any surcharge or interest if the underlying 1601-EQ / 1601-FQ is also late.

Worked example: fixing an invalid TIN row #

Cleaning one bad TIN is often enough to turn a rejected QAP DAT into a zero-error file — provided amounts and ATC were already correct. The payee below is fictional.

A withholding agent’s Q2 2026 QAP fails validation on a single row:

Corrected row before regenerating the DAT:

After the source spreadsheet is fixed, regenerate the QAP DAT and re-run the BIR Alphalist Data Entry and Validation Module until the report shows zero errors — the same pre-eSubmission discipline described in How to Validate a BIR DAT File Before eSubmission.

Pre-upload checklist #

• TINs digits-only, correct length, branch code in its own field, no 000000000 placeholders
• ATC matches income type, payee type (WC vs WI), and remittance / BIR Form 2307
• Every row has a complete registered name or complete required individual name fields
• Tax-withheld totals reconcile to BIR Form 1601-EQ or 1601-FQ for the quarter
• Return period identical on every row and correct for the quarter being filed
• Final DAT cleared through the BIR Validation Module before eSubmission

Frequently asked questions #

Why does my QAP DAT fail TIN validation? #

A QAP payee TIN must be numeric digits in the length and structure the Alphalist layout expects, with the branch code handled as a separate field. Dashes, spaces, a leading digit stripped by Excel, or a placeholder like 000000000 will cause the BIR Validation Module to reject the row.

What causes an ATC mismatch on a QAP file? #

An ATC mismatch means the alphanumeric tax code on the QAP row does not match the income type and rate actually withheld and remitted for that payee — for example, using a goods TWA code on a professional-fee payment, or an individual (WI) code on a corporate payee.

Can a QAP pass if payee names are incomplete? #

No. Every QAP detail row needs a complete registered name for a corporate payee, or complete individual name fields where the layout requires them. A blank registered name with only a partial first name is a common rejection even when the TIN and amounts are correct.

What happens if QAP amounts don’t match my BIR Form 1601-EQ remittance? #

If the tax-withheld totals on the QAP DAT do not reconcile to the amounts remitted on BIR Form 1601-EQ (or 1601-FQ) for the same quarter, the file may still clear structural validation but creates a matching problem the BIR can query — fix the source amounts before eSubmission.

What is the penalty for an incomplete or defective QAP alphalist? #

Failure to file a required information return or alphalist is penalized under Section 250 of the NIRC at ₱1,000 per failure, capped at ₱25,000 per calendar year, with compromise-penalty guidance under RMO No. 7-2015 — separate from surcharge and interest on a late 1601-EQ or 1601-FQ return itself.

Summary #

QAP DAT rejections are usually fixable source-data problems: TIN format, ATC choice, incomplete names, remittance mismatches, or the wrong return period — all of which the BIR Alphalist Data Entry and Validation Module is designed to catch before eSubmission under RR No. 1-2014. Leaving them unfixed risks Section 250 exposure (₱1,000 per failure, ₱25,000 cap) under the same information-return rules used elsewhere in BIR compliance. Validate first, then file. Start from What Is QAP?, build with Excel to BIR DAT File for QAP, and clear errors with the DAT File Validation Module guide before the QAP filing deadline.