DDovel Team
CockpitOverview & what needs youChatAsk the Product agentFigma SyncLive diff vs the PRDFeaturesEvery feature & its spec✓FlowsAI-inferred from the designsBacklogWhat's left to buildScreensPages, specs & criteriaRoadmapNew in Figma → proposalsDriftWhat changed in designMeetingsCalls → decisions → PRDTeamPeople + their AI support
Figma Dovel iQ v0.3 MVP (Active) · 2026-10-10
Dovel Team
PProduct agentsupports Design & PM✓BBackend agentsupports EchecomingFFrontend agentsupports the FE buildcomingQQA agentsupports QualitycomingOOrchestrator agentsupports Opscoming
Product / Transaction Capture & Reconciliation / Upload Expense Records

Upload Expense Records

SCR-RECON-06 · Transaction Capture & Reconciliation

Upload Expense Records
ScopedFigma 519:8950design drifted since last sync

Layout

Let a user without a live bank connection add actual spend by uploading a statement or expense records file, with extracted data reviewed before anything is confirmed.

States

- **Default**: empty upload control. - **Uploading**: in-progress state. - **Extracted, pending review**: transactions extracted from the file, awaiting confirm/exclude. - **Extraction failed**: retry, replace file, or switch to manual entry.

Acceptance criteria

  • The user can upload a file using the standard file upload flow.
  • After upload, extracted transactions appear for review before any are confirmed.
  • If the uploaded file overlaps with already-imported transactions, potential duplicates are flagged.
  • If extraction fails, the user can retry, replace the file, or switch to manual entry (SCR-RECON-07).
  • Extracted transactions are stored with source "uploaded statement" or "uploaded record".

Endpoints

None mapped yet — the backend agent will own these.

In flows

Upload or Manually Enter Expenses
P
Product agent
supports Design & PM
×