- Reviewing is what keeps an import accurate — AI reading is good, not perfect, and bulk imports surface duplicates
- Use filter tabs (All, Ready, Needs Review, Duplicates) to focus instead of scrolling one long list
- Check the Needs Review tab closely for misread amounts, dates, and garbled merchant names
- Use the Duplicates tab to skip repeats — critical when import windows overlap
- Deselect noise like internal transfers, then confirm; nothing saves until you do
The review screen is the most important step in any import, and the one people most want to skip. After the AI extracts your transactions, it’s tempting to slam “confirm” and move on. Don’t. Two minutes here is the difference between a budget you trust and one quietly full of errors.
This is a short, practical tutorial on reviewing an import properly — what to check, how to use the filter tabs, and how to confirm with confidence.
Why the Review Step Exists
Importing is not the same as trusting. Two things make review necessary:
AI reading is accurate but not perfect. A screenshot or PDF has to be visually interpreted, and unusual formats — foreign currencies, dense tables, odd date layouts — can produce a misread. (CSV is structured data, so it’s the most accurate going in, but still worth a glance.)
Bulk imports surface duplicates. If the batch you’re importing overlaps with transactions you already have, you’ll get repeats. A good importer flags them, but you decide what to skip.
The review screen exists so you handle both before anything touches your real history. Skip it and the errors compound silently — which is how people end up with a budget they stop believing.
If an app drops transactions straight into your history with no chance to review, that’s a problem, not a convenience. Insist on reviewing before saving — it’s the safeguard that makes importing trustworthy in the first place.
Use the Filter Tabs to Focus
Scrolling one long list of extracted transactions is slow and error-prone. A well-designed review screen — like the one in Smart Import — gives you filter tabs so you can work in focused passes:
- All — every extracted transaction, for a final overview
- Ready — clean extractions the app is confident about; a quick scan is usually enough
- Needs Review — transactions the app is unsure of; check these closely
- Duplicates — likely repeats of existing transactions; skip these
Working tab by tab turns a daunting list into three quick, targeted passes. Start with Needs Review, then Duplicates, then a glance at Ready.
The Review, Step by Step
Start with Needs Review
These are the transactions most likely to have an error. Check each amount, date, and description against what you’d expect. Fix anything wrong — the fields are editable drafts, so just tap and correct.
Clear the Duplicates tab
Look at everything flagged as a duplicate. If it’s genuinely already in your records, deselect it so it isn’t added twice. This matters most when you imported overlapping files.
Scan the Ready tab
These should be clean, but give them a quick pass anyway. You’re mainly looking for an amount that seems too high or a date that’s out of range — the fingerprints of a misread that slipped through.
Deselect the noise
Remove transfers between your own accounts and anything that isn’t real spending. You want your budget to reflect money spent, not money moved around.
Confirm
Once each tab is handled, confirm. Only now does anything save to your history — everything up to this point was a reviewable draft.
What to Look For (The Common Errors)
Knowing where misreads hide makes reviewing faster. The usual suspects:
- Misread amounts — most common with blurry screenshots or multi-currency statements; a decimal in the wrong place or a currency confusion
- Misparsed dates — when the statement uses an unusual format, a date can land in the wrong month
- Garbled merchant names — cosmetic, but worth a fix if you rely on descriptions to categorize
- Duplicates from overlapping files — the CSV and the PDF both covered last week
If an amount looks wrong or a date seems off, that’s your signal to look closer. Everything else is usually fine.
When you’re short on time, prioritize checking the largest transactions. A misread on a big purchase distorts your budget far more than a wrong amount on a small one. Scan the biggest figures first, then the rest.
Categorize Now or Later?
You can categorize on the review screen or afterward — both are valid:
- Categorize during review if you’re importing a small batch and want it all done in one pass.
- Confirm first, categorize later if you’re importing a large backlog; it’s often faster to get the data in accurately, then do a categorization pass. The follow-up steps are in what to do after you import bank transactions.
Either way, don’t let categorizing slow down the accuracy review. Getting the amounts and dates right matters more than having every label perfect the first time.
After You Confirm
Once you’ve confirmed a clean import, the payoff arrives. Your data is accurate, so anything you build on it — reports, budgets, questions — is trustworthy.
This is a great moment to interrogate the data. If your app has an assistant like Huntee, ask it what your biggest expenses were, or how much a category came to. You just reviewed the transactions, so you know the answer is built on clean data. Accurate import in, reliable insight out.
This is general educational content, not financial advice. Review practices vary by app; always check extracted data before saving it. If you’re dealing with serious debt or financial hardship, consider speaking with a qualified financial professional.
Final Takeaway
The review step is the quiet hero of importing. It’s where AI’s near-misses get corrected, duplicates get skipped, and noise gets removed — before any of it reaches your budget. Use the filter tabs, start with Needs Review, prioritize big amounts, and confirm only when each tab is handled.
Two focused minutes is all it takes, and it’s what makes the difference between importing data and importing accurate data. Ready to try it? Run an import and review it.
Frequently Asked Questions
Why do I need to review imported transactions?
Because importing isn’t the same as trusting. AI reading a screenshot or PDF is accurate but not perfect, and any bulk import can surface duplicates of transactions you already have. The review step lets you catch misreads, skip duplicates, and remove noise before anything is saved. Two minutes of reviewing is what keeps your budget data accurate enough to trust.
How do I find duplicate transactions after importing?
A good importer detects duplicates automatically by matching date, amount, and description against your existing transactions, then flags them. Use the duplicates filter on the review screen to see just those, and deselect the ones already in your records. This matters most when your import windows overlap — like a CSV and PDF that both cover the same week.
What are the most common import errors to check for?
The usual suspects are misread amounts (especially from blurry screenshots or multi-currency statements), misparsed dates when the format is unusual, garbled merchant names, and duplicates from overlapping files. Scan for anything where the amount looks wrong or the date seems out of range — those are where misreads hide.
Do I have to categorize during the review, or after?
Either works. Some people categorize on the review screen so everything’s done in one pass; others confirm first and categorize in a separate cleanup. If you’re importing a large backlog, it’s often faster to get the data in accurately first, then categorize the big and recurring items afterward.
What do the review filter tabs mean?
Filter tabs let you focus during review. “All” shows every extracted transaction. “Ready” shows clean extractions the app is confident about. “Needs Review” flags transactions the app is unsure of, so you check those closely. “Duplicates” shows likely repeats of existing transactions so you can skip them. Working tab by tab is faster than scrolling one long list.
