07 — How Tax Software Actually Works

The mechanics — how a return is built, transmitted, and secured. The concrete substance behind the product.
Sources: research/SOURCE_INDEX.md — [S20][S21].

From interview to filed return

1. The interview — the software asks plain-language questions and maps answers onto the correct forms and schedules (1040 + schedules A/B/C/D/E, plus credits/worksheets). The "engine" is the encoded tax code that turns answers into the right lines and calculations.
2. Import & carryforward — W-2/1099 import and prior-year data reduce entry and errors.
3. Calculation & checks — the engine computes tax, credits, and refund/owe, and runs error/consistency checks.
4. E-file transmission — the completed return is formatted and transmitted electronically to the IRS (and to state agencies for state returns).

E-file / Modernized e-File (MeF) [S20][S21]

• MeF is the IRS's web-based system for electronically filing individual, business, and other returns over the internet. It replaced older, batch-style e-file with a modern, near-real-time system.
• Returns are formatted in XML against IRS schemas and business rules; MeF validates each submission and returns an "Accepted" or "Rejected" acknowledgment. Accepted returns flow into IRS processing.
• Transmission happens via Internet Filing (IFA) or Application-to-Application (A2A) for high-volume transmitters.

Authorized e-file providers & annual certification [S21]

• Software companies are Authorized IRS e-file Providers; a software developer must build to IRS specs and pass Assurance Testing (ATS) each year before being approved to transmit. (Publication 4163 governs the rules.)
• This is the annual update-and-recertify cycle: every season the software must be updated for the new tax code and re-pass IRS Assurance Testing (ATS) against the current-year schemas and business rules — on a fixed calendar, before the season opens. It's not a from-scratch rebuild; it's re-implementing the changed pieces and re-validating the whole. Federal and each state have their own forms/rules and approvals. (Program-opportunity angle: PROGRAM_OPPORTUNITIES.md → PO-1.)

Fraud, identity & security — core to the product

Tax season is a massive fraud target, so security is not a feature but a foundation:
- Refund fraud / identity theft — criminals file fake returns using stolen identities to steal refunds. Defending against it (identity verification, anomaly detection, IRS IP PINs) is central.
- Account/data protection — the software holds the richest financial data a person has (file 06), so breach risk is existential.
- Accuracy safeguards — error checks and guarantees exist because mistakes carry real penalties (file 03).

What it takes to become a filer — the barriers to entry

A common question in the AI era: if an LLM can build the guided experience, can anyone just ship a tax filer? Building your own return with AI is easy; building a product that files other people's returns is not. Two different things:

• Filing your OWN return — no certification needed. You can use AI to understand your taxes and file yourself via Free File Fillable Forms or mail. This is the "shadow layer" eroding DIY-guidance value (file 06).
• A COMMERCIAL filer (a TurboTax competitor) — three real walls, none of which AI removes:

1. IRS e-file authorization [S32][S33][S34]
- Apply to become an Authorized IRS e-file Provider (get an EFIN); software developers/transmitters also get an ETIN.
- Pass Assurance Testing (ATS) every year (Pub 1436 for individual MeF) — IRS-defined test returns whose output must match, validated against that year's schemas/business rules; approval is per tax year.
- Conform to the Pub 1345 handbook, pass a suitability check (background/tax-compliance vetting), and repeat for every state you support.

2. Data-security law [S35]
Tax prep is a "financial activity" under GLBA, so the FTC Safeguards Rule + IRS Pub 4557 require a Written Information Security Plan (WISP), a designated Qualified Individual, MFA, AES-256 at rest, TLS 1.2+, annual penetration testing, and an incident-response plan. Penalties up to ~$50,120 per violation, plus loss of PTIN/EFIN.

3. Accuracy liability & trust (Analysis)
You implicitly stand behind the numbers — so errors mean E&O/malpractice exposure, guarantee costs, and consumer-protection law (the "free" saga, file 10). A confidently-wrong LLM is a liability, not a feature.

Two nuances (don't over- or under-state the wall):
- Real but not insurmountable — hundreds of companies are authorized e-file providers (FreeTaxUSA, TaxAct, Cash App Taxes, many small ones). A funded startup can clear these bars.
- There's a shortcut — newcomers can build on an existing authorized transmitter / "MeF-as-a-service" backend and skip becoming their own e-file provider. That lowers the plumbing wall and pushes the real battleground onto trust, liability, and distribution — exactly where Intuit is strong.

Analysis — why the mechanics matter to the business

The annual, IRS-certified, deadline-bound update is a structural barrier to entry (you can't casually "ship a tax filer") and the reason the season's calendar is inflexible (file 03). It's also where AI-native newcomers face friction: generating tax guidance is easy for an LLM, but becoming an accepted, certified, secure transmitter — and standing behind accuracy — is not. The moat moved: AI collapsed the tax-knowledge layer, but the right to file, the duty to protect data, and accountability for accuracy remain — which is why the durable defense is trust + distribution, not code (see file 11).