How to Prevent Duplicate Supplier Invoices in MYOB

Duplicate supplier invoices in MYOB are a costly AP error, and one of the hardest to unwind once a payment has been released. A duplicated bill that slips through to payment means chasing vendor refunds, reconciling bank feeds against reversed transactions, and explaining the variance in your next BAS or audit review.

The financial exposure is real. According to the Office of the Washington State Auditor, duplicate payments account for 0.8 to 2 percent of total payments, a range that can translate to thousands of dollars paid to vendors in error each year. For businesses processing hundreds of supplier invoices monthly through MYOB, even the low end of that range adds up fast.

MYOB AccountRight does include a native duplicate supplier invoice number warning, found at Setup > Preferences > Purchases. When enabled, it flags an alert if you enter a supplier invoice number that already exists for the same supplier. But this control has significant blind spots. It does not apply to bills created via In Tray, which is how many teams now process their supplier invoices. It is entirely advisory, meaning any user can dismiss the warning and save the duplicate bill anyway. And if you are running MYOB Business rather than AccountRight, the preference does not exist at all.

The rest of this guide covers how to prevent duplicate supplier invoices in MYOB: what the native controls actually do, where they break down based on real-world user reports, how the Import/Export Assistant handles duplicates separately, and how normalising supplier invoice numbers before they reach MYOB closes the gaps that native controls leave open.

How MYOB AccountRight's Duplicate Supplier Invoice Warning Works

MYOB AccountRight (the desktop application that syncs to the cloud, as distinct from MYOB Business which runs entirely in a web browser) includes two separate duplicate warning preferences, both found under Setup > Preferences > Purchases. They look similar but check entirely different fields, and confusing the two is one of the most common configuration mistakes in AP workflows.

"Warn for duplicate supplier invoice numbers" checks the supplier invoice number field each time you record a bill. If another bill already exists for the same supplier with the same invoice number, MYOB displays a warning dialog asking whether you want to continue. This is the setting most AP teams actually need turned on.

"Warn for duplicate Purchase Order numbers" checks the PO number field instead. It has nothing to do with invoice numbers. Enabling this setting alone will not warn you about duplicate supplier invoices.

These are independent toggles. Enabling one does not enable the other. If your team only switched on the purchase order number check, you have no duplicate bill warning active for invoice numbers, and duplicate supplier invoices will record without any prompt.

What the Warning Actually Does

The duplicate supplier invoice number warning is advisory, not blocking. When it fires, the user sees a dialog asking if they want to proceed. They can click through and record the duplicate bill anyway. MYOB does not prevent the entry, lock the record, or flag it for review. The entire control depends on the person at the keyboard reading the prompt and making the right call.

Scope: Same Supplier Only

The check is scoped to the individual supplier. Two different suppliers can share the same invoice number — "INV-001" from Supplier A and "INV-001" from Supplier B — without triggering the warning. This is by design, since supplier invoice numbering schemes frequently overlap across vendors. The duplicate warning only fires when the same supplier and the same invoice number appear on more than one bill.

Where MYOB's Duplicate Invoice Controls Break Down

Even with the duplicate supplier invoice number warning enabled, three distinct failure modes allow duplicate bills to slip through MYOB undetected.

The In Tray Bypass

This is the most operationally dangerous gap. Bills created via In Tray do not trigger the duplicate supplier invoice number warning, even in AccountRight with the preference enabled. MYOB's In Tray is the platform's document intake and OCR feature, and it is increasingly the primary path for processing supplier invoices. The problem: teams that migrated from manual "Enter Purchases" entry to In Tray-based workflows may not realise they silently lost their duplicate check in the process.

The risk compounds at volume. A supplier resends an invoice, the In Tray picks it up, a team member reviews and posts it, and no warning fires. The duplicate lands in accounts payable as a legitimate bill. Teams automating supplier invoice capture through MYOB's In Tray need to treat this gap as a known control weakness and layer additional checks around In Tray-processed bills.

MYOB Business Has No Duplicate Warning at All

MYOB Business, the cloud product, does not have a duplicate supplier invoice number warning. The feature does not exist in any form. It was formally requested through the MYOB Ideas Exchange, but the request was closed due to insufficient votes.

The practical effect: if your organisation runs MYOB Business, you have zero native duplicate detection for supplier invoices, whether entered manually or processed through In Tray. Every invoice number check is on your AP team to perform manually, every time.

Warning Failures in AccountRight

Even where the duplicate warning should work, it does not always fire. Multiple MYOB community reports describe AccountRight silently accepting duplicate supplier invoice numbers despite the preference being enabled. The commonly suggested fix is to clear the AccountRight company file cache and toggle the warning preference off, then back on. MYOB has not published an official root cause for these failures.

This creates a trust problem. AP staff cannot rely on the warning as a hard control if it intermittently fails without explanation or notification. If a duplicate has already been paid, raise a debit note or supplier credit in MYOB against the duplicate bill and contact the vendor to arrange a refund before reconciling the reversed amount against your bank feed.

