Operations

Business Central AI agents in Australia: what finance and operations teams should test now

A practical guide for Australian Business Central buyers and current customers on where Microsoft AI agents fit now, what is live versus preview, and how to test value without creating cost or control drift.

Microsoft has also pushed the topic forward quickly. As of 3 June 2026, the current Microsoft Learn material shows an active Business Central agent stack that now spans Payables Agent, Sales Order Agent, Expense Agent in production-ready preview, and custom agent design capability that reached general availability in May 2026. At the same time, Microsoft's billing and setup documentation makes clear that these agent scenarios should not be treated as a casual “Copilot is included” add-on.

For Australian finance and operations leaders, the useful question is not whether AI belongs somewhere in the roadmap. It is which agent scenario fits a real process bottleneck, what supervision and data quality it needs, and how to test it without creating new cost, mailbox, or control problems.

What Microsoft's current Business Central agent stack looks like

• Microsoft's 2026 release wave 1 overview says a key focus is the expansion of AI-powered agents in Business Central, with explicit emphasis on payables and expenses as well as broader AI-driven ERP capabilities.
• Payables Agent is Microsoft's AP-focused agent. The current overview says it monitors a designated inbox for vendor invoices, extracts invoice data, matches vendors, suggests classifications, and creates draft purchase documents for review.
• Sales Order Agent is Microsoft's customer-order agent. Microsoft's setup documentation says it automates processing of sales quotes and orders from customer email requests and is validated for English (Australia).
• Expense Agent is now in production-ready preview. Microsoft says it handles receipt intake, extraction, categorisation, itemisation, expense creation, and report preparation, and it can accept receipts through a web app or shared mailbox.
• Microsoft also lists “Envision and design AI agents in Business Central” as generally available from May 2026, which means the conversation can now move beyond built-in agents toward supervised custom-agent pilots inside Business Central.

Why this matters now for Australian teams

• The local value is not only language support. It is that Business Central now offers several concrete agent patterns that map to repetitive Australian SMB workflows: AP inbox handling, quote-to-order email handling, and employee expense capture.
• Microsoft's own documentation now gives Australian and regional teams enough product detail to ask sharper buying questions about mailbox design, pilot economics, user review checkpoints, and role ownership.
• Inference from Microsoft's current materials: Business Central is moving from “AI assistant inside ERP” toward “small set of supervised autonomous workflows inside ERP”. That creates opportunity, but only for businesses with enough process discipline to supervise those workflows properly.

What is live, what is preview, and what should be treated carefully

• Payables Agent and Sales Order Agent are current operational product topics, not just roadmap items. Microsoft publishes setup, FAQ, supervision, and billing guidance for both.
• Expense Agent is different. Microsoft calls it a production-ready preview and says the documentation is prerelease and subject to change. That is current enough to test, but not current enough to assume stable long-term rollout behaviour everywhere.
• Custom agent design is listed by Microsoft as generally available in May 2026, but the surrounding feature language still reflects a prototype and supervised-pilot mindset rather than broad no-code production automation.
• The practical buyer rule is simple: treat built-in agents as shortlist or pilot candidates now, but still require a live scenario test with your own data, exceptions, and review model before any wider deployment decision.

Billing and setup are where many teams misread the opportunity

• Microsoft's Copilot and agents guidance says everyone with a Business Central licence gets Copilot at no extra cost, but selected agent capabilities use separate consumption-based billing through Copilot Credits.
• Microsoft's current billing page lists Payables Agent, Sales Order Agent, and designing and coding agents as billable agent capabilities in Business Central.
• Microsoft's billing examples show why this matters. A sample month of 100 Payables Agent invoices with three lines each totals 6,500 Copilot Credits, while a sample month of 100 Sales Order Agent requests totals 1,650 Copilot Credits.
• Expense Agent pricing is also explicit. Microsoft says one receipt handling costs 50 Copilot Credits regardless of complexity.
• Setup also matters commercially. Microsoft documents prepaid Copilot Credit packs and pay-as-you-go billing paths, and it notes that linked Power Platform environments and tenant-level capacity management affect how usage is funded and observed.

