Getting started
Sign in, upload your first statement, and see how the first pass of categorization happens.
Transaction Analyzer turns the statements your bank already gives you into a picture of where the money went — and lets you argue with that picture until it's right. There are no bank logins, nothing is linked to your accounts, and no one is paid to put anything in front of you.
This page walks the first fifteen minutes: sign in, load a statement, and understand what the app did to it.
Sign in
Sign-in is Google-only. There is no password to manage and no email-and-password form to fill in.
The first time you sign in, the app provisions your personal workspace — a private space that only you can reach — and seeds it with 24 starter categories: twenty spending categories (Groceries, Restaurants, Transportation, Utilities, Housing, and so on), Income, two transfer categories, and Savings & Investments.
It does not seed any rules. Rules that ship with the app would be guesses about a stranger's bank; the ones you end up with are derived from your own transactions on your first upload, and from there you own them. See Categories and rules for what that distinction means.
Upload your first statement
Download a CSV or PDF statement from your bank the way you normally would, then choose Upload statement from the Transactions screen. You can drop several files at once; each is limited to 5 MB.
Thirteen bank and card formats are recognized without any setup, plus Chase and Wells Fargo monthly PDF statements. If yours isn't one of them, the app asks you to map the columns once and then remembers — Uploading statements covers that path.
What happens next
The upload returns immediately and the work continues in the background. The capsule in the header names the stage it's on, and the upload screen shows the same thing per file:
- Uploading — the file's bytes are stored. This is the only part that needs your browser.
- Parsing — the file is matched to a format and read into transactions. Each transaction gets an id derived from its date, description, and amount, so re-uploading a statement you already loaded adds nothing.
- Categorizing — this is the first-pass categorization, and it only runs when there are transactions no rule covers. See below.
- Applying rules — every rule is re-checked against every affected transaction and the results are written down.
You can navigate away while this runs. The stages are tracked on the server, so closing the tab doesn't cancel anything.
How the first pass categorizes things
You start with categories and no rules, so on the first upload nearly everything is uncovered. The categorizing stage exists to fix that, and it works on merchants, not on individual charges.
Every description is reduced to a canonical merchant key first — SQ *BLUE BOTTLE COFFEE #4471 SEATTLE WA becomes something like BLUE BOTTLE COFFEE, with the payment processor, the store number, and the location stripped off. Charges that share a key are one merchant, and the app decides a category for the merchant rather than for each charge.
Each merchant is resolved in one of two ways:
- The built-in merchant list. A few hundred well-known national brands — Netflix, Chipotle, Walmart, Costco — ship with the app as a hand-written list of merchant keys and the category each belongs in. It is the same list for everyone, it is there on your very first upload, and nothing in it comes from anybody's transactions.
- A language model, for merchants the list doesn't know. It is asked to place the merchant into one of your existing categories, and only a confident answer is used. A pass may coin at most a handful of genuinely new categories, so your taxonomy doesn't fragment into two hundred one-off labels.
Confident results become rules — real, visible, editable rules that match on the merchant key. Merchants that stay unresolved are left uncategorized on purpose, because a wrong category quietly applied is worse than an honest gap.
The important part: nothing here is a hidden guess attached to a single charge. Every automatic decision is a rule sitting in your Categories screen with your name on it, and you can read it, change it, or delete it.
Look at what it did
Two places are worth the first visit:
- Categories — the rules the first pass created, grouped by the category they assign. Open one and you see exactly which transactions it currently accounts for. This is the fastest way to catch a rule that's too broad.
- The "To review" card on the Transactions screen — the transactions with no category, and any duplicate charges found by a scan. Uncategorized transactions is the page for working through it.
Fixing a category takes one of two forms, and it's worth knowing the difference from the start: setting the category on a single transaction is an override that applies to that row alone, while editing the rule changes everything that merchant ever charged you — past and future. Reviewing rules covers both.
Where to go next
- Categories and rules — the model underneath everything else.
- The Transactions screen — filters, charts, and the list they feed.
- Workspaces and households — sharing one set of books with someone else.