India GST Reverse Charge (RCM) and Self-Invoice Rules

The India GST reverse charge mechanism changes who pays the tax, but it does not automatically answer every document question that follows. In notified section 9(3) cases, and only in limited section 9(4) situations involving purchases from unregistered suppliers, the recipient pays GST instead of the supplier. A self-invoice becomes relevant when the registered recipient is the person required to issue the invoice under section 31(3)(f). From November 1, 2024, Rule 47A requires that a recipient-issued invoice be raised within 30 days of receiving the goods or services. The tax under RCM is paid in cash first, and the input tax credit claim comes afterward if the normal ITC conditions are met.

That distinction matters because finance teams often collapse three separate questions into one:

1. Does this purchase fall under reverse charge at all?
2. If it does, do we also need a self-invoice?
3. What is the payment, reporting, and control sequence after that?

Those questions do not always have the same answer. A transaction can trigger reverse charge without fitting the oversimplified idea that "every RCM purchase needs the same paperwork." The safer workflow is to identify the legal trigger first, then decide whether your team must issue a recipient-side document, then work through payment and ITC in the right order.

That is why Rule 47A matters operationally, not just legally. Once the self-invoice sits behind a 30-day deadline, reverse charge stops being a month-end clean-up issue. It becomes an AP control issue tied to receipt dates, supplier status, and document routing. If your team waits until return preparation to think about reverse charge invoice requirements in India, the document deadline may already be missed even if the tax liability is eventually spotted.

The rest of this guide follows that workflow on purpose. First, decide whether section 9(3) or section 9(4) is actually in play. Then determine when the self-invoice and payment voucher are required. Finally, fit the RCM payment, reporting, and ITC sequence into a repeatable accounts payable process.

Section 9(3) vs Section 9(4): Which Purchases Trigger RCM

In day-to-day processing, the first mistake is asking for the document before you test the tax trigger. Under a normal forward-charge invoice, the supplier charges GST and pays it. Under reverse charge, the supplier may still issue an invoice for the underlying supply, but the tax liability shifts to the recipient. That shift happens only when the law and notifications put the transaction into an RCM bucket.

For most finance teams, section 9(3) is the starting point. It covers notified categories of goods or services where the recipient is made liable by notification. Common examples finance teams watch closely include legal services, Goods Transport Agency services, and some security-service scenarios. The exact recipient conditions still matter, so the safer practice is to read the current notification entry, not just the service label on the bill. A vendor description that says "transport" or "professional services" is not enough on its own.

Section 9(4) is a different question. It is about supplies received from an unregistered supplier, but it should not be treated as a blanket rule for every unregistered purchase. The current legal framework is notification-driven and limited, which is why many practical guides now describe section 9(4) as applying only in specified situations rather than to every transaction from an unregistered supplier. That is the point at which many teams go wrong: they see "unregistered supplier" and jump straight to self-invoicing without first checking whether the recipient class and supply actually fall into an active reverse-charge entry.

This is why section 9(3) vs 9(4) GST analysis belongs at the start of your AP workflow:

• Section 9(3): Ask whether the supply itself is in a notified reverse-charge category.
• Section 9(4): Ask whether the purchase from an unregistered supplier falls into a currently notified, limited case for the recipient class involved.
• Both sections: Ask what evidence you need to support the decision, including supplier registration status, service classification, and the relevant notification language.

A legal-services invoice is a good example. The supplier may issue an invoice for the service, but your team still needs to test whether the recipient bears GST under the relevant reverse-charge entry. The same logic applies when reviewing reverse charge on legal services GST or reverse charge GTA services India queries: the supplier document alone does not settle the tax treatment. Your team needs a classification step before it has a documentation step.

That classification step is also where ERP and vendor-master controls matter. If legal services, GTA charges, and other known RCM categories are tagged only at month-end, the AP team has already lost time it may need later for self-invoice timing, payment voucher issuance, and return reporting.

When a Self-Invoice Is Required and What Rule 47A Changed

