Billing & Invoice Management Tool

Executive Summary

UPS Capital — a financial services division of UPS offering insurance and billing products — needed to migrate their Billing & Invoice Management tool off the legacy Guidewire platform onto a modern, indigenous system. The goal was to separate UPS Capital's accounts from UPS's core systems, reduce licensing costs, and introduce new capabilities including multi-policy invoice and payment management.

6 min read

FigmaAdobe CC
ClientUPS CapitalDomainLogistics · Financial ServicesPlatformWebMy RoleProduct Designer & Design Team Lead
UPS Capital — Billing & Invoice Management Tool, final dashboard UI

UPS Capital — Billing & Invoice Management Tool, final dashboard UI

Context

01 — The Challenge

What we walked into.

Cost & ownership

Guidewire licensing was costly and tied UPS Capital's billing data to UPS's broader systems, limiting flexibility and increasing operational dependency.

Feature parity risk

The new tool had to replicate every essential Guidewire workflow before any new feature could be added, or finance teams would lose critical functionality on day one.

Scope expansion

Beyond migration, the business wanted entirely new capabilities: multi-policy invoice handling and consolidated payment management across accounts.

02 — My Role

End-to-end UX for the migration.

As Product Designer and design team lead, I owned the end-to-end UX for this migration. I led stakeholder workshops, conducted comprehensive user research across six distinct user roles, mapped the existing Guidewire workflows, defined the new information architecture, and delivered a complete design system spanning 348 screens — from initial discovery through final visual design and developer handoff.

03 — Research & Discovery

How we learned what mattered.

Research at a glance

4Workshop types run
6Stakeholder roles involved
36Use cases mapped
3User personas defined

Workshop methods

Discovery

Understand existing product, milestones and plans

Empathy

Prioritise user types and their needs

Design

Rapidly generate and discuss ideas with stakeholders

Prioritisation

Build consensus on highest-value features

Use case breakdown

35Total use cases
  • Existing use cases retained21 · 58.3%
  • Existing use cases updated5 · 16.7%
  • New features added9 · 25%
Existing 21 (58.3%)Updated 5 (16.7%)New 9 (25%)

Users we designed for

Accounts Payable ClerkProcesses invoices and manages vendor payments
Accounts Receivable ClerkTracks incoming payments and reconciles customer accounts
Senior Finance ManagerOversees financial operations and reporting compliance
Chief Financial OfficerSets financial strategy and reviews high-level performance
Operations ManagerManages day-to-day workflows across billing operations
Delinquency ManagerManages overdue accounts and collection strategy

User personas

Sarah Mitchell portrait

Sarah Mitchell

28

Accounts Payable Clerk (Admin User)

Responsibilities

  • Processing invoices
  • Managing vendor payments
  • Reconciling accounts

Pain points

Manual data entry errorsSlow invoice approvalsHard to track payment status

Goals

Automate invoice processingReduce payment errors
Linda Green portrait

Linda Green

45

Senior Finance Manager

Responsibilities

  • Overseeing financial operations
  • Ensuring policy compliance
  • Managing financial risk

Pain points

No real-time financial dataComplex report consolidationCross-department compliance gaps

Goals

Real-time financial insightsStreamlined reporting
Jessica Parker portrait

Jessica Parker

38

Delinquency Manager

Responsibilities

  • Managing overdue accounts
  • Coordinating with legal teams
  • Analyzing delinquency trends

Pain points

High volume of delinquenciesHard to collect overdue paymentsInadequate tracking tools

Goals

Reduce delinquency ratesBetter risk insights into delinquency trends
Heuristic & expert review — usability audit against NCPI and VIMM models
Heuristic & expert review — usability audit against NCPI and VIMM models

Expert review

Key findings from heuristic review

MC

Michael Chen

Sr. Business Analyst, UPS Capital Billing Ops

Error prevention · High

Add inline validation with specific recovery guidance before submission — especially on payment distribution forms where errors are costly to reverse.

PA

Priya Anand

QA Lead, UPS Capital Digital Platforms

Consistency & standards · Medium

Establish a shared component library so button placement, color coding, and terminology stay consistent across Manage Billing, Activities, and Account modules.

DF

David Foster

Operations Manager, Accounts Receivable

Interaction cost · Medium

Reduce click depth for frequent tasks — bring "Apply payment" actions directly into the account summary view instead of a separate page.

KW

Karen Whitfield

Customer Service Training Lead, UPS Capital

Visibility of status · Low

Add persistent loading and progress indicators during report generation and bulk actions, so frontline staff aren't left wondering if the system is responding.

Design work

04 — My Approach & Key Decisions

How the work came together.

01

Understand user needs

Stakeholder interviews, workshops with current Guidewire users, detailed personas.

02

Analyze current systems

Mapped existing Guidewire workflows, identified friction points, ensured feature parity before adding anything new.

03

Define new features

Gathered requirements with stakeholders, prioritized by user need and business goal, ran competitive analysis against industry tools.

04

Information architecture

Used card sorting with stakeholders to define navigation categories and hierarchy across the entire platform.

05

Prototype & visual design

Built high-fidelity interactive prototypes with a consistent, accessible design system.

06

User testing

Iterative feedback loops and usability testing with real users to validate every major workflow.

Key decisions

Feature parity before innovation

over launching new capabilities first, because finance teams couldn't afford to lose existing functionality during migration. We chose to fully replicate every essential Guidewire workflow before introducing new features.

Card-sorted information architecture

over a designer-led IA, because the platform spans 9+ functional areas (Invoices, Payor Management, Policy Management, Operations, Reporting, Security, and more) and needed buy-in across departments to be adopted.

Consistent component library

over ad-hoc screen design, because the scale of the platform — 348 screens — made consistency essential for both usability and long-term maintainability.

IA & flow diagram — full navigation hierarchy
IA & flow diagram — full navigation hierarchy
Task flow — Manage Billing & Direct Bill Payment
Task flow — Manage Billing & Direct Bill Payment
Recommended navigation — final structure
Recommended navigation — final structure
Component library — inputs, alerts, tables, calendars
Component library — inputs, alerts, tables, calendars

05 — Final UI Screens

The screens that shipped.

Customer search — account, payment, invoice, payor lookup
Customer search — account, payment, invoice, payor lookupUnified search across all account types with multi-field filtering
Activities dashboard
Activities dashboardAt-a-glance view of open activities, urgent items, and write-off approvals with live metrics
Direct bill payment — distribution view
Direct bill payment — distribution viewMulti-policy payment distribution with preview and apply workflow
Account details — overview, financials, policy periods
Account details — overview, financials, policy periodsConsolidated account view combining notes, financials, and a payment status breakdown chart
Impact

06 — Outcome & Impact

What it moved.

0UI Screens Delivered
0Use Cases Mapped
0User Personas
0Legacy Platform Replaced

Delivered a complete migration from Guidewire to an indigenous billing and invoice platform — preserving every critical workflow finance teams relied on while introducing multi-policy invoice and payment management. The new design system spans 348 screens across customer search, billing, payments, delinquencies, and administration, giving UPS Capital full ownership of their billing infrastructure.

07 — Reflection

What I'd do differently.

With a platform this large, I'd push to run usability testing on the core navigation structure earlier in the process — before committing to the full 348-screen build. Card sorting gave us stakeholder alignment, but validating it with end users at the same stage would have caught a few navigation depth issues we only found during later testing rounds.

Tools Used

FigmaAdobe CCMiroFigJam