Where Should a Seattle CPA Firm Start With AI?
A Seattle CPA firm should start AI where work stalls, often intake, and settle Washington’s client consent rule and breach deadline before files reach a tool.
In this guide
A Seattle CPA firm should start with a recurring task that has a visible cost, clear review criteria, and a responsible owner. Client document intake is a strong candidate when incomplete files repeatedly stop preparation. Bookkeeping assistance may come first in a client accounting services practice. A specialist tax team may get more value from source-grounded research. The right starting point follows the firm's work, not a universal order of tools. Whichever comes first, settle two Washington rules before client files reach an AI tool: client consent under the Board of Accountancy’s confidentiality rule, and the state’s 30-day breach notice deadline.
For a managing partner, the decision is which small workflow adds more capacity than verification work. Compare tasks within one service line and check what the firm’s software already does.
In Thomson Reuters' 2026 AI in Professional Services Report, organization-wide AI use across professional services almost doubled to 40% in 2026, from 22% in 2025, in a survey of more than 1,500 respondents in 27 countries.
See an illustrative client-document handoff with entity and period checks.
Use the reason work stops to choose the first use case
Start with recent engagements and record the actual reason for each interruption. Waiting on a client is different from staff searching a portal. A preparer blocked by an unclear transaction is different from a partner's review backlog. They can all appear as a late engagement while needing different remedies.
This decision table is a proposed selection method, not a ranking of returns available to every firm.
| If the recurring constraint is… | Consider this first | What must remain visible |
|---|---|---|
| Files arrive with unclear entities, periods, or document types | AI-assisted classification and an intake checklist connected to the client portal | Source file, assigned engagement, missing items, and administrator review |
| Staff repeat known requests because no one owns the follow-up | Practice-management tasks and approved reminders; AI may add little | Last request, next action, due date, and communication owner |
| Bookkeepers repeatedly propose the same transaction coding | Suggestions within the existing ledger workflow | Supporting document, prior treatment, reviewer decision, and unresolved purpose |
| Qualified staff spend substantial time locating current authority | A research tool evaluated on the firm's actual technical questions | Applicable period, jurisdiction, primary sources, and professional analysis |
| Completed work waits for a partner | Review capacity, scheduling, and a better handoff brief | Questions needing judgment and the reviewer's available time |
A firm can legitimately choose research first. Its value should be demonstrated on the technical work being done, including the time needed to check citations and conclusions. Do not rebuild a working intake process to satisfy an AI roadmap.
What an intake pilot should actually deliver
Choose one repeatable engagement type, such as monthly bookkeeping onboarding. Agree the client entity, reporting period, required accounts, expected documents, and readiness owner. Use the existing portal for collection and the practice-management system for status where supported. Before building a separate pipeline, ask whether current checklist, request, and document features can resolve the problem.
The proposed output is a preparation packet: the approved checklist, received files, source-linked classifications, unresolved exceptions, and assigned preparer. It is not a certification that the records are correct or sufficient for every professional purpose. The administrator checks collection; engagement staff decide whether the material supports the work.
This fictional example shows why those responsibilities matter. A client uploads a May bank statement to a June engagement, plus a revised sales export with the same filename as the earlier version. The portal records two successful uploads. The AI-assisted view proposes May as the statement period and flags two versions of the sales export.
The June statement stays outstanding. The administrator confirms the mismatch and approves a specific follow-up. The bookkeeper identifies which sales export should be used and retains the superseded version. The engagement does not advance merely because the number of files matches the number of checklist items.
Compare capacity in the weeks when it matters
The following capacity calculation is illustrative; its inputs are assumptions, not a firm result. Suppose an administrator handles 80 document packets in a month at 18 minutes each, including current rework. That is 24 hours. In the proposed process, every packet needs 7 minutes of review, and 20% need another 10 minutes to resolve an exception.
Expected handling would be 80 × (7 + 0.20 × 10) ÷ 60 = 12 hours, releasing 12 hours of capacity before training and ongoing administration. If routine review takes 13 minutes instead, expected handling rises to 20 hours and the capacity difference falls to 4 hours. The business case is sensitive to the work that remains.
Replace these assumptions with observed times. Count correction, supervision, duplicate-system entry, and maintenance. Check whether the capacity appears during a deadline week or a quiet period, and whether the next team can use it. Available hours are not a payroll reduction, additional accepted engagements, or realized cash savings until those outcomes occur.
Approve the data use before connecting client files
In its August 2026 security reminder, the IRS says tax and accounting professionals must maintain a written information security plan, including attention to service-provider safeguards. A new AI connection belongs in that review.
The same IRS release explains why. Under the Gramm-Leach-Bliley Act, tax and accounting professionals are treated as financial institutions that must implement a data security plan; the FTC expects firms to select service providers that can maintain appropriate safeguards and to require them by contract; and covered institutions must generally report security events affecting 500 or more people to the FTC within 30 days of discovery, a requirement the FTC added to its Safeguards Rule in 2023.
Have the firm's security and professional-practice owners examine the actual service terms, retention, subcontractors, incident handling, and any required client consent. A promise that data is not used for training answers one question; it does not settle all the others. Test early configurations with synthetic or appropriately de-identified material.
Put these questions to each provider in writing:
| Ask the AI provider | Why it matters to the firm |
|---|---|
| Will the contract require you to maintain appropriate safeguards for client data? | The FTC expects firms to choose providers that can safeguard client information and to require it by contract. |
| Where is client data stored, for how long, and which subcontractors can reach it? | Retention and subcontractor access belong in the firm's written information security plan. |
| How quickly will you tell us about a security incident? | Covered firms generally must report qualifying events to the FTC within 30 days of discovery, and cannot report what a provider has not told them. |
| Can access be limited by engagement, and can we export or delete a client's data? | Confidential material must reach only the engagement it belongs to, and the firm needs a way out of the tool. |
The CPA.com AI resource center includes provider due-diligence and build-versus-buy resources. A vendor’s presence there does not establish suitability for your engagement.
For work that reaches a client, identify the reviewer and what they must verify. Technical conclusions need the appropriate authority, context, and professional analysis. Calculations should be checked in the relevant accounting or tax system. An AI-generated memo, reconciled-looking table, or completed checklist is an intermediate output.
What Washington adds before client files reach a tool
Start with confidentiality. Washington’s Board of Accountancy rule says a licensee in public practice, a term that includes CPA firms and their employees, shall not disclose any confidential client information without the specific consent of the client (WAC 4-30-050). Its listed exceptions, such as legal process, quality review and a practice sale, do not mention technology providers. Whether sending files to an AI provider is a disclosure under the rule is a question for counsel; the cautious course is the client’s specific consent, for example in the engagement letter, before client files reach the tool.
The FTC report in the provider table above is not the only deadline for a firm with Washington clients. A firm that conducts business in Washington and owns or licenses personal information must notify each affected Washington resident no more than 30 calendar days after discovering a breach, subject to limited exceptions such as a delay requested by law enforcement, and must notify the Attorney General no more than 30 days after discovery when more than 500 Washington residents receive notice. A provider that holds data it does not own must tell the owner immediately after discovery (RCW 19.255.010). The notices must list, among other items, the types of personal information involved and, if known, the date of the breach and the date it was discovered. Before any client file reaches an AI tool, get the provider's written commitment to immediate notice and to supplying those details.
In Chicago
Illinois reaches a similar duty by another route: its accountancy rules adopt the AICPA Code of Professional Conduct, 2015 edition, as the minimum standard of conduct (68 Ill. Adm. Code 1420.200). That code bars disclosing confidential client information without the client’s specific consent, but before files go to a third-party service provider it accepts either that consent or a confidentiality contract with reasonable assurance of the provider’s safeguards (AICPA Code 1.700.001 and 1.700.040). Washington’s rule lists no contract route, and its board rules prevail where professional standards differ (WAC 4-30-048), so for a firm with clients in both states, the client’s specific consent is the one course both rules accept.
Make the first decision small enough to reverse
Give the pilot one service-line owner and a defined end point. Compare total handling time, wrong-entity assignments, missed document gaps, and files returned by preparers. Review some outputs the system labels complete, because a queue of flagged exceptions will not reveal everything it missed. Stop if confidential material reaches the wrong engagement or the process silently loses a file.
Expand only when the team can operate the workflow, explain its limitations, and demonstrate an improvement worth its ongoing cost. If the trial shows that client responsiveness is the constraint, revise the collection process. If it shows that partner review is full, deal with that capacity before accelerating more preparation work.
The accounting and professional-services guide shows how collection, preparation, and professional handoffs connect.
Quick answers
Where should a CPA firm start with AI?
With a recurring task that has a visible cost, clear review criteria and a responsible owner. Client document intake is a strong candidate when incomplete files stop preparation; bookkeeping suggestions or tax research can come first when those are the constraint.
Can CPA firms use AI with client data?
Yes, once the tool is covered by the firm’s written information security plan, which the IRS says federal law requires, and the provider is bound by contract to safeguard client data, as the FTC expects.
Does a Seattle CPA firm need client consent before using AI on client files?
Washington’s Board of Accountancy rule bars disclosing confidential client information without the client’s specific consent, and its exceptions do not mention technology providers. Have counsel confirm whether a tool counts as disclosure, or get the consent in the engagement letter.
Does AI replace review by a CPA?
No. An AI-generated memo, table or checklist is an intermediate output that a qualified reviewer checks against the right authority, and calculations belong in the accounting or tax system.
Sources
- Thomson Reuters' 2026 AI in Professional Services Report · thomsonreuters.com
- August 2026 security reminder · irs.gov
- FTC added to its Safeguards Rule in 2023 · ftc.gov
- CPA.com AI resource center · cpa.com
- WAC 4-30-050 · app.leg.wa.gov
- RCW 19.255.010 · app.leg.wa.gov
- 68 Ill. Adm. Code 1420.200 · ilga.gov
- AICPA Code 1.700.001 and 1.700.040 · pub.aicpa.org
- WAC 4-30-048 · app.leg.wa.gov
Revision note · October 5, 2026: Refocused on Seattle; removed references to other Washington cities.
How we research and review these guides
Put the ideas to work in your business.
We provide AI consulting and implementation for accounting and professional services firms. Bring us the process that is slowing your team down and the systems involved. We can assess the problem with you and discuss a practical implementation.
Discuss your project →Still exploring? Explore the Workflow Opportunity Workbook →