CW-012 · Expense claims on mobile
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Priority P2 · Area mobile · Estimate M
The backend supports expense claims and the console can manage them, but the employee app cannot submit one — so the person holding the receipt has to wait until they are at a desk. Photographing a receipt is the obvious phone task.
Scope
Submit a claim with line items; attach photos from camera or gallery; track status; see what was reimbursed in which payslip.
Acceptance
A claim submitted on the phone appears in the console approval queue with its attachments intact.
Files mobile/lib/features/ (new expenses/)
Tracked in docs/backlog.md.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in mobile/lib/features/ and inspect nearby feature structure before creating the expenses area. Trace how the employee app handles submissions, attachments, status, and payslip data, then verify that a phone-submitted claim reaches the console approval queue with its receipt photos intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flutter
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100