Interim Payment Certificates in GCC Construction: How to Build a Billing Package That Gets Certified First Time

Most GCC contractors submit their IPC, wait 28 days, and receive a version back with 15–20% disputed. Then the real work starts: resolving line-by-line disagreements on quantities they completed three weeks ago. It does not have to work this way.

What Makes an Interim Payment Certificate Different from an Invoice

An invoice states what you want to be paid. An interim payment certificate demonstrates what you have earned.

The distinction matters under FIDIC and most GCC public contracts. Under FIDIC Clause 14.3, the contractor submits a statement of the amount it considers itself entitled to. The engineer reviews and issues a payment certificate within 28 days (or the contract-specified period). That certificate — not the contractor's statement — is what the client actually pays.

Poorly prepared submissions compress the engineer's ability to certify quickly. Every gap in supporting documentation becomes a reason to query, defer, or reduce.

The Five Components of an IPC Submission

A complete IPC package for a GCC construction project covers five areas.

1. Measurement Record (The Certified Quantity Backup)

This is the core of any IPC — a document that proves what quantities were completed in the period, tied to physical records the engineer can verify independently.

Accepted measurement records include:

Digital work confirmations signed by the GC QS and the engineer's representative at the point of completion
Survey reports for earthworks, concrete pours, and finishes
Installed quantities extracted from drawing registers or as-built records
Material wastage records for supply-and-fix packages

The single most common reason for IPC reductions is a quantity claim the engineer cannot trace back to a contemporaneous site record. "We completed 450m of wall tiling in Week 3" needs to point to specific work confirmation references, not just appear as a number in the summary.

Work confirmations generated through a connected system provide exactly this: timestamped, location-tagged, QS-reviewed records that translate directly into IPC line items.

2. Subcontract Certification Summary

If your IPC includes subcontracted work — as most GCC projects do — you need to show what you have certified to each subcontractor and that your claim to the client does not exceed what you have already verified in the field.

Some GCC clients, particularly Aramco and ROSHN, require confirmation that subcontractors have been paid for previously certified work before the next IPC is processed. The data you need per package: contract reference, previous cumulative certified, this period's certified amount, new cumulative total, and remaining uncertified balance.

If you are managing this manually across 20+ subcontract packages, you will spend two days per month assembling this table. A connected system generates it automatically from live certification records.

3. Variation Account (Approved and Instructed)

Every IPC should include a variation account showing the full register of changes:

Approved variations: value confirmed, included in contract sum adjustment
Instructed variations: instruction received, assessment pending or disputed
Submitted variations: formal claim submitted, awaiting engineer's assessment

Under FIDIC Clause 13.3, the engineer issues a variation instruction before or after the work is executed. GCC clients expect the variation register categorized clearly so they can certify the approved portion without waiting for all variations to be resolved.

The mistake many contractors make: submitting unapproved variations in the base measurement line. The engineer deducts them, you dispute the deduction, and the IPC goes back for revision. Submit variations in a separate account categorized by status. The engineer certifies the clean base and notes the variation position separately.

4. Deductions and Adjustments

Every IPC needs a deductions section covering retention (typically 5–10% of gross certified up to the contract ceiling), advance payment recovery (recoupment rate multiplied by gross certified amount), previous overpayment recovery if applicable, and any other contract deductions such as insurance premiums or scaffolding supplied by the main contractor.

Net certified value equals gross certified value minus all deductions. Clients will apply these deductions whether you show them or not. If you omit them from your submission, the engineer recalculates, the numbers do not match, and you end up negotiating deduction arithmetic instead of base quantities. Enter the retention ceiling, recoupment rate, and deduction rules once in your contract register. Every IPC derives them from that source.

5. Conditions Precedent Compliance Statement

Most GCC project contracts include conditions precedent to payment: requirements the contractor must satisfy before the certification is valid. Common examples include GOSI and WPS compliance for the previous payroll period, current third-party insurance certificates, an HSE performance declaration, an approved programme update, and a current submittal and RFI log.

A short compliance declaration referencing each condition precedent — with the relevant certificates attached — removes a common objection before it is raised. On Aramco and NEOM projects, missing compliance documentation is a standard reason for IPC deferral, not a query. The IPC simply waits until the document arrives.

The Certified vs Invoiced vs Received Reconciliation

Once the engineer issues the payment certificate, you have a second problem: converting it into a collectible invoice and tracking its progress through the client's payment cycle.

The reconciliation every commercial manager needs to see weekly: current IPC certified value, less previous cumulative certified, equals net this period. Minus deductions. Net payable this period. Invoice submitted date. Client confirmed receipt date. Payment received date. Outstanding receivable balance.

When this reconciliation does not exist, finance teams assemble it from emails, spreadsheet tabs, and certification letters. It takes a day to compile and is already out of date. Retention releases sit forgotten because nobody tracked the release trigger against the contract milestones that unlock them.

