RMO No. 8-2015 requires CRS-based reconciliation of BIR collections, daily discrepancy resolution, and documented 12.09 reporting for accurate tax records.

Daily and monthly tax collection reporting must now be reconciled through the BIR Collection Reconciliation System, with unresolved discrepancies affecting reported collection performance and potentially triggering administrative sanctions for responsible users. RMO No. 8-2015 requires Revenue District Offices, concerned Large Taxpayers Service offices, and collection-related BIR units to monitor collections across all payment channels, resolve system-detected discrepancies promptly, and support monthly collection reports with reconciliation reports and documents where needed.

What Changed Under RMO No. 8-2015

RMO No. 8-2015 prescribed the policies, guidelines, and procedures for implementing the Collection Reconciliation System, or CRS. The CRS was designed to standardize and streamline the reconciliation of internal revenue collections across all modes and channels between BIR records and the records of the Bureau of the Treasury, Bangko Sentral ng Pilipinas, Accredited Agent Banks, and Authorized Government Depository Banks.

The most important operational change is that collection reporting is no longer treated merely as a manual office-level reporting exercise. The CRS is intended to detect discrepancies in tax collection records and require responsible offices to resolve them so that collection performance reports are based on reconciled data. The Order specifically addresses recurring problems in the reporting of tax collection performance in the Consolidated Monthly Statistical Reports, or BIR Form No. 12.09, of Revenue District Offices, Regional Offices, and concerned offices under the Large Taxpayers Service.

For tax managers, accountants, and businesses dealing with BIR payments, the practical importance is that the BIRโ€™s internal reconciliation process directly affects whether payments are properly reflected in BIR collection records. RMO No. 8-2015 covers collections through AABs, Electronic Revenue Official Receipts, Electronic Tax Remittance Advice, Special Allotment and Release Orders, direct crediting, manually issued Revenue Official Receipts, manually issued Tax Remittance Advice, and other collection channels.

Who Is Most Affected

RMO No. 8-2015 is primarily directed to BIR offices and personnel, particularly RDO Collection Sections, concerned Large Taxpayers Service offices, the Revenue Accounting Division, the Research and Statistics Division, Regional Collection Divisions, Regional Finance Divisions, Revenue Data Centers, the BIR Help Desk, the Systems Development Division, the Data Warehousing and Systems Operations Division, the Security Management Division, and the Internal Investigation Division.

However, the Order matters to taxpayers because reconciliation issues usually arise from payment records, uploaded bank collection data, RCO collections, eRORs, eTRAs, SAROs, direct crediting, and BIR Form No. 12.09 reporting. Large taxpayers, taxpayers making payments through AABs, taxpayers with ONETT transactions such as capital gains tax and documentary stamp tax, taxpayers dealing with government remittances through TRA or eTRA, and businesses that need proof of payment posting should be particularly mindful of the reconciliation framework.

Common search concerns that this issuance answers include BIR Collection Reconciliation System, CRS-detected discrepancies, BIR Form 12.09 reconciliation, AAB collection data upload, eROR and eTRA reconciliation, SARO direct crediting tax collection, and BIR tax payment not reflected.

Key Compliance Requirements and Deadlines

RDOs and concerned LTS offices are required to strictly monitor their daily and weekly internal revenue collections across all collection channels using CRS facilities. Each concerned office must assign dedicated personnel, preferably the authorized CBR or CRR error handler, to handle all CRS-detected discrepancies on a daily basis. The Chiefs of the RDO Collection Section and concerned LTS offices are directly responsible for regularly monitoring whether discrepancies are acted upon and resolved on time.

Within five days from approval of the Order, all RDOs and concerned Chiefs of LTS Offices must submit to the Chiefs of the Revenue Accounting Division and the Research and Statistics Division the names of the authorized personnel who will resolve detected discrepancies, including their designations, telephone numbers, and email addresses. If the designated personnel changes, the change must also be officially communicated to the same offices within five days from its implementation.

For daily collection reconciliation, the CRS extracts daily collection data from ITS-CBR or eTIS-CRR with the status P-posted, R-reversed, C-cancelled, Q-stored, and O-out-of-district. These statuses are treated as permanent and can no longer be modified or amended. Collections with other statuses, such as N-new, V-valid, and S-suspended, must be immediately resolved by each RDO or LTS office so that they can be processed by CRS and included in the relevant collection performance report.

Un-uploaded BCS collection data to ITS or eTIS must be coordinated daily by the RDO Collection Section or concerned LTS office with the relevant AABs and Revenue Data Centers. This includes collection data from AABs and Revenue Collection Officers using the Mobile Revenue Collection Officer System. Un-uploaded Consolidated Reports of Daily Collections and unremitted tax collections by AABs must be coordinated daily by the Revenue Accounting Division with the concerned AABs and RDCs.

A specific bank reporting deadline is stated in RMO No. 8-2015: under the Memorandum of Agreement among the AABs, BTr, and the BIR, AABs are required to electronically transmit the daily Consolidated Report of Daily Collections to the Revenue Accounting Division on or before the fifth day following the actual collection date. If that deadline falls on a Saturday, Sunday, or holiday, the eCRDC must be received by RAD on or before the next working day.

The Regional Finance Division or the Large Taxpayers Document Processing and Quality Assurance Division must validate collections through eRORs, manually issued RORs, eTRAs, and manually issued TRAs processed in CRS against the Weekly Statement of Report of Collections and Deposits and the Weekly Compliance and Alphalist of National Government Agencies submitted by the RDOs or concerned LTS offices.

