Objective
Refactor invoice IA and UX to allow for a more flexible, intuitive experience for customers to manage their invoices.
The legacy invoice system was actually referred to "Payment Requests." because it wasn't built to effectively manage customer balances and it couldn't accept partial payments. The experience to create an invoice wasn't intuitive or flexible.
Design Process
I approached invoices with the goal of creating a simple, modular experience.
The customer should be able to create invoices from different touch points throughout the app
Invoices should support comments, attaching documents, and linking objects like Weave appointments
Invoices should support multiple payments, including more complex payment types like Weave payment plans
The Final Product
The creation flow is in a side panel. This is consistent with other creation flows in the software and allows for invoices to be created from any point in the app without losing the current context.
The 'Collect Payment' modal doubles as the success modal when the invoice is first created. The customer can change the amount to run a partial charge and then select which payment method they want to use.
Including cash payments moves us one step closer to being able to operate as a payment ledger for our customers.
*Copyrights for these designs belong to Weave Communications, Inc