---
name: transaction-investigation
description: Investigate a financial movement through bounded group or entity transaction queries without dumping the ledger.
---
# Transaction investigation
1. Confirm the date range, group or explicitly named entity scope, currency behavior, and the account, dimension, counterparty, description, or amount pattern to investigate.
2. Resolve group accounts with `list_group_accounts` and dimensions with `list_group_dimensions` plus `list_group_dimension_items` when needed.
3. Call `get_group_transactions_browse` for a group-wide investigation. Use `get_entity_transactions_browse` only for explicitly named legal entities.
4. Start with a grouped or pivoted summary when supported by the current tool schema.
5. Drill into raw rows only for the relevant group key, account, counterparty, or period.
6. Keep each row request date-bounded with a limit of 100 or less. Paginate only when completeness is required.
7. Reconcile the selected rows to the grouped amount before drawing a conclusion.
## Rules
- Do not fetch all transactions when a grouped result can answer the question.
- Do not invent group-by keys, account codes, dimension items, counterparty roles, or transaction types; use values supported by the current schema or returned data.
- Disclose filters, pagination, deleted-row behavior, dimensioned-row behavior, and currency conversion.
- Distinguish source descriptions from inferred business purpose.
- If evidence is inconclusive, say what remains unknown.
## Output
Return the investigation scope, a grouped summary, a short evidence table, reconciliation notes, and unanswered questions.
