Review Flagged Transactions
SCR-RECON-09 · Transaction Capture & Reconciliation
Scopedno Figma mapping
Layout
Give the user a dedicated place to resolve every transaction still flagged as uncertain, so unresolved issues don't silently sit in the transaction list lowering project accuracy.
States
- **Default**: list of flagged transactions with their flag reasons.
- **Detail open**: single transaction with reason (low confidence, possible duplicate, unusually high amount, outside project timeline) and resolution actions.
- **Resolved**: transaction removed from the flagged list once confirmed or excluded.
- **Unresolved**: transactions left as "needing further review" continue to reduce the project's financial confidence score.
Acceptance criteria
- Flagged transactions are visually distinct from confirmed items in the transaction list.
- Opening a flagged transaction shows the reason it was flagged (e.g. low confidence, possible duplicate, unusually high amount, outside project timeline).
- The user can resolve a flag by marking the transaction as confirmed, excluded, or needing further review.
- Unresolved flagged items reduce the project's financial confidence score.
Endpoints
None mapped yet — the backend agent will own these.