Invoices & Reconciliation

Why invoice management is critical

Construction is the worst-paying industry in the developed world, and the numbers are not close. Industry survey research prices slow payment at around $300 billion a year in the US alone — roughly a 14% hidden tax on the sector — with average payment cycles near 90 days and 82% of contractors waiting beyond 30.

And here is the part owners tend not to have thought through: 97% of general contractors say they price payment risk into their bids. Which means the owner is going to pay for the delay either way. They can pay it as a payment made on time, or they can pay it as a premium baked into every tender they receive, forever. Slow payment is not a saving. It is a more expensive way of buying the same building.

The legal edge is sharper than most teams realise. Under UK-style payment regimes, missing or botching a payment notice means the full claimed sum becomes payable by default — administrative lateness converting directly into legal liability, regardless of what the work was actually worth. Somebody misses a date, and the number on the application becomes the number you owe.

And where no such statute applies — which is most of the Gulf — the certification record is everything, precisely because there is no adjudication safety net to catch you. The discipline is not optional there. It is the only thing there is.

The role of invoice discipline in performance

• Keep the two instruments straight. A subcontractor’s interim application is a claim against a schedule of values: cumulative, assessed, certifiable downward, and retention-bearing. A supplier invoice is a demand: matched against the purchase order and the goods receipt, pass or fail. Applications get certified. Invoices get matched. Treat an application like an invoice and you will overpay it; treat an invoice like an application and you will start a dispute over something that only ever needed checking. Confusing them manages to produce both failures at once.

• Certify on the clock, every cycle. Assess every application on time. In notice-based regimes an unassessed application can become the payable amount by default, whatever the work was worth. In every regime it becomes an unmanaged dispute. And the certifier’s discipline — what was certified, what was reduced, why, on the record — is simultaneously cash-flow control and dispute insurance. The same act does both jobs, which is why skimping on it feels free right up until it isn’t.

• Retention is a ledger, not a habit. Typically 5–10% withheld per application, half released at completion and half after defects. Track it per contract with its release triggers, or watch it orphan — and the UK evidence shows what sloppy retention practice actually costs: billions held at any one time, hundreds of millions a year lost to upstream insolvency. Retention reform is a live regulatory question there, with proposals to ban or ring-fence retentions under active consideration. Wherever you operate, the discipline is the same: a ledger with triggers, not a percentage somebody remembers.

• Fraud lives in the payment step. Most payments fraud does not require breaking into anything. It requires an email that appears to come from a subcontractor, changing their bank details a few days before a large certified payment is due — and the AFP survey has bank-detail-change requests up 43% in two years for exactly that reason. The controls are boring and they work: an out-of-band callback to a number you already had, and dual approval on any master-data change. Neither is clever. Both are skipped.

The GCC VAT squeeze

This one deserves its own line, because it is a working-capital drain that most invoice systems simply do not model.

In the UAE, VAT on continuous construction supplies falls due at certification — or at invoice or payment, whichever comes first. On a 90-day payment cycle, that means the contractor remits VAT on money it has not received. The tax is due on the certificate; the cash arrives a quarter later. And Saudi Arabia’s FATOORAH e-invoicing regime, with its clearance-based phase, adds compliance mechanics carrying real fines.

The treatment of VAT on retention specifically is interpretively contested — there is genuine tension in how the timing rules apply to money withheld and released years later, and we are not going to pretend otherwise. This page is not tax advice, and you should confirm your treatment with a tax adviser rather than with a software vendor.

What we will say is the part that is not contested: if your invoice system does not model certified-versus-paid-versus-VAT-due timing, it is hiding a working-capital drain from you. Not creating one. Hiding one.

What happens without invoice discipline

Applications assessed late, producing default-payment exposure in some regimes and unmanaged claims in all of them. Invoices registered at site and never reaching accounts payable — so suppliers go on stop, and then the site cannot get concrete, and a paperwork failure has become a programme failure.

Duplicates paid: an application and an invoice for the same works, or a pro-forma and a final both processed. Retention withheld forever, or released twice. Supplier statements never reconciled — and recovery audits find most of their money in exactly that gap, which tells you something about how much is in it.

And underneath all of it, quietly: every late payment reprices your next tender. The supply chain remembers. It does not send you a letter about it; it just adds a number to the bid.

How Zepth runs invoices and reconciliation

Supplier invoices and subcontractor applications live in one system alongside their purchase orders, receipts, certifications and retention ledgers — because they are the same commercial conversation, and separating them is what lets the duplicates through.

Matching runs automatically. Certifications follow the contractual clocks with the deadlines visible before they expire rather than after. Retention accrues and releases by trigger. Milestone billing for services links to certified milestones rather than to an invoice somebody typed.

And the payment position — certified, paid, retained, disputed, VAT-relevant — is one live picture per supplier and per project. Which is the only version of it that is any use, because the useful question is never “what did we pay?” but “what have we promised, and when does it become someone’s problem?”