Rima field guide / Tax resolution

What we learned deploying AI on 300+ tax resolution cases

Why most AI can't do a 433, what it takes, and how to tell the difference.

For enrolled agents and the people who run resolution practices. A 20-minute read. Nothing in it requires buying anything.

Cover of the Rima field guide, What we learned deploying AI on 300+ tax resolution cases
Detail from the actual guide cover29-page field guide / PDF
From the guide / Part 2

Six mistakes the draft walks through.

These are six actual mistakes from reviewed cases, not six generic checks. The guide pairs each one with the situation, rule, and prohibition that addressed it.

01 / 06

The right number, wrong field

A residence timeline was used for employment tenure on a 433-A (OIC). The value existed, but belonged to a different question.

02 / 06

The right rule, wrong form

Expense logic calibrated for a 433-F was carried into an OIC, where the relevant Section 7 instructions differed.

03 / 06

The wrong source recency

A pay stub and Wage and Income transcript both showed wages. The draft needed a rule for which more-current source to use.

04 / 06

A gap filled from the nearest number

With no bank statement provided, a questionnaire balance was used without the form-specific treatment and flag the case required.

05 / 06

The firm’s conventions were missing

Vehicle, transportation, and Social Security entries exposed practice choices that had not been written into the workflow.

06 / 06

A dropped decimal point

A handwritten expense was misread into an implausible amount. A plausibility check should have stopped it for review.

From the guide / Part 3

The fix was not a better prompt.

Situation. Rule. Prohibition. The guide shows how practitioners turned implicit decisions into instructions that can be reviewed. A rule has to say when it applies, what to do, and what must never happen silently.

That is the difference between reading a number off a document and preparing a draft a practitioner can question.

A rule in practiceSource selection
Situation

Monthly gross wages, with both a Wage and Income transcript and a pay stub available.

Rule

Compute from each source independently, use the more recent one, and identify which source was used.

Prohibition

Do not add the two figures together or silently use the pay stub’s year-to-date column.

Condensed from a case example in the draft. Firms should validate their own rules against the relevant form and client facts.

From the guide / Part 5

Seven questions to ask any AI vendor.

The six mistakes are case examples. These seven are due-diligence questions for a vendor or a tool your team built itself. They are not a second list of findings.

01Where do the rules come from, and can I read them?
02Does it know which form it is on?
03What does it do when the data is not there?
04Can I trace every figure to a page?
05Does it stop for review, or just produce output?
06Who owns the rules when they change?
07What can it change in other systems, and who decides?
About Rima

Why Rima for tax resolution?

Rima prepared 300+ cases alongside enrolled agents across Forms 433-F, 433-B, and 433-A (OIC). The six mistakes in this guide show why extracting a figure is not enough: form-specific rules, source traceability, and a stop for practitioner review matter when messy evidence becomes a draft. The enrolled agent remains responsible for the final decision.

Get the guide

Nothing goes out unread.

Get the full guide by email. Read how six case mistakes became explicit rules, then use the seven questions to examine any AI workflow, including your own.

Rima / Field guideCase preparation is not practitioner approval.