MYOB Acumatica Document Processing: How a Supplier PDF Becomes an AP Bill, and What a Person Still Checks

MYOB Acumatica document processing, listed as AP Bill Entry on MYOB’s AI page, reads a supplier’s PDF invoice and fills in a draft bill on the Incoming Documents form (AP301100). A person checks the mapped fields, links the purchase order lines and clicks Save and Continue; the bill is always created On Hold. As at 20 October 2026 the service is metered by licence and MYOB promises no complete accuracy.

At a glance

• Who it is for: accounts payable officers, finance managers and owners of Australian wholesalers, builders and service businesses on MYOB Acumatica who still receive most supplier invoices as PDF attachments and key them by hand.
• Problem it solves: rekeying supplier invoices costs time and introduces the errors a three-way match then has to catch; recognition does the typing and leaves the checking to a person.
• Platforms: MYOB Acumatica with the AP Document Recognition Service feature enabled on Enable/Disable Features (CS100000). Not available in trial mode; the number of recognised documents is limited by the licence.
• Trigger: a PDF lands in a nominated mailbox with incoming mail processing switched on, a user drags a PDF into AP301100 or the mass-processing form AP301110, or a user clicks Create AP Document in the Outlook add-in.
• Inputs read: the PDF itself (vendor name and address, date, due date, vendor reference, amount, detail lines where the table is legible), the sender’s email address, your vendor records and their contacts, and open purchase orders and receipts for that vendor.
• Systems: MYOB Acumatica’s external recognition service, upgraded to Azure Form Recognizer 4.0 in version 2025.2.1 per MYOB’s release notes; the full-text entity index for vendor matching; the Accounts Payable and Purchase Orders modules.
• What the agent drafts: a recognised document with the Summary fields and detail lines filled in, the vendor found by name or by sender email, and purchase order and receipt numbers linked where a single match exists.
• Approval gate: two. The AP officer validates the recognised document and converts it; the bill is created On Hold regardless of your AP preferences, and your approval map decides who releases it.
• Audit trail: the original PDF is attached to the bill; the recognition record keeps the user, date, time and status; failed attempts are listed in the History dialog; outdated results are cleared with Delete Outdated Recognition Results (AP501100).
• Typical cycle time: seconds per document for recognition; a minute or two of checking per bill for a clean invoice from a known vendor, longer for a first-time vendor or an unreadable table.
• What it never does: release a bill, pay a bill, create a vendor, post to the ledger, decide a GST code, or accept an invoice that doesn’t match a purchase order.
• Typical cost: the recognition service is part of the MYOB Acumatica licence and metered by document count; MYOB publishes no price list for it, so ask your partner for the volume on your quote. Our MYOB Acumatica cost guide covers the licence model.
• Typical timeline: configuration is a day or two of partner time (feature switch, mailbox, index rebuild, a test batch), then one month of running recognition beside manual entry before the mailbox route takes over.
• Last verified: 20 October 2026 against MYOB’s AP Documents from PDFs: General Information, Implementation Checklist, Search for a Vendor by Email Address, Recognition of Purchase Orders in Bill Lines and Detail Mapping user guide topics, the 2025.2.1 and 2026.1.1 release notes, MYOB’s AI page, and the ATO’s tax invoices (updated 18 September 2026) and when you can claim a GST credit (updated 14 September 2026) pages.

Most of the “AI for accounts payable” searches we see land on pages about agents, prompts and roadmaps. The thing people actually want is simpler: the supplier invoice is a PDF in an inbox, and someone has to type it into the ERP. MYOB Acumatica has shipped a way around that typing for years, it just doesn’t get described in enough detail for a finance manager to decide whether to switch it on. This post is that description, with the Australian parts the US-written help topics leave out.

What does MYOB Acumatica document processing actually do?

MYOB Acumatica document processing is the AP Document Recognition Service: an external recognition service that reads a PDF invoice, extracts the header and the line table, looks the vendor up in your full-text index, and presents the result on the Incoming Documents form (AP301100) for a person to validate before a bill exists. MYOB’s AI page lists it as AP Bill Entry among eight AI features as at 20 October 2026, describing it as extracting supplier, invoice, amount and line-item data and checking it against supplier records and existing ERP data.

Two sentences from MYOB’s own general information topic set the expectations correctly. Recognition accuracy “depends on the quality, language, size, and complexity of the submitted file”, and because the model and tools come from a third party, MYOB says it cannot promise complete accuracy. That is the right frame for every drafts-first tool we build or recommend under our AI agents for ERP in Australia practice, and here the vendor says it for us.

What changed recently is the engine. The 2025.2.1 release notes say invoice recognition moved to Azure Form Recognizer 4.0, with clearer results on fields like the total amount and no setup needed after the upgrade. The 2026.1.1 release notes then added a Selected Mode option in the Link Line dialog, so a recognised bill can be linked to a purchase order or a purchase receipt regardless of the vendor’s Allow AP Bill Before Receipt setting. If you are on 2025.1 or earlier, the version you upgrade to decides what you get.

How does a PDF become an AP bill?

