QuickBooks’ new AI feature for importing bank statements is incredibly convenient—until it’s not.
I just watched a business owner almost import $150,000 when the actual transaction was $1,500. The AI misplaced a decimal point, and they nearly clicked “import” without checking.
If that error had made it into their books, their profit and loss statement would have been off by $148,500. Their cash flow reports would have been meaningless. Their tax returns would have been wrong.
All because they trusted the AI without verification.
After 30+ years of bookkeeping, I can tell you that AI is a powerful tool—but it makes mistakes. And in bookkeeping, a single decimal point error can cascade into thousands of dollars in problems.
Let me show you exactly how to review AI-imported bank statements so you catch errors before they destroy your books.
How QuickBooks AI Statement Import Works
QuickBooks can now use AI to scan your bank statements and extract transaction data automatically—dates, amounts, check numbers, descriptions.
The promise: Upload your statement PDF, let AI extract the data, import everything instantly.
The reality: AI gets most of it right, but makes enough mistakes that you absolutely cannot skip the review process.
When AI Can’t Extract All Data
Sometimes the AI tells you upfront it had problems. You’ll see a notification on your dashboard:
“We weren’t able to extract all the data from your statement, but you can see what we got and make edits.”
Click “View statement” to access the review screen.
The Review Process: What You’ll See
The review screen shows you:
- Total questions: How many transactions need your attention (highlighted items)
- Empty fields: Missing data the AI couldn’t extract
- Edited items: Transactions the AI modified
In the example I’m working with, there are 31 questions the AI has about the imported data.
Critical insight: Just because a transaction isn’t highlighted doesn’t mean it’s correct. The AI might have extracted a number confidently—but wrong.
How to Review AI-Extracted Transactions
Step 1: Start with Highlighted Items
Click on the first highlighted transaction. The system will walk you through each one sequentially.
What to verify:
- Date format is correct
- Amount matches the statement exactly
- Decimal points are in the right place
- Check numbers are present (or noted as missing)
Step 2: Check the Amounts Carefully
This is where the most dangerous errors hide.
Example from a real statement review:
AI extracted: $150,000
Actual amount: $1,500
The decimal point was missing. If imported without correction, this would have inflated expenses by $148,500.
Another common error:
AI extracted: $13,358.11
Actual amount: $133.58
Decimal moved two places. A $13,000+ error on a $133 transaction.
Step 3: Don’t Just Check Highlighted Items
The AI only highlights transactions it’s uncertain about. But it can be confidently wrong on others.
Action step: Scan all amounts, especially ones that seem unusually large or small for your business.
Ask yourself: “Does a $15,000 transaction make sense for this vendor?” If not, verify it against the actual statement.
Step 4: Handle Empty Fields
Sometimes the AI can’t read certain data at all—particularly check numbers on older statements or handwritten entries.
For missing check numbers: Enter “No check number” or the actual number if you can find it.
For missing dates: Click into the date field, reference your statement, and enter in the correct format (MM/DD/YYYY).
Step 5: Final Verification Scan
Before importing, scroll through the entire list one more time.
Look for:
- Decimal point errors (amounts that seem too large or too small)
- Missing data you might have skipped
- Duplicate entries
- Transposed numbers
Real story: In my example review, I almost missed a decimal error on the final scan. Glad I checked—it would have been a $10,000+ mistake.
Step 6: Import the Corrected Data
Once everything looks accurate:
- Check the box at the top to select all transactions
- Click Import
- QuickBooks imports the corrected data into your account
The Most Common AI Import Errors
Error #1: Missing or Misplaced Decimal Points
This is the #1 issue I see when reviewing AI imports.
The AI struggles with:
- Handwritten amounts
- Unusual fonts or formatting
- Faded or poor-quality scans
- Decimal points that are faint or unclear
Result: $1,500 becomes $150,000 or $15.00.
Error #2: Date Format Confusion
The AI sometimes:
- Reverses month and day (01/03/2024 vs 03/01/2024)
- Extracts the wrong date from multi-date statements
- Completely misses dates on certain transactions
Error #3: Missing Check Numbers
Older statements or statements with handwritten check numbers often have this data missing entirely.
Why this matters: Check numbers help you match transactions to your records and catch missing checks or duplicates.
Error #4: Transposed Numbers
The AI occasionally swaps digits: $1,234 becomes $1,243.
Small difference, but wrong is wrong—and these add up.
Error #5: Skipped Transactions
Sometimes the AI misses transactions entirely, particularly:
- Transactions at the edge of scanned pages
- Very small amounts
- Handwritten entries
- Transactions in unusual formatting
Solution: Compare the AI’s transaction count to your statement’s transaction count. If they don’t match, you’re missing data.
Why This Review Step Is Non-Negotiable
“But the AI got most of it right. Can’t I just import and fix errors later?”
No. Here’s why:
Problem #1: Errors Cascade
One wrong transaction affects:
- Your bank reconciliation
- Your profit and loss statement
- Your cash flow reports
- Your tax calculations
- Your business decisions based on wrong data
Problem #2: Errors Are Hard to Find Later
Once imported, that $150,000 transaction looks legitimate in your books. You might not notice it for weeks—until you’re reconciling or preparing taxes.
By then, you’ve made business decisions based on inaccurate data.
Problem #3: Fixing Is Harder Than Preventing
Catching an error during review takes 5 seconds: “That’s wrong, fix it.”
Catching an error two months later takes 30 minutes: “Where did this come from? Is it real? Do we need to void it? What else is affected?”
Best Practices for AI Bank Statement Imports
1. Use High-Quality Scans
The better your statement quality, the fewer errors the AI makes.
Upload clear, complete PDFs directly from your bank if possible, rather than scanning paper statements.
2. Review Immediately After Import
Don’t let AI imports sit in “pending” status. Review and correct them the same day.
Why: Fresh in your mind means you’ll catch errors faster.
3. Compare Transaction Counts
Before you start reviewing, note how many transactions are on your actual statement. After AI extraction, verify the count matches.
Mismatch = missing transactions.
4. Trust But Verify
The AI is helpful, but it’s not infallible. Always verify before importing.
5. Keep Your Statement Handy
Have the actual statement open while reviewing so you can quickly reference unclear items.
The Bottom Line
AI bank statement import is a powerful time-saver—if you use it correctly.
The process:
- Upload statement
- Let AI extract data
- Review EVERY transaction (especially amounts and dates)
- Correct errors
- Import clean data
Skip step 3 and you’re gambling with your books’ accuracy.
Take 10 minutes to review properly now, or spend hours fixing errors later.
AI is a tool, not a replacement for human verification. Use it wisely.