After you identify a reverse-charge purchase, the next question is narrower: does this transaction also require the recipient to issue a self-invoice? That is where many articles blur the line between tax liability and document liability. They are related, but they are not interchangeable.

The practical rule is this: do not assume the supplier's invoice answers the recipient's compliance burden. In cases where the registered recipient is required to issue the invoice under section 31(3)(f), the self-invoice becomes part of the compliance file. That is why the document question has to be asked separately after the section 9(3) or 9(4) trigger is tested.

The major workflow change arrived on November 1, 2024. The GST Council notification inserting Rule 47A's 30-day self-invoice deadline states that a registered person liable to issue a self-invoice under sections 9(3) or 9(4) must issue that invoice within 30 days from the date of receipt of the supply. That change matters because many teams historically treated the self-invoice as something that could be cleaned up near return filing. After Rule 47A, the document has its own clear time discipline.

In practice, that means your AP team should capture three dates early:

• the date the goods or services were received
• the date the transaction was identified as reverse charge
• the date the self-invoice was actually issued

If those dates are not visible in your process, the 30-day clock is hard to manage.

Whether your team tracks that through an ERP workflow, an internal tax checklist, or an ICAI-style working paper, the receipt date needs to be captured as structured data rather than left inside email history.

It also helps to separate reverse-charge self-invoicing from India's e-invoicing regime. A self-invoice under RCM is not the same workflow as generating an IRN through the IRP. If your team mixes those concepts, review how India's IRN and IRP e-invoicing workflow differs from reverse-charge self-invoicing before you design the control. One is a recipient-side document requirement under the reverse-charge rules. The other is part of India's electronic invoice reporting system for specified taxpayers and document types.

So the operational test is straightforward:

1. Confirm whether reverse charge applies.
2. Confirm whether the recipient must issue the self-invoice for that fact pattern.
3. Start the 30-day Rule 47A clock from the date of receipt.

That sequence is the clearest way to handle India GST RCM self-invoice questions without over-documenting transactions that do not need it or under-documenting the ones that do.

What the Self-Invoice Must Contain and When to Issue a Payment Voucher

Once your team knows a self-invoice is required, the next task is to make it usable, traceable, and audit-ready. The safest approach is to treat the recipient-issued document as a controlled tax record, not as a makeshift memo created after the fact.

Your template should align with the prescribed invoice-particular framework under GST, especially the invoice-detail expectations commonly mapped back to Rule 46, including the information needed to identify the transaction, the parties, the taxable value, and the tax treatment. In practical terms, most teams want a self-invoice to show at least:

• a unique internal serial number
• the date of issue
• the supplier identity and its registration status
• the recipient's GST registration details
• a clear description of the goods or services received
• the taxable value and GST breakup
• a statement that the transaction is being treated under reverse charge
• a reference back to the supplier bill, contract, PO, or other supporting record

That numbering discipline matters. A self-invoice should be distinguishable from vendor invoices in your ERP and document archive. If both types share the same numbering logic, AP teams struggle to trace which document was supplier-issued and which one was recipient-issued under section 31(3)(f). A separate prefix or numbering series usually makes the audit trail easier to defend.

The second document many teams miss is the payment voucher. Section 31(3)(g) requires a registered person liable under reverse charge to issue a payment voucher at the time of making payment to the supplier. So the payment voucher reverse charge GST requirement is not a duplicate of the self-invoice. The self-invoice records the recipient-side invoice obligation. The payment voucher records the payment event.

It helps to keep the four documents distinct:

• Supplier invoice: the supplier's commercial bill for the goods or services
• Self-invoice: the recipient-issued tax document required in the relevant reverse-charge case
• Payment voucher: the recipient-issued document created when payment is made to the supplier
• Debit note: an adjustment document, not a substitute for a self-invoice

If your team tends to blend those records together, it is worth reviewing how debit notes differ from self-invoices and other tax documents so the wrong form is not used to patch a missing RCM document.

The best control is a checklist tied to the transaction, not a free-text note in someone's inbox. If the AP reviewer can confirm trigger, receipt date, self-invoice number, and payment-voucher status in one place, reverse charge invoice requirements in India become much easier to manage consistently.

