When the Preparer and Reviewer Disagree About an AI-Drafted Entry

A Reviewer sends an AI-drafted entry back. The Preparer opens the same page, reads it again, and still thinks the row is right. The Firm can choose the written dispute path below for two readings of one page, while leaving the final call on sign-off with the Reviewer.

A Firm choosing this path can record both readings and the reason for the outcome. It can also specify that changing a row or closing a note does not, by itself, settle the disagreement.

The tool drafted the row, and that's all it did. It isn't a party to the dispute and it doesn't get a vote. Two people read the page, the Firm's path settles the entry, and the Reviewer keeps the final call on sign-off.

When a send-back becomes a disagreement

The Firm can draw the line in one place: a send-back becomes a disagreement when the Preparer answers the note with a different reading instead of a fix. The clearing loop for review notes assumes the Preparer agrees with the note; this path starts where they don't.

Under the Firm's rule, the Preparer marks the note "contested" rather than clearing it or changing the row to make the note go away. That one word moves the entry onto this path.

Two things stay off the path. Which reading the tool drafted carries no weight, so "the tool put it there" isn't an argument either way. And a question about what a rule requires isn't a disagreement over a page. The Firm sends those to whoever it assigns for technical questions, outside this path. What stays here is narrow: two people reading the same printed page two ways.

Each side states its reading, with the page cited

The Firm can ask both people to write their reading on the note, under the same row, before anyone talks it over. Each reading cites the page and line it rests on. One reading per side, a few sentences, no history of the file.

The Preparer writes what they think the page says and where it says it. The Reviewer does the same. If a reading leans on a second document in the folder, it cites that page too.

Writing first does two jobs. The written note puts both cited readings in one place. Either person can revise their reading after checking the cited line. If that happens, the side that moved writes so on the note and the entry goes back to the normal send-back process.

A set time to settle

The Firm sets a window for the two of them to settle it between themselves, such as one working day. They sit with the page and both written readings and try to agree.

If they agree, the outcome goes on the note, along with which reading it follows. If the window closes without agreement, the entry escalates. Nobody extends the window by default, and nobody lets it lapse into silence.

While the window runs, the contested entry stays open. The rest of the file can keep moving under the Firm's normal process. The Firm decides which other work can continue while the contested entry stays open.

Escalate to a named senior

The Firm names the senior before the season starts, not after a dispute begins. That can be a partner or a senior Reviewer who isn't on the file. The Firm can record the senior's name before a disagreement arises.

The senior reads both written readings and the cited pages, not a retelling from either side. Then the senior decides how the entry reads and writes the reason on the note in a sentence or two. The senior settles the entry. The senior doesn't re-review the whole file and doesn't sign it.

Running the page through the tool again doesn't settle anything. A second draft is one more reading to check against the page, not a tie-breaker.

The Reviewer keeps the final call on sign-off. If the Reviewer can't sign with the senior's outcome, they say so in writing on the note, and the Firm decides who reviews the file from there. Nobody signs over an objection that was never written down.

Record the outcome on the note

The Firm can keep the whole dispute on the note that started it. The note records:

• the row and the page it came from
• the Preparer's reading and the Reviewer's reading, each with its page cited
• how it was settled: agreed in the window, or decided by the senior
• the outcome, with the change to the row and the reason
• who decided and when

The losing reading stays on the note. Deleting it would erase the reason the entry was looked at twice. The note records who decided and when.

The settled note stays with the entry list in the Firm's file, next to the other send-back notes. The reasons an entry goes back in the first place belong to the Reviewer's readback; this note only covers the case where the answer to a send-back was no.

No sign-off while the entry stays open

Under the Firm's rule, there's no sign-off while the entry stays open. Under this chosen path, an unsettled contested note blocks sign-off on the file.

The Firm can make the following conditions part of that rule. Nobody signs with a footnote saying the entry is under discussion. Nobody changes the row to match one reading so the note can close. The entry is settled on the record first, and then the Reviewer decides whether to sign.

A Doe example

The figures below are made up for illustration.

Jane Doe, a Preparer at Doe & Co. CPA, has an AI-drafted entry list for the client Doe Holdings. One row comes from a two-page vendor invoice numbered 0471. Page one prints services of 1,200.00, a credit of 150.00 marked "see note 2", and a balance due of 1,050.00. The drafted row carries 1,050.00.

Pat Doe, the Reviewer, sends the row back. Note 2 on page two says the credit was issued against invoice 0417, a different number from the one at the top of page one. Pat's reading: the credit belongs to another invoice, so the row should carry the 1,200.00 services line, with the 150.00 credit handled separately.

Jane marks the note contested. Her reading, citing page one: the balance due line already nets the credit, and 0417 looks like 0471 with two digits swapped. Both readings go on the note with their pages.

The window is one working day. Jane checks the folder and finds no invoice 0417; that absence does not establish which reading to use. They don't agree, so the entry goes to Morgan Doe, the senior the Firm named for this team.

Morgan reads both notes and both pages. Morgan decides the row carries 1,200.00 as printed on the services line, since the page names a different invoice for the credit, and the 150.00 goes on the file as an open question for the client. Morgan writes that reason on the note with the date.

Jane changes the row from 1,050.00 to 1,200.00, a change of 150.00, and the note shows both readings, the outcome and who decided. Pat reads the row back against page one. Pat keeps sign-off open while the 150.00 client question remains unresolved. After that question and the file's other open items are resolved and documented, Pat decides whether to sign off.

Where TracePrep fits

TracePrep's one shipped workflow today is the Reasonable Compensation Study for an S-corporation shareholder-employee. It's a different job from this dispute path, and it keeps the same kinds of records:

We've built a TracePrep plugin that runs these steps in your Firm's workflow.

Want the TracePrep plugin in your Firm? We'll tell you when access opens.

Join the waitlist

This is general information, not tax or legal advice. Your licensed professional and your Firm's Reviewer are responsible for every return and every conclusion. Keep client data inside the systems your Firm has approved. As general guidance only, not advice: if you use an AI tool with client data, firms generally look for a business or commercial plan whose terms cover how that data is handled; read the vendor's current terms before you do.