Approvals
Who can authorise what, and the record of who actually did.
An approval rule is a threshold, a category, and the people permitted at that level. Rules exist so that spending authority is a policy rather than a habit, and so that the record of who approved what survives the person who approved it.
Every approval carries a name, a time, and the state of the thing at the moment it was approved. Changing a bill after approval voids the approval rather than silently keeping it.
Where everything sits
How to work this page
Rules that require two approvals for every coffee get bypassed within a week. Set the threshold where the amount genuinely warrants a second pair of eyes.
The person who created a payment cannot be its only approver above your threshold. This is the single most effective control against internal fraud.
Anything waiting shows who it is waiting on and for how long. An approval sitting four days is a process problem, not a person problem.
Every approval, rejection, delegation and expiry is recorded permanently and cannot be edited.
On a phone
Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.
Questions people actually ask
Delegation for a period, recorded with both names. The approval shows it was made under delegation, so the trail stays honest.
Yes, by an administrator, and every bypass is reported. A control nobody can override in a genuine emergency gets disabled entirely, which is worse.