Agents for accountants/PBC and records chaser

Accountancy agent

PBC and records chaser

Knows what each job is still waiting for, matches what the client sends and chases what they haven't.

Pilot places open

We're running this with a small number of pilot firms first, because matching what clients send to what you asked for has to be right before it's left to run.

Demo video coming soon

See the PBC and records chaser run, start to finish.

We're recording the demo now. Until it's here, we'll walk you through it live on a free 30-minute call.

Book a free 30-minute call

Scope

Audit PBC lists, corporate finance information requests and self assessment records.

What starts it

It starts on its own.

Standard trigger

A job is created in your practice system. The agent loads the standard list for that job type and sends it to the client.

It could also start when

  • A new row in a SharePoint jobs list
  • A PBC list uploaded to the engagement folder
  • Self assessment season starting on a set date, for every SA client
  • A corporate finance request issued from a template

Keeps it moving

Each email to the shared mailbox, file in the client's upload folder or portal submission is matched to the list automatically.

Manual fallback

The manager starts the job from Teams and attaches the list.

  1. Trigger

    A job is created.

  2. System

    The list is loaded and sent.

  3. System

    The mailbox and upload folder are watched.

  4. AI

    Each item is matched to a line on the list. Partial or wrong-period documents are flagged, not ticked.

  5. Action

    The tracker is updated and chasers are drafted at day 7 and day 14.

  6. Your team approves

    The manager approves the chasers (or lets them send on the agreed schedule). The partner is told after day 21.

  7. Ask it in Teams

    “What are we still waiting for from this client?” is answered live.

What it does

When a job is created, the agent sends the client the right request list and then watches the shared mailbox and upload folder, matching everything that arrives to a line on the list. It keeps the tracker current, drafts chasers at day 7 and day 14 for the manager to approve and tells the partner about anything still missing after day 21.

Where your team approves

The chasers (unless you choose automatic sending) and escalations.

You decide what each agent may do on its own and where a person has to approve. By default, anything that goes to a client or raises a bill waits for one of your team.

Standard in every firm

  • Lists for the three job types
  • Mailbox and folder watching
  • Matching
  • The tracker
  • Chaser timing
  • The chat

Set up for your firm

  • List content
  • Tone
  • Timing
  • Escalation rules

Today

The list lives in an email thread or a shared sheet, and records arrive piecemeal. Someone checks the inbox, works out what's missing, writes a chaser and repeats. January is the worst of it.

With the agent

The tracker is always current, chasers go out on time in the same voice and the manager sees a status instead of an inbox.

Worked example

What it could give back to your firm.

Worked example

Chasers handled a year
2,400
Hours back a year
480
Value a year, with penalties avoided
£40,400

Illustrative defaults. Put in your own numbers.

How it's worked out

  • Chasers handled a year = jobs a month × 12 × checks and chases per job.
  • Hours = jobs a month × 12 × chases per job × (minutes now − minutes with the agent) ÷ 60.
  • Value = hours × value of an hour + late filing penalties avoided.

What you need in place

Before it can run in your firm.

  • A shared mailbox or client portal where records land
  • A “job created” signal from your practice system or a SharePoint jobs list
  • Agreed request lists for each job type

Price

Fixed price, confirmed on a free 30-minute call

Once live, it's looked after under Embed from £750 a month, which covers up to two live agents.

Microsoft's own usage charges, such as Copilot Credits, are billed by Microsoft to your firm, separately from our fees.

All prices exclude VAT.

What happens when a client sends the wrong document?
It's flagged, not ticked. Partial or wrong-period documents stay open on the tracker, so the manager can see what arrived and why it doesn't count yet.
Do the chasers go out on their own?
Only if you choose that. By default the manager approves each chaser before it's sent, and the partner is told about anything still outstanding after day 21.
Why is this a pilot?
Because matching what clients send to what you asked for has to be right before it's left to run. We're running it with a small number of pilot firms first.
Where does our data go?
We build agents in your own Microsoft 365, not on our servers, and we don't host your data. Agents your team talks to only see what that person can already see. Agents that run on their own use a dedicated service account, limited to the mailboxes, folders and systems the job needs, agreed with you in advance. We build in UK regions wherever Microsoft offers them, and anything that has to run elsewhere is set out for your compliance lead to approve before go-live. Microsoft doesn't use your Microsoft 365 content to train its foundation models, and every run is logged.

Next step

Talk to us about this agent.

A free 30-minute call with James. We'll check how your practice would trigger it and confirm the fixed price.