Tax notice management that answers wrong assessments with proof before the window closes
Wrong assessments answered with proof before the window closes, not paid by default.
See one case, screen by screen ↓Tax notice management is the work of receiving every notice from the IRS, state and local agencies, deciding what each one asks for and whether the agency is right, and answering it before its response window closes. Tax Notice Management puts seven agents on that work: they read each notice, work out the real response date, check the claim against your returns, ledger, bank and agency account, and draft the reply with its exhibits, for the tax manager to sign.
How to choose AI solutions for back-office and enterprise work →
Updated
Large companies receive thousands of agency notices a year — balance-due notices, proposed assessments, penalty notices, requests for information — on paper, by e-mail and in dozens of agency portals. Each has its own response window, counted its own way, and once it closes a proposed assessment becomes final, even when the agency is wrong. Today the mail room scans the letters, an analyst keys them into a tracker, and someone pulls the return, the ledger and the bank statement to decide whether the agency is right.
Much of what arrives is a payment-posting problem: tax paid on time but applied to the wrong period or the wrong entity. Proving it means the return, the ledger, the bank and the agency's own account side by side, and without that teams pay to be safe and chase a refund later. Letters reach closed sites weeks late, one wrong treasury template sets off notices in several states that are each answered separately, and a reply marked done is often never checked against the agency's account until the next letter arrives.
Estimated split for one disputed notice handled by hand, and with the solution — about two weeks against one day.
Seven agents read each notice, date it, check it against our books, draft the reply and follow it through; the tax manager signs.
Kestrel & Vane Distribution, part of the Kestrel & Vane Group, receives an Ohio notice of assessment for $32,803.98 — sales and use tax for April to June 2025, sent to a distribution centre that closed in March. Here is how the agents and the tax manager answer it, screen by screen, in the working solution.
Elena owns indirect and payroll notices for eight entities. Today opens with a plain summary: since Friday the agents read the post, the mailbox and the agency downloads and checked every new notice against the returns and payments. Nine need her — five to sign, two payments, two questions — and of the seven due in the next 7 days, none is overdue. On the right, the Deadline, Pattern and Follow-up agents report in their own words, and she can ask them back.
Reconciler agent: “Ohio says we owe $32,803.98. We paid the tax on time; it was posted to the wrong quarter.”
A certified letter arrives forwarded from the closed Dayton site, and Teresa scans it in Columbus with seven other items. The Intake agent reads the batch in 18 minutes: five notices created, a second copy of a Kentucky notice merged into the first, a supplier invoice sent to Accounts Payable, and a partly handwritten City of Columbus letter sent back for a rescan because its amount box is unreadable.
“3 agencies still write to the closed Dayton site. Those letters reach us up to 51 days late.”
The Classification agent names the letter an assessment that can be disputed, with a petition for reassessment due within 60 days under R.C. 5739.13. The Deadline agent counts from the notice date, sets the response date to Sunday 18 October and the file-by date to Friday 16 October, two days early on a working day. It escalates to Elena with nine days left, copies Malcolm Achebe because the amount is above $25,000, and flags that the letter took 51 days to reach the team.
Escalation ladder: 10, 5 and 2 working days before the file-by date. “Missed — never this year: 0 of 1,286.”
The notice screen holds the scan, labelled field by field with confidence and page location, beside a line-by-line comparison. The UST-1 return for April to June was filed on 22 July 2025 with $27,450.00 of tax, and the bank shows $27,450.00 paid by ACH the same day. Ohio's account shows nothing paid for April to June and a $27,450.00 credit on January to March, because the payment record sent with the ACH named the period as 31 March 2025. The penalty of $4,117.50 and interest of $1,236.48 fall away once the payment is moved.
“The department is wrong about the money, and our own payment file caused it.” · 97% sure · Owed if moved: $0.00
The Drafter agent writes a petition for reassessment in six paragraphs, with nine citations and four exhibits: the bank confirmation, the return confirmation, the OH|TAX account statement and the payment record. Every exhibit and every numbered citation opens its source passage — here, the Northmark Bank statement line for the ACH credit on 22 July 2025, settled the same day with no return or reversal.
The Drafter agent never files or sends, and uses only facts the Reconciler agent cited.
The Pattern agent finds the same cause behind the Indiana proposed assessment of $9,880.00 and a Kentucky notice of $6,215.40: three notices, $48,899.38 in all. The treasury template “OH-SUT-quarterly” was made for the January to March payment with the period date typed in, reused for April to June, and copied for Indiana and Kentucky. It proposes the fix and names its owner, Kwame Mensah, Treasury Payments Lead, and drafts change-of-address forms for the three agencies still writing to Dayton.
The Pattern agent proposes only; it never changes another team's system.
Elena asks the Reconciler agent whether the payment really was for April to June. It answers with three facts: the amount matches the April to June return to the cent, it was paid the day before that return was due, and January to March was already paid on 22 April with $26,980.00. She then asks the Drafter agent to add a hearing request; it adds paragraph 7 and shows her the change before she signs.
Drafter agent: “Asking now keeps the right; Ohio only schedules a hearing if the petition asks for one. It is a draft change: you see it before signing.”
Elena approves with reason A1, “Agency error — file as drafted”, and signs as the tax manager under the TBOR 1 on file. The dialog states what is attached, the filing channel and the file-by date, and the Sign and file button stays disabled until she ticks the signature.
“The reply is filed only after you sign. Pick the reason that fits; it is kept with the notice and in the audit trail.”
The Follow-up agent files the signed petition, with the hearing request in paragraph 7, through OH|TAX eServices and records confirmation OH-PET-2026-0081164. The agents' strip across the top now ends with “You signed it”, and the notice moves to filed, waiting on the agency.
The Follow-up agent checks Ohio's account every Monday and expects the $27,450.00 to move within about 41 days, the average for the five similar assessments Ohio withdrew this year. If the department has not acted by Monday 30 November, it drafts a follow-up for Elena. It reads every agency answer too: CDTFA asked for shipping records on another notice, and the second reply, with all 12 bills of lading, is drafted for her signature.
The Follow-up agent never closes a notice on a letter alone — only when the agency's account shows the right balance.
The same Ohio assessment, seen by five of the people who carry it — what their week looked like, and what it looks like now.
Seven agents read each notice, date it, check it against our books, draft the reply and follow it through; the tax manager signs.
Reads mail-room scans, e-mails and agency portal downloads; splits files that hold several notices; reads every field with its location on the page and its confidence; merges duplicates and routes mail that is not a tax notice.
Says what each notice asks for — information, payment, an answer or a dispute — and which rule applies, and proposes closing information-only notices.
Counts the response date from the agency's rule and the earlier of the notice date and service, sets a file-by date two days early on a working day, and escalates at 10, 5 and 2 working days.
Compares the notice with the filed return, the ledger, the bank statement and the agency's own account, line by line, and says in plain words whether the agency is right, with a confidence.
Writes the reply in the agency's own form — petition, protest or letter — attaches the exhibits, cites every sentence, and drafts payment and penalty-relief requests.
Files what a person signed, watches the agency account every week until the balance is right, reads the agency's answers and drafts the next step.
Finds the one cause behind several notices — a treasury template, a stale address, a deposit under a sister company's tax number — traces it to its source and proposes the fix and its owner.
Signs every reply; the controller approves large payments. The agents propose; a named person decides.
Every screen has the agents to talk to. Ask what to do first or why they reached a verdict, or tell them what to change — every answer points to its source, and nothing changes until you approve it.
What should I do first?
Sign the Ohio petition: it is $32,803.98, files by Friday, and the reply is ready with four exhibits. Then the two payments due Monday and Tuesday (Illinois and Texas), about two minutes each. The other 6 can wait until Thursday.
Are you sure the payment was for Apr–Jun?
Yes, 97%. The amount is $27,450.00 to the cent, the same as the Apr–Jun return; it was paid on 22 July, the day before that return was due; and Jan–Mar was already paid on 22 April with $26,980.00, which clears its own accrual exactly. The only thing pointing to Jan–Mar is the period date in our payment record.
Why not just pay it and ask for a refund later?
Paying $32,803.98 now would not stop the assessment becoming final on 18 October, and we would then need a refund claim for the Jan–Mar credit, which Ohio takes months to process. The petition stops the clock and asks for the money already there to be moved. Ohio has withdrawn all 5 assessments like this one this year.
Ask for a hearing too
Added to paragraph 7: “We request a hearing only if the department does not agree to cancel the assessment.” Asking now keeps the right; Ohio only schedules a hearing if the petition asks for one. It is a draft change: you see it before signing.
13 screens from the working solution, on its sample data. Pick one to see it large.
The thresholds and limits the agents work to are settings, and they change only after the VP Tax approves them.
| Setting | Default | Choose from |
|---|---|---|
| Reconciler agent proposes a verdict only above | 85% confidence | Below it, the notice goes to a person as a question |
| Information-only notices close after | One click by a person | A random 10 a month are re-checked |
| File every reply | 2 days early, on a working day | Approved by Ingrid Solberg, VP Tax |
| Escalation | 10, 5 and 2 working days | Owner first; tax manager and controller above $25,000; VP Tax if unsigned |
| Tax analyst approves payments up to | $1,000 | The tax manager approves above |
| Tax manager approves payments up to | $25,000 | Group controller above |
| Ask for penalty relief when the penalty is over | $250 | Below, the choice is recorded |
| Send to the outside advisor when | Apportionment, nexus or transfer pricing | Or any amount over $250,000 |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published rules (Ohio R.C. 5739.13 — a petition for reassessment within 60 days after service, or the assessment becomes final; Canada Excise Tax Act s.301 — a notice of objection within 90 days after the notice of assessment; IRS notice instructions — 21 days on a CP161). Kestrel & Vane Group, its entities, addresses and the people named on this page are fictional — characters and sample data in the working solution; the tax agencies are named only as senders of invented notices.
Tax notice management is the work of receiving every notice from the IRS, state and local agencies, deciding what each one asks for and whether the agency is right, and answering it before its response window closes. Tax Notice Management puts seven agents on that work: they read each notice, work out the real response date, check the claim against your returns, ledger, bank and agency account, and draft the reply with its exhibits, for the tax manager to sign.
The Reconciler agent compares the notice with the filed return, the general ledger, the bank statement and the agency's own account statement, one line at a time, and marks each line the same, different or the cause. It gives a verdict in plain words with a confidence and cites every line; below 85% it asks the tax manager a specific question instead.
The Deadline agent counts from the agency's own rule and the earlier of the notice date and service, not the day the letter reached you, and names the law it used. It sets a file-by date two days early on a working day and escalates at 10, 5 and 2 working days.
Yes. When a payment made on time was posted to the wrong period or entity, the Reconciler agent shows it from the bank, the ledger and the agency account, and the Drafter agent writes the reply asking the agency to move the money, with the bank confirmation and payment record as exhibits.
The Pattern agent looks across notices for one cause behind several — a treasury payment template, a stale address, a deposit under a sister company's tax number — traces it to its source and proposes the fix and its owner. A person sends the fix; the agent never changes another team's system.
The Follow-up agent checks the agency's account every week and proposes closing the notice only when the balance is right, never on a letter alone. It reads every agency answer and drafts the next reply for signature.
Yes. The agents draft and propose; the tax manager signs every reply with a reason code and an e-signature, payments follow your approval limits, and the agents are read-only on your books. Rules change only after the VP Tax approves them, and every step is on a sealed audit trail.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your notice types, agency rules, approval limits and a sample of past notices — and it goes live once every quality gate has passed. First-time setup includes a trial on last year's notices, so you see how the agents would have done before you rely on them.
Every country tested, every field traced, the return ready months before the deadline.
1-min demoE-Invoicing ComplianceEvery invoice checked before it leaves, and every rejection fixed the same day.
1-min demoTransfer Pricing DocumentationEvery margin tested before the year closes, and every file ready inside 30 days.
1-min demoWe'll run Tax Notice Management on a sample of your own past notices, with the returns and payments behind them.