Multi-Currency Project Accounting: How GCC Contractors Track Cost Across SAR, USD, and AED

Why Multi-Currency Accounting Breaks Standard Construction Finance

Most construction accounting systems are built for a single-currency world. Enter the GCC, where a single project can carry commitments in five or six currencies at once:

• Contract priced in SAR
• Equipment rented from a UAE company, invoiced in AED
• Specialist materials imported from Europe, invoiced in EUR
• A Korean curtain wall subcontractor billing in USD
• Labour processed through Musaned and GOSI in SAR

When payments in these currencies are processed, the exchange rate on the transaction date rarely matches the rate embedded in the original estimate. That gap — foreign exchange (FX) variance — can quietly erase 1–3% of project margin if it isn't tracked. On a SAR 200M contract, that's SAR 2–6M disappearing into unexplained cost movement.

The Three Multi-Currency Problems GCC Contractors Face

1. Commitment Costs Booked at the Wrong Rate

When a procurement team raises a PO for equipment from a UAE supplier at AED 285,000, the project cost report needs to capture that commitment in SAR — but at what rate? If the PO was raised at 1 AED = 0.97 SAR and the invoice arrives three weeks later when AED = 1.00 SAR, the cost of that single order jumps from SAR 276,450 to SAR 285,000. That's an SAR 8,550 variance on one PO.

Multiply across a project with 40–60 foreign-currency POs per month, and you have hundreds of thousands of riyals in unexplained cost movement — movement that shows up in the cost report but nobody can trace to an operational cause.

2. Subcontractor Certifications in Mixed Currencies

Specialist subcontractors — MEP firms, façade installers, geotechnical specialists — often negotiate contracts split across their home currency and USD. A Korean curtain wall contractor might invoice 40% in USD (materials) and 60% in KRW (labour). A European façade consultant bills in GBP.

Without currency-aware subcontract management, each certified payment requires a manual FX conversion before hitting the cost code. That conversion is typically done ad hoc in a spreadsheet, using whatever rate the AP team pulls from a bank portal on the day. The rate is rarely the contracted rate, almost never documented, and never reconciled back to the original commitment value.

3. Budget vs Actual Currency Mismatch

Estimators build budgets in SAR. Actual costs flow in from five or six source currencies. The conversion from actuals back to SAR for cost reporting is usually handled by a single corporate rate — fixed at budget time, updated quarterly.

When spot rates move 2–4% over a project's life (common for EUR/GBP/KRW against SAR), that fixed rate produces systematic variance across every cost line with foreign-currency exposure. Finance teams spend hours at month-end explaining cost movements that are pure FX noise — not operational performance at all.

What Multi-Currency Project Accounting Actually Requires

Getting this right requires four things working together: original currency capture, rate management, FX variance isolation, and base-currency reporting.

Original Currency Capture

Every financial transaction — PO, work confirmation, subcontract certification, invoice — must be recorded in the currency it was transacted in, not just converted at the point of entry. The original currency amount and the applied exchange rate must be stored as separate fields, not collapsed into a single SAR figure.

This matters for three practical reasons: you need the original amount to match against the foreign-currency invoice; you need the rate to calculate realized vs unrealized FX variance; and if a subcontractor disputes a payment, you need to show what you certified in their currency — not just what landed in your ledger in SAR.

Rate Management: Three Rates, Three Purposes

For multi-currency projects, there is no single correct exchange rate. Different rates serve different functions:

• Spot rate at transaction date — used for actual cost booking. Captures what you actually paid in the project's base currency.
• Contract rate — negotiated rate locked into a subcontract or supply agreement. Deviations from this rate are genuine commercial variances, not accounting noise.
• Corporate budget rate — used to translate budget figures into SAR for variance comparison. Kept constant for one budget period so cost reports aren't polluted by market movements mid-project.

A properly configured accounting system applies the right rate type to each transaction type, stores all three rates against each foreign-currency document, and calculates the variance between them automatically.

FX Variance Isolation: Separating Noise from Signal

Once you capture transactions in original currency with transaction-date rates, you can split cost report variances into two distinct buckets:

