The Ops Accountant · Analyze · Dataset

Analyze · The data

The sample dataset

Every case study in this section runs on one made-up dataset: 14 wells, ten months of 2026, and the tables an operations accountant works with every day. It's small enough to read and big enough to hide real-looking mistakes, because some were planted on purpose.

Everything here is invented. The wells, owners, operators, vendors, prices and amounts are made up for illustration. No employer or partner data is used anywhere on this site.

The tables

Every table carries well name + cost center, and every join uses both. That's the rule that keeps a cost or a barrel off a lookalike well.

TableWhat a row isRowsColumns
wellsThe well master: one row per well name + cost centerwell_name, cost_center, well_type, operator, field, status, status_effective, royalty_burden, company_wi
decksEach owner's working and net revenue interest by wellwell_name, cost_center, owner, wi, nri
afesAuthorizations for expenditure, operated and non-opafe_no, well_name, cost_center, afe_type, gross_amount, status, approved
invoicesAP invoice lines on operated wells, at 100%invoice_id, vendor, invoice_no, invoice_date, month, well_name, cost_center, afe_no, cost_type, account, amount
jib_linesEach invoice line split to each owner by the JIB deckmonth, well_name, cost_center, afe_no, cost_type, owner, wi, amount, invoice_id
nonop_jibOperators' JIBs received on non-operated wells (the company's net share)month, operator, well_name, cost_center, afe_no, cost_type, gross_amount, company_wi, net_amount
productionMonthly oil, gas and water by wellmonth, well_name, cost_center, oil_bbl, gas_mcf, water_bbl
revenueRevenue paid to each owner by well and monthmonth, well_name, cost_center, owner, nri, gross_value, net_revenue
accrualsThe company's net accrual by well and group, with the actual that came inmonth, well_name, cost_center, cost_group, accrued_net, actual_net

What's planted in it

These are the errors the case studies are built to find. Each mirrors something that happens in real review.

Planted errorWhere it shows up
Jones Unit 1 revenue for September and October booked to lookalike cost center CC-2210SQL: lookalike cost center and billed, not paid
Smith 2H Partner B dropped from the revenue deck from July (suspense)SQL: billed, not paid
Baker 1 Partner A paid at NRI 0.1875 instead of 0.175SQL: NRI check
Davis 4H workover posted $40,000 over its $1.25M AFESQL: AFE spend and the dashboard
A duplicate invoice, an invoice coded to the wrong cost center, a charge on a closed AFE, a Capital line on a P&A AFE, and a charge after Clark 2 was soldSQL: coding exceptions
Accruals that missed: AFE field estimates that lagged, Smith 3H accruing after it was shut inSQL: accrual accuracy, the Excel review and the dashboard
An operator billing a well that isn't in the cross-referencePower Query: unmapped wells

Look inside

Loading…

Showing the first 25 rows. Copy pastes the whole table into Excel or a text file. When the site is hosted on its own domain, each table is also available as a CSV file in analyze/data/csv/.

The data was generated with a short Python script from fixed settings, so it's the same every time. All of it is invented.