01
The dilemma
The group had grown by opening stores, and every new store had quietly brought its own accounting with it. Each location kept its own spreadsheets, its own numbering, its own interpretation of how a sale should be recorded. The group had revenue but no consolidated financial picture it could trust.
What was breaking
- Every store was an accounting island. Disparate spreadsheets per location, with no common chart of accounts and no shared discipline about what got recorded where.
- Month-end took more than ten days. Finance spent the first third of every month collecting files, chasing missing numbers and merging them by hand, work that produced a report, not an insight.
- GST was tracked independently per state. Each location handled its own filings manually. Different people, different interpretations, one shared compliance exposure.
- Inventory valuation would not reconcile. Stock figures and sales figures were maintained in different places, so closing stock never cleanly matched cost of goods sold.
- Online and offline lived in separate worlds. The e-commerce channel was reconciled separately again, with gateway settlements matched to invoices by hand.
The cost of standing still
Ten days of every month bought the group a backwards-looking number they could not fully rely on. Pricing, purchasing and store-level decisions were being made on instinct because the data arrived too late to be useful, and every additional store made the problem arithmetically worse.
02
The idea
The group expected to be sold a full ERP. We recommended something smaller and considerably more effective: keep one accounting organization and use native multi-location capability, so each store and each sales channel becomes a Location inside a single set of books rather than a separate company file. Consolidation then stops being a monthly exercise, because the data is never separated in the first place.
The principles we worked to
- One organization, many locations. Each store and the e-commerce channel became a distinct Location inside one books organization, with a shared chart of accounts.
- Tax treatment derived from location, not memory. GSTIN and tax rules applied automatically based on where the transaction happened.
- Inventory as the source of truth for valuation. Stock movement, COGS and warehouse valuation synced directly rather than being re-keyed.
- Reconciliation automated at the settlement layer. Gateway payouts matched to individual invoices without human intervention.
What we ruled out, and why
| Option considered | Why we did not take it |
|---|---|
| A full ERP implementation | Ten to twenty times the cost and timeline for a problem that was fundamentally about structure, not capability. The group would have been running a change program instead of stores. |
| Separate books per store, consolidated later | Familiar and superficially tidy, but it preserves exactly the merge-at-month-end work we were trying to eliminate. |
| Keeping spreadsheets and adding a BI layer | Dashboards on top of unreliable inputs produce confident wrong answers faster. |
03
The build
The consolidation was delivered in five connected moves.
Location architecture
Every physical store and the e-commerce storefront was configured as a distinct Location within a single books organization. Transactions carry their location, so store-level reporting is a filter rather than a report-building exercise.
Automated GST treatment
Correct GSTIN and tax treatment apply automatically based on the transaction's location. Interstate and intrastate logic is handled by the system, removing the per-state manual interpretation that had been the group's largest compliance exposure.
Inventory and COGS synchronization
Stock movement, cost of goods sold and warehouse valuation sync directly from inventory into the ledger, so closing stock and sales reconcile by construction instead of by argument.
Payment gateway reconciliation
Settlements from the online channel are matched automatically to the individual invoices they cover, ending the manual tie-out that used to consume the online side of every close.
Store-level reporting
Real-time profit and loss per store, comparable across the group, available without a finance request.
04
The impact
| Measure | Before | After |
|---|---|---|
| Month-end close | 10+ days | 1 day |
| Accounting structure | One spreadsheet set per store | One organization, location-tagged |
| GST accuracy | Manual, per state, variable | 100% branch-wise, applied automatically |
| Inventory valuation | Did not reconcile to sales | Synced from inventory, reconciles by construction |
| Online settlements | Matched to invoices by hand | Reconciled automatically |
| Store P&L | Not separately available | Real-time, store by store |
| Opening a new store | New spreadsheet set, new island | New Location, live on day one |
Beyond the numbers
- Nine working days returned to finance, every month. The team moved from assembling numbers to interpreting them.
- Compliance exposure closed. Branch-wise GST stopped depending on which person prepared which filing.
- Expansion stopped adding overhead. Each new store is a configuration change, not another island to consolidate.
05
What comes next
The engagement continues. These are the next moves on the table.
- Store-level budgeting and variance reporting against the consolidated plan.
- Purchase planning driven by location-wise stock velocity.
- Extending the same location model to franchise or partner-operated outlets.
Engagement delivered by the Ideentrix founding team. Technologies, scope and outcomes as recorded at project close, published with the client's consent.
