Joint-venture billing: preserve the basis behind shared charges

Topics: joint venture accounting oil and gas, joint interest billing evidence, JV cost allocation audit, operator partner billing statement

When an upstream or midstream operator issues a monthly Joint Interest Billing (JIB) statement, non-operating partners rarely dispute the arithmetic of multiplying a gross number by their participating-interest percentage. Disputes arise because the statement hides how the gross number entered the joint pool: whether a contractor invoice belonged to an approved Authorization for Expenditure (AFE), why a shared shorebase cost used a provisional split instead of actual vessel usage, whether a sole-risk appraisal expense leaked into the general equity group, or whether corporate IT charges were billed alongside contractual overhead recovery.

The core operational decision in joint-venture accounting is to design a four-layer JIB evidence bridge between the operator's general ledger and the partner statement so every shared charge preserves its source transaction ID, its governing AFE or budget authority, its participating-interest (PI) equity group, and its verified allocation driver. India's exploration and production blocks operate under Production Sharing Contracts (PSC), Revenue Sharing Contracts (RSC), and Joint Operating Agreements (JOA) tracked across operator and partner returns, as summarised in the Directorate General of Hydrocarbons (DGH) Annual Report 2024–25. Because cost recovery, partner cutback, and capital versus revenue presentation depend on the exact executed contract and applicable accounting standards—including property, plant and equipment recognition under Ministry of Corporate Affairs Ind AS 16—software workflows should preserve line-item evidence rather than hard-coding legal or statutory conclusions.

Why summary JIB statements trigger partner audit exceptions

In many ERP systems, the monthly cutback run aggregates thousands of vendor invoices, warehouse issues, timewriting entries, and corporate allocations into ten or twelve summary cost-element rows before multiplying by each partner's participating interest. That compression destroys the three boundaries that non-operating partner (NOP) auditors and joint-venture controllers need to verify:

1. Direct block costs versus shared multi-block pool allocations: A wireline invoice incurred directly on Well W-07 inside the block needs AFE and service-entry verification. By contrast, a shorebase warehouse or offshore supply vessel shared across three blocks requires both source-voucher proof and a signed monthly allocation-driver table (such as verified deck-tonnage-days or reconciled production-accounting volumes).
2. General joint operations versus sole-risk / non-consent elections: Under a Joint Operating Agreement, a partner may elect not to participate in a specific appraisal zone or deepenings scope. If the work order or WBS element is mapped to the default block equity group instead of a dedicated sole-risk equity group, the ERP cutback engine bills the non-consenting partner by mistake.
3. Contractual indirect/overhead percentage versus direct-charged corporate costs: Accounting procedures annexed to a JOA or PSC typically define a specific sliding-scale or percentage fee to compensate the operator for general administrative overhead, while prohibiting separate direct charges for routine corporate headquarters functions unless specifically approved.

1. 1. Validate venture, equity-group & AFE codingBefore running monthly cutback, verify every WBS element and cost centre posts to the authorised participating-interest equity group (separating general joint operations from sole-risk scopes) and links to an active AFE or operating budget line.
2. 2. Lock actual monthly allocation driversReplace provisional budget splits on shared logistics, aviation, and processing pools with signed monthly operational drivers (vessel deck-tonnage-days or reconciled production volumes) before executing cost-centre assessments.
3. 3. Filter eligible base for operator indirectsRun the contractual overhead rule only against eligible joint expenditure—automatically excluding sole-risk WBS elements, unapproved corporate recharges, and prior-period disputed items.
4. 4. Publish drill-down JIB pack & isolate disputesGenerate the partner statement with line-item voucher drill-down; if a non-operating partner raises an audit query within the contractual window, tag only the contested line as Disputed-On-Hold while settling approved lines.

Review boundary: Partner cutback rules, overhead eligibility, and audit dispute windows depend on the executed JOA/PSC accounting procedure and qualified finance review ([O064](O064-accounting-software-fit.md)).

Worked example: Reconciling monthly statement JIB-2026-10 for Block JV-B19

All entities, block identifiers, participating interests, and rupee figures below are illustrative teaching examples constructed to demonstrate pre-cutback JIB reconciliation.

Assume Offshore Block JV-B19 is governed by a Joint Operating Agreement between Operator OP-A (55.00% Participating Interest), Non-Operating Partner NOP-B (30.00%), and Non-Operating Partner NOP-C (15.00%), summing to the full participating interest (0.5500 + 0.3000 + 0.1500 = 1.0000). For October 2026, Operator OP-A's preliminary ERP cutback run generates draft statement JIB-2026-10 showing a gross joint-account pool of ₹4,68,60,000 and billing NOP-B (30.00% share) ₹1,40,58,000.

Before releasing the statement—or during NOP-B's pre-settlement desk review—the JV accounting team reconciles the four cost categories against their underlying evidence:

1. Direct field operations & workover (AFE-2026-09):
   • Draft billing: ₹2,60,00,000 gross (NOP-B 30.00% share = ₹78,00,000).
   • Evidence check: Every line traces to approved AFE-2026-09 (authorised limit ₹2,85,00,000), matched purchase orders, and signed wellsite service entry sheets.
   • Verified amount: ₹2,60,00,000 gross (₹78,00,000 for NOP-B; variance ₹0).
