# Page: Reprocessing and Sanctions

## Purpose

This page explains how administrators and investigators use reprocessing and sanctions workflows when reviewing or correcting fraud and AML events.

## Reprocessing

Reprocessing is used when a transaction or event needs to be evaluated again using updated logic, refreshed data, or corrected input.

### Typical reasons for reprocessing

- a rule or model was updated;
- a previously missed signal should be reviewed again;
- a transaction needs a fresh decision after a data correction.

### Example usage

Example: a new sanctions list becomes available, and the team wants to re-run a batch of historical transactions to verify whether they need to be flagged or blocked.

## Sanctions

Sanctions review is used to validate whether an entity, customer, or transaction matches known restricted or high-risk lists.

### What to review

- sanctions hit details;
- source country or region context;
- whether the case should be escalated or declined.

## Operational guidance

- use reprocessing for correction and refresh scenarios;
- use sanctions review for compliance and risk escalation;
- record the reason for any review action so the decision remains auditable.

## Notes

These workflows are especially important for compliance-sensitive investigations where the decision must be accurate and explainable.