RMO No. 6-2017 requires automatic use of preprocessed RELIEF and BOC data in eLA-covered BIR audits, raising third-party matching risks.

Taxpayers under a BIR electronic Letter of Authority should expect investigating offices to automatically receive and use third-party sales, purchases, and importation data in the audit. RMO No. 6-2017 removes the need for investigating offices to separately request access to preprocessed RELIEF and Bureau of Customs data for cases already covered by eLAs, making third-party matching a built-in part of tax audit procedures effective immediately.

What Changed Under RMO No. 6-2017

RMO No. 6-2017 revised the guidelines and procedures for the extraction, dissemination, and reporting of utilization of preprocessed Third Party Information, particularly preprocessed RELIEF data and preprocessed Bureau of Customs importation data. The key change is operational but highly important for taxpayers: for cases covered by electronic Letters of Authority, investigating offices no longer need to request access to preprocessed RELIEF and BOC data.

Preprocessed RELIEF data refers to historical Summary List of Purchases and Summary List of Sales data matched with taxpayer registration information. Preprocessed BOC data refers to importation details showing individual transactions enhanced through registration information matching. These are raw data prior to the generation of Letter Notices, but under RMO No. 6-2017 they are expressly intended for audit and enforcement purposes.

Before this revision, access to preprocessed RELIEF and BOC data was governed by earlier rules under RMO No. 30-2003 and RMO No. 34-2004, with access generally covered by a request form approved by the concerned Regional Director, Assistant Commissioner, or Deputy Commissioner. RMO No. 6-2017 changes the workflow for eLA-covered cases by making the extraction and deployment of data proactive through the BIR’s internal systems.

Why This Matters to Businesses Under Audit

The practical effect is that a BIR audit covered by an eLA may already include third-party data showing what customers reported as purchases from the taxpayer, what suppliers reported as sales to the taxpayer, and what importation data appears in BOC records. This affects how BIR examiners can verify sales, purchases, VAT declarations, importations, and possible discrepancies in tax returns.

For corporate taxpayers, VAT-registered businesses, importers, and companies with significant supplier or customer transactions, RMO No. 6-2017 means that the BIR audit file may contain independent third-party information even before the taxpayer submits explanations or reconciliations. A mismatch between a taxpayer’s books and the RELIEF or BOC data may lead to audit findings unless properly reconciled and documented.

Searches such as RMO No. 6-2017 third party information, BIR preprocessed RELIEF data, BOC importation data in tax audit, eLA BIR audit third party matching, and Summary List of Sales purchases audit are therefore directly relevant for CFOs, accountants, tax managers, and in-house counsel preparing for BIR examinations.

Who Is Most Affected

The order directly governs BIR internal offices, including investigating offices, the Business Intelligence Division, the Audit Information, Tax Exemption and Incentives Division, Revenue District Offices, Large Taxpayers Service audit divisions, Enforcement and Advocacy Service audit divisions, VAT Audit Sections, Assessment Divisions, and reviewing offices in the National Office.

For taxpayers, the most affected are businesses already subject to electronic Letters of Authority. These include taxpayers under audit by Revenue District Offices, large taxpayers being examined by LTS audit divisions, VAT taxpayers subject to VATAS review, and importers whose BOC data may be matched against tax declarations.

SMEs are affected when they are issued eLAs and have transactions appearing in the Summary List of Purchases or Summary List of Sales of other taxpayers. Large corporations are especially affected because their volume of customer, supplier, and importation transactions increases the likelihood of third-party data comparisons. Importers must pay close attention because the BOC data component may show transaction-level importation details matched with registration information.

Key Compliance Requirements and Timelines Inside the BIR Process

RMO No. 6-2017 sets specific internal timelines for the processing and deployment of preprocessed data. The Business Intelligence Division of the Information Systems Group must access eLAMS every Tuesday to determine the list of electronic Letters of Authority issued by each investigating office.

On the following day, the BID must access the Data Warehouse to extract RELIEF data on Summary List of Sales and Summary List of Purchases, as well as BOC importation data, pertaining to taxpayers with issued eLAs for the covered taxable period.

The BID must transmit the preprocessed RELIEF and BOC data to the Audit Information, Tax Exemption and Incentives Division within three days from extraction. The AITEID must then classify the data per investigating office within three days from receipt. After classification, AITEID deploys the data by email or, where email facility is not available, by registered mail to the Revenue District Officer or chiefs of concerned offices, including the Assessment Division of regional offices and reviewing offices in the National Office.

