GST / RCM

Reverse Charge Control

CA Nikhil Gupta·June 2026·3 min readGST / RCM

RCM liability sits in the expense ledger, so it is often missed when teams focus only on sales invoices.

Quick View

Decision

Run a monthly vendor and expense scan for notified supplies and import transactions.

First action

Build RCM vendor list.

Core evidence

Vendor master.

Main warning

Assuming unregistered vendor always means RCM.

Why It Matters

Reverse charge can arise under section 9(3), specified section 9(4) cases and the IGST import-of-services framework.

RCM tax is generally paid in cash; eligible ITC can be claimed separately after payment and satisfaction of conditions.

Self-invoice and payment-voucher requirements apply in specified cases where the supplier does not issue a GST tax invoice.

Control Framework

AreaWhat to establishOperating rule
TriggerNotified supply and recipient category.Maintain legal matrix.
TimePayment, invoice or statutory time-of-supply event.Age expenses.
DocumentSupplier invoice, self-invoice and voucher.Use prescribed form.
CreditBusiness use and blocked-credit review.Claim after payment.

Action Checklist

  1. Build RCM vendor list.
  2. Scan expense ledgers.
  3. Identify import services.
  4. Calculate time of supply.
  5. Pay through cash ledger.
  6. Claim eligible ITC with evidence.

Practical Example

A company pays legal fees to an advocate but books the invoice without RCM coding. Liability is discovered months later, creating interest even though ITC may ultimately be available.

Evidence to Keep

  • Vendor master.
  • Contract and invoice.
  • RCM legal matrix.
  • Self-invoice where required.
  • Payment voucher.
  • Cash and credit ledger entries.

Warning Signs

  • Assuming unregistered vendor always means RCM.
  • Paying through credit ledger.
  • Claiming ITC before liability payment.
  • No time-of-supply review.
  • Missing imports paid by card.

Detailed Review

GST control should connect five records: commercial contract, tax invoice, movement or service evidence, accounting entry and portal return. A filing that cannot be traced back to all five records is difficult to defend.

Every reconciliation should have a clear opening balance, current-period additions, corrections, reversals, payments and closing balance. Avoid unexplained plugs that make the total match but do not identify the invoice or legal reason.

Portal data is important but not conclusive by itself. GSTR-2B, e-invoice, e-way bill and ledger data should be read with the statute, rules, notifications, contracts and actual supply evidence.

Keep original source files and final filed versions. Screenshots help explain a portal event but should not replace downloaded returns, JSON, signed invoices, acknowledgements or bank records.

For material exposure, prepare a written position memo stating facts, issue, law, alternatives, conclusion, amount and approval. The memo should record uncertainty rather than hide it.

Expense-side GST controls should scan vendor master, general ledger and foreign payments before return filing. These liabilities may never appear in outward-supply systems.

Allocation across GST registrations should be supported by recipient use, legal mechanism, valuation and consistent accounting.

Escalation Route

Start with the GST portal record, responsible business owner and tax working. Where the issue is operational, correct the source system and retain the acknowledgement. Where it is legal or disputed, obtain a reasoned professional position before payment, reply, refund or appeal.

Track the statutory or portal deadline separately from internal approval. Preserve helpdesk tickets, ARN, hearing requests, orders and payment records so a later reviewer can reproduce the entire path.

Transaction Test

Before filing or replying, prepare a one-page issue sheet showing GSTIN, tax period, transaction type, amount, applicable provision, portal form, evidence owner and due date. This prevents different teams from solving different versions of the same problem.

Reconcile tax by CGST, SGST, IGST and cess rather than only by total. A total can match even when the wrong tax head, state or period has been used, which can still create interest, cash-flow and customer-credit consequences.

Build an exception register with five statuses: identified, evidence pending, vendor or customer action, tax treatment approved and closed. Every exception should retain its original amount even after correction so the audit trail remains visible.

Test the position against the counterparty’s records. Customer ITC, vendor GSTR-1, transporter data, marketplace statements and bank receipts can expose differences that are invisible in the taxpayer’s own ledger.

The final approval should record who reviewed the legal position and who approved the return, reply, payment, refund or appeal. Material GST decisions should not remain buried in informal email chains.

Create a recurring expense-code scan for legal fees, director services, freight, security, import services and other notified categories. Update the matrix whenever a notification or business model changes.

For group allocations, document the recipient GSTIN, benefit received, allocation basis and invoice or ISD document before credit is distributed.

Frequently Asked Questions

Is every purchase from an unregistered vendor under RCM? â–¼
No. Only notified situations and specified categories apply.
Can RCM be paid with ITC? â–¼
RCM output liability is generally paid in cash.
Can the tax become ITC? â–¼
Eligible credit may be claimed after payment and other conditions.
Why scan expense ledgers? â–¼
RCM is frequently absent from sales and purchase-tax workflows.