Why QuickBooks Rejects Your Bank Statement

A rejected import almost always comes down to one of four things: the wrong file format, a corrupted export, a date format QuickBooks doesn't recognize, or a bank statement layout the import tool doesn't understand. Knowing which one you're dealing with is most of the fix.

None of these are QuickBooks being difficult for no reason — each one is a specific, fixable mismatch between what the file contains and what the import screen expects. Working through them in order usually finds the problem faster than re-exporting the same file and hoping it works the second time.

The wrong file format

This is the most common cause, and the easiest to check. QuickBooks Desktop imports QBO or IIF files; QuickBooks Online's bank feed import takes QBO or OFX. A CSV export will sometimes work, but only once every column has been mapped to match what QuickBooks expects — skip that step and the import fails outright. Our comparison of QBO, OFX, and CSV breaks down which format each version actually needs.

A corrupted or incomplete export

A file that looks fine when you open it can still fail on import if the export itself was cut short or corrupted partway through — a browser tab closed mid-download, a spreadsheet re-saved in a format that stripped some of the original structure, or a PDF that only captured part of a multi-page statement. If a file fails to import and the format is definitely correct, re-exporting or re-downloading the original statement is worth trying before anything else.

A date format QuickBooks doesn't recognize

Dates are one of the most common silent failure points. A statement exported as DD/MM/YYYY will misread as MM/DD/YYYY (or the reverse) in some import paths, and QuickBooks doesn't always flag this clearly — transactions can import with the wrong date instead of failing outright, which is arguably worse than a rejected import, since it can slip past a quick review. This is exactly the kind of mismatch that's easy to miss when reformatting a statement by hand, and one reason a converter built specifically around QuickBooks's expected format matters more than it might seem.

An unsupported bank statement layout

Every bank formats its statements a little differently — where the transaction table starts, how multi-line descriptions are broken up, how debits and credits are represented. A converter or import tool built around a specific set of banks will read those correctly; handed a statement from a bank it wasn't built for, it may misread the layout entirely, dropping transactions or garbling amounts. Skyline Convert is built around statements from RBC, TD, Scotiabank, CIBC, BMO, National Bank, Desjardins, and Amex specifically, rather than attempting to guess at an arbitrary layout it's never seen.

Working through it in order

Start with the format — confirm you're exporting QBO or IIF for Desktop, QBO or OFX for Online. If the format is right and the import still fails, check the file itself for signs of a partial or corrupted export. If the file imports but the numbers look wrong, check dates first, since a misread date format often shows up as transactions landing on the wrong day rather than failing to import at all. And if none of that explains it, the statement's original bank layout is worth checking against what your conversion tool actually supports.

How Skyline Convert avoids most of this

Skyline Convert reads the PDF directly and outputs the exact file format your version of QuickBooks expects — QBO or IIF for Desktop, QBO or OFX for Online — so the format mismatch that causes most rejected imports isn't a decision you have to get right yourself. Every transaction lands in an editable review table before the file is generated, with the running total checked against the statement's own balance, so a misread date or amount surfaces before the import happens rather than after. See the full conversion process for how the upload-review-download flow works end to end.

Frequently asked questions

My file imported but some transactions are missing. What happened?

That's usually a layout issue — the import tool read part of the statement but not all of it, often because of how that specific bank formats multi-line transactions. Re-checking against the original PDF is the fastest way to confirm what's missing.

Why did QuickBooks accept the file but show the wrong dates?

This is almost always a date-format mismatch — DD/MM/YYYY read as MM/DD/YYYY or the reverse. It's worth checking the first few transactions against the original statement any time an import completes without an error.

Is a rejected import always a formatting problem?

Not always, but it's the most common cause by far. A corrupted export and an unsupported bank layout are the next two things worth ruling out before assuming the data itself is the issue.

Once I fix the immediate error, could the same problem happen again next month?

It can, if the underlying cause was the export process rather than a one-off glitch — the same bank layout or date format will produce the same mismatch on the next statement too. Fixing it at the conversion step, rather than patching the imported file each time, is what stops it from recurring.

The bottom line

A rejected or wrong-looking import almost always traces back to one of a handful of specific causes, not a mystery. Working through format, file integrity, dates, and bank layout in that order finds the actual problem faster than re-exporting and hoping — and using a converter built around the format your QuickBooks version needs removes the most common cause before it happens.

Try Skyline Convert →