THE IMPORT RESCUE GUIDE

Review possible duplicate bank transactions carefully

Why matching date, description, and amount can flag a duplicate without proving one exists.

A match is evidence, not a verdict

Two transactions with identical dates, amounts, and descriptions may both be legitimate. Treat a match as a review warning and check bank transaction identifiers or the original statement before removing anything.

Check overlap between sources

Duplicate records can result from overlapping export date ranges or importing a file after a bank feed has already brought in the same activity. Compare the existing register and pending bank feed transactions before importing again.

Keep an audit trail

Record which row you intend to omit and why. Compare signed totals and row counts before and after the change. Keep the original file so an accidental omission can be investigated.

Use account context

This website cannot see your QuickBooks register and currently offers only a synthetic example. Future local file checks alone cannot prove whether a transaction already exists in your account.

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 →