Inter-store transfer format for restaurants — IST template + GST handling

About this piece. Inter-store transfers (IST) are the most under-documented operation in Indian multi-outlet restaurants. A bag of paneer moves from Outlet 2 to Outlet 5 because Outlet 5 ran short; nobody writes it down; the food cost % at Outlet 5 looks better than reality and at Outlet 2 looks worse. Multiply across 30 transfers a month and you cannot trust either outlet's P&L. This piece is the IST format, the GST treatment that applies (especially across GSTINs), and the audit trail that closes the loop.

What an IST is and is not

An inter-store transfer is the movement of inventory between two outlets of the same business — typically because one is short and another is long, or because the central kitchen ships to outlets daily.

It is not:

• A purchase (the goods were already yours)
• A sale (no money changed hands externally)
• An expense (the food cost shifts between outlets, not in/out of the business)

It is:

• A movement that needs to be recorded so each outlet's P&L is honest
• A potentially GST-relevant event when crossing GSTINs (i.e. across states or across registered branches)
• An audit trail that protects against shrinkage allegations

The 11-field IST format

A 12th optional field — reason for transfer (shortage, redistribution, central kitchen dispatch) — is helpful for monthly trend analysis.

The format itself

┌─────────────────────────────────────────────────────────────┐
│  INTER-STORE TRANSFER (IST)                                  │
│  [Brand name]                                                │
│                                                              │
│  IST No: __________            Date: ____   Time: ______     │
│                                                              │
│  FROM: ____________________  GSTIN: ____________________     │
│  TO:   ____________________  GSTIN: ____________________     │
│                                                              │
│  ┌──────────────────────────────────────────────────────┐    │
│  │ # │ Item / SKU      │ Qty │ Unit │ Rate │ Value │ GST│    │
│  ├──────────────────────────────────────────────────────┤    │
│  │ 1 │                 │     │      │      │       │    │    │
│  │ 2 │                 │     │      │      │       │    │    │
│  │ 3 │                 │     │      │      │       │    │    │
│  └──────────────────────────────────────────────────────┘    │
│                                                              │
│  Total value: ₹ ___________   Total GST: ₹ ___________       │
│                                                              │
│  Reason for transfer:                                        │
│  □ Shortage at destination  □ Excess at origin               │
│  □ Central kitchen dispatch □ Other: ______________          │
│                                                              │
│  Authorised by (origin):     Received by (destination):      │
│  Manager signature ________  Manager signature ____________  │
│                                                              │
│  Vehicle / mode of transport: __________  Time received: __  │
└─────────────────────────────────────────────────────────────┘

A4 portrait, three-up if used as a tear-pad. The IST is filled at the origin, signed by the origin manager, accompanies the goods, and is countersigned at the destination.

The GST treatment

Three scenarios, each with a different tax handling:

Scenario 1 — same GSTIN (typically same state, single registration)

Goods moving between two branches under the same GSTIN are not a supply under GST. No tax invoice is needed; an internal transfer document (the IST above) is sufficient. The CGST Act treats this as a stock movement, not a taxable event.

Scenario 2 — different GSTINs (typically different states)

Goods moving between branches under different GSTINs are a deemed supply under GST (Schedule I of the CGST Act). The origin outlet must:

• Raise a tax invoice to the destination outlet
• Charge IGST (since it crosses states) at the applicable rate for the goods
• Report it in GSTR-1 as a B2B invoice
• The destination outlet claims input tax credit in its GSTR-3B (subject to ITC restrictions under CGST §17(5) for blocked credits like food and beverage — restaurant-specific reading needed with your CA)

Scenario 3 — same state, different GSTINs (less common; some chains register separately)

Treated like Scenario 2 — deemed supply, tax invoice, IGST or CGST+SGST depending on state structure. Verify with your CA — this depends on registration architecture.

The IST format above accommodates all three; field 9 is left blank for Scenario 1 and filled for Scenarios 2 and 3.

A worked example

Scenario: Chain has 3 outlets in Bangalore (one GSTIN) and 1 in Chennai (separate GSTIN — different state).

