Let’s tidy up that bank CSV.

1. Grab the practice file

Download the practice CSV (.csv)

Try QuickBooks CSV Fixer ↗

Free · no account needed · files processed in your browser

Open the fixer and choose your download. We’ve included a bad date and a repeated row so you can see what needs attention.

2. Match the columns

Keep First row contains column names checked. Match the columns like this:

• Date order: Day / Month / Year
• Number format: 1,234.56
• Remove later copies of exact duplicates: off

These settings are for this example. Check your own bank’s date and number formats before using a real file.

3. Take a look at the result

Here’s our example subscription, tidied up:

The date still means February 3; the output uses month/day/year. Parentheses become a minus sign.

Expect 4 valid rows, 1 invalid row and 1 exact duplicate. The bad date is left out, not fixed. The repeated row stays because removal is off.

Compare yours with the expected result (.csv)

That’s the practice done. For real files, keep the original and correct every excluded row using your source before importing. Never guess a missing date or remove a payment just because it repeats.

The tool cannot detect previous QuickBooks imports or guarantee acceptance. Review your file and the QuickBooks import preview separately.

Optional: which number format does my bank CSV use?

Compare these synthetic amounts with the decimal and grouping separators in your original statement or bank export settings. Do not delete punctuation until you know what it means.

This separate synthetic CSV example quotes the amount because it contains a comma. Practice only; never import it into a real account.

Date,Description,Amount
03/02/2026,DEMO deposit,"1.234,56"

Choose Day / Month / Year and Number format 1.234,56. The date means February 3 and exports as 02/03/2026; the amount exports as 1234.56.

1.234 or 1,234 alone can mean different amounts. Likewise, 01/02/2026 can mean January 2 or February 1. Auto-detect blocks every corrected download when either has multiple valid meanings; choose the source format explicitly. Currency symbols and other rows do not settle an ambiguous value. If different dates require conflicting month-first and day-first formats, correct the source file and load it again; a single choice cannot resolve that conflict.

The formatter changes text and structure. It does not reconcile your account, validate a statement or guarantee import acceptance. For destination requirements, see Intuit’s CSV import troubleshooting.

Why Credit and Debit can look reversed

Source headers do not establish money direction. Use the bank statement or export documentation to identify actual payments and deposits, then review the suggested mappings. Do not rely on the words Credit, Debit or Payment alone, or on currency or locale.

This separate synthetic example defines a payment of 100.00 and a deposit of 200.00. Practice only; never import it into a real account.

Date,Description,Credit,Debit
2026-01-15,DEMO payment,100.00,
2026-01-16,DEMO deposit,,200.00

On first load, these header-based suggestions have not been verified: no corrected download or control total is shown. For this fictional source, change both mappings as shown before confirming. The bank statement or export documentation must establish the meaning for your own file.

After correcting both selectors, check I checked the source and confirm the money-in and money-out mappings shown above, including any unmapped side. The fixer then shows money in 200.00, money out 100.00 and net 100.00. Do not swap every file’s columns: other exports may use the opposite convention. A file with only one direction can leave the other side unmapped after you confirm that this matches the source.

All split-column corrected downloads and control totals stay blocked until you confirm. Changing the file, header interpretation or a column mapping clears confirmation. Ambiguous date and number formats still need resolution separately. The signed Amount workflow does not require this split-column confirmation.

Source confirmation is not destination validation. The fixer retains its existing output header order Date,Description,Credit,Debit, with money in under Credit and money out under Debit. Verify which fields and signs your QuickBooks import expects, map the destination appropriately, and inspect its import preview against your source. Do not assume matching header names mean matching direction or that these totals reconcile your account.

See Intuit’s US CSV format guidance, UK CSV format guidance and manual upload instructions. No destination import or account reconciliation was performed for this example.

QuickBooks CSV too large? Review separate upload parts

Intuit’s manual upload guidance lists a 350 KB file limit and up to 1,000 lines per upload. It recommends downloading a shorter date range for larger uploads. If you already have a CSV, the fixer can split its formatted output: each part has its own header, at most 999 transaction rows and at most 350,000 bytes. Long descriptions can make a part reach the byte limit sooner.

Here is the boundary in a synthetic 1,000-transaction file, with unique descriptions DEMO payment 1 through DEMO payment 1000 and the same date and amount on every row. Map Date, Description and Amount; keep duplicate removal off. Practice only; never import this data into a real account.

Before: the last two transactions in the source CSV (the first 998 are omitted from this excerpt).

Date,Description,Amount
2026-01-15,DEMO payment 999,-1.00
2026-01-15,DEMO payment 1000,-1.00

After — part 1: 999 transactions; this excerpt shows its header and final transaction.

Date,Description,Amount
01/15/2026,DEMO payment 999,-1.00

After — part 2: one transaction; this is the complete CSV content.

Date,Description,Amount
01/15/2026,DEMO payment 1000,-1.00

Choose Download part 1 and Download part 2. A two-row file copied from the excerpt will not split. Review excluded rows first, then check each real part in QuickBooks and keep a record of which parts you imported. Do not also import the original or an overlapping rerun. Splitting cannot detect existing QuickBooks transactions, recover excluded rows or guarantee import acceptance.

Want a closer look?