Search, filter, and bulk edit transactions
Use the main ledger efficiently when you need to find, review, or update more than one transaction.
Use filters before editing
The main transactions table supports server-backed filtering and pagination. Narrow the list first, then apply edits or bulk actions once the result set only shows what you mean to change.
Common workflows
- Search by description or merchant text.
- In the Category filter, search by category name or full path, such as
Home / Utilities. - Filter by account, category, spender, date range, or review state. The date filter includes the data-anchored
Last 3 monthspreset,All time, other quick presets shared with Dashboard and Reports, and a custom range when you need exact dates. - Use the consistent rectangular filter triggers in the ledger toolbar, then read the active scope from the status immediately below them. The table does not repeat those same filters in a separate summary panel.
- Sort when you need the newest, largest, or most unusual rows first.
- Move across pages when the matching result set is larger than the first screenful.
In category filters, selecting a parent includes all of its descendants. If you select only some children, the parent appears partly selected so you can see that the selection is mixed.
Bulk-edit safely
Bulk actions are most helpful after you confirm the filtered result set. Use them for one-off cleanup such as category changes, spender updates, deductible or tax-free income flags, or one-off flags. To change a category, expand the parent and assign a child (leaf) category.
If you are trying to automate the same change over and over, it is usually better to create a smart rule so future imports land correctly.
Transactions ignores dates stored by Dashboard, Budget, and Reports, so cleanup, category, import, review, and recurring links stay unfiltered unless their URL explicitly includes dates. Choosing All time records range=all in the URL and shared session scope; choosing another preset records its exact dates. If you need the broader decision queue, open the review inbox at /transactions?tab=review.
If the page resets to page 1
That is normal when you change filters or sorting. The transactions URL keeps page state in sync and intentionally clamps invalid pages after the result set changes.