MYOB Supplier Invoice Automation: A Complete Workflow Guide

MYOB automates supplier invoice capture through its In Tray feature, which accepts emailed, uploaded, or scanned invoices and uses OCR to prefill bill fields. For automated supplier feeds, MYOB partners with select vendors to deliver invoices directly into the system. However, native OCR accuracy is limited, and many users report extraction errors that require manual correction, making upstream data extraction tools valuable for high-volume processing.

The manual processing burden is still large in Australia. CPA Australia notes that a high percentage of Australia's 1.2 billion annual invoices are still prepared and posted manually, and cites ATO estimates that paper or PDF invoices cost $27 to $30 to process compared with less than $10 for an eInvoice. For bookkeepers and finance teams running accounts payable through MYOB, that manual burden lands squarely on bill entry: keying in supplier details, line items, tax codes, and amounts from PDFs or scanned documents.

MYOB offers three main pathways for getting supplier invoices into the system:

1. In Tray with OCR — Upload, email, or scan invoices into MYOB's In Tray, where built-in OCR reads the document and prefills bill fields for your review.
2. Invoice feeds — A smaller number of participating suppliers can push invoices directly into your MYOB account through integrated feed partnerships, bypassing manual upload entirely.
3. Manual entry or file import — The fallback for everything else: keying bills by hand or importing transaction data from external files.

---

How MYOB's In Tray and Built-In OCR Process Invoices

MYOB's In Tray is the accounts payable inbox inside MYOB. Supplier invoices, receipts, and bills enter this queue before they can become posted transactions, so it is important to separate what In Tray actually automates from what still needs manual review.

Getting Documents Into In Tray

There are three routes for getting supplier invoices into In Tray, and each carries different implications for downstream OCR accuracy.

Email forwarding is the most hands-off method. Every MYOB Business file has a dedicated In Tray email address. You forward supplier invoices (or have suppliers send directly) to that address, and attached documents appear in your In Tray automatically. Because these are typically born-digital PDFs, they tend to produce the cleanest OCR results, provided the PDF isn't a flattened scan or image-only file.

Direct file upload through the MYOB web interface lets you drag and drop PDFs or image files straight into In Tray. Native PDFs usually parse better than photos or scans of printed invoices, where camera angle, lighting, paper folds, and low resolution all degrade OCR before it starts.

What Happens After a Document Arrives

Documents that land in In Tray do not process automatically. They sit as unprocessed files until you select one and create a bill or spend money transaction. MYOB triggers OCR at that point, attempts to prefill fields, and leaves you to review, correct, and complete the entry before recording it.

In Tray is a staging area, not an automation engine. The OCR assist only fires when you manually initiate bill creation from a queued document.

What OCR Prefills vs. What You Still Enter Manually

MYOB's OCR typically attempts to prefill:

• Supplier name (matched against your existing contacts list)
• Invoice number
• Invoice date
• Total amount or balance due

That looks useful on paper, but the fields that consume the most data entry time are rarely prefilled reliably. Line item descriptions, quantities, unit prices, tax codes, and account allocation categories almost always require manual entry or correction. For invoices with multiple line items, you are still doing the bulk of the keying work yourself.

Account coding is a particular gap. Even when OCR reads header-level data correctly, it has no logic for mapping line items to your chart of accounts. That allocation step remains entirely manual, and for firms processing high volumes of supplier invoices, it represents the real bottleneck.

Edition Differences: MYOB Business vs. AccountRight

Not all MYOB editions handle In Tray the same way.

MYOB Business (the cloud-native product) includes In Tray with OCR as a standard feature. The email forwarding address, drag-and-drop upload, and OCR prefill workflow described above all apply to Business.

MYOB AccountRight (the desktop/hybrid product) also offers In Tray, but the experience differs. AccountRight users may need to upload documents manually and should check whether their version offers OCR prefill when creating a bill. If the prefill option is absent, In Tray functions as document storage and all data entry is manual.

---

How MYOB Invoice Feeds Work

Separate from the In Tray, MYOB offers an invoice feed feature that bypasses document capture entirely. Instead of uploading a PDF and relying on OCR to extract data, invoice feeds deliver structured invoice data straight into MYOB from the supplier's own systems.

The mechanism works through direct partnerships between MYOB and select Australian suppliers. When a participating supplier issues you an invoice, that invoice data flows electronically into your MYOB file without any manual upload, email forwarding, or scanning on your end. Large retailers and office suppliers like Officeworks are among the notable participants. If you purchase regularly from one of these partners, their invoices appear in MYOB ready for review and posting.

A feed-delivered invoice arrives with pre-populated fields pulled from the supplier's own records — ABN, invoice number, line items, amounts, and GST breakdowns. Because this is structured data transmitted directly rather than text extracted from a scanned image, you avoid the OCR misreads that plague In Tray processing. There is no ambiguity over whether a "5" is actually an "S", no missing line items, no incorrectly split totals. The invoice lands in MYOB looking substantially cleaner than what the In Tray typically produces.

