Microsoft ships agents for sales orders, payables and expenses. The obvious next ones are credit control, replenishment and parts of the month-end close. A wish list, why each one fits an agent, and what you can do in the meantime with standard features and a custom agent.
Three Microsoft agents ship in Business Central today: Sales Order, Payables and Expense (see agentic AI in BC). The processes they cover share a pattern: high volume, clear rules, documents arriving from outside, and exceptions a person can handle. Plenty of other processes fit that pattern. This is a wish list, with what you can do now. It's our view, not Microsoft's roadmap.
Why it fits: rules-based (days overdue, amounts, customer status), repetitive, and the human decision (do we put them on stop?) is clear.
What it would do: prioritise who to chase, draft chasers in the right tone for the customer, log promises to pay, flag disputes, suggest stops.
Meanwhile: reminders automation (reminders), statements on a schedule (statements), and a custom chaser in Copilot Studio (your first Copilot Studio agent).
Why it fits: the planning worksheet already calculates; the human work is reviewing suggestions, adjusting for what the system doesn't know, and raising POs.
What it would do: run planning, explain the suggestions in plain language, flag unusual demand, draft purchase orders and supplier emails for approval.
Meanwhile: the planning worksheet and requisition worksheet on the job queue, item availability by event (item availability).
Why it fits: a checklist of known steps, each with a clear test of done.
What it would do: work through the checklist, check reconciliations agree, list unposted documents, flag unusual balances, draft accrual journals for review, and report what's left.
Meanwhile: the year-end checklist applied monthly, scheduled reports, and an assistant working through it via MCP (using an assistant with BC).
Why it fits: collecting and checking the same information every time.
What it would do: request details, check VAT numbers and company registration, prepare the vendor card for approval, and never set bank details without a person verifying them (prompt injection).
Why it fits: "where's my order?", "can I have a copy invoice?", "what's my balance?" are answered from data the system already has.
What it would do: read the email, look up the answer, draft the reply.
Why it fits: matching and eliminating balances between companies is rules-based and dull.
Some of these may arrive from Microsoft, some from AppSource partners, and some you'll build yourself with Copilot Studio and MCP. Whichever, the preparation is the same: clean data, written processes, narrow permissions, and a human on the decisions.
