Multi-office staffing across branches means a firm's Mumbai, Chennai, and Pune offices routinely share staff on engagements — a partner from one office signing off a client based in another, a senior travelling during peak season to help a stretched branch. An audit tool's multi-office feature has to support this by design: office tagging on a member or client is an organisational label, never a restriction on which engagements that member can be staffed on or see.
Why cross-staffing is the norm, not the exception
Multi-branch CA firms open a second or third office for reasons that have nothing to do with keeping each branch's work separate — proximity to a client cluster, a partner's home base, lower-cost talent in a smaller city. The staff pool behind those offices is one firm's pool, not three. During statutory audit season, firms move people where the work is: a Pune senior spending three weeks on a Mumbai-office client's inventory count, a Chennai partner being the EQCR reviewer on a Hyderabad-office bank audit.
- A partner practising across multiple branches as part of the same firm's governance structure
- A senior or EQCR reviewer drafted onto another office's engagement for a specific skill or sign-off requirement
- Peak-season staff pooling, where whoever is free gets staffed regardless of their home office
- A client that relocates its registered office from one city to another without changing its auditor
What a hard office boundary would actually do
A tool that enforces office as a second access-control layer on top of role and engagement membership would, in this normal pattern, lock out exactly the people a firm just staffed. The Pune senior assigned to a Mumbai-office client would need her own office reassigned, or the client's office tag changed, before she could open the file she was told to work on this week. Multiply that by every cross-staffed engagement in a season and the feature becomes a constant source of support tickets rather than a convenience.
| Changes with office tagging | Unaffected by office tagging |
|---|---|
| Which branch a member's profile is grouped under in reports | Which engagements that member can open and work on |
| Which office a client's relationship is recorded against | Who is staffed on that client's engagement |
| How a firm filters a staffing or client list by branch | Whether a cross-office reviewer can see the file they're reviewing |
Common practice, not a requirement
Firms that do run tight office boundaries internally (separate client bases, no shared staff) tend to already know it and ask for it explicitly — it's a deliberate governance choice, not something that falls out of normal multi-branch operation.
How we think about this
Lekhya's multi-office feature assigns an office to a member or a client purely for organisational and reporting purposes. Access to any specific engagement is determined entirely by role and engagement membership — the same rule that applies in a single-office firm. Office assignment never adds or removes what a person can see.
The practical test for a vendor's claim
Before adopting any tool's multi-office feature, staff a cross-office engagement the way the firm actually would, and watch what happens. If the cross-staffed person can open the file immediately with no office reassignment needed, the feature matches how the firm works. If they can't, the tool has quietly built the harder, access-boundary version of 'multi-office' — useful only to firms that genuinely don't cross-staff.
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.
Related resources
- Audit workflow & automationMulti-office administration: organising a firm by branch without rebuilding access controlA firm with three branches needs to know who sits where. It doesn't need a second, parallel access-control system to find that out.
- Internal audit & IFCTesting segregation of duties: a practical approachThe classic SoD conflicts, how to test for them in a small finance team where perfect separation is not realistic, and how to document the compensating controls that stand in.
- Technology, data & AI in auditMeasuring ROI of audit automation for a mid-size firm (10-30 staff)At 10-30 staff, the real ROI isn't hours saved on one file — it's whether a partner can review five engagements at once without five different working styles slowing every one of them down.
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.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.