Multi-branch operations
Two branches, two spreadsheets, two versions of the truth.
Every group operation eventually discovers that its branches count things differently — and that the consolidated report is therefore an estimate with a decimal point on it.
Your operation
Each branch runs its own book. They were probably acquired rather than founded, so each arrived with its own process, its own reference format and quite possibly its own software.
Head office needs a consolidated view. Branch managers need their own book and reasonably do not want head office reading their notes. Handlers need their caseload and nothing else. Those three requirements are in tension, and the usual resolution is that everybody gets everything and nobody looks.
Then a group report is assembled monthly by exporting from each branch and reconciling in a spreadsheet, and it is late and slightly wrong every time.
Where it costs you
Everybody can see everything
Because segmenting it properly was too hard, so access control became an honesty policy rather than a control.
Branches count differently
One counts a claim from instruction, another from verification. Both are defensible; the consolidated figure is neither.
The group report is a monthly reconciliation
Done by a person, from exports, and out of date by the time it is circulated.
An acquired branch stays on its old system
Indefinitely, because migrating it was quoted at a number nobody wanted to approve, so the group runs two of everything.
A handler sees the whole book
Which is a data protection exposure that grows with headcount and is invisible until it is an incident.
What changes
Visibility is a second axis, not a role
What a person may DO and how much of the book they may SEE are set independently. A handler with full capability on their own caseload and no access to the rest is a normal configuration rather than a compromise.
Teams and branches
Claims belong to a team; people belong to teams. A branch manager sees their branch, head office sees the group, and neither has to be granted the other's view to get their own.
One definition of every figure
Because there is one system. The consolidated report is a query rather than a reconciliation, and every branch is counted the same way because the counting is not theirs to change.
Analytics Pro →Migration is included
So bringing an acquired branch across is not a capital request. Map, validate, rehearse without changing anything, review, commit — and the mapping profile is reused for the next acquisition on the same source system.
How migration works →Every change is attributable
Before-and-after values, the actor and their address — across the whole group, in one audit log rather than several.
What a firm like yours actually runs
Core — teams, branches, record-level visibility, the audit log and the Migration Centre are all Core. None of the above requires a module.
- Analytics Pro — group reporting with consistent definitions and prior-period comparison.
- API & Integration — if a group data warehouse needs to read from the source rather than from an export.
Enterprise adds single sign-on, a 99.9% service level with credits, a named contact and procurement support — which is usually what a group actually needs beyond the software itself.
See it against one of your real claims.
Thirty minutes, no slides. Bring a live file and we will run it through the system end to end.