Oregon-based · Serving organizations nationwideoffice@harrisfcs.com · 541-204-0597
Tax & Accounting Security

Secure client document sharing: a practical guide for tax and accounting firms

Secure client document exchange is not just a portal subscription. It is a repeatable process for sending, receiving, storing, and retiring sensitive files.


Why the handoff matters

A tax return may be prepared inside a well-managed application, yet the supporting documents arrive through personal email, a text message, or an unrestricted cloud link. The weak point is often not the tax software. It is the path documents take into and out of the firm.

Tax and accounting offices routinely handle Social Security numbers, financial statements, payroll records, identity documents, and other sensitive information. A secure document-sharing process should be easy enough for clients to use and controlled enough that staff can explain who received a file, who could open it, and when access should end.

Choose a primary channel instead of improvising

A client portal or managed file-sharing service is usually a better default than collecting attachments across several employee inboxes. The important features are not the vendor's marketing claims but the controls available: encryption in transit and at rest, account authentication, access restrictions, administrative oversight, and an understandable retention process.

Make the approved channel obvious in appointment reminders, onboarding messages, and document requests. Staff should know where to direct clients who send sensitive attachments to ordinary email. A secure system nobody uses is not a useful control.

Treat links as access permissions

A link can be convenient without being private. Some cloud platforms allow anyone holding a link to view or download its contents. Other links require a specific authenticated recipient. Those settings are not interchangeable.

For sensitive client files, favor access limited to the intended recipient or client account. Disable anonymous or public sharing where the workflow does not require it. Apply expiration dates when available and useful, and avoid granting edit rights when a client only needs to download a completed document.

Review the default sharing configuration before the busy season. A secure default reduces the number of judgment calls employees must make under deadline pressure.

Authentication matters on both sides

Protect staff accounts with multifactor authentication (MFA), especially accounts that can access many clients' files. Use individual staff identities instead of a shared office login so permissions can be reviewed and departures handled cleanly.

For client-facing portals, select an authentication process that is proportionate to the sensitivity of the information. A portal that relies solely on a reusable link forwarded through email may not provide the same assurance as one requiring the intended client to sign in.

Plan for clients who lose access to an account. A help-desk request to change an email address or reset access should include an identity-verification procedure; otherwise an attacker may simply target the recovery process.

Email is useful for notifications, not necessarily for the files

Email can notify a client that a document is ready without including the document itself. Keep sensitive personal information out of subject lines and unnecessary message bodies. An ordinary email message and a properly configured secure portal do not provide the same controls.

Sometimes an encrypted attachment is the practical fallback. If the firm uses one, verify that the file is actually encrypted, choose a strong unique password, and deliver that password through a separate verified channel. Merely putting a password in the same email as the attachment defeats much of the point.

The IRS's guidance on secure email communication emphasizes protecting identifying information and encrypting sensitive attachments in applicable email exchanges. Its specific procedures for communicating with IRS employees should not be mistaken for a blanket approval of ordinary email for client document exchange.

Keep incoming documents organized

Receiving a file securely is only half the workflow. Decide where the authoritative copy belongs, who may move it, and how duplicates are handled. A download folder on an employee's laptop should not become an unofficial archive of client tax records.

Use documented naming and storage conventions appropriate to the firm's software. Limit access by role and client assignment when the platform supports it. If staff must download files for processing, consider device encryption, managed endpoints, and cleanup of temporary copies.

The IRS's Protect Your Clients; Protect Yourself resources and its tax-security checklist emphasize safeguarding taxpayer data as a continuing operational responsibility. A document workflow is one concrete place to turn that guidance into daily practice.

Be deliberate about retention and deletion

A link that expires is not the same thing as deleting the underlying file. A client portal may retain documents, backups, versions, or audit records after the client can no longer see them. Understand those differences before promising that a file has been removed.

Set retention periods based on actual business, contractual, and legal obligations. Then document what happens when a client leaves, a matter closes, or the firm changes platforms. Deletion should be coordinated with required recordkeeping rather than performed automatically just because a project ended.

Avoid the wrong-client problem

Not every disclosure involves an attacker. A staff member can upload a return to the wrong client folder or select the wrong recipient from a list. These ordinary mistakes are worth designing around.

Use clear client identifiers, restrict broad folder access, and build a quick recipient check into the release process. For especially sensitive packages, consider a second-person verification step. The goal is a short reliable habit, not a cumbersome approval chain for every routine file.

Prepare for suspicious documents and messages

Attackers may impersonate prospective clients and send attachments or links described as tax records. The IRS warns that phishing and malicious attachments targeting tax professionals can lead to credential theft, malware, and unauthorized access to taxpayer data.

Teach staff how to report unexpected files, suspicious sign-in pages, and requests to bypass the normal portal. Do not assume that a message is safe because it uses a familiar client name. Verify unusual requests through a known contact method rather than a phone number supplied in the suspicious message.

Audit what the system can actually tell you

When evaluating a portal or file-sharing system, ask whether administrators can identify who uploaded a document, who accessed it, when permissions changed, and which external links remain active. Audit logs vary by product and license, so verify the capabilities rather than assuming they exist.

Logs also need an owner. If a client reports an unfamiliar download or the firm discovers a file was sent to the wrong person, someone should know where to investigate and how to preserve the relevant information.

A workable checklist for a small firm

  • Choose one approved channel for sensitive document exchange.
  • Require MFA for staff and protect client authentication.
  • Limit sharing to intended recipients; avoid unnecessary public links.
  • Keep sensitive details out of email subject lines and messages.
  • Verify recipients before releasing documents.
  • Store authoritative copies in managed business systems.
  • Control temporary downloads and local copies.
  • Define retention, deletion, and client-exit procedures.
  • Review active external links and user access periodically.
  • Document how to handle suspicious files and mistaken disclosures.

Assign responsibility for these controls and review them periodically. A five-person office may use a modest portal and a simple written procedure; a larger firm may need more granular access and auditing. The principle is the same: make secure sharing repeatable.

Connect the workflow to your WISP

A written information security plan (WISP) should describe how the firm protects client information in practice. Document exchange touches access control, encryption, employee training, service providers, retention, and incident response. It should not be treated as a separate convenience feature.

For firms subject to the FTC Safeguards Rule, the broader security program must reflect the organization's risks and applicable requirements. This article is an operational guide, not a determination of a firm's legal obligations. Our tax and accounting IT and WISP services focus on turning written controls into working processes.

Further reading

Is your client document workflow consistent?

HarrisFCS can help review your file-sharing configuration, staff access, and document-handling procedures as part of practical IT and WISP management.