Skip to content
Finance & Law Explained in 2 Minutes

Inter-State vs intra-State nature of supply

Reviewed 2026-07-19Robots: index,followOfficial law prevails

Workflow in 2 Minutes

Fix supplier location, place of supply, special deeming rules and territorial-water treatment before choosing the tax head.

Decision sequence

  • Freeze the relevant date and legal entity/registration.
  • Classify the supply, product, service, machine or process.
  • Apply the parent Act and exact special rule before the general rule.
  • Map rate/exemption/RCM/ECO/cess and connected form.
  • Reconcile books, customs/production/location evidence and portal data.
  • Prepare exception log, reviewer sign-off and litigation note.

Worked control example

The finance team fixes the relevant date, opens the official provision and connected instrument, applies the legal conditions to the transaction documents, and records the conclusion in a reviewed position note.

Evidence pack

  • Executed contract / purchase order
  • Invoice and tax head
  • GSTIN and location evidence
  • Shipping/customs/SEZ or machine records
  • Rate/notification and computation sheet
  • Returns, challans and acknowledgements
  • Review note and source archive

Practical Q&A

What is the first control?

Fix the transaction, manufacture or import date and identify the legally relevant locations, product/service classification and liable person.

What is the minimum evidence file?

Act/Rule/notification sources, contract and invoice, location or production evidence, calculation, return/form acknowledgement and reviewer approval.

Can a portal result determine the law?

No. Portal treatment is operational evidence; the Act, Rules, notifications and binding judgments govern.

OPERATING CONTROL

Finin2min practical control layer

Law vs system

This transaction workflow must be reconciled to the Act, Rules and notified forms. Portal behaviour or an advisory can explain implementation but cannot override a statutory provision or Gazette instrument.

Evidence pack

Retain source records relevant to the step: acknowledgement/reference number, submitted JSON/PDF, ledgers, invoice/e-invoice/e-way-bill records, notices/orders, screenshots only where needed, and system/error tickets.

Reconciliation

Cross-check the portal result with books/ERP, return period, GSTIN, document identifiers, tax head, tax amount and downstream return/ledger effect.

Exception workflow

  1. Identify the legal deadline or condition independently of the portal display.
  2. Reconcile master data and transaction values before submission.
  3. Save acknowledgement and the exact filed/generated artefact.
  4. Investigate any mismatch, rejected record, blocked action or missing auto-population; do not overwrite the audit trail.
  5. Escalate through the official grievance/help route where the system prevents a legally required action and preserve evidence of the attempt.