Six exports, side by side
These are the layouts the converter is tested against — every claim below is checked by an automated test on a file in that format, not copied from a support article.
| Bank | Columns | Header row | Dates | Balance | The thing that catches people |
|---|---|---|---|---|---|
| Chase Checking |
7 | Yes | MM/DD/YYYY | Yes | Ships a Type column most converters throw away — it maps onto real QuickBooks transaction types |
| Bank of America Checking |
4 | Yes | MM/DD/YYYY | Yes | Balances are quoted with thousands separators — "1,954.80". Miss the quoting rule and every column after it shifts |
| Wells Fargo Checking |
5 | Usually none | MM/DD/YYYY | No | The payee column is empty on every row — the real description is in the memo |
| American Express Credit card |
3 | Yes | MM/DD/YYYY | No | The riskiest of the six: nothing in the file can confirm the sign convention, so the preview check is the only safeguard |
| Capital One Credit card |
7 | Yes | ISO YYYY-MM-DD |
No | Separate Debit and Credit columns, one of which is always blank. Blank is not zero |
| Discover Credit card |
5 | Yes | MM/DD/YYYY | No | Two date columns — Trans. Date and Post Date. Picking the wrong one shifts transactions across your month end |
What that table is really saying
A running balance is the difference between "verified" and "guessed"
Only Chase and Bank of America give you one, and it does real work: each balance minus the one before it should equal that row's amount. When that holds for every row, the amount column and the direction of the signs are proved by arithmetic. Without it — the other four — there is nothing inside the file to check against, and the converter says so rather than pretending otherwise.
Credit cards run the signs backwards
Amex, Capital One and Discover all record purchases as positive numbers, because from the card's point of view a purchase increases what you owe. Checking accounts do the opposite. A tool that doesn't detect this imports every transaction the wrong way round — and nothing errors, because a signed number is a signed number. You find out at reconciliation.
Column names are the least reliable thing in the file
Running Bal. and Trans. Date carry stray full stops. Wells Fargo
labels a column payee and leaves it blank. Capital One and Discover name the same idea two
different ways. This is why the converter profiles each column by what it contains
rather than matching header text against a list — header matching is what produces a
statement of blank descriptions.
Bank pages
- Chase CSV to QBO the Type column, and the trailing comma on every line
- Wells Fargo CSV to QBO no header row, and the empty payee column
Bank of America, American Express, Capital One and Discover don't have their own pages yet — the converter handles all four, they just haven't been written up. Use the main converter for those; it reads the same layouts.
Your bank isn't on the list?
Try it anyway. Nothing here is hardcoded per bank. The date, amount, description and balance columns are worked out from what the columns contain, which is why a layout nobody has ever seen usually goes straight through. If a column can't be placed, the page tells you which one instead of failing quietly.
Credit unions and smaller banks are worth a particular mention: they're the ones most likely to have no bank feed available at all, which makes file export the only route in — and their CSV layouts are often stranger than the big six above.
Frequently asked questions
Do all banks export CSV in the same format?
Not remotely. See the table — three columns to seven, one with no header row, one on ISO dates, and the credit cards on the opposite sign convention to the checking accounts. There is no standard to conform to, which is why matching against a fixed template is the wrong approach.
Why do my credit card transactions import backwards?
Because the card lists purchases as positive numbers. The converter detects this and flips them, then asks you to confirm the first transaction — on a card export there's usually no balance column, so that confirmation is the only check available.
My bank offers "Quicken" or "QuickBooks" downloads. Should I use those instead?
If your bank offers a QuickBooks / Web Connect (.qbo) download, take it — that's the file QuickBooks Desktop wants, and you don't need a converter at all. A Quicken (.qfx) download is a different thing: QuickBooks Desktop does not accept it. On Desktop, take the CSV and convert it here.
How far back can I export?
Usually years, which is the real advantage over a bank feed — feeds typically reach back around 90 days. Catching up on old months is the most common reason people end up converting files.
Related
- CSV to QBO converter works with any of the above
- Excel to QBO if your bank gives you .xlsx
- Which file does your QuickBooks take? Desktop vs Online
- Why won't my CSV upload? eight causes, in order