Citi - Billing Intelligence
A source-safe Citi Velocity Billing Intelligence case showing phased requirements, role-based billing workflows, usage explainability, Data Manager linkage, and commercial-intelligence controls through a synthetic prototype.
Media Showcase
Media 1 / 12
MovieBilling Intelligence
Enterprise Billing Intelligence
Project Notes
Company
Citi
Role
Creative Director / Enterprise UX Architecture / Prototype Recreation
Focus
Enterprise Billing Intelligence
Skills
Billing UX / Commercial Intelligence / Creative Direction / Dashboard Design / Data Visualization / Enterprise UX / Entitlement Governance / Information Architecture / Payments UX / Source-safe Prototype / Subscription Management
What It Proves
Enterprise product thinking across billing operations, payment workflows, usage explainability, Data Manager linkage, entitlement governance, anomaly monitoring, and sales-ready commercial intelligence.
Technologies / Tech Stack
Prototype stack
These technologies describe the portfolio prototype, recreation, or presentation layer.
Product Workflows
Invoice review, payment, and dispute
A portfolio reconstruction of the client-admin workflow from the project requirements. Review leads to payment for an eligible invoice or a dispute routed to Billing Ops. Payment is unavailable while the invoice is disputed.
Problem
Enterprise billing work often separates invoices, payment operations, subscription changes, usage analytics, entitlements, alerts, and sales insight across multiple tools. The source material framed Billing Intelligence as a proactive layer that helps client teams understand cost, resolve invoice issues, manage payment controls, and connect usage behavior to Citi-side governance and commercial action.
Approach
01
Translate Phase 1 requirements into a usable foundation: invoice lists and detail drawers, pay-now and dispute flows, stored payment methods, autopay setup, client overview KPIs, Citi admin invoice controls, RBAC, and audit history.
02
Layer Phase 2 self-service and explainability into the experience through subscription management, usage analytics, proactive billing signals, multi-entity hierarchy support, and notification preferences.
03
Represent Phase 3 enterprise administration with Data Manager integration, minimum monthly fee policy logic, commercial intelligence, governance rules, anomaly monitoring, entitlement-to-billing linkage, and lightweight API billing signals that hand off operational health investigation to Data Manager.
Keep payment eligibility visible
The documented workflow makes invoice state part of the payment decision. An invoice under dispute remains unavailable for payment while Billing Ops reviews the issue. The interface needs to explain that state before a client starts a payment.
Make the dispute handoff explicit
Raising a dispute changes who acts next. The client needs to know that the issue has reached Billing Ops, while the reviewing team needs the invoice context and the reason for the dispute. This connects the client action to the operational work that follows.
Next route