Searchable Receipt Wallet
Design a receipt organizer that accepts store-issued and photographed receipts, then makes returns, warranties, and expenses easy to find.
The brief
Understand the problem
Background
Receipts arrive on paper, by email, and through retailer accounts. Important return dates and warranties are easy to miss, while automated extraction can misread totals or merchant names.
User context
Grace buys equipment for freelance work and needs reliable records for returns and tax reporting. She wants to capture a receipt in seconds, then correct any mistakes later.
Product problem
The system must merge multiple receipt sources, expose extraction uncertainty, and keep sensitive purchase history private and searchable.
Objective
Design receipt capture, review, organization, and retrieval for a personal receipt wallet.
What to design
Define the experience
Required experience
- Paper receipt capture
- Extracted detail review
- Search and filter
- Return or warranty reminder
Screens and states
- Receipt inbox
- Camera capture and crop
- Receipt detail
- Search results
Core user flow
Follow the critical path
- 01
Grace photographs a receipt
- 02
The service extracts merchant, date, total, and items
- 03
She corrects one uncertain line
- 04
She tags the purchase and schedules a return reminder
Product rules
Requirements and constraints
Requirements
- Identify the source of each receipt
- Mark uncertain extracted values
- Prevent duplicate imports
- Support categories, notes, and document export
- Show relevant return and warranty dates
Constraints
- Receipts can be faded or crumpled
- Store integrations may deliver delayed copies
- Financial records require secure access
Reality check
States worth considering
Ready-to-use content
Mock data
Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.
Receipt details
- Northline Office Supply
- 14 September 2026 at 16:22
- USB microphone, $84.00
- Return eligible until 14 October
- Extraction confidence: merchant name needs review
Finish line
What to deliver
- Four responsive screens
- A review state for uncertain extracted data
If you want more
Optional extensions
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Theory to review
UX principles for this brief
Use these as decision lenses, then validate the design with the people and context in the brief.
