Help Topics
Register with Access Key Invite a Guest Enter Your PIN Navigation Menu
Upload Troubleshooting Fix Sign Problems Review Transactions
Submit a Support Ticket
Open System

Review Imported Transactions
Before You Add Them

The review screen is the moment between "the file was read" and "the transactions are saved." Nothing is final yet — which is exactly why this step matters so much.

Critical Step 8 min read Account Upload Center Review Screen
Understand why the review screen exists
Read the table like a statement, not a spreadsheet
Edit cells, add missing rows, remove duplicates
Only approve once the table is clean

Why This Step Matters

The system can read CSV, Excel, and PDF files very well — but this is still the stage where you are expected to confirm that the imported rows actually match your statement.

This is not a cosmetic check. It is a truth check. If you approve bad rows here, the rest of the workbook will faithfully report bad input. Garbage in, garbage out.

This screen exists so you can catch: missing rows, duplicated rows, sign mistakes, strange descriptions, wrong dates, and summary lines that do not belong.

Interactive Review Screen Demo

This is what the review screen looks like. Try clicking a description cell to edit it, removing the duplicate row, and approving the import when the table looks clean.

Review Imported Transactions
Date Description Amount
Jul 1 Grocery Store Purchase −$112.40
Jul 3 Monthly Salary +$3,200.00
Jul 3 Monthly Salary duplicate +$3,200.00
Jul 6 Coffee Shop −$6.50
Jul 9 Utility Bill −$88.00
Import approved — transactions written to the upload sheet.

9 Steps Through the Review Screen

1

Wait for the Review Screen to Open

After you choose the account, file type, account type, optional bank, and upload the file, the system reads the file and opens a review screen. Do not click away while it is loading.

2

Read the Table Like a Statement, Not a Spreadsheet

Look at the rows the way you would look at a bank or card statement: date, description, amount. Do not just glance at the row count and approve because it "looks about right."

3

Compare It to the Original Statement

Keep the original CSV, Excel, or PDF open while you review. As you compare, check:

  • Are all rows present?
  • Do any rows appear twice?
  • Are dates correct?
  • Are descriptions readable enough to recognize?
  • Are income and expense amounts behaving correctly?
4

Click Any Cell That Needs Fixing

The review table is editable. If something is wrong — a typo, wrong date, misread amount — click the cell and correct it before saving. Do not push bad data forward thinking you'll clean it up later.

5

Use Add Line If Something Is Missing

If the import missed a transaction entirely, use Add Line. This is the safe way to complete the review set. Use it for real missing rows only — not to create guesswork or duplicates.

6

Remove Rows That Do Not Belong

If the system pulled in a duplicate or a summary line that should not be imported, remove it at the review stage. This is far better than importing it and cleaning up the damage later.

7

Reverse All Signs If Everything Is Backward

If the whole table looks like the signs are reversed, use ± Reverse All Signs. Use this when the entire direction is wrong — not when only one single row is mistaken.

8

Do Not Click "Add These Transactions" Until the Table Is Clean

Nothing is saved until you click that button. This is your last safe checkpoint. If you are still unsure, pause. Fix missing lines, duplicate lines, and unreadable descriptions now.

9

Approve the Import

Once the review table matches the source statement closely enough to trust it, click Add These Transactions. Only then does the Upload Center write the batch into the upload sheet.

Completion Checklist

You know this stage is complete when all of these are true:

  • All rows look correct — none missing, none duplicated
  • Dates, descriptions, and amounts are believable
  • Missing lines were added manually
  • Bad lines and duplicates were removed
  • Sign direction is correct
  • You clicked "Add These Transactions" only after the table looked clean

Common Mistakes

Approving too quickly
This is the biggest one. The review screen exists for a reason. Even thirty seconds of real comparison against your source file catches most problems before they flow downstream.
Treating AI review as "probably fine"
The system is strong, but this checkpoint still exists for a reason. The AI reads the file; you confirm the result matches reality. Those are two different things.
Fixing structural issues later instead of now
Small problems are easiest to solve at the review stage. Once they flow into the system, cleaning them up requires far more work and creates risk of cascading errors in reports.

What Not to Do

  • Do not approve rows you already know are wrong.
  • Do not assume a PDF import is perfect without review.
  • Do not ignore sign problems thinking the account tab will magically fix them later.

"This step is where automation and human judgment work together. The system does the heavy lifting; you do the final truth check."

Related
Submit a Support Ticket Properly