Skip to content
Compliance & Audit agent

Auditor requests

Your auditors send the list. It finds each answer in your records, checks it covers the right period and sign-off, and drafts the reply with the files attached. Gaps and sensitive files wait for a person.

  • $12,500 fixed
  • Live in 3 to 6 weeks
  • Yours to keep
Let’s build your agent How it works
The review screen for Auditor requests: four items, three done, and one (Approval missing) waiting for the controller, who is asked: Payment 19 of 25 has no approval on file. Hold the answer until you find one?
How it works

Before anyone opens a folder, most audit requests have a draft.

Here’s a typical run, step by step: what automation handles, what the agent does, and the calls that stay with your team.

The workflow for Auditor requests, in 5 steps. It starts with “The request list arrives” and ends with “Every request answered”. Each step lists what automation, the agent and your team do there.
Auditor requestsA typical run
Starts withThe request list arrivesYour auditors send 64 items for the year-end audit, each with a due date, through their portal.
The agent: Reads each of the 64 requests, vague ones like “support for significant accruals” included, and notes what would answer it.
Automation: Adds every request to the tracker with its due date and an owner, and opens a folder for each one.
~6h/mo

Step 1 of 5Read the list

  • The agent

    Reads each of the 64 requests, vague ones like “support for significant accruals” included, and notes what would answer it.

    Auditors write requests in their own words. “Support for accruals” can mean a schedule, the invoices, or both.

  • Automation

    Adds every request to the tracker with its due date and an owner, and opens a folder for each one.

    Every request needs a due date and a folder, and none of that changes from item to item.

Reads
  • Auditor portal
Writes
  • Audit tracker

~6 hours a month back

Where teams differSome auditors send a spreadsheet by email. Others work entirely in their own portal.

Automation: Fetches what sits in the same place every year: bank statements, the trial balance, board minutes from the shared drive.
The agent: Searches accounting and the shared drive for the harder ones, like the 25 vendor payments the auditors picked, each with its invoice.
~18h/mo

Step 2 of 5Find the records

  • Automation

    Fetches what sits in the same place every year: bank statements, the trial balance, board minutes from the shared drive.

    December’s bank statement is where it always is, so fetching it is routine.

  • The agent

    Searches accounting and the shared drive for the harder ones, like the 25 vendor payments the auditors picked, each with its invoice.

    A payment’s approval might be an email, a note in accounting or a signed PDF. It has to be read to be found.

Reads
  • Accounting
  • Shared drive
Writes
  • Audit tracker

~18 hours a month back

The agent: Reads each file against its request. Payment 19, $18,400 to Tallis Logistics, has an invoice but no approval anywhere.
~10h/mo

Step 3 of 5Check it answers

  • The agent

    Reads each file against its request. Payment 19, $18,400 to Tallis Logistics, has an invoice but no approval anywhere.

    A file can be the right kind and still the wrong year, or unsigned. Those are the ones auditors send back.

Reads
  • Shared drive
Writes
  • Audit tracker

~10 hours a month back

Where teams differAn approval might be a signature, an email reply or a click in the payment system, depending on the team.

Automation: Anything missing, and anything you’ve marked sensitive like payroll, goes to the controller with the request and what was found.
IfYour team: Finds the approval for the $18,400 payment, or writes the note explaining it, before that answer goes back.
~5h/mo

Step 4 of 5Settle the gaps

  • Automation

    Anything missing, and anything you’ve marked sensitive like payroll, goes to the controller with the request and what was found.

    A missing file is plain to see, and you mark sensitive ones in advance, so both reach a person on their own.

  • Your teamIf something is missing

    Finds the approval for the $18,400 payment, or writes the note explaining it, before that answer goes back.

    What the company tells its auditors about a gap is a call for whoever answers for the audit.

Reads
  • Audit tracker
Writes
  • Audit tracker

~5 hours a month back

Where teams differWho clears a gap varies: the controller for a financial audit, the compliance lead for a security one.

Your team: Looks over the week’s answered requests on one screen and releases them, or holds any for another look.
Automation: Uploads every released file against its request in the portal and marks it answered in the tracker.
~6h/mo

Step 5 of 5Release the answers

  • Your team

    Looks over the week’s answered requests on one screen and releases them, or holds any for another look.

    Everything the auditors see is something the company has told them. Someone on your team says when it goes.

  • Automation

    Uploads every released file against its request in the portal and marks it answered in the tracker.

    Once a file is released, all that’s left is attaching it to its request number.

Reads
  • Audit tracker
Writes
  • Auditor portal
  • Audit tracker

~6 hours a month back

Ends withEvery request answeredEach item filed against its request with the source attached, released by your team.
Total~45h/mo

What changes

