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 scanned image. It arrives as structured data through MYOB's eInvoicing service and appears in Uploads in MYOB Business, or in an online AccountRight company file opened in a browser. From there, MYOB reads the eInvoice data and lets you create a bill, download the document, or reject the eInvoice.

MYOB auto-populates as much bill information as it can from the eInvoice data, including supplier, invoice number, issue and due dates, line descriptions, quantities, unit prices, GST/tax code, subtotal, tax, total, balance due, notes, and freight where configured. 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 Uploads, the workflow to create a bill is straightforward:

1. Open the eInvoice from Uploads. 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.

---

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 most important data point for reliable supplier matching in MYOB. 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 eInvoice carries tax amounts and rates. In MYOB, the Tax/GST code is filled from the eInvoice tax rate when the corresponding code is set up. Australian 10% lines map to GST and 0% lines map to FRE; other rates or category defaults may leave the field blank or override it, so the code still needs review before finalising the bill.

Pay closer attention to 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 PDF Intake

MYOB gives you two invoice intake paths: structured eInvoices for Peppol-capable suppliers, and OCR or manual capture for PDFs, photos, and scans. Most Australian businesses need both because suppliers will move to Peppol at different speeds.

With Peppol eInvoicing, the supplier's accounting software generates a structured data file and MYOB uses that data to prepare a bill. There is no document to scan, no image to interpret, and no character recognition to second-guess.

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	Bill fields populated from eInvoice data, including supplier, dates, line items, tax, totals, and payment details where available	Core fields extracted from the document, with line-item detail and tax breakdowns often needing 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.

For Peppol-capable suppliers, ask them to send eInvoices to your MYOB business and keep their ABNs current in your supplier records. For suppliers who still send PDFs or scans, use OCR or a separate extraction step so the invoice still reaches MYOB as structured data. You can extract supplier invoice data automatically from PDF invoices into fields such as supplier name, ABN, invoice number, dates, line items, amounts, and GST codes, then review the output before import or bill creation.

Check supplier Peppol capability periodically through the Australian Business Register or a Peppol participant directory. A quarterly check of your highest-volume suppliers can move more invoices from the correction-heavy PDF path to the structured eInvoice path.

---

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.

This matters for AP controls because three-way matching catches overbilling, duplicate charges, and unauthorised purchases before payment. In MYOB, the structured eInvoice data still has to be checked manually against the relevant purchase order.

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.