MYOB Australia: browser or AccountRight statement-import route?
Updated · 4 min read
MYOB’s browser and AccountRight Desktop statement instructions are different routes, even when both accept a bank OFX or QIF. First identify the product and interface, then inspect the account’s import boundary and existing feed coverage. Do not search for a Desktop command inside a browser workflow.
The current MYOB Australia statement guide puts Browser and Desktop branches on one page. This guide helps prepare an import decision; it does not change the company file or perform an upload.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Select the branch before selecting a file
| Check | Browser branch | AccountRight Desktop branch |
|---|---|---|
| Entry point | Banking → Banking hub → account menu → Import statement | Banking command centre → Reconcile Accounts → Get Statement |
| Target identity | Bank account chosen for the import | Account in Reconcile Accounts |
| Earlier-history boundary | Opening balance settings; lock date can also exclude records | Company file’s Conversion Month |
| Review context | Bank statement import history and Bank transactions | Statement matching against existing company transactions |
The same page names QIF and OFX, with files under 10 MB, in its download guidance. Its Desktop steps additionally list QFX and OFC. Keep that distinction visible rather than extending the broader Desktop list to the browser. A CSV prepared for another importer is not automatically a bank statement file for these routes.
Browser preflight: compare the existing history first
- Confirm the bank account in Banking hub. Use its account menu to view the statement-import route and existing import history, without uploading another file during evidence collection.
- Record which date intervals already arrived through a bank feed or previous statement import.
- Inspect Business settings for the opening balance boundary and any lock date. MYOB’s zero-import explanation names dates before those boundaries as possible exclusions.
- Compare the proposed bank file’s actual dates and account with that evidence. Keep any inaccessible setting as unknown rather than adjusting it to make an old file import.
A successful import message with zero transactions is not proof that the file was empty. Check the documented boundary explanations before requesting a new bank export or changing source dates.
Desktop preflight: use the existing company-file context
The Desktop branch starts in Reconcile Accounts, with the target account, statement closing balance and date, then Get Statement. It names cheque number, date and amount as matching criteria. If a transaction is already in the company file, matching it and adding a new Spend Money or Receive Money transaction are different decisions.
Record the Conversion Month and the existing account records before choosing the candidate file. The browser’s Opening balance date and Desktop’s Conversion Month are not interchangeable controls. Do not alter either merely to bypass a historical import restriction.
Synthetic route check for a historical September file
An invented September bank file is intended for browser account A. The working notes instead contain a screenshot instruction saying “Get Statement” from Desktop, while browser history already covers September 15–30 through a feed.
| Finding | Result of the preflight |
|---|---|
| Desktop menu in a browser job | Replace the instruction with the browser branch |
| Proposed full-month file overlaps the feed | Establish the real missing records before preparing another import |
| Old dates meet an opening or lock boundary | Ask the responsible reviewer to resolve the boundary; do not rewrite bank dates |
This example does not establish a real import range. MYOB documents a deletion-and-replacement path for a specific duplicate-import case, but that is not a general instruction to delete reconciled or linked data. Deliver the branch, destination, existing coverage and boundary notes before any authorised import. That is the useful result; changing a setting or receiving an import message alone does not complete reconciliation.
Synthetic review case. The values are teaching data, not a vendor export or an import file.
For a bank source available only as PDF, download LocalExtract. It processes one PDF locally into date,description,amount CSV; review and adapt those rows for the actual destination.
Related guide: Bank statement CSV: check the format before an accounting import.
Documentation for the added task checked October 16, 2026.
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy