RMO No. 29-2005 sets BIR procedures for correcting calendar or fiscal year mismatches that suspend returns, affect payments, and distort audit notices.
Corporations and other non-individual taxpayers that changed, or need to correct, their accounting period must make sure that their BIR registration records match the accounting period used in their tax returns. RMO No. 29-2005 matters because a mismatch between the accounting period in the BIR Registration System and the accounting period reflected in returns can suspend return processing, disrupt payment posting, create erroneous compliance cases, and even produce incorrect audit notices.
What RMO No. 29-2005 Changed
RMO No. 29-2005 prescribed the internal BIR guidelines and procedures for resolving issues involving changes in accounting period or accounting type. The issuance covers problems affecting several BIR systems: the Registration System, or REG; the Return Processing System, or RPS; the Collection and Bank Reconciliation System, or CBR; the Returns Compliance System, or RCS; the Case Monitoring System, or CMS; and the Audit System.
The key change is procedural but important for taxpayers. When a taxpayer’s accounting period or type in the BIR system does not match the accounting period or type used in its returns, the BIR offices concerned must follow specific steps to verify the correct accounting period, prepare Data Fix Request Forms, attach BIR Form No. 1905 and supporting documents where available, coordinate with the Revenue Data Center or Help Desk, and correct the system records.
This is especially relevant to businesses that shifted from calendar year to fiscal year, from fiscal year to calendar year, or whose accounting period was wrongly encoded from the start of business operations. The Revenue Memorandum Order recognizes that taxpayers other than individuals may be allowed to change accounting period or type upon approval by the Commissioner of Internal Revenue, or by the delegated Regional Director or Assistant Commissioner, by submitting BIR Form No. 1905 together with required attachments such as SEC amendment documents or approval letters.
Who Is Affected by RMO No. 29-2005
RMO No. 29-2005 primarily affects corporations, partnerships, and other non-individual taxpayers that use or have changed an accounting period or accounting type. It is most relevant to companies that file income tax returns, value-added tax returns, percentage tax returns, withholding tax returns, and other returns based on an accounting period reflected in BIR records.
The issuance also directly affects Large Taxpayers, taxpayers registered with Revenue District Offices, and taxpayers handled by Large Taxpayer District Offices, LTAD I, LTAD II, and LT-DPQAD. For business owners, CFOs, tax managers, and corporate accountants, the practical point is simple: the BIR system must recognize the same accounting period used in the company’s tax filings. Otherwise, filed returns and payments may be treated as suspended, mismatched, unregistered, wrongly posted, or subject to follow-up action.
Taxpayers searching for “BIR change accounting period,” “BIR Form 1905 change fiscal year,” “RMO 29-2005 accounting period,” “BIR fiscal year registration error,” or “BIR suspended return error 1011” are usually dealing with the exact operational problem addressed by this issuance.
Key Error Codes and System Issues Covered
RMO No. 29-2005 specifically identifies Error Code 1011 in the Return Processing System, which refers to an inconsistent accounting period in REG and in the return. It also identifies Error Code NM, referring to accounting type mismatched, and Error Code NF, referring to unregistered accounting type, in the Collection and Bank Reconciliation System.
These error codes may arise when a taxpayer files an amended return or a compliance return using a previous accounting period or type, while the latest accounting period or type in the Registration System is different. They may also arise when the taxpayer’s registered accounting period or type was wrong from the start due to encoding error, or when the taxpayer already secured approval for a change but the new accounting period was not implemented in the BIR registration database.
For taxpayers, the consequence is not merely technical. A return that is not properly posted can cause downstream problems in tax compliance monitoring, case generation, tax clearance, audit, and payment reconciliation. The company may have filed and paid, but the BIR system may not correctly recognize the filing or payment until the accounting period mismatch is resolved.
Four Situations Covered by the Guidelines
The first situation involves the filing of an amended return or compliance return for a previous accounting period or type. In this case, the RDO, LTDO, or LT-DPQAD Error Handler prepares a List of Taxpayers with Suspended Returns or Payments using Annex “A” for cases involving Error Code 1011 and either Error Code NM or NF. The REG Officer or User then verifies the correct accounting period or type, retrieves BIR Form No. 1905 and attachments where available, and prepares the Data Fix Request Form for approval.
The second situation involves taxpayers whose accounting period or type in the Registration System is different from the returns filed from the start of business. The RMO gives the example of a taxpayer that should have been a fiscal filer from the beginning, with accounting period or type “F” and start month “05,” but whose registration table showed “C” for calendar and start month “01.” In this case, returns and payments posted under the wrong accounting period or type must be reversed and re-encoded to the correct accounting period or type.
The third situation involves the filing of returns under a new approved accounting period or type. This applies where a taxpayer requested a change from calendar to fiscal year, or from fiscal to calendar year, submitted BIR Form No. 1905 and required attachments, and obtained approval, but the BIR office failed to implement the change in the Registration System. Under the RMO, only returns and payments covered by the effective date of the new accounting period or type should be reversed and re-encoded. Returns and payments posted under the old accounting period or type for return periods before the effective date of the new accounting period must not be included for reversal.
The fourth situation involves the generation of an audit notice for a taxable period that falls within the effectivity of the old accounting period or type, but the accounting period or type reflected in the audit notice is the current one. In this case, the Revenue Officer must prepare a Data Fix Request Form to correct the taxable period in the audit notice and all related system correspondence, subject to approval by the appropriate BIR officials.
Compliance Requirements and Deadlines
For businesses, the most important compliance document remains BIR Form No. 1905, together with supporting documents showing the approved change in accounting period or type. Depending on the circumstances, supporting documents may include an approval letter, SEC amendment, or other documents establishing the taxpayer’s correct accounting period.
RMO No. 29-2005 gives an internal processing deadline for BIR personnel: the verification of Annex “A” and preparation or forwarding of the Data Fix Request Form, together with BIR Form No. 1905 and attachments where available, must be accomplished within five days from receipt of Annex “A” in the relevant cases. This five-day period is important because unresolved mismatches can keep returns and payments suspended or incorrectly posted.
The RMO also provides that it takes effect immediately. Because it was issued on October 17, 2005, taxpayers and tax practitioners dealing with historical returns, old fiscal year changes, system mismatches, or audit notices involving accounting period issues should treat the procedures as part of the applicable BIR administrative framework for resolving such cases.
Penalties and Risks for Non-Compliance
RMO No. 29-2005 does not impose a new tax rate, surcharge, interest rate, or standalone penalty. However, the compliance risks are significant. A mismatch in accounting period or type can result in suspended returns, payment posting errors, invalid or erroneous RCS cases, incorrect audit notices, and confusion over the correct taxable period.
From a taxpayer’s standpoint, the danger is that the company may have complied in substance but still appear non-compliant in the BIR system. This can affect compliance monitoring, tax audits, tax clearance applications, and the resolution of open cases. A business should not ignore Error Code 1011, Error Code NM, Error Code NF, or any BIR notice indicating that the accounting period in the return does not match the Registration System.
Practical Steps for Businesses
First, companies should verify whether their BIR registration records correctly reflect their actual approved accounting period or accounting type. This is especially important for corporations that shifted from calendar year to fiscal year, underwent SEC amendments, changed accounting year for business reasons, or inherited old registration data from prior management or accountants.
Second, tax departments should keep a complete file of BIR Form No. 1905, the approval letter, SEC amendment documents, and related correspondence. These documents are needed when the BIR must validate the taxpayer’s correct accounting period or prepare a Data Fix Request Form.
Third, if returns or payments were posted under the wrong accounting period, the company should coordinate with the proper RDO, LTDO, or Large Taxpayer office so that the BIR can reverse and re-encode the affected returns and payments. In cases involving a new accounting period, the taxpayer should distinguish between returns covered by the effective date of the new accounting period and returns belonging to periods before the change.
Fourth, if an audit notice reflects the wrong taxable period because of an accounting period mismatch, the taxpayer should not assume that the defect will correct itself. The issue may require a Data Fix Request Form and correction through the Case Monitoring System and Audit System.
How Ablola, Saribong & Gueco Can Help
Accounting period issues can look like simple system errors, but they can affect return posting, payment recognition, open compliance cases, and audit exposure. Ablola, Saribong & Gueco assists corporations, CFOs, accountants, and in-house counsel in reviewing BIR registration records, preparing position letters and supporting documentation, coordinating correction requests, and resolving BIR compliance issues involving calendar year and fiscal year mismatches.
For assistance with RMO No. 29-2005, BIR Form No. 1905, fiscal year registration changes, suspended returns, RPS and CBR error codes, or audit notices involving accounting period issues, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.