Search the full matching dataset
Use the grid search for references, descriptions, counterparties, nominal names/codes and other supported fields. A page showing 50 or 100 rows is a viewing window, not necessarily the whole dataset.
Filter before bulk action
Apply status, type and date filters first, then review the resulting set before selecting rows. “Select visible” should mean the visible/matching selection intended by the screen, not every transaction ever imported.
Shape the grid to the job
Use show/hide, reorder and resize controls to keep the columns relevant to your task visible. Where preferences are persisted, use a sensible practice layout rather than constantly rebuilding it.
Row actions and same-screen editing
Use the row action menu or same-screen modal for supported edits so you retain context. Hover/drill-down should show the double-entry or source relationship where available.
High-volume behaviour
For very large bank/source datasets, filtering and search should remain server-backed. If the screen becomes slow, capture the client, module, row count and filter/search used when reporting the issue.