RMO No. 8-2015 also requires timely and accurate encoding of collections through SAROs and direct crediting in ITS or eTIS so that they can be captured by CRS through ITS-CBR or eTIS-CRR. Other internal revenue collection data, including BTr Journal Entry Vouchers and BSP Lists of Remittances, must be electronically sent by RAD to the Systems Development Division in CSV format for uploading to CRS until the concerned agencies can electronically transmit the required data directly to the BIR.

Effect on Monthly Collection Performance Reports

One of the most consequential provisions of RMO No. 8-2015 concerns BIR Form No. 12.09. The ITS or eTIS-generated Monthly Consolidated Statistical Report of Collection must be reconciled with the manual Monthly 12.09 Reports submitted to the Research and Statistics Division. If applicable, Monthly Collection Reconciliation Reports, together with supporting documents, must be submitted to RSD as attachments to the monthly 12.09 reports.

If an RDO or LTS office fails to submit the required reconciliation of tax collections, RSD will use the ITS or eTIS-generated 12.09 report or the CRS-generated data, whichever is lower, as the monthly collection performance figure. This is a significant internal consequence because unresolved or unsupported collection differences may reduce the officeโ€™s reported collection performance.

For RDOs where CRS has not yet been implemented, the manual procedure for reconciling collections must still be strictly followed. In those areas, the ITS or eTIS-generated 12.09 report must be used as the exclusive basis for reporting collection performance. If there are unaccounted collections in the system-generated reports, the concerned RDO or LTS office must submit Monthly Collection Reconciliation Reports and supporting documents to RSD and RAD to allow proper adjustments.

The Order further states that RSD and RAD will not consider additions or adjustments to submitted collection reports other than the system-generated report unless supported by the prescribed attachments and specific details of collection adjustments. It also reminds offices that out-of-year collections posted or booked in ITS-CBR as current-year collections must be part of adjustment items for monthly collection performance reporting, because revenue recognition in ITS-CBR is based on booking date and not the actual collection date.

Access, Help Desk, and User Accountability Requirements

All CRS-related issues must be officially reported by users to the Help Desk by email. The Help Desk must issue a Trouble Ticket Number for every logged issue. That TTN is then used to monitor the status of the issue until resolution. Revenue Data Center Heads are required to ensure that issues logged with their respective Help Desks are immediately closed, resolved, and acted upon on time.

Authorized CRS users must secure access accounts from their respective Revenue Data Centers by accomplishing the Request for Systems Access form, BIR Form No. 0044. If a CRS user is transferred, separated, or no longer performs CRS functions, a request for revocation of access must be filed immediately using BIR Form No. 0037. Heads of concerned offices must require submission of BIR Form No. 0037 before transfer or immediately upon separation or termination of CRS-related services, and must transmit it to the RDC as soon as possible.

Penalties and Consequences for Non-Compliance

RMO No. 8-2015 expressly provides that appropriate administrative sanctions shall be imposed on concerned CRS users who deliberately fail to comply with the Order. It also links discrepancy resolution to performance evaluation by providing that CRS-detected discrepancies must be given utmost priority because they form part of performance evaluation based on CRS-generated Key Performance Indicator Reports.

The Revenue Accounting Division must prepare a list of CRS users designated as CBR error handlers who fail to regularly utilize the system, based on the CRS Users Log generated by the Security Management Division. RAD must forward that list to the Internal Investigation Division not later than the 25th day of the following month for the imposition of necessary sanctions or penalties, if warranted. The Security Management Division must generate Monthly CRS User Logs and forward them to RAD for analysis not later than the 10th day of the following month.

Practical Steps for Taxpayers and Businesses

Although RMO No. 8-2015 is an internal BIR implementation order, taxpayers should take practical steps to reduce the risk of payment mismatches. Businesses should preserve AAB validation records, payment confirmations, tax returns, deposit details, eRORs, RORs, TRAs, eTRAs, and documents supporting SARO or direct crediting transactions. Where a payment does not appear in BIR records, taxpayers should be ready to provide complete supporting documents so the proper BIR office can reconcile the transaction.

For finance teams, the key action point is to treat tax payment evidence as audit-critical documentation. A payment made through an AAB, RCO, eTRA, direct crediting, or other channel may still require reconciliation if the corresponding data was not uploaded, was uploaded incorrectly, or was tagged by CRS as a discrepancy. Companies should also reconcile their own tax payment ledgers against BIR records, especially before tax clearance applications, tax audits, open case reviews, or assessments where proof of payment is material.

For taxpayers with high-volume filings, ONETT payments, government-related remittances, or large taxpayer transactions, RMO No. 8-2015 reinforces the importance of complete payment trails. When a collection is tagged as a duplicate item or discrepancy, the concerned RDO or LTS office may need to provide RAD with a list of valid collection transactions, such as capital gains tax, documentary stamp tax, registration fee, and other transactions, to enable necessary CRS adjustments.

How Ablola, Saribong & Gueco Can Help

Ablola, Saribong & Gueco assists businesses, CFOs, accountants, and in-house counsel in resolving BIR collection reconciliation issues, validating tax payment records, responding to BIR discrepancies, preparing documentary support for tax payments, and handling tax compliance concerns involving AAB payments, BIR Form 12.09 issues, eRORs, eTRAs, SAROs, direct crediting, and BIR collection records.

If your company is facing a BIR tax payment mismatch, collection discrepancy, tax clearance issue, open case concern, or audit problem involving unreflected payments, our Makati-based tax and business law team can help review the records, identify the proper supporting documents, and coordinate a legally sound compliance strategy. Visit MakatiLawFirm.com to consult Ablola, Saribong & Gueco on BIR compliance and tax collection reconciliation concerns.


Leave a Comment

Your email address will not be published. Required fields are marked *