MYOB Acumatica AI: What Australian Finance Teams Can Switch On Today

Updated 15 September 2026: MYOB renamed AI Studio to AI Automation and now lists eight AI features for MYOB Acumatica; the release names now use MYOB’s own version numbers (2025.2 and 2026.1) instead of Acumatica R-numbers; MYOB’s statement on where AI data is processed changed and is corrected below; the Acumatica global AI page and the Microsoft partnership were re-verified; added the short answer, an At a glance block, question headings, a captioned feature table, “Goes well with” and a rebuilt FAQ.

As at 15 September 2026, MYOB lists eight AI features for MYOB Acumatica: AI Assistant, AI Automation (formerly AI Studio), AP Bill Entry, Expense Management, Anomaly Detection, Production Variance Anomaly Detection, Cross-Sell Assistant and Auto Complete. Each one drafts, suggests or flags and leaves the release to a person. Global Acumatica features such as MCP access are announced with no confirmed ANZ date.

At a glance

• Who it is for: CFOs, financial controllers and operations managers running MYOB Acumatica (formerly MYOB Advanced) who want to know which AI features are in their tenant today, which are still global Acumatica announcements, and what to switch on first.
• Problem it solves: planning around a feature you read about in a global Acumatica or Microsoft announcement that is not in the MYOB release you are running.
• Platforms: MYOB Acumatica 2025.2 and 2026.1 (MYOB’s own version numbers for the ANZ product); the global Acumatica product runs ahead of it and its features are labelled separately below.
• What ships today (MYOB’s list, 15 September 2026): AI Assistant, AI Automation, AP Bill Entry, Expense Management, Anomaly Detection, Production Variance Anomaly Detection, Cross-Sell Assistant, Auto Complete.
• What is global Acumatica only: MCP access for Claude, Gemini, Cursor and other MCP-compatible tools, the case summaries and file tagging agents, and the 2026 R2 items on Acumatica’s AI page; none has a published MYOB ANZ date.
• What is roadmap: the features MYOB and Microsoft promised for MYOB Acumatica under their April 2026 partnership (contextual financial insights, natural-language queries, AI-assisted document processing), due “late 2026” per the announcement.
• Approval gate: AP Bill Entry and Expense Management create documents for a person to review and release; AI Automation prompts run when a person clicks the action; Anomaly Detection and the Cross-Sell Assistant flag and suggest; nothing in the list posts to the ledger without a person.
• Where the data goes: MYOB stores customer data in Australia; depending on the feature, AI processing happens in Australia or through global infrastructure run by Anthropic, AWS and Microsoft, which may process but not store or train on it, per MYOB’s AI page.
• Typical cost: the AI features are part of the platform and “subject to licensing” per MYOB’s LLM provider documentation; confirm with your account manager. A scoped agent pilot on top of the platform typically starts from a few thousand dollars ex GST per our AI agent services page.
• Typical timeline: switching the built-in features on is an administrator task measured in hours; a custom agent pilot is 4 to 10 weeks from discovery to a drafts-first go-live per the same page.
• Last verified: 15 September 2026 against MYOB’s AI features page, the MYOB Acumatica knowledge base and Acumatica’s AI page (modified 26 August 2026).

Every few weeks another AI announcement lands from Acumatica, MYOB or Microsoft, and somewhere in Australia a finance manager opens their MYOB Acumatica tenant looking for the feature it described. Usually it isn’t there yet. Sometimes the announcement covered the global Acumatica product, which runs months ahead of the ANZ release. Sometimes the feature has been renamed since the press release.

That gap causes real planning mistakes. So here’s the sorted version: what MYOB Acumatica AI can do in the release Australian customers are running, what’s a global announcement, and what’s still a promise with a date attached. Everything below traces to a vendor page checked this month.

What AI features does MYOB Acumatica have today?

MYOB’s own AI features page lists eight, and the list is worth reading as a finance person, because each item sits at a different point on the read-to-write scale.

