Home · Solutions · Finance & accounting
Solution · Finance & accountingEvery morning the venue knows whether yesterday’s money adds up, and by how much it does not
Daily takings reconciled every morning
Each night a robot gathers three truths about yesterday: the till’s daily report, the terminal settlement and the sales from the booking or POS system, compares them with each other and with the bank inflows, and shows the differences in Teams in the morning with a hint where to look. Explaining stays with people; postponing it to Sunday ends.
Executive summary
A venue’s takings flow in three streams today: the till, the card terminal and the sales in a booking or POS system; each stream has its own report, and a human reconciles them, in practice once a week, from memory.
Each night the robot lines up the till’s daily report, the terminal settlement, the system’s sales and the bank inflows; matching days it closes silently, and differences it reports in the morning with specifics: day, shift, amount, likely spot.
Differences get explained the next day, while everyone remembers their shift, not on Sunday after a week; the owner stops being the after-hours auditor of his own firm.
daily till and terminal reports via export; sales from the booking system; inflows from the bank statement; a morning report in Microsoft Teams
Business problem
Three devices count the same day and each remembers it differently
A day at a leisure venue or restaurant ends with three reports: the till prints its daily summary, the terminal sends its settlement, and the booking or POS system holds its own sales total. In theory these are three photographs of the same day. In practice they differ by refunds, tips, payments split across two cards, an entry sold in the system but never rung up, and the other way round.
Reconciling these three truths falls to the owner or the manager, with a standing deadline: someday. In practice once a week, on Sunday evening, over a pile of printouts. After six days nobody remembers who processed Tuesday’s refund or why Wednesday’s drawer came up a hundred and twenty short. Differences get written off, because life is too short, and that writing off quietly becomes company policy.
In this mode small errors and small abuses look identical: like noise. Voids after a table is closed, refunds without a receipt, entries “on the notebook” drown in the weekly pile. The venue does not have an honesty problem; it has the problem that honesty cannot be confirmed, and that corrodes the atmosphere worse than any audit.
The bank adds a fourth truth: terminal inflows arrive in bulk and with a delay, so even a diligent owner cannot say whether Friday’s cards truly landed on Monday. Reconciling four sources daily is too much for a person and exactly right for a robot, which never gets bored.
How it works today
Below is what the work looks like before anything is automated.
- PersonClosing the day: the till report, the terminal settlement, the system total
- Risk of errorPrintouts land in a plastic sleeve; reconciliation waits for Sunday
- WaitingAfter six days nobody remembers refunds or who was on shift
- Risk of errorDifferences written off, because explaining costs more than the amount
- WaitingTerminal inflows arrive in bulk; nobody knows if they are complete
- Risk of errorThe owner plays auditor of his own firm on his free evenings
Why the current process costs more than it appears
The bill that never shows up in a budget.
- When did the till, terminal and system last agree to the penny, and how do you know?
- How many hours a week does reconciling printouts cost, and who pays them with their evening?
- How many differences did you write off this year because explaining after a week made no sense?
- Are terminal inflows checked day by day, or taken on faith?
Cost of inaction
The model assumes a venue with takings in the hundreds of thousands a year, converted to euros, and 0.3% lost in the noise of differences. The first month of daily reconciliation shows your own number; sometimes lower, sometimes more interesting.
The biggest line is not financial: suspicion. A team where differences cannot be explained lives on conjecture; a team where every difference has a date and an amount sleeps well.
A model organisation with realistic proportions – the numbers exist so you can run the same maths on your own data; they are not a client result.
A trampoline park with a café: a till, two card terminals, a booking system for entries and birthdays, cash and card takings, Microsoft 365. Reconciliation: Sunday evening, the owner.
Tuesday night, 3:10 am: the robot pulls the till’s daily report, both terminal settlements, the system’s sales and a fresh statement export.
Tuesday agrees to the penny at every joint; the robot closes the day without a word, adds a row to the monthly summary and that is that.
Wednesday: the till shows 180 less than the booking system. The robot points: two family entries sold in the system at 5:40 pm have no counterpart on the till; afternoon shift, a new cashier.
In the morning the manager asks; it turns out to be a training matter: the new person rang entries onto the wrong key. A correction and a note; the difference explained before lunch, after one day, not a week.
On Friday a terminal inflow lands short of the settlement by an unusual fee; the robot flags it, the bank confirms a rate change. In the modelled quarter, Sunday reconciling disappears from the owner’s calendar. These are model figures, not the venue’s records.
Proposed solution
The sources stay the ones you have: the till’s daily report, the terminal settlements and the sales from the booking or POS system, via exports or APIs, plus the bank statement. We replace nothing; the robot reads what these devices produce every night anyway and composes one picture of the day: cash, cards, recorded sales, inflows on the account.
The reconciliation logic is yours, written down once: what must match what, which deviations are normal (tips, fees, rounding), what counts as a difference to explain. Matching days close by themselves and build the monthly summary. Differences arrive in Teams in the morning with specifics: the day, the amount, the joint where it arose, the shift it concerns and a hint where to start.
Explaining remains people’s work, but it starts the next day, with memory fresh, not on Sunday after a week. Every difference gets a status: explained, training issue, written off by the owner’s decision, and stays in the register, so patterns show within a month: which shift, which joint, which menu item. The robot insinuates nothing and accuses nobody; it supplies amounts and dates, and the conclusions are yours.
UiPath Orchestrator: the nightly schedule, retries when an export is unavailable and an audit trail of every reconciliation; UiPath Integration Service connectors to SharePoint, Teams and Outlook 365
Nightly report collection, a reconciliation engine on your rules, a morning differences report with specifics, a differences register with statuses and a monthly summary for the accountant
The till, terminals and booking system via exports or APIs; the bank statement as CSV/MT940; no device replacement and no change to how shifts work
How the automated process works
- AutomationEach night the robot pulls the till, terminal, system and statement reports
- AutomationReconciliation by your rules: normal deviations sifted out
- SystemA matching day closes itself and adds a row to the summary
- AutomationA difference is reported in the morning in Teams: day, amount, joint, shift
- PersonA person explains it the next day, while everyone remembers their shift
- SystemThe differences register with statuses reveals patterns within a month
Human-in-the-loop model
Automation handles
- The nightly composition of till, terminals, system and statement into one picture
- Sifting out normal deviations and reporting the true differences each morning
- The differences register, statuses and the monthly summary for the accountant
People decide
- Explaining differences and talking to the shift; the robot supplies facts, not accusations
- Decisions to write off small differences and to set sensitivity thresholds
- The reconciliation rules: what must match what, set once and changed when needed
Before and after
Systems and integrations
The stack is short on purpose: one engine, one execution layer, one place where a person decides.
Inputs
- the till’s daily report via export
- the card terminal settlements
- sales from the booking or POS system
- the bank statement as a CSV/MT940 export
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- UiPath Action Center
Target systems
- a morning reconciliation report in Teams
- a differences register with statuses in SharePoint
- a monthly takings summary for the accountant
Human touchpoints: a morning glance at the report; explaining a difference with the shift; a monthly look at the patterns
Technologies used
the nightly schedule, retries, a trail of every reconciliation
Areports, the register and summaries where you look
Ayour thresholds, normal deviations and joints, written down once
Areports via exports or APIs; the devices stay as they are
Binflows and fees from the CSV/MT940 export; no account access
BIllustrative economic model
Numbers you can check against your own data.
The model assumes a mid-sized venue’s takings and 0.3% lost in today’s noise; how much truly comes back is shown by the first month, because only then does the noise get dates and amounts. Put your own figures into the calculator beside.
Run the maths on your data
An illustrative estimate based on your inputs. It models freed capacity, not promised savings.
Business benefits
- Every day closes in the morning with a verdict: matched, or a difference with specifics
- Explaining starts while the shift still remembers its day
- A training error, a device fault and an abuse stop looking identical
- Terminal inflows checked to the day and to the fee
- The accountant gets a monthly summary instead of a sleeve of printouts
The management view
- The owner stops auditing his own firm on Sunday evenings
- Trust in the team grows, because differences have dates and explanations, not conjecture
- Pricing and staffing decisions rest on takings that can be believed
Board-level KPIs
days closed as matched · time from difference to explanation · the sum of written-off differences · terminal inflows matching settlements · the owner’s hours spent reconciling
Security and governance
The automation has exactly the permissions it needs. Not one more.
- The robot reads device reports and the statement export; it has no access to the bank account or the till itself
- Reports speak of amounts, joints and shifts, not of persons; personnel conclusions belong to the owner
- Every reconciliation and every difference status is logged: who decided what, and when
- Takings data is visible only to the owner and the people he designates
- Data stays in your Microsoft 365 tenant; the robots run in the EU region of UiPath Automation Cloud
Why now
The season raises takings and transaction counts; the noise grows with them, and weekly reconciling stops catching anything.
Terminals and banks change fee rates more often than they used to; without daily checks the changes slip in unnoticed.
A quick-win deployment closes in weeks, because it reads the reports your devices already produce.
Relevant executive roles
Gets his Sunday evenings back and knows yesterday’s money adds up
Explains differences the next day with specifics instead of defending a week from memory
Receives a monthly summary and a differences register instead of a box of printouts
Common questions and objections
Almost certainly not. A daily report in any electronic form is enough: an export, a file, even a scan of the printout the robot can read. We settle the form during discovery; replacing the till is not a precondition.
No. The robot compares amounts between devices and points at the joints where the day does not close. It judges nobody and looks over nobody’s shoulder; what it gives the team is precious: differences stop being conjecture.
Usually yes, because franchise systems have reports and exports. The robot reads them like any other source; nothing in the franchisor’s system is changed.
When this is not the right solution
- One payment stream and a dozen transactions a day: the cash book suffices
- No electronic reports from the devices at all: first the exports, then the reconciling
- Expecting the robot to rule on who is at fault: it points at amounts and joints, not culprits
A question for the next management meeting
What is the sum of the takings differences we wrote off this year because explaining them a week late made no sense?
Implementation approach
Scope without ambiguity, before anything is signed.
We deliver
- Nightly collection of till, terminal, system and statement reports
- A reconciliation engine with your rules and sensitivity thresholds
- The morning report in Teams and a differences register with statuses
- A monthly takings and fees summary for the accountant
- Threshold calibration and two weeks of assistance after go-live
We need from you
- Access to the reports: till, terminals, booking system, the statement export
- Your rules: what must match what, and which deviations are normal
- Half an hour with today’s reconciler to walk one week back
Stages
Discovery
The money streams, device reports and today’s reconciling routine; half a day
Rules
Joints, thresholds, normal deviations, the morning report format
Build
Pulls, the reconciliation engine, reports, the register, summaries
Parallel run
Two weeks: the robot counts beside the Sunday ritual, you compare
Go-live
Sunday returns to the family; a threshold review after a month
A quick win. Most of the work is a one-off write-up of the rules and wiring of exports; after that reconciliation happens at night, with no people involved.
Thursday, 7:40 am, a Teams report: “Wednesday matched. Tuesday: a 180 difference, till versus system, afternoon shift.” Explained before lunch.
Pull last Saturday’s reports: the till, the terminal and the system, and try to tie them together. Send us the result of that attempt; we will send back reconciliation rules for your joints and the arithmetic of the recovered evenings.
Check your yesterdayThe neighbouring process usually has the same problem
On the fifth the accountant asks about missing invoices. The inbox hunt begins.
See the solution Management & planningThe owner’s morning report in one messageYesterday’s takings, today’s staffing, overdue payments. One message instead of three systems.
See the solution Finance & accountingGift vouchers sold and reconciledA voucher bought a year ago, printed twice, redeemed once. Probably. The register lives in three places.
See the solutionIndustries where we deploy this most oftenAesthetic medicineSmall business & services