Bank statement to QuickBooks
QuickBooks will not accept a raw statement PDF, and it is picky about the CSV you feed it. The requirement is narrow: a date, a description and a signed amount, in that order, with no balance column confusing the parser.
What QuickBooks expects
The three columns below are what the CSV importer maps to. Anything else either gets ignored or breaks the mapping step.
| Target | Column 1 | Column 2 | Column 3 |
|---|---|---|---|
| QuickBooks CSV | Date | Description | Amount |
The sign convention is the whole game
QuickBooks treats a positive amount as money in and a negative amount as money out. If your bank prints both as positive numbers in separate columns, every withdrawal imports as a deposit and your reconciliation is off by twice the value. One signed amount column removes that failure mode entirely.
Balance columns break the importer
A running balance column is useful to a human and harmful to the importer, which will try to map it as a second amount. Export the CSV without it — the balance is not part of the transaction, it is a derived value that QuickBooks recalculates.
Questions
Can I import directly instead of using the bank feed?
For a historical period the bank feed no longer reaches, a CSV import is the normal route. Convert, then import through the bank account's upload option and review the mapping step before committing.
Will duplicates occur if the bank feed is also on?
Possibly, for any period the feed already covered. Import historical periods that the feed missed, or review the for review queue before accepting anything.
Does this work with QuickBooks Online and Desktop?
The CSV shape suits QuickBooks Online. Desktop accepts the same file through its own import wizard, though the mapping screen differs.
Other formats
Try it on your own statement
No account, no card, no email. Convert one file and check the rows against the original.
Open the converter