Rules & Merchants
Manage your merchant aliases. System merchants are read-only and can be copied into your personal merchant set. Changes apply on next analyze run.
Merchant detection runs during analyze and sets a normalized merchant value used across tables and reports. Matching order is: personal aliases first, then system aliases. Personal aliases always win.
| Mode | Behavior | Example |
|---|---|---|
| word | Whole-word boundary match (stricter). | rewe |
| contains | Substring match (broader). | amzn mktp |
Tip: Start with word aliases; use contains only when statement text is inconsistent.
When copied aliases already belong to another personal merchant, they are skipped and shown in Alias Conflict Queue.
Merchant edits are not retroactive. Existing analyzed transactions are not rewritten automatically.
Current calculations, charts/visualizations, reports, exports, and table results stay unchanged until you run analyze again.
Your Merchants (0)
Copied merchants can be renamed and tuned with aliases. Your merchants override system matching.
System Merchants (37)
Copy a system merchant to your personal set to override and customize independently.