Skip to content
Auboros

The AI Agent Register: How to Stay in Control When Your Business Runs More Than One Agent

An AI agent register lists each agent's job, owner, permissions, approval gate and cost. Why the OAIC's 30 September 2026 guidance makes it matter.

By Bill Alvarez, Practice Manager, Auboros · · Updated

Updated 8 October 2026: added the short answer, an At a glance block, four question headings and a captioned table of the register’s columns; the privacy section now reflects the OAIC’s automated decision-making guidance published on 30 September 2026; the Odoo section was rebuilt on Odoo 20 (released 24 September 2026) and the MYOB Acumatica section on MYOB’s current AI feature list; the ABS figure was re-sourced to the 25 June 2026 release; “Goes well with” added. Bill’s quote is unchanged.

An AI agent register is a one-page record of every AI agent your business runs: its job, owner, systems and permissions, model and data path, approval gate, cost and review date. The National AI Centre’s guidance tells organisations to create and maintain one, and the OAIC’s 30 September 2026 guidance on the 10 December 2026 privacy policy rule is hard to follow without it.

At a glance

  • Who it is for: owners, CFOs, operations managers and IT leads of Australian businesses running, or about to run, more than one AI agent or AI feature beside Odoo or MYOB Acumatica.
  • Problem it solves: nobody can say what is running, who owns it, what it can write to or what it cost last month, and the privacy policy has to describe automated decisions from 10 December 2026.
  • Platforms: Odoo 20 and Odoo 19, MYOB Acumatica, and every agent outside them: Copilot flows, chatbot projects, scheduled scripts and anything a contractor left behind.
  • What it records: name and job, owner, trigger, systems and scope, model and data path, approval gate, cost, escalation and review date, and whether the agent feeds a decision about a person.
  • Who keeps it: one named person, with a named owner on every line.
  • Review cadence: a monthly half-hour in the example below; a new line before any new agent touches production.
  • Typical cost: the National AI Centre’s AI register template is free, in Word or Excel. If you want the agents designed and governed as well, a pilot or proof of concept starts from $5,000 ex GST per our AI agents for ERP in Australia page, as at 8 October 2026.
  • Typical timeline: about an hour for the first page, in our experience. Agent work itself runs discovery 1 to 2 weeks, sandbox pilot 2 to 6 weeks and drafts-first go-live 1 to 2 weeks, per the same page.
  • Last verified: 8 October 2026 against the National AI Centre’s Guidance for AI Adoption, the OAIC’s announcement of 30 September 2026, Odoo’s 20.0 AI agents documentation and MYOB’s AI feature page.

It sounds like admin. It is admin. It’s also the difference between running agents and being run by them. The ABS Characteristics of Australian Business release of 25 June 2026 reports that 12% of Australian businesses used AI in 2024-25, so plenty of teams are about to find that out.

We’ve covered what AI agents can do inside Australian businesses and the controls that make a single agent safe. This post is about the next problem, the one that arrives quietly: what happens when there’s more than one.

One agent is a tool, five agents are a fleet

Nobody plans agent sprawl. It happens one useful idea at a time. The sales team gets an agent that drafts orders from emailed PDFs. The buyer wants the same treatment for replenishment. Meanwhile someone in accounts has built a Copilot flow nobody else has seen, and a manager is pasting debtor lists into a chatbot because it’s faster than asking for a report.

Each might be fine on its own. Together they raise questions that get harder every month. What’s actually running? Who owns the one that touches pricing? What did they cost last month? Which ones can write to the ledger, and who approves what they write?

Auboros runs research, content and QA agents over our own operations, drafts-first with a person approving the output, and even at that scale we lost track of one for a fortnight. It kept working. That was the unsettling part. An agent that fails loudly gets fixed; one that hums along unwatched is the real risk.

“The first register we build with a client is never surprising because of the agents IT knows about. It’s the two nobody wrote down. You can’t govern what you haven’t listed.”

Bill Alvarez, Practice Manager, Auboros

What goes in an AI agent register?

The fix is a table, not a platform. Ours fits on a page.

