BILL
2026
Payment Remediation Framework
I designed a scalable self-service framework that enabled Accounts Payable teams to identify, understand, and resolve recoverable payment failures without contacting support. The experience brought together contextual guidance, embedded remediation workflows, and reusable interaction patterns across multiple payment exception types. By simplifying complex operational processes, I helped improve payment transparency, customer confidence, and operational efficiency.
Overview
Designing a reusable self-service framework for payment recovery.
I designed a scalable framework that enabled Accounts Payable teams to identify, understand, and resolve recoverable payment failures without contacting support. The solution unified multiple payment exception types into a consistent experience, improving transparency while establishing reusable patterns for future payment workflows.
Challenge
Distinguishing remediable payments and failed payments
When businesses send payments, failures happen for many reasons—an invalid bank account, insufficient funds, an outdated mailing address, or a debit block. Although these payments appear "failed," many can be recovered with a simple customer action.
Unfortunately, customers couldn't distinguish between recoverable and unrecoverable failures. Payments disappeared into support queues while Accounts Payable teams, vendors, and BILL agents worked together to identify what had gone wrong.
The result was thousands of avoidable support conversations every month.
Approach
One recovery framework supporting multiple payment failures.
Step 1 — Classify payment failures
Partnered with Engineering to map backend payment states into two meaningful customer-facing categories: Recoverable and Permanently Failed.
Step 2 — Differentiate visually
Introduced clear visual indicators throughout the payment list so users could immediately distinguish payments that required action from those that did not.
Step 3 — Reinforce awareness
Added a persistent banner and contextual entry points that surfaced recoverable payments at the top of the experience, ensuring actionable issues weren’t buried within large payment lists.
Step 4 — Guide users to resolution
Introduced a contextual Fix Now action that launched a reusable side drawer, guiding users through a consistent remediation workflow regardless of the underlying payment exception.
Solution
A unified experience for identifying, prioritizing, and resolving payment issues.
I designed an end-to-end recovery experience that surfaced actionable payment issues directly within existing Accounts Payable workflows. The solution combined a semantic status model, contextual notifications, priority indicators, and dynamic remediation flows that adapted to each payment type while maintaining a consistent interaction pattern across the platform.
Impact
Self-service reduced friction while creating a scalable platform capability.
The framework established a foundation for embedded payment recovery, shifting common remediation tasks from manual support toward self-service. It improved payment transparency, reduced operational complexity, and introduced reusable design patterns that could scale across future payment rails, exception types, and customer touchpoints.
Reflection
Great enterprise experiences simplify decisions, not complexity.
This project reinforced the importance of designing systems instead of isolated features. By building reusable patterns rather than one-off solutions, we created a framework that could evolve with the platform while helping customers confidently recover payments without understanding the complexity behind them.
