Case Studies

How a contractor got profit by project, every month

Moving a six-site fit-out and MEP contractor to Zoho Books and Zoho Expense, with progress billing and retention.

Axiora team · 20 November 2026 · 3 min read

The business

A fit-out and MEP (mechanical, electrical and plumbing) contractor in Saudi Arabia, working on six active projects at a time for developers, retailers and offices. Around 120 people, most of them on site, with a small head-office team handling finance, procurement and contracts.

The company was growing quickly and winning larger contracts. But its systems had not kept up: accounts were kept in a desktop package, and everything project-related lived in spreadsheets owned by individual project managers.

The challenge

No profit by project

Costs were recorded by type, such as materials, subcontractors and labour, but not by project. The owner could see whether the company made money overall, but not which projects earned it and which lost it. Problems on a project surfaced only at final account, when it was too late to act.

Site expenses weeks late

Site engineers paid for urgent materials, transport and small services from petty cash. Receipts came back to head office in envelopes, three or four weeks later, often incomplete. Costs landed in the wrong month and VAT on missing receipts was lost.

Progress billing and retention in spreadsheets

Each project manager kept their own sheet of progress claims, client approvals, retention held and advances recovered. Finance raised invoices from those sheets by hand. Nobody had a reliable figure for total retention receivable, and some retention was never followed up after handover.

Subcontractor bills coded inconsistently

Subcontractor and supplier bills were approved by email and posted without a project reference, so cost reports by project could not be trusted even when someone tried to build them.

What we did

  1. Requirement study: sessions with the owner, project managers, procurement and finance to agree what each needed to see per project and per month.
  2. Project structure: every contract set up as a project in Zoho Books, with reporting tags for project and cost type, so every transaction carries a project reference.
  3. Chart of accounts: redesigned to separate direct project costs, site overheads and head-office costs.
  4. Progress billing: progress invoices raised from approved claims, with retention posted to a separate retention receivable and advances recovered on each invoice in line with the contract.
  5. Zoho Expense for site teams: engineers photograph receipts on site, tag the project and submit; project managers approve on their phones; finance posts in days.
  6. Purchasing discipline: supplier and subcontractor bills cannot be saved without a project, and approvals follow limits by role.
  7. Training: recorded sessions for site engineers, project managers and finance, each focused on their own tasks.
  8. Reports: profit by project, retention by contract and cost against budget, set up so the owner can ask for them in plain words.

Typical outcomes

Per projectProfit and cost, every month
3 weeks → 3 daysSite expenses recorded
Every contractRetention and advances tracked

For the first time, the owner could open a profit and loss for each project at month-end. Two projects that looked fine on paper turned out to be over budget on subcontractor costs, early enough to renegotiate scope and recover part of the overrun through variations.

Site expenses were recorded within days, with a receipt attached to every entry. Recoverable VAT that had previously been lost on missing receipts was now captured. The total retention receivable became a single number on one report, and finance began following up each amount at handover and at the end of the defects period.

What made the difference

  • Making the project the starting point of every transaction, not something added later.
  • Giving site teams a tool that was faster than the envelope.
  • Separating retention and advances from ordinary receivables.
  • Agreeing approval limits before go-live, so discipline was built in from day one.

Projects like this usually take a few weeks from requirement study to go-live, depending on the number of active projects and the state of existing records. Support after go-live continues through the client portal.

Want this working in your business?

Book a free 30-minute call and we will show you how it applies to your setup.

Chat on WhatsApp