Client Portal for CPA and accounting firms
Give customers controlled access to account documents and requests.
Does this function belong in your operation?
Use when customers repeatedly request copies, statements or account updates.
Customers need their own financial records or updates.
Clients upload tax organisers, bank statements and receipts, and see which items are still missing. Signed returns are shared for e-signature. Messages stay with the engagement for the whole year.
Bring the records the workflow depends on.
- Customer contacts
- Available documents
- Access rules
Outputs to check
- Customer account view
- Document-access record
- Customer request and response history
Follow the client portal workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
The portal needs approved customer-account data and login access. Financial documents come from invoicing or accounting, either through imports or agreed connections. Online payment and support-ticket creation are separate handoffs; customer access does not grant editing rights over the ledger.
Systems and records it connects with
- Invoice management: Issued invoice references, line amounts and outstanding balances.
- Receipts management: Recorded customer payments and invoice allocations.
- Ticket management: Numbered requests, ownership and resolution history.
- Payment gateways and bank transfers: Payment references and reconciled settlement or bank evidence.
Configure, test and introduce the workflow.
- We list the documents and actions you want to expose. You decide what stays internal. A written view of the portal pages comes back.
- Customer records are matched to login holders. You supply contact names, and we return a trial import to check. Logo, colours and domain are applied. You get a private link to try the portal as a client would.
- A small group goes in early. Their notes on wording and missing documents come back to you as a short list. Invitations go out in groups. Your accounts desk learns the reply screens, and phone requests for copies fall away as clients get used to the page.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Customers cannot view other accounts.
- Balances reconcile with the ledger.
- Requests retain submission dates.
How the business operates.
A CPA firm sells a deadline. Individual returns, business returns, quarterly estimates, payroll filings, reviews and audits each fall due on a date set by someone else. Every one passes from preparer to reviewer to partner.
The records that hold the operation together.
- Client and entity register. Hold each client with its entities, owners, family links, contacts and the engagements the firm performs for them. Partnerships, S corporations, trusts and individuals sit side by side on one register.
- Engagement letters and proposals. Prepare proposals with service scope and fee, and record acceptance. The signed engagement letter and any representation letter stay on the client file, so scope can be checked when a client asks for extra work.
- Deadline calendar and extensions. Raise each return, filing and monthly job from your service list with its due date and extension date. See the week’s deadlines by person. Quarterly estimates and payroll filings sit beside annual returns on the same calendar.
- Document checklist and client portal. Send a checklist to the client. Accept uploads by item. Staff see which items are in, which are late and which were chased, so prior-year carryover figures and statements are never requested twice.
Operational bottlenecks to check
Deadlines are tracked in a client spreadsheet
Each return or filing has a due date and an extension date, and both are entered once a year by hand. A missed update shows only when the date has passed, and the penalty notice arrives after.
Document requests are chased by email
Clients send statements, receipts and tax forms in parts and by different routes. Staff cannot tell what is still missing without opening the whole email thread and reading every attachment name.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Engagement set-up
A proposal is accepted, the engagement letter is signed, and the engagement is created with its services, fee basis, partner, preparer, reviewer and due dates.
2. Document collection
A checklist goes to the client portal. Uploads attach to the job, and reminders go to the client for anything still missing, such as a depreciation schedule or a year-end bank statement.
3. Preparation
The assigned accountant prepares the return or statements, records hours, ties out balances to the trial balance, and notes any open question for the client or the manager.
4. Review and sign-off
A reviewer adds notes against the workpapers, the preparer clears them, and the partner signs off before the file is filed or released.
5. Filing and delivery
The filed copy and the acknowledgement are stored on the engagement. The client receives the final documents through the portal, with the signed e-file authorisation beside them.
6. Billing and follow-up
A fixed fee or recorded time feeds each bill, a partner approves any write-down, and balances still owing drop onto the collections list.
Industry reports to connect with
- Deadlines and extensions by week and person
- Document requests outstanding by client
- Files awaiting review or partner sign-off
- Hours and realisation against budget by engagement
Questions before implementation.
When should cpa and accounting firms consider client portal?
Use when customers repeatedly request copies, statements or account updates. Customers need their own financial records or updates.
What should we bring to the requirements discussion?
Bring anonymised examples of Customer contacts; Available documents; Access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Give customers controlled access to account documents and requests. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
Payments, signing and identity connections need separate scope confirmation.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customers cannot view other accounts. Use this check when reviewing the first working version.
Related functions for cpa and accounting firms.
Discuss client portal for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements