Bank statement to MYOB
Turn any bank's PDF statement into an OFX or QIF bank-feed file (or a CSV) that MYOB imports straight into the bank account — no manual entry. Any AU, NZ or international bank, scanned or digital, balance-validated.
Any bank · scanned or digital · balance-validated · OFX / QIF / CSV
Get PDF statements into MYOB without retyping
MYOB's bank feeds are great for the major Australian and New Zealand banks — but feeds take days to set up, don't cover every account, and won't help with the historical months you only have as PDF statements. Entering those by hand in MYOB Business or AccountRight is slow and a common source of reconciliation errors.
FlowParse extracts every transaction from the PDF and writes a bank-feed file MYOB reads — OFX or QIF — or a clean CSV, with debits and credits normalised to a single signed amount and dates parsed in DD/MM/YYYY. Every file is balance-validated so the imported account reconciles cleanly.
AI extraction handles any layout, so statements from CommBank, Westpac, ANZ, NAB and the neobanks all convert the same way — as do international banks for businesses that trade across borders.
Two ways in
In the file
From PDF to MYOB in three steps
1 · Upload the PDF
Drop your PDF bank statement — digital or scanned, any bank, any number of pages.
2 · AI builds the file
FlowParse extracts every transaction, signs the amounts, validates balances and writes a OFX.
3 · Import into MYOB
Bring the file into the matching account in MYOB and reconcile — no manual entry.
How to import into MYOB
Convert: upload the PDF to FlowParse, review the editable preview, and download the OFX (or QIF/CSV).
Import: in MYOB, open Banking and import the statement file into the matching bank account, then match and allocate the transactions as you reconcile. OFX/QIF carry per-transaction detail so MYOB lines them up correctly; with CSV, run it through the import and map Date, Amount and Description.
Recording sales too? FlowParse also produces a MYOB Service sales import CSV (Import/Export Assistant → Sales) so invoices follow the same path.
What lands in the MYOB file
| Field | From the statement |
|---|---|
| Date | Transaction date (DD/MM/YYYY) |
| Amount | Signed — money out negative, money in positive |
| Description | Payee / narrative (extra columns kept here) |
Works with any bank's PDF
Because extraction is AI-based rather than template-based, FlowParse reads layouts it has never seen — ideal for accounts MYOB's feeds don't cover and for historical months:
Reconciling a whole year? Use Smart Merge to consolidate first, then export once.
Why convert instead of keying it in
In MYOB, a reconciliation that won't balance usually traces back to a typing slip or a feed gap — a missed line, a wrong sign on a refund, a duplicated payment. Converting the PDF removes the typing and the balance check proves the period is complete before it reaches MYOB, so the account reconciles on the first attempt.
For BAS time and year-end, that reliability compounds: a bookkeeper can bring in a year of statements across several accounts in minutes and spend their time on review and advice, not data entry. Reconciling many months? Smart Merge consolidates them first.
MYOB bank feeds, imports and the gaps between them
MYOB bank feeds work well for the big AU and NZ banks once they're set up — but setup can take days while the bank approves the feed authority, and feeds don't cover every account, card or international bank. In the meantime, and for any account a feed never reaches, you're left importing statements manually. MYOB supports that through OFX and QIF bank-feed files and CSV, so the real question is how to turn a PDF Kontoauszug — sorry, a PDF statement — into one of those formats without retyping. That's what FlowParse does, with DD/MM/YYYY dates and signed amounts that match MYOB's locale.
The choice between MYOB Business (the cloud product) and AccountRight (desktop) doesn't change the approach: both read a standard OFX/QIF bank-feed file, and both have a CSV import wizard where you map Date, Amount and Description. FlowParse produces all three from one upload, so whichever MYOB product a client runs, the file is ready. Once the transactions are in, MYOB's bank rules auto-allocate the recurring ones, so the cleaner the imported descriptions, the less manual coding you do.
For Australian and New Zealand bookkeepers, the payoff lands hardest at BAS and year-end. Instead of keying months of transactions across several accounts, you convert each statement, let the balance check confirm nothing's missing, and import — turning a day of data entry into a few minutes of upload-and-review. Reconciling a full year across accounts? Smart Merge consolidates the statements first so you import a single clean set.
Validated before it reaches MYOB
A bad import means a reconciliation that never balances. Before the file is built, FlowParse checks the data so what lands in MYOB is complete and correct:
See the validation engine and reconciliation tools.
Accuracy, security and a BAS-time catch-up
Accuracy is what keeps a MYOB reconciliation from becoming a hunt for a difference. FlowParse reads each statement by meaning, so AU, NZ and international layouts are handled without per-bank templates, and scanned statements are OCR'd before structuring. Crucially, every statement is balance-validated (opening + transactions = closing) before it becomes a file, with low-confidence fields flagged in an editable preview — so what lands in MYOB is complete and correctly signed.
Bank data is sensitive, so FlowParse processes in EU data centres, deletes the original PDF after extraction, encrypts the extracted data, and never trains models on your documents (see the security page). For a bookkeeper handling several clients, that's one less thing to worry about at a busy time of year.
BAS time is where this earns its keep. Imagine a bookkeeper with five clients, each with a couple of bank accounts and a card, none of them fully on feeds. Instead of keying months of transactions, they convert each statement, let the balance check confirm nothing's missing, and import OFX/QIF straight into MYOB — a day of data entry compressed into a short review. Reconciling a whole year? Smart Merge consolidates the statements first.
The same extracted data also exports to Excel and to other accounting systems, so a client who later moves tools — or who runs MYOB alongside something else — never forces a re-upload. One conversion serves every destination.
One upload, every format
The same extraction powers every export — so if you also run QuickBooks, Quicken, Xero or just need a spreadsheet, take the same statement to the format you need without re-uploading.
Take the same data to Excel, QuickBooks or Xero.
| Format | Best for |
|---|---|
| OFX | Importing this statement into MYOB |
| Excel (.xlsx) | A full workbook with every source column for your records |
| CSV | A simple, editable table for any tool or import wizard |
| OFX / .QBO / .QFX | Bank-feed files for QuickBooks, Quicken and OFX apps |
| Xero / Sage / Wave | Tailored CSV layouts for other accounting software |
Who imports statements into MYOB this way
Anyone who reconciles a MYOBbank or card account from statements rather than a live feed — because the feed doesn't cover the account, hasn't been set up yet, or the months they need predate it. A few of the most common:
AU/NZ bookkeepers
Catch up MYOB bank accounts in minutes and reconcile for BAS.
Accountants
Bring client bank history into MYOB without re-keying months of data.
Small businesses
Import statements from accounts MYOB feeds don't cover.
AccountRight users
Load OFX/QIF into desktop ledgers for clean reconciliation.
Importers/exporters
Convert international bank statements for MYOB.
Tax agents
Standardise mixed-bank PDFs before year-end and BAS.
Any bank → one MYOB-ready file
Upload statements from every account you reconcile — FlowParse turns each into a clean file MYOB imports.
Tips for a clean import into MYOB
A statement import goes smoothly when the data underneath is complete and correctly signed. A few habits make every MYOB import reconcile on the first pass:
- Convert the full statement period rather than a partial export, so the opening and closing balances are present for the validation check to confirm nothing is missing.
- Import each statement period once — or use the OFX file where MYOB supports it, since it de-duplicates by a per-transaction ID if you re-import.
- Match the MYOB account's currency to the statement you're importing; FlowParse preserves the amounts and signs exactly as the bank reported them.
- Review the fields the validation report flags in the editable preview before you download — clean statements pass automatically, so you only check the exceptions.
- Reconciling a whole year? Consolidate the statements with Smart Merge first, then import a single clean, balance-checked set into MYOB.
Frequently asked questions
How do I import a bank statement into MYOB?
Convert the PDF with FlowParse to an OFX or QIF bank-feed file (or CSV), then in MYOB go to Banking and import it into the matching bank account. Match and allocate the transactions as you reconcile; OFX/QIF line them up automatically.
Does MYOB import OFX, QIF or CSV?
MYOB works with OFX and QIF bank-feed files and with CSV via its import. FlowParse can produce each from the same upload, so you use whichever your MYOB product and workflow prefer.
Does this work for MYOB Business and AccountRight?
Yes. The bank-feed file follows the standard format both read, and the CSV gives a tidy Date / Amount / Description layout for the import wizard in either product.
Can I convert statements from any bank?
Yes — CommBank, Westpac, ANZ, NAB, Macquarie, Bendigo and the neobanks all convert, as do international banks, because extraction is AI-based rather than per-bank templates.
Are the dates in Australian format?
Yes. Dates are written DD/MM/YYYY to match MYOB's AU/NZ locale, and amounts are signed so the balance reconciles.
Can I import historical statements for BAS or year-end?
Yes. Convert any PDF you have, including older months only available as PDFs, and import them to backfill MYOB before reconciling for BAS or year-end.
Is it free to try?
You can convert within the monthly page allowance and preview the transactions first; bank-feed and accounting exports are part of the paid plans for ongoing volume.
Can I convert statements from any bank for MYOB?
Yes. FlowParse uses AI extraction rather than per-bank templates, so PDF statements from UK banks (Barclays, HSBC, Lloyds, NatWest, Monzo, Starling), US banks (Chase, Bank of America, Wells Fargo, Capital One), and EU and neobanks (Wise, N26, Revolut) all convert to a MYOB-ready file. A layout the tool has never seen is read correctly on the first try.
Are scanned or photographed statements supported?
Yes. Image-only PDFs run through OCR first, then the AI structures the recognised text into transactions before building the file for MYOB. Any low-confidence field is flagged so you can check it before importing.
How are debits and credits handled?
They are normalised into a single signed amount — money out negative, money in positive — with the correct transaction type, so the imported balance reconciles against your account.
Is the conversion accurate?
FlowParse reaches around 98% field-level accuracy on standard statement formats, and every file is balance-validated (opening balance + transactions = closing balance) with per-field confidence scores you can review before importing into MYOB.
Can I review the transactions before importing?
Yes. An editable preview lets you correct any value, and the validation report flags duplicates, low-confidence fields and balance breaks before you download the file — so nothing wrong reaches your books.
Do I also get other formats from the same upload?
Yes. One upload can export Excel, CSV, OFX and the Intuit-tagged .QBO and .QFX for QuickBooks and Quicken, plus Xero, Sage, Zoho Books, NetSuite and MYOB — so multi-tool firms convert once and export everywhere.
Where are my bank statements processed and stored?
FlowParse processes documents in EU data centres, deletes the original PDF as soon as extraction completes, stores only the extracted data (encrypted, and deletable on demand), and never uses your documents to train models. So converting a statement for MYOB is safe, not a privacy trade-off — the full posture is on the security page.
What happens with multi-page or very long statements?
They're stitched into one continuous list and any weak page is retried automatically, so nothing is dropped at a page break. The balance check then confirms the whole statement — first page to last — was captured before the file is built.
Can I automate converting statements for MYOB at volume?
Yes. The same conversion runs over the bank statement API: send a PDF and receive structured JSON or a ready-to-import file per page, with the balance validation built in. That lets high-volume teams turn statement intake for MYOB into a pipeline step instead of a manual task.
Do I have to enter any transactions by hand?
No. FlowParse extracts every line from the PDF and writes them into the file, so MYOB loads the transactions in one import instead of you typing each one. You only review the few fields the validation report flags.