EnKash – Utility Payments Dashboard Redesign
Transforming Utility Payments into an Operational Control System
Role: Product Designer
Timeline: 4 Months
Scope: Utility Payments Dashboard + Platform UI System
Users: SMBs & Enterprises
Scale: 3,00,000+ monthly bills | ₹150–200 Cr monthly transactions
Ottawa, Ontario, Canada
2006
E-commerce
$1.578 billion (2019)
5,000+
Context
EnKash is a B2B fintech platform that enables businesses to manage payments, expenses, and financial operations through a unified system.
The Utility Payments module is one of the most critical workflows on the platform. Finance and operations teams use it daily to manage recurring bills across vendors and multiple locations.
The issue was not the ability to make payments.
The issue was the absence of a structured operational dashboard.
Users lacked:
Real-time visibility
Clean status tracking
Risk prioritization
Clear filtering logic
Obvious next actions
They were executing high-value transactions without operational clarity.
Results
Finance teams managing utility payments across locations were operating within cluttered, inconsistent interfaces that:
Overloaded them with undifferentiated data
Hid critical signals
Distributed actions across multiple layers
Increased hesitation in high-risk financial decisions
This resulted in:
Missed dues
Incorrect payments
Operational inefficiencies
Limited visibility into recurring spend
Core Insight:
Utility payments were not failing due to usability.
They were failing due to lack of decision support.
67%
Reduction in cognitive load
25%
Increase in user retention
68%
Reduction in user errors
Process
1. Audit & Identify Gaps
Reviewed the existing dashboard to find friction in hierarchy, filters, and actions.
2. Map User Workflow
Studied how finance teams manage bills and identified critical decision points.
3. Prioritize Information
Structured data into critical, informational, and historical to guide layout decisions.
4. Redesign & Simplify
Unified filters, clarified CTAs, reduced overload, and introduced clean hierarchy.
5. Build for Scale
Created consistent UI patterns and reusable components for long-term scalability.
“ This dashboard changed how we operate. It doesn’t just show data — it helps our finance teams act with confidence.”
CFO,
Enterprise Client
Conclusion
This was not just a UI redesign.
It was a shift from a transaction-heavy payment screen
to a decision-driven financial operations dashboard.
By introducing hierarchy, clarity, and system-level consistency, the utility module became a controlled and scalable operational layer for growing businesses.
