Common BIR eAFS Upload Errors and How to Fix Them Before the Deadline

A rejected BIR eAFS upload is almost always a fixable file problem, not a system outage — most commonly a duplicate file extension like .pdf.pdf left over from a scan or conversion, a file that isn’t actually a PDF despite the name, or a filename built for the wrong taxable year. This guide walks through the specific errors that get an Audited Financial Statements package bounced from eAFS and how to fix each one before your attachment deadline closes.

This is a companion to What Is the BIR eAFS System, and How Do You Submit Financial Statements Electronically?, which covers what eAFS does and the standing 15-calendar-day submission window — this post assumes you already know that and are now staring at a rejected upload.

Why does eAFS reject a file that opens fine on your screen? #

The single most common eAFS rejection is a duplicate file extension — a filename like EAFS123456789AFSTY122025.pdf.pdf that opens normally in any PDF viewer but fails eAFS’s upload check because the system reads the trailing characters literally. This happens when a scanning app or PDF converter automatically appends .pdf to a filename the preparer had already typed with .pdf on the end, or when a file is renamed in a file manager that hides extensions by default and an extra one gets typed in by hand.

• Duplicate extensions (.pdf.pdf): rename the file so .pdf appears exactly once, then re-upload — do not just add another extension on top.
• Non-PDF formats: eAFS accepts PDF only; Word documents, JPEG/PNG images, and ZIP archives are rejected outright regardless of what the filename extension claims.
• Corrupted or partially converted scans: a multi-page scan interrupted mid-export, or a file produced by a scanner app that writes a placeholder before finishing the conversion, can look like a valid PDF in a file listing but fail validation on upload — re-scan or re-export the document rather than retrying the same file.

The file-naming convention eAFS actually checks #

eAFS does not just accept any PDF — it expects a specific filename structure built from your TIN, a document-type code, and the taxable year, and getting any part of that wrong is a separate failure mode from a corrupted file. Under Revenue Memorandum Circular No. 43-2021, the prescribed structure for an Audited Financial Statements file is built from the literal prefix EAFS, the taxpayer’s 9-digit TIN, the document code AFS, the literal code TY, and the month and year the taxable period ended — for example, a calendar-year 2025 filer’s AFS file follows the pattern EAFS + TIN + AFSTY122025.

Additional files within the same document-type group (a multi-page AFS submitted as separate PDFs, for instance) are numbered in sequence rather than each reusing the same filename — reusing an identical filename for a second file typically causes the second upload to silently overwrite or be rejected rather than appending.

Uploading the Audited Financial Statements for the wrong taxable year #

eAFS generally does not cross-check the taxable year embedded in your filename against the Income Tax Return you actually filed — it accepts the upload, and the mismatch only surfaces later when the BIR reconciles the attachment against your return for that period. A common version of this error: a filer who prepares AFS packages for multiple fiscal years back-to-back accidentally reuses last year’s filename template and uploads a 2024 AFS set under a filename coded for taxable year 2025, or vice versa.

Because the portal will not flag this automatically, the practical fix is procedural, not technical — have whoever assembles the eAFS package verify the taxable-year code in every filename against the actual Income Tax Return being attached before clicking upload, every single filing season, rather than trusting a template carried over from the prior year.

Missing required attachments eAFS won’t warn you about #

eAFS confirms that the files you uploaded went through — it does not check whether your submission is complete, so a package missing the Statement of Management’s Responsibility or the Independent CPA’s Certificate will upload successfully and still leave you exposed to a compliance gap. See BIR Form 1701 Attachments: What to Submit With Your Annual Income Tax Return for the full checklist; the pieces preparers most often forget are:

• The Statement of Management’s Responsibility, a separate signed page from the AFS itself
• The Independent CPA’s Certificate accompanying the audited statements
• BIR Form 1709 (Related Party Transactions), where the taxpayer has reportable related-party dealings
• The BIR Form 2307 certificates and supporting SAWT where creditable withholding tax is being claimed against the return

What to do when eAFS itself is down or rejecting everything near your deadline #

When the file is genuinely fine and eAFS itself is unresponsive or erroring across the board close to a deadline, BIR precedent shows the agency can grant a short, penalty-free resubmission window — but that relief has historically been issued for a specific filing season, not as a standing rule you can assume applies every year. Under Revenue Memorandum Circular No. 39-2026:

“The final and uniform deadline for submitting all required attachments through eAFS is 15 May 2026, regardless of the actual date of electronic filing within the extended period.” — Grant Thornton Philippines, tax note on RMC No. 39-2026

That circular fixed one uniform deadline regardless of filing date; separately, the BIR has in past seasons allowed taxpayers who could document a genuine eAFS system problem to resubmit for a short additional window without a late-submission penalty. Treat any such grace period as season-specific relief, not a guarantee, and in the meantime:

1. Screenshot or save every error message with its timestamp, not just a note that “it didn’t work.”
2. Try a clean re-export — a single, freshly generated PDF per document rather than retrying the identical file that already failed.
3. Check for an official BIR system-unavailability advisory for that date before assuming the problem is on your end.
4. Remember the ITR itself is a separate deadline — an eAFS attachment problem does not excuse a late Annual Income Tax Return filed through eFPS or eBIRForms.

Worked example: fixing a rejected 2025 AFS upload #

Meridian Trading Corp.’s bookkeeper scans the 2025 Audited Financial Statements, converts it with a desktop scanning app, and uploads it to eAFS two days before the attachment deadline — the portal rejects it. Checking the filename shows EAFS001234567AFSTY122025.pdf.pdf: the scanning app’s “Save as PDF” step appended a second .pdf on top of the name the bookkeeper had already typed.

The fix took minutes once the actual cause — the doubled extension — was identified, rather than hours spent re-scanning a document that was never the problem.

Frequently asked questions #

Why does the BIR eAFS system reject a file that opens fine on my computer? #

The most common cause is a duplicate file extension such as “.pdf.pdf” created when a scanner or converter appends “.pdf” to a filename that already ends in “.pdf” — the file opens fine locally but eAFS reads the extension literally and rejects it. Non-PDF formats (Word, JPEG, ZIP) and corrupted or partially converted scans are the other leading causes.

What file naming convention does BIR eAFS require? #

Under Revenue Memorandum Circular No. 43-2021, eAFS filenames embed the literal prefix EAFS, the taxpayer’s 9-digit TIN, a document-type code (such as AFS for the Audited Financial Statements or ITR for the return itself), and the taxable year the filing covers, generally ending in the month and year the taxable period closed.

What happens if I upload the Audited Financial Statements for the wrong taxable year? #

eAFS will often still accept the upload since the taxable-year field is part of the filename you control, not something the portal independently verifies against your return. The error surfaces later, when the BIR reconciles the attachment against the filed Income Tax Return for that period and finds a mismatch — so always double-check the taxable year in the filename against the return before uploading, rather than relying on eAFS to catch it.

Does a rejected eAFS upload excuse a late Annual Income Tax Return? #

No. The eAFS attachment submission and the Annual Income Tax Return filing are governed separately. A problem uploading attachments through eAFS does not extend or excuse the ITR’s own filing and payment deadline, which is filed and paid through eFPS or eBIRForms.

What should I do if eAFS keeps rejecting every file close to my deadline? #

Document each failed attempt with a timestamp and the exact error shown, try a fresh single-page-per-file PDF export instead of a scanned multi-page file, and check for a BIR system-unavailability advisory for that date. BIR precedent under Revenue Memorandum Circular No. 46-2026 shows the agency has granted a short penalty-free resubmission window for taxpayers who had genuine eAFS system problems near a deadline — but that relief was issued for a specific filing season and is not a standing rule you can assume applies automatically.

Summary #

Most eAFS upload failures trace back to one of a handful of fixable causes: a duplicate file extension like .pdf.pdf, a non-PDF or corrupted file, a filename built under the wrong taxable year, or a package that’s missing a required attachment eAFS doesn’t flag on its own. Check the filename structure under RMC No. 43-2021 before assuming a system outage, and remember the eAFS attachment window runs separately from the ITR filing deadline itself. See What Is the BIR eAFS System for the portal’s mechanics and standing 15-day rule, and RMC No. 39-2026 for how the BIR has handled a uniform deadline during a filing-season extension.