Skip to main content

PwC - Request to Pay (RTP)

Client PricewaterhouseCoopers
Role UX Developer
Years 2018 - 2020
Financial Commerce SaaS UI

The Request to Pay application was a large-scale enterprise SaaS platform developed for PricewaterhouseCoopers to streamline end-to-end cash flow management across financial operations. Working as an embedded UX Developer across five cross-functional agile teams, the role demanded a balance between rapid sprint delivery and maintaining rigorous design consistency at scale - all within a complex Angular/Kendo UI environment where component decisions had downstream effects across the entire product.

Request to Pay Dashboard
PricewaterhouseCoopers Request to Pay homepage screenshot

Request It - Homepage & Dashboard

The Request It homepage was designed to orient users immediately - surfacing the two core actions (Track and Request) in a prominent right-rail, pairing them with at-a-glance procurement and invoice status counts so users could assess their workload before taking a single click. A welcome panel with embedded tutorial video addressed onboarding without interrupting the primary workflow. The entire UI was built on a custom Sass architecture created from scratch - establishing a scalable, component-driven foundation that maintained PwC brand consistency across the application while giving development teams a clean system to build on.

RTP Application - Detail View
PricewaterhouseCoopers Request to Pay detail view screenshot

Category Selection - Dropdown Autocomplete Search

The category selection step presented a unique technical challenge - embedding a live keyword autocomplete search bar inside an open dropdown component. As the user types, the list filters in real time against a taxonomy of procurement categories, surfacing suggested keywords before narrowing the full list below. Implementing typeahead behavior within a Kendo UI dropdown required careful management of focus, input events, and component state to prevent conflicts with the dropdown's own keyboard handling - a non-trivial interaction pattern that significantly improved category discoverability for users navigating a deep, unfamiliar taxonomy.

Request It FAQ Section
PricewaterhouseCoopers Request It FAQ section screenshot

Request It - FAQ & Resource Hub

The Request It resource hub consolidated everything a user might need into a single, quadrant-based layout - Application links, Policies, Training materials, and an FAQ accordion all living on the same screen without competing for attention. Each training video opens in its own modal, keeping users anchored to the page rather than bouncing them to an external player. The FAQ section uses a clean accordion pattern to surface answers on demand. Building the layout from scratch meant engineering each quadrant to meet accessibility standards independently - keyboard navigation, focus management, and ARIA roles all had to work correctly across four distinct interaction patterns on a single view.