AI Agents for ERP in Australia: Inside Xero, MYOB, NetSuite and Odoo
Trade orders still arrive as emailed PDFs. Supplier bills wait for someone to code the GST. Marketplace orders from Amazon.com.au and Bunnings Marketplace need fixing before they reach Cin7 or Unleashed. We build AI agents that do that work inside Xero, MYOB, NetSuite and Odoo, and save every record as a draft for your team to approve.
What does an ERP AI agent do for an Australian business?
An ERP AI agent reads the documents that start your office work, such as a customer purchase order or a supplier bill, and drafts the matching record in Xero, MYOB, NetSuite or Odoo. A named person approves each draft before it posts. The agent signs in with its own limited role, and every lookup and write is logged. FactoryJet builds custom ERP AI agents for Australian businesses on Xero, MYOB, MYOB Acumatica, NetSuite and Odoo, and shows each agent working on your own documents before you sign.
An ERP (enterprise resource planning system) is the software that holds your stock, orders and money in one place. An API is the published set of requests one program can send another to fetch records or add new ones. MCP, the Model Context Protocol, is an open standard that lets AI tools make those requests. An OAuth scope is one permission on a login, such as read invoices, so the agent can reach only what it is granted. A SuiteApp is an add-on installed inside NetSuite. Xero, NetSuite and Odoo all now publish ways for AI to connect.
This page is for established businesses: wholesalers and distributors with trade accounts, manufacturers quoting from part lists, and brands selling across a web store and several Australian marketplaces. If one person spends most of a day each week retyping orders or coding bills between two systems, that job is usually where the first agent goes.
Xero, MYOB, NetSuite and Odoo: what each one lets an agent do
Each system opens a different door to AI, and each door has its own limits. These notes restate the maker’s own documentation as we read it on 29 October 2026, with a link to check it yourself.
Xero
Through the Xero API and Xero’s own MCP server, published on GitHub, an agent can list, create and update accounting records, including draft invoices and quotes. Xero also announced a multi-year partnership with Anthropic on 27 March 2026. We build each Xero integration on those official connections and give the agent a role scoped to the job. Xero MCP server.
MYOB Business and AccountRight
Agents draft bills, invoices and sales orders through the MYOB API (MYOB Business API), and your team approves each one inside MYOB. The agent gets a login of its own, separate from any staff member’s. MYOB Business API.
MYOB Acumatica
MYOB’s cloud ERP for mid-sized businesses, formerly MYOB Advanced, covering finance, stock and projects in one system. The edition and licence you hold decide the connection; we confirm it in scoping. MYOB Acumatica.
NetSuite
Oracle has adopted the Model Context Protocol for NetSuite and ships MCP Standard Tools as a free SuiteApp. The role the agent signs in with sets what it can reach, so we design that role first, record type by record type. Oracle NetSuite AI Connector FAQ.
Odoo
Odoo 19 has its own AI agents, built from topics and sources. Outside agents use the External JSON-2 API, which Odoo says is only available on Custom pricing plans. The older RPC endpoints are due for removal in Odoo 22 and Odoo Online 21.1. Odoo External JSON-2 API.
Cin7 Core, Unleashed, QuickBooks
The inventory and accounts tools many Australian wholesalers run beside Xero or MYOB. The agent usually sits between them, so one order becomes one sales order and one invoice without anyone retyping it.
Six ERP jobs an AI agent drafts for your team to approve
Each job starts with something arriving from outside and ends with a draft record. None of them posts money, stock or a customer message without a person saying yes.
Customer purchase orders into sales orders
Trade customers email purchase orders as PDFs, spreadsheets or a few lines in the message body. The agent finds the customer, the delivery address and each SKU in Cin7, NetSuite or Odoo, checks the price on the PO against your price list, and saves a draft sales order with the original attached. A price difference is flagged, never quietly accepted.
See sales order automation with AI agents for this job in depth.
Marketplace orders and exceptions
Orders from Amazon.com.au, eBay, Kogan, Bunnings Marketplace or THE ICONIC usually arrive through a connector. The agent watches what the connector cannot handle: a SKU that does not map, a bundle, an address that fails validation. It drafts the fix and asks a person before anything is changed.
Supplier bills with GST coded
Supplier invoices arrive by email or through Peppol. The agent matches each one to its purchase order and goods receipt, suggests the account and GST code from how your team coded that supplier before, and drafts the bill in Xero, MYOB or NetSuite. Our accounts payable automation page covers this job in depth.
See accounts payable automation for Xero and MYOB. Peppol background: business.gov.au, eInvoicing.
Purchase orders from reorder points
A SKU in Unleashed or Odoo drops under its minimum, or a large trade order needs stock you do not hold. The agent prepares the supplier PO from the preferred supplier and last cost on file. Later, if the supplier writes back with a later ship date or a short quantity, your buyer sees it on the same screen.
Payment and settlement matching
Payouts from Stripe, Afterpay and Zip land as single bank lines that cover many orders, less fees. The agent breaks each payout down against its settlement report, matches the orders and fees, and prepares the reconciliation for your bookkeeper to approve.
Freight and order status answers
Staff and customers ask where an order is. A read-only agent looks it up in the ERP and the Australia Post, StarTrack or Sendle tracking, and answers in your help desk or team chat. It cannot change a record, because its role does not allow it.
What can an ERP AI agent change without a person approving it?
Your ERP stays the single source for price lists, stock on hand and trade terms. The agent asks for them fresh on every document it handles, so when your team updates a price in Xero or NetSuite at 9am, the 9.05am order is checked against the new figure.
The agent’s login decides what it can touch, so each system gets a narrow one of its own: a NetSuite role covering only the record types the job uses, Xero OAuth scopes for those records alone, an Odoo API key for one integration user, a MYOB login that belongs to the agent and no staff member.
- Looking up stock, prices, ordersread-only questionsAutomatic
- Drafting sales orders and billssaved as drafts in the ERPDraft only
- Confirming an order or posting a billa named approverApprove
- Payments, credits, price changesmoney leaving or movingAlways approve
- Payroll, STP, BAS lodgementoutside the agent’s roleNever
From your brief to a live ERP agent, in seven steps
Open any step to see what happens and what you get. The demo on your data comes at step three, before you sign anything.
01Read your brief and list the systems
We start from your written brief or a short call, then list every system the job touches, with its edition and plan: Xero or MYOB, NetSuite or Odoo, Cin7 or Unleashed, the store and the marketplaces.
You get: A one-page system map, with the plan limits that matter, such as Odoo’s Custom-plan rule for its external API.
02Collect real documents
You send 20 to 50 recent examples of the documents that start the job: customer POs, supplier bills, payout reports. We also note what your team entered for each one.
You get: A test set built from your own history.
03Show the demo on your data
A first version of the agent drafts records from that test set. Your team compares its drafts with what they entered. This happens before any contract.
You get: A side-by-side comparison you can judge for yourself.
04Write the rules and the approval points
What the agent may do alone, what needs a named person to approve, and what it can never touch. We also list the personal information it will see and which privacy rules apply.
You get: An agent specification and a fixed price for each phase.
05Connect with a dedicated, limited role
The agent gets its own login in each system, with only the record types and actions the job needs: a NetSuite role without Administrator rights, a Xero connection without payroll scopes.
You get: Working connections in a sandbox or test file.
06Run a supervised pilot
The agent drafts live records and a person approves every one for an agreed period. Each approval, edit and rejection is logged, so the numbers show when a step is ready to move to bulk approval.
You get: Pilot results and a go-live decision that is yours.
07Go live and keep it working
ERPs release updates and model makers retire versions. Odoo has already set removal dates for its older APIs. We watch the logs, re-test after changes and fix what breaks, inside the defect cover period and after it if you choose.
You get: A live agent you own, with the team that built it on call.
Next step
Send us one week of purchase orders or supplier bills
We will run them through a first version of the agent and show you its drafts beside what your team entered. Tell us which systems you run.
What to put in your brief for an ERP AI agent
A written brief gets a firmer answer than a contact form. If you are running a formal RFP, send it as it is. Otherwise these five points are enough for us to come back with questions and a scope.
- Your systems and editions. Xero or MYOB Business, MYOB Acumatica, NetSuite, Odoo and its plan, plus Cin7 Core, Unleashed, your store and the marketplaces you sell on.
- The one job to start with. For example, trade POs into sales orders, or supplier bills into Xero.
- Volume. Roughly how many documents arrive each week, and how many people handle them today.
- Who approves now. The person or role who signs off the record today, and any dollar limits.
- Dates that matter. A financial year end on 30 June, a system migration, a peak season.
- Questions on anything unclearFirst reply
- A system map with plan limitsWritten
- A demo on your documentsBefore you sign
- Scope and price per phaseFixed
- Founder on every replyWithin 24 hours
ERP AI agent project terms: demo, fixed price, code ownership
The same terms on every project, written into the proposal. An ERP agent needs re-testing each time the ERP or the AI model changes, so what happens after launch is written down as plainly as the build.
A demo on your data before you sign
Working software on a sample of your real documents, so you judge the drafts, not a slide deck.
Fixed price per phase
Each phase is scoped, priced and signed on its own. You can stop after any of them.
You own the code from day one
Everything we write sits in your repository. Nothing depends on a FactoryJet login.
Your accounts, at cost
The AI model and hosting can run in your own accounts at cost, with no markup from us.
Defects fixed inside the build price
For a cover period we agree in writing before work starts.
Support is optional
Each change is quoted and approved. No monthly minimum. We can keep managing the servers, models and connections if you want us to.
The Australian rules that shape an ERP agent
Staff details on expense claims and bank details on supplier cards are the fields most easily swept into an ERP agent by accident. The OAIC’s AI products guidance also says checking an AI product is not a set-and-forget job. So the list of fields each agent may see goes into its written specification before we build, and is reviewed whenever the agent takes on a new job.
A worked example for APP 1.7: an agent checks each trade order against the customer’s credit limit. If it flags an order over the limit and a credit controller decides what happens, the agent only advises. If it puts a sole trader’s account on stop by itself, it sits much closer to the decisions the 10 December 2026 rule covers, and your privacy policy may need to describe it. We build the first kind by default and leave the call on the second to your adviser.
Once your software is connected to Peppol, supplier eInvoices arrive as data, so the agent skips the reading and goes straight to matching. Business.gov.au notes that the ATO runs the network but cannot see the invoices sent across it. GST codes are suggested from your own tax rates and supplier history, and approved by a person. BAS lodgement and Single Touch Payroll reporting stay with your accountant and payroll software.
Sources: OAIC, guidance on privacy and commercially available AI products; OAIC, APP guidelines chapter 1; business.gov.au, eInvoicing.
- Only the fields the job needsPrivacy Act
- Business AI terms, never a public chatbotOAIC
- A record of what each agent decidesAPP 1
- GST suggested, approved by a personYour rates
- No BAS, STP or payroll accessExcluded
We are not lawyers or tax agents and do not give legal or tax sign-off. We build to the rules you and your adviser set.
Built-in ERP AI vs an off-the-shelf app vs a custom agent
Start with what your system already gives you. A custom agent earns its place when the job crosses systems or needs your own approval rules. Off-the-shelf here means tools such as Dext and Hubdoc, which capture bills and receipts into Xero or QuickBooks Online, and ApprovalMax, an accounts payable approval tool for Xero, QuickBooks Online and NetSuite.
Swipe sideways to see every column.
| What you get | Custom agent (FactoryJet) | Built-in AI (JAX, Odoo AI, NetSuite connector) | Off-the-shelf app (Dext, Hubdoc, ApprovalMax) |
|---|---|---|---|
| Best fit | Jobs that cross Xero, Cin7, a store and marketplaces | Questions and tasks inside one system | One standard task, such as bill capture or bill approval |
| Your approval rules | Written with you, per record type | The maker’s settings | The app’s settings |
| Works across systems | Yes, by design | Mostly within its own system | Usually two systems |
| Demo on your data first | Before you sign | Included or add-on, try it in your own system | Varies by vendor, often a trial |
| Who owns it | You: the repository | The ERP maker | The app vendor |
| Support after launch | Same team, optional, no monthly minimum | The maker’s support | The vendor’s help desk |
How much does an ERP AI agent cost in Australia?
Flowtivity’s March 2026 Australian guide puts multi-system workflow automation at A$20,000 to A$50,000 or more over 6 to 12 weeks. That is a market range, not a FactoryJet price. Where a project lands depends mostly on the four things below.
- How many systems the agent writes to. Reading from Xero is lighter work than writing to Xero and Cin7 in the same step.
- How messy the documents are. Peppol eInvoices are structured; scanned PDFs and free-text emails need more testing.
- The approval design. One approver is simpler than limits by dollar value, customer or supplier.
- Access and plans. An Odoo database not on a Custom plan, or a NetSuite account without the right features, adds a step.
- Systems written toReach
- Document types and qualityHandling
- Approval levelsControl
- Plan and permission changesAccess
- AI model and hostingYour accounts, at cost
- Demo on your dataBefore you sign
ERP integration work on Odoo and QuickBooks
Connection work on the same platforms an Australian ERP agent uses, which is where most of the effort in an agent project goes. Our ERP agent work covers RFQ automation, daily bookkeeping and the generation of purchase and sales orders, on Odoo, NetSuite, SAP Business One, ERPNext and custom-built ERPs. Before any contract we show working software on the buyer’s own data: for one prospect, a demo pricing agent ran on their own rule book and re-priced a job they had already quoted.
Sow Easy
B2B distribution · WooCommerce and Odoo. A WooCommerce trade store being joined to Odoo, with Odoo as the master for stock, pricing and product identifiers. It is being tested against Odoo’s staging system; launch is still ahead. The same Odoo connection work sits under an Odoo AI agent. Read the case study.
Two Shopify + QuickBooks projects
Shopify · QuickBooks Online and Enterprise. Both in progress: one Shopify store being joined to QuickBooks Online, the other to QuickBooks Enterprise, so orders reach the books without retyping. See our ERP agent work.
ERP AI agents: questions Australian finance and operations teams ask
Replies within 24 hours.
Q01What is an ERP AI agent?
It is software we build to work inside Xero, MYOB, NetSuite or Odoo. Something lands in an inbox, say a trade customer’s purchase order or a supplier bill. The agent pulls out the lines, checks them against your customers, prices and stock, and leaves a draft record waiting. Someone on your team reviews that draft. Nothing is confirmed or posted until they say yes.
Q02Is AI replacing ERP systems?
No. The makers are building AI into their own systems instead. Xero announced a partnership with Anthropic in March 2026 to bring Claude into Xero. Oracle has opened NetSuite to outside AI clients through MCP. Odoo 19 ships its own AI agents. Every agent we build reads its facts from your ERP and writes its drafts back there, so the ERP becomes more central, if anything.
Q03What is the best AI for ERP?
Start with what your system already supports, then pick a model for the job. For NetSuite, Oracle names Claude Pro and ChatGPT as clients that work with its AI Connector Service today. Xero is partnering with Anthropic, the maker of Claude. For a custom agent we choose the model with you, based on the task, how messy the documents are and where your data is allowed to go.
Q04Can AI bookkeeping or ChatGPT do my books?
A chatbot on its own should not run your books. AI bookkeeping that works is narrower. A custom agent can take the repetitive layer: lining up Stripe or Afterpay payouts against orders, finding the purchase order behind each supplier bill, and proposing a GST code from your past coding. The result is a queue of drafts for your bookkeeper, who still approves every line and still owns the BAS.
Q05Is it safe to put bank statements into ChatGPT?
Not into a free, public chatbot. A bank statement names the people and businesses you pay and are paid by, and the OAIC’s AI guidance tells organisations to keep personal information out of publicly available generative AI tools. A custom agent is different: it runs under business terms, sees only the fields its job needs, signs in with its own limited login and logs every lookup. Bank data then stays inside a setup you control.
Q06Is Xero an ERP?
Xero is accounting software, and many Australian businesses run it as the centre of a wider stack: Cin7 Core or Unleashed for inventory, Shopify or a marketplace for sales, a payroll app alongside. Together those behave like an ERP. An AI agent works well across that kind of stack, because most of the slow work is copying data between the pieces. When the stack outgrows Xero, MYOB Acumatica, NetSuite and Odoo are the usual next steps.
Q07Can ChatGPT or Claude integrate with Xero?
Yes, through the Xero API and Xero’s own MCP server. Xero publishes the MCP server on GitHub under the MIT licence, and the README lists tools to list contacts, invoices and bank transactions, create invoices and quotes, and update draft invoices. Any MCP-capable AI client can use it. We use the same route for custom agents, with OAuth scopes (the list of record types a login is allowed to touch) limited to the records the job needs. Payroll and Single Touch Payroll reporting stay in your payroll app.
Q08What is the Xero MCP server?
MCP, the Model Context Protocol, is an open standard for connecting AI applications to outside systems. Xero’s MCP server is its implementation for Xero, published on GitHub. It signs in either with a Custom Connection, where you set a client ID and secret, or with a bearer token (a temporary access key passed with each request) for working across several Xero organisations. Its tools cover reading, creating and updating accounting records, so the permissions you grant matter.
Q09What is Xero AI (JAX), and how is a custom agent different?
JAX is the name Xero gives its own AI. In its March 2026 release Xero called JAX its AI superagent and said it would handle tasks such as predicting cash flow gaps and identifying unpaid invoices. JAX works inside Xero. A custom agent is for jobs that cross systems, such as turning an emailed purchase order into a Cin7 sales order and a Xero invoice, with your own approval rules.
Q10Can an AI agent work with MYOB?
Yes, through the MYOB API. One Business API covers AccountRight, Essentials and MYOB Business, per MYOB’s developer pages, and new Australian customers are now put on MYOB Business rather than the older two. An agent can read and draft records there under its own access. For mid-sized businesses on MYOB Acumatica, MYOB’s cloud ERP formerly called MYOB Advanced, we confirm the connection your edition allows during scoping.
Q11Does NetSuite have AI?
Yes. NetSuite now speaks the Model Context Protocol, according to Oracle’s help centre, and ships a SuiteApp (an add-on installed inside NetSuite) called MCP Standard Tools for working with your NetSuite data, with the option to build your own tools. Oracle does not charge for the connector or that SuiteApp, per its FAQ; the cost sits with your AI client subscription, if any. We build custom tools on top when a job needs rules the standard set lacks.
Q12How do I connect an AI agent to NetSuite?
Switch on what Oracle lists: two features, Server SuiteScript (NetSuite’s own scripting) and OAuth 2.0 (a standard sign-in method for apps), plus the MCP Server Connection permission on the role the agent uses. The standard tools also need REST Web Services (NetSuite’s web API) if the agent creates or updates records. Oracle blocks the connection for Administrator and for roles with full permissions, which forces a narrower role. We set up a dedicated role with only the record types the job touches.
Q13Does Odoo have AI agents?
Yes, in Odoo 19. Odoo’s documentation calls an agent a smart assistant that understands natural language and performs tasks, built from topics, which hold its instructions and tools, and sources, which hold its reference material. Creating agents needs the AI app installed. For agents that live outside Odoo, check your plan first: Odoo says its external API is only available on Custom pricing plans.
Q14We have an old Odoo integration. Will it keep working?
Check which API it uses. Odoo’s developer docs give the XML-RPC and JSON-RPC endpoints (the two older ways programs talk to Odoo) an end date: Odoo Online 21.1 in 2027, then Odoo 22 in 2028. Anything new should use the External JSON-2 API, which takes a bearer API key. If your current connector uses the old endpoints, we can move it across while building the agent.
Q15Can an AI agent work with Cin7 or Unleashed?
Yes. Many Australian wholesalers keep stock in Cin7 Core, formerly DEAR, or Unleashed, with Xero or MYOB holding the books. Some run QuickBooks Online instead. An agent often sits between them, turning an order into a sales order in the inventory system and an invoice in the accounts. We check which connection each system offers on your plan before quoting.
Q16Does the Privacy Act apply to an ERP AI agent?
Yes, if your business is covered by the Privacy Act 1988 and the agent handles personal information. Customer names and delivery addresses on a sales order are personal information, and the OAIC’s guidance says your obligations follow that data into the AI and into the drafts it writes back. We map which fields each agent sees before building, and keep everything else out of its reach.
Q17Is a credit-limit agent covered by the December 2026 privacy rules?
They might. From 10 December 2026, APP 1.7 requires covered businesses to explain in their privacy policy when a computer program uses personal information to make, or substantially help make, a decision that could significantly affect someone’s rights or interests. An agent that drafts a sales order for approval is unlikely to be that. One that sets credit limits or refuses accounts might be. We document what each agent decides so your adviser can judge.
Q18Will the agent code GST and lodge our BAS?
It will suggest GST codes, and it will not lodge anything. The agent proposes a tax rate on each draft bill or invoice from the supplier’s history and the tax rates set up in Xero or MYOB. A person approves the batch. Your BAS, and every conversation with the ATO, stays with your bookkeeper or registered agent. Payroll and Single Touch Payroll reporting stay in your payroll software, outside the agent’s role.
Q19Can the agent handle Peppol eInvoices?
Yes, and they are easier than PDFs. Business.gov.au says Peppol is a common standard in Australia and that eInvoices are delivered through ATO-approved service providers to software connected to the Peppol network. Because the invoice arrives as data rather than as a page to read, the agent spends its effort on matching it to the purchase order and receipt, then drafting the bill for approval.
Q20How much does an ERP AI agent cost in Australia?
Flowtivity’s March 2026 Australian guide puts multi-system workflow automation at A$20,000 to A$50,000 or more, and a full consultant-led implementation at A$15,000 to A$50,000 or more. The guide says its figures are in AUD and does not say whether GST is included. These are market ranges, not our prices. FactoryJet quotes a fixed price per phase in writing after a short scoping call.
Flowtivity, Australian AI agent pricing guide (March 2026) ↗
Q21How long does it take to build an ERP AI agent?
Flowtivity’s Australian guide gives 6 to 12 weeks for multi-system workflow automation, which is a fair guide for an agent that writes to two systems. One that only reads and answers is quicker. Access is often the slowest part: a sandbox or test file, a dedicated role for the agent, and a yes from the person responsible for the ERP. The timeline goes in writing with the quote.
Q22Can we see it working before we sign?
Yes, and we insist on it. You send a sample of last week’s emailed purchase orders or supplier bills. We run them through an early version of the agent and put its drafts next to what your team keyed in by hand. You decide from that comparison whether a build is worth paying for.
Q23Can we send a brief or an RFP?
Please do. A written brief gets a faster, firmer answer than a form. Name the systems and editions you run, the job you want the agent to take, roughly how many documents arrive each week, who approves today, and any deadline such as a financial year end or a system migration. We reply with questions, then a written scope and a fixed price per phase.
Q24Who owns the agent, and what happens after launch?
Your business does. The repository is yours from the first commit, along with the prompts and connection code. If you prefer, the model and hosting bills go straight to your own accounts, at cost and without any markup. Anything we got wrong is fixed within the build price during a cover period set before work starts. After that, support is your choice, priced per change, with no monthly minimum.
See your own orders and bills drafted by an agent before you sign
Send your name, work email and the systems you run. The founder replies within 24 hours to arrange a demo on a sample of your documents. No spam, no obligation.