How to Receive eInvoices in MYOB and Create Supplier Bills

When a supplier sends a Peppol eInvoice to your MYOB business, the invoice doesn't arrive as a PDF attachment or a scanned image. It arrives as structured data, transmitted through the Peppol network directly into your MYOB In Tray. MYOB operates as a Peppol Access Point, which means the exchange happens system-to-system: the supplier's accounting software packages the invoice into a standard Peppol format, the network routes it, and MYOB receives and parses the data automatically.

The practical result is that over 25 fields auto-populate from a single eInvoice. That includes the supplier name and ABN, invoice number, invoice date, due date, full line item details (descriptions, quantities, unit prices, and amounts), GST codes, and totals. None of this requires manual entry. The structured data maps directly into MYOB's bill fields, which is fundamentally different from processing a PDF where software has to interpret an image or text layout.

To receive eInvoices in MYOB, your business needs to be running MYOB Business (the online product) with eInvoicing enabled and registered as a Peppol participant. If you haven't yet completed registration, it's worth reviewing Australia's Peppol e-invoicing requirements and deadlines to understand the current mandate timeline and what's involved.

Once an eInvoice lands in your In Tray, the workflow to create a bill is straightforward:

1. Open the eInvoice from the In Tray. MYOB flags it as an eInvoice so you can distinguish it from scanned or emailed documents.
2. Review the auto-matched supplier. MYOB attempts to match the incoming ABN and supplier details against your existing contacts. Verify this match is correct.
3. Verify the populated data. Check line items, quantities, pricing, GST codes, and totals against what you expected from the supplier. The data is pre-filled, but a quick review catches any discrepancies before they hit your ledger.
4. Create the bill. Convert the eInvoice directly into a supplier bill. Because the data is already structured and mapped, there's no re-keying involved.

This end-to-end process eliminates the data entry bottleneck of traditional invoice processing. The structured format means fewer transcription errors, faster processing, and a clean audit trail from the moment the eInvoice arrives.

---

How MYOB Matches Suppliers and Handles GST from eInvoice Data

When an eInvoice arrives through the Peppol network, MYOB needs to answer two questions before it can create a usable bill: which supplier sent this, and how should the tax lines be coded?

ABN-Based Supplier Matching

MYOB uses the Australian Business Number (ABN) embedded in the incoming eInvoice as its primary matching key. The system compares the sender's ABN against the ABN field stored in your existing supplier contact records. If it finds an exact match, the bill is automatically linked to that supplier, and the line items, amounts, and references populate without manual intervention.

