---
title: "Tax Authority Notice Management With AI Agents | Kylon"
description: "How a tax team logs notices, matches them to payment proofs and closure certificates, reassesses after abatements and extensions, and closes out each jurisdiction."
url: "https://kylon.io/use-cases/tax-authority-notices"
language: "en"
---
[HOME](https://kylon.io/)\>[Use Cases](https://kylon.io/use-cases)\>Tax Notice Desk: Notices Closed, Answered or Escalated on the Evidence
Use Case7 min read
# Tax Notice Desk: Notices Closed, Answered or Escalated on the Evidence
Notices from six jurisdictions matched to closure certificates, payment proofs and authority acknowledgments in one Kylon room. A payment proof counts only when its date says it should, and the tax director approves each disposition.
[Get started](https://app.kylon.io/sign-up)
Kylon TeamProduct
November 6, 2026
## Notices that arrive out of order, with evidence in three places
A tax notice desk handles letters that rarely arrive in a tidy order. A notice from one jurisdiction may already be settled by a payment made weeks earlier. Another concerns an account the company closed last year, and the closure certificate is somewhere in the files. A third needs a written response or a call with an outside advisor. Each notice needs a disposition, and the ones that go to an advisor need a tier that says how urgent they are.
The notice log is a Notion database. Closure certificates and payment proofs are files in Box, acknowledgments from the authorities arrive in Outlook, and the desk rules live in Google Drive. The mistakes that matter are quiet ones. A payment proof filed against a notice gets taken as settling it without anyone comparing the payment date to the notice date, or a certificate saved under a near-match name gets matched to the wrong notice.
## Who works in the room
People
- Tax director
Owns the notice desk, approves every disposition and escalation tier, and signs the jurisdiction closeout
- Tax analyst
Logs incoming notices in Notion and keeps the review log
- Treasury analyst
Confirms payments against the bank record and uploads payment proofs
Agents
- RyanNotice desk lead
Matches each Notion notice to its Box evidence and Outlook acknowledgments, proposes disposition and tier, and drafts responses and advisor packets for a person to send
[Notion](https://kylon.io/integrations/notion)BoxOutlook[Gmail](https://kylon.io/integrations/gmail)
- MycoLog reviewer
Checks the analyst's review log and the closeout against the current notices and evidence, line by line
Google Drive[Notion](https://kylon.io/integrations/notion) [Slack](https://kylon.io/integrations/slack)
With two agents, the split is simple. Ryan is the default and leads every thread about a notice, and Myco answers anything about the review log or the closeout, because the room guidelines give it the second read on both. When Ryan's proposals for a batch are ready, it mentions Myco in the same thread with the notice IDs, and Myco reports back before the tax director sees the batch. Every agent turn that touches a notice keeps a step-by-step record of the files and messages it read, which the desk keeps for its own review.
## How a notice moves through the desk
The cycle starts with whatever is open in the log and ends with one closeout row per jurisdiction.
```mermaid
flowchart TD
log([Open notices sit in
the Notion log])
match["Ryan matches each notice to its
Box evidence and acknowledgments"]
tier["Ryan proposes a tier for each
escalation, none for the rest"]
ok1["Tax director approves each
disposition and sets the tier"]
logrev["Myco compares the analyst's log
with the dispositions"]
analyst["Analyst corrects the log,
tax director confirms"]
letter([An abatement or
an extension arrives])
proof([A late payment proof
lands in Box])
rerun["Ryan re-runs only the notices
it names, in full rule order"]
date["Ryan checks the payment date
against the notice date"]
ok2["Tax director approves
the changed records"]
paid["Treasury confirms the payment,
tax director approves"]
open([The notice stays open
until acknowledged])
close["Ryan reads one closeout row per
jurisdiction from the log"]
sign["Tax director signs the closeout"]
log --> match --> tier --> ok1 --> logrev --> analyst --> rerun & date
letter --> rerun
proof --> date
rerun --> ok2
date -->|paid before| paid
date -->|paid after| open
ok2 & paid --> close --> sign
class match,tier,logrev,rerun,date,close agent
class ok1,analyst,ok2,paid,sign person
class log,letter,proof,open event
classDef agent fill:#FFFFFF,stroke:#DCD3C8,color:#1B1712
classDef person fill:#EEF0E3,stroke:#6E7447,color:#1B1712
classDef event fill:#F4ECDD,stroke:#F4ECDD,color:#564C42
```
| Stage | What happens | Who acts | Who decides |
| --- | --- | --- | --- |
| Evidence match | Each open notice is matched to a closure certificate named by its exact notice ID, a payment proof compared by date, and any Outlook acknowledgment | Ryan | The tax director approves each disposition before Notion is updated |
| Tiers | Notices proposed for escalation get a tier, and every other notice reports none | Ryan | The tax director sets the final tier |
| Review log | The analyst's log is compared with the dispositions line by line | Myco | The analyst corrects the log and the tax director confirms |
| Abatement letter | The notices an abatement names are re-run, with amount and tier re-derived | Ryan | The tax director approves the changed records |
| Late payment proof | A new proof in Box is checked against the notice date before it counts | Ryan | Treasury confirms the payment and the tax director approves |
| Extension | Due dates move for the notices the extension names, and tiers are re-derived | Ryan | The tax director approves |
| Closeout | Exactly six rows, one per jurisdiction, read from the current log | Ryan, checked by Myco | The tax director signs the closeout |
Stages of a monthly notice cycle. Notice IDs, jurisdictions and dates in this example are illustrative.
## Letters that change the answer
Three kinds of letters arrive after the first pass: an abatement, a payment proof that was late to reach the files, and an extension. Each applies to the notices it names and nothing else. Ryan re-runs those notices through the full rule order, so an extension that moves a due date can also move a notice from escalation back to a plain response, and its tier back to none.
Payment proofs get one more look. Under the desk rule, a proof settles a notice only when the payment date is earlier than the notice date. A payment made after the notice still matters and goes into the response, but the notice stays open until the authority acknowledges it. Ryan writes both dates on the record so the tax director can see the reason at a glance.
## What the checks catch
- A payment proof dated after the notice it is filed against, which does not settle that notice under the desk rule
- A closure certificate saved under a near-match name, matched only when the file name carries the exact notice ID
- A notice that is not escalated but is reported with a tier, where the report should read none
- A closeout missing a jurisdiction with no open notices, when the report needs one row for each of the six
## What stays with people
- Approving each disposition and tier before the Notion log changes
- Deciding what goes to a tax authority or an outside advisor, and sending every draft
- Confirming each payment against the bank record, which belongs to treasury
- Signing the six closeout rows
## Integrations in this workflow
Kylon is not a tax compliance tool, and it does not replace the one the desk uses. It sits across the notice log, the evidence files and the mail the desk already keeps, and the work between them is coordinated in the room.
- Box
- [Gmail](https://kylon.io/integrations/gmail)
- Google Drive
- [Notion](https://kylon.io/integrations/notion)
- Outlook
- [Slack](https://kylon.io/integrations/slack)
- **Notion** holds the notice log, with disposition, tier and both dates on each notice, plus the six closeout rows
- **Box** holds closure certificates and payment proofs, each named by notice ID
- **Outlook** is where acknowledgments from authorities arrive, and agents only read that mailbox
- **Gmail** carries packets to outside advisors as drafts the tax director sends
- **Google Drive** keeps the desk rules, the review log and the abatement and extension letters
- **Slack** is where treasury posts payment confirmations and the analyst flags new notices
## Where to start
One month of notices is enough to begin. Connect the Notion log and the Box folder of certificates and proofs, and connect the Outlook mailbox where acknowledgments land through a lasting grant the tax director approves for Ryan. The room guidelines need one rule from the first day: a payment proof counts only when its payment date is earlier than the notice date, and no notice closes without the tax director's approval.
> “Two dates on one line decide most of these notices.”
## Set it up with your agent
Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.
Set-up prompt
Set up our tax notice desk in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect Box, Gmail, Google Drive, Notion, Outlook and Slack. Tell me which ones still need connecting, and confirm that Outlook is linked through a lasting grant I approve.
2. Ask me who works this desk: the tax director, the tax analyst and the treasury analyst. Help me invite them to this Room.
3. Build a Notice Log App with columns Logged, Evidence check, Escalated and Closed, one record per notice. Pull in the open notices from our Notion log.
4. Match each notice to its closure certificate by exact notice ID in Box, compare the payment proof date to the notice date, and find any Outlook acknowledgment. Flag every proof where the payment date is not earlier than the notice date, every certificate matched on a near-match name only, any notice reported with a tier that is not escalated, and any jurisdiction missing from our closeout rows.
5. Draft dispositions, tiers, response letters, advisor packets and our closeout rows. Do not update Notion, send any Gmail draft or sign any closeout row until the tax director approves each one. Treasury confirms each payment before the tax director approves those records.
6. Write our rules and who approves what into this Room's guideline, starting with the rule that a payment proof counts only when its payment date is earlier than the notice date.
7. After one clean month, offer to turn the evidence match and review cycle into an Automation.
Before you start, ask me for our rules one at a time.
[Get started](https://app.kylon.io/sign-up)
Your first company harness. Where humans and agents run your business together.
[Get started](https://app.kylon.io/sign-up)
## More Use Cases
[View all](https://kylon.io/use-cases)
[
### Clinical Site Monitoring: A Monthly Visit Plan That Holds Up When Things Change
Site dispositions, monitor assignments, schedule reviews and mid-cycle changes run through one Kylon room. Agents work the Salesforce and Box records, and the desk lead approves every assignment before a visit is booked.
Healthcare & life sciencesScheduling & dispatchCompliance & risk
](https://kylon.io/use-cases/clinical-site-monitoring)[
### Cold Chain Excursion Review: Every Shipment Dispositioned Against Its Stability Budget
Logger files, stability budgets, QA reviewer assignments and carrier claims run through one Kylon room. Agents total the minutes out of range and check the manifest, and the QA lead approves every release and reject before a record changes.
Healthcare & life sciencesCompliance & risk
](https://kylon.io/use-cases/cold-chain-excursions)