← muthari.com

Claim what was actually done

Muthari OS · the Project Operating System for Specialist Contractors

Commercial in Muthari OS claims what was actually done, for contractors who fabricate what they install. The BOQ is broken into zones for execution; when a zone’s quantities run past the BOQ line, a variation is raised and the zone breakdown freezes until it is approved — so the excess is caught before you install it for free. Approved variations and omissions produce a revised contract value that the claim header and the over-billing check both use. A progress claim is a grid of BOQ line by payment stage whose previous quantities are derived from the last invoice, never typed, so double-claiming is structurally impossible — and the goods receipts and work inspections behind each line ride with the claim as its evidence.

Budget that gates the claim

A category tree with an approval gate: no claim can be raised until the budget is approved, and the gate is re-checked after lock. Budget versus actual on three axes, where an actual nobody recorded shows as a dash — never as a green zero.

Cost that is written, not estimated

Actuals come from expenses (voided, never deleted), supplier invoices net of back-charges, and certified rework cost. Purchase-order commitments confront the material and subcontract budget and go red on the line when they exceed it.

Variations, remeasures, omissions

Quantity-excess variations with a freeze, an approval ladder and an audit trail; remeasured quantities and rates captured on the record. Omissions are negative variations with the sign carried through and the revised quantity clamped at zero. Base plus approved variations is the revised contract value.

Claims that derive their own history

BOQ × payment stage grid; previous quantities pulled from prior invoices and re-derived after lock. Value of work done, less advance recovery, less retention, plus VAT. Certification with due-date clocks, payments recorded against the certified amount, every revision kept and none wiped.

The payment application, styled

A payment-application workbook exported straight from the claim, filters honoured, ready to go to the consultant with the same numbers the system holds.

Honest limits: Muthari OS is not an ERP and holds no general ledger. There is no forecast final cost, no cash-flow view, no retention release ledger, and no invoice document generator — the workbook is the output. The over-contract check on a claim is a warning the approver sees, not a block. Variation quantities are currently valued in the claim at the BOQ rate, not the agreed variation rate. Labour and overhead actuals are typed expenses, not fed from elsewhere.

Next in the chain

The quantities a claim stands on come from Site; the commitments it is measured against come from Procurement. Muthari OS is built by contractors in the trade.

Book a free demo  See the whole system →