Bank Reconciliation Automation with Azure, UiPath and Power Apps
Middle East aviation group
In short
How can bank reconciliation be automated while people keep control of every match?
Each day, the client's bank reconciliation team matched hundreds of transactions from two systems by hand, cleared them in SAP and chased owners by Outlook. The ERP's own matching rules were too limited, so the work, and the knowledge, sat with a few people. We built a daily cycle in which an Azure algorithm matches, a UiPath bot clears in SAP, and a Power Apps app keeps people in charge of every decision.
At a glance
- Hundreds of daily transactions matched by algorithm first
- SAP clearing handled by a UiPath bot
- Every open item assigned to an owner automatically
The client
The client is an aviation company in the Middle East that runs its finance on SAP. Its bank reconciliation team compares bank and ERP transactions every day and chases the teams and counterparties behind anything left open.
What it was costing them
- Time: hundreds of transactions a day were searched, matched and cleared by hand.
- Weak rules: the matching rules in the finance software were limited, so too little was matched automatically.
- Key-person risk: owners and counterparties were queried by Outlook, so progress depended on who knew whom.
- Scattered records: communication about open items lived in inboxes, not next to the transaction.
What we built
We automated the daily reconciliation cycle from data extract to SAP clearing and kept people in charge of the decisions.
- More matched automatically: a Python algorithm on Azure Databricks matches outstanding ERP and bank transactions daily, with data moved from SAP to Azure storage on a schedule.
- Trust through review: suggested matches arrive in a model-driven app where the team confirms, rejects or suggests its own match.
- No manual clearing: a UiPath bot clears the confirmed match groups in SAP at a scheduled time.
- Every open item has an owner: the algorithm adds a reason code and assigns a business owner based on it.
- Less chasing by email: bot notifications send suggested matches and open items to the right teams with a link to the app, plus daily and month-end reports.
- One record of communication: actions and comments on each item are stored in Dataverse.
Results
- The process runs as a scheduled cycle of ten steps, some automatic and some for people to confirm.
- The stated benefits were time savings, data quality, digital data access, better issue tracking and less dependency on individuals.
- Result: the clearest match types are cleared without a manual step, which removes most manual searching.
The risk most teams miss
The month-three risk is drift in matching quality. New vendors, new bank formats or changed SAP clearing rules lower the match rate, and a bot breaks when a SAP screen changes. Every match stays behind a human confirmation, reason codes make the rules easy to tune, and the bot writes a log for each processed item. We add a weekly match-rate view and a bot health alert.
What we would add today
Improvements we would add on top of what is live.
- Replace screen-driven SAP clearing with a supported integration where IT approves it, keeping the bot as a fallback.
- Read supplier replies and remittance documents with Azure Document Intelligence to close open items faster.
- Add a Copilot Studio agent so owners can ask for their oldest open items and update status in plain language.
- Deploy with Power Platform pipelines, connection references and a service principal, and keep SAP and UiPath credentials in Azure Key Vault.
Technology
Power Apps model-driven app, Dataverse, UiPath (Studio and Orchestrator), SAP, Python, Azure Databricks, Azure Storage and ETL services.
Tell us how many transactions your team matches by hand each day, and we will tell you how much of that a rule-based matching and review cycle can take over.
Products and capabilities
- Power Apps
- Dataverse
- Azure
- UiPath
- bank reconciliation
- SAP integration
- robotic process automation
- finance automation
The service behind this work
Power Platform development
Related use cases
FinanceBank Reconciliation Proof of Concept for Oracle
Matching bank transactions to finance records by hand costs time every day and ties the process to the people who know the rules. The client was moving to a new Oracle system and asked how reconciliation could work on it. We ran a short proof of concept on its own data.
Schools Division Integrated Planning in the Accountability Framework App
Each year, the schools division network of the client had to plan business, manpower and finances for all of its schools and centres, in separate spreadsheets that someone had to merge by hand. The cycle had a fixed calendar and a presidential review, so late or inconsistent plans cost real time. We added integrated planning to its existing Accountability Framework app.
- 30+
- schools on shared templates
- c. 90
- departments imported
Weighbridge Integration and Automated Invoicing for Quarries
At a quarry every load is weighed, but the weight often stops at the gate. When tickets are keyed in again for invoicing, bills go out late, mistakes slip in and stock figures lag behind what has left the site. We linked the weighbridge to invoicing and to a live view of reserves.
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.