What Australian finance teams should test first

• Payables Agent fits best where invoice intake is repetitive, supplier master data is reasonably clean, and finance leaders can define exactly who reviews drafts, exceptions, duplicates, and posting readiness.
• Expense Agent should be tested only after checking policy rules, approver behaviour, and mobile or mailbox submission habits. A clever receipt demo is less important than whether approvals, audit trail, and reimbursement timing still work cleanly.
• Finance teams should also measure agent value against close impact. Faster document intake is useful only if coding quality, exception handling, and reconciliations stay reliable in the first three reporting cycles after rollout.

What Australian operations and customer-service teams should test first

• Sales Order Agent is a stronger fit where quote and order requests still arrive by email, catalogue data is disciplined, and customer-service teams can define when human review must stay mandatory.
• Microsoft's setup guidance makes mailbox and language design a real implementation decision. Teams should test with English (Australia), real customer wording, real attachments, stock exceptions, and partial-availability scenarios.
• The agent should be judged on throughput and exception management, not just drafting speed. If special pricing, freight promises, substitutions, or customer contact ownership remain messy, the agent will expose that weakness quickly.

A sensible first pilot sequence

• Step 1: pick one process only. Usually that means AP intake, email-driven order capture, or expense receipts, not all three at once.
• Step 2: define one owner group, one mailbox pattern, one review path, and one cost-review checkpoint before enabling the agent.
• Step 3: pilot with messy real cases, not only clean demos. Use poor attachments, exceptions, odd customer phrasing, and incomplete references so the team sees real failure points early.
• Step 4: measure four outputs only: throughput improvement, exception rate, review effort, and Copilot Credit consumption per successful work item.
• Step 5: decide whether to expand, redesign, or stop. A pilot that saves time but creates unclear ownership or opaque spend is not actually ready to scale.

Where Australian buyers should stay cautious

• Do not collapse Copilot, agents, and custom-agent design into one AI budget line. Microsoft's own documentation separates these categories, and buyers should do the same.
• Do not assume local relevance only because a feature is current. Language support, preview maturity, mailbox design, and process ownership still determine whether an Australian rollout is sensible.
• Do not let partners skip live scenario proof. If an agent is meant to handle your invoices, orders, or receipts, it should be tested against your real document formats, data quality, and review model before approval.

FAQ

• Are Business Central AI agents relevant in Australia now? Yes. As of 3 June 2026, Microsoft publishes current setup, billing, and supervision guidance for Payables Agent and Sales Order Agent, and it has recently added Expense Agent and custom-agent design capability to the stack.
• Which Business Central AI agent should Australian teams test first? Usually the one with the most repetitive and best-governed process. For many teams that is AP intake first, then order capture, then broader custom-agent experiments.
• Are all Business Central AI agents included in the normal licence? No. Microsoft says core Copilot is included, but selected agent capabilities use Copilot Credits and separate consumption-based billing.
• Is Expense Agent fully mature? Not yet. Microsoft currently describes it as a production-ready preview and notes that the documentation is prerelease and subject to change.
• Is Sales Order Agent suitable for Australian users? Microsoft's setup page explicitly lists English (Australia) among the validated and supported languages.

Sources used

• Microsoft Learn 2026 release wave 1 overview for Business Central agent investment areas and current product direction.
• Microsoft Learn Payables Agent overview and FAQ for current AP-agent workflow and PDF-invoice limitation.
• Microsoft Learn Sales Order Agent setup page for English (Australia) support and mailbox prerequisites.
• Microsoft Learn Expense Agent overview and setup pages for preview status, supported usage model, and 50-Copilot-Credit pricing per receipt.
• Microsoft Learn manage consumption-based billing page for billable agent capabilities and Copilot Credit examples.
• Microsoft Learn custom agent design release-plan page for May 2026 general availability timing.