THE IMPORT RESCUE GUIDE

Resolve date ambiguity before a QuickBooks CSV import

Learn how to review ambiguous, mixed, and spreadsheet-altered bank transaction dates before import.

Two valid readings can describe different days

04/05/2026 can represent April 5 or May 4. Look at the bank’s export convention and compare the statement. A value whose day exceeds 12 may provide context, but mixed source data can still be inconsistent.

Confirm one source convention

Select the date interpretation that matches the bank export before choosing an output format. Keep the date mapping and selected format consistent during the QuickBooks import preview.

Watch spreadsheet conversions

Spreadsheet software can interpret dates according to device locale. Preserve the original download and inspect the actual CSV text after saving a copy. Two-digit years and timestamp values also need explicit interpretation.

Check the calendar and statement range

A string that looks like a date can still be impossible, such as February 30. Validate calendar dates and check that the first and last transaction dates match the intended statement period. Do not silently replace an invalid date with today’s date.

Reference: Intuit’s bank CSV formatting guidance. Check the current guidance for your account and workflow.

Explore a careful review

See how the planned tool approaches uncertain values with our synthetic example.

Try the sample demo →