Most accounting firms have, at some point, bought a client portal. Fewer have a client base that actually uses it. The usual failure mode is not technical. The portal works, the login exists, and clients still email a PDF of their bank statement to whichever member of staff replied to them most recently. A portal that exists alongside email rather than instead of it has not really changed anything. It has just added a second system that nobody has fully committed to, including the firm.
There is also a quieter cost to the status quo that rarely gets named directly. A bank statement, a passport photo or a set of payroll records sitting in a personal inbox for years is a data protection exposure the firm is carrying without having chosen to. It sits outside any retention policy, it is searchable by nobody except whoever received it, and it leaves the firm the moment that staff member does. None of that is a deliberate decision anyone made; it is just what happens when the primary channel for sensitive client documents is a general-purpose inbox never designed to be one.
Accupe's Client Hub is built on a different premise: it should be the only place a client needs to go, not an alternative to email that quietly loses the competition for convenience. The clearest way to show what that means is to follow one engagement through the Hub from the day the firm opens the file to the day the signed accounts and the paid invoice both land back on the client record. That is what this piece does.
What the client actually logs into
A client does not receive a username and a password they will forget within a month. They receive a Client Code and a PIN, set up once, and a link to the firm's own portal login screen. There is no "forgot password" flow to support because there is no password to forget in the conventional sense, and staff are not fielding a weekly trickle of lockout requests from clients who last logged in eleven months ago. Once inside, the layout is deliberately narrow.
- Documents: a folder structure the firm controls, for sharing files out and requesting files in
- Messages: a single threaded conversation with the firm, tied to the client record
- Signatures: pending and completed signing requests, reviewed and signed in the browser or on a phone
- Tasks: action items the firm has assigned to the client, each one visible until it is done
- A compliance status card showing where identity verification currently stands: Verified, Pending, or Not Started
Onboarding a client into the Hub without a support ticket
The reason the Client Code and PIN model matters more than it looks is that it removes the single biggest source of portal support tickets: password resets for a system a client opens four times a year. A firm setting up a new client generates the code once during onboarding, sends it alongside the PIN in a single welcome message, and the client is in. There is nothing to remember beyond two short values, and nothing that expires the way a temporary password does if a client does not log in within the first week.
This sounds like a small design choice, but at scale it is the difference between a portal a firm can genuinely require every client to use and one it quietly stops insisting on because the friction of supporting it is not worth the fight. A firm with two hundred clients that never has to field "I've forgotten my portal password" is recovering a real amount of receptionist and junior staff time every single month, even if no one has ever measured it directly.
The same model also means a client who only ever engages with the firm once a year, at renewal time for a confirmation statement and an annual accounts approval, does not arrive at that one login moment locked out and needing a reset before they can even see what is being asked of them. Low-frequency use is exactly the pattern a client portal has to survive to be worth building at all, and a Client Code and a PIN survive it far better than a password most people will type incorrectly on the first attempt after eleven months away.
A UK limited company's March year end, start to finish
Consider a small limited company client with a 31 March year end, run through the Hub as the engagement is actually structured inside Accupe. In early April, the manager opens a recurring annual accounts job on the Smart Board and sends a standard document request through the portal: bank statements for the full year, the sales and purchase ledgers, any asset additions, and confirmation of outstanding loans. The client receives one notification, not a chain of separate emails, and uploads what they have from their phone over the following fortnight, a few documents at a time, whenever it is convenient rather than whenever the firm asked.
When the manager starts the draft in July, two figures do not reconcile against the bank feed, and there is a query over a director's loan repayment the client had not mentioned. Instead of a phone call that interrupts both parties' afternoons, the manager posts a portal message asking for the missing invoice and the loan agreement, and the client replies with a photo of both the next morning, the conversation sitting permanently against the job rather than buried in a personal inbox. By September, the draft is complete and partner reviewed. The accounts approval letter goes out through the Signatures tab; the client reads it, signs from their phone on the train, and the signed PDF lands back on the client record automatically, no download and no forwarding required.
A week later, the invoice for the job appears in the same portal, and the client pays it without leaving the Hub. The whole cycle, from document request to paid invoice, happened inside one login, with a complete record of every exchange sitting exactly where the next person to open the file will look for it, whether that is the same manager next year or a new joiner three years from now who has never met the client and needs to understand the relationship from the record alone.
The document request, replacing the inbox and the USB stick
The specific thing the Documents tab replaces is not really email as a technology. It is the particular failure mode of email as a filing system: the attachment that arrives correctly but gets saved to the wrong client folder, the WeTransfer link that expires before anyone downloads it, the USB stick a client still occasionally brings into reception because that is how they have always done it. A request sent through the Hub tells the client exactly what is needed, in plain language, with a single upload target that accepts photos taken directly on a phone as readily as a scanned PDF. What comes back is filed automatically against the correct client and, where the request was linked to a specific job, against that job too, so a manager opening the annual accounts job six months later finds the supporting records already sitting where the work needs them.
The folder structure itself is nested and firm-controlled, so a nine-year relationship with a client does not degenerate into a flat pile of two hundred identically named PDFs. If a client re-uploads a corrected version of a document, the earlier one is retained rather than silently overwritten, so nobody has to guess which version a decision was actually based on. Files are stored in encrypted cloud storage, and the client sees only what the firm has chosen to share with them, never the firm's working papers or internal notes.
This also changes what happens when a client leaves and comes back, or when a second entity under the same ownership needs onboarding. Because the document history sits on the record rather than in whichever inbox happened to receive it three years ago, reopening a dormant client relationship does not mean starting the paper trail from zero; the firm can see exactly what was previously supplied and what genuinely needs refreshing.
Messaging that survives staff turnover
The Messages tab is deliberately unglamorous. It is a real-time chat thread, encrypted in transit and at rest, attached permanently to the client record rather than to any individual staff member's inbox. Messages arrive with read receipts on both sides, so the client can see their query was actually opened rather than wondering whether it landed in a spam folder somewhere, and the firm can see when a document request has been read but not yet acted on. Standard staff see only the threads for clients assigned to them; managers and admins see every conversation, which matters both for quality oversight and for the moment a manager leaves the firm and a successor needs to understand eighteen months of context in an afternoon rather than reconstruct it from memory.
The practical effect over a full financial year is that a genuinely difficult client relationship, the one with the persistent late payer, the one who disputes a fee, the one whose records always arrive incomplete, has a documented history the firm can point to rather than a partner's recollection of "we did chase them, several times." The conversation is not a nice-to-have layered on top of the real record. It is part of the record, and a firm defending its own conduct in a fee dispute is in a materially stronger position with a dated, timestamped thread than with a shared recollection of a phone call from four months earlier.
Signatures and tasks close the loop in the same tab set
The reason the Hub feels complete rather than partial is that signing and task tracking sit next to the documents and the messages, not in a separate tool the client has to be onboarded to separately. Pending signature requests, whether an engagement letter, an accounts approval, or a one-off authority form, sit in the Signatures tab alongside everything the client has already signed with the firm, so a client can always check back on exactly what they previously agreed to without emailing to ask for a copy.
If the firm has asked for something specific, such as "provide bank statements for Q3" or "confirm the new registered address," it appears as a Portal Task with its own due date, so the client always has a concrete, visible answer to "what does the firm still need from me," rather than having to re-read an old email to find out. A task left outstanding past its due date surfaces on the manager's side too, so a stalled client response is visible to the firm before it becomes a missed deadline rather than after, giving the manager a genuine window to chase before the consequence lands rather than after.
How much of this is actually branded
Every Accupe plan gives clients a portal under the firm's own login screen, with the firm's name and logo attached rather than a generic vendor page. Elite goes further: it unlocks full portal colour customisation, letting the firm match its own brand palette rather than a fixed default, and a genuine custom domain, so the client can be sent to something like portal.firmname.co.uk with no visible reference to Accupe anywhere in the experience.
For a firm competing on a premium advisory positioning, or one whose clients are used to a polished Big Four style portal from a previous adviser, that distinction is worth having, and it is the kind of detail a prospective client notices in the first five minutes of a relationship even if they never mention it. For a smaller bookkeeping practice where the client cares more about whether the upload works than what colour the buttons are, the base experience on Solo or Growth is already doing the job that matters, and the firm can revisit the custom domain question later as the practice grows and the branding investment starts to pay for itself in client perception rather than function alone.
What the Client Hub does not do, and what changes when it works
The Hub is the experience and record-keeping layer, not the work itself. It does not prepare the accounts, calculate the tax, or file anything with HMRC, Companies House or the FTA; those remain the firm's professional work and its chosen filing tools. It is also not a replacement for judgement about when a conversation needs to happen by phone rather than by message; a sensitive discussion about a client's financial difficulty or a dispute over fees is still better held as a call, and the firm should treat the portal as the channel for structured, documented exchange rather than the only channel available for every kind of conversation. Nor does it replace the firm's bookkeeping software: documents uploaded through the portal are supporting evidence for the work, not a live feed into a general ledger, and a client's Xero or Zoho Books connection remains the source of the underlying financial data.
Firms that move a genuine majority of client interaction into the Hub describe a consistent pattern. Document chasing becomes less frequent because requests are specific and the upload path is a single tap from a phone the client already has in their hand. Response times to client queries improve because messages route to the right person immediately rather than sitting in a shared inbox behind newsletters and supplier invoices. And, less obviously, the firm accumulates a searchable record of every document, message, signature and task across the relationship, which is worth more with every year that passes. A portal only earns that value once it is where the relationship actually lives, not a second system running alongside the one everybody still uses out of habit.
