RMC No. 82-2021 allows clear eAFS screenshots as proof of BIR submission when no confirmation or acknowledgement email is received after upload.
Taxpayers who uploaded scanned documents through the BIR eAFS System but did not receive a confirmation or acknowledgement email may still prove submission by presenting clear screenshots from the eAFS System. This matters immediately for corporations, accountants, and compliance teams that need proof of BIR submission for regulatory or business purposes, including submission requirements involving the Securities and Exchange Commission.
What RMC No. 82-2021 Changed
RMC No. 82-2021 addresses a practical compliance problem: some taxpayers successfully upload scanned copies of documents through the Bureau of Internal Revenue electronic Audited Financial Statements System, but due to technical issues, they do not receive the usual confirmation or acknowledgement email. Without that email, taxpayers may have difficulty proving to other offices that they already submitted the required documents to the BIR.
The key rule is simple but important: in lieu of the confirmation or acknowledgement email, copies of screenshots from the eAFS System may be considered sufficient proof of submission to the BIR, provided that the screenshots clearly show the relevant details. This gives taxpayers an alternative evidentiary record when the eAFS System does not generate or transmit the expected email confirmation.
For businesses searching for BIR eAFS proof of submission, no BIR confirmation email after eAFS upload, eAFS acknowledgement email not received, AFS submission proof to BIR, or SEC proof of BIR AFS submission, the practical takeaway is that the absence of the email does not automatically mean there is no proof of submission. The taxpayer must, however, preserve screenshots that clearly show the taxpayer and transaction details in the eAFS System.
Who Is Most Affected
The taxpayers most affected are corporations and other entities required to upload scanned copies of documents through the BIR eAFS System, especially those that need to show proof of submission to another government office. The circular specifically mentions that affected taxpayers may be unable to present proof to other offices such as the Securities and Exchange Commission when the confirmation or acknowledgement email is not received.
Corporate accountants, CFOs, tax managers, external auditors, bookkeepers, and corporate secretarial teams should pay particular attention to this rule. In practice, the person handling annual compliance may complete the eAFS upload but later discover that the company has no acknowledgement email to attach to internal records, board files, bank requirements, due diligence requests, or SEC-related submissions.
The rule is also relevant for large corporations and SMEs alike. The circular does not create a separate threshold based on gross sales, asset size, paid-up capital, industry, or taxpayer classification. The operative fact is whether the taxpayer uploaded documents to the eAFS System and failed to receive the confirmation or acknowledgement email because of technical issues.
What Screenshots Must Show
RMC No. 82-2021 does not allow any random screenshot to replace the acknowledgement email. The screenshots must clearly show the details contained in the eAFS System. The examples in the circular show taxpayer information under the Companies section, including the Company TIN, Registered Name, and RDO Code. These details matter because they connect the eAFS transaction to the correct taxpayer.
The examples also show transaction information, including the Upload Date, Transaction Code, Remarks, and Action columns. The Transaction Code is especially important because it functions as a unique reference for the uploaded documents. The Upload Date is also critical because it helps establish when the taxpayer made the eAFS submission.
The circular further illustrates a file-level view showing the Upload Date, File Name, Document Type, File Size in MB, Page Count, and whether the uploaded file is a PDF. For compliance teams, this means the safer approach is to capture screenshots at both the taxpayer or company level and the transaction or file-detail level, so that the screenshots show not only that the taxpayer had an eAFS record, but also what documents were uploaded and when.
Effective Date and Compliance Deadline
RMC No. 82-2021 is dated June 22, 2021 and states that its provisions take effect immediately. It does not set a future transition period, grace period, or separate filing deadline. The circular is therefore best understood as an immediate evidentiary rule for taxpayers affected by the absence of an eAFS confirmation or acknowledgement email.
The issuance does not change the underlying deadlines for filing or submitting audited financial statements or other covered documents. It only addresses what may be used as proof when the expected acknowledgement email is not received after uploading documents to the eAFS System. Taxpayers should still comply with the applicable BIR and SEC deadlines governing annual filings, attachments, and related regulatory submissions.
Penalties and Risks of Non-Compliance
RMC No. 82-2021 does not impose a new penalty, surcharge, interest, or administrative fine for failure to keep eAFS screenshots. It also does not state a new monetary penalty for taxpayers who do not receive a confirmation or acknowledgement email. However, the practical risk is evidentiary: without the acknowledgement email or proper screenshots, the taxpayer may have difficulty proving that the documents were submitted to the BIR.
This risk can become serious when another office, regulator, auditor, investor, bank, or counterparty asks for proof of BIR submission. A company that cannot produce either the confirmation email or complete eAFS screenshots may face delays in compliance processing, questions during audit or due diligence, or difficulty proving timely submission.
For this reason, taxpayers should treat eAFS screenshots as compliance records, not merely temporary screen captures. They should be saved with the same care as tax returns, filing confirmations, payment forms, audited financial statements, and SEC compliance records.
Practical Steps for Businesses and Accountants
First, after every eAFS upload, the taxpayer or accountant should check whether the BIR confirmation or acknowledgement email was received. The email remains the usual proof of submission. If it is received, it should be saved in the taxpayerβs annual tax compliance folder together with the filed documents.
Second, even if the email is received, it is prudent to take screenshots of the eAFS System immediately after uploading. The screenshots should show the Company TIN, Registered Name, RDO Code, Upload Date, Transaction Code, Remarks, File Name, Document Type, File Size, Page Count, and PDF file indicator, to the extent these appear in the system. This creates a backup record in case the email is misplaced, deleted, blocked by spam filters, or not transmitted.
Third, if no acknowledgement email is received, the taxpayer should preserve the eAFS screenshots in a dated folder and label them by taxpayer name, taxable year, and transaction code. The file name should be easy to retrieve later, especially during SEC submissions, BIR audits, annual compliance reviews, bank renewals, and due diligence exercises.
Fourth, companies should update their annual compliance checklist to include a specific step for saving proof of eAFS submission. The checklist should require either the BIR acknowledgement email or, in its absence, complete eAFS screenshots showing the taxpayer details and transaction details. This is a simple internal control that can prevent compliance disputes later.
Finally, businesses should avoid waiting until a regulator asks for proof. Screenshots should be captured at the time of upload, because system views, access credentials, and available transaction displays may change over time. A taxpayer that waits too long may have difficulty reconstructing the full transaction record.
How Ablola, Saribong & Gueco Can Help
RMC No. 82-2021 is a reminder that tax compliance is not only about filing on time; it is also about preserving reliable proof that filing was completed. For corporations, SMEs, accountants, and in-house legal teams, the safest approach is to maintain organized evidence of every BIR submission, especially where the eAFS System is involved.
Ablola, Saribong & Gueco assists businesses with BIR compliance, tax documentation, SEC coordination, corporate housekeeping, audit support, and regulatory submissions. If your company needs help reviewing its eAFS records, reconstructing proof of BIR submission, or building a defensible tax compliance file, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.