BankImport Rescue

A useful example, with the checks in view

SYNTHETIC INPUTS · NO CUSTOMER DATA

One ambiguous date. Three rows. An exact total.

Use a tiny fictional bank CSV to choose the date order deliberately, inspect possible repeats, and explain every cent in your export.

A file small enough to inspect by eye

Date,Description,Amount
07/10/2026,Sample credit,0.10
07/10/2026,Second credit,0.20
07/10/2026,Sample credit,0.10

No bank connection or real account data. The repeated credit is deliberate test data.

Which date did the source mean?

07 / 10 / 2026

Day / Month / Year: October 7, 2026
Month / Day / Year: July 10, 2026

Both are valid. The tool requires an explicit choice; a plausible-looking date cannot establish the source’s intention.

What belongs in the total?

0.10 + 0.20 + 0.10 = 0.40

All three rows remain included at first. Rows 1 and 3 form one possible-repeat group. A candidate repeat is not proof of a duplicate.

If you deliberately exclude only the third row, two rows remain and the selected net becomes exactly 0.30.

Reproduce the check

  1. Open BankImport Rescue and choose the fictional CSV above. Keep comma separator, UTF-8 and the header row.
  2. Map Date, Description and Amount. Choose one signed amount column; positive amounts mean money coming in.
  3. Choose Day / Month / Year, two decimal places, dot decimals and no thousands separator. Leave the currency marker blank.
  4. Review transactions. The dates should read 2026-10-07. Source and selected net should both be 0.40, with three selected rows.
  5. For this practice scenario only, uncheck the third row (source line 4). Selected net becomes 0.30 and the source net stays 0.40. In a real file, exclude a row only after checking the original records.
  6. Choose the QuickBooks or Xero layout and output date order, complete the review acknowledgement, and download. Recheck the destination app’s preview before importing anything.

Expected exports, kept separate

These reference files were produced by the actual export function using Day / Month / Year input and output. Their names make the exclusion choice explicit.

Checked October 11, 2026 against the actual parsing, analysis, summary and export functions in Node. Amounts use exact integer arithmetic. This does not test a live accounting-app import or reconcile existing transactions.

When this tool is the wrong step

  • Your source is a PDF, image, OFX, QIF or Excel workbook. This release expects CSV, TSV or delimited TXT.
  • Your file mixes accounts or currencies. Separate them before conversion; the tool does not convert currency.
  • You need to repair an unknown date, missing transaction or unexplained balance. Return to the original statement instead of guessing.

Ready to try it?

Every feature and export is free. No account is needed. Start with a practice file, then keep your real inputs local.

Open BankImport Rescue ↗