A portal your clients will actually use
FigsFlow is client portal software for accountants — tokenized access with no account to create, mobile upload, 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 owner, start with the six client portal screens your client actually sees in the tour below. Practice manager or ops, go straight to where the chasing goes wrong.
See the client portal the way your client sees it
Click through the six screens of the client portal 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 firm’s own SharePoint, not in storage FigsFlow owns.
This is the client’s side of the client 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 March 14th, and you're still waiting on one 1099
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 number you need, and the client is certain they already sent it.
Nobody in this story is doing anything wrong. The firm is chasing documents 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.
One client record: what the client portal takes in, and what it sends back
The client 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
- An information request raised on a jobBuilt from your own request templates and sent as one link — [[forms-and-requests|see how requests are built and chased]]
- The job's deadline and its ownerSo the client sees a real date and your team sees who is waiting — [[jobs-and-workflow|see how jobs, steps and tasks work]]
- A document waiting for signatureAn engagement letter or proposal, assembled elsewhere and signed here — [[engagement-letters|see how engagement letters are assembled]]
Out of the portal
- Files, filedStraight into your own SharePoint tenant, in your folder structure — [[documents|see how document storage works]]
- An approval that moves the jobThe status changes because the client acted, not because someone remembered to update it
- A signed document and its audit trailWho signed, what version, and when — held against the client record
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 CPA firms of every size.
Can a client use the client portal without creating an account?
Yes. Access to the client portal is tokenized: 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 April, 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 client 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 documents 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 client 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, in the client portal, 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 client portal they uploaded the source documents 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 firm documents. It is not e-file signature authorization: IRS Publication 1345 requires knowledge-based authentication for a remote signature on Forms 8878 and 8879, and FigsFlow does not sign those. Your tax software still does that part.
[[engagement-letters|See how engagement documents get assembled and signed]]
Will clients see where things stand without emailing you to ask?
The client 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.
The client portal carries your firm's name and colors rather than ours, because as far as your client is concerned this is your practice's client 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 firms already have somewhere clients can send files, and call it a client portal. The question is what happens to the conversation around them.
Email and a file-share link The manual way
- Documents 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 client portal solves the conversation around it.
Where the client portal earns its keep
Monthly close teams live in it
The same request, the same twelve clients, every month. The client portal is the difference between a cadence and a chase.
[[bookkeeping-and-cas|See how monthly close teams run recurring client requests]]
Tax teams need 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.
[[tax-firms|See how tax season chasing works end to end]]
Built to sit on top of the stack you already run
The client 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. [[documents|See how document storage works]]
-
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.
Where your client data actually sits
Client uploads land in your own Microsoft tenant, not ours. Staff reach the client 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 — the controls a Written Information Security Plan has to describe under IRS Publication 4557 are how the portal works by default. FigsFlow assists your WISP obligations; your firm remains responsible for them.
No US tax software integrations — not Drake, Lacerte, ProSeries, ProConnect, CCH Axcess, TaxAct or TaxSlayer. We would rather tell you that here than let you find it out in week three. If tax-prep connectivity is the thing you are buying on, we are not the right fit yet.
Built inside working firms
FigsFlow was built inside two practices that use it every day — UK Property Accountants and Sterling Wells. That is why the client 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.
The template requires a quote about the client portal specifically, with the person's name and country shown. No verified quote was supplied, so nothing has been written here. This slot is reserved and must be filled before publication.
Founding-customer program
- Open to ten to fifteen US firms
- A direct line to the product team
- Pricing held for your first year
- Real influence over the US roadmap
What's live in the US right now
Every client portal claim on this page, stated plainly and dated, so you are not finding the gaps out later.
Checked 08/21/2026
Live in the US today
- Tokenized client access, no account creation
- Mobile upload and phone camera capture
- Step-by-step, resumable requests
- Draft approvals against a job
- E-signature on engagement documents
- Plain-English status and firm branding
- Documents into your own SharePoint
Not in the US version yet
- Anti-money-laundering and client due diligence — a UK module, not a US one
- Voice and video calls inside the portal — on the roadmap
- Knowledge-based authentication for IRS Forms 8878 and 8879 — not available
- Pre-built US tax-calendar workflow templates — build your own for now
[[pricing|See what each tier includes]]
What the client portal connects to
Client information requests
Where the requests the client answers are built and chased.
[[forms-and-requests|Client information request software]]
Engagement letters
Assembled from a governed clause library, signed in the client portal.
[[engagement-letters|Engagement letter software for CPAs]]
Document management
Your SharePoint stays the master copy of everything uploaded.
[[documents|Document management for accounting firms]]
Jobs and workflow
The job whose status the client's action actually moves.
[[jobs-and-workflow|Accounting workflow software]]
Email management
For the client conversations that still happen in an inbox.
[[email|Email management for accounting firms]]
Proposals
Where the client relationship starts, on the same record.
[[proposals|Accounting proposal software]]
The awkward client portal questions, answered
Do my clients have to create an account to use the client portal?
Can my clients sign IRS Form 8879 in the portal?
Where do the documents my clients upload actually end up?
Can we put our own firm's branding on the client portal?
Does the client portal work properly on a phone?
Does the portal make my firm compliant with the FTC Safeguards Rule?
See what your clients would see
Thirty minutes on the client portal, driven by someone who has used it inside a working firm. Bring the client conversation you dread most.
Once a client approves in the client portal, the job moves on by itself and the time recorded against it flows into billing — [[jobs-and-workflow|see how a job closes and hands off]].
Start Smarter. Grow Faster.
From proposals to pricing, streamline every step with automation designed particularly for accountants, bookkeepers and tax advisers.