eFPS Payment Not Reflected? What to Do When Your Return Still Shows Unpaid

When eFPS shows a return as “unpaid,” “e-Payment Failed,” or “Pending” even though a bank account was already debited, the most common cause is a timing gap between the bank’s own confirmation of the debit and eFPS updating its payment status to match — not a lost payment. The fix starts with your bank’s own transaction record, not with paying again: the money already left your account, so your bank has independent proof of that transaction whether or not eFPS has caught up yet.

Why eFPS can show “unpaid” after your account was already debited #

eFPS payment is processed by a Transacting Bank’s own internet banking system, which debits the taxpayer’s account and issues its own Confirmation Number independently of what eFPS itself displays a moment later. Per BIR’s own eFPS payment help documentation, that number is:

“A control number generated online by the Transacting Bank’s Internet Banking System to confirm the tax payment.”

That single sentence is the key to understanding the gap: the bank’s confirmation is generated by the bank’s system at the moment of debit, but eFPS’s own payment status reflects a separate step — the bank crediting the payment to the Bureau of Treasury account and that record being matched back to the filed return. A brief lag between those two systems, or an interrupted session on the taxpayer’s end right after authorizing payment, can leave eFPS displaying “Failed,” “Pending,” or an outright “unpaid” status on a return that the bank has, in fact, already debited. This is a distinct problem from confirming a return was filed at all — see eFPS and eBIRForms Filing Reference Number (FRN) for that separate step, and from an enrollment being stuck, which is covered in BIR eFPS Enrollment Rejected or Stuck Pending.

FRN vs. bank Confirmation Number: check you have the right proof #

A Filing Reference Number and a payment Confirmation Number prove two entirely different things, and a taxpayer troubleshooting an “unpaid” status needs to be looking at the right one. Confusing them is a common reason a filer assumes a payment problem when the actual gap is somewhere else, or vice versa.

If you only have an FRN and no bank-side confirmation at all, the return may be filed but genuinely unpaid — a different problem, and one where paying is the correct next step, not a mistake. If you have a bank debit and a Confirmation Number but eFPS still shows unpaid, the filing and the money both likely exist; the two records just haven’t reconciled on screen yet.

Step-by-step: what to do when eFPS shows unpaid but your account was debited #

Work from your own bank record outward, and hold off on re-paying until you’ve ruled out that the original transaction is simply still processing. In order:

1. Open your bank’s app or online banking portal and check the transaction history directly — do not rely on eFPS’s screen alone. The debit either appears there with a status and reference number, or it doesn’t.
2. Screenshot or save the bank’s transaction confirmation, including the Confirmation Number, exact date and time, amount, and the return/tax type referenced, if the bank’s system captures that detail.
3. Do not click “Pay” again immediately. If the original debit is simply delayed in posting to eFPS, a second payment creates a real overpayment, not a fix.
4. Allow at least one full business day for the bank to credit the payment to the Bureau of Treasury account and for that record to reach eFPS, since this crediting step is separate from the initial debit and is not instantaneous.
5. If the status still hasn’t updated after that window, contact the Authorized Agent Bank first. The bank holds the debit record and can confirm whether the payment was successfully credited on its end.
6. If the bank confirms the payment posted but eFPS still shows unpaid, escalate to your RDO with both the bank’s Confirmation Number and your eFPS Filing Reference Number, so BIR can reconcile its own records against the bank’s.
7. Only make a new payment once the bank or BIR has affirmatively told you the original transaction failed — not merely because eFPS’s status hasn’t refreshed yet.

BIR’s own eFPS documentation does not appear to publish a single, named procedure specifically titled for this debited-but-unreflected scenario as distinct from a general payment or filing FAQ — the steps above follow directly from how the bank-confirmation and eFPS-status layers are described to work, plus standard reconciliation practice of checking the payer’s own bank record before assuming BIR’s system is the source of truth. If BIR later publishes a specific circular naming this exact procedure, it would supersede the general practice above.

Worked example: a Q3 1701Q filer stuck on “e-Payment Failed” for 24 hours #

A self-employed consultant files BIR Form 1701Q for Q3 2026 through eFPS on the statutory deadline and authorizes payment through her enrolled bank’s internet banking session. Her bank app immediately shows a debit with a Confirmation Number and a timestamp. Back on eFPS, the payment status reads “e-Payment Failed” rather than confirming success.

