Joint Operating Committee - Capability Deployment, Part II
Today’s blog post examines the development of transaction templates and their associated Accounting Vouchers, together with the interfaces engineers and geologists will need to use them. These templates will support the planning and deployment of the commercial aspects of oil & gas operations, from filling a vehicle’s fuel tank to drilling a well. They will connect the work being undertaken with its financial consequences, providing visibility into commercial issues and opportunities as the project unfolds. This will substantially reduce organizational latency.
Accounting expertise will be available throughout. Engineers and geologists, however, must drive the operating requirements and help design the interfaces through their participation in our user community. Service providers will contribute the accounting expertise necessary to translate those requirements into dependable financial processes. We cannot build a system that meets your needs without comprehensive input and active participation from the engineering and geological communities.
These transactions may extend across several accounting months. Their associated Accounting Vouchers must maintain a continuous view of the project while recognizing costs and obligations in the appropriate accounting periods. Accruals will record costs already incurred for which invoices or final amounts remain outstanding. As actual charges become available, the corresponding accruals will be cleared or adjusted, ensuring that each cost is recorded once. Project completion will bring a reconciliation of recorded costs, outstanding obligations, and remaining estimates.
Once the transaction’s activities, responsibilities, and accounting treatment have been defined—with service providers supporting the accounting specifics—the template will provide the basis for what Synallagi describes as Autonomous Asynchronous Transaction Orchestration. This orchestration will coordinate the transaction as work progresses, information arrives, and authorized actions become due. The Accounting Voucher will record the financial consequences and retain the supporting evidence.
The engineer or geologist will manage the project according to their professional judgment and discipline, within the authority assigned to them. Our objective is to automate most routine accounting activity, with service providers managing accounting oversight, exceptions, reconciliation, and administration through Synnefa, our cloud offering. This will allow engineers and geologists to concentrate on the work and its commercial performance, supported by accounting that develops alongside the project.
1. Designing Transactions
Capturing the agreement
Designing Transactions establishes the business basis of an engagement before its recurring processing begins. The parties identify what will be delivered, how it will be measured, what value will be exchanged and how compensation will occur. The design captures their understanding while that understanding is available to the people making the agreement.
The Accounting Voucher provides the transaction-design capability. Accountants and the relevant business participants define the units of work, the beneficiary, the charging basis, the accounting destinations and the evidence required for processing. Standardizing, counting, valuing and compensating give a transaction an agreed meaning across organizational boundaries. Different Joint Operating Committees can use these common methods while retaining their particular contracts, operating configurations and capabilities.
The transaction design also identifies the event that causes work or AFE’s and Lease charges to arise. For production accounting, a production input can initiate the defined service-provider task, with billing based on the work rendered. The Accounting Voucher template supports reuse in subsequent months. Changes to the property or agreement must be reflected in the applicable version, while earlier configurations remain available for prior-period work, adjustments or corrections.
Connecting delivery and value
The financial integration adds the expected technical and commercial contribution to the engagement's description. Participants should be able to identify the problem, the proposed work, its anticipated cost and the result they intend to evaluate. An engagement to diagnose a well may deliver a reliable explanation and recommendations; an engagement to implement a correction may deliver a changed operating condition. Their acceptance evidence will differ.
Service delivery, payment entitlement and realized property performance are separate questions. An agreed service can be completed and payable before its effect on production or capital recovery is known. Recording the expected contribution enables later evaluation without silently changing the provider's agreed compensation into a performance-contingent arrangement.
The proposed automation follows the designed transaction, the applicable agreement and valid authority. It processes defined events and presents exceptions requiring attention. Accounting Voucher provides the accounting expression, including posting to the General Ledger. Business transaction design supplies the accounting and commercial basis; field direction proceeds through Operational Control.
The Synallagi transaction connects the applicable authorization, resource deployment, commitments and accounting results. Its design must retain the relationship between deployed financial resources and their authorized sources and destinations, through the Work Order for operational engagements and through Episteme for research collaboration. It must also accommodate approved changes without obscuring the basis on which earlier work occurred.
2. Operational Control
Innovation and execution
An innovative producer needs both the freedom to develop better methods and the ability to execute work under recognized authority. The Joint Operating Committee may assemble a temporary operating organization from several producers, vendors, suppliers and service providers. Everyone involved needs to understand who directs the work, which instruction applies and what has already been authorized.
Industrial Command & Control establishes that operational chain of command. The Job Order provides the particular field instruction issued by its recognized and designated authority. Field operations require the appropriate Job Order, and execution follows its authorized scope.
Job Order and contractual authority
Work Orders and Job Orders are mutually exclusive business tools. The Work Order deploys financial resources and supports specialist assignments, time and charging. The Job Order directs field action. Operational financial resources are distributed through a Work Order. Episteme retains the research functions previously housed in Work Orders and deploys independently approved participant funding without a mandatory separate Work Order. The operational financial deployment requirement does not make the Work Order a field instruction or prescribe a parent-child relationship between the two tools.
The user community will determine the shared references, detailed relationships and amendment procedures. The distinction already established is that operational financial deployment uses the Work Order, while operational direction uses the Job Order under recognized command authority. Episteme retains financial deployment and related controls for research collaboration.
A Job Order has no spending authority outside the previously approved contractual arrangements for its listed tasks. An instruction to perform work must therefore remain within the relevant contract and authority. Where a proposed action exceeds those arrangements, the required contractual and expenditure approvals must be addressed before the expanded action proceeds. The detailed amendment procedure remains for the user community to specify.
Acting on a financial finding
A financial anomaly should reach the people able to investigate its cause and assess a response. It may reveal a measurement problem, an unexpected cost, a production deficiency or an assumption that no longer holds. The finding initiates review; it does not establish a physical diagnosis or authorize expenditure by itself.
Technical and commercial participants develop the response under the applicable governing arrangements. Investigation, correction, preservation, suspension and restoration each require the appropriate authority and work arrangements. This gives financial information a route into operational decisions while preserving responsibility for those decisions.
3. Purchase Order
Discretionary contract control
Purchase Order functionality is discretionary and selected by the producer. Standard Synallagi configuration excludes it. Where selected, it supports the control of vendor relationships and significant contracts within the Accounting Voucher environment.
Its purpose includes qualifying vendors, conducting the bidding process, recording the agreed work and controlling payment against contractual conditions. Selection must consider the vendor's ability to perform the required work and meet the project's criteria. The lowest submitted price does not by itself demonstrate that capability.
Payments and coding
The approved contract supplies the basis for prepayments, progress payments, partial payments, holdbacks and final acceptance, as applicable. The Purchase Order records the relevant conditions so that Accounting Voucher processing can apply them. Final payment follows the contract's completion and acceptance requirements, including any unresolved holdbacks or other conditions.
The Purchase Order number does not replace or change the AFE, Cost Center or Lease charge code. Expenditure still reaches the appropriate accounting destination and retains its capital or operating classification. A payment under a Purchase Order must remain distinguishable from the evidence used to judge the engagement's eventual commercial contribution.
Producers choosing this functionality gain a further means of expressing and administering their contract controls. Its discretionary status does not remove the need for valid contracts, spending authority or accounting when the feature is absent. The detailed facility-project purchasing example and implementation of purchasing services remain matters for user-community development.
4. Work Order
Assigning expertise and recording its cost
The Work Order is the means through which financial resources are deployed for operational engagements. It also records a specialist's approved assignment and provides the basis for recording time and charging the appropriate beneficiary. It supports the deployment of producer capabilities across Joint Operating Committees and preserves the terms needed to recover the cost of providing them.
All financial resources distributed for the operational engagement pass through the Work Order. The record connects the approved source of those resources with their intended use, beneficiary, commitments and charging destinations. This deployment role operates within the existing expenditure and contractual authorizations; it does not originate an AFE or create authority beyond those arrangements.
The assignment identifies the person or resource, the work, its beneficiary, the agreed charging basis and the authorized accounting destinations. Time can be attributed to the applicable AFE, Lease, project, research or administration account as the work progresses. Accounting Voucher provides the accounting representation and General Ledger posting, and Partnership Accounting applies the relevant participant allocations and joint-account consequences. The Work Order's resource-deployment role remains connected to those accounting and payment functions; it does not establish a separate settlement system.
A specialist may work across several properties. Each assignment must remain identifiable so that one Joint Operating Committee's work is not charged to another and the same time is not charged twice. Resource commitments must also remain visible to those authorized to make them. A listing of expertise does not establish that the specialist is available or already assigned.
Research collaboration is organized through Episteme, described in section 9. Episteme retains the research functions previously housed in Work Orders, including participant contributions, funding, allocation, approvals and accounting support. Participants' approved time and charging arrangements can support research within that arrangement without a mandatory separate Work Order.
Example: a completion specialist
Producer X participates in Joint Operating Committee Y. Y requires X's completion capability, listed in Knowledge & Learning. X's COO proposes a trusted former employee as Senior Engineer. The engagement is agreed through Y's Joint Venture Agreement operating procedure, recorded through a Work Order and charged for the authorized hours against the completion AFE.
Where the discretionary Revenue Per Employee method is selected, People, Ideas & Objects example uses a $3 million annual reference and an agreed $300 hourly rate. These are illustrative inputs. The example does not establish a mathematical conversion between them or presume that the former employee is currently employed by X. The contracting and representation arrangement, and the rate derivation under the industry-based standard methodology, require specification.
The financial integration adds the expected completion outcome and a subsequent review of its technical and commercial effects. The record should allow participants to distinguish work accepted, charges processed, payment received and improvement demonstrated. Any field instructions retain their separate Job Order and Industrial Command & Control basis.
5. Lease
The operating accounting context
Lease is the accounting feature derived from the petroleum lease that captures the Joint Operating Committee's revenue, royalties and operating costs. It provides the monthly breakdown of those amounts through the financial statements being prepared. It separates day-to-day operating accounting from special-purpose capital expenditure recorded against an AFE.
No capital costs are chargeable to Lease. A shared view of property performance must preserve that separation. Bringing operating results and capital-recovery information together for analysis does not move capital expenditure into the Lease accounts.
Capability Deployment uses the Lease context when authorized work and charges relate to operations. The applicable authority for Lease spending forms part of the Synallagi transaction; the Lease charge code alone does not provide spending authority. The Work Order deploys the approved financial resources, while the Lease supplies the operating accounting destination.
The underlying record should retain the well or activity to which an amount is attributable and identify the basis of shared allocations. This detail permits an individual well's performance to be examined without losing the Joint Operating Committee's overall accounting relationship.
Actual costs and comparable information
The financial integration requires actual administrative and service-provider charges to remain visible. Where a cost is shared, the allocation method must be identifiable. A standard method supports comparison between properties, while the underlying information must preserve material differences in their physical conditions, contracts and work performed.
Monthly reporting supplies a period view. Current work may also need the latest available accounting and commitments. Users must be able to distinguish the selected period, estimates and subsequent amendments. These distinctions allow engineers and geologists to use financial results as evidence without treating every variance as a confirmed change in physical performance.
Lease serves this accounting purpose. Administration of petroleum rights and interests continues through the responsible property and agreement functions.
6. AFE — Authorization for Expenditure
Purpose, approval and commitments
The Authorization for Expenditure establishes the approved budget and purpose for capital outlays. It records the required participating Joint Operating Committee approvals and reports expenditure against the agreed budget. Supplementals and other approved changes form part of the continuing authorization history.
Deployment must remain connected to that approved purpose and the contractual arrangements for the work. Financial resources authorized through the AFE are deployed through Work Orders for operational engagements and through Episteme for research collaboration. The applicable AFE authorization, deployment authority and changing commitment position form part of the relevant Synallagi transaction context.
Budget availability must reflect commitments already made as well as expenditure already recorded. Live or near-live information must support controls that prevent the same available resources from being committed again; refreshing a displayed balance alone is insufficient.
The user must also be able to return to the relevant accounting period or production month. The historical view must preserve the approval and accounting context applicable at that time.
Commercial evaluation of additional expenditure
The financial integration connects a proposed capital engagement to its expected contribution. Participants need to see the additional expenditure, the production it is expected to enable or preserve, its timing and its effect on continuing capital recovery. A workover may improve performance without adding reserves; its commercial case should describe the benefit actually expected.
Earlier investment remains visible when additional work is undertaken. New expenditure cannot make an earlier recovery deficiency disappear from the commercial evaluation. The evaluation should distinguish opening unrecovered expenditure, additions, the actual contribution toward recovery and the remaining recovery requirement, using a defined method that avoids counting the same deficiency twice.
This is a management-accounting evaluation. Financial-reporting depletion, the carrying value of assets and the commercial recovery requirement remain separate measures. Any allowance for replacement of produced reserves must also be explicit and distinguishable from recovery of expenditure already incurred. This specification adopts no universal recovery period or return assumption and does not direct that operating losses be capitalized.
AFEs for a Joint Operating Committee are approved by its members under the applicable governing arrangements. An independently authorized producer research AFE retains that producer's approval basis. Approved AFE funding is appropriate for eligible Work Order or Episteme activity; the deployment record does not originate or enlarge that authority.
Research funding
An independently approved producer or Joint Operating Committee AFE may fund an eligible research contribution. A producer may also independently authorize an AFE for its research budget. Episteme can deploy the resources made available under those independent approvals; it cannot originate an AFE. Episteme retains the research functions previously housed in Work Orders and deploys those resources within the approved arrangements, without a mandatory separate Work Order. Episteme does not create the funding authority it relies upon.
Funding source and accounting classification remain distinct. Research contributions must be classified according to their nature and the applicable accounting treatment. A capital account cannot accept an operating charge merely because funding was described through an AFE. The precise mapping is a user-community development matter.






