What to Do When a Payee Gives You a Wrong or Missing TIN for QAP Reporting

When a payee gives a wrong, invalid, or missing TIN, the withholding agent cannot simply file the QAP with a placeholder — the BIR Alphalist Data Entry and Validation Module rejects the row, and the fix is to verify the payee’s real TIN through ORUS or BIR channels, correct the source data, and regenerate the DAT file before (re)submission.

Why does a payee’s TIN matter for QAP at all? #

A payee’s TIN is not a convenience field on the Quarterly Alphalist of Payees (QAP) — it is the legal identifier the National Internal Revenue Code (NIRC) requires on any return, statement, or document filed with the BIR, and QAP is one of those documents. Section 236(j) of the NIRC states the requirement directly:

“Any person required under the authority of this Code to make, render or file a return, statement or other document shall be supplied with or assigned a Taxpayer Identification Number (TIN) which he shall indicate in such return, statement or document filed with the Bureau of Internal Revenue for his proper identification for tax purposes.”

— Section 236(j), National Internal Revenue Code (NIRC), as amended

QAP is filed as a required attachment to BIR Form 1601-EQ or 1601-FQ under Section 2.58 of Revenue Regulations (RR) No. 2-98, as amended by RR No. 11-2018, and the alphalist itself must reflect the name of each income payee, that payee’s TIN, the income paid, and the tax withheld. A missing or malformed TIN on a QAP row is therefore not a cosmetic gap — it fails the same identification requirement Section 236(j) imposes on every BIR filing. For the full list of things a QAP row must contain, see What Is QAP?; for who has this filing obligation in the first place, see Who Must File QAP?.

What happens when the Validation Module catches a bad TIN? #

The BIR Alphalist Data Entry and Validation Module checks the TIN field structurally before it will issue a zero-error report, and a TIN that fails that check stops the whole file from being submittable — the module does not silently accept the row and flag it later. A payee TIN fails validation when it:

• Has the wrong number of digits for the layout (too short, too long, or a branch code merged into the base TIN)
• Contains non-digit characters — dashes, spaces, or letters left over from a pasted format
• Was truncated or lost a leading digit because Excel stored it as a number instead of text
• Carries a wrong check digit, so it does not match the structure the BIR’s TIN validation logic expects for a real registration
• Is left blank, or filled with an obvious placeholder like 000000000

None of these are conditions the withholding agent can file around. Unlike a rounding difference or a stale-but-plausible ATC code, an invalid TIN is a hard validation failure — the file will not clear the module with a zero-error report until the TIN itself is fixed at the source. This is a narrower, TIN-specific version of the broader error categories covered in Common QAP DAT File Errors and How to Fix Them; this guide focuses specifically on what to do once that TIN row is flagged, not the other error types.

The correction workflow: verify, correct, resubmit #

Once a row is flagged for a bad TIN, the fix is a three-step loop — verify the payee’s actual registered TIN, correct it in the source spreadsheet (not just the DAT file), and regenerate and revalidate before resubmission. Do not guess at a corrected digit or reuse a similar-looking TIN from another payee; an incorrect-but-valid-looking TIN can pass structural validation while still being wrong, creating a mismatch the BIR can query later even though the file uploaded cleanly.

1. Isolate the flagged row(s). Note the payee name, the TIN as originally entered, and the specific validation error the module reported.
2. Verify the correct TIN. Use the ORUS TIN Verification facility at orus.bir.gov.ph to confirm the payee’s TIN against BIR’s records, or ask the payee directly for their Certificate of Registration (BIR Form 2303) or a recent BIR Form 2307 they received from another withholding agent. See How to Verify or Retrieve a Lost BIR TIN Online Using ORUS for the full verification process, including what to do if the payee has forgotten their TIN entirely.
3. Handle a genuinely unregistered payee separately. If the payee has never been issued a TIN at all, the payee — not the withholding agent — needs to register with the BIR and obtain one before the transaction can be reported correctly; there is no verified, generally applicable placeholder TIN format that a withholding agent may use in its place. Resolve this before resubmission rather than filing an unverified number.
4. Correct the source spreadsheet, formatting the TIN column as text, entering digits only, and keeping any branch code in its own field so Excel does not re-truncate it on the next save.
5. Regenerate the QAP DAT file and run it back through the BIR Alphalist Data Entry and Validation Module until it reports zero errors — see How to Validate a BIR DAT File Before eSubmission for that step.
6. Resubmit through the same channel used for the original attempt — eFPS attachment, eSubmission, or the BIR’s alphalist email address — before the QAP deadline for that quarter, since correcting a TIN does not extend the filing deadline.

Worked example: a wrong check digit stalls a Q3 filing #

The payee below is fictional, illustrating a wrong-check-digit scenario rather than an actual taxpayer record.

A withholding agent preparing its Q3 2026 QAP includes a professional-fee payee, Cielo Marasigan Consulting, with the TIN entered as 456-789-124 based on a business card the payee handed over months earlier. The BIR Alphalist Data Entry and Validation Module flags the row: the digit sequence does not match a valid TIN structure — the withholding agent’s own working copy, cross-checked separately, shows the correct number should end in -123, not -124, a single transposed digit likely miscopied from the card.

Because only the TIN digit was wrong and every other field — ATC, income, tax withheld, period — was already correct, fixing the single transposed digit was enough to turn a rejected file into a clean one. A payee that turns out to have no TIN at all would instead need to complete BIR registration before any correction to the QAP row is possible.

Summary #

A payee’s TIN is not negotiable on a QAP filing — Section 236(j) of the NIRC requires it on any document filed with the BIR, and the BIR Alphalist Data Entry and Validation Module enforces that requirement structurally by rejecting rows with the wrong TIN length, non-digit characters, a bad check digit, a blank field, or an obvious placeholder like 000000000. When that happens, the withholding agent’s job is to verify the payee’s actual TIN — through ORUS TIN Verification, the payee’s BIR Form 2303, or a prior BIR Form 2307 — correct the source spreadsheet, regenerate the DAT file, revalidate it to a zero-error report, and resubmit before the quarter’s deadline. A payee with no TIN at all needs to complete BIR registration first; there is no confirmed shortcut around that step. Pair this workflow with Common QAP DAT File Errors for the other rejection categories and QAP Filing Deadlines to make sure a correction cycle still lands on time.