An enforced office access boundary is a genuinely different, more complex feature than standard multi-office administration: instead of tagging members and clients by branch for reporting, it would restrict what a person can see based on which office they belong to. Most multi-branch firms don't need this because they cross-staff routinely. The firms that do need it are the small minority running their offices as functionally separate practices with no shared staff or clients.
The test: do the offices actually share anything?
The honest way to tell which version a firm needs is to ask whether its offices currently share staff, share clients, or report up to a common set of partners who review work across branches. If the answer is yes to any of those, an enforced boundary would restrict the firm's own partners and seniors from doing what they already do. If the answer is genuinely no across the board, the firm may be running what amounts to two or three separate firms sharing a name and back office — and that's a real case for a harder boundary.
| Standard multi-office administration | Enforced office access boundary |
|---|---|
| Office is a label on members and clients | Office is a gate on what can be seen |
| Cross-office staffing works exactly as before | Cross-office staffing requires an explicit exception or doesn't work at all |
| One set of roles and permissions, same as a single-office firm | A second permission dimension layered on top of role |
| Fits firms that staff across branches | Fits firms that genuinely never do |
Why this is a bigger ask than it sounds
- Every exception to the boundary (a shared quality-review partner, a firm-wide EQCR pool) needs its own override mechanism
- Firm-wide reporting across offices becomes harder to reconcile, since the boundary that protects data also blocks the rollup
- Partners who occasionally do cross over need a documented, auditable reason, not a quiet workaround
- The firm has to maintain this as a second access model indefinitely, not configure it once and move on
A firm that asks for an enforced boundary because of one sensitive client, rather than because its offices are structurally separate, is usually better served by engagement-level access controls on that one client — not a firm-wide second permission system that affects every other engagement too.
Common practice, not a requirement
Firms that do run genuinely separate practices under one brand tend to already manage this informally — separate email domains, separate billing, partners who've never worked a file together. If that's not already true, the firm's branches aren't separate enough to need the enforced version.
How we think about this
Lekhya's multi-office administration deliberately stays on the organisational side of this line. Office tagging never restricts access; role and engagement membership do that, exactly as in a single-office firm. Building a genuinely enforced boundary would be a different, larger feature aimed at a different kind of firm, and isn't something the current scope attempts.
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.
- Audit workflow & automationMulti-partner firm technology decisions: who needs to be in the roomA managing partner, an audit partner, and a quality-control partner are evaluating three different things when they look at the same software. Here's what each one actually cares about.
- 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.
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.