Same Payee, Two ATCs: How to Report Multiple Alphanumeric Tax Codes on One QAP

When the same supplier is paid under two different Alphanumeric Tax Codes (ATCs) in one quarter, QAP reports that payee as two separate rows — one per ATC — not as a single combined line. A professional fee and a separate purchase of goods to the same payee carry different withholding rates, so collapsing them into one ATC misstates the rate applied to at least one of the two payments and breaks the reconciliation to that payee’s own certificates.

Why does the same payee sometimes need two ATCs in one quarter? #

A single supplier can bill a withholding agent for more than one kind of income payment within the same quarter, and each kind of payment carries its own Alphanumeric Tax Code under Revenue Regulations (RR) No. 2-98, as amended. A corporate supplier that both renders a professional or technical service and sells goods to the same client in the same three-month period is not an edge case — it is routine for suppliers who do more than one thing for a client.

The ATC exists precisely to capture that distinction. Two payments to the same TIN can legitimately sit under two different codes because:

• The nature of the payment differs — a professional/consultancy fee is withheld under a different ATC than a purchase of goods, even from the identical vendor.
• The rate attached to each ATC differs — professional fees, rentals, and goods purchases are not withheld at a uniform rate under RR No. 2-98 as amended.
• The payee’s TIN does not change, but the transaction category does — the TIN identifies who was paid; the ATC identifies what they were paid for.

For the full list of codes this site has already documented, see What Is an ATC?.

Does QAP combine or separate payments to the same payee under different ATCs? #

QAP separates them: a payee reported under two different ATCs in the same quarter appears as two distinct rows, each carrying its own income amount and tax withheld for that code — never merged into a single blended line. The governing provision describes a QAP row by the fields it must carry, which are tied to a single income category rather than to the payee alone.

“The return filed shall be accompanied by the Quarterly Alphabetical List of Payees (QAP), reflecting the name of income payees, Taxpayer Identification Number (TIN), the amount of income paid segregated per month with total for the quarter, and the total amount of taxes withheld, if any.”

— Section 2.58, Revenue Regulations No. 2-98, as amended by Revenue Regulations No. 11-2018, as quoted in tax-practitioner commentary summarizing the regulation

That segregation runs by income category and rate, not merely by payee name. Because the ATC is what identifies the income category and the rate used for a given line, a withholding agent with two ATCs for the same TIN in one quarter reports two lines — each complete with its own income total and its own tax-withheld total — rather than averaging, summing, or picking one code to represent both payments. Who has to file QAP in the first place is covered separately in Who Must File QAP?; this guide assumes that obligation already applies and focuses only on how one payee’s rows are structured once it does.

Worked example: one supplier, two ATCs, one quarter #

The scenario below is entirely fictional, built only to show how two income types to the same corporate supplier turn into two QAP rows instead of one. Northwind Business Services Corp. is a Top Withholding Agent that works with a single recurring corporate vendor, Everbright Trading Corp. (fictional TIN 456-789-012-000), in Q3 2026.

During the quarter, Northwind pays Everbright Trading Corp. for two unrelated things:

• A management consultancy engagement, billed at ₱50,000, withheld under ATC WC010 (professional fees, corporate payee, 5% rate) — tax withheld ₱2,500.
• A bulk purchase of office equipment, billed at ₱200,000, withheld under ATC WC160 (purchase of goods by a Top Withholding Agent, 1% rate) — tax withheld ₱2,000.

Both payments are to the identical TIN, in the identical quarter, from the identical withholding agent. The QAP DAT file still needs two rows for Everbright Trading Corp., not one:

The bottom row shows the problem with merging: forcing both payments under WC010 overstates the tax that should have been withheld on the goods purchase (₱12,500 instead of the correct combined ₱4,500), while forcing both under WC160 understates the tax owed on the consultancy fee. Only the two-row version — ₱2,500 plus ₱2,000, for a correct combined ₱4,500 — matches what was actually withheld and remitted on BIR Form 1601-EQ for the quarter.

What goes wrong if the two ATCs are merged into one row? #