Table: the columns of a one-page AI agent register, what to write in each and why
ColumnWhat to writeWhy it is there
Name and jobOne sentence a non-technical director would understand: “Reads emailed purchase orders and drafts sales orders for approval”If you can’t say it in a sentence, the scope isn’t settled
OwnerA named person, not a departmentThe owner answers for the agent’s output
TriggerA person clicking, a schedule, or an event such as an inbound emailUnattended agents need tighter limits than ones a person starts
Systems and scopeWhich systems, read-only or write, and whose permissions it acts underAn agent should act with a real user’s data scope, never a shared super-user
Model and data pathWhich model or vendor sits behind it and where the data is processedIf customer records leave Australia, this is where that gets written down
Approval gateWhat it may draft and who approves each draft before anything postsLedger, tax, pricing and stock write-backs need a person on the gate, every time
CostThe subscription or credits plus last month’s usageAgent costs drift, and this is where drift shows
Escalation and reviewWho can switch it off, what it does when unsure, the next review dateSomebody has to be able to stop it
Decision about a person?Yes or no, and which decisionThis column feeds the privacy policy from 10 December 2026

You don’t have to invent the format. The National AI Centre’s Guidance for AI Adoption, which condensed Australia’s earlier ten voluntary guardrails into six essential practices in October 2025, says to “create and maintain an AI register” that documents all your AI systems and how you use them. Its free AI register template covers key characteristics, use cases, accountable people and governance level. For agents that touch an ERP we add the trigger, approval gate and cost columns, and now the last one.

Not on its own. The national guidance is voluntary and Australia still has no general AI Act. It is, though, the standard a customer, insurer or board member will reach for when they ask how you govern AI, and “we follow the national guidance, here’s our register” is a short, convincing answer.

One date gives the register teeth: 10 December 2026. From then, businesses covered by the Privacy Act must describe in their privacy policies the kinds of decisions a computer program makes, or substantially helps a person make, where the decision could significantly affect an individual, and the kinds of personal information used. The Office of the Australian Information Commissioner (OAIC) published its fact sheet, flowchart and updated guidelines on 30 September 2026.

Three points from that guidance matter for a register. “Computer program” covers rule-based processes as well as AI, so an automatic credit-hold rule belongs on the list beside the agents. Advisory output counts when a person relies on it, and the fact sheet says human review doesn’t automatically take a decision out of scope. And the updated APP 1 guidelines say businesses should actively identify, assess and keep oversight over third-party programs.

The OAIC doesn’t prescribe a register. You still can’t write that disclosure without knowing what your agents do, and the register is where the answer comes from. The OAIC says most small businesses with turnover of $3 million or less aren’t covered by the Privacy Act, with exceptions, so check where you sit with your privacy adviser. We covered the wider control set in our guide to AI agent governance for Australian businesses; the register is the page that makes the rest of it auditable.

What do Odoo and MYOB Acumatica already record for you?

If your agents live inside your ERP, part of the register already exists.

Odoo

In Odoo 20, released on 24 September 2026, every AI agent is a record. Odoo’s 20.0 documentation lists the fields: the agent’s name, its provider, a response style, a system prompt, the sources it may read and the skills it has been given. Skills are where the scope column comes from. The documentation says an agent with no skills “is only able to provide information”, and the preconfigured skills include Create Records and Update Records, so the agent form tells you at a glance which agents can write.

Three Odoo 20 changes add lines to the register. The release notes say agents can be summoned by automated and scheduled actions, which is why the trigger column exists; we’ve written up what runs unattended in Odoo 20. Odoo 20 also ships a built-in MCP server, so an outside assistant holding a staff member’s key is an agent too; our note on the Odoo 20 MCP server and its permissions covers what it exposes by default. And every AI feature draws on prepaid credits, which is the cost column; see what Odoo 20 AI costs.

MYOB Acumatica

MYOB’s AI page, read on 8 October 2026, lists eight AI features for MYOB Acumatica, from AI Assistant and AI Automation to AP Bill Entry and Anomaly Detection. Each one you switch on is a register line. AI Automation, the feature that runs your own prompts on a form, was called AI Studio until MYOB renamed it, and its prompts run when a person clicks the action, as we set out in our MYOB Acumatica AI Automation hand-off note.

The same page helps with the model and data path column. MYOB says customer data is stored in Australia and that, depending on the feature, data may be processed in Australia or through global AI infrastructure from its named providers, which can process it to generate a response but cannot store it or train on it. Write that down per feature. Global Acumatica features are a separate matter: they have typically reached the ANZ product 6 to 9 months after the global release, so label those register entries shipped or roadmap, as our MYOB Acumatica AI guide does.

