A place-of-supply workflow for domestic and cross-border services covering B2B/B2C rules, property, events, performance, intermediary, OIDAR and recipient evidence.
A customer GSTIN is not the place of supply for every service. The specific IGST Act rule must be selected before the tax type.
Sections 12 and 13 of the IGST Act contain separate place-of-supply rules depending on whether both parties are in India or either party is outside India.
For many domestic B2B services, the general rule points to the registered recipient’s location, but specific exceptions override it.
Immovable-property, event, performance, transportation, telecom, banking, intermediary and OIDAR services can have special rules.
Place of supply is different from the supplier’s location and the customer’s billing address.
| Check | What to examine |
|---|---|
| Parties | Legal supplier, recipient, GST registration and establishment. |
| Service | Actual deliverable, use and contractual recipient. |
| Rule | General rule or named exception. |
| Evidence | Property, event, performance, address, device or account records. |
| Tax type | IGST or CGST/SGST after supplier location is compared with place of supply. |
A Delhi consultant invoices a Karnataka company for an event physically held in Goa. The finance team selects Karnataka because the customer GSTIN is there. The event-specific rule must first be tested; the customer GSTIN does not automatically override the place linked to the event.
Create a place-of-supply decision tree by service line. The ERP should ask the factual question that drives the rule—property location, event location, recipient registration or performance location—not merely request a state code.
For cross-border services, separately test export or import conditions. A place outside India does not alone prove export if the recipient, payment or distinct-establishment condition fails.
Identify the GSTIN, tax period, transaction, document and exact statutory question. Review parties, service and rule together. Freeze the source data so that later ERP edits do not destroy the evidence used for the decision.
Start with the contract or commercial event. Move through the invoice, receipt or movement evidence, e-invoice or e-way bill, accounting entry, return and electronic ledger. Classify each difference as timing, error, ineligible amount, statutory exception, disputed position or completed correction. Avoid a plug entry whose only purpose is to make two reports equal.
Prepare a concise position note with facts, authority, amount, alternative view and approval. Preserve the filing acknowledgement and update the responsible master data, vendor rule, invoice workflow or monthly checklist. The objective is not only to survive one review but to prevent the same issue in the next period.
GST positions are strongest when the transaction, legal provision, invoice, physical or service evidence, books, return and electronic ledger agree. A portal match without commercial evidence is not a complete control.
Use the current official instrument, portal or regulator publication before acting. This panel separates the category authority from page-specific references.