Returned Payment Automation Suite
Unified UiPath workflow handling 17 returned payment scenarios through configuration-driven architecture. A flag-based decision engine processes 25+ fields per account, enabling new scenarios via configuration changes rather than code modifications.
The Problem
Business Context
Operations team processing returned payments for fleet card accounts. Manual process required navigating a web portal to update account statuses, modify fields, and assign accounts to queues across multiple scenarios. Each account took 5-10 minutes, repeated hundreds of times daily.
The Manual Process
Pain Points
| Issue | Impact |
|---|---|
| Time-consuming | 5-10 minutes per account, 300-400 accounts daily |
| Error-prone | ~8% error rate from manual data entry and field selection |
| Training intensive | 2-3 weeks to train new staff on all 17 scenarios |
| Knowledge bottleneck | Only senior staff could handle complex scenarios |
| Scaling ceiling | Volume increases required proportional headcount |
Solution Architecture
The system uses a 4-layer architecture separating concerns: data ingestion, decision logic, portal automation, and audit logging. This design enables adding new scenarios by updating configuration flags rather than modifying workflow code.
Processing Workflow
Scenario Configuration
Each scenario code maps to a specific combination of decision flags. The table below shows 8 of the 17 production scenarios, organized by return type and complexity level.
| Code | Scenario Name | Fields | Complexity | Status |
|---|---|---|---|---|
| G | 1st Return - Standard | 15 | Base | Production |
| H | 2nd Return - Standard | 18 | Medium | Production |
| I | 1st Return - Prepay Convert | 20 | High | Production |
| J | 2nd Return - Prepay Convert | 22 | High | Production |
| K | 1st Return - Recourse | 17 | Medium | Production |
| L | 2nd Return - Recourse | 19 | Medium | Production |
| M | 1st Return - FLEET Queue | 16 | Medium | Production |
| N | 2nd Return - FLEET Queue | 18 | Medium | Production |
Decision Flags
| Flag | Description | Active In |
|---|---|---|
| SET_RETURN_NUMBER | Update return counter field | All |
| SET_COLLECTIONS_STATUS | Change status dropdown | All |
| LOCK_CREDIT_HOLD | Set credit hold checkbox | G, H, I, J |
| SET_LIMIT_METHOD | Configure limit calculation | I, J, K, L |
| ASSIGN_RETURNS_QUEUE | Route to returns processing | All |
| CHECK_FLEET_STATUS | FLEET vs non-FLEET routing | M, N |
| SET_DESCRIPTOR_DATE | Update descriptor timestamp | G, H, M, N |
| PRESERVE_CHECKBOXES | Maintain existing states | All |
| VALIDATE_AR_NUMBER | Verify account exists | All |
Results
| Metric | Before | After | Improvement |
|---|---|---|---|
| Processing Time | 5-10 minutes | ~45 seconds | 96% |
| Accuracy Rate | ~92% | 99%+ | +7% |
| Training Time | 2-3 weeks | Same day | 95% |
| Daily Capacity | ~50 accounts | 300+ accounts | 6x |
| Error Recovery | Manual restart | Auto-resume | Full |
Documentation Suite
The project includes a 4-document technical suite ensuring knowledge transfer and operational continuity. Documentation is treated as a deliverable, not an afterthought.
Interactive HTML Docs
Searchable reference with scenario lookup, field specifications, and troubleshooting guides. Dark/light theme support.
Bot Builder Matrix
Complete field specification matrix showing exactly which fields each scenario modifies.
Visual Workflow Reference
Step-by-step screenshots of each workflow phase with annotations.
Quick Start Guide
Single-page operational guide for daily use. Setup, execution, and common issues.
