Set the context
Choose a fleet or customer.
Find the relevant invoices.
Making fleet invoice review easier to manage—from account selection to confident batch submission.

Fleet Account Managers need to move invoices forward while checking that the account, vehicle, details, and submission destination are correct. Their work spans multiple fleets and customers: finding records, reviewing and editing details, tracking statuses, and submitting invoices. Each step depends on keeping the right context visible.
I owned the UX/UI design of AutoNation Mobile Service’s fleet invoice workbench from requirements through the finished feature. The goal was a clear workflow that supported efficient processing and quality control. The workbench was tested and shipped.
How could I help managers move faster while keeping the details they needed to make an accurate decision? I treated speed and accuracy as connected goals. The interface needed to reduce the effort of finding and reviewing invoices while keeping account context and the scope of an action visible.
Choose a fleet or customer.
Find the relevant invoices.
Review invoice details.
Edit and select the right records.
Submit the selected invoices.
Check their statuses.
Moving an invoice forward means knowing whose records you’re reviewing, what needs attention, and what the next action will affect.
Workflow synthesized from stakeholder requirements and Jira tickets.Whose invoices am I reviewing?
What needs my attention?
What belongs in this batch?
Where will these invoices go?
One queue connects discovery,
review, and batch selection.
0203The fleet selector establishes context before records appear. This gives the review task a clear starting point.

The submission dialog brings the recipient and optional comments into focus before the manager confirms.

Each opportunity addresses a point where context or action scope can become unclear.
Requirements-based workflow framing, not interview findings. Original case-study screenshots; select any image to enlarge.
I explored multiple wireframe options for connecting account context, invoice discovery, and submission. The final workbench follows three stages of review.
I used AutoNation’s existing design library to create the workbench layout, building on the company’s established visual language while organizing account selection, invoice review, and batch submission into a connected workflow.
I no longer have access to the company’s design library, so I can’t show the library itself here.
Managers work across fleets and customers. I made fleet selection an entry point for narrowing the workbench before reviewing individual records. This connects invoice discovery to the account the manager is working on.

Before a manager can decide what to review, they need to know whose invoices they are looking at. I used fleet selection to establish that context first, so filtering and review could happen within a clearly defined account.
I used Ready, Needs Review, and Closed labels to distinguish invoice states. Filters narrow the queue, helping a manager move from a broad list to the records relevant to the task. The design combines a quick status scan with more precise invoice discovery.

A status answers “What needs attention?” A filter answers “Which records am I looking for?” I gave both a role in the workbench so managers could scan the queue, then narrow it to a specific task without losing the surrounding invoice details.
Checkboxes and a selected count make the batch visible. Before the final action, the submission dialog presents the recipient and optional comments. This gives the manager a checkpoint for reviewing which records will move forward and where they will go.

A batch action affects more than the invoice currently in focus. I made the selected count, recipient, and optional comments part of the submission flow so managers could review what they were sending and where it would go before confirming.
The fleet invoice workbench was tested and shipped. I owned its UX/UI design from the initial requirements through the finished feature, working with the Director of Design and project/product managers. I explored wireframe options and worked with stakeholders to develop the final workbench. Stakeholders chose to proceed without an interactive prototype. The shipped experience brings account selection, invoice discovery, status review, batch selection, and submission into a connected workflow.
THE PRODUCTION WORKBENCH · SELECT TO ENLARGE
Choose the account. The fleet selector narrows the invoice queue.
Confirm the batch. Selected invoices, recipient, and comments are reviewed before submission.
The central design principle was to keep account context and action scope visible. In an operational tool, a manager needs to understand both which records they are reviewing and what the next action will affect.
To evaluate the workbench’s impact, I would measure time to locate an invoice, accuracy of edits, batch-selection errors, and confidence before submission.