Transfer 1: Outlet 2 (Bangalore) sends 5 kg paneer to Outlet 3 (Bangalore) at standard cost ₹350/kg.

• Same GSTIN. Internal IST only. No tax invoice. Total value ₹1,750. Field 9 blank.
• Outlet 2 P&L reduces COGS by ₹1,750; Outlet 3 P&L increases COGS by ₹1,750.

Transfer 2: Outlet 3 (Bangalore, GSTIN1) sends 10 kg basmati rice to Outlet 4 (Chennai, GSTIN2) at standard cost ₹120/kg. GST on rice is 5%.

• Different GSTINs across states. Tax invoice required. Total value ₹1,200. IGST ₹60.
• Outlet 3 raises invoice ₹1,260, reports in GSTR-1.
• Outlet 4 receives invoice, books as inward supply, claims ITC subject to applicable rules.

The IST document captures both transfers identically; the GST line drives whether a tax invoice is also required.

The audit trail

The IST stack at each outlet should yield three reconciliations every month:

1. Origin outlet IST register = sum of all outgoing transfers, by date, by destination
2. Destination outlet IST register = sum of all incoming transfers, by date, by origin
3. Cross-outlet match = origin outgoing should equal destination incoming, item by item

A mismatch is a flag. Three common causes:

• IST raised at origin, never received at destination (lost in transit, unrecorded)
• Goods received at destination, no IST raised (informal transfer, not documented)
• Quantity discrepancy (origin sent 10 kg, destination received 9 kg — the 1 kg is variance)

Monthly cross-outlet reconciliation should be part of the area manager's monthly deep-dive. Patterns of mismatch with one outlet point either to a process gap or to leakage — both worth catching.

What happens without the IST discipline

Three measurable consequences:

1. Outlet P&L distortion. Outlets that frequently donate stock look worse than reality; outlets that receive look better. P&L benchmarking across outlets is meaningless.
2. Inventory variance unattributable. When the monthly stock count comes in short at Outlet 3, you cannot tell whether it is shrinkage, over-portioning, or undocumented transfers out.
3. GST exposure. Cross-GSTIN transfers without tax invoices are a deemed-supply violation. The exposure surfaces during a GST audit and can be three years deep.

"We don't bother with IST docs for small things. The cook just sends two kg of dal across and we move on." — common, and the source of the year-end CA conversation that begins "we have a problem".

The discipline that makes IST run

Three operating disciplines:

1. No transfer without an IST. Even small transfers (1 kg, 2 packets). The discipline only works if it is binary.
2. Origin manager raises; destination manager receives. Never the same person on both ends. Two-signature rule.
3. Monthly reconciliation owned by the area manager. The area manager pulls all IST registers monthly, matches origin to destination, flags variances.

A tablet-based IST capture (in a chain ops tool or even a shared Google Sheet) speeds this up. Paper works too if discipline is strong.

When IST volume signals something else

If you find yourself doing 30+ transfers a month between three outlets, the underlying problem is usually not transport — it is forecasting. Transfers are reactive when ordering and consumption are not in sync. Two diagnoses:

1. One outlet is over-ordering (and donating). Tighten the ordering pattern; cut the par stock.
2. Vendor reliability is weak across the chain (and you are using transfers as a backup). Fix the vendor, not the transfer process.

A healthy chain runs 5-10 ISTs per month per outlet for genuine redistributions, plus the daily central-kitchen dispatch where applicable. Volumes meaningfully above that are a forecasting signal, not a transfer-process triumph.

Where this fits in the multi-outlet stack

• IST format — the document for each transfer (this piece)
• POS multi-outlet inventory — the system layer that should hold the running stock
• Multi-outlet management — the broader model (hub)
• Audit checklist — IST discipline is one of the 60 audit items

The IST is small in size and large in P&L impact. Get the format right and reconcilable, and your outlet-level financials become trustable.

Related on Restaurant Daily

• Multi-outlet restaurant management in India — what changes between 1 and 5
• Multi-location restaurant POS for India — 6 systems compared on consolidation, taxes, sync
• Franchise restaurant audit checklist — free 60-point template