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

Matching what clients send to what you asked for has to be right before it's left to run, so this agent starts with a pilot period.

How it runs

The PBC and records chaser starts on its own and stops for your team to approve.

What starts it, what it does and where your team approves are set out on this page.

Book a Copilot Readiness Check

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.

Ask it in Teams

Ask it a question. It answers from the same data.

The agent keeps the data it works from, so anyone on your team can ask it in Teams. It checks its sources and shows which ones it used.

Someone asks the agent in Teams: “What are we still waiting for from this client?” The agent checks the request list, client uploads and tracker, works out the answer and replies, showing the sources it used.

  1. 01 You ask in Teams
  2. 02 It checks its sources
  3. 03 It works it out
  4. 04 It answers, with sources

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

How it's bought

Built as part of a Firmwide install, or added to a Run plan from £2,500.

Firmwide install, first department
£6,950
Each extra department
£2,500
Extra agent on Run
From £2,500
Run
£750 or £1,950 a month

Most firms get it as their department's agent in a Firmwide install, typically six to eight weeks including mapping, with the price fixed on your Plan on a Page and the timetable by the end of mapping, built on the templates and procedures the foundation step put in SharePoint and connected to the systems it needs. Once live, Run keeps it working, from £750 a month with the first month included and Run optional after that. A bespoke agent built onto a Run plan is priced lower than one handed over with no support. Both prices are fixed before anything is built.

Microsoft's own usage charges (Copilot Credits) are billed by Microsoft to your firm. We estimate them during mapping and keep them low by design: routine steps run as standard automations and AI is only used where judgement is needed.

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.
Where does our data go?
We build everything in your own Microsoft 365, not on our servers, and we don't host your data. An agent your team talks to only sees what the person using it can already see, and the install sets permissions on least privilege. 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, every run is logged and every agent has a kill switch.
  1. User documentation

    Written for a normal member of staff, in plain English: how to use it day to day.

  2. Technical documentation

    For your IT team or another technical person: how it is built, where it lives, permissions, how to change it and how to switch it off.

  3. A hands-on handover session per department

    The people who will use it use it on their own data, with us in the room or on the call.

Next step

Find out where Copilot can and can't see your data.

Free, 30 minutes, online, with James. You leave knowing where Copilot can and cannot see your data, the two jobs to automate first and a rough install price.