Most requests come back drafted with their files attached, so your team’s time goes on the few gaps and on what to tell the auditors about them.

  • 4steps automated
  • 3steps for the agent
  • 2calls kept with your team

Pick any step to see what happens there and why it sits in that lane.

What it could be worth

~45 hours a month back

$35,100 a year in time

For a company answering about 300 requests a year across its financial and security audits, at $65 an hour. We work out yours from your own volumes before you sign.

Let’s build your agent
What we customize with you

One proven agent, plugged into how you work.

Every team does this job a little differently, so we set these five with the people who do it today. We’ve done this in dozens of businesses, so we know where teams usually differ and ask about those first.

The agent

Same for every client
  • Follows the same proven steps
  • A person on every exception
  • Every decision logged
  • Tested on your past work first
  • Never sends anything to your auditors on its own

  1. Your systems

    Where the work comes in, and where the result goes.

    For this agentRequest lists from your auditors’ portal or spreadsheet, files from accounting and the shared drive.

  2. Your rules

    The limits and exceptions it works to.

    For this agentWhat answers each kind of request, and which files never go out without a look.

  3. Your team

    Who signs off, and who covers when they’re away.

    For this agentThe controller for financial requests, the compliance lead for security ones.

  4. Your channels

    Where your team hears from it.

    For this agentThe auditors’ portal for answers, Slack for your team, a weekly status list.

  5. Your output

    What it hands back, in the format you already use.

    For this agentEach request answered with its files, or held with a note on what’s missing.

Control evidence and access reviews are other agents in the catalog. What to tell the auditors about a gap, and how to answer a finding, stays with your team.

What you get

The agent, and everything that keeps it working.

  • The agentRunning on your systems, under your rules.
  • The review screenWhere the exceptions land for your controller and compliance team.
  • Your rulebookYour limits, exceptions and who signs off, in one place, often for the first time.
  • A test reportYour past audit requests, run through it and checked against the number.
  • The runbookHow it works, what to check, and what to do if it stops.
  • 30 days of tuningAfter it goes live, through a full month of your real audit requests.
The number we agree

Days from a request list landing to every item answered. We measure last year’s list, then the first one it runs.

How we get there

Live in 3 to 6 weeks. About seven hours of your time.

We do the building. Your side: access, last year’s request list and the answers your team sent, and a short weekly check-in.

  1. Before kickoff

    We send the access checklist.

    You, 2 hours. Access, an owner, and last year’s request list and the answers your team sent.

  2. Weeks 1 to 2

    We connect your systems and set it up.

    You, 1 hour. Walk us through your rules.

  3. Weeks 2 to 4

    We test it on your past audit requests.

    You, 1 hour. Review what it flagged.

  4. Weeks 3 to 6

    It runs beside your team, then goes live.

    You, 1¼ hours. Work from the review screen.

Then 30 days of tuning, with a short check-in each week, about two hours of yours. At day 30 we show you the number and hand everything over.

After it’s live

It keeps running whether or not we stay.

  • It runs in your accounts

    Your cloud, your systems, and an AI account in your name, billed by the provider at their rates.

  • Changes in the first 30 days are included

    A new rule, a changed limit, someone new signing off. That’s what tuning is for.

  • After that, your call

    Your team edits the rulebook, the care plan covers it, or a bigger change is quoted first.

Audit-day questions at a lender went from weeks to seconds with work like this.

Questions

About this agent.

Does it work in our auditors’ portal?
If the portal lets software upload files, it answers there. If not, it builds a folder per request and your team uploads it.
What about sensitive files, like payroll?
You mark those in the rulebook. It finds them and holds them for the right person to check before anything is shared.
Can it answer the auditors’ follow-up questions?
It drafts replies from the record, with the source attached, for your team to send. Explaining a finding stays with you.
Our process isn’t quite like this. Will it still work?
That’s the usual case. The job looks the same in most businesses, but the details never do. We map how your team does it today, then set the rules, systems and approvals to match. That’s what most of the 3 to 6 weeks are for.
How do we agree the number?
Together, before any work starts. For this agent it’s the days from a request list landing to every item answered. We measure last year’s list, then the first one it runs.
What does it cost to run once it’s live?
Hosting and AI, paid straight to the providers, not through us. It usually runs 5x to 25x cheaper than doing the same work by hand, and we work out your figure from your real volumes before you sign.

When does your next request list arrive?

Tell us how your team handles audit requests today. We’ll show you this agent on examples like yours, and whether it fits the fixed price.

Let’s build your agentBack to Compliance & Audit
New to Switchboard Agents? How it works, what’s included, and what it costs.
  • 3 to 6 weeksto live, then 30 days of tuning
  • $12,500fixed, per agent
  • Yours to keepno license fees
See the service
Switchboard Agents$12,500 fixed · live in 3 to 6 weeks How it works Let’s build your agent