Conversational ERP in Australia: What It Is, What's Shipped, and How to Keep It Safe

Ask a question in plain English, get an answer from live business data. That is the pitch for conversational ERP, and in 2026 it has moved from conference demo to shipping feature. Odoo 19 includes a built-in assistant. MYOB has signed a five-year deal with Microsoft to bring natural-language queries to MYOB Acumatica. 12% of Australian businesses now use AI, and among large businesses it is around 35%, so a chat box on top of the ledger is coming to your industry whether you plan for it or not.

Here is the part the vendor demos skip: the model is not the hard bit. The hard bit is deciding whose eyes the answer is allowed to see through.

What conversational ERP actually means

Conversational ERP is natural-language querying of a live business system. Instead of building a filtered report, you type the question the report was meant to answer: “which invoices over $10,000 are more than 30 days overdue?”, “what did we sell to Queensland customers last month?”, “which purchase orders are late?” The answer comes back from live data, not from a spreadsheet someone exported last Tuesday.

The people who benefit most are the ones who never learned the report builder. A warehouse lead who wants to know what is arriving this week. An owner who wants one number on a Saturday morning without phoning the bookkeeper. A sales rep prepping for a call who needs the customer’s order history and open credits in thirty seconds. That value is real, and it lands on day one because answering questions does not require the agent to change anything.

What conversational ERP is not: a reason to hand an AI system open access to everything. Which brings us to permissions.

The permissions question that decides everything

Every conversational ERP setup answers one question, either deliberately or by accident: whose login does the agent use?

If the agent runs as a shared super-user account, anyone who can type a question can read anything the ERP contains. Payroll. Margins. The warehouse casual asking “what does everyone here get paid?” is one autocomplete away from an answer no permission matrix would ever have shown them. The rule we set out in our AI agent governance guide applies with full force here: an agent acts with the requesting user’s exact data scope, never a shared privileged account.

“Whose login does the agent run under? That single question does more for safety than any model choice. Get it wrong and you have built a search engine for everything the ERP was carefully hiding.”

Josh Craig, Director, Auboros

There is also a compliance clock on this. From 10 December 2026, Australian privacy policies must describe automated decisions that use personal information and could affect people’s rights or interests. A read-only question box sits at the low-risk end, but once the same agent starts recommending credit holds or reading staff records, the disclosure obligation is squarely in frame. Design the permission model now rather than retrofitting it in December.

What Odoo and MYOB Acumatica offer today

It pays to be precise about shipped versus promised, because the gap is wide.

Odoo: shipped. Odoo 19 includes Ask AI, an assistant you can open anywhere in the database. Per Odoo’s official documentation, the standard assistant can open views and display reports but cannot create or alter records, and agents operate inside the signed-in user’s access rights. You can restrict an agent to approved sources, and it only gets write-capable tools you deliberately hand it. The AI apps are Enterprise-only. We covered the mechanics, and what the v20 roadmap adds, in our Odoo AI agents deep-dive.

MYOB Acumatica: mostly roadmap. MYOB’s April 2026 partnership with Microsoft promises contextual financial insights, natural-language queries and AI-assisted document processing for MYOB Acumatica, with the first jointly built features due late in 2026. That is an announcement, not a release. What ANZ customers can use today is narrower: AI Studio in technology preview plus the shipped 25 R2 features we walked through in our MYOB Acumatica AI review. If a salesperson tells you natural-language querying is live in MYOB Acumatica today, ask them to show you.

The bring-your-own route: available now, with work. You can also connect a hosted assistant to either platform through the Model Context Protocol, an open standard for wiring AI tools to business systems. An MCP server sits in front of the ERP with its own scoped credentials, so you decide what it can see and do, and you can swap the underlying model later without rebuilding. This is how we run our own agents. For Odoo, MCP servers exist today from the community and the app store; at the time of writing there is nothing first-party from Odoo SA.

A worked example: credit questions that stay read-only

Here is how the pattern looks for a wholesale distributor. An accounts receivable officer asks the agent: “which customers are over their credit limit and still placing orders?” The agent queries the ERP under her login, and only her login. It returns four customers, each with the exposure amount, the last order date and a link to the underlying records so she can check the numbers herself.

Then she asks it to do something about it: “draft hold notices for the two largest.” The agent writes two emails and proposes a credit-hold flag on each account. And there it stops. Nothing sends and no flag changes until she has read each draft and approved it. Reads are instant, writes wait for a human. That one rule is the difference between a useful assistant and an incident report.

Five questions before you switch it on

Put these to any vendor, integrator or enthusiastic staff member proposing a chat interface over your ERP:

• Whose login does it use? The agent should act with the requesting user’s permissions, never a shared account with broad access.
• Can it write, and where are the gates? Read-only is a fine starting point. Any write-back to ledgers, pricing, stock or customer records needs a named human approving each change.
• What gets logged? You want a record of who asked what, what the agent read and what it proposed. Auditors will eventually ask for it.
• Where does the data go? Know which model processes your prompts, in which country and under what retention terms before finance data flows through it.
• What is it allowed to answer from? Source and tool allowlists beat an open connection to everything. Start narrow and widen deliberately.

If those five have good answers, conversational ERP is one of the lower-risk places to start with AI: mostly reads, and easy to trial in a sandbox before anyone touches production. If they don’t, the chat box can wait.

---

Thinking about a plain-English layer over your ERP?

Auboros designs and runs drafts-first AI agents over Odoo and MYOB Acumatica from Brisbane, with role-scoped permissions and human approval on anything that writes. If you want to scope conversational ERP for your business, book a free consultation. We’ll tell you what’s shipped, what’s roadmap, and what’s worth waiting for.