UltraTax AI Prep FAQ: What's Supported, What to Review, and Best Practices

Last updated: September 17, 2026

Filed AI Prep handles most standard 1040 data entry in UltraTax CS automatically. Like any preparer, it is stronger on some documents than others, and we believe in being transparent about both so your team knows exactly where to focus review time. We update this page as coverage improves, and it improves quickly: many of the items in the review sections below have active engineering work behind them.

Where we're most confident

These are the screens and documents where Filed performs best today. Preparers typically see standard inputs in these areas flow into UltraTax with little cleanup needed, though every return is different and results should still be reviewed like any other prepared work:

  • 1040 General Information: taxpayer, spouse, filing status, address, dependents

  • W-2 and W-2G: wages, withholding, Social Security and Medicare amounts, state and local detail

  • Standalone 1099-INT, 1099-DIV, 1099-R, 1099-G, 1099-NEC, 1099-MISC, SSA-1099, RRB-1099/1099-R

  • Schedule C: income and common expense categories from source documents

  • 1099-SA and 5498-SA, IRA contribution information

  • Schedule A inputs including 1098 mortgage interest, taxes paid, and charitable detail

  • 1095-A, 2441, and education inputs

  • Payments and estimates, direct deposit fields (always review account details)

Partially supported: plan on reviewing these

We support these areas, but not every field within them consistently lands correctly every time. Rather than promise field-level precision, here is where preparers should expect to spend some review time:

  • Consolidated 1099s and brokerage statements. Filed reads these, but a multi-section statement (interest, dividends, and trades in one document) may not fully transfer, and clients with several brokerage accounts can see entries land on the wrong or a duplicate Broker screen. Compare the UltraTax result against the binder before relying on it.

  • K-1s. Core identifying information and common income lines transfer. Supplemental and less common lines may not, and QBI detail always needs a reviewer's eye. K-1s issued under an SMLLC or other disregarded-entity FEIN will be flagged for review because the EIN won't match the taxpayer's SSN. That flag is expected, and you can resolve it in the binder or add a firm protocol for how those should be treated.

  • 1098 mortgage interest. By default Filed enters 1098s through the MortgInt screen. If your firm prefers direct Schedule A entry, a protocol can direct that, but keep the MortgInt screen for clients over the $750,000 mortgage limitation or with multiple mortgages so the limitation worksheet calculates. Filed does not complete the limitation worksheet today.

  • Rolled-over and proforma clients. Filed attaches new-year data to an existing proforma entry only when it can confidently match it. If a Schedule E property or brokerage account can't be matched, Filed creates a new entry instead of guessing, and that new entry won't carry the prior-year depreciation or carryovers. Source documents that include the exact property or account name used last year match far more reliably.

  • Document pass-through. On some returns, individual documents that are in the binder do not reach UltraTax, and today the run can complete without clearly flagging them. Until that changes, do a document-by-document check of the UltraTax result against the binder rather than assuming everything transferred.

  • Formatting. Entries may arrive in inconsistent casing (all caps vs mixed case). Cosmetic, but worth knowing. A firm protocol can standardize this.

Known limitations and coming soon

  • Form 8606 (Nondeductible IRAs): coming soon

  • Form 4562 (Depreciation and Amortization): coming soon

  • Inherited IRA routing on 1099-Rs: requires extra review

  • Home office (8829) routing for 1098s: not yet a destination, review manually

  • Multi-state returns: additional review required today

Best practices for UltraTax firms

  • Write protocols for your firm's preferences. Protocols can redirect where documents land (for example, 1098s to Schedule A) and standardize formatting.

  • Review the UltraTax return against the binder after every run, especially consolidated statements and K-1s.

  • For partially completed returns, Filed only updates fields where the new data differs, and it packages a "before data entry" backup with every run. Download a fresh backup before rerunning anything.

  • When something lands wrong, send it to us with the client and screenshots. Real examples are exactly what drives the fixes above, and several recent improvements came directly from firm reports.

Review reminder

Filed AI Prep reduces manual data entry; it does not replace preparer and reviewer judgment. Always review the completed UltraTax return and confirm diagnostics before filing.