How the financial systems team at one of the world's most recognized humanitarian organizations chose Oracle APEX over the traditional Forms-and-Reports path — and grew one Collections application into a 20-plus-application modernization portfolio. A story we told together on stage at OAUG Ascend 2026.
Oracle E-Business Suite has been this organization's financial backbone since the late 1990s — today running release 12.2 on Oracle Database 19c, fully hosted on Oracle Cloud Infrastructure. A proven core, continuously evolving, carrying complex processes under tight mission-driven budgets and rigorous audit requirements.
The friction wasn't the core — it was how new capability got built around it. Every option carried a tax: Forms and Reports customizations accumulated over decades, OAF development where every change meant a full JDeveloper deployment cycle, or third-party tools eating license budget every year. As the team put it at the time: relying on JDeveloper for every minor change wasn't sustainable. And there was a real need on the table — a Collections capability the business simply didn't have.
Three options were considered: license Oracle Advanced Collections, build in OAF the traditional way — or try something new. Oracle APEX won on the criteria that mattered: zero additional licensing (it ships in the Oracle Database license already owned), zero new infrastructure, dramatically faster development, a modern mobile-ready experience, and one quiet superpower — APEX applications can serve people beyond EBS user accounts: internal teams, external customers, partners.
This is the part most modernization stories get wrong. Nothing was ripped out. Existing Forms kept running. Instead of rebuilding the old, the team built the new on APEX — extending what E-Business Suite could do, on a platform the organization already owned.
January 2022: a prototype built from Excel data. Weeks later: proof of concept approved. A focused two-to-three-month build followed, and by July 2022 the Collections application was in production — six months from technology decision to a live enterprise EBS extension. For this class of system, that speed changed what leadership believed was possible.
Collectors got a daily prioritized worklist, a workbench with every account's history in one place, and action-oriented tools — promise-to-pay, follow-ups, templated outreach. In the words of the accounts receivable leadership: a game changer, improving every aspect of collections activity.
That request marked the turn: expansion stopped being pushed and started being pulled. Over the next three and a half years the portfolio grew past twenty applications, portals, reports, and integrations — spanning accounts receivable and collections, expense and payment management, finance planning and analytics, and operations: an electronic invoicing portal, purchasing- and travel-card systems, wire payment processing, GL workflow, planning and supplier reporting, reconciliation tooling, even test-case management. As the IT leadership now describes it: any new request that comes in, the business straight away says — let us do it in APEX.
The portfolio's flagship is a customer-facing electronic invoice portal — external customers view and download invoices, make payments, and manage their own access, with receipts created in EBS through APIs. It runs on the OCI APEX Service against the EBS core, replaced a third-party SaaS product, and reached ROI within 24 months against the recurring fees it retired — leaving an owned, extensible platform instead of a rented one. Customer feedback: easier to use, faster to navigate than the platform it replaced.
The methodology now at the center of how AgilentPoint works everywhere — prove and pull — wasn't invented in a conference room. It emerged here, over three years: land one high-visibility application users touch daily, deliver it iteratively with users in the room, let business demand pull the next one, and expand across the Oracle environment as trust deepens. Production in weeks or months, not years; below-threshold pilots instead of procurement-heavy programs; no new licensing.
And the thesis held: the organization's systems weren't technical debt to escape — they were a foundation to extend. With AI-augmented development now delivering 30–50% productivity gains on APEX and PL/SQL, each step of that playbook runs faster than when this story began.
Including the honest parts — what was hard, what we'd do differently, and whether your environment fits the same pattern.
Start a conversation