Problem: Mobile invoice submission was slow and error-prone, especially for drivers working under time pressure and unreliable connectivity.
Role: Senior UX Designer
Scope: Mobile invoice creation, validation, review, submission, drafts, and invoice history.
Outcome: Faster invoice submission, fewer errors, and improved confidence for users submitting invoices on the go.
Why This Work Existed
This work began as an effort to improve internal QA and auditing workflows, but it quickly surfaced a larger issue. Invoice submission on mobile wasn’t designed for how people actually use it.
Drivers were often creating invoices between stops, on unstable connections, or while multitasking. The existing experience assumed focus, time, and ideal conditions, none of which reflected reality. As a result, invoices took longer to submit, errors increased, and confidence in the process eroded.
Designing for the Entire Workflow
Invoice submission wasn’t a single moment; it was a workflow. Creation, validation, review, and submission often happened across short, interrupted sessions. Designing only for the final submit action would have ignored where most friction actually occurred.
Reducing Input Without Losing Clarity
Speed mattered, but not at the cost of confidence. Users needed to move quickly while still trusting that invoice details were correct.
Where possible, data was prefilled from uploaded paperwork. When attention was required, the interface made that clear without forcing users to re-enter everything manually.
Feedback and Validation on Mobile
Invoice submission carries a real financial impact, making feedback and validation critical throughout the experience. This included real-time validation, duplicate checks, and clear indicators for missing or problematic information.
Rather than deferring errors until the end, feedback appeared progressively through inline messaging, visual indicators, and review states. This helped users resolve issues early without feeling blocked or overwhelmed on a small screen.
Draft invoices can be selected or deselected to control what is included in a submission.
Attention is directed to the invoices that require action first.
Current State
This work is actively evolving. Core flows for upload, validation, drafting, and submission are in place, with refinements continuing as usage data and platform needs mature.
Future iterations will focus on edge-case handling, performance improvements, and deeper reporting as real-world submission patterns emerge.
Why This Matters
This project reflects how I approach mobile design when requirements are still taking shape. Start with real-world behavior, prioritize clarity over completeness, and design workflows that can evolve without breaking what comes next.
This workflow maps the end to end invoice submission flow, including validation paths and fallback states.
Functions and user needs were defined to guide scope, priorities, and workflow decisions.
Early wireframes explored invoice creation, file uploads, and editable details within a single mobile flow.
Autocomplete search speeds customer selection, while invoice details clearly reflect current status and next steps.