There are four doors in, and they all lead to the same form.

• The mailbox. A system email account on Email Accounts (SM204002) with Incoming Mail Processing switched on and Submit Incoming Documents ticked. Every PDF attachment in that mailbox is submitted for recognition. MYOB recommends a dedicated mailbox or folder, and so do we: accounts@ with newsletters in it will feed the service a lot of noise.
• The form. Drag a PDF into the preview pane of Incoming Documents (AP301100) and click Recognize. Files over 50 pages get a warning that recognition may fail; MYOB suggests staying under 10 MB.
• The mass-processing form. Incoming Documents (AP301110) takes a batch of files at once, then Recognize or Recognize All runs them.
• The Outlook add-in. Create AP Document from an email with a PDF attached; View Document opens the recognised result. In 2026 R1 the add-in’s Modern UI can also create a wider range of records from an email.

A document moves through Pending Recognition, In Progress and Recognized, or Error, which keeps a History dialog of failed attempts for your partner or MYOB support to read. Recognized is where the person comes in.

Vendor matching has its own logic worth knowing. The service tries to find the vendor from the name and address on the invoice against your full-text entity index, which is why the implementation checklist tells you to rebuild that index (SM209500) on a fresh or demo site. If that fails, the email search kicks in: the sender’s address is compared with each vendor’s Account Email and contact emails, then the sender’s domain is compared with vendor and primary-contact domains. Domains on the Excluded Email Domains form (SM209600) are skipped, which is what stops a tradie’s Gmail address matching every other tradie on Gmail. Multiple matches or no match means the AP officer picks the vendor by hand.

Purchase order linking follows the vendor’s billing setting. Per the purchase order recognition topic, a line is linked automatically when the PO number was recognised and the order exists (with a single receipt, if the vendor bills on receipts), or when exactly one order or order-and-receipt pair fits the line. Anything ambiguous waits for Link PO Line. Vendors who bill on receipts can only link stock and non-stock items that require a receipt, so a freight line on a goods invoice stays unlinked until someone deals with it on the bill.

Then Save and Continue. The Bills and Adjustments form (AP301000) opens with the new bill, the PDF attached, and the status On Hold. MYOB’s documentation is explicit that this happens regardless of the Hold Documents on Entry setting on Accounts Payable Preferences (AP101000). Recognition never produces a releasable bill. Your approval map, the same mechanism our MYOB Acumatica accounts payable guide describes, takes it from there.

What does a person still check on an Australian tax invoice?

The help topics are written for a US locale, and that matters more here than it sounds. MYOB’s general information topic says files in the en-us locale give the best results and that dates “are more likely to be recognized in the MM/DD/YYYY format”. Australian suppliers print DD/MM/YYYY. An invoice dated 03/09/2026 can come back as 9 March instead of 3 September, which moves the bill into the wrong period and shifts the due date by months. For the first twelve days of every month the two formats are both plausible, so the date and due date are the first two fields the AP officer checks on every recognised document, every time. The validation tools help: focus a field and the mapped value is framed in red on the preview; click a value in the preview to remap it; hold Ctrl to combine several values into one field.

The second check is whether the document is a tax invoice at all. The ATO’s tax invoices page (updated 18 September 2026) lists what one must show: that it is intended to be a tax invoice, the seller’s identity and Australian business number (ABN), the issue date, a description of what was sold with quantity and price, the GST amount or a “Total price includes GST” statement where GST is exactly one eleventh, and the extent to which each sale is taxable; sales of $1,000 or more also need the buyer’s identity or ABN. The ATO’s GST credit page (updated 14 September 2026) says you must have a tax invoice to claim a GST credit for purchases over A$82.50 including GST. The recognition service reads a total. It does not read “this is a valid tax invoice”, and it does not decide the GST code on each line; the vendor’s defaults and the AP officer do.

The third check is the detail table. Recognition “may not recognize invoice details at all, or it may recognize them partially or incorrectly”, per the detail mapping topic: empty columns, merged cells, tables split across pages. The built-in table mapping mode (Add Row, tick the rows in the preview, click a column to map it, Exit Table Mapping) is faster than typing, and Clear Table starts again when the result is a mess. A supplier whose invoice layout defeats the service every week is a supplier to ask for a cleaner PDF, or for a Peppol e-invoice; our MYOB Acumatica eInvoicing guide explains why a structured e-invoice needs no recognition at all and is itself a valid tax invoice.

The fourth is duplicates. The Vendor Ref field carries the supplier’s invoice number, and the Raise an Error on Duplicate Vendor Reference Number setting on Accounts Payable Preferences (AP101000) does the work once the bill is created. The person’s job is to make sure the reference was read correctly in the first place, because a misread “INV-10234” as “INV-10284” sails past that check.

What does a Tuesday morning look like, approval gate included?

Here is the pattern on a Brisbane building products distributor, with details changed. Around sixty supplier invoices a day arrive at a dedicated bills mailbox. By 8am the overnight batch sits on Incoming Documents as Recognized, with a handful in Error that re-run cleanly once the officer clicks Recognize again.

