Procure-to-Pay

Procure-to-pay (P2P) in oil and gas has requirements that standard ERP P2P modules don't anticipate: AFE-coded purchase orders for capital expenditure, three-way matching against field receiving tickets rather than warehouse receipts, service order management for oilfield contractors, and the split of operating versus capital costs at the invoice level.

What P2P in oil and gas ERP must handle

AFE-coded purchase orders. Every capital purchase in E&P — drilling bits, casing, wellhead equipment, completion materials — is charged against an AFE. The purchase order must carry the AFE number and the expense code that determines whether the cost is IDC (intangible drilling cost) or tangible equipment for depletion purposes. ERP P2P that doesn't model AFE coding forces accountants to manually allocate capital purchases after the fact.

Joint-interest cost allocation. When a purchase serves a well or lease with working-interest partners, the cost must be split to each partner's decimal interest at the time of invoice processing — not at month-end as a batch allocation. Getting this wrong in the AP module means JIB statement errors downstream, which generates partner disputes.

Field receiving and oilfield services invoices. Oil and gas vendor invoices often don't match a clean three-way match. Oilfield services invoices arrive as daily field tickets — a day rate, a crew count, and a job number — rather than as a traditional purchase order receipt. ERP P2P needs to handle service-order-based matching, not just goods-receipt-based matching.

Vendor qualification and compliance. Wellsite contractors must carry adequate insurance and comply with operator HSE standards before they can receive a purchase order. ERP P2P should integrate to vendor qualification systems or enforce an internal vendor onboarding workflow before a PO can be issued.

P2P process flow in oil and gas ERP

The standard P2P flow for a capital purchase:

1. Requisition created with AFE number, lease, and expense code
2. Approval routing based on AFE budget remaining and authority limits
3. Purchase order issued to a qualified, HSE-approved vendor
4. Field receipt or service confirmation recorded against the PO
5. Vendor invoice matched to PO and receipt or service confirmation
6. Invoice cost split by working-interest owner for JIB allocation
7. Payment processed with remittance detail to vendor

The hardest step to automate is step 4 — field receipt confirmation — because receiving in O&G happens at the wellsite, not at a warehouse. Mobile receipt apps or field-ticket scanning integrations solve this but require configuration beyond the standard ERP P2P module.

ERP platforms and P2P in oil and gas

SAP S/4HANA's procurement module handles AFE-coded POs and joint-interest allocation natively through IS-Oil. Oracle ERP Cloud's procurement module is strong on approval workflows and three-way matching. Dynamics 365 and NetSuite require ISV add-ons for AFE coding. Acumatica handles the purchasing workflow but needs configuration for joint-interest allocation.

The implementation test: ask any ERP vendor how their system handles an oilfield services invoice that arrives without a PO, in excess of the AFE budget, for a well with three working-interest partners. How the vendor answers that question tells you more than a demo.

Book an assessment to review your current P2P process gaps and identify which ERP handles oil and gas procurement requirements without significant custom development.