1. She does not click “Pay” again, since the bank clearly shows the money already left her account.
2. She screenshots the bank’s transaction history entry — Confirmation Number, date, time, and the ₱24,000 amount — and separately screenshots eFPS’s “e-Payment Failed” screen for the record.
3. She waits until the next business day rather than assuming the worst overnight, since the debit itself already exists as proof a payment attempt was made on time.
4. The following morning, eFPS still shows the same status, so she calls her bank’s corporate/business banking support line, references the Confirmation Number, and asks whether the payment was credited to the Bureau of Treasury account.
5. The bank confirms the transaction settled successfully on its end. She brings that confirmation, along with her Filing Reference Number and the bank’s Confirmation Number, to her RDO to have eFPS’s own record reconciled.
6. Within a few business days, eFPS updates to reflect the payment. Throughout, she kept both reference numbers together in the same file, the same practice recommended in BIR Online Payment Options for any electronic payment channel.

Why you should not simply pay again #

Re-paying before confirming the status of the original transaction turns a timing delay into an actual overpayment, which is far slower to fix than waiting a business day. If both the original debit and a second payment eventually post for the same return and period, the taxpayer has genuinely paid twice, and recovering the extra amount means filing an administrative claim for refund or tax credit for an erroneously or illegally collected tax — a process governed by Sections 204(C) and 229 of the National Internal Revenue Code, which impose a two-year prescriptive period from the date of payment and require the claim to be filed with the BIR before any judicial claim can follow. That process is measured in months, not the day or two it typically takes a delayed eFPS status to catch up with a bank record that already shows the debit went through.

This is also why the payment side of a filing deserves the same discipline as the filing side itself: an eFPS-integrated payment and a separate channel like GCash, Maya, or LandBank Link.Biz each produce their own confirmation number that has to be kept and, if needed, matched manually against BIR’s own records — see How to Pay BIR Taxes via GCash, Maya, or LandBank Link.Biz for how that reconciliation step works on channels outside eFPS.

Frequently asked questions #

Why does eFPS still show my return as unpaid after my bank account was debited? #

eFPS payment happens through a Transacting Bank’s own internet banking system, and the bank debits the taxpayer’s account and generates its own Confirmation Number the moment the instruction is processed. eFPS itself only updates its payment status once that transaction is posted and matched back to the return, which does not always happen instantly, so a real debit can sit ahead of eFPS’s own status update for a period of time.

What should I do first if eFPS shows my payment as Pending or Failed but my bank account was already debited? #

Open your bank’s own app or online banking transaction history first — the debit already exists there independently of what eFPS displays — and save or screenshot the bank’s Confirmation Number and the exact date, time, and amount. Do not attempt the payment again until you’ve confirmed with the bank or BIR whether the original transaction actually failed.

Is it safe to just pay again if eFPS still shows unpaid? #

No, not before confirming the status of the original transaction. If the first debit ultimately posts successfully and a second payment is also made for the same return and period, the taxpayer has overpaid and must pursue a refund or tax credit for the erroneous second payment under the NIRC, which takes considerably longer to resolve than simply waiting a business day or two for the first payment to reflect.

What’s the difference between a Filing Reference Number and an eFPS payment Confirmation Number? #

The Filing Reference Number (FRN) is proof the return itself was received and accepted by BIR’s system; the Confirmation Number is a separate control number the Transacting Bank generates to confirm that a tax payment was processed. A taxpayer can have a valid FRN and still have an unresolved payment status, because filing and payment are two different steps that each produce their own confirmation.

Who do I contact if an eFPS payment discrepancy isn’t resolved after a few business days? #

Contact the Authorized Agent Bank (AAB) that processed the debit first, since it holds the transaction record and confirmation number for the debit itself, and ask it to confirm whether the payment was credited to the Bureau of Treasury account. If the AAB confirms the payment posted but eFPS still doesn’t reflect it, escalate to your RDO with both the bank’s confirmation number and your eFPS filing reference number so the mismatch can be reconciled on BIR’s side.

Summary #

A return that shows “unpaid,” “Pending,” or “e-Payment Failed” in eFPS after a bank account was already debited is usually a reconciliation lag between the bank’s own confirmation and eFPS’s payment status, not a lost payment — check your bank’s transaction history first, save the Confirmation Number, and give it at least a business day before escalating to the AAB and then the RDO. Never re-pay before confirming the original transaction’s actual status, since an unnecessary second payment turns a timing delay into a slow, formal refund claim under NIRC Sections 204(C) and 229. For the separate question of confirming a return was filed at all, see eFPS and eBIRForms Filing Reference Number (FRN), and for a full comparison of every BIR electronic payment channel, see BIR Online Payment Options.