A 4-branch education trust closed its books on the 3rd, not the 15th

The trust in one line

A 9 200-student education trust running 4 schools across 3 cities — two in one northern state capital, one in another, one in a central-Indian state capital. CBSE + state board mix. Trust HQ in one of the state capitals.

The before

Each of the four branches ran its own accounting in its own Tally instance. Once a month, the trust accountant collected the trial balances by email, attempted to consolidate, found discrepancies, fired emails back to each branch asking for explanations.

The pattern repeated, with a few variations:

• Period close happened on the 15th-20th of the following month, not in the first week.
• Inter-branch transactions (one branch fronting a payment for another, transferring fees collected from a sibling at branch A to a fee balance at branch B) routinely didn't reconcile. Two-week email threads.
• No standardised chart of accounts. Branch A's "Stationery — staff" was branch B's "Office supplies" was branch C's "General expenses". The consolidated P&L was useless.
• Two late nights of overtime for the trust accountant + each branch accountant every month.
• Auditor took 6 weeks for the annual audit (year before last). Most of that was reconciliation, not actual audit work.

What we changed

We migrated all 4 branches onto School Console's Finance & Accounts module over 14 weeks (one branch every 3-4 weeks, smallest first, largest last). Key elements:

One chart of accounts, four sub-organisations. Each branch is a sub-organisation under the trust tenant. Same account codes everywhere. Branch-level postings stay branch-scoped; trust-level rollup is a SUM not a manual aggregation.

Maker-checker on every voucher above ₹50,000. Bank vouchers, journal vouchers, contra entries. The accounts clerk makes; the branch accountant or trust accountant checks. Audit trail captured at submit + at approve.

Inter-branch settlement workflow. A pre-defined "Inter-Branch Loans/Settlements" account pair. Branch A pays for Branch B → automatic journal entry on both sides, both branches' books match on the day, not after a fight.

Period-close discipline. Last day of the month: auto-job freezes that period for non-admin users at 23:59. Trust accountant runs the four pre-close checks (no unposted vouchers, no draft journals, no reconciliation breaks, no period-overlap entries). Pass → close period → trial balance snapshot to FinReportSnapshot. Hand to auditor.

The after

The audit-time reduction was the one that surprised us — we'd planned for a 30-50% reduction; got 75-80%. The auditor explained why on a debrief: "I used to spend the first month re-doing your reconciliation before I could even start auditing. Now I see clean books on day one."

"I used to dread the first week of every month. Now I close before lunch on the third."
— Trust accountant

"We have meaningful month-on-month P&L comparisons for the first time. Before, every month's category totals meant something different."
— Trust board treasurer

What we'd do differently

Two things:

One: we did the smallest branch first to de-risk the migration. In hindsight, do the branch with the most experienced accountant first — they catch process issues during their migration that the smaller branches would have stumbled into. We had to retrofit a few inter-branch settlement patterns after branch 2 went live; doing them at branch 1 would have saved a week.

Two: the chart-of-accounts unification was painful and we tried to do it as part of branch 1's migration. Branch 1 accountant didn't have the trust-wide context. Standardise the chart of accounts as a separate exercise before any migration starts, and have the trust accountant own it.

Run a multi-branch trust struggling with consolidation? Talk to us — we've done this pattern four times now and have the playbook.