Every decision carries a name, a time — and a fingerprint of the figures approved
This is the layer that separates a system that records from a system you can rely on. Every approval has a chain, and every approved report carries a seal with a verification code and a fingerprint of the figures — so if the numbers change after approval, that shows instead of slipping through.
The questions it answers
The questions asked at the moment of a problem — and they need a written answer.
"Who approved this?"
The approval chain is stored with each approver’s name and timestamp — and the printed report carries their seal.
"Was the figure this at the time of approval?"
The seal holds a fingerprint of the figures. If they changed afterwards, the system states that the approved version no longer matches the current one.
"Who can see payroll?"
Permissions are per screen and enforced in the database itself — a user without permission cannot reach the data even from outside the screen.
"Who edited this invoice?"
The activity log records who, when, which row, and what changed.
What is inside
The layer that protects the numbers.
How it connects to the rest
No module works alone. These are the links that keep the numbers consistent.
Every module
Any document involving money passes an approval chain — so this layer runs across the whole system.
Finance
An approved entry is locked, and a closed period takes no backdated entry.
Payroll
A run does not reach the bank before it is approved.
Notifications
Whoever owes an approval is alerted — so a request does not sit a week in someone’s inbox.
No trial works without this layer
In the trial we set up the approval chains with their thresholds, and you see a sealed report with its verification code.