The practical limitation is straightforward: invoice feeds only work with suppliers who have a formal partnership with MYOB. There is no way to request or configure a feed for an arbitrary supplier. Either they participate in the program or they do not. For the vast majority of Australian SMBs, this means invoice feeds cover a small handful of recurring supplier relationships at best. MYOB's Peppol eInvoicing support for supplier bills widens the pool considerably — any supplier connected to the Peppol network can deliver structured invoices directly, without needing a bespoke feed partnership.

For businesses evaluating how to reduce manual invoice handling across the full supplier base, the feed feature alone will not get them there.

---

The Full Supplier Invoice Workflow: Capture to Posted Bill

The supplier invoice lifecycle in MYOB shows where automation helps and where the work still stays with the bookkeeper.

Stage 1: Receive the invoice

Supplier invoices enter MYOB through email forwarding, invoice feeds, direct upload, or scanned paper (as covered in the sections above). The intake method determines extraction quality downstream: feed invoices arrive pre-structured, born-digital PDFs produce reasonable OCR results, and scanned paper is the most error-prone.

Stage 2: Capture and extract data

When you select an In Tray document and create a bill, MYOB fires its OCR engine and attempts to prefill fields. Extraction quality varies significantly by invoice format and supplier layout.

Stage 3: Review and correct

This is where the real work happens. You need to verify that MYOB matched the right supplier, confirm the invoice number and date, check that the invoice has not already been entered — see how to catch and prevent duplicate supplier invoices in MYOB — and review amounts and line items. For most finance teams, this review-and-correct step consumes the majority of processing time.

Stage 4: Code the bill

With the header information confirmed, you allocate each line item to the appropriate expense account and assign tax codes. MYOB may suggest allocations based on prior invoices from the same supplier, but you still need to confirm them, especially for new suppliers or multi-line invoices across different expense categories.

Stage 5: Approve, post, and pay

After review and coding, approve the bill according to your controls, post it, and schedule payment in MYOB. What is available varies significantly by product tier, but the automation question is mostly settled before this point: In Tray, invoice feeds, or upstream extraction determine how clean the bill data is before approval.

Where the bottleneck actually sits

For teams handling diverse supplier invoices with varied layouts at volume, stages 2 through 4 are where the workflow slows down. OCR accuracy is the single biggest variable: a clean extraction might need 30 seconds of verification, while a poor extraction that misreads key fields can take longer to fix than manual entry from scratch. Every percentage point of extraction accuracy you gain upstream translates directly into less time spent reviewing and correcting bills.

Bypassing In Tray for bulk or historical imports

Not every invoice needs to go through the In Tray pipeline. If you are migrating historical invoices from another system, onboarding a backlog, or importing a large batch of bills from a standardised data source, the alternative path is importing invoice data into MYOB using CSV files. This approach skips OCR entirely and feeds structured, validated data directly into MYOB as bills, which is faster and more accurate when you already have clean source data to work with.

---

Troubleshooting Common In Tray and OCR Errors

In Tray failures are routine friction points for businesses processing invoices from many suppliers with inconsistent document formats. These are the common errors to check first.

"Failed to get OCR data"

This is the single most reported In Tray error. MYOB's OCR engine fails to extract any usable data from the uploaded document, and the user gets no actionable detail about why.

Common causes:

• Low-resolution scans. Documents scanned below 300 DPI often lack the clarity OCR needs to identify text regions. Mobile phone photos taken at odd angles or in poor lighting fail even more frequently.
• Image-based PDFs without embedded text. A PDF that is essentially a photo of an invoice (no selectable text layer) forces MYOB to rely entirely on image recognition, which fails on complex or non-standard layouts.
• Non-standard invoice formats. Handwritten invoices, invoices with heavy background graphics, or layouts that deviate significantly from typical invoice structures can confuse the OCR engine entirely.
• File size limits. Documents exceeding MYOB's upload size threshold will either fail silently or throw this error.

Resolution: Re-scan the document at 300 DPI or higher. If the source is a photo, crop it tightly to the invoice content and ensure even lighting. Where possible, request digitally generated PDFs from suppliers rather than scanned copies. Verify the file is within MYOB's size limits before re-uploading.

Wrong Invoice Data Displayed

Some users report selecting one invoice in the In Tray but seeing data from a completely different document when they proceed to create a bill. This is disorienting and can lead to posting errors if not caught.

Common causes:

• Browser caching. The browser serves stale data from a previously viewed document rather than fetching the current selection.
• In Tray sync lag. MYOB's In Tray may not have fully synchronized after recent uploads or deletions, causing a mismatch between the document list and the data served.

