End Manual Invoice Data Entry with Business Central Payables Agent
Finance • AI in ERP
Accounts payable is the last department in most New Zealand businesses still running on manual keystrokes. The Payables Agent in Microsoft Dynamics 365 Business Central changes what an AP person actually does all day - and it automates the processing, while keeping people involved in reviewing and finalising invoice drafts.
erp365 · Auckland, New Zealand · Microsoft Dynamics 365 Business Central
Ask a finance manager where their team's week goes and the answer is rarely “analysis”. It goes on invoices. A PDF lands in a mailbox. Someone opens it, reads the vendor name, finds the vendor in Business Central, keys the invoice number, the date, the due date, the amounts and the currency. Then they work out which general ledger account it belongs to, apply the right dimensions, check whether a purchase order exists, and finally push it into an approval workflow where it waits for someone who is in a meeting.
Multiply that by a few hundred invoices a month and you have a full-time role built almost entirely out of transcription. It is also where the expensive mistakes live: a mistyped vendor code, a missed early-payment discount, a duplicate invoice that gets paid twice because nobody spotted it in the queue.
Microsoft's answer is the Payables Agent, and the important thing to understand up front is what kind of thing it is. It is not a chatbot you ask questions. It is an agent that sits inside the accounts payable workflow, watches a mailbox, and does work without being prompted each time.
What the Payables Agent actually does
The end-to-end flow is deliberately narrow, and it is worth walking through it in order because each step maps onto a task someone on your team is doing manually right now.
A vendor emails an invoice to a monitored mailbox, or an employee forwards one in. The agent picks up the unread email and creates an entry in Inbound E-Documents for every PDF attachment it finds. It then extracts the invoice information from the PDF using Azure Document Intelligence, and attempts to identify the matching vendor in Business Central from what it read.
Where it is confident, it moves on. Where it is not, it stops and asks. The agent supervisor - a real person in your finance team - can help identify the right vendor, or instruct the agent to create a new vendor card prefilled from the extracted details. A vendor created this way arrives blocked for processing until someone unblocks it, which is exactly the control you want.
The agent then uses AI to suggest the invoice details, and the supervisor reviews, confirms or changes them in a purchase document draft before the agent finalises it into a purchase invoice that appears in the normal Purchase Invoices list.
The agent stops at draft. Nothing is posted, approved or paid without a person in the loop - and that is a design decision, not a gap.
What it can and cannot do
Being honest about the boundaries is what separates a successful rollout from a disappointing one. The table below reflects how the feature is documented and behaves today.
Capability | Status |
|---|---|
Read PDF invoices from a monitored mailbox | Yes - PDF attachments only |
Extract header and line detail via document intelligence | Yes |
Identify the vendor in Business Central | Yes, with supervisor assistance when uncertain |
Create a new vendor card from extracted details | Yes - created blocked until unblocked |
Suggest invoice details and produce a draft | Yes |
Post or pay without human review | No - by design |
Process emails with no PDF attachment | No - raised as a task needing manual attention |
Process an email carrying more than ten attachments | No - the email is skipped entirely |
Two practical setup points that catch people out
First, use a shared, internal-only mailbox rather than exposing the monitored address to vendors. Your employees become the first pair of eyes on every document, which matters for invoice fraud, and it keeps noise out of the agent's queue.
Second, keep attachments per email to ten or fewer. An email carrying more than ten is skipped in full, not partially processed - so a well-meaning supplier bundling a month of invoices into one message will silently produce nothing.
Note also that the Copilot capability is validated and supported in English. It can be used in other languages but may not behave as intended.
What happens to the AP team?
This is the question finance leaders actually ask, usually in a slightly lowered voice, and it deserves a straight answer. The Payables Agent does not remove the need for accounts payable people. It removes the part of their job that consists of retyping things a computer can already read.
What is left is the work that was always more valuable and never had time allocated to it. Exception handling, where the agent was not confident and a human judgement is genuinely required. Vendor relationship management - chasing missing invoices, resolving disputes, negotiating terms. Cash flow decisions about payment timing and early-payment discounts. And process improvement: refining how coding is suggested, tightening approval routing, looking at spend patterns that nobody previously had the hours to look at.
For a small New Zealand finance team, that is not a headcount story. It is a capacity story. The same three people can carry considerably more transaction volume without the business needing a fourth, which is precisely the constraint most growing firms hit first.
Is your environment ready?
Before you switch anything on, work through these questions with your partner:
- Are you on a Business Central version that carries the agent, and is your environment cloud rather than on-premises?
- Do you have a shared mailbox you are willing to dedicate, and a clear internal rule about who forwards invoices into it?
- Do you have enough posting history for the coding suggestions to be drawn from your own patterns rather than generic assumptions?
- Who is the agent supervisor? This is a named role, not a committee - someone has to own the review queue.
- Are your approval workflows in a state you would be happy to automate around, or do they need tidying first?
That last point is the one most often skipped. An agent applied to a messy approval process produces automated mess, faster. Get the process right, then let the agent run it.
Where to start
The sensible first move is a sandbox. Turn the agent on against a copy of your own data, point it at a test mailbox, and run a fortnight of real invoices through it alongside your existing process.
You will learn more about your own AP data quality in two weeks than in two years of reporting on it - which vendors have inconsistent naming, which invoices never carry a purchase order, where the coding rules live only in one person's head.
Then decide. Most teams find the agent earns its place on the routine majority of invoices and leaves the awkward ones exactly where they always were: with a person who knows the business.
Talk to us about the Payables Agent
erp365 works with New Zealand manufacturers, distributors and food businesses to get real value out of Microsoft Dynamics 365 Business Central. If you want to know whether the Payables Agent fits your AP process, start a conversation.
