Cost Control and Payment Applications: Knowing the Real Margin on Every Project

- 1.Where Contracting and Maintenance Companies Lose Their Profit
- 2.Work Orders: From WhatsApp Messages to a System That Tracks Every Request
- 3.Scheduling Field Teams and Dispatching Visits
- 4.Preventive Maintenance: From Fixing Breakdowns to a Schedule That Prevents Them
- 5.Cost Control and Payment Applications: Knowing the Real Margin on Every Project (you are here)
- 6.Spare Parts and Inventory Across Sites and Technician Vans
- 7.The Manager's Dashboard: The Indicators You Actually Run Operations On
Cost Control and Payment Applications: Knowing the Real Margin on Every Project
The previous parts built disciplined operations: a request that enters through one channel carrying a number, an owner and a clock; a visit dispatched to the right technician with the right part; a preventive plan that generates its own work orders. All of that makes a company faster and less chaotic, but none of it answers the question that decides survival rather than efficiency: does this work make money?
Most contracting and maintenance companies know exactly one number — the full-year result in the financial statements. The problem is that this number is an average, and averages hide more than they show. A company profitable in total can be bleeding on three contracts covered by one excellent one. And as long as nobody knows which contract earns and which drains, the company will renew the contract that eats it with enthusiasm and haggle over the one that feeds it.
The job number: the container everything lands in
Cost control starts with something simpler than most people expect: every project or contract has one number, and that number is a mandatory field on every transaction that costs the company money. A labour hour, a part issued, a subcontractor invoice, equipment rental, a crew's travel to an out-of-town site. If the entry carries no job number it becomes a general expense — and general expenses are where losses go to disappear.
Three rules make that number work instead of becoming a field filled in at random:
- Open it at contract signature or award, not a month into execution. Anything spent before it exists lands somewhere wrong and never comes back.
- Give it levels that follow the shape of the work: contract, then site or building, then work order. Cost is recorded at the finest level and rolls up, because rolling up is easy and breaking down is impossible.
- Close it at final handover and release of retention, not on the last day of site work. Projects keep costing money during the warranty period, and that cost belongs to the project itself — not to this year's new job.
The four cost streams, and where each one comes from
Real project cost is made of four flows, each with an operational source we built in the earlier parts:
- Labour hours. Sourced from work orders and attendance, not from a site manager's monthly estimate. The most common error here is calculating the hourly rate from basic salary alone. A loaded hourly cost includes salary, allowances, GOSI contributions, accommodation, transport and medical insurance — divided by hours actually productive, not by contracted hours, because travel, waiting and leave are part of the cost your price has to cover.
- Parts and materials. Issued against the work order itself rather than out of the warehouse in general, so the value lands on the right project at the moment of issue. That is the subject of the next part, because it is the biggest single hole in this sector.
- Subcontractors. A purchase or award order tied to the job number, then subcontractor payment applications approved against documented completed work. Tracking their output with the same discipline as your own crews is not bureaucracy: their delay shows up in your schedule and their shortfall shows up in your commitment to the client.
- Direct expenses. Equipment rental, transport, permits, temporary accommodation, site petty cash. This is the line most often recorded with no job number, because it is spent quickly in small scattered amounts that look immaterial until they are added up at the end of the contract.
That leaves a fifth line that ruins reports more than it improves them if you rush it: indirect costs — management, office, supervision, vehicles. Allocating them across projects is theoretically more accurate, but only if the allocation basis is written down and agreed internally before the first report is issued. Without a fixed basis, every review meeting turns into an argument about the method instead of a conversation about performance. The practical start is to get direct costs right, read contribution margin per project, and add allocation later.
Compared to what: the bill of quantities and the contract value
Cost on its own is a number without meaning. Meaning comes from comparing it to what was sold: the bill of quantities in contracting projects, the annual contract value and included visit count in maintenance agreements. Once those values sit in the system as a baseline, three comparisons become available daily instead of at handover:
- Planned versus executed quantities per line, showing where execution has overrun what was actually priced.
- Estimated versus actual cost per line, telling you whether the problem is in pricing or in execution. That distinction matters: the first is fixed in the next proposal, the second is fixed on site this week.
- Percentage complete versus percentage of budget consumed. This is the single strongest early-warning signal in the sector: a project that has burned a large share of its budget while under half complete will not be rescued by a miracle in the final month.
The purpose of these comparisons is not a handsome report after handover. It is to surface the problem while the project is in its second month, when negotiating a change order, adjusting the execution method or switching a supplier is still possible. A report that arrives after handover documents the loss; it does not prevent it.
Change orders: the thing that settles the argument months later
No contracting or maintenance project is executed exactly as written. The client asks for an addition, site conditions contradict the drawings, an authority imposes a requirement nobody costed. This is where companies lose more money than any technical error costs them: the work is done on the back of a verbal request or a quick message, and months later, when the claim is raised, the client says — in good faith or not — that it was inside the original scope. Whoever holds a document wins that argument, not whoever tells the better story.
A disciplined change order needs six fields, no more:
- A description of the additional work precise enough to distinguish it from the original scope.
- Who requested it, by name and role, because the requester's authority is the first thing disputed later.
- The date of the request and the date of execution.
- Its effect on price and on duration together. Many companies document the money and forget the time, then get penalised for a delay the client caused.
- Its reference in the contract or bill of quantities.
- Written approval before execution. A signature on a phone screen on site is an acceptable document, and it is far better than a verbal approval everyone remembers differently.
And the operational rule that always gets forgotten: an approved change order must raise the contract value in the system immediately. If the cost of additional work lands on the job number while its revenue does not, a successful project will look like it is bleeding, and you will make a wrong decision from a correct number read out of context. Work executed but not yet approved is recorded as a pending claim shown clearly in the report, because the difference between confirmed revenue and a claim under negotiation is something a manager should see, not be ambushed by.
Payment applications and retentions: from executed work to cash in the account
Executed work is not cash, and the distance between the two is what kills companies that are profitable on paper. The journey is familiar: measurement of completed work, approval by the consultant or client representative, a payment application, a tax invoice, then settlement. Every step has a stalling point every company in the sector knows by heart.
Most delays are not disputes about the work itself. They are gaps in what proves it: photos not attached, handover records unsigned, visit reports that do not match the application, undocumented change orders. This is where everything built in the earlier parts pays for itself: a work order closed with photos, a client signature and logged readings means the application file comes out of the system ready, instead of being assembled from memory and chat groups during one exhausting week every month.
Three numbers must be tracked separately and never blended into revenue:
- Retention. A share the contract withholds from every application, usually released in two stages tied to preliminary and final handover. It is your money, but it is not in your account — and forgetting to chase it is one of the most common ways companies lose cash with no dispute involved at all.
- Advance payment and its recovery. Where the contract provides one, it is a loan recovered progressively from applications. Treating it as revenue early creates a false sense of liquidity that unravels mid-project.
- Application aging. How many applications are submitted but not approved, how many approved but not paid, and how long each has been sitting. This report alone tells you which client deserves your crews' priority and which one needs better terms at renewal.
On the regulatory side, every approved application ends in a tax invoice meeting the e-invoicing requirements of the Zakat, Tax and Customs Authority in the integration phase. A company that issues invoices from the same system that holds its work orders and applications re-enters nothing by hand and never lives through a mismatch between the invoice figure and the completed-work figure. Running one system for operations and another for invoicing with no link between them means paying for the gap twice: once in staff time and once in errors.
The Origami view
When we sit with a contracting or maintenance company, our first question about cost is not about systems. It is a number: what was the margin on the last project you handed over? In most cases the answer is an estimate from memory that its owner walks back two minutes into the discussion. That walk-back is the real starting point, because it means pricing, renewal and new-work decisions are currently being made on instinct.
As a technology company serving the Saudi contracting and maintenance sector, three rules apply in every delivery: the job number is a mandatory field on every financial transaction from day one, not after the system settles; a change order is never executed before written approval, however friendly the client relationship; and we do not build profitability reports on allocated indirect costs before management has approved the allocation basis in writing. A fourth rule comes from the field: a cost that surfaces two months after it was incurred is not management, it is history. Data that arrives late documents what happened and changes nothing.
Where this leaves you
Knowing the margin on every project is not an accounting report issued at year end. It is the result of daily operational discipline: a job number on every transaction, four cost streams arriving from their sources rather than from estimates, a contractual baseline to compare against, change orders documented before execution, and payment applications produced by the same system that executed the work. Once that loop closes, your next quote stops being a gamble and becomes a decision based on your actual cost rather than on market prices alone.
That leaves the largest single hole in any maintenance company's cost base: parts. Part six covers spare parts and inventory across sites and technician vans — treating every site container and every van as a real stock location, and why issuing a part against a work order is what makes everything in this part true in the first place.
Sources
- Zakat, Tax and Customs Authority — e-invoicing requirements, the integration phase, and VAT treatment of invoices and payment applications.
- Ministry of Finance — the Government Tenders and Procurement Law and its implementing regulations: advance payments, payment applications, guarantees and retentions in public contracting.
- Etimad platform — government contracting procedures and electronic submission and tracking of payment applications.
- Saudi Organization for Chartered and Professional Accountants — standards adopted in the Kingdom, including revenue from contracts with customers and its effect on recognising revenue by percentage of completion.
- Ministry of Human Resources and Social Development — Labour Law provisions on wages, working hours and overtime that feed into hourly cost calculations.
- Saudi Vision 2030 — the national direction on spending efficiency and financial discipline in contracting and facilities operations.
Frequently asked questions
How do I calculate a technician hourly cost correctly?+
Not by dividing basic salary by contracted hours. A loaded hourly cost adds salary, allowances, GOSI contributions, accommodation, transport, medical insurance and any other employee-related cost, then divides by hours actually productive rather than hours attended. Time spent travelling, waiting and on leave is a real cost your price must cover, and ignoring it is the most common reason a project looks profitable in the proposal and loses money at closure.
What is the difference between a payment application and a tax invoice?+
A payment application is a measurement and approval document: it records the work completed in a given period and is approved by the consultant or client representative, with contractual retention and advance-payment recovery applied to it. The tax invoice is the statutory document issued after that approval and must meet the e-invoicing requirements of the Zakat, Tax and Customs Authority. The order matters: work, then measurement, then approval, then invoice. Skipping a step almost always ends in a payment dispute.
What should I do if my crew executed extra work without an approved change order?+
Record it immediately as a pending claim rather than revenue: the description of the work, who requested it by name and role, the request and execution dates, any correspondence proving the request, and site photos. Then present it to the client in writing as soon as possible rather than at project end, because the chance of approval falls the older the date gets. To stop it recurring, make the system block opening a work order outside contract scope without a change-order reference — control by procedure beats reminders in meetings.
Do I need a full system, or is a spreadsheet enough for cost control?+
A spreadsheet is enough for one small project and a limited crew, and it collapses quickly across multiple projects, because cost originates in the site, the warehouse, procurement and attendance at once, and any late manual entry turns the numbers into history rather than a decision tool. The practical signal that the time has come is when producing a project profitability report takes more than an hour, or when two departments report different figures for the same project. The answer is not the largest system available, but one that carries the job number on every operational and financial transaction and issues the payment application and invoice from the same place.
Follow Origami in Google
Pin Origami as a preferred source and our articles will surface first for you in Google Search and Top Stories.

