Skip to content
DekkoSecure
All articles

Industry Insights · Accounting firms · 8 min read

Secure File Sharing for Accountants: Client Portals and the Rules

Secure file sharing for accountants: why email is risky, what the FTC Safeguards Rule, IRS Pub 4557 and APP 11 expect, and a client portal checklist.

Accountants hold the files identity thieves want: tax returns, financial statements, payslips and copies of driver's licenses and passports. The IRS warns that thieves have placed tax practitioners in their sights, yet many of those files still travel as email attachments.

This guide explains why email is a weak channel for client files, what the rules in the United States and Australia expect, and what to look for in a client portal or file sharing service.

What is secure file sharing for accountants?

Secure file sharing for accountants means exchanging tax returns, financial statements and ID documents through a service that encrypts them, limits each file to named people, can withdraw access and logs who opened what. The FTC Safeguards Rule requires US tax preparers to protect customer information, including encrypting it; in Australia, APP 11 and the TPB Code add security and confidentiality duties.

Why email attachments are a risk for client files

Once a tax return leaves as an attachment, the firm has no say over where copies end up.

  • Copies multiply. The file sits in the sent folder, the client's inbox and every device that syncs either mailbox.
  • Wrong recipients. One autocompleted address sends a return to someone else. The OAIC lists personal information "mistakenly given to the wrong person" as an example of a data breach.
  • No way back. A sent attachment can't be withdrawn, and the sender can't see if it was forwarded.
  • Phishing. The IRS tells tax professionals never to open attachments from unknown senders, including potential clients, without first making contact, by phone for example.

IRS Publication 4557 says tax professionals should "send only password-protected and encrypted documents" if they must share files with clients by email, or use SFTP instead. The sample security plan in IRS Publication 5708 goes further: personal data is not to be emailed without encryption or password protection, passwords go by a different channel, and the firm may use a password-protected portal.

What the rules expect in the United States

The FTC Safeguards Rule (16 CFR Part 314)

Under the Gramm-Leach-Bliley Act, professional tax preparers count as financial institutions. The FTC's Safeguards Rule names "an accountant or other tax preparation service that is in the business of completing income tax returns" as one, and IRS Publication 5708 says this applies regardless of size. The rule requires a written information security program, and several of its controls apply directly to file sharing:

  • Encryption of customer information in transit over external networks and at rest, or alternative controls approved by the firm's Qualified Individual if that isn't feasible (§ 314.4(c)(3)).
  • Access controls that limit staff to the customer information they need for their duties, and customers to their own information (§ 314.4(c)(1)).
  • Multi-factor authentication for anyone accessing any information system (§ 314.4(c)(5)).
  • Logging of authorized users' activity (§ 314.4(c)(8)).
  • Service provider oversight, with safeguards required by contract (§ 314.4(f)).
  • Breach notice to the FTC within 30 days of discovering a notification event involving at least 500 consumers (§ 314.4(j)), in effect since May 2024 according to the FTC's business guide.

Firms holding customer information on fewer than 5,000 consumers are exempt from four provisions, including the written risk assessment and incident response plan (§ 314.6), but not from encryption, access controls or multi-factor authentication.

IRS Publication 4557 and the WISP

IRS Publication 4557, "Safeguarding Taxpayer Data" (revised June 2024), is the IRS guide to data security for tax professionals. It says tax return preparers must create and enact security plans under the FTC Safeguards Rule, and that failing to do so may result in an FTC investigation. Its basic steps include multi-factor authentication and encrypting all sensitive files and emails.

That plan is the written information security plan, or WISP. IRS Publication 5708 gives a sample WISP for tax and accounting practices, including an electronic exchange policy and a list of staff authorized to access client data. It is a starting point, not a substitute for a plan built around the firm's own needs.

What the rules expect in Australia

Privacy Act 1988: APP 11

Australian Privacy Principle 11 in the Privacy Act 1988 requires an entity holding personal information to take reasonable steps to protect it from misuse, interference and loss, and from unauthorized access, modification or disclosure, including technical and organizational measures. The OAIC's APP 11 guidelines give encrypting data as an example, and expect more as the amount and sensitivity of information grows.

APP 11 generally applies to businesses with an annual turnover above $3 million, though some smaller businesses are covered. Tax file numbers are treated separately: the Privacy (Tax File Number) Rule 2015 applies to anyone holding records with TFN information, and the OAIC's TFN guidance names tax agents and accountants. TFN recipients must safeguard that information and restrict access to staff who need it; the OAIC suggests audit logs to monitor access.

