> ## Documentation Index
> Fetch the complete documentation index at: https://control-dev.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Keep transaction data current

> Understand synchronization behavior and resolve stale transactions or mismatches between statements and drilldowns.

# Keep transaction data current

Control synchronizes source-system changes so transactions, dimensions, drilldowns, and statement totals remain aligned. Use sync history and targeted transaction refreshes to distinguish an isolated stale record from a wider connection problem.

## What synchronization updates

A source system can change after an initial import. Depending on the connected source and supported data, later synchronization can pick up:

* newly created records;
* edits to existing transactions;
* deleted source records;
* changed dimensions or counterparties;
* records posted to an earlier period.

These changes can affect more than the transaction row. Mappings, statement drilldowns, dimension totals, and downstream outputs may need the refreshed data before they agree.

## Check data freshness

When a number appears stale:

1. Confirm that the expected record and value exist in the source system.
2. Review the connection's most recent sync status and completion time.
3. Confirm that the sync covers the affected entity and period.
4. Open the transaction in Control and compare its identifying fields with the source.
5. Check the statement or grouped transaction result after the synchronization completes.

Do not use a successful request start as evidence that data is current. Verify the completed sync status and the resulting financial value.

## Choose the appropriate refresh scope

| Situation                                      | Action                                                         |
| ---------------------------------------------- | -------------------------------------------------------------- |
| One known transaction is stale                 | Refresh that transaction from the grid or statement drilldown. |
| Several records from one period are missing    | Review and run the relevant source synchronization.            |
| A source connection reports an error           | Resolve the connection or authentication problem first.        |
| Transactions are current but grouping is wrong | Review account and dimension mappings.                         |
| An external workbook is stale                  | Verify upstream data, then run the relevant data output.       |

## Resolve a drilldown mismatch

If a statement value and its drilldown do not appear to agree:

1. Confirm both views use the same entity, period, dimension, and currency scope.
2. Wait for any active synchronization or recalculation to finish.
3. Check for late edits or deletions in the source system.
4. Review recently changed account or dimension mappings.
5. Refresh a single transaction only when the mismatch has been isolated to that record.

## Collect information for support

If the problem continues, record:

* the affected entity and connection;
* the source transaction identifier without credentials or sensitive attachments;
* the selected period, dimensions, and currency;
* the most recent sync completion time and status;
* the statement line or transaction view where the mismatch appears;
* the checks and refresh actions already attempted.

## Related content

* [Investigate transactions](/product-docs/transactions/investigate-transactions)
* [How financial data flows through Control](/product-docs/concepts/financial-data-flow)