The client portal that keeps every request, document and approval moving
FigsFlow's client portal for accountants 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.
Monday · 2026-09-07
Good morning, Sarah
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.
The problem
Less chasing. More client work completed on time.
Four things that happen in every Canadian practice between February and April.
“I sent it on WhatsApp”
Three months of bank statements, photographed and sent to someone's personal phone. Nobody can file them and nobody can find them again.
“scan0043.pdf”
No covering note, no tax year, no client name. Someone has to open it just to work out whether it is a T4, a T5 or an RRSP receipt.
“I definitely sent that in March”
They might have. Nobody can prove it either way without opening a dozen email threads and hoping none were filed to the wrong folder.
“Ask Mei, she keeps the list”
The outstanding list is a spreadsheet on one desktop — and Mei is on vacation until Thursday, two weeks before the T1 deadline.
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.
One client record
From 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 corporate year-end job through it.
FigsFlow runs the practice and the client relationship. The return itself is still prepared and filed in your own tax software.
- Engagement letter signedThe T2 and financial statements job is created from your service template. The prospect record simply becomes a client record.
- Records requestedThe information request goes out as a portal form with a slot for each item. The controller uploads from her phone on the GO train.
- Everything files itselfEach file lands named, tagged and filed against the Maple Ridge year-end job, because the portal knew which job it was asking for.
- Draft approvedThe financial statements go back to the portal for sign-off. The director signs and the job moves to filing.
- Invoice paidRaised against the agreed fee and paid in the same portal session, by the same person who just approved the statements.
What it does
What does each client need to do next?
The six things your client opens the client portal to do.
Action required
The portal opens on one banner for anything overdue or due within 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 statements as a single merged file.
Where's my return?
Current stage, progress, assigned handler and the date you agreed — with several years running at once grouped rather than listed flat.
Every deadline, by authority
CRA, Revenu Québec and provincial obligations colour-coded by status, with the linked job one tap away.
Pay on approval
Card, Apple Pay or Google Pay, with the status updating in real time and the receipt emailed automatically.
Closing the job
Everything that closes the loop, logged as it happens
And the four things that close the job out.
Sign in two taps
Signature fields are highlighted in the viewer rather than buried on page nine, and the client draws, types or uploads.
Joint signatures
Each signatory is notified separately, and the document completes only when both spouses or both directors have signed.
Questions on the record
Chat sits on every screen, nothing can be deleted once sent, and threads export and are retained to your policy.
Audit trail per file
Version history, a log of who opened what and when, and a signed version that a later upload can never overwrite.
Read more about e-signature and approvals and documents in your SharePoint.
By practice size
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 firm running it.
The 9 p.m. reminder round
How it works nowYou are the chasing function, and the work stops the week you are away.
With FigsFlowReminders go out without you — on assignment, then seven, three and one day before, then daily once overdue, capped at five.
The week Mei is away
How it works nowThe outstanding list lives with whoever built the spreadsheet.
With FigsFlowThe outstanding list is the system, not a document. Anyone can see what was asked of whom and when.
Six handlers, six ways of asking
How it works nowEvery handler chases differently, and the partner has no view until the deadline is close.
With FigsFlowOne request process for every service, with a partner view of which jobs are blocked on the client.
The access question
How it works nowAcross offices and client groups, nobody is confident who can currently see what.
With FigsFlowAccess is a dated, scoped grant per person per client or engagement, revocable in one action.
The comparison
A client portal, or a folder with a password on it
Most firms already have somewhere clients can send files. 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.
Integrations
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, with invoice status updating in real time and the receipt emailed automatically.
Documents · Microsoft 365
Client uploads live in your own Microsoft 365 tenant — SharePoint and OneDrive — under your folder structure and retention policy.
Email and calendar · Outlook
Entra ID single sign-on and MFA for staff, with notifications and scheduling through the mail and calendar you already use.
The rest of FigsFlow
Proposals, engagement letters, jobs and onboarding 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 single sign-on with MFA, access is role-based, and every view and download is logged. FigsFlow supports your firm's privacy and record-keeping obligations; your firm remains responsible for its own compliance with PIPEDA and any applicable provincial privacy legislation.
What isn't connected yet
No tax preparation software integrations yet. The portal collects records, approvals and signatures; it does not push data into the package where the T1 or T2 return is prepared. We would rather tell you that here than let you find out in week three.
Availability
Get the client portal as part of your FigsFlow workflow
Not a separate product with its own login — it runs on the same client record as the rest of the platform.
Live today
- Client dashboard and to-do tasks
- Job status tracking
- Push, in-app and email notifications
- Document library with camera upload
- Form-guided document intake
- E-signature and approvals
- Chat with your client team
- Invoice view and Pay Now
Built, but not yet
- Financial insights from Xero or QuickBooks Online
- Document lock to invoice
- OCR and full-text document search
- Recurring and subscription billing
- Native iOS and Android apps
No committed date
- Trend and variance analysis
- Time tracking and billable hours
- In-portal voice and video calls
- AI-drafted financial commentary
We would rather tell you what is not built yet than have you find out in month two.
Related platform features
Connect the portal to the rest of your practice
Every action a client takes in the portal is logged against the same record your team works from.
See it run on your own practice.
Screen-shared, using your services, your client mix and your CRA deadlines. You will see where FigsFlow fits — and where it does not.