TrackIt Getting started
Concepts
Accounts, sides, categories, rules, and what Other really means.
TrackIt is organized around a few sticky ideas. Once these click, the rest of the UI is mostly filters and shortcuts around the same model.
Building blocks
| Concept | Meaning |
|---|---|
| Account | Bank, savings, or credit card you import into (institution + name + number). |
| Transaction | Dated row with description, amount, category, tied to one account. |
| Debit side | Bank & Savings tab. Chequing and savings style activity. |
| Credit side | Credit Cards tab. Card purchases and payments. |
| Category | Lifestyle label (or Other). See Categories reference. |
| Rule / mapping | Normalized merchant pattern mapped to a category. |
| Agent | Chat that calls tools on your data (signed-in only). |
Debit vs credit sides
Analytics Debit and Credit spending cards follow the same split so card and bank spend do not get mashed into one confusing total.
Other
Other means TrackIt could not confidently categorize the row. It is a queue, not a real lifestyle category. Clear it with Needs review, dropdown suggestions, or Rules → Apply to Other.
Learned vs manual
- 1
Confirm
Override in import or table
- 2
Learn
Merchant mapping saved
- 3
Reuse
Future imports + Apply to Other
Manual edits are immediate on the row. Learned rules also shape future imports and bulk backfills. Guest learning stays local to the browser mock.
Learning side-effect