Audit Apply Logo

Audit ApplyGuides

⚙️ Launch Toolkit
← Back to Guides

GSTN Introduces RCMDOM & RCMIMP (Section 9(3) / 9(4)): Complete Compliance Guide for CAs & CFOs

The Goods and Services Tax Network (GSTN) has introduced dedicated schema indicators—RCMDOM (Reverse Charge Mechanism Domestic) and RCMIMP (Reverse Charge Mechanism Import)—for the generation of e-invoices on self-supplies under reverse charge. With sandbox testing currently active, corporate finance teams, Chief Financial Officers (CFOs), and practicing Chartered Accountants (CAs) must restructure their ERP systems to ensure seamless e-invoice generation for unregistered-to-registered transactions and import of services.

1. Statutory Framework & Legal Background

The operationalization of RCMDOM and RCMIMP anchors on core provisions of the Central Goods and Services Tax (CGST) Act, 2017 and the Integrated Goods and Services Tax (IGST) Act, 2017:

Compliance & Penalty Consequences: Failure to generate mandatory e-invoices for RCM transactions via the designated Invoice Registration Portal (IRP) results in severe penalties under Section 122 of the CGST Act, 2017—amounting to ₹10,000 or an amount equivalent to the tax evaded, whichever is higher, per document. Furthermore, non-issuance of self-invoices directly jeopardizes the taxpayer's eligibility to claim Input Tax Credit (ITC) under Section 16(2), as matching with GSTR-2B will be impaired.

2. Scope of Expansion & Applicability Matrix

The introduction of RCMDOM and RCMIMP schema categories bridges a critical compliance gap where recipients were previously manual-logging self-invoices without standard electronic verification. The applicability matrix spans two distinct operational verticals:

As per current GSTN advisories, taxpayers crossing mandatory e-invoicing aggregate turnover thresholds must configure their enterprise billing software to route these specific self-invoice streams through the IRP.

3. Step-by-Step Operational & ERP Workflow

Integrating RCMDOM and RCMIMP into existing Enterprise Resource Planning (ERP) frameworks such as SAP, Oracle, or Tally requires a structured 4-step execution architecture:

  1. Transaction Tagging at PO Level: Configure purchase order (PO) and vendor master modules to automatically flag transactions involving unregistered vendors or foreign service providers as 'RCM Applicable'.
  2. Schema Mapping & JSON Generation: Update ERP middleware to map custom fields to the new GSTN e-invoice schema elements, explicitly populating the document type flags for RCMDOM (domestic un-reg/notified RCM) or RCMIMP (imports).
  3. IRP Authentication: Push the generated JSON payload to the Invoice Registration Portal (IRP) to secure a unique Invoice Reference Number (IRN) and digitally signed QR code.
  4. Auto-Populated GSTR-2B Reconciliation: Ensure that the self-invoice data successfully flows into GSTR-3B (Tables 3.1(d) for inward supplies liable to reverse charge) and matches with GSTR-2B for ITC claim validation.

4. Comparative Analysis: Previous Practice vs. New Mandate

Compliance Parameter Previous Practice New Mandate (RCMDOM & RCMIMP)
Invoice Generation Mechanism Manual generation of self-invoices internally within ERP without IRP reporting. Mandatory electronic generation via IRP with distinct RCMDOM/RCMIMP schema tags.
IRN & QR Code Validation Not applicable; self-invoices lacked cryptographic IRNs and QR validation. Mandatory IRN and signed QR code generation required for audit trail validation.
ITC Claim Verification Based entirely on internal book entries and manual GSTR-3B liability computation. System-validated matching via GSTR-2B with strict audit linkages.
Audit & Scrutiny Risk High vulnerability to departmental mismatch notices due to manual reporting gaps. Low risk; standardized electronic schema ensures transparent audit trails.

5. Action Plan Checklist for Finance & Audit Teams