We use cookies to understand which pages and tools are useful, nothing more — no ad tracking across other sites. You can change this later from the footer.

Skip to content
Lekhya.in

Guide4 min readPublished

Multi-office administration: organising a firm by branch without rebuilding access control

Why most multi-branch CA firms need offices as an organisational grouping for members and clients, not a second permission boundary layered on top of engagement roles — and how to tell a vendor is conflating the two.

Multi-office administration, in an audit tool, means a firm can group its members and its clients by branch — Mumbai, Chennai, Pune — so a report, a staffing view, or a client list can be filtered by office. It is an organisational label, not a second access-control boundary. Whether someone can see a specific engagement is still governed by their role on that engagement, exactly as it is for a single-office firm; office assignment answers 'which branch is this person part of', not 'what can they see'.

The two different problems that get conflated

'Multi-office' gets used by vendors to mean two genuinely different things, and conflating them produces either a feature that's weaker than a firm needs or a feature that's far more complex than the firm asked for.

Two different things called 'multi-office'
Organisational groupingA second access boundary
Tags members and clients with the branch they belong to, for reporting and administrationRestricts what a Mumbai-office member can see to only Mumbai-office engagements
Access is still governed entirely by role and engagement membershipAccess depends on both role AND office, which is a materially larger permission model
What most firms that describe themselves as 'multi-office' actually needWhat a firm needs only if offices are run as genuinely separate practices with no cross-staffing
Two different things called 'multi-office'

Common practice, not a requirement

Most Indian CA firms with multiple offices staff engagements across offices routinely — a Chennai partner reviewing a Mumbai-office client's file, a senior moving between branches during the season. A tool that enforces office as a hard access boundary gets in the way of exactly that normal practice, unless the firm genuinely runs each office as a walled-off unit.

What organisational grouping actually buys a firm

  1. 01A reportable structureWhich office is carrying how many engagements, which office's staff utilisation is tightest during the season — questions a partner actually asks, answerable by filtering on office without needing a second access system underneath it.
  2. 02Clean onboarding per branchA new office opening can be staffed and tagged without touching how any existing engagement's team or roles are configured.
  3. 03A client's 'home' office recorded, not enforcedKnowing which office owns the relationship with a client is useful administratively even when staff from other offices work on that client's engagements.

When a firm genuinely does need the harder version

A firm that operates its branches as functionally separate practices — different partners with no overlapping client base, no cross-staffing, each branch effectively running its own book — has a real case for office as an enforced access boundary. That's a materially different, more complex system than most firms asking for 'multi-office' actually need, and it's worth being explicit with a vendor about which one is actually being requested, since building the wrong one either under-delivers or costs more than the firm's actual structure calls for.

If a vendor's multi-office feature silently becomes an access boundary — a member assigned to an office suddenly can't see an engagement they were previously staffed on — that is a breaking change to how the firm's people work, not a neutral administrative feature. Ask explicitly, before adopting it, which of the two models above a tool actually implements.

How we think about this

Lekhya's multi-office administration is deliberately the organisational-grouping version: an office tags members and clients for reporting and administration, and every access decision is still made purely on role and engagement membership, exactly as it would be for a firm with one office. That scope decision is explicit, not a limitation discovered later.

This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.

Free tools, no signup

Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.