How RCM Payment, GSTR-3B Reporting, ITC, and Registration Fit Together

Reverse charge does not end once the document is created. The finance consequence is that GST must usually be paid in cash first, after which the business can evaluate and claim input tax credit if the normal ITC conditions are satisfied. That sequence is what makes RCM a cash-flow and control issue, not just a paperwork issue.

At a high level, the workflow looks like this:

1. identify the reverse-charge transaction
2. issue the required self-invoice and payment voucher where applicable
3. discharge the GST liability
4. report the liability in the return
5. claim ITC afterward if the credit is otherwise available

That order matters because RCM ITC claim GST India questions often get reduced to "Can I take credit?" The better question is "Have I completed the steps that make the credit supportable?" If the tax is not discharged properly, or the underlying documentation is weak, the later ITC position becomes harder to defend.

For return reporting, finance teams commonly track reverse-charge liability in the reverse-charge line of GSTR-3B Table 3.1(d). The precise reporting treatment should still be checked against your current return process, but the main operational point is that the tax liability, the cash payment, and the later ITC logic need to reconcile to the same transaction record.

Registration is another area where shortcuts create risk. Section 24 of the CGST Act includes persons required to pay tax under reverse charge among the categories that must register. That means a business asking whether GST registration required for reverse charge can be ignored below the usual threshold is asking the wrong question. If your facts put you into an RCM obligation, you need to test the compulsory-registration rules promptly rather than relying on the ordinary turnover threshold alone.

At the same time, the exact result still depends on the nature of the transaction and the current notification landscape, especially in the narrower section 9(4) area. So the right operational message is not "everyone below the threshold must register because of any unregistered purchase." It is "if reverse charge liability actually applies to you, registration consequences may follow and should be checked immediately."

This is why AP and tax teams should reconcile four things together:

• the legal trigger for reverse charge
• the supporting document set
• the cash payment of the tax
• the later ITC claim

If those pieces live in separate spreadsheets or separate teams, errors show up late. If they stay attached to the same transaction file, the compliance story is much cleaner.

A Practical AP Workflow for Reverse-Charge Purchases

The most useful way to handle RCM is to turn it into a repeatable AP decision process instead of leaving it to month-end memory. A workable control flow looks like this:

1. Flag likely RCM categories early. Tag vendors and spend types that regularly raise reverse-charge questions, such as legal services, transport, and other notification-driven categories.
2. Check the trigger. Decide whether the purchase falls under a section 9(3) notification or a limited section 9(4) situation. Do not use supplier status alone as the decision rule.
3. Check the document obligation. If the fact pattern requires a self-invoice, start the 30-day Rule 47A countdown from the date of receipt of goods or services.
4. Issue and link documents. Record the self-invoice number, attach the supplier bill, and create the payment voucher when payment is made.
5. Route the tax step. Make sure the reverse-charge liability is handed off for cash payment and return reporting, not left sitting as an AP-only note.
6. Retain support for ITC. Keep the tax-payment evidence and document trail tied to the same transaction so the later credit claim is defensible.

The common failure points are usually process failures, not conceptual failures. Teams know reverse charge exists, but they:

• review the transaction too late
• treat every unregistered-supplier purchase the same way
• forget the payment voucher
• miss the receipt date that starts the Rule 47A clock
• separate tax payment from the source documents that support the later ITC claim

Good controls do not have to be complicated. A vendor-master flag, an exception queue for known RCM categories, a separate numbering series for self-invoices, and a weekly review of open reverse-charge items can eliminate most deadline misses.

If the same transaction also involves physical movement of goods, remember that reverse charge is only one part of the compliance picture. You may still need to check transport-document obligations separately, including when the same goods movement also triggers India's e-way bill requirements.

For most teams, that is the real value of an RCM workflow: it converts a legal rule into a visible operational sequence. Once that sequence is built into AP review, the business is far less likely to miss a self-invoice deadline, misfile a payment voucher, or lose the evidence needed for the later credit position.