• AI Assistant: ask questions in plain language about revenue, customers, invoices, inventory and financial performance, or start from a ready-made prompt. Reads and answers; changes nothing.
• AI Automation (previously called AI Studio): custom prompts you attach to any form, written once by an administrator and run by anyone with access to that form. MYOB’s knowledge base confirms the rename in its setup article.
• AP Bill Entry: document recognition that reads a supplier invoice and creates the bill for someone to check and release.
• Expense Management: receipt recognition on the mobile app that fills in the expense claim from a photo.
• Anomaly Detection: learns what normal looks like across expenses, supplier invoices and other transactions and flags the unusual ones.
• Production Variance Anomaly Detection: the manufacturing version, watching production costs, labour time and efficiency.
• Cross-Sell Assistant: suggests complementary items from your sales history at the point of sale.
• Auto Complete: text completion while you type in notes and status fields.

Notice what they have in common. Every one of them drafts, suggests or flags. A bill created from a PDF still waits for release. A flagged variance still waits for a production manager to decide it matters. That’s the shape of AI we tell clients to trust first, and it’s the same drafts-first pattern we apply to AI agents for ERP in Australia generally.

To use any of it, an administrator goes to the Enable/Disable Features screen and ticks the AI features on, per MYOB’s turning-on guide. Two things about that screen are worth knowing. The tick list still shows both “AI Studio” and “AI Automation”, a leftover of the rename. And the AI features sit under “Experimental Features”, which is MYOB’s way of saying they’re available, documented and supported, but young. Read the release notes for your version before you build a month-end process on one.

Demand for this is not speculative. MYOB’s ERP Trends research found 78% of wholesale distribution businesses plan to use AI in their ERP, and the ABS reports that 12% of Australian businesses used AI in 2024-25, rising to 35% of large businesses. The question for most mid-market finance teams is no longer whether to use AI, it’s which features are real in their release.

How does AI Automation work, and what does it send to the model?

AI Automation is the piece most Australian buyers should look at first, because it’s the one you shape yourself. You write a prompt on the LLM Prompts form, attach it to a source form such as Cases or Stock Items, and it appears as an action on that screen. MYOB ships a prompt library by function: finance, sales and customer, people, supply chain, projects, manufacturing and field services. The sales set includes a draft order acknowledgement, a sales quote proposal summary and an account pre-engagement briefing; the people set includes summarising employee status and checking timesheet hours.

Here’s how that looks as a worked pattern for a wholesale distributor. A prompt on the Purchase Orders form reads the open order and the supplier’s delivery history on the record, and drafts a chasing email with the PO details filled in. The purchasing officer opens the order, clicks the action, reads the draft, edits the two lines that misread the situation, and sends it. Nothing leaves the building without a person deciding it should. The prompt removes the hour of looking things up, not the judgement.

The plumbing matters for the CFO in the room. On version 2025.2 an administrator sets up the MYOB-managed connection (the provider is MYOB’s own AWS Bedrock proxy, no API keys to manage); on 2026.1 it’s available immediately, per the setup guide. If you want to use your own provider, MYOB’s documentation lists Azure, Amazon Bedrock, OpenAI and Anthropic connections, and warns that providers retire models with little notice, so someone has to own the connection. Before any prompt runs, the platform applies the user’s existing access rights and audit logging, and only authorised users can configure or run prompts.

The control we like most is data masking. You mark fields in the prompt, account numbers, prices, the customer’s name, and the model receives placeholders. The real values never leave MYOB Acumatica; the platform swaps them back into the response, and a trace page shows exactly what was sent. One limit to know: a field buried inside a larger text block, such as an email body, can’t be masked. Keep sensitive values in their own fields.

Where does MYOB Acumatica AI data actually go?

This is the paragraph we corrected in this update, because MYOB’s own wording changed. The launch material we quoted in August said AI processing ran in local data centres and data never left Australian or New Zealand borders. MYOB’s current AI page says something more precise: customer data is stored in Australia; depending on the feature, AI processing happens either in Australia or through global enterprise infrastructure run by Anthropic, AWS and Microsoft; those providers can process data to generate a response but cannot store it or use it to train models; and anything MYOB retains, including conversation history, stays inside the platform in Australia.

That’s still a good answer, and it’s a better answer than most vendors give. But “may be processed offshore for some features” is a different sentence from “never leaves the country”, and your privacy policy, your customer contracts and your risk register need the accurate one. If customer or employee data flows through an AI feature, check your obligations under the Australian Privacy Principles using the OAIC’s guidance on commercially available AI products, and use masking for anything the model doesn’t need to see.

Why aren’t Acumatica’s AI headlines in your system yet?

