Flows / Manage transactions & expenses / transaction-issues/not-assigned

transaction-issues/not-assigned

transaction-issues/not-assigned · Figma 7059:88919

Livebuilt in the frontendFigma 7059:88919

Frontend · Frontend agent owns this

Built in ph_projects → packages/ph_projects/lib/src/presentation/pages/project/transaction_issues_page.dart

Endpoints this screen calls · 4 endpoints, 0 confirmed in code · the Backend agent owns these

GET /transactions/inboxPOST /transactions/inbox/{ob_transaction_id}/confirmPOST /transactions/inbox/{ob_transaction_id}/dismissPOST /transactions/inbox/{ob_transaction_id}/split

Acceptance criteria · drafted by Product agent

User can review unassigned bank transactions in the inbox via GET /transactions/inbox, each showing amount, date, and counterparty.
User can confirm a transaction to assign it to the project, triggering POST /transactions/inbox/{ob_transaction_id}/confirm and removing it from the inbox list.
User can dismiss a transaction that is not project-related via POST /transactions/inbox/{ob_transaction_id}/dismiss, and it no longer appears in the inbox.
User can split a single bank transaction into multiple project expenses via POST /transactions/inbox/{ob_transaction_id}/split, allocating amounts that must sum to the original total (system validates this before allowing submit).

What's on the screen

—