All use cases
Bank reconciliation automation.
Every morning someone downloads the statements, matches them to the ledger and chases what doesn't agree. With Exekra, a Runner inside your network does the matching before the team arrives, and people decide only the lines that still don't match.
How it runs with Exekra.
How it is done today
- Download yesterday's statements from each bank portal
- Match thousands of lines to the ledger in a spreadsheet
- Chase the ones that don't match, one by one
- Prepare the daily report before the morning meeting
With Exekra
- 1Starts at six, before the team arrivesA schedule in the Hub, around your holiday calendar
- 2Reads the statement exportsExcel and file steps
- 3Matches each line to the ledgerRules built and tested in Studio
- 4Looks up what is missing in the bank portalBrowser steps, with a credential the Hub holds
- 5Hands what still doesn't match to a personA Hub worklist, with the evidence for each item
- 6Saves the reportTo the share the team already uses
Where people stay involved
The reconciliations team decides the exceptions. Everything they need is on the worklist item.
What could improve
- The report is ready when the team arrives
- Every exception has an owner and a due date
- Each run, and the hours it returned, is recorded in the Hub
On your own servers.
The automation is built and tested in Exekra Studio, then runs on a Runner inside your network, governed and measured in the Hub. The documents it handles, the credentials it uses and the record of every run stay on your machines.
How Exekra is deployed and securedWhere this process comes up
- Banking
- Insurance
- Telecommunications
- Finance and accounting