Accounting AI from the ITECS Dallas team
AI Solutions for Accounting and CPA Firms
ITECS builds governed AI for regional and local CPA firms of 50 to 300 people. A tax return readiness agent checks each client's documents against last year's return, tracks expected K-1s, drafts missing-items requests for staff approval, and hands preparers a source-linked packet, while people keep each determination, signature, and filing.
Firms already pay for extraction inside their tax software. What busy season lacks is a governed layer across the portal, document system, workflow tool, and tax package that knows which returns are truly ready, which are blocked and why, and who needs to hear from the client.
Accounting signal map
Tax + audit + trust
Tax
Intake, readiness, and K-1 tracking
Audit
PBC requests and evidence matching
Trust
Section 7216, WISP, and reviewer sign-off
Busy-season IT behind accounting AI
Accounting AI from a team that already plans Dallas CPA firms' busy season.
ITECS supports Dallas accounting firms with tax-season readiness, Microsoft 365 governance, secure client document workflows, and backup planning for partners, staff, and seasonal users. ITECS AI keeps the same boundary: it does not replace your tax software publisher, your compliance counsel, or the professionals who sign. Read about ITECS IT services for accounting firms.
June 24, 2026
The IRS Office of Professional Responsibility issued its first guidelines for responsible AI use in tax practice, tied to Circular 230 duties.
IRS OPR Issue 2026-1965%
Share of AICPA members who prepare returns that use AI for tax research; 32% use it for client communication.
The Tax Adviser, Aug. 2026Aug. 2026
The Texas board told CPAs that professional responsibility cannot be delegated to software and that AI-generated analyses are not audit evidence.
Texas State Board Report
Operating pressure
Accounting AI Starts With Capacity, Readiness, and Trust
The first step is not picking a model. It is finding where preparers wait on incomplete returns, where managers chase status by email, and where client data needs firmer boundaries before AI touches it.
Capacity pressure
A thinner talent pipeline and steady deadline volume leave less room for preparers to sort documents and chase clients.
- Preparers starting returns that turn out to be incomplete
- Status chased through email and spreadsheets
- Seasonal staff onboarded during the busiest weeks
- Reviewers buried in rework from missing items
Readiness pressure
K-1s arrive late or corrected, brokerage statements are reissued, and organizers come back half answered.
- Expected K-1s tracked from memory
- Corrected 1099s that arrive after preparation starts
- Generic reminder blasts instead of specific requests
- Extension decisions made in the final days
Trust pressure
AI is only usable when return information stays inside Section 7216, the firm's written security plan, and professional review.
- Consumer AI accounts outside the firm's written security plan
- Third-party AI vendors not yet vetted or contracted
- Client consent and engagement-letter disclosure questions
- AI output that must be verified before it reaches a client or the IRS
Example busy-season signal board
The Metrics an Accounting AI System Should Make Visible
A tax readiness program should show the managing partner which returns are ready, which are blocked and why, and how many extensions are coming. These figures are illustrative for a fictional 140-person CPA firm on March 30 of busy season; discovery replaces them with the firm's own data.
Readiness bridge
Returns blocked by cause
Returns ready for preparation
1,512
63% of 2,400 individual engagements, packets built
Returns blocked on client items
588
24.5% of engagements, broken down by cause
Client follow-ups awaiting approval
146
Drafted by the agent, not yet sent
Projected extensions
410
Mostly late K-1s and corrected brokerage statements
What leadership sees
- Ties each blocked return to its cause and the client request that clears it
- Separates returns likely to clear before the deadline from likely extensions
- Routes client messages and readiness releases for staff approval
Accounting AI use cases
Where AI Creates Measurable Value for CPA Firms
Start where the documents already arrive and a professional already approves the result: tax readiness, audit requests, close work, and client communication.
Tax Return Readiness & Intake
Classify portal and email uploads, compare them with last year's return and the organizer, and mark each return ready, blocked with a reason, or not started.
Preparers start only complete returns
K-1 Tracking & Extension Forecasting
Build the expected K-1 list from last year, log arrivals and corrected copies, and project which returns will need extensions.
Extension calls made weeks before the deadline
Client Missing-Items Requests
Draft specific, plain-language requests that list exactly what is missing, held for staff approval before anything goes out.
Fewer generic reminders, one auditable record
Audit PBC & Evidence Requests
Roll forward last year's PBC list, track open requests, and match received documents to selections while auditors perform and conclude the procedures.
Less request administration for seniors
CAS Month-End Close Assistant
Surface uncategorized transactions, unreconciled items, and unusual variances, and draft client questions and proposed entries for accountant approval.
A standard close with exceptions queued
IRS Notice Triage & Response Drafts
Classify the notice and its deadline, pull the related return and workpapers, and draft a response for an EA or CPA to review.
Each notice logged with its deadline on day one
Engagement Letters & Consent Forms
Draft engagement letters from firm templates with the firm's third-party disclosure language and any consent form counsel has approved.
Consistent letters with required language intact
Tax Research With Citation Checks
Summarize authorities and draft memos as desktop agents, with each citation checked against the primary source before use.
Faster first drafts, mandatory cite checks
Firm Knowledge Agent
Answer staff questions from the firm's procedures manual, review standards, written security plan, and software how-tos, with links to the source.
Consistent answers for seasonal staff
Flagship enterprise agent
Tax Return Readiness Agent: Only Complete Returns Reach a Preparer
An illustrative solution design, not a reported client result. The agent prepares, checks, and routes; people decide, prepare, review, sign, and file.
Ingest and classify uploads
The agent fingerprints each file from the portal or intake mailbox, flags duplicates, corrected forms, and unreadable scans, and classifies W-2s, 1099s, 1098s, and K-1s, using existing extraction output where the firm has it.
Check completeness against last year
It compares what arrived with last year's payers, entities, and accounts and the organizer answers, then lists expected items not received, items not expected, and the K-1s still outstanding.
Flag variances, not conclusions
Year-over-year changes above firm thresholds become review flags for the preparer, never tax positions, which keeps the agent to auxiliary work rather than substantive determinations.
Staff approve the client request
The agent drafts a specific missing-items request and holds it in the review queue. Staff approve before anything reaches the client, and a tax senior confirms readiness.
Human approval point
Build the packet and route
It saves a bookmarked source binder and an input worksheet that links each value to its page, then updates the workflow tool to ready for preparation or blocked with a cause.
What it reads
- Client uploads from the portal or document system and the intake mailbox
- Last year's return and the organizer answers
- Engagement status and assignments from the workflow tool
- Extraction output from tools the firm already licenses, such as SurePrep or CCH Axcess Scan
What it never does on its own
- Files, e-files, or signs a return, or submits Form 8879
- Writes into a return in the tax software on its own
- Makes a tax determination or communicates a tax position
- Sends a client message without staff approval
Two kinds of accounting agents
Firm-Wide Agents and Desktop Agents
ITECS builds two kinds of agents for CPA firms. Each has its own owner, controls, and rollout path.
Engineered by ITECS
Enterprise hosted agents
Engineered by ITECS, connected to the portal, document system, workflow tool, and tax software through supported import, export, or API methods, and run in a governed hosted environment with a review portal and audit trail. Firm leadership owns them.
- Tax return readiness, K-1 tracking, and client follow-up
- Audit PBC and evidence requests
- CAS month-end close assistance where independence allows
Built with your team
Personal desktop agents
Built with staff on business plans of Microsoft 365 Copilot, ChatGPT, or Claude, which the vendors state do not train on business inputs by default, then rolled out through training under the firm's AI policy. Department heads own them.
- Client status updates and extension explanations for staff review
- Engagement letter and proposal drafts from firm templates
- IRS notice first drafts for EA or CPA review
Systems accounting agents read
- UltraTax CS
- CCH Axcess
- CCH ProSystem fx
- Lacerte
- SurePrep
- SmartVault
- ShareFile
- Karbon
- XCM
- Suralink
- Caseware
- QuickBooks Online
- Microsoft 365
Technologies ITECS evaluates and integrates through supported import, export, or API methods confirmed in discovery; listing a product does not imply a formal partnership or a native connector.
Start here
Accounting AI Readiness Assessment
ITECS starts by mapping the business case, client-data flows, vendor terms, and governance model before recommending an agent build.
Map busy-season priorities
Identify where returns stall, where staff chase status, and which deadlines drive extensions and rework.
Trace client data and your WISP
Document where return information lives, which tasks need it, and how each AI service fits Section 7216 and the firm's written security plan.
Rank use cases by economics
Prioritize by returns cleared, reviewer hours returned, extensions avoided, and feasibility, starting where documents already arrive.
Write the governed path
Document the AI policy, approval points, the consent position from counsel, audit logging, and vendor terms before any production build.
Governance
Built Around Section 7216 and Professional Review
ITECS designs accounting AI around the rules that govern return information and the professionals who stay responsible for each return.
Return information boundaries
Section 7216 limits how preparers use and disclose return information. Whether an AI vendor fits the auxiliary-services exception is unsettled, so the design minimizes exposure and counsel decides consent.
- US-only processing and storage, with offshore access excluded
- Enterprise terms that exclude model training on firm data
- Written Section 6713 and 7216 confidentiality terms with ITECS and subprocessors
- A consent workflow in the IRS format if counsel requires one
Professional responsibility
IRS guidance under Circular 230 and the Texas board both treat AI output as a draft that a qualified professional verifies.
- Preparers, reviewers, and partners keep each judgment and signature
- The agent recorded as an overseen service provider in the firm's WISP
- Independence review before any agent touches an attest client's systems
- SOC 2 Type II applies only if Promus managed cloud hosting is selected
Security
Security for Accounting AI Workflows
Accounting AI touches tax return information, payroll files, and client financial records. ITECS designs these systems with MFA, activity logging, retention rules, and staff approval before anything reaches a client or the IRS.
FAQ
Accounting AI FAQ
Does using AI on client tax data violate Section 7216?
Section 7216 bars preparers from using or disclosing return information without written consent unless an exception applies, such as a US provider of auxiliary services that makes no substantive determinations. Whether an AI vendor fits is unsettled, so ITECS designs for US-only processing, no training on your data, and written confidentiality terms, and your counsel makes the consent call.
Will the agent prepare, sign, or file returns?
No. It classifies documents, checks completeness against last year, drafts follow-ups for staff approval, and hands preparers a source-linked packet; preparers, reviewers, and partners keep each judgment and signature.
How does this fit our WISP and the FTC Safeguards Rule?
Tax preparers are financial institutions under the Safeguards Rule, so the agent is documented as an overseen service provider in your WISP, with MFA, activity logging, retention rules, and incident response coverage. IRS Publication 5708 is the template many firms use.
We already pay for SurePrep or CCH Axcess Scan. Why add this?
Those tools extract document data into your tax software. The readiness agent works around them, using their output to decide which returns are complete, track K-1s, draft requests, and update your workflow tool, and discovery maps what your licenses already cover.
Can we use it on audit or CAS clients?
Yes, with guardrails. An audit agent can roll forward PBC lists and match documents to selections, but the Texas board reminds firms that AI-generated analyses are not audit evidence, and your independence partner signs off before any agent touches an attest client's systems.
