The problem

Tax prep is 80–90% knowledge work but carries preparer penalties (§6694/§6695) and the criminal §7216 data rule, so naive automation is dangerous.

What you get

Returns prepared and positions authority-classified; below-standard positions disclosed or escalated; a credentialed preparer signs and the taxpayer signs Form 8879 before e-file.

The flow

Intake to outcome. 🤖 steps run automatically; 🧑‍⚖️ steps are where a named human signs off the judgment calls.

1

🤖 Intake taxpayer documents (W-2 / 1099) and statements

agent intake · Doc intake (W-2/1099)Bank / brokerage feed
2

🤖 Compute the return and classify each position's authority (substantial authority / reasonable basis)

agent preparer · Tax engine
3

🤖 Check Circular 230 due diligence, §7216 data-use consent, below-standard positions and jurisdiction scope

agent compliance · Jurisdiction / law DB
4

🧑‍⚖️ A credentialed preparer signs (PTIN); the taxpayer signs Form 8879 before filing Human checkpoint

Credentialed preparer (PTIN / EA / CPA)
5

🤖 Transmit the signed return via IRS e-file (MeF)

agent filer · IRS e-file (MeF)
6

🤖 Track acceptance / rejection and handle notices

agent monitor · IRS e-file (MeF)

Agents & tools

Doc intake (W-2/1099) stub today → OCR + parsers
Bank / brokerage feed stub today → Plaid
Tax engine stub today → CCH
Jurisdiction / law DB stub today → legal data vendor
IRS e-file (MeF) stub today → IRS MeF

Connectors run as sandbox stubs today — flip to the real provider to go live.

Human checkpoints

Credentialed preparer (PTIN / EA / CPA) — A credentialed preparer signs (PTIN); the taxpayer signs Form 8879 before filing

The autopilot escalates the judgment calls to a qualified human — the rest is straight-through.

Why it's safe to let it run

Every autonomous decision is logged — who · what · confidence. Signed human checkpoints and a built-in compliance reviewer enforce the rails, so the outcome holds up to an audit, not just a demo.

Start your tax autopilot Compare all autopilots ↗