Collapsing two income types into a single ATC row does not just misstate the rate on paper — it creates a mismatch that surfaces later against the payee’s own records and the annual alphalist. The error compounds because the same ATC and amount data feeds more than one downstream filing.

• Wrong withholding rate. Whichever payment doesn’t actually belong to the chosen ATC gets taxed at the wrong rate, understating or overstating the tax withheld for that income type.
• BIR Form 2307 mismatch. The payee’s certificate for the quarter should show each income type at its correct rate; a QAP that blends the two no longer agrees with what the certificate says.
• Annual 1604-E mismatch. The year-end alphalist consolidates each quarter’s ATC-level detail. A merged quarter carries the error forward into the annual reconciliation — see QAP vs Annual Alphalist (1604-E) for how the two filings are supposed to tie out.
• Validation Module exposure. An ATC that doesn’t match the income category it’s forced onto is the same kind of structural mismatch covered in Common QAP DAT File Errors, even though the specific trigger here is a merging choice rather than a typo.

A sourced reminder of why the alphalist detail matters at all: it is treated as inseparable from the return it supports, not an optional attachment a withholding agent can simplify on its own.

Frequently Asked Questions #

Can I combine two payments to the same supplier into one QAP row if they use different ATCs? #

No. If the same payee was paid under two different Alphanumeric Tax Codes in the same quarter — for example, a professional fee and a separate purchase of goods — each ATC gets its own QAP row for that payee. Merging them into one row forces a single rate onto two payments that were legally withheld at different rates.

Why does the same TIN appear twice on a QAP DAT file? #

A TIN appears more than once on a QAP DAT file when the withholding agent paid that payee under more than one Alphanumeric Tax Code during the quarter. Each TIN-and-ATC combination is its own row, so a supplier billed for two different income types in one quarter is a perfectly normal case of the same TIN showing up on two lines, not a duplicate to be deleted.

Does reporting one payee under two ATCs cause a QAP validation error? #

Not by itself. The BIR Alphalist Data Entry and Validation Module checks each row’s structure — TIN format, ATC validity, amount fields — rather than flagging a repeated TIN as an error, since a payee legitimately appearing on multiple rows under different ATCs is expected. A validation error would come from a malformed TIN or an ATC that does not match the income type, not from the repetition itself.

What happens if I pick just one ATC for a supplier that actually has two income types? #

Picking a single ATC to cover both payments misstates the withholding rate for whichever payment does not actually belong to that code, understates or overstates the tax withheld for that income type, and creates a mismatch against the payee’s own BIR Form 2307 certificates and the annual BIR Form 1604-E alphalist, which track the same payments by ATC.

Do I need to issue two separate BIR Form 2307 certificates for the two ATCs? #

The certificate itself can carry more than one ATC line for the same payee and period, but each income type still needs its own correctly coded line showing its own income amount, rate, and tax withheld — the same one-line-per-ATC principle that governs the QAP row for that payee.

Does this multiple-ATC situation change who must file QAP? #

No. Whether a payee is reported once or twice in a quarter has no bearing on the underlying filing obligation — any withholding agent with expanded withholding tax activity in the quarter already must file QAP regardless of how many ATCs or rows the file ends up with. See Who Must File QAP? for that separate question.

Summary #

A supplier paid under two different income types in the same quarter is not reported once on QAP — it is reported once per ATC, with each row carrying its own income amount, rate, and tax withheld under Section 2.58 of RR No. 2-98 as amended by RR No. 11-2018. Merging the two into a single row applies the wrong rate to at least one payment and breaks the reconciliation to that payee’s BIR Form 2307 certificates and the annual BIR Form 1604-E alphalist. Keep the ATC, not just the TIN, as the unit of a QAP row, and the same-payee, multiple-ATC case resolves itself as two clean lines rather than one disputed one. For the broader filing obligation this builds on, see Who Must File QAP?; for how a quarter’s QAP data should tie out against the year-end return, see QAP vs Annual Alphalist (1604-E); for other structural DAT issues to clear before eSubmission, see Common QAP DAT File Errors.