Investigate transactions

Move from a statement value to raw, grouped, or pivoted transaction detail and isolate the cause of an unexpected amount.

Investigate transactions

Use the transactions browser to move from a reported value to its supporting records. You can inspect raw rows, group activity, pivot the result, and refine filters without leaving the investigation.

Start from the right context

Open transactions either directly or from a statement drilldown. A drilldown carries the relevant reporting context into the transaction view, which can include:

• entity or group scope;
• group or local account;
• reporting period;
• dimensions;
• currency context.

Before changing filters, note the starting total. This gives you a value to reconcile as the investigation becomes more specific.

Choose an investigation view

View	Use it when you need to…
Raw rows	Inspect individual transactions, dates, descriptions, and metadata.
Grouped	Summarize activity by an attribute such as account or counterparty.
Pivoted	Compare one attribute across another, such as entity across period.

Server-side pagination and aggregation allow grouped and pivoted analysis to work with larger transaction sets. A displayed page of rows may therefore be only part of the full filtered result; use the view’s aggregate totals when reconciling the complete scope.

Narrow an unexpected value

Change one dimension of the investigation at a time:

1. Confirm the period and entity scope.
2. Group by account to find the accounts contributing to the value.
3. Group or pivot by dimension to identify the business slice responsible for the movement.
4. Filter by counterparty when the question concerns a customer, supplier, or related party.
5. Return to raw rows to inspect the exact records behind the remaining total.

Keep track of whether each filter includes or excludes values without a mapping. An apparently missing total can come from a scope mismatch rather than missing source data.

Refresh one transaction

If one record appears stale, refresh that transaction from the transaction interface or the statement drilldown. A single-record refresh is intended for an isolated issue and avoids running a wider synchronization.

After refreshing:

1. Confirm that the transaction reflects the expected source state.
2. Re-run or reopen the relevant grouped view.
3. Return to the statement and verify that the drilldown and displayed total remain aligned.

If several transactions are missing or stale, investigate the source connection and synchronization state instead of refreshing records individually.

Common investigation patterns

Question	Useful first view
Which entity explains the group movement?	Pivot by entity.
Which accounts make up this statement row?	Group by account.
Why did a cost center change?	Filter the dimension, then group by account or counterparty.
Does one source record look stale?	Open raw rows and refresh the individual transaction.
Why does a drilldown differ from a report?	Recheck period, entity, dimensions, currency, and data freshness.

Verify the conclusion

An investigation is complete when the filtered transaction total reconciles to the value you started from and the contributing records explain the business event. Record the relevant scope and filters when sharing the conclusion with another reviewer.

Related content

• Build and review financial statements
• How financial data flows through Control
• Keep transaction data current