Client document collection software for UK accountants
FigsFlow is client document collection software for UK accounting and bookkeeping firms. Ask for the records once, from the job that needs them. The client sees exactly what is outstanding, uploads without creating an account, and the request chases itself until everything is in.
281 reviews from
G2 reviews
Google reviews
Verified reviews
The firm's request board showing five clients who have returned part of what was asked for, none of them complete, and the same request as the client sees it on a phone.
Trusted by the best
Watch one request go out and come back
Ninety seconds. Raise the request from the job, watch the client open it, upload two of five items, get chased on day three, and finish. This is what client document collection software looks like when the request belongs to the job rather than to somebody’s inbox.
You have asked twice. It is not rude to ask a third time
The bank statements are still not here. You asked in an email that is now forty messages down, and you cannot remember whether the second chase went out or you only thought about sending it. One client has replied with three of the seven things and no note about the rest. The deadline has not moved.
The bank statements are still not here.
You asked in an email that is now forty messages down, and you cannot remember whether the second chase went out or you only thought about sending it.
One client has replied with three of the seven things and no note about the rest.
The deadline has not moved.
Everywhere you have to ask a client for something
Requests are not an onboarding feature. They run the whole year: the records for every monthly bookkeeping job, the quarter’s VAT paperwork, the year-end pack, and the identity documents an AML check needs before anything can start.
Choose a point in the year to bring its request forward.
New client onboarding
CompleteMonthly records
Part returnedVAT quarter
Part returnedYear-end pack
Not openedAd-hoc queries
Part returnedWhat it collects
When you request documents from clients, this is usually the list.
Do clients need an account?
No. One link, no password, no app. They see a checklist of what you need, tick items off as they upload, and come back to it later on whatever device is nearest. Nothing is lost if they only do half of it today.
- One link, opened on whatever device is nearest.
- No password to set and no password to reset.
- Half-finished today is still half-finished tomorrow, not lost.
Shown: the request as the client opens it, and the same request on the firm’s board
Your accountant needs 7 things to finish your 2025/26 accounts.
- Bank statementsReceived
- Your photo IDReceived
- Sales invoices for the year
- Purchase invoices
- Mortgage interest
- Payroll changes
- Business purchases
Progress saves as you go. Powered by FigsFlow.
One template. Each request carries that client’s own list and deadline.
- Complete · 118
- Part returned · 46
- Not opened · 36
Can we send the same request to two hundred clients?
Yes. One template, two hundred requests, each carrying that client’s own list and deadline. They come back onto one board instead of two hundred email threads, and you never send the same reminder twice by accident.
- Templates to build
- One
- Requests raised from it
- 200
- Each request carries
- That client’s list and deadline
- Where replies land
- One board, not 200 threads
Shown: the Monthly records template, November run
Does it chase for us?
On a schedule you set, in your firm’s name, and it stops the moment the last item arrives. No client is ever chased for something they have already sent, which is the part that actually costs you goodwill.
- Reminders go out
- Day 3, day 7, day 10
- Sent in the name of
- Your firm
- Second reminder covers
- Outstanding items only
- Schedule ends
- When the last item arrives
Shown: one request to Ridgeline Foods, from raised to escalated
Chase history
Ridgeline Foods Ltd- 12 Oct 2026
Request sent — 7 items
7 outstanding - 15 Oct 2026
Reminder 1 sent automatically
7 outstanding - 15 Oct 2026
Client uploaded 2 items
5 outstanding - 19 Oct 2026
Reminder 2 sent — outstanding items only
5 outstanding - 21 Oct 2026
Client uploaded 1 item
4 outstanding - 22 Oct 2026
Escalated to the client manager
4 outstanding
When the seventh item arrives the schedule ends itself. Nobody is chased for something already sent.
Reminder schedule
OnSent in your firm’s name. Stops the moment the last item arrives.
Requests across the book
11 November 2026Blocking a job right now
Sorted by deadlineHow do we know what is still missing?
One board across the whole book: requested, part returned, complete. You can see which clients are holding up which jobs before the deadline is close enough to matter, and what arrives files itself into your own SharePoint.
- Requests in flight
- 214 across the book
- Statuses on one board
- Requested, part returned, complete
- Blocked jobs sorted by
- Deadline
- Returned files land in
- Your own SharePoint
Placeholder. Your actual certifications only. If FigsFlow holds none, display none — no competitor’s badge has been borrowed here.
Seen enough? Raise one request and watch what comes back.
A shared folder, or a request that knows what is missing
A folder accepts whatever arrives and tells you nothing. A request knows what it asked for, what came back and what is still outstanding.
It accepts whatever arrives
Send a link. A client uploads something. You open it to find out what it is, then work out what is still missing.
It knows what it asked for
Every requested item has a visible state. Chasing happens automatically and stops when the item arrives.
Who it is for
Whose problem this actually is
One request, four sizes of practice. Choose yours and see what the same chase looks like from where you sit.
↑ ↓ to move between practice sizes
Three of you, one client, the same ask
Three people chase the same client for different things in the same week. One request per job, visible to all of you, ends the double-asking that makes a practice look disorganised to its own clients.
- Shared request
- One chase schedule
- 12 October 2026, 09:04 · A. Shrestha raised the request · 7 items
- 15 October 2026, 07:00 · reminder 1 sent · automatic
- 15 October 2026, 19:22 · client uploaded 2 items
- 19 October 2026, 07:00 · reminder 2 sent · 5 items outstanding
- 21 October 2026, 11:38 · client uploaded 1 item
- 22 October 2026, 07:00 · escalated · R. Basnet notified
The same request, four reasons to want it. The mechanism does not change — what you do with the board does.
See how a request is builtWorks with what you already run
What arrives lands in your own SharePoint tenancy, filed against the client and the job. Requests go out through your Microsoft 365 or your own sending domain, so the client sees your firm.
Ridgeline Foods Ltd
CT600 · 2026
- Bank statementsReceived
- Signed leaseReceived
- Directors’ loan detailOutstanding
Sent from your domain · filed to your SharePoint
Your tenant at both ends. The records start in the systems you already run and finish there too.
Workiro names TaxCalc and IRIS on its UK page. If FigsFlow connects to either, naming them is worth more to a UK buyer than another generic integration badge. Only name what genuinely connects.
Built inside a working UK practice
Built inside working practices, not in a lab — by people who had returned their own work with review points on it.
Placeholder
0:48
Placeholder
1:02
Placeholder
0:55
Placeholder
1:14
What it costs
A real number belongs here. It is deliberately blank rather than filled with something plausible.
Placeholder. US availability, with a date. Undated availability notes age badly and get quoted back at you.
Questions firms ask before they switch
The six that come up on every call, answered the way we would answer them on the call.
How is this different from a shared folder or a client portal?
A folder accepts whatever arrives. A request knows what it asked for, shows the client what is still outstanding, chases on its own, and tells the job when it can start. The portal is where the client does it; the request is what makes it a list rather than a pile.
Do clients need a login?
No. One link, no password, no app, and they can come back to a part-finished request later.
What if a client sends things by email anyway?
Attach them to the request. The list is what matters, not the route, and the outstanding items update either way.
Can we reuse the same request every month?
Yes. Requests attach to recurring jobs, so the monthly bookkeeping list goes out on its own schedule without anyone rebuilding it.
Where do the files actually end up?
In your own SharePoint tenancy, filed against the client and the job. FigsFlow does not become your document store.
Is it secure enough for identity documents?
Placeholder, held open on purpose. Do not answer this with adjectives. State the actual encryption, retention and access controls, and name only certifications FigsFlow genuinely holds. Security is the fight on this SERP: SmartVault answers the equivalent question with four named standards, so an answer made of reassuring words will lose to it.
Raise one request and see what comes back
Pick the client who always sends three of seven things and send them a real request. You will know within a week whether client document collection software changes anything, and it takes about five minutes to set up. Free trial. Or bring your current records checklist to a demo.