Operating expenditure (OPEX) refers to the recurring costs of operating a business in its normal course — including personnel costs, property and occupancy costs, technology and software subscriptions, professional services, marketing, maintenance, and utilities. OPEX costs are expensed in the income statement in the period they are incurred, reducing profit immediately. This is their defining characteristic: unlike capital expenditure, OPEX does not create an asset on the balance sheet. It is consumed in the period.
The practitioner distinction that matters most for financial reporting: the OPEX versus CAPEX boundary is not always obvious in practice. A software implementation cost — the fees paid to consultants to configure an enterprise system — may be partially capitalised (development phase costs meeting IAS 38 criteria) and partially expensed (research phase and ongoing maintenance costs). Classifying all of it as OPEX understates assets and overstates current-period expenses. Classifying all of it as CAPEX overstates assets and understates expenses. The correct treatment requires judgment and documentation at the cost component level.
In the Context of the GCC
In government-linked enterprises and family conglomerates across the GCC, OPEX control is a recurring governance focus — particularly in environments where headcount-driven OPEX has grown faster than revenue during periods of expansion. Vision 2030 initiatives in Saudi Arabia, and parallel economic diversification programmes in the UAE and Qatar, have driven significant OPEX growth in both the public and private sectors — in hiring, in technology investment, and in professional services. Finance functions in these organisations are under increasing pressure to model OPEX productivity: what revenue is generated per unit of OPEX, and how does that ratio trend over time.
How This Connects to EPM
OPEX is the largest planning category in most enterprise EPM models. Workforce planning — the largest component of OPEX for knowledge-intensive businesses — is typically managed in a dedicated EPM workforce module, where headcount assumptions drive salary cost forecasts at the department level. Non-headcount OPEX is planned through a combination of driver-based assumptions (occupancy cost per square metre, IT cost per user, travel cost per headcount) and zero-based line item review for discretionary categories. The EPM model provides the framework; the quality of the OPEX plan depends on the quality of the drivers and assumptions fed into it.
What Goes Wrong
The failure mode that overstates profits through OPEX misclassification is the capitalisation of costs that should be expensed — most commonly, ongoing software maintenance and support fees, internal staff time allocated to projects on an approximate basis, and consultant fees for enhancement work on existing systems. When these costs are capitalised rather than expensed, the current period P&L is understated in expense (profits look higher), the balance sheet carries an inflated intangible asset, and future periods carry higher depreciation or amortisation charges. Auditors find this pattern regularly; the remediation requires a restatement of prior periods if the amounts are material.
How Loop Wise Solutions Encounters This
In EPM planning engagements, OPEX model design is the area where we spend the most time on governance — specifically on the rules for what is planned as OPEX versus what is capitalised. These rules must be agreed with the finance and accounting team before the EPM model is built, because the EPM model enforces whatever classification approach is embedded in it. If the capitalisation policy is ambiguous, the EPM plan will reflect that ambiguity.