The officer works the list. Forty-one are repeat vendors with purchase orders: vendor matched, PO lines linked, totals agree, date reads correctly because those suppliers print the month in words. Thirty seconds each, Save and Continue, On Hold. Nine are stock invoices where the PO number was not printed, so the Link PO Line dialog shows two open orders for the same vendor and the officer picks the one with the matching quantities. Four are from a new steel supplier whose invoice puts the ABN in the footer and the date as 06/10/2026; the service read October 6 as June 10, so the officer corrects the date, confirms the ABN and “Tax invoice” wording are on the page, and remaps a line table that came through as one merged cell. Three are statements, not invoices, and get deleted from the queue. Two are a freight company’s invoices where the goods vendor bills on receipts, so the freight lines stay unlinked and are coded to the freight expense account on the bill.

Everything the officer converts is On Hold. The approval map routes bills over $5,000 to the finance manager, who opens each one with the PDF beside it, checks the GST line and the PO variance, and releases it. Nothing was paid, posted or released by the recognition service. It typed, matched where it was sure, and waited.

“Document recognition is a typist that never gets bored, not an accountant. The day you stop checking the date field is the day a September invoice lands in your March BAS.”

Bill Alvarez, Practice Manager, Auboros

Where does an AI agent fit beyond recognition?

Recognition stops at the draft bill. The questions that still need a person, or a drafts-first agent with a person behind it, are the ones that need two documents read together: does this invoice price match the PO price, is this the second invoice for the same delivery, did this vendor’s terms change, and should this bill wait because the goods were short-shipped. That is the AI accounts payable agent pattern, and in MYOB Acumatica the recognised bill is its input, not its competitor. Switch recognition on first, run it for a month, and only then decide whether the exceptions are frequent enough to justify an agent reading them.

MYOB’s own AI Automation prompts sit in the same place. A prompt a person runs from the bill can draft a description or summarise an attachment, as our MYOB Acumatica AI Automation hand-off post describes, and MYOB’s AI page lists “document processing” among the workflows AI Automation can be built for. Build those under the same rules: the prompt reads, a person saves.

Two housekeeping points belong here because they are easy to miss. First, recognition records accumulate: every submitted PDF leaves a record with the user, date, time, status and the file, and MYOB recommends clearing processed results regularly with Delete Outdated Recognition Results (AP501100), which keeps the PDF on the bill and removes only the recognition data. Second, the sender email addresses and contact names in those records are personal information about people at your suppliers. The OAIC’s guidance on commercially available AI products expects due diligence on where that data goes and a privacy policy that says you use it; MYOB’s AI page states that data may be processed through AWS, Anthropic or Microsoft infrastructure and is not used to train external models, which is the line to carry into your own policy.

What goes wrong, and how do you start?

The failure modes we see are predictable, and most are configuration rather than AI.

• The index was never rebuilt, so no vendor ever matches on a new site and the officer picks every one by hand. Rebuild Full-Text Entity Index (SM209500) fixes it in minutes.
• The mailbox is shared. Remittance advices, statements and marketing PDFs all get recognised, and the queue fills with documents that are not bills. Use a dedicated address and tell suppliers to use it.
• Dates swap months for the first twelve days of each month on DD/MM invoices. Make the date check a habit, and ask high-volume suppliers to print the month as a word.
• Receipt-billed vendors with service lines cannot link those lines, so the bill carries unlinked freight or install charges that the approver then queries. The 2026.1.1 Selected Mode helps when the line is on the order; otherwise code it on the bill and move on.
• Volume outruns the licence. The service is metered. Find the number on your licence before you point a sixty-a-day mailbox at it.
• Someone treats Recognized as approved. It never is. On Hold is the designed state, and the approval map is the control.

To start, enable the feature, set up the mailbox, rebuild the index, and run a week of invoices through AP301100 beside your normal entry. Count three things: how many vendors matched without help, how many dates or totals needed a correction, and how many line tables had to be mapped. Those three numbers tell you whether the mailbox route is ready, which suppliers to chase for cleaner PDFs or Peppol, and whether an agent on the exceptions is worth building. As a MYOB Acumatica partner in Brisbane we run that week with clients regularly, and the numbers usually settle the question without a debate.

Goes well with

• MYOB Acumatica accounts payable in Australia: what happens after the bill is released, from approval maps to ABA payment batches and BAS-ready coding.
• MYOB Acumatica eInvoicing in 2026: the structured alternative for suppliers whose PDFs keep failing recognition.
• The AI accounts payable agent: the drafts-first layer that reads the recognised bill against the PO, the receipt and the vendor’s history, and flags what a person should look at.

Still typing supplier invoices into MYOB Acumatica?

Auboros is a Brisbane-based MYOB Acumatica and Odoo consultancy working with distributors, builders and service businesses across Queensland and beyond. We set up document recognition properly, with the mailbox, the index, the PO linking rules and the approval map, and we tell you what it won’t do before you rely on it.

If your AP team is rekeying PDFs that a configured feature could read, book a free consultation. If your volume is twenty invoices a week and a good template would do, we’ll say that instead.