Multi-branch practice
Multi-Branch Practice Management: All Your Offices in One Software
A worked example: forty offices across India, five in the UAE and five in Singapore. Pick a question and watch the same fifty offices regroup to answer it.
Each square is one office. All fifty stay on screen the whole time — they only regroup. Nothing is added, nothing disappears.
Fifty offices, one practice. Every office raises its own work, bills its own clients and keeps its own staff — and all fifty live in one MyTask account, sharing one client list and one service tree.
Most practices never reach the last two steps. Every office in one country on one financial year, so every figure is a single number across the whole firm. The splitting above is what happens when a branch keeps a different year end or trades in a different currency.
Most practice software treats a second office as a second copy of the first. In MyTask the branch runs through the whole system: every screen you enter work on, and every report you read it back from, answers branch by branch or for the practice as a whole. Each office keeps its own financial year, its own currency and its own tax rules — and the firm still adds up.
What each branch has separately
These are decisions the software makes per branch, not per firm — and they hold on every screen in the product, not on a branches page somewhere in settings. That is the difference between multi-branch and multi-login.
Its own financial year
An Indian office runs April to March. A Dubai or Singapore desk runs January to December. Neither has to pretend to be the other, and no report has to be re-cut by hand to reconcile them.
Its own currency
Branches bill in the currency they trade in. An invoice can be viewed converted into another currency without changing the invoice itself — the figure your client agreed stays the figure on the document.
Its own tax structure
Indian branches carry GST, including multiple registrations across states. Branches outside India carry whatever their jurisdiction requires, as a tax and rate structure you define rather than one we assume.
Its own people and permissions
Access is granted per user, per branch, per module. A manager in Jaipur sees Jaipur; a partner sees everything; and nobody has to be trusted with the whole firm to be useful in one office.
How branches work day to day
Pick the office
A branch selector sits at the top of the dashboard. Everything below it — tasks, schedules, notices, performance — answers for that office. Partners with access to all of them switch without logging out.
Work is raised against a branch
A task belongs to the office that owes it. Task creation asks for the branch first, and the service tree, the team and the due dates follow from there.
Reports read either way
Run a report for one office when you are managing it, and for the practice when you are running the practice. It is the same report either way, not a separate consolidated edition kept somewhere else.
Nobody sees more than they should
Access is set per user, per branch, per module. A branch manager sees their office; a partner sees the firm. The permission and the branch are the same setting, so there is nowhere for one to drift from the other.
Worth having if
- You have more than one office and currently reconcile them in a spreadsheet at month end.
- You have a desk outside India — Dubai, Singapore, London — on a different financial year and a different currency.
- You hold more than one GST registration and need each to stand on its own while the practice still reads as one.
- You are about to open a second office and would rather not find out later what the software assumed.
See it against your own branch structure?
Branches are included on every package — there is no per-branch licence and no cap on how many you run.