Recipients of data sent by email must acknowledge receipt of the email transmission. This acknowledgment requirement helps create an audit trail within the BIR for the distribution and use of preprocessed third-party information.

How Revenue Officers Must Use the Data

The Revenue Officer assigned to the investigation must utilize the preprocessed RELIEF and BOC data in the audit. The utilization must be fully disclosed in the Revenue Officer’s narrative memorandum, and its effect must be presented in the audit report using the applicable BIR Form No. 0500 Series.

If the preprocessed data is not included in the audit findings for valid reasons, the Revenue Officer must explain the reason in the memorandum report and present the explanation as a footnote on Form 0500. This means non-use of the data is not treated casually; it must be justified in the audit papers.

Group Supervisors, Revenue District Officers, Division Chiefs of audit divisions under the Large Taxpayers Service and Enforcement and Advocacy Service, Chiefs of VAT Audit Sections, and chiefs of reviewing offices are required to monitor and review the utilization of the data per case. Reviewing offices must verify either the inclusion of findings from the data or the justification for non-utilization.

Quarterly Reporting and Data Tracking

RMO No. 6-2017 requires a Quarterly Status Report on Preprocessed RELIEF/BOC Data Utilization to be submitted to AITEID by the concerned head of investigating offices and Chiefs of VATAS. This report is covered by Annex A of the order.

AITEID must also maintain a separate record per investigating office of all deployed preprocessed RELIEF and BOC data. The required record includes the control number, eLA number, name and Taxpayer Identification Number of the taxpayer, taxable period covered, date of release of data, total amount of sales of the taxpayer as reported by buyers, total amount of purchases as reported by suppliers, and total amount of importations.

For taxpayers, these details identify the specific categories that may surface during a BIR audit. Businesses should therefore maintain reconciliations not only for their own books and tax returns, but also for customer-reported purchases, supplier-reported sales, and import records.

Penalties and Confidentiality Rules

RMO No. 6-2017 expressly provides that non-submission of the Quarterly Status Report is a ground for the imposition of administrative sanction against the responsible revenue officer. This penalty is internal to the BIR, but it underscores that the use and reporting of preprocessed third-party data is mandatory within the audit process.

The order also imposes confidentiality obligations on revenue officials and employees who have access to the system or knowledge of deployed preprocessed RELIEF and BOC data. They must use the data exclusively for official internal revenue tax purposes and treat it as strictly confidential. Any unauthorized divulgence, unless authorized by law, is a ground for administrative sanctions and the filing of appropriate charges against the erring official or employee.

Practical Steps for Taxpayers and Accounting Teams

Businesses with pending or expected BIR audits should prepare for third-party data matching as a normal part of the examination. The accounting team should reconcile declared sales against customer-reported purchases, declared purchases against supplier-reported sales, and importation records against BOC data and tax returns.

VAT taxpayers should pay particular attention to Summary List of Sales and Summary List of Purchases submissions. Any differences caused by timing, encoding errors, cancelled transactions, credit memos, returns, discounts, import entry classification, or supplier/customer reporting mistakes should be documented before the BIR raises them as audit findings.

Importers should ensure that import entries, customs documentation, VAT and duties records, inventory receiving reports, and accounting books are consistent. If BOC importation data shows transactions not reflected in the books or tax returns, the taxpayer should be ready with documentary explanations.

Corporate officers and in-house counsel should also review the scope of the eLA, the taxable period covered, and the audit findings in the narrative memorandum and Form 0500. Since RMO No. 6-2017 requires Revenue Officers to disclose utilization of the data or explain non-utilization, taxpayers may expect third-party matching issues to appear in the audit trail.

How Ablola, Saribong & Gueco Can Help

RMO No. 6-2017 makes third-party information a more systematic part of BIR audits involving eLAs. For businesses, the risk is not merely that the BIR has more data; it is that discrepancies from RELIEF and BOC sources may be converted into audit findings unless properly explained, reconciled, and supported by records.

Ablola, Saribong & Gueco assists businesses, CFOs, accountants, importers, and in-house legal teams in responding to BIR audits, reconciling third-party data, preparing position papers, reviewing Letters of Authority, and managing tax assessment disputes. For assistance with BIR audit compliance, RELIEF and BOC data discrepancies, VAT assessments, or tax controversy strategy, visit MakatiLawFirm.com.


Leave a Comment

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