---

Duplicate Handling in MYOB's Import/Export Assistant

If you use MYOB's Import/Export Assistant to bring supplier bills in from spreadsheets or external systems, you have access to a separate duplicate-handling mechanism that works independently from the preferences-based warning covered earlier.

During each import, the Assistant presents a dropdown with three options for handling records that match existing entries:

• Reject duplicate records — the import skips any incoming record that matches an existing bill, leaving your data unchanged.
• Add duplicate records as new entries — every imported record is created regardless of whether a match exists, which can deliberately or accidentally introduce duplicates.
• Update existing records with imported data — matching records are overwritten with the incoming data, replacing field values in the existing bill.

This is a completely separate mechanism from the duplicate invoice warning under Setup > Preferences. The preferences-based warning fires only during manual bill entry. The Import/Export Assistant's check runs at the moment of import, comparing incoming records against what already exists in your MYOB file. The two systems do not interact.

That distinction matters because the Import/Export Assistant's duplicate handling has a narrow scope. It only evaluates records during the import itself. It will not retroactively flag duplicates already sitting in your purchases register, and it offers no protection against duplicates entering through other channels such as manual entry or the In Tray. If the same invoice arrives once via import and once through manual entry, neither mechanism catches the overlap.

When importing invoices into MYOB via the Import/Export Assistant, select the duplicate handling option that fits your workflow. For most AP teams processing supplier bills at volume, Reject duplicate records is the safest default. Switch to Update existing records only when you intentionally need to overwrite previously imported data, and avoid Add duplicate records unless you have a specific reason to allow it.

---

Closing the Control Gaps Before Invoices Reach MYOB

MYOB's native duplicate detection covers only a narrow slice of the problem. Strengthening your controls requires work on two fronts: tightening the processes around manual entry and adding an upstream validation layer that catches duplicates before they ever touch your accounting system.

Standardise Your Invoice Number Entry Rules

Most duplicate failures trace back to inconsistent data entry. One team member keys in INV-001, another enters 001, and MYOB treats them as completely different invoices from the same supplier. Eliminate this by documenting a clear entry standard for your AP team:

• Always enter the full alphanumeric string as printed on the supplier's invoice. Do not strip prefixes, suffixes, or leading zeros.
• Agree on separator handling. If a supplier prints "INV 001" with a space, decide whether your team records it with a hyphen, a space, or no separator, and apply that rule every time for that supplier.
• Record the standard in your AP procedures document so new staff follow the same convention from day one.

This alone will not catch every duplicate, but it makes MYOB's existing exact-match warning far more likely to trigger when it should.

Run Periodic Duplicate Scans

For invoices that slip through, a retrospective check acts as a safety net. Export your bills to a spreadsheet, then sort or filter by supplier and invoice number to surface duplicates. This is especially important for MYOB Business users, who have no native duplicate detection at all. Running this scan monthly (or weekly during high-volume periods) catches duplicates that entered through the Import/Export Assistant, manual entry without warnings, or any other unprotected channel.

At minimum, MYOB Business users should check each supplier invoice number against recent entries before recording a new bill. It is a manual step, but without native controls it is the only pre-entry defence available inside the application.

Validate and Normalise Invoice Numbers Before Import

The most effective control is preventing duplicates from reaching MYOB in the first place. An upstream extraction layer addresses the root cause: supplier invoices arrive in inconsistent formats, and MYOB's duplicate check relies on exact string matching. If "INV-001", "INV 001", and "001" all refer to the same invoice, they need to be normalised to a single canonical format before import.

You can extract and validate supplier invoice data before importing into MYOB by uploading your supplier invoices to an AI-powered extraction tool. The process is straightforward: upload a batch of invoices, prompt the AI to extract supplier name, invoice number, date, and total, and instruct it to normalise invoice number formats by stripping whitespace, standardising prefixes, and removing formatting inconsistencies. The output is a structured spreadsheet where duplicate invoice numbers per supplier become immediately visible before anything enters MYOB.

Because the extraction is prompt-driven, you can tailor the normalisation rules to your supplier base and apply them consistently across every batch.

Once the extracted data is clean and deduplicated, it imports into MYOB through the Import/Export Assistant with far greater reliability. The assistant's own reject duplicate records check now works properly because the invoice numbers are formatted consistently. For manual entry workflows, your team is keying in standardised values that align with what is already in the system, so AccountRight's duplicate warning fires correctly.

Layer Your Controls

No single check eliminates duplicate payments entirely. The combination of standardised entry rules, periodic retrospective scans, and upstream normalisation creates a layered defence consistent with broader accounts payable duplicate payment controls, where a duplicate invoice has to bypass multiple independent checks before it results in a payment, rather than relying on a single warning that can be dismissed with one click.