Tax Notice Desk: Notices Closed, Answered or Escalated on the Evidence

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

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.

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
• Google Drive
• Notion
• Outlook
• 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.