Contracting Payment Application: Progress Billing Template + Saudi Guide

In contracting projects, money does not reach the contractor in a single lump sum at building handover. Payment flows as periodic installments tied to actual percentage of completion on site, and each installment needs a combined accounting and engineering document known as a contracting payment application (or progress payment certificate). This application is the bridge linking the line items priced in the project contract, the quantities physically executed on the ground, and the amount the contractor is owed by the owner at the close of an accounting period.

Missing or inaccurate payment applications produce one of three scenarios: a contractor who receives more than was actually executed and then stalls on closing the project, a contractor who is genuinely owed money but cannot prove it and loses cash flow, or an owner who pays without an auditable document and lands in litigation at handover. The payment application is not a formality; it is the formal accounting tool that organizes three axes at once: percentage of completion, net amount due, and retentions and bonds tied to it.

In this practical guide we explain contracting payment applications from scratch: the precise definition, the types adopted in the Saudi market, the full components of any application, the retention system and how it is computed, direct and indirect costs, ZATCA e-invoicing requirements, a detailed numeric example for a 10 million SAR construction project, common mistakes, the relationship between the application and the bank guarantee, and finally how Qoyod turns this complex monthly cycle into an automated process inside the contracting sector.

What is a contracting payment application? Precise definition and place in the project cycle

A contracting payment application is a combined accounting and engineering document prepared by the contractor, certified by the consultant, and approved by the owner. It determines the value of works actually executed on site during a defined period (typically a month) and claims disbursement of the contractor’s dues for that period after deducting statutory and contractual withholdings. In international practice it is known as a Progress Payment Certificate or Interim Payment Application, and in Gulf contracts it is sometimes shortened to “interim payment certificate”.

The core idea is that contracting is by nature long term: a residential building is delivered in 14 months, a road takes two years, a power station exceeds three. Nobody accepts that the contractor goes without cash flow for that entire span, and nobody accepts that the owner pays the full value before seeing the outcome. The solution: break the project into regular completion periods, issue a payment application at the end of each period, and disburse the entitlement based on it. This way the completion cycle is synchronized with the payment cycle, and the balance of interests between the two parties is preserved.

Functionally, the payment application serves five purposes at once: proving actual completion with a neutral, auditable figure, establishing the financial claim with a documented amount, computing the retention that protects the owner’s right to fix any latent defect, applying withholdings (advance payment recovery, delay penalties, insurances), and issuing a formal tax invoice under ZATCA regulation. Any simplification that drops one of these dimensions opens a wide door to dispute.

Types of contracting payment applications in the Saudi market

In practice, contracting accountants distinguish between three main types of payment applications, and each type has a different accounting and legal nature. Mixing them up confuses the ledgers and corrupts the end-of-project account reconciliation.

Periodic (monthly) application: The most common. It is issued monthly throughout execution and reflects the value of works completed within that specific month only. Its advantage is keeping a steady cash flow for the contractor and letting the owner track progress step by step. Periodic applications are numbered (No. 1, 2, 3, etc.) and are cumulative in values, not in disbursement.

Final (closing) application: Issued once on preliminary handover of the project. Its function is a full inventory of everything executed since project inception, minus the sum of prior periodic applications. Here pending items, extra quantities, and variation orders are settled, and typically half of the retention value is released. Any error in the final application is hard to correct later because it closes the main claims cycle.

Maintenance bond release application: Issued at the end of the contractual maintenance period (usually 12 months from preliminary handover). Its function is to release the second half of the retention that remained held to guarantee that the contractor addresses any defects appearing after handover. This application contains no new execution items, only a single item: the release of the remaining retention.

Alongside these three, some projects use an advance payment recovery application issued at project start to recover part of the Advance Payment against a bank guarantee equal to its value. For readers who want to deepen their grasp of advance payment logic, the project accounting guide on the Qoyod blog is a useful starting point.

Components of a contracting payment application in detail: what the template holds from A to Z

A professional payment application does not stop at one line called “value of executed works”. It branches into nine sequential elements, each built on the prior one, until reaching the net amount payable. The order itself matters because it determines what gets multiplied by VAT and what is deducted afterward.

1) Project and parties data: Project name, contract number, location, owner name, contractor name, consultant, execution start date, contract duration, current application number, and the period it covers (from date to date).