The Notifiable Data Breaches scheme

Under the Notifiable Data Breaches scheme, an organization covered by the Privacy Act must notify affected individuals and the OAIC when a data breach is likely to result in serious harm, and must take all reasonable steps to assess a suspected breach within 30 calendar days. The scheme also covers TFN recipients for breaches involving TFN information, so a small practice can still have to notify.

The TPB Code of Professional Conduct

For registered tax and BAS agents, the Tax Practitioners Board's Code of Professional Conduct says that unless you have a legal duty to do so, you must not disclose information about a client's affairs to a third party without the client's permission. The TPB's guidance on Code item 6 says a third party can include offsite data storage, including cloud storage, and expects appropriate arrangements to prevent inadvertent disclosure.

Client portal and file sharing checklist for accountants

Whether it's called a client portal or secure file sharing, the same questions apply.

What to look forWhy it mattersRelated US rule or guidanceRelated Australian rule or guidance
Encryption in transit and at restProtects files if a laptop is lost or a server is breachedSafeguards Rule § 314.4(c)(3)APP 11; OAIC lists encryption as a technical measure
Each client sees only their own filesKeeps one client's documents away from another§ 314.4(c)(1) access controlsAPP 11; TFN Rule access limits
Upload links that need no client accountClients stop falling back to email attachmentsIRS Publication 4557 email guidanceAPP 11 reasonable steps
Multi-factor authenticationA stolen password alone doesn't open client files§ 314.4(c)(5)APP 11 reasonable steps
Expiry dates and instant revocationAccess ends when the engagement doesSupports § 314.4(c)(1)TPB guidance on inadvertent disclosure
Audit log of views and downloadsShows who opened what, which helps assess a suspected breach§ 314.4(c)(8) loggingOAIC TFN guidance on audit logs; NDB assessment
eSignatures for engagement lettersKeeps a record of client permission with the fileNot addressed by the ruleTPB: permission by signed engagement letter or consent
Known hosting location and provider termsLets the firm oversee the provider and tell clients where files are held§ 314.4(f) service providersTPB: a cloud storage provider can be a third party

Where DekkoCORE fits

Accounting firms can use DekkoCORE to collect and share client files. Clients upload through a submission link or QR code, with no account or app. Clients added as External Members see only the folders shared with them and can't see other external parties. Files are encrypted on the user's device with AES-256 keys before upload, and DekkoCORE never has the keys to open them.

Any share can have an expiry date and be revoked instantly. Engagement letters can go out as eSignature requests. Every view, download, signature and version is logged, and the audit log exports as CSV. Firms can require external users to use two-factor authentication or passkeys, and choose hosting in Australia, the United States or Canada. These controls can support a WISP or an APP 11 program; they don't replace one. See also our guide to secure file sharing and DekkoCORE for financial services.

Common questions

Frequently Asked Questions

Is it safe to email tax returns to clients?

Once sent, an email attachment can't be withdrawn, can reach the wrong person and stays in every mailbox it passes through. IRS Publication 4557 advises sending only password-protected and encrypted documents if email must be used, or using SFTP instead.

Does the FTC Safeguards Rule apply to small accounting firms?

Yes. The rule names accountants and other tax preparation services that complete income tax returns as financial institutions, and IRS Publication 5708 says this applies regardless of size. Firms with customer information on fewer than 5,000 consumers are exempt from four provisions, but not from encryption or multi-factor authentication.

What is IRS Publication 4557?

IRS Publication 4557, "Safeguarding Taxpayer Data", is the IRS guide to data security for tax professionals. It covers basic security steps, spotting and reporting data theft, and complying with the FTC Safeguards Rule, including the written information security plan (WISP).

Do Australian accountants have to comply with the Privacy Act?

Businesses with an annual turnover above $3 million are covered, and some smaller businesses are too. A practice holding client tax file numbers is a TFN recipient under the Privacy (Tax File Number) Rule 2015, and registered tax agents must also meet the TPB Code's confidentiality obligation.

What is the difference between a client portal and secure file sharing?

A client portal is usually a website where clients sign in to exchange documents with one firm. Secure file sharing is the broader practice of exchanging files with encryption, access controls, expiry and an audit trail, through a portal, an upload link or a shared folder.

Like to learn more?

Talk to our team about protecting your most sensitive files and evidence.