Daily closing is a simple procedure that prevents big problems: five minutes at the end of the workday reveals a difference that occurred today, instead of discovering it a month later when it is impossible to track it.
It is one of the clearest differences between a system designed for actual operation and another designed to record amounts.
The operational situation addressed by the topic
End of the day: There is a sum of cash in the fund, a sum in the network device, and operations in the payment gateway. What is required is to ensure that the sum of what was recorded in the system matches what actually arrived in each channel.
If there is a difference, it should be known today — not in a month’s review when no one remembers the details of a particular operation.
The requirements you write for the resource
- Breakdown by channel: Cash, network, transfer, and portal — all in one.
- Detailed by user: Who received what? The responsibility is individual, not collective.
- Refunds and Exemptions: Is shown separately, not silently deducted from the total.
- Difference Recording: A field to prove any difference, why, and who discovered it.
- Approval of lock: Authorized, with the next day’s transactions locked or any subsequent modification clearly recorded.
- Payment Gateway Matching: A per-process reference matches the gateway list.
- Lock register: Save for monthly review reference.
A practical example of testing the procedure
- Record receipts through different channels, then request the closing report: Are they separated?
- Perform a refund: is it shown separate or silently deducted from the total?
- Record a difference in the box: Is there a field to prove it and why?
- Approved the closing and then tried to modify today’s transaction: What happened?
- Request a log of locks for a week: Can it be reviewed?
Make locking a habit from the first day of operation, not a procedure added later. The team that has been used to it from the beginning implements it in minutes, while the team that is asked to do it after six months sees it as an imposed oversight burden — and the difference is in the application, not the procedure itself.
Controls and exceptions
- Closing is daily, not monthly: Postponing it makes tracking differences practically impossible.
- The difference is not an accusation: Recording it is a normal accounting procedure, and turning it into immediate accountability prompts employees to hide it — which is much worse.
- Separate validity: Whoever receives it is not the one who approves the closing, and this is an essential supervisory control.
- Branches: Independent locking of each branch and then grouping, no joint locking.
Next step for system review
Request a lock report template at the show and compare it to what you are using today. See Financial reporting page.
Request a system demo
We record receipts through different channels and close the day for you — by matching the channels, recording the differences, and authorizing approval.