Five shrines, one trust, one ledger: trust-board reporting from 6 weeks to 4 days.
How a Vaishnava trust managing 5 shrines across the Deccan plateau consolidated donations, sevas, accounting and 80G/10BD on a single federated temple management software.
The structural problem
The trust was founded in the 1940s and grew organically: a main shrine plus four satellite shrines added across the next four decades. By 2025, the operating structure looked like this:
| Shrine | Annual donations | Software in use | Accountant |
|---|---|---|---|
| Main shrine | ₹3.8 Cr | Custom Excel + Tally | Full-time, on-site |
| Sub-shrine A (urban) | ₹1.1 Cr | Different temple billing software | Full-time, on-site |
| Sub-shrine B (district town) | ₹0.8 Cr | Excel only | Part-time |
| Sub-shrine C (highway shrine) | ₹0.5 Cr | Paper receipt-book | Volunteer-only |
| Sub-shrine D (village) | ₹0.2 Cr | Paper receipt-book | Volunteer-only |
Five shrines. Four different recordkeeping systems. Eleven trustees scattered across four cities, none of whom could see consolidated numbers without 6 weeks of manual reconciliation every quarter. The trust's chartered accountant was effectively building the consolidated trial balance by hand from spreadsheets emailed in late.
The Form 10BD problem was worse: each shrine generated its own donation list, with different receipt-number formats, missing PANs, and no consistent classification of which donations qualified for 80G vs which were anonymous hundi cash. The trust's auditor had been asking for a unified system for two filing cycles.
The federated rollout
Most temple software is built for one shrine at a time. The trust needed a federated structure: each shrine operates locally, but consolidated views, accounting, 80G/10BD and trust-board reports roll up automatically.
Rollout sequence:
- Week 1-2 — Main shrine. Cutover from Excel + Tally. 4 years of donation history, 14,000-row devotee master, seva catalogue migrated. Tally integration kept live.
- Week 3-4 — Sub-shrine A. Migration from competitor temple billing software. CSV export plus Tally exports merged into 3ioSetu. Counter staff retrained.
- Week 5 — Sub-shrine B. Excel-only migration; volunteer admin trained on the shared cloud login.
- Week 6 — Sub-shrines C and D. Paper-receipt-book shrines onboarded with hand-held POS tablets the trust funded; receipt-number continuity preserved.
- Week 7 — Federation layer + first board pack. Trustees granted role-based access; consolidated dashboards live. First quarterly trust-board report generated automatically.
Results after one full quarter
consolidation time
vs prior quarter, paper-shrines now compliant
audit-traced gap, sub-shrines C+D, FY pre-deployment
consolidated, all 5 shrines, single quarterly filing
role-based, audit-logged
freed from manual consolidation
The non-obvious win: the sub-shrines
Most of the donation-leakage was at the two paper-receipt-book shrines (C + D). Volunteers had been doing their best, but with no systematic recording of named donors, no PAN capture, and quarterly cash-up that depended on memory, ~₹14L per year of donations were either uncounted or untraceable to a 80G receipt — effectively leaving the trust unable to claim its full position with the auditor.
Once those two shrines were on hand-held POS tablets running the same temple management software as the main shrine, every donation got a serial receipt, named or anonymous, and consolidated into the trust's quarterly filing.
What's running now
All 5 shrines run on 3ioSetu's federated temple management software. Donations flow through the integrated temple payment gateway with PAN-validated 80G receipts. The chairman's quarterly board pack is now a 1-click PDF export. The CA still does year-end audit; he no longer does monthly reconciliations — that disappeared.
Phase 2 (Q3 2026) adds donation kiosks at the main shrine for the trust's annual rath utsavam (chariot festival). Phase 3 (Q4) extends the architecture to two more sub-shrines the trust is in conversation to absorb from a sister Vaishnava lineage.
Multi-shrine trust? We have done this before.
If your trust runs more than one shrine, you have probably been wrestling with the same consolidation problem. Book a free demo — we'll show you exactly how the federation layer works, with your shrine structure on the screen.
Book a Free Demo →