The problem

• Numbers that depend on each other. One adjustment changes subtotals, taxes and totals, and users need to see the original next to the change.
• Invoices go to many clients at once. Each client needs its own summary type and recipients.
• No design layer in between. As the only designer, my files go straight to PMs, Product Owners and developers, so they have to be build-ready.

My role

Sole UI/UX designer. I own flows, prototypes and specs, and I review and approve UI decisions with product and engineering.

Key decisions

1. Original next to Adjusted.
   Pre-Bill charge-level adjustments show Original and Adjusted values side by side, with totals that cascade as you edit.
2. One modal direction for invoice adjustments.
   I set the modal pattern for invoice adjustments with product and engineering, so similar edits behave the same way.
3. Send to many clients without losing control.
   The Send Invoice to Client modal uses one scrollable card per client, with a Summary Type choice and To/CC toggles.
4. Allocation and time entry built for speed.
   Prototypes for the AR Allocations member tab and a time entry screen focused on fewer clicks for repeated daily tasks.

Impact

Billing staff can see what changed and why before an invoice goes out, and multi-client invoicing became one flow instead of several. Developers work from specs that answer edge cases up front.

Reflection

When you are the only designer, the spec is the conversation. Clear states and edge cases in the file save more time than any meeting.