Layer 01 · Foundation
Duplicate customers. A fragile billing integration. The foundation needed a rebuild.
Leading Product Analytics Platform · Financial Systems
The Client
A product analytics platform, scaling its financial core
A leading product experience and analytics platform was scaling fast: consolidating its integration tooling onto Workato and migrating its financial systems to Workday. The Workday–Stripe billing flow sat squarely in the critical path of that move. Every customer record and every invoice payment ran through it.
The Challenge
The root cause was architectural, not operational
Like many fast-growing companies, the platform's Workday-Stripe integration had been built early and iteratively, and the engineers who built it had since moved on. Documentation never caught up. By the time the team brought us in, duplicate customer records were accumulating in Workday, task consumption was climbing, and every troubleshooting session started from zero because the integration's behavior wasn't written down anywhere.
The root cause was that the integration ran a bi-directional sync, allowing Stripe to write back to Workday. Workday was not the source of truth. On top of that, the recipes were monolithic: a change to one part risked breaking everything else.
Our Approach
Re-architect from scratch. No patches on a broken foundation.
We started with a full review before writing a single line of code. That review surfaced the bi-directional sync as the primary culprit. We mapped every data flow, documented the business rules the integration was trying to enforce, and identified three core workflows: customer sync, invoice payment link generation, and payment application.
We built each as a standalone modular recipe. We also found that the standard Stripe connector was inefficient for their volume, so we built a custom SDK with batch processing.
The Architecture
Three workflows. One direction of truth.
Customer and invoice data flow one way, from Workday to Stripe. Only completed payments flow back, applied automatically against the right invoice.
Design Principles
Workday as the single source of truth
Data flows to Stripe. Stripe does not write back. This eliminated duplicate creation at the architectural level.
Three modular recipes
Replaced a monolithic flow with three specialized recipes. Changes to one recipe do not touch the others.
Custom Stripe SDK
Batch processing reduced task consumption and API calls significantly. The SDK uses dynamic methods for easy extension.
Governance and transparency layer
Comprehensive logging, Slack error notifications, and full documentation including Mermaid flow diagrams.
The Results
Live since May 2025. Billing runs itself.
The re-architected integration went live in May 2025. With Workday established as the single source of truth, the duplicate-record problem ended at the architectural level: zero duplicate customer records since launch, a 21% reduction in Workato task consumption from the batch-processing SDK, and an estimated $58.4k in annual operational savings.
Invoice adjustments handle themselves. When an invoice amount changes in Workday, the integration automatically regenerates the Stripe payment link and deactivates the old one. No manual cleanup, no stale links reaching customers.
International payments process correctly. Transaction currency is handled accurately across regions, so global invoices flow through the same automated path as domestic ones.
Reconciliation got simpler. Invoice and customer metadata sync to Stripe, which means customers receive clear receipts and finance matches payments to invoices without detective work.
It is the same documented, modular standard we bring to every integration engagement.
"We had a great experience with OneSolve revising one of our Workday integrations. They drastically simplified our recipes and troubleshot several roadblocks we faced along the way."
Financial Systems Leader · Product analytics platform
Technology
Have an integration that nobody trusts?
Bring us the fragile recipe or the sync that keeps creating duplicates. We will show you what a documented, modular, production version looks like in a 30-minute working session.