Copilot and Claude now have an accounting team. Make it yours.


Microsoft and Anthropic are giving us the beginnings of an AI accounting and finance team.

Let's see what it looks like in Copilot, in Claude and in ChatGPT, and how we can bring it in and make it our own.

Copilot: Accounting for Cowork

In Copilot, I went to the plugins area and searched for Accounting for Cowork.

A skill is a playbook.

A plugin is a bunch of skills and connectors and some files, all working together.

The Microsoft accounting plugin has about a dozen skills, like financial statements, reconciliation and journal entries.

The accounting root skill teaches the AI how to behave when it does accounting. For example, always offering an audit trail, and always including the outcome, entity, period and scope, a step-by-step breakdown of the process, the material decisions, the assumptions made, and when to stop and what to check.

The journal entry skill tells the AI to start with the accounting root skill, so it knows how to behave, and then how to do a journal entry.

I particularly like this part: base every figure and conclusion on the system of record, not on trackers and other things.

Then it covers reversals, the arithmetic, and specific entries like AP accruals, fixed assets, prepaids, payroll and revenue.

And it has a list of gates before anything is released: arithmetic integrity, accounting validity, completeness and authorisation, with authorisation levels.

It is optimised for the US

Look at the About section of the plugin. It says it's optimised for English US.

When you look at it in detail, or ask your AI to compare it like I did, you'll find some references to US laws and US reference material.

And there are things it doesn't have.

The skills don’t mention GST anywhere.

They don’t deal with our payroll (super, PAYG).

And there is no mention of the Australian or New Zealand accounting standards.

Claude: the Finance plugin

In Claude, we go to the Customize area, then Plugins. Here it's called the Finance plugin.

There's a shorter list of skills. The journal entry prep skill is very similar, but more concise. It covers fixed asset depreciation, prepaid expense amortisation and payroll accruals.

Compared to Microsoft’s, the Claude skills seem more bullet-point level. Less micromanagement.

They're very similar for a reason. Microsoft tells us so, in its journal entry skill:

"This experimental Microsoft revision consolidates the Microsoft Journal Entry and Journal Entry Standards baseline. That baseline incorporates guidance from Anthropic's Finance & Accounting plugin."

So they come from the same world.

ChatGPT: one short skill

In ChatGPT, when I searched for accounting, there was just one skill, and a relatively short one.

It doesn't go into journal entries or reconciliations. It's very high level: keep communication focused on the user's work, make the work easy to verify, keep a changelog, then a few principles for bookkeeping, reviews and audits, and presenting your findings.

That's it. It's a guide to the principles of good accounting work, not specific procedures.

I wouldn't just install any of them

To me, all of these are best practice for how to write good skills for AI, coming from Anthropic, Microsoft and OpenAI. Who better to do that?

But I wouldn't just go and install these plugins.

They're not localised to our country. They're US-based.

They're designed for in-house finance teams in pretty large businesses, rather than for accounting firms.

So we need to take them and adapt them to our business.

There are two ways I suggest, and both use our AI.

Option one: take their skills and adapt them: "Hey Copilot/Claudie/Chatty, go get copies of all these skills, and let's look at how to adapt them to my business."

Option two: start from the skills you already have. "Hey Copilot/Claudie/Chatty, look at the skills we already created for you. Then research these skills published by Anthropic and Microsoft, find the gaps, and let’s talk about ways to improve our ones."

Why I don't like layering

Another approach you’ll hear suggested is layering.

Install the plugin as it is, then create your own skills on top that tell it how to act differently.

I don't like it. I think it's confusing, and there's going to be too much mess in our system.

It's like hiring a US-based accountant, letting them keep all their US knowledge, and then saying, "Yeah, but remember that we do things slightly differently here."

There are going to be contradictions. And they can lead to inconsistencies.

I don't want that. I just want our local Australian or New Zealand knowledge.

It's the same with skills built for large corporates, talking about ERP systems and authorisation levels, and then adding, "And here's the override you should remember for me."

I'd rather take the skill and update it.

The downside: when Anthropic or Microsoft update their skill, I won't know, because I'm working on my own copy of the skill.

I think that's okay. Every three months, a reminder in my calendar (or a task for my AI) goes and checks for new or updated skills, compares them to mine, and suggests any changes. It also checks whether they've released localised ones.

Two more finds in Claude

Claude gives us another trick. In the plugin library there's a plugin called Plugin Management, and one of its skills is the Cowork plugin customizer.

It teaches Claude how to customise a plugin for us: reviewing the plugin, looking at how we work, interviewing us about what's missing, chatting about how we want it to work, and then making the adjustments.

That's how I usually work anyway. I don't install plugins. I just say, "Hey Claude (or Copilot), research these skills online. Look at how we work. Let's brainstorm together and build skills for us."

The other one I want you to know about is the Small Business plugin in Claude. It has 44 skills. That's a lot.

They go across lots of different areas. Some are accounting and finance, like cash flow and closing the month. Others are content strategy, contract review, invoice chasing and many more.

Again, I'm not suggesting you install it and use it to run your business. It's an awesome place to look, and to get your AI to look, so we develop better skills together.

Only take skills from reliable sources

There are many more skill libraries online.

Everyone's pushing them now.

I suggest we download skills only from very reliable sources, like Microsoft, Anthropic and OpenAI.

Downloading from any other party is like telling my AI, "Hey, do you see this person I don't know? Do whatever they say. Take their playbook and just follow it."

I don't know what's going to be in there. That's a risk.

If you find one you really like and everybody's telling you it's amazing, at least sit and read the entire thing, word by word. I know they're long. That way you know what instructions you've given your AI.

What to do today

Go and look at these libraries. Send your AI to read them and to suggest how to adapt them to your business.

You'll see an amazing change in how AI behaves when you start giving it skills.

We've got this,

--

Inbal Rodnay

Guiding Firms in AI Adoption and Automation

Keynote speaker | AI Workshops | Executive briefings | The Tech Savvy Firm


Next
Next

Xero into Excel in one prompt