Resolution: Clear your browser cache and hard-refresh the page. If the issue persists, close the In Tray, wait a moment, and reopen it. As a last resort, remove the affected document from In Tray and re-upload it. Switching to an incognito or private browsing window can also confirm whether caching is the root cause.

Invoices Not Appearing in In Tray

You've emailed an invoice to your In Tray address, but nothing shows up. This is particularly frustrating because there's often no error message — the document simply never arrives.

Common causes:

• Incorrect In Tray email address. Each MYOB company file has a unique In Tray email. A single character off and the document goes nowhere.
• Unsupported file types. MYOB's In Tray only accepts PDF and image files (JPEG, PNG). Word documents, Excel spreadsheets, or other formats attached to the email are silently rejected.
• Email attachment size limits. Oversized attachments may be stripped by either your email provider or MYOB's ingestion process.
• Email provider delivery issues. Some corporate email systems or spam filters may block automated forwarding to external addresses.

Resolution: Double-check the exact In Tray email address in your MYOB settings. Confirm the attachment is a PDF or image file and within size limits. Check your sent folder and email delivery logs to verify the message actually left your outbox. If using automated forwarding rules, test with a manual send first to isolate the issue.

Supplier Matching Failures

Even when OCR successfully reads the invoice, MYOB frequently fails to match the supplier name on the document to an existing contact in your file. You're then forced to manually select or create the supplier before proceeding.

Common causes:

• Name discrepancies. The trading name on the invoice ("Bob's Electrical Services Pty Ltd") doesn't match the contact record you created ("Bobs Electrical"). OCR is doing a literal text match, not a fuzzy one.
• New suppliers. First-time invoices from a supplier with no existing contact record will always require manual intervention.
• Duplicate contact entries. If you have multiple records for the same supplier (perhaps with slight name variations), MYOB may match to the wrong one or fail to match at all.

Resolution: Standardize your supplier contact names to match exactly how they appear on invoices. Periodically audit your contact list for duplicates and merge them. For high-volume suppliers, verify the contact name matches the invoice header after the first successful match.

The Underlying Pattern

Most of these errors trace back to the same root issue: the quality and format of the source document. MYOB's In Tray and OCR work best when they receive clean, high-resolution, digitally generated PDFs with standard layouts. The further a document strays from that ideal, the more likely you are to hit one of these errors.

For teams processing invoices from many different suppliers, this creates a reliability problem. You can't control how your suppliers generate their invoices. If you're spending significant time re-scanning, re-uploading, and manually correcting OCR output, it may be worth evaluating free invoice scanning tools that pair with accounting software that handle extraction before documents reach MYOB, reducing how often you encounter these issues in the first place.

---

Getting Cleaner Invoice Data Into MYOB with Upstream Extraction

Every OCR limitation covered in the previous sections traces back to the same root cause: MYOB is attempting to read unstructured documents. Invoice layouts vary wildly between suppliers, scans arrive at different quality levels, and multi-page documents confuse page-boundary detection. The native In Tray was never designed as a dedicated extraction engine. It is a convenience feature bolted onto an accounting platform.

Upstream extraction flips this workflow. Instead of feeding raw invoice PDFs and images into MYOB and hoping the built-in OCR interprets them correctly, you process documents through a purpose-built extraction tool first. The output is a structured CSV or Excel file with clean, verified data that maps directly to MYOB's import fields. MYOB receives exactly the data it needs, in the format it expects, without attempting to parse a single document.

This matters because a tool whose sole purpose is reading invoices handles the edge cases that trip up MYOB's OCR: inconsistent supplier layouts, handwritten annotations, low-resolution mobile photos, concatenated multi-page PDFs, and line-item extraction across varied table formats. A dedicated extraction step is easier to quality-control because it turns mixed invoice files into one structured dataset before anything is posted to MYOB.

The third-party landscape

There are two practical upstream paths: a direct MYOB integration that creates bills automatically, or a spreadsheet-first extraction workflow that lets you verify the data before import.

A practical upstream workflow with Invoice Data Extraction

For bookkeepers and finance teams processing diverse supplier invoices at volume, Invoice Data Extraction fits the upstream step cleanly. Upload a batch of PDFs or image files, then write a natural language prompt for the MYOB fields you need: supplier name, invoice number, invoice date, due date, net amount, GST, total, tax code, and one row per invoice. The output arrives as an Excel or CSV file you can review before import.

The batch processing capability is where time savings compound. Processing 200 supplier invoices through MYOB's In Tray means correcting each one individually in the browser. Processing the same batch upstream produces one spreadsheet where errors can be caught before anything touches MYOB.

For MYOB users who need to extract invoice data into structured spreadsheets for MYOB import before it enters their accounting system, this upstream step eliminates the In Tray bottleneck entirely. MYOB still handles posting, allocation, and payment. The extraction tool simply ensures that the data feeding those workflows is accurate from the start.