2) Bill of Quantities (BOQ): A list of every contract line item with its description, unit (cubic meter, ton, piece), contract quantity, quantity executed this month, cumulative executed quantity, unit price, and value. This is the computational heart of the application.

3) Cumulative value of executed works: Sum of line item values through the end of the current month, regardless of what has already been disbursed.

4) Monthly value of executed works: The difference between the cumulative value this month and the cumulative value last month. This is the figure that flows to the contractor’s revenue in the income statement for the month.

5) Variation Orders: Any adjustments to quantities or prices approved by the consultant and the owner. They are added to or deducted from the cumulative value.

6) Discounts and withholdings: These include the performance retention, advance payment recovery, delay penalties if any, and any other contractual deductions.

7) Net amount due before tax: The monthly value minus the deductions.

8) VAT (15%): Computed on the net amount due in line with ZATCA requirements.

9) Net amount payable: The final figure transferred to the contractor’s bank account after the owner signs the disbursement order.

For accountants running multiple projects at once, combining this application with the daily accounts journal helps close the project cycle each month without losing any entry.

Interim versus final payment applications

Many project owners confuse the “interim” application, which is really the first or second periodic application, with the “final” (closing) application. The difference is not just chronological; it is a difference in accounting and legal nature:

• Interim/periodic application: reflects partial completion, is editable later, the retention accumulated in it is held temporarily, and it closes no item permanently.
• Final application: issued after preliminary handover, summarizes the final quantities of all line items, locks unit quantities, and releases half of the retention (50% of accumulated retention value). It is the dividing document between the execution and maintenance phases.

Legally, the owner’s signature on the final application means preliminary acceptance of the works and counts as the starting point of the maintenance period. For that reason lawyers insist on tying the final application to a preliminary handover record signed by a handover committee made up of the owner, the consultant, and the contractor, not just a solo signature by the site engineer.

The retention system in contracting contracts: how it is computed and when it is paid

Retention is a percentage of every application’s value held by the owner as a guarantee of execution quality and remediation of any defects that surface later. The standard rate in Saudi contracting contracts is 10% of each application’s value, capped at 5% of the total contract value. The rule works as follows:

Retention is computed monthly at 10% of the monthly value of executed works and accumulates in a retention account. Once the accumulated amount reaches 5% of total contract value, retention stops and no further deduction applies to subsequent applications. After the final application is issued and the works are preliminarily accepted, 50% of accumulated retention value (i.e., 2.5% of contract value) is released. The other 50% stays held throughout the maintenance period (typically 12 months) and is released at its end after a final handover free of defects.

Some contractors prefer to swap cash retention for a Retention Bond of equal value. This option frees their cash flow but carries bank fees. The decision depends on project margin and the contractor’s cost of funding. Whichever option is chosen, retention must be booked in the ledgers as a long-term receivable, not deferred revenue, because it is money owed to the contractor whose collection date simply has not yet arrived.

Direct and indirect costs in contracting accounting

Before preparing any payment application, a contractor’s accountant must understand the project cost structure because it determines the real profit margin behind each line item. Costs split into two types:

Direct costs are those attributable specifically to the project: raw materials (cement, steel, ready-mix concrete), direct site labor wages, equipment rentals dedicated to the project, salaries of site engineers, subcontractor work, and material transport to the site. These costs vary with the volume of completion and are charged to a specific contract line item.

Indirect costs (Overhead) are those that serve the project non-exclusively: head office rent, executive salaries, insurances, telecom bills, general license fees, and accounting depreciation of shared fixed assets. They are allocated across projects using a fair allocation base (a share of total labor, a share of contract value, or equipment operating hours).

The practical difference: direct cost is deducted from project revenue to give gross profit, while indirect cost is deducted from gross profit to give operating net profit. Mixing the two inflates gross profit and hides real operating losses. Going deeper into this classification starts with grasping the core financial statements and then applying them to each project as an independent cost center.

ZATCA e-invoicing for the contracting sector

Since the Zakat, Tax and Customs Authority (ZATCA) rolled out e-invoicing in the Kingdom, every financial claim in the contracting sector goes through two stages: the technical application certified by the consultant and the owner, then the electronic tax invoice issued after the application’s approval and sent to the Fatoora platform as soon as it is signed.

