QAP (Quarterly Alphalist of Payees): What Lenders Need to Know

If Form 1601-EQ is the summary of the withholding tax you remitted for a quarter, the QAP is the detail behind it: the who, not just the how much. The BIR uses it to match what you withheld against what your payees later claim as credits. When the two sides agree, everyone is happy; when they don't, the BIR sends a notice. For a lending company that pays professionals, landlords, and contractors regularly, keeping a clean QAP is a quiet but important discipline.

What the QAP contains

The QAP is essentially a table with one row per payee, listing the payee's name, TIN, the nature of the income payment, the alphanumeric tax code, the amount paid, and the tax withheld for the quarter. It is submitted electronically in the BIR's prescribed format and attached to the 1601-EQ. Because it is data-driven, its quality is only as good as the vendor records behind it — one missing TIN and the whole alphalist can fail validation.

Why complete vendor data is everything

The single most common QAP problem is incomplete or inconsistent payee information. A missing TIN, a misspelled name, or an address that doesn't match the BIR's records can cause the alphalist to bounce or, worse, create a mismatch that surfaces months later when the payee claims their credit. This is exactly why you should capture a supplier's complete legal name, TIN, and registered address the moment you engage them — long before quarter-end.

The QAP, the 2307, and the 1601-EQ are three views of the same withholding. If they disagree, the BIR assumes something is wrong — and the burden of proof is on you.

The reconciliation that matters

Three numbers must tie together: the total tax on your 1601-EQ, the sum of the withholding on your QAP, and the total across the 2307 certificates you issued for the quarter. If the QAP says you withheld ₱15,000 but your remittance was ₱14,500, the BIR will ask why. Keeping these aligned is trivial when a single system records each payment once and generates all three from the same data — and painful when they are assembled by hand from scattered records.

What happens when the QAP is wrong

It helps to understand the consequences that make QAP accuracy worth the effort. The BIR uses the alphalist to cross-check what you withheld against what your payees claim as creditable tax on their own returns. When your QAP says you withheld ₱1,000 from a supplier but that supplier's TIN is wrong or missing, the system cannot match the two — and either your alphalist is rejected outright or the payee's claimed credit is questioned. Both outcomes generate work and, often, a notice.

These mismatches also have a way of surfacing long after the quarter closed, when a payee files their annual return and their credits don't reconcile with the BIR's records of what you reported. By then, fixing the problem means amending filings and chasing information you should have captured at the start. This lag is exactly why the discipline of complete, correct payee data at engagement pays off: the cost of getting it right is a few minutes when you onboard a vendor, while the cost of getting it wrong is a reconciliation exercise months later, sometimes involving both your company and the payee.

Make the alphalist a by-product

A QAP should never be a quarterly ordeal. If every payment your lending company makes is recorded with a complete payee and the correct tax code as it happens, the alphalist writes itself and already agrees with your remittances and certificates. LendKoPH ties expanded-withholding accounts to vendor records that require full details, so the data a clean QAP needs is captured up front — and reconciliation stops being a source of BIR notices.