Related articles
- Business SystemsHR and Payroll Systems for Saudi Businesses: What You Actually Need and How to ChooseA practical guide to choosing an HR and payroll system in Saudi Arabia: what it must cover, how it connects to Mudad, GOSI and Qiwa, and when custom beats off-the-shelf.
- Business SystemsThe Rodri Transfer Lesson: Why Performance Does Not Move With the Asset You BuyBarcelona are closing in on Rodri, and the question occupying analysts is the same one facing every manager who buys the best system on the market or hires the strongest candidate: does performance travel with the asset, or is it a property of the system that produced it? A technical and managerial read of a deal that is not done yet.
- Business SystemsField Service Management Software: Run Technicians and Work Orders From One PlaceA practical guide for Saudi maintenance and service companies: what field service management software is, when you need it, its core modules, and how to connect it to e-invoicing.
- Business SystemsKnowledge Management: Why It's Your Company's Most Valuable Asset — and How to Stop It LeakingKnowledge is your company's most valuable asset, yet the only one that walks out the door every evening. Knowledge management keeps your company's expertise available to your team instead of trapped in people's heads — and with AI it's more powerful than ever. A practical guide for business owners.
- Business SystemsCRM Systems for Saudi Businesses: A Guide to Choosing the Right Customer PlatformA practical guide for Saudi business owners: what a CRM is, the signs you truly need one, how it differs from ERP, and how to choose the right system without overpaying.
- Business SystemsERP Systems for Saudi Businesses: When You Need One and How to ChooseA practical guide for Saudi business owners on what an ERP system is, the signs you actually need one, and how to choose the right ERP without overpaying.
Weekly newsletter
The latest articles that matter to business owners, once a week. Just your email.
Have a project in mind?
We build custom systems, apps and websites for your business. Tell us your idea and we will give you a straight answer on it.
