Where accounting software stops and construction ERP begins for contractors on Wafeq, Qoyod or Daftra
Wafeq, Qoyod, Daftra and similar Saudi platforms do a genuinely good job of bookkeeping, VAT returns and ZATCA e-invoicing, and for a small contractor running a handful of jobs they are often enough. The line between them and a construction ERP is not quality, it is scope: they are built around a chart of accounts and a ledger, not around a cost code, a BOQ line and a monthly valuation. This page sets out which construction questions a general ledger cannot answer, so you can decide honestly whether you have crossed that line yet.
Six things a general ledger was never asked to do
None of this is a criticism of accounting software. These are contracting-specific structures that sit outside the accounting model, which is why they usually end up in parallel spreadsheets. Feature sets change, so check the current documentation of whichever product you use before assuming any of this applies to your edition.
Job costing by cost code
A ledger tells you what you spent by account. A contractor needs to know what one cost code on one project has consumed against its budget, and where it will land at completion.
- Cost breakdown structure per project, not just a project tag on a GL account
- Budget, committed, actual and forecast on the same row
- Estimate at completion and variance the moment a cost lands
- Drill from a cost code down to the PO, timesheet or invoice behind it
BOQ, tender and variations
Work is won on a priced bill of quantities and then changed by variation orders. Without the BOQ inside the system, both the awarded budget and the billing basis live outside it.
- Priced BOQ with rate build-up carried from bid into execution
- Award converts the winning bid into the live project budget
- Variation orders adjust contract value and budget together
- Quantity-based valuation instead of manually typed invoice lines
Committed cost, not just spent cost
Accounting recognises a cost when the invoice arrives. On site the money is effectively gone the day the subcontract is signed or the PO is issued, often weeks or months earlier.
- Purchase orders and subcontracts reserve budget on approval
- Uncommitted balance visible before the next order is raised
- Goods received but not invoiced held against the job
- Overrun visible while it can still be argued, not at month end
Progress billing: the IPC or مستخلص
A construction invoice is a valuation, not a sales invoice. It carries work done to date, previously certified amounts, advance recovery and retention, and it still has to clear ZATCA Phase-2 correctly.
- Cumulative-to-date valuation against BOQ lines or milestones
- Advance payment recovery at the agreed percentage
- Retention deducted, tracked and released at handover
- ZATCA-compliant tax invoice generated from the certified valuation
Subcontractors and back-to-back certificates
Subcontractor payments are certificates that mirror the same valuation logic, ideally back-to-back with what the client certified, each holding its own retention (ضمان أعمال).
- Subcontract value, variations and remaining balance per package
- Payment certificates with their own advance recovery and retention
- Back-to-back timing against the main contract valuation
- Retention release schedule and expiry dates on bank guarantees
Labour and plant landing on the right job
WPS payroll and GOSI are payroll obligations. Cost control needs those same wages split across the cost codes people actually worked on, and plant recharged to the projects that used it.
- Timesheet or attendance allocation from worker to cost code
- WPS file, GOSI and Qiwa/Mudad data from the same payroll run
- Owned and hired plant recharged by hour or day used
- Site establishment and overhead distributed on a defensible basis
Which side of the line are you on?
Most contractors know the answer before they finish reading this. If you are on the first card, staying where you are is the right commercial decision.
You are fine on accounting software if...
Your current platform is doing exactly what it was designed for, and nothing important is escaping into spreadsheets.
- A few projects at a time, and you can hold their status in your head
- Billing is broadly lump sum or milestone, not quantity-based valuations
- Little subcontracting, or subcontracts settled simply
- Margin is known at the end of the job and that has never hurt you
- The owner or accountant personally reviews everything each month
- The jobs to be done are VAT, ZATCA e-invoicing and clean books
It is time to move if...
These are the signals that the accounting system is being asked to do a job it was never scoped for.
- The real project numbers live in Excel and the ledger is a formality
- You cannot say today whether a project is over or under budget
- Committed cost is discovered when the subcontractor finally invoices
- Preparing the mustakhlas takes days of manual assembly every month
- Retention and advance recovery balances are reconciled by hand
- Payroll is compliant, but you cannot say what labour cost each job
- A bank, client PMO or Etimad work demands cost reporting you cannot produce
The honest middle ground
Moving is not all or nothing, and the real question is usually when rather than whether.
- Many contractors pilot one project on job costing before switching everything
- Your chart of accounts and your accountant's way of working can come across
- Financial reporting stays under the same SOCPA and IFRS framework you use now
- If your projects are short and simple, the extra structure will feel like overhead
- If you are moving toward larger or government work, the reporting gap widens fast
Related: Job costing by cost code · BOQ and tender management · IPC and progress billing (مستخلص) · Subcontractors and retention · ZATCA Phase-2 e-invoicing · WPS payroll and GOSI · Construction ERP overview
How a move off accounting software usually runs
Map the chart of accounts, then add cost codes
Your existing chart of accounts comes across largely as it is, so your accountant keeps working the way they do. The cost breakdown structure is added alongside it, not instead of it, so cost codes roll up into the accounts you already report on.
Bring over balances, live projects and contracts
Trial balance, customers, suppliers, the VAT position and open receivables and payables transfer as opening balances. Live projects arrive with contract value, BOQ, variations to date, certified work, advance recovered and retention held, so the next valuation continues the sequence instead of restarting it.
Onboard ZATCA and prove clearance before go-live
Phase-2 e-invoicing is device-based, so a new e-invoicing generation unit is onboarded and its CSID issued for IntellaQ Flow. Standard clearance and simplified reporting are validated in the ZATCA sandbox first, and the old system stops issuing on an agreed cut-off date so no sequence overlaps.
Close one cycle in parallel, then cut over
Run one month in both systems and reconcile. When the VAT return, the payroll run and at least one valuation tie out, the old system becomes a read-only archive for historic reporting.
Questions contractors ask before moving
Can we keep our accountant and our existing chart of accounts?
Yes, and that is the normal path. Your chart of accounts is imported and stays the structure your financial statements are built on, so the trial balance, VAT return and year-end pack still look familiar to whoever prepares them. What changes is that a second dimension, the cost code, is captured on transactions so the same posting answers both a financial question and a project question. Accountants who resist a move often expect to lose their account structure; when they see it preserved, the objection usually goes away. External accountants and auditors can be given their own read-only access instead of being sent exports.
What actually migrates, and do we lose our history?
Standard migration covers the chart of accounts, customers, suppliers, items, opening balances, open receivables and payables, the current VAT position, employee master data with GOSI and WPS details, and in-progress projects with contract value, BOQ, certified work to date, advance recovery and retention balances. Full transaction-level history from earlier years is usually not re-posted, because rebuilding old entries into a new cost structure costs effort and adds little. The common approach is balances plus the current fiscal year, with the old system kept in read-only mode as the archive for prior periods, which also keeps your record-retention obligations intact.
Do we lose ZATCA compliance during the change?
No, but the sequence matters. Phase-2 integration is tied to a registered e-invoicing generation unit with its own cryptographic identity, so changing systems means onboarding a new unit rather than moving the existing one. In practice IntellaQ Flow is onboarded and passes compliance checks in the ZATCA sandbox before go-live, both standard B2B clearance and simplified B2C reporting are validated, and only then does invoicing stop in the old system on an agreed date, so two systems never issue against the same sequence. Your VAT registration and reporting obligations do not change; only the issuing system does.
How does the cost compare with what we pay now?
It is higher, and it would be dishonest to pretend otherwise. Per-user accounting subscriptions are priced for bookkeeping. A construction ERP carries project control, procurement, subcontract management, payroll and compliance, plus an implementation to configure your cost structure, so it is quoted against scope rather than as a flat list price. The question worth asking is not the licence difference but what one mispriced variation, one unrecovered advance or one retention balance released late has already cost you. If you cannot point to that number, the honest answer may be that you do not need to move yet.
Can we keep our accounting software and add job costing on top?
Some contractors try this and it works for a while. The difficulty is that job costing is fed by transactions that originate in accounting and payroll: supplier invoices, purchase orders, wages, plant hire. If those live in one system and the cost structure in another, someone spends every month re-keying or reconciling the two, and the numbers diverge exactly when you are busiest. A hybrid is reasonable as a transitional step, or where a group has one contracting entity and several that are not. As a permanent design it tends to recreate the spreadsheet problem in a more expensive form.
How long does implementation take?
A contractor with a clear cost breakdown structure and clean opening balances can typically be live in weeks rather than quarters, with the first month closed in parallel against the old system. What extends it is rarely the software: it is agreeing the cost code structure, deciding how overhead and plant are recharged, and cleaning supplier and employee data. Those decisions are worth making properly, because every report afterwards depends on them. We would rather spend two extra weeks on the cost structure than deliver a fast go-live that produces numbers nobody trusts.
Bring us one live project and we will show you the numbers a ledger cannot produce
Tell us how your business works. We'll show you the integrated ERP & CRM that fits it — and start building next week.