transaction-issues/duplicate
transaction-issues/duplicate · Figma 7059:88956
Livebuilt in the frontendFigma
7059:88956Frontend · Frontend agent owns this
Built in
ph_projects → packages/ph_projects/lib/src/presentation/pages/project/transaction_issues_page.dartEndpoints this screen calls · 2 endpoints, 1 confirmed in code · the Backend agent owns these
GET /projects/{project_id}/transactions/issuesPOST /projects/{project_id}/transactions/{transaction_id}/resolve-duplicate
Acceptance criteria · drafted by Product agent
- User can see all flagged duplicate transactions via GET /projects/{project_id}/transactions/issues, with each duplicate group showing the transactions involved and their overlap (amount/date/counterparty).
- User can resolve a duplicate by choosing which transaction to keep, and on confirm the app calls POST /projects/{project_id}/transactions/{transaction_id}/resolve-duplicate and removes the resolved group from the issues list.
- System prevents resolving a duplicate group without an explicit keep/discard selection.
- After resolution, the issues list and counts refresh to reflect the remaining duplicates.
What's on the screen
—