Reproducible conversion walkthrough
Verify a bank CSV conversion before importing it.
John Moores, Mockup Maestro · October 2, 2026
A successful download can still contain wrong dates, direction or scope. This walkthrough uses three invented transactions and an automated comparison with the converter's output. It proves preparation arithmetic, not acceptance by a particular QuickBooks edition.
Download both sides of the example
Original signed-amount CSV · Expected normalized CSV · Reconciliation checklist
Never import these fictional files into production books. Map Posted Date → Date, Description → Description, Amount → signed Amount and Reference → transaction ID. Keep the date order month/day/year. The normalized CSV contains Date, Description and Amount; the reference is not an extra column in that export.
| Transaction | Direction | Expected amount |
|---|---|---|
| Northside Office Supply, Store 14 | Withdrawal | −$42.60 |
| Customer Receipt | Deposit | $900.00 |
| Monthly Bank Fee | Withdrawal | −$9.00 |
Four independent checks
- Count: three transactions remain three; exclude the header.
- Dates: July 1–3, 2026. Confirm the source date convention: 07/01 is ambiguous without it.
- Direction: withdrawals total $51.60 and deposits total $900. Negative amounts are money out here.
- Net: $900 − $51.60 = $848.40. Movement is not a closing balance.
The comma in the first merchant name stays inside a quoted field. Splitting on every comma would shift the amount column. The fixture verifies that the description remains one field.
Test a controlled failure
On a copy, change the fee date to 02/30/2026. The converter should reject that impossible date rather than move it into March. In a separate debit/credit layout, populating both money-out and money-in on a row should also be rejected. Undo the change before comparing exports.
What has—and has not—been verified
Regression tests compare the downloadable expected CSV with output from Bank2QBO's parser and normalization functions. The input is fictional. No authenticated import into a current QuickBooks Online or Desktop account was performed for this walkthrough; no bank-specific certification is claimed.
CSV preparation and QBO Web Connect are different paths. QBO needs institution/account identifiers and an explicit closing balance; net movement cannot substitute for it. Institution recognition can still reject a structurally valid file. Read the format comparison and QuickBooks CSV guidance before exporting.
Apply the checks to a real import
Start with a short, non-overlapping range from one account. Retain the untouched export; compare counts, dates and totals; select the correct receiving account; inspect its transaction review screen; and reconcile against the statement. Record scope and outcome in the import control log before retrying a batch.
Try the converter · Testing methodology · Report a fictional reproduction