Why This Work Existed
This project followed the redesign of our internal F2 audit workflow. While that work focused on improving audit efficiency, it became clear that audit quality is shaped upstream by how invoices are created and submitted on mobile.
The goal was not to refresh a single screen. The work needed to ensure that what users submit integrates cleanly with newly designed audit systems and aligns with parallel efforts across the product to support a consistent in-app experience.
Designing for the Entire Workflow
Invoice uploading on mobile is not a single action. It spans creation, validation, review, submission, tracking, and often resubmission. Early work focused on mapping this full lifecycle rather than optimizing individual screens in isolation.
Mobile constraints required clear decisions about what users needed to complete immediately and what could wait. Interruptions, incomplete data, and return visits were treated as expected behavior rather than edge cases.
Designing for the Entire Workflow
Invoice uploading on mobile is not a single action. It spans creation, validation, review, submission, tracking, and often resubmission. Early work focused on mapping this full lifecycle rather than optimizing individual screens in isolation.
Mobile constraints required clear decisions about what users needed to complete immediately and what could wait. Interruptions, incomplete data, and return visits were treated as expected behavior rather than edge cases.
Reducing Input Without Losing Clarity
A core goal of the redesign was reducing manual input during invoice creation. Transcribed data from uploaded paperwork was used to prefill invoice details whenever possible, lowering effort and speeding up completion.
Because transcription is not always reliable, clear fallbacks were built into the flow. Each step distinguished what required attention from what was recommended, allowing users to understand and correct issues without second-guessing the system.
Feedback and Validation on Mobile
Invoice submission carries 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.
The overview highlights invoices needing attention through clearer hierarchy and visual prioritization.
Current State
This work is still in progress. Core flows for upload, validation, drafting, and submission are defined, with ongoing refinement as the broader platform evolves.
Future iterations will focus on deeper edge-case validation, performance improvements, and expanded reporting as real submission data becomes available.
Why This Matters
This project reflects how I approach mobile design when requirements are still forming. Start with real-world behavior, design for clarity over completeness, and build systems that can evolve without breaking downstream workflows.
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.