Fifty offices or five — one system, under your policy
FigsFlow is practice management software for larger accountancy firms. Permissions are delegated by office and team, onboarding and engagement follow one firm standard with room for local variation, and every action is written to an exportable audit trail — so a review does not start with a reconstruction exercise.
Partner or COO, start with the firm view below. IT or compliance, jump straight to permissions and the audit trail.
Same firm standard everywhere. Each office rolls out on its own timeline, and none of them wait for the others.
- Offices Six sites · one instance
- Permissions Delegated by office and team
- Onboarding One standard · local variation
- Audit Every action exportable
- Reporting Firm-wide and by office
one instance, without one central bottleneck
One instance, seen the way a partner or COO needs it
This is the same system every office signs into. Nothing here is a separate tenant per site — click through the stages below to see what the firm controls centrally and what each office runs itself.
Illustrative interface and sample data. The firm and figures are fictional.
What changes when each office can administer its own
Three shifts a firm of fifty and up notices once the rollout settles — none of them require a bigger IT function, just a system built to be delegated rather than centralised by default.
Permissions by office and team
Each site administers its own users and templates inside a firm-wide standard, rather than raising a ticket centrally for every starter and leaver.
One standard, local variation
The firm sets what must be consistent and offices vary the rest, so a national policy does not collapse on contact with a local practice.
An audit trail you can hand over
Every change is recorded and exportable, so a file review or an internal audit does not become a reconstruction exercise.
How a larger firm sequences a rollout
Scope with IT early
Before commercial terms, not after.
Agree the firm standard
And what each office owns.
Start with one office
Never at year end.
Extend site by site
With a review in between.
One firm, and six different ways of doing the same thing.
The firm grew by acquisition and by opening new sites, and each office arrived with its own way of running the practice — its own spreadsheet, its own version of the engagement letter, its own idea of what the AML file should contain.
Access to systems is requested by email, and IT grants it when they get to it. Onboarding in Leeds looks nothing like onboarding in Bristol, because nobody wrote the standard down, or the standard exists in a document nobody re-reads. Then a regulator, an insurer, or an internal audit asks for evidence across every office, and compliance spends a fortnight assembling something that should have already existed.
Nobody designed it this way. It is what happens when a firm scales the number of offices before it scales the system underneath them.
Permissions and the audit trail, on the same record as the work
Running the practice is one side. Standing behind it — who could do what, and proving it afterwards — is the other. They are supposed to meet at the same instance, and in most multi-office firms they meet in a spreadsheet IT maintains by hand instead. The gap is invisible until a review asks you to close it in a fortnight.
One instance. Permissions, the firm standard and the audit trail are properties of the same record, so evidence exists because the action happened, not because someone assembled it.
Two systems. The practice system runs the work; a spreadsheet or ticket queue runs access. The gap is where an ex-employee keeps a login, or a review finds a hole nobody knew was there.
From the firm standard to the evidence a review asks for
Five stages, one instance. An office is added to the firm, not procured separately — so nothing here is a hand-off between systems, only a change of who is allowed to act.
Clause set, AML procedure and required fields — what cannot vary by office.
Added to the existing instance, on its own timeline, with local admin rights.
The office admin grants scoped permissions — nobody emails IT for a starter.
Written to one audit trail regardless of which office it happened in.
Firm-wide or by office, exported without anyone reconstructing anything.
- The firm's approved templates — locked centrally, applied everywhere
- Office-level admin rights — scoped by the firm, run locally
- Role definitions — what a fee earner, manager or partner can see
- The audit trail — every action, attributable, exportable
- Firm-wide reporting — and the same numbers broken down by office
- Insurer and regulator responses — built from the record, not assembled for the occasion
Short list, honestly labelled
What a multi-office firm needs to run under its own policy is already inside FigsFlow. The rest of this fold is what is not connected yet, because finding that out in month two is worse than reading it now.
Single sign-on across every office, with the identity your firm already administers.
Entity, officer and PSC data read once, held on the client record for every office to use.
Existing office data imports as a starting point, and every report exports in full.
Firm-wide or by office, in a format built for handing to a reviewer, not for reformatting first.
No sync with BrightHR, BambooHR, Breathe or the rest. Leave is requested and approved inside FigsFlow.
Phase 2 — not committed to a dateFull data exports today; a native warehouse or BI-tool connector is not yet built.
Not in this releaseEntra ID SSO is supported; other identity providers are not yet configurable.
Not in this releaseQuestions larger firms ask first
Four that come up before commercial terms.
How are permissions handled across multiple offices?
Each office has its own administrator who manages that office's users and templates. Firm-wide settings — the clause set, the AML procedure, required fields — are held centrally and cannot be overridden locally.
What does the audit trail actually record?
Every action that changes a client record, a permission or a firm setting, attributed to the person who made it and timestamped. It exports firm-wide or filtered by office, in a format built for handing to a reviewer.
How is a rollout across several sites sequenced?
Scope with your IT function before commercial terms, agree what the firm standard covers, then start with a single office rather than everyone at once — ideally not at year end. Each additional office extends the same instance.
How is it priced at fifty seats and above?
Banding at this size is confirmed on a call rather than published, since it depends on office count and modules. See the pricing page for the standard tiers below fifty seats.
Walk your own structure through it
A session built around your offices, your roles and the questions your review will ask.