Key terms in this article
What is MCP?
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to business software in a controlled way. Instead of copying data into a chat window, the assistant queries the system directly, within whatever permissions it has been given.
What is an AI assistant?
An AI (artificial intelligence) assistant is a chat tool, such as Claude or ChatGPT, that understands plain-English requests. Once connected to a billing platform, it can answer questions like “how much did we collect last month?” from live data.
What is OAuth?
OAuth (open authorisation) is the standard way web apps grant each other access without sharing passwords. It is the same mechanism you use when a site offers “sign in with Google”, and it is how a well-built AI connection should work too.
What does 2FA mean?
2FA (two-factor authentication) means proving who you are with something extra beyond a password, usually a six-digit code from your phone. For AI connections to billing data, it stops a stolen password being enough to connect.
Ask ten resellers what they think about AI and you will get ten different answers. Some are already drafting customer emails with it. Some are waiting to see. A few would happily never hear the term again.
But something has changed this year, and it matters for billing specifically. AI assistants can now connect directly to business systems, in a controlled way, through an open standard called MCP. Your accounts package, your CRM, and yes, your billing platform. The question is no longer “will this happen?” It is “what should it look like when it does?”
Key Takeaways
- AI assistants such as Claude and ChatGPT can now connect to business systems through MCP, an open standard
- For billing, the prize is instant answers: revenue, collections, aged debt, and customer history in plain English
- The risks are real, so judge any vendor on permissions, consent, and audit trail, not on the demo
- Write access should always be off by default, with significant actions confirmed by a person
- We are bringing this to the SAFE platform soon, built on those exact principles
Why Would Anyone Connect an AI to Billing?
Because billing is where the questions live. Who owes us the most? How did collections go last month? Which customers are growing, and which are quietly shrinking? Every reseller asks these, and in most businesses the answers sit behind reports someone has to build.
An assistant connected to your billing platform answers them on demand. Ask in plain English, get the figure from live data, then ask the follow-up that the answer prompts. No exports, no version-three-final spreadsheet, no waiting for the one person who knows where the report lives.
There is a second prize too. When a customer rings, the assistant can pull their account, invoices, and payment history while you are still saying hello. Small time savings, repeated all day, across the whole team.
What Could Possibly Go Wrong?
Plenty, if it is done casually. Billing data is some of the most sensitive information a reseller holds. It covers what every customer buys, what they pay, and how promptly they pay it. Handing an AI unrestricted access to that would be reckless.
The risks worth taking seriously:
- Over-broad access. An assistant that can see everything, for everyone, forever.
- Shared credentials. One company-wide API key pasted into chat tools, impossible to trace or revoke cleanly.
- Silent changes. An AI that can edit records with no confirmation step and no record of what it did.
- No off switch. Connections that nobody can list, review, or kill when someone leaves.
None of these is a reason to avoid AI. They are reasons to demand the right design. The same worries applied to online banking once, and the answer was standards and controls, not staying away.
What Should Resellers Demand From a Billing Vendor?
If your billing provider offers AI assistant access, or promises it soon, put these five questions to them. The answers separate a considered feature from a bolted-on chatbot.
- Whose permissions does the assistant use? The right answer: the individual member of staff who connected it, never a shared account. If Sam cannot see dealer margins in the platform, Sam’s assistant should not see them either.
- How is the connection approved? Look for a proper sign-in with 2FA, using OAuth rather than pasted API keys.
- Is write access separate, and off by default? Reading a report and raising a refund are different powers. You should grant them separately, and changes should need a deliberate opt-in.
- Is there an audit trail? Every question and every action should be logged, marked as assistant activity, and traceable to a named person.
- Can you revoke it? Each person should be able to disconnect their own assistant instantly, and an administrator should have a company-wide off switch.
If a vendor cannot answer these clearly, the feature is not ready for your billing data, whatever the demo looks like.
What Are We Doing About It?
We have built AI assistant access into the SAFE platform, and it is launching soon. It follows every principle above, because we wrote the list by building it. Each connection belongs to one person, approved with 2FA. Read and write consent are separate, with changes off by default. Actions go through vetted workflows, everything lands in the audit trail, and there are off switches at both the personal and company level.
In practice, that means you will be able to connect Claude or ChatGPT and ask for your collections, aged debt, growth figures, or any customer’s history in plain English. With write access deliberately granted, the assistant can also handle small tasks, such as emailing an invoice or generating a payment link, and it confirms significant actions with you first.
You can read more on our AI assistants service page, or see how it compares with our existing API access for code-based integrations. The technical detail lives on the platform site.
Do You Have to Care Yet?
Honestly? Not this month. Your billing will run fine without an AI assistant, and healthy scepticism is a fair position.
But it is worth watching, because the direction is set. The Model Context Protocol is an open standard backed by the major AI companies, and business software is adopting it quickly. Within a year or two, asking your systems questions in plain English will feel as normal as searching your email. The resellers who benefit most will be the ones who chose vendors that did it carefully.
If you would like to be one of the first to try it, get in touch and we will add you to the early access list. And if you just want to talk through what AI does and does not mean for your billing, we are happy to have that conversation too. We are a family business; talking to resellers is rather the point.