Order-to-Cash

Order-to-cash (O2C) in oil and gas differs fundamentally between upstream operators selling production, midstream companies billing for transportation and processing, and oilfield services companies billing for field work. Each sub-type has O2C requirements that general ERP handles imperfectly — and the wrong ERP configuration for your O2C model creates month-end close delays and revenue leakage.

O2C for upstream E&P: production to payment

For upstream operators, O2C is production-to-payment rather than a traditional sales cycle. There is no sales order — production flows to a purchaser under a term gas marketing contract or crude oil purchase agreement. The process steps are:

1. Production volumes recorded and allocated by well and lease
2. Production sold at index price (NYMEX, OPIS) plus or minus a differential per contract
3. Revenue distribution calculated to working-interest owners, royalty owners, and ORRI holders
4. Purchaser remittance received and reconciled to the revenue run
5. Disbursements made to revenue owners with accompanying revenue statements

The ERP must handle variable pricing — gas price at point of sale differs from wellhead price by gathering, compression, and transportation charges — and must apply the correct deduction structure to each revenue owner based on their specific lease terms. This is not standard AR functionality. Purpose-built O&G systems and SAP IS-Oil handle it natively; general ERP does not.

O2C for midstream: tariff billing

Midstream companies charge shippers for gathering, compression, processing, and transportation under FERC tariffs or negotiated agreements. The O2C process involves:

• Measuring volumes at custody transfer points
• Applying tariff rates per MCF or barrel per the transportation agreement
• Producing monthly invoices to shipper customers
• Managing volume imbalances between nominated and actual volumes
• Collecting payment and applying to the customer account

High-volume tariff billing at scale — hundreds of shippers, multiple receipt and delivery points, tariff schedules that vary by contract — requires ERP configuration that most mid-market systems don't support without custom development. SAP, Oracle, and IFS handle midstream tariff billing more readily than Dynamics 365 or NetSuite.

O2C for oilfield services: job billing

Oilfield services O2C is closest to standard ERP AR. The distinguishing challenge is field ticket integration — invoices need to be generated quickly after job completion because operators pay on net-30 or net-45 terms and late invoicing compresses cash flow. Mobile field ticket apps that push directly to ERP AR reduce the billing lag from 5–10 days to same-day.

Revenue recognition under ASC 606 adds complexity for long-term contracts — a multi-stage completion job or a drilling contract that spans months needs percentage-of-completion accounting, not point-in-time revenue recognition. NetSuite, Oracle, and Workday handle ASC 606 natively; Acumatica and Dynamics 365 require more configuration.

Choosing the right ERP for your O2C model

For upstream production revenue: SAP IS-Oil, Oracle JVM module, and purpose-built O&G systems handle production-to-payment O2C correctly. For midstream tariff billing: SAP, Oracle, and IFS are the primary options. For oilfield services billing: Dynamics 365, NetSuite, and Acumatica all handle service-order billing with appropriate configuration.

Book an assessment to identify which O2C model applies to your operation and which ERP handles it without significant custom development.