Finance teams at enterprise companies were manually reconciling hundreds of batch transactions every day — cross-checking truncated ACH memos against invoice records, line by line, in spreadsheets. It was slow, error-prone, and completely disconnected from the procurement platforms where the work actually happened.

The Problem

Large enterprises use B2B procurement marketplaces like SAP Ariba to manage buying and selling at scale. But payment and reconciliation had never caught up. Sellers received batch ACH transfers with truncated memos — no invoice numbers, no line-item detail — leaving finance teams to manually guess which payment matched which invoice. Buyers, meanwhile, ran payout workflows in separate ERP systems, completely disconnected from the procurement flow.

The result: high error rates, delayed reconciliation cycles, and finance teams drowning in manual cleanup instead of strategic work.

My Role

JPMorgan Chase brought me in as the lead designer to define and build a digital wallet that could eliminate these friction points — embedded directly inside procurement workflows so neither buyers nor sellers had to leave the tools they already used. I led end-to-end: discovery research, user flows, system design, prototyping, and stakeholder alignment.

What We Did

Discovery Research

I interviewed 16 CFOs and finance directors across enterprise buyer and seller organizations. Two pain points emerged clearly:

• Sellers couldn't match incoming payments to invoices because ACH memos were truncated, and batch payments had no line-item breakdown.
• Buyers were forced to manage payouts in standalone ERP tools, manually re-entering data that already existed in their procurement system.

Solution Design

The design challenge was twofold: build something technically capable and ensure that both sides of the marketplace would actually adopt it. I designed the wallet to live inside Ariba — not as a separate tool — with four core capabilities:

• Real-time money movement to eliminate settlement delays and improve cash flow.
• Unlimited payment data attachment so every transaction carries full invoice-level detail — no more truncated memos.
• Near-perfect auto-reconciliation using unique transaction IDs to match payments to invoices automatically.
• Ledgering with sub-wallets so buyers and sellers could each manage customized transaction flows within the same infrastructure.

Critical User Journeys

I mapped and designed two end-to-end flows that covered the core use cases:

• Buyer pays a seller — payment is initiated within Ariba, full invoice data travels with the transaction, and reconciliation happens automatically on arrival.
• Seller receives a payment — full transaction details are visible in the dashboard, matched to the corresponding invoice; zero manual lookup required.

Stakeholder Alignment

Adoption required buy-in from finance teams, who were deeply reluctant to change workflows. Rather than presenting the solution abstractly, I used the user flow maps and prototype as a shared language — showing specifically how the wallet would reduce their daily reconciliation load and fit into the tools they already use.

Results

• Near-perfect reconciliation accuracy — payment matching errors dropped significantly in prototype testing, addressing the #1 seller pain point from research.
• Manual reconciliation eliminated — finance teams could stop the daily spreadsheet grind and redirect their time to higher-value work.
• SAP and JPMC system compatibility confirmed — the embedded approach proved viable within the existing enterprise infrastructure.
• $500M market opportunity identified for embedded payment solutions within B2B procurement marketplaces.

What I Learned

• Embedding beats adding. Every time we considered a standalone product, adoption friction multiplied. The wallet only became viable when it was invisible inside tools people already trusted.
• Both sides of a marketplace have to win. Designing only for sellers or only for buyers would have stalled adoption. The network effect requires both to see immediate value.
• Prototypes are negotiation tools. With skeptical finance leaders, showing a working flow of how reconciliation would look day-to-day was far more persuasive than any slide.