• Operational variance — the contractor delivered more or less work than planned, productivity differed from estimate, or scope changed.
• FX variance — the exchange rate moved between the budget rate and the transaction date.

This distinction is critical for management reporting. A project showing SAR 1.2M cost overrun might actually be SAR 1.8M of operational savings hidden under SAR 3.0M of FX loss. Without the split, a PM looks at a red number and has no idea whether to address subcontractor performance or talk to the treasury team.

A SAR 150M Infrastructure Project: What This Looks Like in Practice

Consider a GCC contractor running a SAR 150M infrastructure project with the following currency mix: 65% SAR (local labour, Saudi subcontractors, local materials), 20% USD (specialist equipment, international consultants), 10% EUR (German engineering firm, technical materials), 5% AED (UAE plant hire).

At project start, the finance team locks in corporate rates: USD = 3.75, EUR = 4.10, AED = 1.02 (all vs SAR).

Six months in, spot rates shift: USD = 3.78 (+0.8%), EUR = 4.25 (+3.7%), AED = 1.02 (stable — AED/SAR is pegged to USD). The EUR movement alone on a SAR 15M EUR-denominated scope creates SAR 540K of additional cost — with zero operational cause. Without currency isolation, this shows up as an unexplained overrun across European-supplier cost codes.

With proper multi-currency tracking, the cost report reads clearly:

• European engineering and materials: SAR 540K over budget — 100% FX, zero operational variance
• US equipment and consultants: SAR 240K over budget — 100% FX
• Local subcontractors: SAR 1.3M under budget — 100% operational outperformance

The project is actually SAR 1.3M ahead operationally, carrying SAR 780K of currency headwind. That's a very different conversation with the project owner than an unexplained SAR 520K overrun.

Currency Exposure and the Hedging Question

Most GCC construction companies don't hedge currency exposure systematically — and with the SAR pegged to USD at 3.75, US dollar risk is effectively zero. The real exposure concentrations are in EUR, GBP, and specialist Asian currencies (JPY, KRW, CNY) for projects with significant European or Asian technical content.

Whether to hedge is a CFO-level decision based on exposure size and tenor. But you can't make that decision without first knowing your exposure. The prerequisite is always visibility: which cost codes carry foreign currency exposure, what is the aggregate open exposure by currency, and what is the unrealized FX position on outstanding POs and open subcontract balances?

A multi-currency project accounting system provides this as a live view — not a quarterly treasury exercise assembled from spreadsheets.

ZATCA Phase 2 and Multi-Currency Compliance

Saudi Arabia's ZATCA Phase 2 e-invoicing mandate requires that invoices to Saudi entities be denominated in SAR, with foreign currency amounts shown as a secondary reference. For GCC contractors receiving invoices from foreign suppliers, the ZATCA-compliant document must show both the original currency amount and the SAR equivalent at the applicable exchange rate.

This creates a compliance dimension that intersects directly with your multi-currency accounting: the SAR equivalent on the invoice must match the rate applied in your accounts payable booking. If your AP team uses a different rate than what appears on the ZATCA-compliant invoice, you have a potential audit variance. Getting multi-currency accounting right is increasingly a compliance requirement in the Saudi market, not just a finance best practice.

Key Takeaways

Multi-currency project accounting is not a complexity reserved for large contractors. Any GCC company with foreign-currency subcontracts, imported materials, or international consultants carries currency exposure that affects cost reporting accuracy. Here's where to start:

• Audit your current currency workflow. How are foreign-currency POs and subcontract payments currently recorded? At what rate? Is it documented anywhere?
• Separate budget rate from transaction rate. Stop collapsing both into a single SAR figure. You need both to isolate FX variance from operational variance.
• Require original currency on every document. POs, work confirmations, and invoices should store the transaction amount in its source currency — not just the SAR equivalent.
• Set up FX variance as an explicit cost code. Until FX movement is tracked separately, it hides inside operational variances and corrupts performance reporting.
• Build currency exposure reports before any hedging conversation. Know your open EUR, GBP, and USD exposures by project before deciding whether and how to hedge.

GCC construction is inherently multi-currency. The contractors who track that clearly will have cost reports they can actually explain — and projects where exchange rate movements don't quietly erode the margin their teams worked to earn.