The most expensive gap in facilities management is not between what was contracted and what was delivered. It is between what was delivered and what was paid. An organization may know a contractor missed three rounds and still release the full amount — because the link between the shortfall record and the payment item does not exist, or exists in a file one person reviews under time pressure.
Tracking contract financial items closes that gap by tying every payment to an operationally verifiable condition, instead of leaving it as a number in a spreadsheet approved on trust.
What Counts as a Financial Item?
A financial item is not simply the contract value. It is any defined financial obligation inside the contract carrying a condition or a date:
- Periodic payments — the monthly or quarterly amount for the core service
- Milestone payments — tied to completing a defined scope or activating a new site
- Retentions and guarantees — amounts held until contract end or the expiry of a warranty period
- Penalties and deductions — linked to recorded violations or shortfalls
- Variable items — unit-priced work whose quantity changes monthly
- Final settlements — at closure or early termination
The last three types generate most disputes, because they are the only ones whose value is not known in advance.
Why Spreadsheet Tracking Fails
A spreadsheet works well for fixed payments and collapses at the first variable item. Four reasons:
No link to the event. The spreadsheet records a deduction of a certain value but does not retain the link to the violation that produced it. When the contractor objects, a manual search through other files begins.
Multiple copies. One version with operations, another with finance, and updating one does not reach the other.
No history. The spreadsheet shows only the current state. Establishing who changed an item’s value, when and why becomes practically impossible.
Detached permissions. Anyone with edit access can change any figure leaving no trace.
Those last two are specifically what makes spreadsheet tracking unacceptable in any serious audit review.
The Correct Tracking Structure
A well-managed financial item inside the system carries six elements:
| Element | Purpose |
| Item type | Periodic, milestone, penalty, retention, variable |
| Value or calculation formula | Fixed, or tied to a quantity or percentage |
| Condition | What must be satisfied before entitlement |
| Timing | Due date or recurring cycle |
| Operational link | The related clause, violation or round |
| Item status | Due, on hold, approved, paid, disputed |
The fifth element is the heart of the matter. A financial item not linked to an operational record remains a number requiring manual justification at every review.
Linking Deductions to Violations
This is the most sensitive point, because it is where financial data intersects with a live contractual relationship. The practical rule:
Automatic deduction fits where the rule is stated in the contract with three components: violation definition, deduction value or percentage, and a ceiling per period. For example: repeated failure to complete a scheduled round, at a defined value per instance, capped at a set percentage of the monthly entitlement.
Proposed deduction fits better for discretionary cases — substandard delivery quality, or delayed response under exceptional circumstances. Here the system calculates and proposes, and an authorized approver confirms with a recorded reason.
Confusing the two causes most disputes: a discretionary deduction applied automatically appears arbitrary to the contractor, while a contractually specified deduction left to discretion loses its contractual force.
Retentions and Guarantees: The Forgotten Item
Retained amounts are the most frequently forgotten items, because they fall due months after contract end. Many organizations hold retentions on contracts that ended years ago without settlement, while others release them automatically without verifying that the warranty period has passed or that outstanding claims are settled.
The fix is simple: record every retention as a financial item with a release date and release condition, tied to an alert independent of the contract’s own lifecycle.
Alerts With a Direct Return
Three financial alerts save real money:
- Payment approaching due date — with enough lead time to reconcile before release rather than after
- Deduction ceiling approaching — when violations approach the agreed cap, an early signal of a fundamental performance problem rather than just another deduction
- Retention release date — presenting any outstanding claims before release
Governance and Permissions
Contract financial data is among the most sensitive information in an operations system. The essential controls:
Segregation of duties. Whoever logs the violation does not approve the deduction, and whoever approves the deduction does not release the payment.
Permissions by role, not by person. So approvals neither stall when staff change nor remain open after they move on.
A complete audit trail. Every change to an item’s value or status recorded with user, timestamp, previous value and reason.
Scope-limited visibility. A center supervisor sees the operational clauses relevant to their site without access to the contract’s full financial values.
How Masharef Supports Financial Item Tracking
The Masharef contract operations module tracks financial items and violations within the same module that manages operational contracts and their rounds — the connection that makes a deduction traceable to a documented operational record rather than a manually added figure.
User management controls roles and permissions through Microsoft Azure integration to implement the segregation of duties described above, while center management links items to their locations for per-center financial analysis. Instant reports and analytics with interactive notifications cover the follow-up and entitlement layer.
Conclusion
A defensible financial item is one that can be traced to a documented operational event. Once that holds, invoice review stops being a monthly negotiation and becomes a reconciliation procedure — which by itself returns days of operations and finance time every cycle.
Frequently Asked Questions
Should automatic deductions apply from the first month?
Better to run them in display-only mode during the first month: the system calculates and shows without applying. This exposes configuration errors and misread rules before they become a dispute with the contractor.
How should a disputed item be handled?
With a dedicated “disputed” status that freezes payment for that item without holding up the rest of the invoice, recording each party’s position and attachments. Freezing an entire invoice over one item damages the operational relationship unnecessarily.
Should penalties be capped monthly?
Yes, and the cap serves two purposes: it prevents a deduction becoming a disproportionate penalty that could be legally challenged, and it makes reaching the cap itself an indicator calling for a performance review rather than simply another deduction.
Who should see contract financial values?
A limited group: the contract owner, finance, and authorized management. Center supervisors need operational clauses and acceptance criteria to deliver and document, without access to financial values.