Technical requirements for contracting invoices include: issuing the invoice in XML format with an embedded PDF/A-3, a QR code carrying seller, buyer, amount and tax data, the contractor’s approved e-signature, a unified serial number, both parties’ tax numbers (contractor and owner), a clear Arabic description of the works, and issuance date and time. Any invoice failing these conditions is rejected by Fatoora and exposes the contractor to penalties.

The added complexity in contracting: the invoice sometimes includes discounts (retention, advance payment) that precede the tax, and others that follow it. The correct order: VAT is computed on the monthly value of works after deducting retention but before deducting the recovered advance payment, because the advance payment’s tax invoice was issued upfront at project start. This order alone prevents double taxation on the same revenue.

Practical example: contracting payment application for a 10 million SAR construction project

Let us apply the above to a commercial villa construction project in Riyadh with a total contract value of 10,000,000 SAR, 14-month execution, a 10% advance payment (1,000,000 SAR) against a bank guarantee of equal value, 10% retention per application capped at 5% of contract value, and advance payment recovery at 12% of each application’s value.

At the end of month four, the contractor issued application No. 4 with the following figures:

• Cumulative value of executed works through end of month 4: 3,200,000 SAR
• Cumulative value of prior application (No. 3): 2,400,000 SAR
• Monthly value of executed works: 800,000 SAR
• Performance retention (10%): -80,000 SAR
• Advance payment recovery (12% of monthly value): -96,000 SAR
• Net amount due before tax: 624,000 SAR
• VAT (15% on 800,000 – 80,000 = 720,000): 108,000 SAR
• Net amount payable: 732,000 SAR

Condensed accounting entry on certification of the application: debit project revenue 800,000, debit accounts receivable 732,000, credit retention payable 80,000, credit advance payment 96,000 (reducing its balance), credit VAT payable 108,000. The equation balances: 800,000 + 108,000 = 732,000 + 80,000 + 96,000.

Common mistakes in preparing contracting payment applications

After reviewing dozens of applications by contractors in the Saudi market, seven mistakes recur clearly. Each costs the contractor or the owner real money or opens a later legal dispute:

• 1) Confusing monthly with cumulative quantities: the application is built cumulatively and paid on the delta. Recording the monthly quantity in the cumulative field doubles the claim and corrupts subsequent tables.
• 2) Applying retention to VAT: retention is deducted from value before computing VAT, not after. The reverse order produces a deficient tax invoice and exposes the contractor to a ZATCA review.
• 3) Failing to separate variation orders from original line items: variation orders must sit in a standalone table at different prices, since mixing them with the original items hides the actual inflation in contract value.
• 4) Updating quantities without a certified variation order: any increase in quantities without a variation order signed by the owner is rejected in the final application, even if it was physically executed on site.
• 5) Issuing the tax invoice before application certification: the invoice follows the application, it does not precede it. Issuing it before signature places a tax obligation on revenue that may not be certified at the same value.
• 6) Not booking retention as a receivable: some contractors subtract retention from revenue, understating project revenue and hiding a real financial asset. The correct treatment: retention is a long-term receivable.
• 7) Omitting delay penalties from the application: if the contractor overruns the contract schedule, the penalty is due in the application that coincides with the delay, not in the final application alone.

Avoiding these mistakes starts with adopting a unified application template across every project and connecting project ledgers to an accounting system that moves entries automatically the moment the application is certified. The accounting detail of each entry is worth reviewing through the double-entry guide before building the sub-account chart for each project.

The contracting payment application and the bank guarantee

Any serious contracting project in Saudi Arabia is accompanied by at least three bank guarantees: the advance payment guarantee, the performance bond, and the maintenance bond. Their relationship to payment applications is tight and reciprocal:

Advance Payment Guarantee: issued by the contractor’s bank in favor of the owner for the full advance payment value (typically 10% of the contract). Its value drops automatically with every application by the advance payment recovery rate, until it reaches zero once the advance is fully recovered. The owner is responsible for sending the bank a periodic reduction letter reflecting what has been recovered through applications.

Performance Bond: furnished at contract start at 5% of value. It stays valid throughout execution and is released after certification of the final application and signing of the preliminary handover record. It is not deducted from applications but is held as a separate guarantee.

