Client relationship ownership, in multi-office administration, means recording which branch office is the administrative point of contact for a client — the office that brought the client in, bills them, or is the first call if something needs attention. It is a label, set independently of engagement staffing, and it has no bearing on who can work on or see that client's engagement. A client tagged to the Chennai office can still have a Mumbai-based engagement team.
Two separate questions, often collapsed into one
In a multi-partner, multi-branch firm, "who owns this client" and "who's doing this client's audit" get asked by different people for different reasons, and the answers don't have to match. A partner in Pune might have originated and still manage the relationship with a manufacturing client whose factory, and therefore whose fieldwork, is in Chennai — staffed by the Chennai team for practical reasons, while the Pune partner remains the one the client calls.
| Question | What answers it |
|---|---|
| Which office does this client administratively belong to? | The client's office tag — set once, changed rarely |
| Who bills and manages the relationship? | Usually follows the office tag, but is a firm convention, not something the software enforces |
| Who is actually doing the audit work? | The engagement team and roles — set per engagement, independent of the client's office tag |
| Who can see this client's engagement file? | Role and engagement membership only — never the office tag, for the client or for any team member |
Why recording it is still worth doing
- A clean answer to "how many clients does each office carry" without needing to infer it from staffing records
- A record that survives engagement team changes — if next year's team is entirely different people, the relationship owner is still on file
- A basis for internal conversations about branch growth, workload, and fee allocation between offices
- A reference point when a client moves cities or a partner relocates, separate from re-staffing anything
Common practice, not a requirement
Firms often set the client's office tag to match wherever the relationship partner sits, then leave it alone even as the engagement team rotates year to year. The tag tracks the relationship, not the work.
Don't treat a client's office tag as a staffing instruction. Tagging a client to the Chennai office is not a statement about who should audit them, and changing the tag will not reassign or restrict the engagement team in any way.
How we think about this
Lekhya keeps relationship ownership and engagement access deliberately separate. A client's office tag is recorded for administration and reporting; it never determines, restricts, or implies anything about who can work on or see that client's engagement. That access is governed purely by role and engagement membership, as in a single-office firm.
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.
- Audit workflow & automationAudit firm succession and knowledge-transfer riskThe departing senior doesn't take a skill the firm can rehire for. They take the specific knowledge of why last year's unusual transaction wasn't actually a problem.
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.