Everything outside the ERP

What neither platform can see is everything outside itself: the Copilot flow in accounts, the chatbot project a manager runs from a browser, the automation a contractor left behind. That gap is why Microsoft sells Agent 365, which it describes as a “control plane to observe, govern, and secure agents” and which became generally available on 1 May 2026. For a large organisation deep in Microsoft 365 it’s worth a look; for most mid-market businesses it’s more platform than the problem needs. The one-page register comes first either way, because no tool can govern agents you haven’t decided to own.

A Tuesday morning in mission control

Here’s the register alive. Picture a Queensland distributor running three agents over its ERP.

At 7:20am the operations manager opens the approval queues. The replenishment agent proposed eleven purchase orders overnight; the buyer approves nine and sends two back because a supplier has changed its minimum order quantity. The sales order agent read fourteen emailed purchase orders and drafted thirteen; the fourteenth was an unreadable scan, so it escalated to a person instead of guessing. The credit agent drafted six payment reminders; the credit controller approves five and holds one because that customer is mid-conversation about a payment plan.

Then the cost column earns its place. Usage on the sales order agent doubled last week. The register names an owner, the owner looks, and the cause is a supplier now attaching a 300-page catalogue to every order email. The fix takes ten minutes. Without the register, that cost drifts until someone spots it in the P&L, with no name attached.

Twenty minutes, one page, three people making every decision that matters. That’s mission control at mid-market scale.

How do you start an AI agent register?

Start with a page, not a platform. If you run even one agent against live business systems, start the register this week.

  • List everything that runs, including the unofficial ones and the automatic rules. An amnesty gets better answers than an audit.
  • Name an owner for each line. A person, with a phone number.
  • Write down trigger, scope, gate and last month’s cost. Leave a cell blank if you don’t know it; the blank is the finding.
  • Mark the lines that feed a decision about a person, and take those to your privacy adviser before 10 December.
  • Book a monthly half-hour review, and give new agents a sandbox before they touch production.

Our AI agents for ERP in Australia page describes how we design these patterns, drafts-first with role-scoped permissions, and the register is the first artefact we build on every engagement.

Goes well with

Running more than one agent, or about to?

Auboros designs, governs and runs AI agents over Odoo and MYOB Acumatica for Australian businesses, from our base in Brisbane and the Gold Coast. We’ll help you build the register, set the approval gates and wire the agents in safely.

If you’d like a second pair of eyes on what’s already running in your business, book a free consultation. Bring the unofficial agents too. We’ve seen worse.

FAQ

Frequently asked questions

What is an AI agent register?

An AI agent register is a single record of every AI agent a business runs: what each agent does, who owns it, what triggers it, which systems it can read or write, which model sits behind it, what it costs, and who approves its output. The National AI Centre publishes a free AI register template as part of its Guidance for AI Adoption.

Is an AI register a legal requirement in Australia?

Not on its own. The national Guidance for AI Adoption is voluntary and Australia has no general AI Act. From 10 December 2026, though, privacy policies must describe the kinds of decisions computer programs make or substantially inform and the personal information used, and a register is the practical way to know what to disclose. Ask your privacy adviser how the rules apply to your business.

Does the OAIC's automated decision-making guidance require a register?

No. The guidance published on 30 September 2026 does not prescribe a register. The updated APP 1 guidelines do say businesses should actively identify, assess and keep oversight over third-party computer programs, and the disclosure covers rule-based programs as well as AI, so a list of everything that runs is the obvious starting point.

How many AI agents do you need before a register is worth keeping?

Start it with the first agent that touches a live business system. In our experience a one-page register takes about an hour to set up, and it's far easier to keep current from day one than to reconstruct after five agents have accumulated.

What is the difference between an AI agent register and Microsoft Agent 365?

The register is a practice: a documented list of your agents, owners, permissions and approval gates. Agent 365 is a Microsoft product, generally available since 1 May 2026, that Microsoft describes as a control plane to observe, govern and secure agents. Most mid-market businesses get the bulk of the value from the one-page version.

Want help with your own implementation?

We're a Brisbane-based Odoo Silver Partner and MYOB Acumatica Partner. Book a free consultation and get a straight answer.