This is the part most coverage skips. Acumatica, the global platform MYOB Acumatica is built on, publishes an AI page (last modified 26 August 2026) that describes an AI Assistant that understands the screen you’re on, a case summaries agent that condenses long support threads, a file tagging agent, AI-powered product help, and Model Context Protocol access so Claude, Gemini, Cursor and other MCP-compatible tools can read permitted data under existing role security. Several items on that page are marked 2026 R2. Global Acumatica announcements generate most of the AI headlines you’ll read.

MYOB Acumatica typically receives global Acumatica features 6 to 9 months after the global release, because MYOB localises each release for ANZ payroll, GST and compliance before shipping it, and it numbers its releases by year (2025.2, 2026.1) instead of Acumatica’s R-numbers. As at 15 September 2026, MYOB’s feature list does not include MCP access or the two agents above, and MYOB hasn’t published a committed ANZ date for them. Our MCP for ERP guide explains what MCP access would mean when it lands, and how to connect an external model to MYOB Acumatica through the API under a scoped user in the meantime.

So when you read about an Acumatica AI capability, ask one question before it goes anywhere near a plan: which release is that in, and is it a MYOB release? Your partner should be able to answer from the release notes. If they can’t, that tells you something too.

What does the Microsoft partnership promise, and when?

In April 2026, MYOB and Microsoft signed a five-year partnership to jointly fund and build AI features across MYOB’s products, using Microsoft’s Foundry, Copilot Studio and Agent 365 tooling. For MYOB Acumatica specifically, the announcement promises native AI features for contextual financial insights, natural-language queries and AI-assisted document processing, with the first customer-facing features due late 2026.

All of that is roadmap. As at 15 September 2026, MYOB’s feature list doesn’t attribute any MYOB Acumatica feature to the partnership; Microsoft appears on the AI page as one of the processing providers. The partnership is a credible signal of where the platform is heading, and the natural-language query direction lines up with what the AI Assistant already does and what our clients keep asking for. But a signed partnership is not a feature in your tenant. Don’t build a business case on it until release notes say otherwise.

Switching things on safely

The features above are the vendor’s side of the story. The other side is yours: an AI feature is only as safe as the controls around it and only as useful as the data underneath it.

The controls are the ones we set out in AI agent governance: role-scoped access so a prompt sees only what the person running it could see, human approval on anything that writes to the ledger or leaves the business, and an audit trail of what was suggested and who accepted it. MYOB Acumatica gives you most of that natively for its built-in features. One catch we’ve documented elsewhere: on the Process Bank Transactions form, payments the system creates from matched lines skip approval workflows, so a reconciliation agent has to put its gate on the match list, not the payment. Anomaly Detection is the feature to pair with a month-end close agent, and AP Bill Entry and Expense Management are the native starting points the expense claim verification agent builds on.

The data question decides more outcomes than the model does.

“The businesses getting value out of these features aren’t the ones with the most ambitious use cases. They’re the ones with clean item files, tidy supplier records and consistent naming. Point a prompt at messy data and you get confident drafts of the wrong thing.”

Bill Alvarez, Practice Manager, Auboros

If you want to be ready, the useful work this quarter is unglamorous: clean the master data the first prompts will read, decide which workflows you’d trust to drafts-first automation, switch on AI Automation in a test tenant and try three prompts from MYOB’s library, and put a one-page AI usage policy in front of your team. We covered what that looks like in practice in our guide to what AI agents actually do inside Australian businesses. If you’re weighing the platform itself, we’re a MYOB Acumatica partner in Brisbane and can show you these features on a demo tenant with your own data.

Goes well with

• AI agents for ERP in Australia: what to build on top of the native features once you’ve switched them on, and what a scoped pilot costs.
• MCP for ERP: how to connect Claude, Copilot or your own model to MYOB Acumatica through a scoped API user today, and what changes when MCP access reaches the ANZ release.
• AI agent governance for Australian businesses: the four controls to have in place before the first prompt runs on customer data.

Working out what MYOB Acumatica AI is worth to your business?

Auboros implements and supports MYOB Acumatica across Queensland and beyond, and we run AI agents against live ERP systems in our own operations, so we can tell you which of these features will earn their keep in yours. Book a free consultation and we’ll go through it with your data, not a demo script. No pressure either way.