Wedlake Consulting
Menu
Book a free intro →

Wedlake Consulting · Remote or in Manchester

← Notes

Let Copilot prepare the accounts. Keep approval with your team.

Microsoft's new finance capabilities make it worth asking what AI may prepare, who approves it and who can act. Put those boundaries in writing before connecting accounts.

Published
Reading
4 min
Topic
Governance

On 29 October 2026, Microsoft announced new finance capabilities across Copilot, including preparing reconciliations, drafting journal entries and assembling month-end review packages. Its announcement lists accounting capabilities as available in Frontier, while the Finance plugin for Cowork is generally available. Partner plugins are beginning to roll out, including work with accounting providers such as Xero.

For a small finance team, the useful question is where preparation ends and authority begins. I would answer that before connecting business accounts or handing over a live month-end task.

A tool that helps assemble the paperwork can be useful without having permission to approve it. Write down that distinction so the person configuring the system and the person responsible for the accounts understand the same boundary.

Separate preparing, approving and acting

Start with a task your finance lead can describe precisely: preparing a draft explanation of movements between the management accounts and the budget, for example. Agree what the finished draft must contain and who will receive it.

Then divide the work into preparation, approval and action. Preparation might include gathering approved reports and proposing explanations. Approval means a person checks the evidence and accepts responsibility for the result. Action might mean posting an entry to the accounts or sending the report to the directors.

Those are different permissions. I would begin a trial with preparation only, keep the normal finance approval in place and leave posting or sending with the staff already authorised to do it.

Microsoft says finance professionals retain control of recommendations, decisions, approvals and subsequent actions. This is the boundary I would turn into a working arrangement:

  1. SystemSource materials
  2. AutomatedPrepare a close review package
  3. ManualFinance professionals review
  4. ManualDecisions, approvals and actions
My recommended approval boundary, using the finance workflow described by Microsoft. This is a proposed working arrangement, not a claim that the product enforces these gates. Source: Microsoft's finance announcement, 29 October 2026.

Ask whoever configures the trial to show how its access and available actions match that arrangement. A sentence in an AI usage policy needs corresponding settings and a clear procedure for staff.

Check the connection before approving the trial

Do not assume that a provider’s name in an announcement means your accounts package is ready to connect. Microsoft says third-party services may need separate licences, subscriptions, authentication or administrator enablement.

Ask your Microsoft 365 administrator and accounting provider to confirm the exact capability available to your organisation, the cost and the permissions requested. Have them distinguish reading records from creating or changing them. If the connection asks for more access than the agreed task needs, pause and ask whether it can be narrowed.

Get the finance lead to identify the right company, reporting period and approved reports for the task. Make it explicit whether the trial may use payroll, employee expenses or customer-level records. For a first trial, I would choose work that can be tested with less sensitive material and use only tools already approved by the business.

Keep any unresolved access question open until someone can explain the answer. Connecting a system is a business decision about what information and actions you are making available.

Require evidence a reviewer can use

Agree what the reviewer needs alongside the draft. For a variance explanation, I would require the source report, reporting period, calculation and a clear distinction between a recorded fact and a proposed explanation. Ask the preparer to flag missing information rather than fill it with a plausible story.

A change in a total does not establish why it changed. The reviewer should be able to follow the explanation back to records or ask the colleague who knows the transaction. If that evidence is missing, the explanation remains unapproved.

Microsoft describes an optional audit trail for accounting capabilities in Excel, recording changes and their reasons in chat history. Where available, ask the administrator to demonstrate it and agree how the team will retain the evidence it needs. Keep the source material, final approved output and approval record together in your normal business filing process.

An AI change history and a finance approval answer different questions. The former helps explain what the tool did; the latter records who accepted the result and authorised the next step.

Make a narrow decision during November

For a November trial, I would put the agreement on a short page: the task, permitted information, permitted actions, required evidence, reviewer and the point where work must stop for approval. Ask the finance lead and administrator to walk through it together before using live information.

Try it on a completed reporting period with a known, approved result. Check whether the proposed explanations stand up to review and whether gathering evidence and correcting the draft takes more effort than the preparation it replaces. Include that checking time when deciding whether to continue.

If the trial is useful, agree the next scope explicitly. Preparing a good draft does not by itself justify permission to post accounting entries or send external messages. Those need their own decision, with the person responsible for the accounts involved.

The outcome I would aim for is a useful preparation task with an approval boundary everyone can explain. That gives a small team a concrete way to try the new capabilities while keeping financial authority clear.

Written by

Owain Wedlake, technology and AI consultant in Manchester. Questions or a different view? Reply by email.

Next step

Start with a conversation.

A free intro session. Bring one process that eats your team's time, and leave with a straight answer on what's worth changing.

Free · No obligation · Remote or in Manchester