Manage transactions & expenses
Record expenses and keep the transaction feed clean, assigned and deduplicated.
The user opens a transaction to review its details and spend-insight suggestions, drills into the scope category it belongs to, and adds paid expenses. They then work through the transaction-issues inbox — assigning unassigned transactions and resolving or dismissing duplicates.
8
screens
6
built
12
endpoints
Screen sequence · 8 steps · 🛖 Project
1. transaction-details/new
built3 states1 ep
2. transaction-details/suggestion
built2 states2 ep
3. scope-category
built1 ep
4. add-paid-expense
3 ep
5. transaction-issues/new
built2 states1 ep
6. transaction-issues/not-assigned
built4 ep
7. transaction-issues/duplicate
built2 ep
8. duplicate-transaction
2 ep
Endpoints across this flow
Flow endpoints · 12 endpoints, 4 confirmed in code · the Backend agent owns these
POST /projects/{project_id}/transactionsGET /projects/{project_id}/transactions/{transaction_id}POST /projects/{project_id}/transactions/{transaction_id}/categorizeGET /budget/catalogPOST /projects/{project_id}/transactions/receipt-scan/upload-and-analysePOST /projects/{project_id}/transactions/receipt-scan/{media_item_id}/confirmGET /projects/{project_id}/transactions/issuesGET /transactions/inboxPOST /transactions/inbox/{ob_transaction_id}/confirmPOST /transactions/inbox/{ob_transaction_id}/dismissPOST /transactions/inbox/{ob_transaction_id}/splitPOST /projects/{project_id}/transactions/{transaction_id}/resolve-duplicate