Onboarding that ends with the work already started
FigsFlow is client onboarding software for UK accountancy practices — enquiry, Companies House lookup, due diligence, risk assessment, proposal, engagement letter and the first job, on one client record. The client signs and the work is already scheduled. Nothing is re-typed between steps, and nothing reaches a client before the check that is supposed to gate it.
Partner or principal, start with the two views in the tour below. MLRO or practice manager, go straight to where the re-keying starts.
- Source Website enquiry · stamped at capture
- Entity The register · live lookup
- Diligence Cleared 04/09 · gate held
- Fee £4,800 · from the live proposal
- Stage Letter signed · first job created
delivery starts on this record — nothing is re-typed
The same onboarding, seen two different ways
A partner opens FigsFlow and sees every client being taken on — what is waiting, what is blocked and what is about to be signed. Whoever is doing the onboarding opens the same system and sees one screen: what is theirs to finish today. Switch between the two, then move through the stages to look around.
Illustrative interface and sample data. The gate behaviour shown — a letter that cannot be released before diligence clears — is the part worth watching.
Nobody chose to type the company name five times. The tools chose it for them.
It is Thursday. A new company client said yes on the phone this morning, and taking them on properly means touching four different systems before anybody does a minute of chargeable work.
The company details go into the onboarding form. Then into the AML tool, because that tool has never heard of this client. Then into the proposal, where the fee is agreed. Then into the letter, which is drafted from a template somebody copied from the last one — including, occasionally, the last client's registered office. Then into the practice system, so the jobs exist.
Somewhere in that sequence the letter goes out before the diligence finishes, because the letter lives in a signing tool that has no idea the check is still open. Nobody decided to work that way. It happens because the check and the letter are in different products, and no product can enforce a gate it cannot see.
One record, from first enquiry to the first job
This is what makes it an onboarding suite rather than an AML tool with a proposal bolted to it. The enquiry, the entity, the check, the fee, the signature and the job are six stages of one record — so the seams in the last fold are not shortened, they are gone. The test an onboarding process has to pass is whether the gate holds when someone is in a hurry, and that is what this flow is built around.
Web form, phone call or referral. The contact and the prospective engagement are created together, with the source stamped on both.
One search against the register brings back the entity, its officers and the PSC data. Nobody types a company number twice.
The fee is not a number somebody typed. It comes from your pricing model, and any override is recorded against the figure it replaced.
The letter cannot be released until diligence clears. The signature is an event, so the signed date and the recorded date cannot disagree.
Jobs and deadlines exist from the signature. The handover is a status change, not a document somebody writes on a Friday.
The gate that either holds, or depends on somebody remembering
Checking the client is one side. Taking them on is the other. They are supposed to meet at a single point — the moment the engagement letter is released — and in most firms they meet in two different products, so the only thing enforcing the order is a person. What that costs you depends on the size of your practice, and so does how often it goes wrong.
Judge onboarding software on that gate rather than on a feature list. The question is not how many AML providers a tool integrates with — it is whether a letter can physically leave the building while a check is open, and whether the answer is still no at 5pm on the last Friday of the quarter when a partner wants it sent. Everything else on this page follows from that one property.
One record. The check and the letter are stages of the same object, so the release is blocked by the system rather than by a person's memory.
Two systems. The signing tool cannot read the AML status, so the gate is a habit — and habits fail on the days you are busiest.
Every size of practice, and the reason each one comes looking
Onboarding stops being something you can hold in your head at the point where you are no longer the only person taking clients on. That point arrives at a different headcount for every practice — and the thing that finally forces the change is different every time too.
Same choice as the section above — pick once, both follow
Short list, honestly labelled
The suite connects to the things a UK practice touches while taking a client on — the registers, the mailbox and the identity checks. The rest of this fold is what is not connected, because finding that out in month two is worse than reading it now.
One search returns the entity, the registered office, the officers and the persons with significant control, and writes them to the client record. It is the first step of onboarding and the reason nothing downstream has to be typed.
- COMPANY SEARCH
- OFFICERS
- PSC DATA
- FILING DATES
- IRISH CRO
Client identity, face match and liveness, PEP and sanctions screening, Amberhill and address verification, run against the matched entity rather than a name somebody keyed in. Companies House identity verification sits in the same session.
- PHOTO ID + LIVENESS
- PEP & SANCTIONS
- ADDRESS VERIFICATION
- AMBERHILL
Mail and calendar work from inside the client record rather than beside it, documents are held in your own tenant under your existing IT policy, and people sign in with the identity your firm already administers.
- OUTLOOK
- SHAREPOINT — YOUR TENANT
- CALENDAR
- ENTRA ID SSO
A submission creates the contact and the prospective engagement together, stamps the source and drops it at the first stage with no human touch. For most practices this is where the majority of enquiries already arrive.
- CONTACT + ENGAGEMENT IN ONE STEP
- SOURCE STAMPED
- FIELDS MAPPED AT SETUP
FigsFlow reads the register to build the client record and support due diligence. It does not file. Statutory filing stays with WebFiling or your filing software.
Not in this releaseThe suite scopes and prices MTD work and schedules the quarterly jobs, but the updates and the Final Declaration are submitted through MTD-compatible software on HMRC’s list. See MTD Income Tax
By design — not plannedNo two-way sync with the ledger your clients keep their records in. The suite takes the client on and schedules the work; it does not post to the books.
Not in this releaseNo integration with the tools you actually prepare and file returns from. Onboarding hands over a scheduled job, not a populated return.
Not in this releaseThe suite runs the checks, records the evidence and holds the gate. Whether the diligence was sufficient, and whether a report should be made, is a judgement for your firm and your MLRO.
Not our roleBring the messiest client you took on this year
Thirty minutes with a practice specialist. We run the whole sequence in front of you on a real company — enquiry, register lookup, diligence, fee, letter, first job — and you can try to send the letter early to see what happens.
Everything the suite does writes itself to the record as it happens. See the audit trail
United Kingdom and Republic of Ireland. This page describes how FigsFlow supports a practice’s onboarding workflow and is not legal, regulatory or tax advice. Your supervisory body’s guidance takes precedence, and your firm remains responsible for its own AML procedure and for deciding whether the due diligence it performs is adequate. Capability statements checked on 01/09/2026 and should be re-verified before release.