2. Shared onshore supply base & marine vessel pool (POOL-MAR-04):
   • Draft billing: Total monthly shorebase and supply-vessel pool cost across Blocks JV-B19 and JV-B22 is ₹1,20,00,000. The draft cutback used a provisional budget split of 0.7500 (75.00%) to JV-B19, charging ₹90,00,000 gross (₹27,00,000 to NOP-B).
   • Evidence check: Signed October marine-manifest logs show JV-B19 consumed 450 deck-tonnage-days out of 750 total deck-tonnage-days across both blocks: Verified Allocation Factor = 450 deck-tonnage-days ÷ 750 deck-tonnage-days = 0.6000 (60.00%)
   • Verified amount: 0.6000 × ₹1,20,00,000 = ₹72,00,000 gross (NOP-B 30.00% share = 0.3000 × ₹72,00,000 = ₹21,60,000). This removes ₹18,00,000 gross (₹5,40,000 for NOP-B) that belonged to Block JV-B22.
3. Sole-risk appraisal testing on Zone Z-4 (WBS-SR-Z4):
   • Draft billing: ₹80,00,000 gross was booked under the default block equity group EG-GEN, billing NOP-B ₹24,00,000 (30.00%).
   • Evidence check: Formal election notices show NOP-B elected non-consent on Zone Z-4; only OP-A and NOP-C participated under Sole-Risk Equity Group EG-SR-Z4 (OP-A 55/70 = 78.5714%, NOP-C 15/70 = 21.4286%, NOP-B 0.0000%).
   • Verified amount in General Joint Pool: ₹0 (NOP-B share = ₹0; ₹80,00,000 moves to separate sole-risk statement JIB-2026-10-SR, reducing NOP-B's general billing by ₹24,00,000).
4. Operator indirect recovery & corporate IT recharge:
   • Draft billing: The draft statement included a ₹30,00,000 direct recharge from OP-A's corporate headquarters IT cost centre plus a 2.00% indirect fee calculated on ₹4,30,00,000 (₹2,60,00,000 + ₹90,00,000 + ₹80,00,000), adding ₹8,60,000 for a combined charge of ₹38,60,000 gross (₹11,58,000 to NOP-B).
   • Evidence check: Under the illustrative JOA accounting procedure, general corporate IT infrastructure is covered by the 2.00% indirect fee unless covered by a specific partner-approved AFE, and sole-risk expenditure is excluded from the general indirect base. The eligible general joint cost base is: Eligible Indirect Base = ₹2,60,00,000 (Direct) + ₹72,00,000 (Verified Shared Pool) = ₹3,32,00,000 Verified Indirect Fee (2.00%) = 0.0200 × ₹3,32,00,000 = ₹6,64,000 gross
   • Verified amount: ₹6,64,000 gross (NOP-B 30.00% share = 0.3000 × ₹6,64,000 = ₹1,99,200; reduction of ₹31,96,000 gross or ₹9,58,800 for NOP-B).

Draft Gross Pool₹4,68,60,000 (NOP-B 30% draft bill: ₹1,40,58,000)

Verified General Pool₹3,38,64,000 (Direct ₹2.60 Cr + Shared ₹72.0 L + Indirect ₹6.64 L)

Verified NOP-B Share₹1,01,59,200 (0.3000 × ₹3,38,64,000)

Overbilling Prevented₹38,98,800 (NOP-B share) / ₹1,29,96,000 (General pool)

Arithmetic check: ₹1,40,58,000 (draft NOP-B) − ₹5,40,000 (shared logistics true-up) − ₹24,00,000 (sole-risk reclassification) − ₹9,58,800 (ineligible IT recharge & excess indirect base) = ₹1,01,59,200 verified payable.

Compare ERP JVA configuration vs external spreadsheet cutback

Operators and non-operating partners evaluating oil and gas accounting software fit typically compare native ERP Joint Venture Accounting (JVA) engines against spreadsheet-based post-close cutback workbooks:

Observable acceptance tests for JIB evidence workflows

Before closing a JVA configuration or partner-reporting workflow, run three acceptance tests on a staging ledger:

• ACT-O061-01 (Sole-risk equity-group isolation test): Create a test work order under a sole-risk WBS element (EG-SR-Z4 where NOP-B = 0.00%) and attempt to post a ₹10,00,000 contractor service entry using the block's default cost centre. Pass condition: The ERP derives the sole-risk equity group EG-SR-Z4 from the WBS element (overriding the default cost-centre rule) and allocates ₹0 to NOP-B in the simulated cutback run.
• ACT-O061-02 (Provisional-driver block on final JIB release): Enter a provisional statistical key figure (0.7500) for a shared marine pool and attempt to execute a Final (rather than Provisional) monthly JIB cutback run without uploading a signed actual driver table for the period. Pass condition: The pre-cutback validation report flags the shared pool assessment as Provisional Driver Unverified and blocks Final statement generation until the period driver (0.6000) is confirmed by the operations controller.
• ACT-O061-03 (Line-level partner audit dispute hold): Simulate a non-operating partner dispute against a single ₹30,00,000 corporate recharge line on a ₹4,68,60,000 statement. Pass condition: The system places only the disputed line ID into Audit Query — On Hold with an ageing timer and owner, while allowing the undisputed balance to clear against cash calls and partner receivables without manual journal splitting.

Summary and next actions

Preserve the operational and contractual basis behind every shared charge before the monthly cutback run executes:

1. Audit your active WBS and cost-centre mapping table: verify that every open AFE, reimbursable work order, and sole-risk project points to the exact participating-interest equity group authorised under the block's JOA or PSC.
2. Replace fixed percentage splits on shared shorebases, vessels, and processing facilities with dated monthly statistical key figures backed by signed operational logs or reconciled production-accounting volumes.
3. Configure the operator-overhead calculation schema to exclude ineligible cost elements—including sole-risk scopes, prior-period adjustments, and unapproved headquarters recharges—before computing the contractual percentage fee.
4. Run acceptance tests ACT-O061-01 to ACT-O061-03 on one prior month's JIB statement to verify that every billed row drills down to an approved AFE, source voucher, and signed allocation driver.