This makes the ABN the single most important data point for reliable MYOB Peppol supplier matching. A missing or outdated ABN in either direction (the supplier's outgoing eInvoice or your MYOB contact record) will break the automatic link.

Practical step: Audit your supplier contacts and confirm that every active supplier has a current ABN recorded. For suppliers you expect to receive eInvoices from, verify their Peppol registration status through the Australian Business Register or a Peppol participant directory before assuming eInvoices will flow through automatically.

When Matching Fails

If MYOB cannot match the incoming ABN to any supplier contact, the eInvoice data still arrives in the In Tray, but it is flagged for manual supplier assignment. This typically happens when:

• You are receiving from a first-time supplier with no existing contact record in your MYOB file
• The supplier's ABN is recorded differently (or not at all) in your contacts
• The supplier has changed their ABN due to a restructure and your records reflect the old number

In these cases, you must manually link the eInvoice to an existing supplier or create a new supplier record before the bill can be finalised. Until you resolve the match, the bill cannot be processed through your normal AP workflow.

GST Code Interpretation

Beyond supplier identity, each Peppol eInvoice carries structured tax data: GST amounts, tax category codes, and taxable/non-taxable line classifications defined by the Australian Taxation Office's requirements. MYOB maps these incoming tax categories to its own internal GST tax codes when populating the bill lines.

For standard cases (all lines GST-inclusive at 10%, or all GST-free), this mapping works predictably. Where you need to pay closer attention is with MYOB supplier eInvoices that contain:

• Mixed GST items on a single invoice, where some lines are taxable and others are GST-free
• GST-free supplies that must be coded correctly to avoid overclaiming input tax credits
• Input-taxed acquisitions (such as financial supplies), which require specific GST codes to ensure accurate BAS reporting

Always verify the mapped GST codes before finalising the bill. The eInvoice data is only as accurate as what the supplier's system generated. A miscoded tax category on the supplier's end flows straight through to your bill, and if you do not catch it, it flows straight into your BAS.

---

eInvoice Reception vs OCR and In Tray Capture

MYOB offers two distinct paths for getting supplier invoices into your system, and they differ fundamentally in how data enters your books. Understanding the practical gap between structured eInvoice reception and OCR-based capture through the In Tray is critical for any AP team managing a mix of supplier capabilities.

With Peppol eInvoicing, your supplier's accounting software generates a structured data file that travels directly into MYOB through the network. Every field, from ABN to individual line items, arrives as machine-readable data. There is no document to scan, no image to interpret, and no character recognition to second-guess. The data was structured at source, so MYOB simply maps it into a draft bill.

The In Tray path starts differently: you or your supplier uploads a PDF, photograph, or scanned image. MYOB's OCR engine then attempts to read that unstructured document layout and extract the relevant fields. Even with modern OCR accuracy, this interpretation step introduces friction: a smudged total, a slightly unusual invoice template, or a handwritten PO reference can produce misreads that require manual correction. For teams looking at automating supplier invoice capture through MYOB's In Tray, OCR has improved significantly, but it remains an interpretation of a visual document rather than a direct data transfer.

Here is how the two paths compare across the dimensions that matter most to AP workflows:

Dimension	Peppol eInvoice	OCR / In Tray Capture
How the invoice enters MYOB	Structured XML data delivered automatically via the Peppol network	PDF, photo, or scan uploaded manually or forwarded by email to In Tray
Data accuracy	Machine-readable fields, no interpretation required	OCR-interpreted text, prone to misreads on amounts, dates, or ABNs
Fields populated	25+ structured fields including line items, tax categories, payment terms, and supplier identifiers	Core fields extracted (total, date, supplier name), but line-item detail and tax breakdowns often need manual entry or correction
Manual review effort	Verification only — confirm the data looks right	Correction — fix OCR errors, fill missing fields, reconcile against the original document
Speed of bill creation	Near-instant draft bill from structured data	Minutes per invoice depending on document quality and complexity

The cost difference is measurable. According to CPA Australia's analysis of e-invoicing costs in Australia, the ATO estimates that processing a paper or PDF invoice costs Australian businesses A$27 to A$30 per invoice, while e-invoicing reduces that cost to under A$10. That gap reflects the labour buried in the OCR path: opening the document, checking extracted values against the original, correcting errors, and manually keying missing fields.

Once a bill exists in MYOB, the intake path no longer matters. Whether the bill originated from an eInvoice or from a corrected OCR capture, downstream processing is identical. Approval routing, payment scheduling, and bank reconciliation all follow the same workflow. If you are refining that downstream process, the guide on setting up bill approval workflows in MYOB covers the steps regardless of how the bill was created.

---

Why MYOB Cannot Match eInvoices Against Purchase Orders

If your business uses purchase orders as part of its AP controls, you might expect that structured eInvoice data would flow directly into a three-way matching process. It does not. MYOB does not currently support linking or matching incoming eInvoices against existing purchase orders in the system.

This is not a configuration gap on your end. MYOB staff have confirmed in community forums that automated PO matching for eInvoices is a feature that is simply not yet available.

The absence matters more than it might seem at first glance. Three-way matching (purchase order, goods receipt, supplier invoice) is a foundational AP control. It catches overbilling, duplicate charges, and unauthorised purchases before payment goes out. When an eInvoice arrives with perfectly structured line items, quantities, and totals, the natural assumption is that MYOB could validate those figures against the corresponding PO automatically. It cannot.

In practice, this means the structured data advantage of eInvoicing does not extend to procurement reconciliation within MYOB. You receive a cleanly parsed invoice with accurate line-level detail, but you still need to manually cross-reference that data against your purchase orders before converting the eInvoice into a bill. The manual verification step remains in your workflow regardless of how the invoice was received.

The workaround is direct but manual. Before you convert an incoming eInvoice to a bill, open the corresponding purchase order in MYOB and compare it line by line against the eInvoice data: item descriptions, quantities, unit prices, and totals. Flag any discrepancies before the bill is created. For teams processing high volumes of PO-backed invoices, this adds a meaningful time cost that structured eInvoice data alone does not eliminate.

---

Managing a Mixed Supplier Environment in MYOB

The reality for most Australian businesses using MYOB is that not all your suppliers send eInvoices, and that situation will persist for years. Some suppliers are registered Peppol participants and deliver structured eInvoice data directly into your MYOB inbox. Others still email PDFs, post paper invoices, or send scanned images. Your AP workflow needs to handle both paths without creating bottlenecks or doubling your processing time.

Identifying which suppliers can send eInvoices

Before you can optimise your intake workflow, you need to know which suppliers are actually Peppol-capable. The Australian Business Register (ABR) and Peppol participant directories let you look up a supplier's ABN to confirm whether they are registered to send and receive eInvoices through the Peppol network. Running this check across your active supplier list gives you a clear split: suppliers you can request eInvoice delivery from, and suppliers who will remain on the PDF or paper path for now.

This lookup is worth doing periodically, not just once. As more Australian businesses register for Peppol, suppliers who were PDF-only six months ago may now be eInvoice-capable. A quarterly check of your top suppliers by volume can gradually shift more of your intake toward the structured eInvoice path.

Setting up your dual-path workflow

For Peppol-capable suppliers, the action is direct: contact them and request eInvoice delivery to your MYOB business. Once they send invoices through Peppol, those invoices arrive pre-populated with structured data (supplier details, line items, amounts, GST) and require only review and approval before becoming bills. No manual keying, no OCR interpretation.

For suppliers who cannot or will not send eInvoices, PDFs and scanned images continue to arrive by email or through MYOB's In Tray. These invoices carry the same data as an eInvoice, but it is locked inside an unstructured document. Someone has to extract it. Manually keying invoice numbers, dates, line items, quantities, unit prices, and GST amounts from dozens of PDF invoices each week is exactly the bottleneck that eInvoicing was designed to eliminate. When a supplier is not on Peppol, you need another way to bridge that gap.

Closing the PDF gap with AI-powered extraction

AI-powered extraction tools solve this problem by converting unstructured PDF invoices into the same structured data that eInvoices provide natively. Rather than manually entering each field from a supplier's PDF, you can extract supplier invoice data automatically and produce a structured output containing supplier name, ABN, invoice number, date, line item descriptions, quantities, amounts, and GST codes.

With a tool like Invoice Data Extraction, the workflow mirrors the efficiency of the eInvoice path. You upload a batch of PDF supplier invoices and the AI extracts the specific fields needed for MYOB bill creation (supplier details, line items, amounts, GST codes) into a structured Excel or CSV file within minutes. That structured output is then ready for import into MYOB, turning what would have been hours of manual data entry into a few minutes of review.

The practical outcome

The goal for MYOB mixed supplier invoicing is consistency: whether a supplier invoice arrives as a Peppol eInvoice or a PDF attachment, it should end up as structured, verified data in MYOB.