← Back to Projects

Financial Bank Reconciliation RPA with UiPath REFramework

Enterprise RPA solution automating bank statement reconciliation using UiPath Orchestrator, Dispatcher-Performer pattern, OCR, and Regex—achieving 96% time reduction and 81.8% ROI.

Financial Bank Reconciliation RPA with UiPath REFramework

Executive Summary

Enterprise RPA solution automating bank statement reconciliation using UiPath Orchestrator, Dispatcher-Performer pattern, OCR, and Regex—achieving 96% time reduction and 81.8% ROI.

Executive Summary

Bank reconciliation is a critical yet time-consuming process in finance operations. This project delivers a production-ready RPA solution using UiPath’s REFramework to automate the matching of bank transactions against ERP ledger entries.

The solution leverages the Dispatcher-Performer pattern with Orchestrator Queue management, processing PDF bank statements through OCR, extracting transaction data using sophisticated regex patterns, and performing both exact matching and fuzzy matching against a SQL Server database.

Result: 150+ ERP records across multiple payment scenarios, 100% match accuracy, 96% processing time reduction.


The Business Problem

Manual Reconciliation Pain Points

ChallengeImpact
Time-Intensive2-4 hours per bank statement
Error-Prone5-10% manual data entry errors
Delayed Close3-5 days for month-end reconciliation
ScalabilityCannot handle volume spikes
Audit RiskIncomplete paper trails

Current State Process

  1. Receive bank statement PDF via email
  2. Manual data entry from PDF to Excel (30 min)
  3. Open ERP system and search each transaction (10 min/item)
  4. Update status for matches, flag mismatches for review
  5. Generate reconciliation report (20 min)

Average Manual Time: 2.5 hours × 20 statements/month = 50 hours/month


Solution Architecture

Dispatcher-Performer Pattern

ComponentResponsibilityTechnology
DispatcherPDF → OCR → Regex Parsing → QueueUiPath, OCR, VB.NET Regex
Orchestrator QueueTransaction state managementUiPath Orchestrator
PerformerQueue Item → SQL Match → ERP UpdateREFramework, SQL Server

Why This Architecture?

  • Parallel Processing: 5 robots can process queue simultaneously
  • Failure Isolation: Dispatcher failure doesn’t affect in-flight transactions
  • Built-in Retry: Orchestrator handles system exception retries automatically
  • Audit Trail: Complete transaction history in Orchestrator

Matching Logic

Match TypeConditionAction
Exact MatchInvoice Number matches perfectlyUpdate ERP: “Matched”
Fuzzy MatchAmount within ±$30 toleranceUpdate ERP: “Fuzzy Match”
BATCHMultiple invoices = 1 bank paymentGroup matching by Batch_Group
SPLIT1 invoice = Multiple bank paymentsCumulative payment tracking
UnmatchedNo ERP record foundBusinessRuleException → Email Alert

Business Value & ROI

Cost-Benefit Analysis

Assumptions:

  • Monthly bank statements: 20
  • Average transactions/statement: 50
  • Finance staff rate: $35/hour
  • UiPath license: $10,000/year
MetricBefore (Manual)After (Automated)
Processing time/statement2.5 hours5 minutes
Monthly staff hours50 hours6.7 hours
Monthly labor cost$1,750$235
Error rate5-10%< 1%
Reconciliation cycle3-5 daysSame day

Annual ROI Calculation

ItemValue
Annual manual cost$21,000
Annual automated cost$12,820
Annual savings$8,180
ROI81.8%
Payback period14.7 months

Qualitative Benefits

  • Compliance: Complete audit trail in Orchestrator
  • Scalability: Queue-based architecture handles volume spikes
  • Accuracy: Eliminates manual data entry errors
  • Speed: Same-day reconciliation enables faster month-end close
  • Focus: Staff reviews only true exceptions, not routine matches

Results & Metrics

KPITargetAchieved
Match Accuracy> 95%100%
Processing Time Reduction> 90%96%
Error Rate Reduction> 80%90%
Exception Rate< 15%8%

Test Scenarios Validated

  • ✅ Standard 1:1 invoice matching (9 transactions)
  • ✅ Fuzzy matching with amount tolerance (2 transactions)
  • ✅ BATCH payment processing (3-to-1 matching)
  • ✅ SPLIT payment tracking (1-to-2 matching)
  • ✅ Exception handling for unmatched items

Skills Demonstrated

CategoryTechnologies
RPA PlatformUiPath Studio, REFramework, Orchestrator, Queue Management
Pattern DesignDispatcher-Performer, State Machine
ProgrammingVB.NET, Regular Expressions (Regex), LINQ
DatabaseSQL Server, Parameterized Queries, Transaction Management
Document ProcessingOCR Text Extraction, PDF Parsing
Finance DomainBank Reconciliation, ERP Systems, AP/AR Processing

Future Enhancements

EnhancementBusiness Impact
Machine LearningIntelligent fuzzy matching for complex edge cases
Power BI DashboardReal-time reconciliation status monitoring
Multi-Bank SupportTemplate-based approach for different bank formats
SAP API IntegrationDirect ERP integration eliminating database layer
Attended Bot ModeHuman-in-the-loop for exception handling

Technical Deep Dive

For detailed implementation including SQL queries, Mermaid decision flowcharts, REFramework configuration, and code examples, see the companion blog post:

👉 Bank Reconciliation RPA: Technical Implementation Guide

The 'BankRecon_Performer' workflow running within the REFramework state machine.
Figure 1: Utilizing the REFramework, the robot processes the transaction items. The logs highlight a success case where the logic correctly identified an Accounts Receivable (AR) entry and performed an 'Exact Match' linking Bank Reference DEP000001 to ERP Invoice DEP-240102.
The 'BankRecon_Dispatcher' workflow.
Figure 2: The robot ingests a raw bank statement PDF (Bank_Statement_Demo.pdf). The output logs confirm the successful extraction of 24 total transactions (14 debits/subtractions and 10 credits) ready to be added to the queue.
The Demo Cathay Bank Business Account Statement for the period of January 1–31, 2024.
Figure 3: The Demo Cathay Bank Business Account Statement for the period of January 1–31, 2024. Used as Source Bank Statement PDF. The document contains **14 Debits** and **10 Credits**. It is designed with specific edge cases to test the RPA solution, including **Split Payments** (e.g., Oracle License split between 01/22 & 01/25) and **Unknown/Mystery Items** (e.g., Unknown Vendor on 01/26 and Unknown Deposit on 01/25) to trigger business rule exceptions.

Project Info

Date
October 2025
Skills & Tools
UiPath REFramework Orchestrator SQL Server OCR Regex VB.NET Financial Automation