A portal your clients will actually use
FigsFlow is client portal software for accountants — tokenised access with no account to create, upload from a phone, approvals and e-signature on the same client record your information requests, engagement letters and jobs already run on. Every file lands in your own SharePoint, and the job status moves as the client acts.
Partner or principal, start with the six screens your client actually sees in the tour below. Practice manager, go straight to where the chasing goes wrong.
See the client portal the way your client sees it
Click through the six screens your client actually sees. Everything here is their side of the portal — your side is the job, and it updates as they go.
Every file opened in the client portal lives in your practice’s own SharePoint, not in storage FigsFlow owns.
This is the client’s side of the portal, shown with sample data. Sending a request, countersigning and exporting run in the live demo rather than here — those are the parts worth watching someone drive.
Watch the two-minute tourIt’s the 14th of January, and you’re still waiting on one dividend voucher
The return is ninety percent done. The client sent six photos to your personal Outlook on Friday night, two of them sideways. Your colleague emailed the same request on Tuesday, not knowing you had already asked. Somewhere in a thread eleven replies deep is the one figure you need, and the client is certain they already sent it.
Nobody in this story is doing anything wrong. The practice is chasing records across an inbox, a file-share link and a voicemail, and calling the gap between them “waiting on the client”. It isn’t waiting. It’s the cost of never having given the client one place to look.
What the client portal takes in, and what it sends back
The portal is not a separate system with its own client list bolted onto the side. It is the client-facing face of the same record your team is already working on.
Into the portal
- A records request raised on a jobBuilt from your own request templates and sent as one link, on the schedule your workflow sets — see how templates drive client-facing steps
- The job’s deadline and its ownerSo the client sees a real date and your team sees who is waiting — see how jobs, tasks and deadlines work
- A document waiting for signatureAn engagement letter or proposal, assembled elsewhere and signed here — see how engagement letters are assembled
- A due diligence check that has to clearIdentity documents and CDD collected before work starts — see AML and client due diligence
Out of the portal
- Files, filedStraight into your own SharePoint tenant, in your folder structure and under your retention policy
- An approval that moves the jobThe status changes because the client acted, not because someone remembered to update it — see it on the practice dashboard
- A signed document and its audit trailWho signed, which version, and when — see the audit trail
- An approval to file, captured as a recordThe client’s approval sits on the job. The submission itself happens in your tax software
Why this matters more than the feature list. A client portal bought on its own becomes a second place to keep track of. Because this one reads and writes to the same client record as the pipeline, the engagement letter and the job, a document arriving from a client changes what your team sees — with nobody re-keying anything into a second system.
In the order they get asked on a demo call, by practices of every size.
Can a client use it without creating an account?
Yes. Access is tokenised: the client opens a secure link tied to their own record and goes straight to the task. There is no username to invent, no password to reset in January, and no “I never got the invite” to work through on the phone.
That matters less for the client who logs in happily and everything for the one who doesn’t. A portal only works if the reluctant client uses it too. Every account you don’t ask a client to create is a reason they don’t fall back to emailing you an attachment instead.
See this in the tourWill clients actually send records from their phone?
Most clients answer you from a phone, standing up, between two other things. They photograph a receipt with the camera, drop it into the request, and stop when they run out of time — the portal keeps what they have done and lets them resume where they left off.
A half-finished request is not a failure. It is progress your team can see on the job instead of silence you have to interpret.
See the mobile flowCan clients approve and sign without a scheduled call?
Send a draft for approval and the client reads it, asks a question against it, or approves and signs — in the same portal they uploaded the source records to. Every action is timestamped against the job, so the file shows who approved which version and when.
The boundary, stated plainly. E-signature in FigsFlow covers engagement letters, proposals, consents and your own practice documents. FigsFlow does not submit anything to HMRC or Companies House. A client’s approval to file is captured as a dated record on the job; the filing itself still happens in your tax or accounts production software.
Will clients see where things stand without emailing to ask?
The portal says “we’re waiting on your two bank statements” and “your accounts are with your accountant for review”. It does not say “status: pending”, and it does not show a workflow code your client has no reason to understand.
It carries your practice’s name and colours rather than ours, because as far as your client is concerned this is your practice’s portal, not a piece of software you happen to subscribe to.
See the status viewA client portal, or a folder with a password on it
Most practices already have somewhere clients can send files, and call it a portal. The question is what happens to the conversation around them.
Email and a file-share link The manual way
- Records arrive in one person’s inbox
- Two staff chase the same thing on the same day
- Version history is whatever the thread remembers
- The client’s question is “did you get it?”
- Nothing about the job changes when a file arrives
One client record With FigsFlow
- The request, the upload and the approval all sit on the job
- The whole team sees the same state, so nobody double-chases
- Files land in your SharePoint under your retention policy
- The client can see where things stand without asking
- The job status moves as the client acts
A file-share link solves storage. A portal solves the conversation around it.
Where the portal earns its keep
Bookkeeping and VAT teams live in it
The same request, the same twelve clients, every month or every quarter. The portal is the difference between a cadence and a chase — and under Making Tax Digital the cadence gets shorter, not longer.
Self Assessment needs it hardest for ten weeks
Two hundred clients, all owing you something, all at once. Visible status is what stops the chasing becoming its own job by the middle of the month.
Built to sit on top of the stack you already run
The portal doesn’t ask you to move your documents somewhere new. It writes into the tenant your IT function already governs.
-
Microsoft 365
Entra ID single sign-on and MFA for your staff, Outlook and Teams for notifications, and documents written into your own SharePoint tenant rather than ours. Your data stays under your existing retention policy.
-
Xero and QuickBooks Online
Your ledger stays where it is. FigsFlow runs the practice around it rather than replacing it.
-
Stripe
For collecting fees against the work the portal helped get done.
-
The rest of FigsFlow
The connection you never configure. Proposals, engagement letters, jobs, due diligence and the practice dashboard are already the same record — which is why a client upload changes what your team sees.
Where your client data actually sits
Client uploads land in your own Microsoft tenant, not ours. Staff reach the portal through Entra ID single sign-on with MFA, access is role-based, and every view and download is logged. Encryption in transit and at rest, your retention policy, your audit trail — these are the controls your practice’s own data protection and record-keeping policies have to describe, and they are how the portal works by default. FigsFlow supports those obligations; your practice remains responsible for them and for its own UK GDPR and MLR 2017 compliance.
No tax or accounts production software integrations — not TaxCalc, IRIS, Taxfiler, CCH, Sage or BTCSoftware. The portal collects records, approvals and signatures; it does not push data into the package where the return is prepared. We would rather tell you that here than let you find it out in week three. If tax-software connectivity is the thing you are buying on, we are not the right fit yet.
Built inside working practices
FigsFlow was built inside two practices that use it every day — UK Property Accountants and Sterling Wells. That is why the portal handles the awkward parts of a client conversation rather than the demo-friendly ones, and why it is written for accountants rather than for a generic services business.
This slot is reserved for a named client quote about the portal specifically, with the person’s name and firm shown. No verified quote has been supplied, so nothing has been written here. It must be filled or removed before this page is promoted.
Founding-customer programme
- Open to a small number of UK practices
- A direct line to the product team
- Pricing held for your first year
- Real influence over the roadmap
What’s live in the UK right now
Every claim on this page, stated plainly and dated, so you are not finding the gaps out later.
Checked 02/09/2026
Live in the UK today
- Tokenised client access, no account creation
- Mobile upload and phone camera capture
- Step-by-step, resumable records requests
- Draft approvals against a job
- E-signature on engagement documents
- Identity documents and CDD collection
- Plain-English status and practice branding
- Documents into your own SharePoint
Not in the portal yet
- Tax and accounts production software integration — not in this release
- Filing to HMRC or Companies House from the portal — approvals only, by design
- Voice and video calls inside the portal — on the roadmap, no committed date
- A portal in languages other than English — not available
What the client portal connects to
Engagement letters
Assembled from a governed clause library, signed in the portal.
E-signature and approvals
What a signature is worth, and what it is recorded against.
AML and client due diligence
The identity checks the portal collects before work starts.
The awkward client portal questions, answered
Do my clients have to create an account to use the portal?
Can clients approve and file their tax return through the portal?
Where do the documents my clients upload actually end up?
Can we put our own practice branding on the portal?
Does the portal work properly on a phone?
Can we collect AML identity documents through it?
Does using the portal make my practice UK GDPR compliant?
See what your clients would see
Thirty minutes on the client portal, driven by someone who has used it inside a working practice. Bring the client conversation you dread most.
Once a client approves in the portal, the job moves on by itself and the time recorded against it flows into billing — see how a job closes and hands off.