The AI Accounts Payable Agent: How Supplier Bills Get Checked in Odoo and MYOB Acumatica

An AI accounts payable agent reads each supplier bill after Odoo or MYOB Acumatica has captured it, checks the ABN, the GST, the purchase order, the receipt and the bank details, and drafts an exception note for the accounts payable officer. As at 7 October 2026 both platforms capture bills with AI. Neither runs those checks, and a person still approves every bill and every payment.

At a glance

• Who it is for: finance managers, accounts payable officers and owners of Australian businesses on Odoo or MYOB Acumatica who process a few hundred supplier bills a month and review most of them by eye.
• Problem it solves: capture is no longer the slow part. Checking is. Someone still has to notice the duplicate, the freight line that crept up, the missing ABN and the bank account that changed since last month.
• Platforms: Odoo 20 and Odoo 19 (Accounting with Document Digitization on Enterprise, Purchase, Documents) and MYOB Acumatica (Accounts Payable with AP document recognition, Purchase Orders). The agent is built alongside either platform and reads through its API under its own login.
• Trigger: a schedule (7am on weekdays in the example below), plus an on-demand run before a payment batch is prepared.
• Inputs read: draft bills and their attached PDFs, the vendor record including the bank account on file, purchase orders and receipts, posted bills for the past 12 months, and the supplier’s public ABN record.
• What the agent drafts: one note per bill. Either “matches the order and the receipt, nothing to add”, or a short list of exceptions with the two values that disagree and a suggested next step.
• Approval gate: the accounts payable officer posts or rejects each bill, the ERP’s own approval workflow applies above your dollar limits, and a second person releases the payment file.
• Audit trail: every read is logged under the agent’s own credentials, each note keeps the records it compared, and the officer’s decision sits beside the note on the bill.
• Typical cycle time: notes are on the bills before the officer starts; in the example below 38 bills take about 25 minutes to clear.
• What it never does: post a bill, approve one, change a vendor’s bank details, add a bill to a payment batch, or decide a GST or withholding question.
• Typical cost: a pilot or proof of concept from $5,000 ex GST, per the AI agents for ERP in Australia hub as at 7 October 2026. Odoo’s bill capture is charged separately, at one prepaid credit per document.
• Typical timeline: discovery 1 to 2 weeks, sandbox pilot 2 to 6 weeks, drafts-first go-live 1 to 2 weeks, per the same hub page.
• Last verified: 7 October 2026 against Odoo’s 20.0 document digitisation documentation, the Odoo 20 Enterprise source, MYOB’s AI feature page, MYOB’s help on recognising AP documents, the ATO’s tax invoice rules and ASD’s Annual Cyber Threat Report 2024-25.

Most of what gets sold as AI accounts payable is capture: a PDF goes in, a bill comes out with the supplier, date and lines filled in. That part works, and you probably own it already. Both ERPs we implement have shipped it for several releases.

What capture doesn’t do is read the bill the way your most experienced accounts payable officer does. She knows this supplier never charged a fuel levy before. She remembers paying something that looked like this in September. She would ring before paying into a new bank account. That reading is the job worth giving an agent, on one condition: it writes notes and she makes the decisions.

What does an AI accounts payable agent do?

It starts where capture stops. The bill is already a draft in the ERP with its PDF attached. The agent then does four things, and stops.

• It reads. The draft bill, the PDF behind it, the vendor record, the purchase order and receipt if there are any, and the supplier’s posting history.
• It checks. The Australian tax invoice details, the ABN, the GST, whether the bill has been seen before, whether it agrees with what was ordered and received, and whether the bank details on the page match the ones on file.
• It drafts. A note on the bill in plain language, with the two values that disagree shown side by side.
• It waits. A person posts the bill or sends it back. The agent has no permission to do either.

If the note says “nothing to add” on four bills out of five, that is the agent working. The officer’s attention goes to the fifth.

What do Odoo and MYOB Acumatica already do without an agent?

More than most AI content admits. Set these up before you think about an agent.

Odoo

Odoo’s Document Digitization turns vendor bills and refunds into draft bills, automatically on upload or on demand, including PDFs emailed to a journal’s address. Each document uses one prepaid credit, and structured XML files such as eInvoices use none because there is nothing to read optically. On 7 October 2026 Odoo’s in-app purchase page listed packs from 100 documents for 15 euros to 100,000 for 5,000 euros, with 200 free credits. That is the euro pricing we were shown; check the Buy Credit screen in your own database.

In the Odoo 20 Enterprise source, digitisation is its own service with its own credit balance, separate from the credits that pay for Odoo 20’s AI agents, which we covered in what Odoo 20 AI costs. The AI accounting module in that source adds a text-drafting helper to the send-invoice window and one sample chat prompt about cash flow. It adds nothing to bill checking. The Documents app is more interesting: a folder can carry an AI sorting prompt whose tools move, tag and rename incoming files, and can include an action that creates a vendor bill from one.

The checking Odoo does ship is rule-based and good. The Odoo 20 release notes describe improved purchase order matching, with a summary of what matched and a warning when price or quantity differ from what was expected. Three-way matching and the Should Be Paid flag are covered in our Odoo accounts payable guide.

One setting deserves care. Per vendor, Odoo can auto-post digitised bills: Always, Ask after 3 validations without edits, or Never. “Always” removes the person. We leave it on Never for any supplier whose bills vary.

MYOB Acumatica

