Costs attach to the work order as lines: invoices, labour and materials, approved, posted, and rolled up by building and by trade. Labour is valued at the rate in force when the hours were logged and is never re-priced afterwards, and when somebody changes a recorded cost, Prova logs an official correction instead of overwriting the original entry. Spending limits are defined at multiple levels and across different currencies, with approvals climbing the requester’s reporting line and falling back to the designated approver above the building, then to the owner. Consolidated expenditure reports can be pulled by site or by period with the invoices still attached.
A number that can be changed without trace is a number nobody trusts. Correction logging is what allows a finance team to accept operational cost data without re-keying it, and it is the difference between a spend report and an auditable one. On the control side, delegated authority written into a policy document is not enforced, while delegated authority built into the approval path is. The escalation fallback is the practical part, because most approval systems fail on absence rather than on policy, and a request stuck behind one manager on leave is how people learn to work around the system.
In practice
A repair quoted at 2,400 euro invoices at 3,150, and the site manager cannot approve the difference.
Finance accepts the figures without re-keying them, because every number can be traced and every change left a mark. The pattern is visible too: three of five air handling repairs this year came in above quote, all from the same contractor. One invoice at a time, that looks like nothing.
Illustrative walkthrough. Not a customer record.
Next step
Thirty minutes on your own estate: your buildings, your obligations and your numbers. We will show you where the time and the money are going.
Book a demo