Maintenance Bond: provided in lieu of the second half of accumulated retention, with a value of 2.5% of the contract. This is an optional substitute that lets the contractor collect the second half of retention immediately on preliminary handover instead of waiting 12 months.

A good accountant logs every bank guarantee under Contingent Liabilities in the disclosures, since these are obligations that do not appear on the balance sheet but may convert to actual liabilities if their terms are breached.

How Qoyod turns the contracting sector into an automated monthly cycle

The contracting sector lives with two structural knots: many concurrent projects, and many parties in each project (owner, consultant, contractor, subcontractors, suppliers, banks). Running this cycle manually consumes a full week of the accountant’s time each month, and any small mistake propagates across every project. Qoyod was designed to master these complexities in three layers:

Layer one, track every project as an independent cost center: the accountant creates a project per contract, defines its revenue line items, direct cost line items, and its share in indirect cost allocation. Every financial entry is automatically charged to the relevant project and updates a project-specific income statement in real time. The accountant sees the margin of every project live, not in the year-end report.

Layer two, automate the application cycle from certification to entry: the moment an application is certified, its value is entered into Qoyod and the system generates automatically: the revenue entry, the retention entry (long-term receivable), the advance payment recovery entry, the VAT entry, and the electronic invoice sent to ZATCA. Instead of 5 manual, error-prone entries, the accountant is responsible for entering one number only: the certified monthly value of works.

Layer three, integration with banks and guarantees: Qoyod links project accounts with bank accounts, so incoming transfers from the owner appear automatically and are tied to each application. It also keeps a register of bank guarantees and their renewal dates, so the contractor is never surprised by an expired guarantee at application certification. For those who manage subcontractors, the system also integrates the full procurement cycle so subcontractor invoices are linked to the main project’s applications.

On top of that, project reports in Qoyod show the executive owner three key figures per project: percentage of financial completion (disbursed / contract value), percentage of physical completion (executed / contract value), and the cash flow gap (retentions + uncollected invoices). Together these numbers tell whether the project is generating liquidity or draining it.

Frequently asked questions about contracting payment applications

Is the contractor entitled to issue a monthly application even if completion is small? Yes, as long as the contract does not impose a minimum application value. In practice, some contracts impose a minimum (say 100,000 SAR) to avoid excessive administrative overhead.

What happens if the consultant rejects the application? The contractor amends the disputed items and resubmits. Disputes over quantities are referred to an independent reference engineer under the contract’s dispute resolution mechanism.

Is VAT computed on retention? Retention is deducted from value before VAT, so no VAT is charged on it at application issuance. When it is released later, a standalone tax invoice is issued for the released retention value plus 15% VAT.

Can the contractor pledge application receivables to the bank? Yes, this is called Assignment of Receivables and requires written consent from the owner. Many Saudi banks finance contractors against assignment of application receivables.

When are works considered “executed” for inclusion in the application? Works are considered executed once they are completed per specification and accepted by the consultant on site. Partial or rejected works are not included until completed.

Conclusion: the application is the project’s accounting compass

The contracting payment application is not a routine administrative form. It is the central tool coordinating field execution, the accounting cycle, the tax obligation, and the bank guarantees. Any gap in preparing it translates into a cash flow delay, a distortion in declared revenue, and a potential dispute at close-out. A serious contractor builds a unified template, trains the team on the correct order of deductions, ties the cycle to an accounting system that generates entries automatically, and keeps a complete archive of every application with its certifications and tax invoice.

Whether you run a single project or a portfolio of concurrent ones, invest today in one payment application template and embed it in your accounting cycle. The difference between a contracting company that hits a healthy margin and another that stalls is rarely the size of contracts; it is the discipline of the cycle from application to entry to invoice to disbursement.

References and related links from Qoyod

• Daily accounts journal template: to document every entry tied to the application the moment it is certified.
• Work order template: to link work orders to the monthly application line items.
• Payroll template: for direct labor on the project site.
• Financial distress forecast template: to assess financial risk across a portfolio of projects.
• Employee KPI template: to measure the performance of project engineers.
• Qoyod plans: to pick the right plan for the size of your project portfolio.
• Qoyod integrations: to connect with banks, the Fatoora platform, and payment gateways.
• Qoyod blog: for more articles on contracting accounting.
• Sales team: for a specialized consultation for the contracting sector.
• Start your free trial: 14 days, no credit card.