MYOB’s AI page lists AP Bill Entry among eight AI features as at 7 October 2026, alongside an AI Assistant, Anomaly Detection and AI Automation. MYOB’s help documentation describes the mechanics of recognising AP documents from PDFs: a PDF arrives by email or is dropped onto the Incoming Documents form, the recognition service fills in the summary and line details, and a person reviews them and clicks Save and Continue. The result is a bill with the status On Hold and the PDF attached. Nothing is released without a person.

From there the platform’s own controls apply. With the Approval Workflow feature on, a bill moves to Pending Approval before it can be released, and Accounts Payable Preferences has a setting named Raise an Error On Duplicate Vendor Reference Number. Bills for stock items link to purchase orders or receipts. Our MYOB Acumatica accounts payable guide walks through matching and approval maps, and how an AI Automation prompt hands work back to a person covers the click-to-run AI feature.

MYOB states that its AI features respect existing user permissions, that customer data is stored in Australia, and that processing may happen in Australia or through global AI infrastructure depending on the feature. Read that statement before supplier documents go through any AI feature, the built-in ones included.

What does the agent check that the platform rules don’t?

Rules catch exact matches. A duplicate check on the vendor reference catches INV-0931 entered twice. It doesn’t catch INV-0931 and 931. Tolerances catch a price variance on a matched line. They don’t notice a new line.

The GST rows matter at BAS (Business Activity Statement) time. The ATO says you must hold a tax invoice to claim a GST credit on purchases over $82.50 including GST. A bill that isn’t a valid tax invoice is cheaper to fix in the week it arrives than at quarter end. You can check a single ABN yourself with our ABN check tool; the Australian Business Register also offers free ABN Lookup web services, which is what an agent uses.

A worked example

Picture a Queensland packaging distributor on Odoo that processes about 400 supplier bills a month. At 7am on a Tuesday the agent reads the 38 bills captured since Monday morning. On 31 it writes that the bill agrees with the order and the receipt. Seven get a longer note.

A freight bill is 18% over the freight line on its purchase order, and the PDF shows a fuel levy this carrier hasn’t charged before. A consumables bill for $2,310 has the same supplier, amount and date as one posted in September under a differently formatted number. A sole trader’s bill for $480 quotes no ABN. One supplier has charged GST while the register shows no GST registration for its ABN. A $1,240 invoice doesn’t identify the buyer. A stock bill is for 60 cartons against 48 received. The seventh bill carries a BSB and account number that differ from the vendor record.

The accounts payable officer clears the 31 in a few minutes, rejects the duplicate, sends two bills back to suppliers for a corrected invoice, asks the buyer about the cartons and the levy, and takes the ABN question to the finance manager. On the seventh the agent’s note says only that the details differ and that nothing has been changed. She rings the supplier on the number already on file. All up, about 25 minutes. The agent has posted nothing and paid nothing.

“Reading the invoice was never the hard part. The hard part is the bill that looks fine and isn’t. I want the agent to tell my AP officer which five bills to slow down on, and I never want it anywhere near a supplier’s bank details.”

Bill Alvarez, Practice Manager, Auboros

Why should an agent never change a supplier’s bank details?

Because that is the step fraud depends on. ASD’s Annual Cyber Threat Report 2024-25 lists business email compromise fraud as 15% of the cybercrime businesses reported, the second most common type, and the average self-reported cost of a cybercrime report at $56,600 for small businesses and $97,200 for medium ones. The usual pattern is an invoice that looks right, from a supplier you know, with a new account number.

An agent is useful here because it compares every PDF with the vendor record and doesn’t get tired at 4:45pm on payment day. It is also the wrong thing to trust with the fix. A language model reading a document can be talked into things by the document. So the design is blunt. The agent’s login can’t write to vendor bank fields at all. A mismatch produces a flag and nothing else. A second person confirms the change by calling a number that was on file before the invoice arrived.

How do you run an AI accounts payable agent safely?

• Capture first, agent second. Switch on digitisation or AP document recognition, set tolerances and the duplicate check, and run that for a month. The agent reads what those tools produce.
• Read-only, own login. The agent can read bills, orders, receipts and vendor records and write a note. It can’t post, approve, pay or edit a vendor.
• Keep auto-post off where the agent runs. In Odoo, an agent’s note is no use on a bill that posted itself. If you build the agent inside Odoo 20, follow the pattern in our post on the approval gate for Odoo AI server actions.
• Leave tax calls with people. The agent flags a missing ABN or a doubtful GST amount. Your accountant decides what happens next.
• Mind whose data it is. Sole traders’ invoices carry names, addresses and bank details, which is personal information under the Australian Privacy Principles. Know which model reads them and where it runs, and record it in your AI agent register.
• Measure it. For the first quarter, count the flags that were right, the flags that were noise and the problems the officer found that the agent missed. Language models make mistakes; that count shows you how often yours does.

This is the same drafts-first pattern behind all our AI agents for ERP in Australia. It is slower than the “touchless AP” in the brochures, and nobody has to explain an automatic payment to the wrong account.

Goes well with

• AI reconciliation agents inside ERP: what happens after the payment leaves, when the bank line has to find its bill.
• AI agent governance for Australian businesses: the four controls that keep a read-only agent read-only.
• What an AI agent costs to run in Australia: the seats, tokens and review time behind the pilot figure above.

Wondering what an agent would flag in your own supplier bills?

We’re a Brisbane-based ERP consultancy that implements Odoo and MYOB Acumatica across Queensland and beyond, and we build drafts-first AI agents over both. If you’d like to see what an accounts payable agent would have flagged in last month’s bills, book a free consultation. We’ll tell you plainly whether the capture tools you already own would do the job first.