How to Strengthen CAPEX OPEX Governance in Upstream E&P
Cost governance in upstream E&P are not effective when approval, evidence, and accountability do not move at the same speed as field operations. That risk is high where operators, non-operators, vendors, auditors, and regulators all sit inside a contract-driven environment.
CAPEX and OPEX decisions must stand up to internal review, joint venture scrutiny, and regulatory examination. A strong framework reduces disputes, protects cost recovery, and gives management a clear view of commitments before money is spent.
Start with the Indian upstream contract environment
In India, upstream E&P governance is shaped by contract terms, joint venture arrangements, Directorate General of Hydrocarbons guidance, and audit expectations. The exact obligations depend on the block, bid round, contract model, and participating interest structure.
Older blocks may operate under Production Sharing Contracts. Later arrangements may follow Revenue Sharing Contract terms or HELP-era models. Each structure has its own treatment of costs, approvals, reporting, procurement, accounting, and government interface.
The practical point is simple. Company policy alone is not enough. CAPEX and OPEX governance must reflect:
The E&P contract and accounting procedure
The joint operating agreement
The annual work programme and budget process
The management committee or operating committee approval route
DGH submissions and compliance expectations
Internal delegation of authority
Procurement and contracting rules
Audit and cost recovery requirements
A good framework connects these sources. It avoids parallel systems where technical teams follow the work programme, finance follows the budget, procurement follows vendor rules, and legal reviews only after disputes arise.
For Indian upstream assets, capex opex governance oil gas exploration production controls should sit at the centre of block management. The goal is not paperwork for its own sake. The goal is defensible spending.
Build approval hierarchies that match risk and contract duties
Approval hierarchies sometimes fail because they are built around job titles, not decision risk. In upstream E&P, a low-value item can carry high contractual exposure. A variation order on a drilling contract, a change in rig standby treatment, or a technical change in well design may affect both cost and recoverability.
The approval matrix should separate four types of authority.
Decision type | What it covers | Who should review it |
Technical authority | Scope, design basis, execution method, HSE need | Subsurface, drilling, facilities, operations |
Financial authority | Budget availability, cost coding, cash call impact | Finance, cost control, asset accounts |
Contract authority | Tender route, contract terms, variation rights | Contracts, procurement, legal |
JV and regulatory authority | Committee approval, DGH alignment, audit trail | Asset management, compliance, company secretariat |
This split prevents one common mistake. A finance approval does not prove that the expenditure is contractually sound. A technical approval does not prove that the cost can be booked to the right account or claimed under the contract.
Set clear thresholds for CAPEX
CAPEX decisions need stage gates. This is critical for drilling campaigns, offshore facilities, development wells, subsea systems, pipelines, processing units, and long-lead equipment.
A practical CAPEX hierarchy should include:
Concept approval
Budget provision in the approved work programme
Authority for expenditure
Tender approval
Contract award approval
Variation approval
Commitment tracking
Completion and close-out
The authority for expenditure should not become a formality. It must explain the scope, cost estimate basis, contingency, schedule, contract strategy, and approval status under the JV framework.
For example, an offshore well work programme may be approved at a high level. But each major commitment still needs support. Rig services, casing, cementing, marine spread, well testing, drilling offshore Logistics, and specialist tools may all need separate approval and cost tracking.
Set practical controls for OPEX
OPEX governance needs speed. Field operations move fast. Maintenance, logistics, consumables, safety work, and production support cannot wait for slow approval loops.
The answer is pre-approved operating envelopes. Use annual or quarterly operating budgets and service level controls. Then require stronger approval when spending exceeds defined limits or changes the nature of the scope.
OPEX controls should address:
Recurring contract spend
Emergency work
Standby and idle time
Consumables and rentals
Warehouse issues and inventory drawdowns
Production support services
Shared costs across blocks or fields
Charges from affiliates or related parties
Emergency work deserves special treatment. It must allow quick action for safety, environment, well control, or production integrity. It must also require a post-facto approval note, incident reference, cost summary, and evidence pack.
Make audit-readiness part of daily work
Audit-readiness is not an annual exercise. It is a way of working.
Indian upstream companies face reviews from internal audit, statutory auditors, JV partners, government-appointed auditors, and regulatory stakeholders. Questions often arise years after the activity. By then, teams have changed, vendors have moved on, and informal explanations are hard to defend.
A spend item should pass three tests.
Was it approved before commitment?
The file should show that the right people approved the scope, value, budget head, contract route, and JV requirement before the company became liable.
Was it incurred for contract operations?
The record should link the expenditure to an approved work programme, field operation, well, facility, block, or project.
Was it reasonable and supported?
The file should contain bids, technical evaluations, commercial comparisons, rate references, invoices, work completion certificates, measurement sheets, goods receipts, and variation notes where needed.
Cost recovery challenges often start with gaps in evidence. The service may have been real. The work may have been necessary. But if the record does not prove it, the company carries risk.
Use an audit evidence index
Every material CAPEX or OPEX file should have an evidence index. This avoids last-minute searches and inconsistent file building.
A basic evidence pack should include:
Approved work programme and budget reference
Authority for expenditure or purchase requisition
Bid documents and clarifications
Technical evaluation
Commercial evaluation and negotiations thereof
Award approval
Contract and amendments
Purchase order or service order
Change orders and variation approvals
Work completion or service entry record
Invoice and payment approval
Cost allocation worksheet
JV approval or notification where required
Close-out note
For high-value CAPEX, add basis of estimate, cost risk register, schedule baseline and commissioning or completion evidence.
For OPEX, add rate verification, consumption records, field service tickets, daily reports, equipment logs, and allocation basis across fields or blocks.
Raise documentation standards across the contract life cycle
Governance fails when documentation starts too late. A contract file built after award will miss critical reasoning. A variation file created after invoice receipt will not show why the change was valid.
Documentation must follow the full life cycle.
Before tender
The file should state why the service or material is needed. It should connect the requirement to an approved budget line or operational need. It should also state the contract strategy.
Key questions include:
Is competitive bidding required?
Is single sourcing allowed under the contract and company policy?
Does the scope involve related-party work?
Does the procurement need JV consent?
Is DGH or management committee reporting expected?
Are local taxes, customs, duties, or import rules material?
Is the scope CAPEX, OPEX, inventory, or mixed?
This early classification matters. Wrong classification can distort budgets, affect cost recovery, and weaken management reporting.
During evaluation and award
Technical and commercial evaluations should be separate, documented, and signed by authorised reviewers. Exceptions need clear justification.
During execution
Execution records prove that the company received what it paid for. This is where upstream files often weaken.
Field teams should maintain daily records, service sheets, rig reports, material receipts, inspection reports, and work completion certificates. Finance and contracts teams should not approve invoices based only on vendor claims.
Variation control is critical. A variation should show the reason, contractual basis, cost effect, budget effect, and approving authority. It should not be hidden inside invoice approval.
Align joint venture operations with the governance model
Joint venture governance adds another layer. The operator spends money on behalf of all partners. Non-operators need visibility. The contract may require approval through a management committee, operating committee, technical committee, or other agreed mechanism.
This creates a simple rule. Internal approval does not replace JV approval.
The operator should maintain a clear map of decisions requiring partner or committee approval. This map should be part of the governance manual and not buried inside the joint operating agreement.
Common JV approval areas include:
Annual work programme and budget
Budget revisions
Major procurement awards
Sole-source awards
Material variations
Development plans
Drilling programmes
Abandonment and decommissioning plans
Asset transfers and shared cost allocations
Insurance, claims, and major disputes
Cost reporting should match the chart of accounts agreed under the contract. Partners should be able to trace actual costs to budget lines and approved activities.
Cash calls need the same discipline. They should link to approved budgets, forecast activity, prior period expenditure, and upcoming commitments. Weak cash call support creates disputes and delays.
Treat non-operator challenges as a governance test
Non-operator queries should not be seen as administrative irritation. They test the strength of the file. Strong operators respond with evidence. Weak operators respond with explanation alone. The difference matters when a later audit or government review raises the same point.
A query register helps. It should track the issue, amount, contract reference, owner, response date, evidence shared, and final status. Repeated queries show where the framework needs repair.
Address common governance failures before they become audit issues
Many upstream governance failures are predictable. Most do not start with fraud. They start with pressure, poor handovers, unclear authority, or field urgency.
Here are the failures that deserve early attention.
Spending starts before approval
This is common in drilling and operations. A verbal instruction is given to avoid delay. The purchase order follows later. The invoice arrives before the approval file is complete.
This creates audit exposure. It also weakens commercial control if the vendor disputes scope or rates. Fix it with clear commitment rules. No work starts without an authorised contract, purchase order, call-off, or emergency approval route.
Budget approval is confused with contract approval
An approved budget line only means funds are planned. It does not prove that procurement rules, JV approvals, or contract conditions have been met.
Fix it by separating budget release from award approval. The approval note should state both conditions clearly.
Variations become routine
Small variations can hide major scope drift. Repeated extensions can also avoid fresh tendering. Fix it with cumulative variation tracking. Once variations cross a defined threshold, require higher approval and fresh commercial review.
Costs are booked to the wrong block or activity
Shared services, logistics, warehouses, marine support, and personnel costs can be misallocated. This creates partner disputes and audit exceptions.
Fix it with documented allocation rules. The basis may be time, usage, production, headcount, activity, or another agreed measure. The method must be consistent and approved.
Related-party transactions lack independent support
Affiliate services can be valid. They also attract scrutiny. The file should prove need, fair pricing, actual service delivery, and compliance with the contract. Fix it with benchmark support, clear service descriptions, and independent review where value or sensitivity is high.
Close-out is ignored
Projects close technically, but commercial files remain open. Unused commitments, retention, materials, warranties, and final invoices remain unresolved.
Fix it with a close-out checklist. Make close-out a required step before final cost reporting.
Bring in independent advisors where governance needs outside assurance
Independent advisors can help when internal teams are stretched, when a block is moving into a development phase, or when audit issues have already surfaced.
Firms such as FINLOG E&P Oil & Gas Consultants can support operators and joint ventures by reviewing the governance structure against contract duties, DGH-guided expectations, and industry working practices. The value lies in independence and E&P depth.
Typical support areas include:
Designing delegation of authority matrices for CAPEX and OPEX
Reviewing joint venture approval workflows
Building contract compliance manuals
Preparing audit evidence standards
Reviewing procurement and tender files
Testing cost allocation methods
Supporting responses to audit queries
Training asset, finance, contracts, and operations teams
Improving management committee submission packs
Reviewing high-risk contracts before award or variation
An independent advisor should not replace management accountability. The operator remains responsible for decisions. The advisor helps build a governance system that is clear, documented, and able to withstand scrutiny.
The best time to involve advisors is before a major campaign, not after the audit notice arrives. Development projects, drilling campaigns, large offshore service contracts, and JV disputes all benefit from early governance review.
A practical governance checklist for upstream E&P
Use this checklist to test whether a CAPEX and OPEX framework is fit for Indian upstream operations.
Governance area | Minimum standard |
Contract alignment | The framework maps contract, JOA, DGH-related reporting, and company policy requirements |
Approval hierarchy | Technical, financial, contract, and JV approvals are defined separately |
Budget control | Work programme, budget, AFE, and commitment tracking are linked |
Procurement | Tendering, exceptions, awards, and variations have documented approval |
Documentation | Each file has a complete evidence index |
Audit-readiness | Records prove approval, necessity, reasonableness, and delivery |
JV governance | Partner approvals, queries, and cost reports are tracked |
Cost allocation | Shared costs follow approved and supportable methods |
Variations | Scope and price changes are tracked on a cumulative basis |
Close-out | Contracts and projects close with final cost, claims, and evidence checks |
A framework that passes this test will not remove all disputes. It will reduce weak spots. It will also make reviews faster and less disruptive.
FAQ
What is the difference between CAPEX and OPEX governance in upstream E&P?
CAPEX governance controls long-term asset investments such as wells, facilities, pipelines, and major equipment. OPEX governance controls recurring and operating costs such as services, maintenance, logistics, rentals, and production support. Both need approvals, budget control, and evidence.
How does DGH guidance affect CAPEX and OPEX decisions?
DGH does not run a company’s internal approval process. But Indian upstream contracts, reporting expectations, and government oversight create a framework that operators must respect. Spending should match the approved work programme, contract terms, accounting procedure, and JV approval route.
Why do upstream cost recovery disputes arise?
Disputes often arise because approval was late, documentation was weak, costs were misclassified, procurement exceptions were not justified, or shared costs were not allocated clearly. Many disputes are evidence problems rather than technical problems.
When should an operator review its governance framework?
A review is useful before a drilling campaign, field development, major contract award, annual budget cycle, audit, JV dispute, or change in operatorship. It is also useful when repeated partner queries point to the same control gap.
Can independent advisors help with audit responses?
Yes. Independent advisors can review files, identify evidence gaps, prepare structured responses, and recommend process fixes. They can also help prevent repeat findings by improving approval, documentation, and reporting standards.
The takeaway
Strong CAPEX and OPEX governance in upstream E&P is built before money is spent. It starts with contract alignment. It then moves through clean approval hierarchies, disciplined procurement, audit-ready documentation, and active JV governance.
For Indian upstream operations, this discipline is not optional. It protects cost recovery, reduces partner disputes, and supports regulatory confidence. Independent advisors such as FINLOG E&P Oil & Gas Consultants can add value when the framework needs outside review, stronger controls, or better evidence standards.
The test is simple. If a reviewer asks why money was spent, who approved it, how the vendor was chosen, where the cost was booked, and whether the work was delivered, the answer should be visible in the file.
Comments