The client portal that keeps every client request, document and approval moving
FigsFlow’s client portal gives every client one secure place to see what you need from them, upload it against the right job, ask a question, approve a draft and pay their invoice. Every action is logged against the same client record your team already works from — so nothing important lives in an inbox.
281 reviews from
G2 reviews
Google reviews
Verified reviews
Trusted by the best
See how clients keep your books moving
Four chapters, exactly as your client sees the client portal: what’s outstanding, sending documents, asking a question, approving and signing.
- What’s outstanding
- Send the documents
- Ask a question
- Approve and sign
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 walkthroughLess chasing. More client work completed on time.
Four things that happen in every practice in January.
Three months of bank statements, photographed, sent to someone’s personal mobile. Nobody can file them and nobody can find them again.
No covering note, no year, no client name. Someone has to open it just to work out what it is and which job it belongs to.
They might have. Nobody can prove it either way without opening a dozen email threads and hoping none were filed to the wrong folder.
The outstanding list is a spreadsheet on one desktop. Priya is on annual leave until Thursday.
None of this is a document problem. It is a request problem — nobody can see, in one place, what was asked for, who it was asked of, when, and what actually came back.
See what your outstanding list looks like in one placeFrom client request to close, keep everything connected
The client portal is not a bolt-on with its own database. It is the client-facing side of the record your practice already works from. Follow one job through it.
-
Engagement letter signed
The accounts job is created from your service template. Nobody opens a new record: the prospect record simply becomes a client record.
-
Records requested
The information request goes out as a client portal form with a slot for each item. The finance manager uploads from her phone on the train.
-
Everything files itself
Each file lands named, tagged and filed against the Harlow Joinery accounts job, because the client portal knew which job it was asking for.
-
Draft approved
The accounts go back to the client portal for sign-off. The director signs. The job is marked filed.
-
Invoice paid
Raised against the agreed fee and paid in the same client portal, in the same session, by the same person who just approved the accounts.
FigsFlow runs the practice and the client relationship. The filing itself happens in your tax and ledger software.
See how an engagement letter starts the job How jobs and workflow steps are built How the fee reaches the invoice
Follow a job end to endWhat does each client need to do next?
The five things your client opens the client portal to do.
Action required
The client portal opens on one banner for anything overdue or due inside 48 hours, above active jobs, next deadlines and unpaid invoices.
One obvious button
Every task card carries a live countdown, a priority badge, the job it belongs to and a single action — Upload, Sign, Approve or Review.
A slot per document
Requests arrive as forms with one labelled slot per item, so nobody submits twelve months of bank statements as a single merged file.
Where’s my return?
Current stage, progress bar, assigned handler and the date you agreed — with several years running at once grouped rather than listed flat.
Every deadline, by authority
Statutory obligations colour-coded by status, with the late-filing penalty and the linked job one tap away.
Everything that closes the loop, logged as it happens
And the five things that close the job out.
Sign in two taps
Signature fields are highlighted in the client portal viewer rather than buried on page nine, and the client draws, types or uploads.
Joint signatures
Both fields shown with a status against each name, each signatory notified separately, and the document complete only when both have signed.
Pay on approval
Card, Apple Pay, Google Pay, bank transfer or Direct Debit, with the status updating in real time and the receipt emailed automatically.
Questions on the record
Chat sits on every screen of the client portal, nothing can be deleted once sent, and threads export and are retained for at least seven years.
Audit trail per file
Version history, a log of who accessed what and when, and a signed version that can never be overwritten by a later upload.
More than a client portal. A better way to run client work.
What a client portal has to do depends entirely on the size of the practice running it. Pick yours.
The 9pm reminder round.One person, ninety clients, and every chase is one you personally remembered to send.
You are the chasing function, and the work stops the week you are away.
Reminders go out without you: on assignment, then seven, three and one day before, then daily once overdue, capped at five. What is outstanding across every client sits on one screen.
The week Priya is away.One person holds the outstanding list, and nobody else can answer a client without reading her inbox.
The outstanding list lives with whoever built the spreadsheet.
The outstanding list is the system, not a document. Any member of staff can see what was asked of whom and when, because the request and the reply both sit on the job.
Six handlers, six ways of asking.Nobody is doing it wrong, and nobody is doing it the same.
Every handler chases differently, and the partner has no view until the deadline is close.
One request process for every handler and every service, with a partner-level view of which clients are unresponsive and which jobs are blocked on them rather than on you.
The access question nobody can answer.Multi-office, client groups, and no confident answer to who can currently see what.
Access is managed by whoever set it up, and nobody is confident who can currently see what.
Access is a dated, scoped grant per person per client, engagement or group, revocable in one action. A consolidated group view needs a recorded disclosure scope on top, because group membership alone is never authority to see one client’s data beside another’s.
A 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.
Give your team and your clients a better way to work
We are recording the first client portal stories now. Four practices, four sizes, in their own words.
FigsFlow is built inside a working UK practice — used day to day by UK Property Accountants, supported by the Sterling Wells team, on real clients with real deadlines. The founding practices joining now are the ones whose stories fill this section.
How a two-to-ten person practice sets this up What changes when you pass twenty staff
Fits into your accounting stack, not around it
The client portal is where your stack meets your client, so it connects to the tools already carrying that work.
-
Payments · Stripe
Card, Apple Pay and Google Pay at launch, plus bank transfer and Direct Debit where you have it configured. The invoice status updates in real time and the receipt is emailed automatically.
-
Documents · Microsoft 365
Client uploads live in your own Microsoft 365 tenancy — SharePoint and OneDrive — rather than in a store only FigsFlow can read. Your folder structure, your retention policy.
-
Email and calendar · Microsoft 365 and Outlook
Entra ID single sign-on and MFA for your staff, with notifications and scheduling running through the mail and calendar your practice already uses.
-
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.
See what happens when client follow-up gets off your plate
FigsFlow is built inside a working UK practice. The client portal is used day to day by UK Property Accountants, supported by the Sterling Wells team, on real clients with real deadlines — which is why it argues about joint signatures and rejected document slots rather than about dashboards.
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 programme
We are onboarding founding practices onto the client portal now — founding pricing, a migration of your existing client list, and direct access to the product team while the roadmap is still being set.
Talk to us about the founding programmeGet Client Portal as part of your FigsFlow workflow
The client portal is not a separate product with its own login. It is part of the FigsFlow workflow, running on the same client record as the rest of the platform.
Live in the UK today
- Client dashboard and to-do tasks
- Job status tracking
- Notifications across push, in-app and email
- Document library with upload from file, camera or cloud
- Form-guided document intake
- E-signature and approvals
- Chat with your client team
- Statutory compliance calendar
- Proposals and engagement letters
- Invoice view and Pay Now, including Apple Pay and Google Pay
Built, but not yet
- Financial insights — P&L, balance sheet and key ratios drawn from Xero or QuickBooks Online
- Document lock to invoice
- OCR and full-text document search
- Contextual chat linked to a specific job or document, with escalation SLAs
- Recurring and subscription billing
- Native iOS and Android apps
No committed date
- Trend and variance analysis with benchmarking
- Time tracking and billable hours
- In-portal voice and video calls
- Single sign-on
- AI-drafted financial commentary
Accurate as at 11/09/2026. We would rather tell you what is not built yet than have you find out in month two.
Connect the portal to the rest of your practice
Every action a client takes in the portal is logged against the same client record your team works from, so nothing has to be copied across afterwards.
One labelled slot per requested item, so an upload lands against the right job.
See forms and requests → E-signature and approvalsSignature fields highlighted in the viewer, with joint signatures supported.
See e-signature → Client mobile appThe same portal as a native app, with biometric sign-in.
See the client app → Timesheets and billingCard, Apple Pay, Google Pay, bank transfer or Direct Debit, through Stripe.
See timesheets and billing → AI assistant AML and client due diligence API and webhooks Audit trail and evidence Companies House CRM and pipeline Documents in SharePoint Email Engagement letters HMRC deadlines Jobs, tasks and deadlines Meetings and scheduling MTD Income Tax Onboarding suite Practice dashboard Pricing and quoting Proposals Reporting and analytics Risk assessment and scoring Team and capacity Workflow templates The whole platformYour Client Portal questions, answered
Do clients need another password to remember?
Can a husband and wife share one login?
Can one login see several of my client’s companies?
Can clients see our internal notes or our real target date?
Does the client portal file anything with HMRC or Companies House?
What happens to clients who carry on emailing us attachments?
What if a client just ignores the reminders?
Is there a mobile app?
How long are client portal messages and documents kept?
Ready to close the loop on client follow-up?
Book a demo and we will run one of your own services through the client portal end to end — the request, the upload, the approval and the invoice — so you can see where your chasing actually goes.
Next in the flow: the invoice your client pays in the client portal is raised from the fee you agreed at proposal stage — see where the fee is agreed.