It starts with a simple request. A client's new controller emails asking for the files they submitted for last year's audit. The person who uploaded them has left, and nobody on the client side kept a copy.
Your team wants to help, and returning client-provided records on request is part of the job. But the request touches three obligations at once: data security, retention and independence. Reopen the old client portal and access lingers well past an engagement’s close. Become the place the client comes back to every year and you drift into the role of its record keeper.
The problem isn't any one portal, drive or policy. Client data has a life that runs well past the engagement, and most firms manage only part of it.
Every firm holding client data is working under several rules at once. A client data retention policy for accounting firms has to satisfy all of them, and "we turn off portal access when we're done" doesn't get you there on its own. Here's what each obligation requires, and where most firms fall short.
|
Obligation |
What it requires |
Where most firms fall short |
|
AU-C 230 (nonissuers) |
Retain audit documentation at least 5 years from the report release date |
Firm workpapers and client-provided files sit together, so retention gets applied to everything, including data the firm doesn't need to keep |
|
AS 1215 (PCAOB issuers) |
Retain audit documentation 7 years from the report release date |
Same pattern: the longer window becomes a reason to hold every client file, not just the documentation the standard covers |
|
ET §1.295.143, Hosting services |
Don't act as custodian of an attest client's data or records, which impairs independence |
"Reasonable period" for ending client access is never defined, so each team decides and portals stay open as a courtesy |
|
ET §1.400.200, Records requests |
Return client-provided records when the client asks for them |
Access ends with no handoff, so the client leaves without its own records and the requests start from scratch next year |
|
ET §1.700, Confidential client information |
Don't disclose client information without the client's consent |
Client files sit in email attachments and file-sharing links that nobody tracks or revisits |
|
GLBA Safeguards Rule |
Run a written information security program and report qualifying breaches to the FTC |
The program covers the client portal but not the copies in shared drives and inboxes |
|
State breach notification laws |
Notify affected individuals when personal information is exposed |
Without a map of where client data lives, the firm can't quickly scope an exposure |
Read together, they point one way: keep what your standards require, return what belongs to the client and hold as little else as you can. Every client file you keep past its purpose is breach exposure.
For attest clients, the hosting rule is the one most likely to catch a firm off guard. Since July 1, 2019, the AICPA's hosting services interpretation has treated certain custody of an attest client's data as a nonattest service that impairs independence.
The practical test is simple. If a client couldn't operate, or switch providers, without relying on data your firm is holding, your firm is likely providing a hosting service. Exchanging files during an engagement isn't the concern. Becoming the client's long-term custodian after it is.
That's why post-engagement data matters. It's where good intentions, like keeping a portal open as a courtesy, can quietly become an independence question.
[Pull quote] Handling client data well is a process, not a switch.
Clients have retention obligations of their own, and many assume their auditor has those records covered. It's an easy assumption to make: the auditor reviewed everything, and the files are sitting in the auditor's portal.
|
Client type |
Rule |
What it requires |
|
Employee benefit plans |
ERISA §107 |
Keep records supporting required filings for at least 6 years after the filing date |
|
Federal award recipients (governments, nonprofits) |
2 CFR 200.334 |
Retain award records for 3 years from submission of the final financial report |
The gap is sharpest in employee benefit plan, governmental, and nonprofit engagements, where clients often treat the auditor's files as their own. When a DOL inquiry or grant review comes up years later, the first call goes to the firm.
The firm can't fill that role without running into the hosting rule, so the gap stays open unless the client closes it. The firm's job is to make sure clients know that.
Staying compliant comes down to managing client data at four stages, each with one question your firm should be able to answer. Here's what we recommend at each stage, followed by five steps to make it firm policy.
|
Stage |
The question to answer |
The risk if you can't |
Obligations it covers |
|
1. Kickoff |
Where will client data live, and what happens to it after close? |
Expectations get set by habit, not policy |
ET §1.295.143, ET §1.400.200, ET §1.700 |
|
2. Active engagement |
Who has access to what, and can we prove it? |
Data spreads across email, drives and links |
ET §1.700, GLBA Safeguards Rule, state breach laws |
|
3. Close and handoff |
When does access end, and is that decision documented? |
"Reasonable period" becomes indefinite |
ET §1.295.143, ET §1.400.200 |
|
4. Long-term retention |
What do we keep, and what belongs to the client? |
The firm becomes the client's archive |
AU-C 230, AS 1215, GLBA Safeguards Rule |
Most data problems are decided on day one. If an engagement starts with files arriving by email, through a personal file-sharing link and in a portal, the firm will spend the rest of the lifecycle chasing copies.
At kickoff, define four things and put them in the engagement letter:
Saying this up front also makes the eventual end of access feel like a plan, not a surprise.
During fieldwork, the security surface grows fast. More staff, more requests and more client contacts all mean more places for data to land.
What good looks like:
This is where most firms improvise. The deliverable ships, and the client's access sits there until someone remembers to revoke it.
Instead of deciding engagement by engagement, set a firm-wide standard:
A documented, consistent standard is easier to defend in peer review than a series of individual judgment calls.
Retention is where two different obligations get confused.
The goal is a clean split: the firm retains what it must for its own documentation, and the client holds its own history somewhere the firm doesn't control.
A recommendation only helps if it outlasts the engagement team that made it. These five steps turn the stages above into firm policy.
Then bring the conversation to your risk, quality control and IT leaders. Client data governance touches all three, and none of them can fix it alone.
Clients need their history. Firms can't be the ones holding it. With Suralink you can automate engagement archiving on the schedule your firm sets, and give clients a place to keep their own history independently from your firm.
|
Approach |
Client keeps its history |
Firm stays clear of hosting |
What the client experiences |
|
Turn off portal access at close |
No |
Yes |
Files are gone, and next year's requests start from scratch |
|
Keep the firm's portal or shared drive open |
Yes |
No |
Convenient, but the firm becomes the custodian |
|
Send the client a download at close |
Partly |
Yes |
Files land in an inbox or on a laptop and leave with the next staff change |
|
Client-owned archive plus scheduled access removal |
Yes |
Yes |
Access ends on time, and prior-year files stay organized and on hand every year |
Firm-hosted tools like SharePoint, Google Drive or a firm-managed file-sharing portal recreate the hosting question the moment access persists past close. A client-owned archive changes who holds the data. The client keeps its records on a platform it controls, and the firm isn't the custodian.
That's the model behind Suralink's Client Data Vault, an optional subscription that clients purchase directly. It gives them ongoing access to their own past submissions, shown next to the current year's requests in the Suralink workflow. Suralink developed it in consultation with the profession’s governing bodies, and multiple Top 100 firms have vetted it.
Client Data Vault covers the client's side. Firm Policies covers yours. A firm admin sets the rule for engagement archival and deletion once, and Suralink applies it to every engagement.
Archiving used to be all or nothing, so teams skipped it to keep the files they needed next year. Firm Policies ends the client's access without taking the team's.
[Pull quote] "When I saw the Client Data Vault, I'm like, we need to connect on this. It can resolve an issue our teams are feeling and mitigate potential litigation risk for us." [Name, Title, Firm: attribution needed]
What is the AICPA hosting services interpretation? It's ET §1.295.143, effective July 1, 2019. It treats acting as the custodian of an attest client's data or records as a nonattest service that impairs independence.
How long can a firm keep client portal access active after an engagement? The guidance calls for a "reasonable period" without naming a number of days. Set a firm-wide default with your ethics or risk counsel, and document it for every engagement.
What questions should a firm ask about access controls and audit trails before selecting a client portal? Ask whether you can limit each user to what they need, remove access on a schedule, see who viewed or downloaded each file and export that history. Also ask how the portal handles client access after the engagement closes.
How should accounting firms compare secure file sharing with a client request portal? Secure file sharing moves files from one place to another. A client request portal ties each file to a specific request, tracks its status and keeps an audit trail. For audit work, that structure makes access easier to control and end.
Does this apply to non-attest clients? The hosting services interpretation is scoped to attest clients. For other engagements, follow your firm's own data policy.
What is a client-owned archive? It's a model where clients keep their own records on a platform they control. Clients keep their history, and the firm never becomes the host. Client Data Vault is one example built for accounting firm clients.
This article is for general educational purposes and is not legal or professional advice. Consult AICPA guidance and your firm's ethics or risk counsel for engagement-specific decisions.