ARC Settlement / Section 02 of 05
Problem
Core Challenge
How do you modernize a financial compliance workflow that 200+ airlines and agencies depend on daily, without disrupting the precision and timing the industry requires?
A ticket moves through several stages before money changes hands. It's issued through a booking system, reaches ARC in a daily file, can be corrected by the agency during the current weekly cycle, and becomes settled when that cycle closes. Each stage lived in a different place, and the friction compounded at every level:
- Fragmented workflows
- Agents had the archive and the editing tool open side by side, cross-referenced document numbers by hand, and often resorted to screenshots or spreadsheets to reconcile mismatched data.
- Exchanges broke the trail
- An exchange or refund creates new documents. The ticket number a customer quotes might be settled history while the answer they want sits on a newer document in a different tool.
- UI debt
- Dense data tables, confusing labels, and cumbersome navigation reflected interfaces that hadn't evolved with user needs in over twenty years.
- Terminology misalignment
- Labels and status indicators meant different things across tools and teams, causing misinterpretation at points where errors had real financial consequences.
- Manual work behind the scenes
- Operations teams tracked incoming transaction files in spreadsheets, switched between many applications to troubleshoot errors, and often couldn't resolve an issue without waiting on another team.
- No culture of validation
- User-centered discovery had not been embedded in ARC's product process. Building that foundation was as much a part of the work as the UI itself.