FIDIC Clause 14 Timing and GCC Contract Variations

Under FIDIC 1999, the contractor submits the IPC statement. The engineer issues the payment certificate within 28 days. The client pays within 56 days of the contractor's submission — not the engineer's certification date.

In practice, GCC contracts modify these timelines. Saudi public contracts under CTL allow 60 days from invoice submission. NEOM and ROSHN typically operate on 45 days. Private clients range from 30 to 90 days depending on the engineer's certification cycle.

The clock starts when you submit, not when the engineer certifies. A submission with errors or missing documents resets the clock when you resubmit. On a project generating SAR 8M in monthly certifications, a two-week submission correction adds roughly SAR 200,000 in financing cost at a 6% working capital facility rate. The cost of a poorly structured IPC is not abstract — it accumulates every month.

What the Engineer Is Actually Checking

Engineers on GCC construction projects review your IPC against five things:

The construction programme — Does claimed progress align with the accepted schedule?
Measurement records or work confirmations — Can they trace every quantity to a site record?
The variation register — Are variation values consistent with what was agreed or instructed?
Deduction calculations — Do retention and advance figures match the contract terms?
Conditions precedent — Are all required certificates current and attached?

Build your IPC package to answer these five questions in sequence and the certification cycle shortens. Build it as a financial assertion without supporting evidence and the engineer does the verification work themselves — creating queries, waiting for responses, issuing partial certificates for the undisputed items only.

The Five Common Reasons GCC IPCs Come Back

Across construction projects in the GCC, the same five issues drive IPC rejections and reductions.

Quantity claims without contemporaneous records. Works completed in Week 2 with no signed work confirmation until Week 4 when the IPC was assembled. The engineer cannot backdate the verification, so the quantity enters a pending status and waits for the next period.

Unapproved variations buried in the base measurement. Instructed but unapproved variation work mixed into measurement sheets. The engineer deducts it, you dispute the deduction, and the IPC enters a revision cycle that costs three to four weeks.

Retention ceiling reached but not tracked. The contractor continues deducting retention after the ceiling is met. The client receives a lower net figure than expected, flags the discrepancy, and the IPC is revised before payment is processed.

Conditions precedent documents expired or missing. Insurance certificate lapsed two weeks ago. GOSI statement absent. The IPC is valid in principle but uncertifiable in practice until documentation is updated and resubmitted.

Advance recovery rate discrepancy. Contractor and client are using different recoupment rate formulations. Small differences accumulate into meaningful disputes on long projects and delay final account settlement.

Every one of these is preventable. Most arise because the IPC is assembled from multiple disconnected data sources under time pressure at the end of each billing period, rather than drawn from records kept current throughout the month.

Building the IPC from Live Data

A connected construction platform does not just store data — it generates your IPC package from operational records that are already current when billing day arrives.

Quantities: work confirmation register generates the measurement summary by BOQ item, current to the day
Subcontract account: certification ledger produces the subcontract schedule by package with running totals
Variations: change order register outputs the variation account categorized by status
Deductions: contract register runs the automatic retention ceiling check and advance recoupment calculation
Conditions precedent: compliance calendar flags certificate expiry dates in advance of the submission date

What typically takes a commercial team two to three days to compile monthly takes two to three hours when the underlying data is clean and connected. The submission goes out earlier in the billing period, the engineer has more review time, and payment arrives at the front end of the collection window rather than the back.

For a GCC contractor running five active projects with monthly billings totaling SAR 30–40M, compressing each collection cycle by ten days frees SAR 8–11M in working capital that would otherwise sit in the financing gap between certification and receipt.

Practical Starting Steps

If your current IPC process involves assembling documents from multiple sources at the end of each billing period, start here.

Define your standard IPC package per contract. List every document the engineer and client require. Build it as a checklist. Missing items are blockers, not afterthoughts to chase after submission.

Move work confirmations to the point of completion. Confirmations signed three days after the work is done are worth less than confirmations signed the same day. The engineer's query arises at the point of uncertainty, not the point of payment.

Maintain a live variation register. Categorize every variation as Approved, Instructed, or Submitted. Update status after every engineer meeting. Submit the variation account as a separate schedule in every IPC — never buried in the base measurement.

Automate your deduction calculations. Enter the retention ceiling, advance amount, and recoupment rate in your contract register. Derive IPC deductions from that single source — not a separate spreadsheet that diverges from the contract record over time.

Set a fixed submission date. Decide on a submission date per project and work backwards to set data cutoffs and internal review workflows. Late submissions are self-inflicted payment delays that compound across the project life.

The contractors who consistently get certified first time on GCC projects are not doing more complex work. They are submitting better-organized packages with cleaner underlying data — because they capture that data in real time rather than reconstructing it at the end of each period.