Use the Account Upload Flow
One clean window. AI reads your statement, masks sensitive numbers, and hands you a table to approve. Nothing lands in your sheet until you say so.
If you remember the old way — pasting rows into a raw upload area, wrestling with an "Upload Type" dropdown, flipping a checkbox, then copying a "Finalized" block into your account tab — you can let all of that go. None of it exists anymore. The entire upload now happens inside one clean window, and the hardest part of reading your statement is handled for you.
When you bring in a file now, Money Mastery's AI reads it, quietly masks sensitive numbers like full card and account digits, sorts your transactions, and hands them to you in a simple table to look over before anything is saved. You're no longer the one deciphering your bank's messy export. You're the one giving it a final nod.
Step 1 — Open the Upload Window
From your Money Mastery navigation menu, open the upload tool. A window titled "Upload Your Bank Statement" appears. It may pause briefly on a "Loading Your Accounts" screen while it reads your workbook — that clears on its own.
Step 2 — Select Your Account
Choose the account this statement belongs to from the dropdown. This is the single most important click on the screen — it decides where your transactions land. Take the extra second if you have several accounts with similar names.
Step 7 — Let the AI Read It
A loading screen takes over. Keep the window open while it works — behind the scenes it's pulling out every transaction, masking full account and card digits for your privacy, and sorting everything into order.
Step 8 — Review Your Transactions
A screen titled "Review Your Transactions" appears with every transaction in a simple table — Date, Description, Amount — and a running count at the top. This screen is yours to correct before anything is saved. With your actual statement open beside you, check three things:
- Dates and descriptions read correctly — click any cell to fix a typo
- Amounts and signs are right — expenses negative, income positive. If every sign looks backward, click ± Reverse All Signs to flip them all at once
- Nothing's missing or doubled — use + Add Line for anything the AI missed, and the × at the end of a row to remove a duplicate
| Date | Description | Amount | |
|---|---|---|---|
| 01/03/2026 | Whole Foods Market | −$67.43 | |
| 01/07/2026 | −$34.99 | ||
| 01/10/2026 | Shell Station #4421 | −$52.10 | |
| 01/15/2026 | Direct Deposit — Employer | +$2,840.00 | |
| 01/18/2026 | Netflix | −$15.49 |
Step 9 — Approve and Save
When the table matches your statement, click ✓ Add These Transactions. A short saving screen runs, and then a success screen confirms how many transactions were added.
The note on the review screen — "AI can make mistakes" — isn't there to worry you. It's there because that review step is exactly what makes the automation safe. You always get the last word. Nothing is final until you click Add These Transactions.
What to Check When You're Done
- The success screen showed a transaction count that roughly matches your statement
- In your account tab, you can see the new block bracketed by a blue first row and a gold last row
- Expenses are negative and income is positive — no manual fixing needed
- Sensitive numbers (full card or account digits) do not appear in descriptions — the system masks them to the last four
A Few Things That Are Easy to Get Turned Around
-
Wrong account selected in Step 2This is the one worth slowing down for — it decides where everything lands. If a block of transactions shows up in the wrong tab, it's almost always this. Re-run the upload into the correct account.
-
Every sign looks backward on the review screenDon't edit them one at a time — that's what ± Reverse All Signs is for. It usually means Account Type (Step 4) was set to the opposite of what this account needs. One click fixes all of them.
-
PDF result looks messyPDFs are read by extraction and occasionally come out imperfect. The system itself will nudge you toward CSV/XLSX when it can — take that suggestion. A clean CSV almost always imports better.
-
The AI missed or duplicated a lineThat's exactly why the review screen exists. Add or remove the line right there before approving — the whole point is that nothing is final until you say so.