Client intake is where a CPA firm meets new people and accepts their files: onboarding a new client, and gathering documents for each engagement. It is also where the firm decides what personal information to collect and where it will be stored. That makes intake a security process as much as an administrative one. This article covers why intake attracts attackers, how to verify new contacts, what to collect, and how to control where incoming files end up.
Why intake attracts attackers
Intake staff are expected to open documents from people they have never met. IRS Publication 4557 warns that phishing thieves may pose as a prospective client, and that spear phishing targets a specific firm, perhaps after finding staff email addresses on the firm’s website. Its advice is direct: never open or download attachments from unknown senders, including potential clients, and make contact first, for example by phone.
What intake collects also makes it valuable. Tax organizers, W-2s, identity documents and bank details are exactly what identity thieves need to file fraudulent returns.
Verify new contacts before accepting files
A short routine helps:
- Before accepting documents from a new contact, confirm who they are through a channel you choose, such as a call to a number from an independent source or a scheduled video meeting.
- Send new contacts an invitation to your portal instead of accepting attachments by email.
- Treat urgency, unusual requests and pressure to skip steps as warning signs, not reasons to hurry.
- Route unexpected attachments to a named person for review rather than opening them at the front desk.
Collect only what you need
The sample plan in IRS Publication 5708 states that the firm will collect only the personal information necessary for its legitimate business needs, and limit access to staff whose duties require it. The FTC Safeguards Rule, which covers tax preparers and accountants under its definitions, similarly limits authorized users to the customer information they need and calls for periodic review of data retention in section 314.4. This is general information, not legal advice.
Review your intake checklists and organizers with that in mind. If a copy of an identity document or a full account number is not needed for the engagement, do not ask for it. Data the firm never collects cannot be stolen from it.
Control where intake files land
Incoming documents tend to pass through several temporary locations before they reach the client folder. Each one needs a rule.
Shared intake mailboxes
Give staff access to the shared mailbox through their own accounts, not a shared password. Individual access keeps a record of who opened, moved or forwarded each message, and makes removing someone’s access a single step.
Scanners and multifunction printers
Scan to a protected folder with restricted access, not to an open network share or to any email address typed at the device. Publication 5708’s sample plan also calls for changing default passwords on printers, copiers and other connected devices.
Downloads folders and desktops
Files downloaded from a portal or saved from email should be moved to the client folder and deleted from the local copy the same day. Redirecting or regularly clearing download folders on intake workstations makes this the default rather than a habit staff have to remember.
Paper and removable media
Publication 4557 recommends a clean desk policy. Keep paper documents in locked storage when unattended. For USB drives clients bring in, scan them before opening or ask for the files through the portal instead; Publication 5708’s sample plan disables AutoRun on USB ports so a drive cannot start a program on its own.
Protect the devices that do intake
Front desk and intake workstations open a steady stream of files from outside the firm. Keep them fully updated, remove local administrator rights from daily accounts, and use endpoint detection and response rather than antivirus alone. Titan Tech deploys SentinelOne for EDR and pairs it with Huntress for SIEM and managed detection and response; see endpoint security.
Train the people who handle intake
The routine only works if staff know it and feel able to slow down. A short session on the intake lures Publication 4557 describes, plus a clear rule about whom to ask when something looks wrong, is easier to follow than a long policy. Our security awareness training covers phishing and verification.
What to do next
List every route documents take into the firm, including the informal ones: email replies, the scanner, USB drives, personal phones. For each route, decide where files land and who cleans them up. Then trim your intake checklists to what each engagement actually needs. If you want an outside view of your intake devices and accounts, you can request a Blind Spot Scan.