Blog

What Happens During Crude Oil Month-End Settlement?

A Step-by-Step Guide for Gathering Operators

March 16, 2026 · 9 min read

If you've been in midstream operations for any length of time, you know that month-end settlement is the event that drives everything else. It's when the numbers have to balance, the statements have to go out, and the payments have to flow. And if your process isn't tight, it's also when problems you've been ignoring all month come crashing down at once.

This guide walks through the five stages of crude oil month-end settlement at a gathering facility — what happens at each step, where the process tends to break down, and how the manual approach compares to an automated one. Whether you're a measurement tech, an operations manager, or someone evaluating settlement software for the first time, understanding this workflow is essential.

Why Month-End Settlement Matters

Month-end settlement is the financial reconciliation process where a gathering operator accounts for every barrel of crude oil that moved through their system during a calendar month. The operator determines how much oil was received from each producer or shipper, how much was delivered to downstream purchasers, what adjustments apply, and how much money changes hands.

For a mid-size gathering system handling 20,000 to 80,000 barrels per day across multiple receipt points and delivery points, settlement involves hundreds of individual data points per day — LACT readings, truck tickets, quality samples, meter calibration records, and contract terms that vary by shipper.

Get it wrong, and you face payment delays, producer disputes, regulatory exposure, and erosion of the business relationships your operation depends on. Get it right, and settlement becomes a competitive advantage — operators who settle quickly and accurately retain producers and attract new ones.

Stage 1: Data Close and Cutoff

Settlement starts with locking the measurement period. At midnight on the last day of the month, all LACT unit readings, truck dispatch records, and SCADA data feeds need to be finalized. This sounds straightforward, but it's where many operators lose their first few days.

What happens manually: A measurement tech or operations coordinator contacts each facility to confirm final meter readings. Field tickets from the last few days trickle in via email, fax, or sometimes phone. Someone manually checks whether every truck run and every LACT transaction has been recorded. Missing data gets flagged, and the team starts making phone calls — to trucking dispatchers, to field operators, to producers — to fill in the gaps.

This stage typically takes 2–4 business days in a manual environment. If a single receipt point has a data gap, the entire settlement process stalls while the team chases down the missing information.

What happens with automation: Settlement software pulls LACT readings, SCADA data, and dispatch records automatically throughout the month. By the time the calendar rolls over, most data is already in the system. Automated validation flags gaps, duplicates, and out-of-range values in real time — so by the first business day of the new month, the team is reviewing exceptions rather than hunting for missing data. Data close typically takes hours, not days.

Stage 2: Volume Reconciliation

Once the data is locked, reconciliation begins. This is the process of comparing receipt-point volumes against delivery-point volumes for every shipper and every system segment. The goal is to account for every barrel and explain any differences.

Reconciliation involves calculating pipeline loss allowance (PLA) — the acceptable variance between what enters the system and what exits it. Losses from evaporation, meter tolerance, temperature effects, and BS&W differences are expected and contractually defined. What matters is whether actual losses fall within the allowed range.

What happens manually: An analyst builds or updates a reconciliation spreadsheet for each system segment. They pull receipt volumes from one set of records and delivery volumes from another, map them to shipper accounts, calculate PLA based on contract terms, and check whether variances are within tolerance. For a system with 15–20 receipt points and 3–5 delivery points, this work can take 3–5 business days. Errors in the spreadsheet — a wrong cell reference, a misapplied contract formula — can cascade through the entire reconciliation and may not be caught until a producer disputes the statement.

What happens with automation: The software maps all receipt and delivery points, applies PLA rules per contract, and generates a volume reconciliation report automatically. Variances that exceed thresholds are flagged for human review. The analyst's job shifts from building the reconciliation to reviewing and approving it — a process that takes hours instead of days.

Stage 3: Quality Adjustments and Contract Application

Raw volume numbers are only part of the equation. Before you can calculate what anyone owes or is owed, you need to apply the quality adjustments and contractual terms that govern each shipper relationship.

This stage involves:

  • BS&W deductions — subtracting basic sediment and water content from gross volumes to arrive at net oil volumes
  • API gravity adjustments — applying price differentials based on crude quality (lighter crudes typically command higher prices)
  • Temperature corrections — normalizing volumes to standard conditions (60°F / 15°C) using API correction tables
  • Shrinkage factors — accounting for volume reduction when crude oil of different qualities is commingled
  • Gathering fee calculations — applying per-barrel tariffs, tiered pricing structures, or minimum volume commitments per each shipper's contract
  • Marketing fees and deductions — applying downstream marketing arrangements where the gathering operator also markets the crude

What happens manually: This is where spreadsheet-based settlement gets truly dangerous. Each shipper's contract may have different BS&W limits, different gravity adjustment scales, different gathering fee structures, and different effective dates for rate changes. Someone has to read the contract (or remember the terms), translate them into spreadsheet formulas, and apply them correctly to that shipper's volumes for that month. When a contract changes mid-month or a new amendment takes effect, the complexity multiplies.

Operators running 30–50 shipper contracts through spreadsheets routinely spend 3–5 additional business days on this stage. The risk of error is high, and errors here directly affect payment amounts — which means disputes.

What happens with automation: Contract terms are encoded in the system once and applied automatically every month. When a rate changes or a new amendment takes effect, the operator updates the contract record and the system applies the correct terms to the correct period. The same calculations that take days in a spreadsheet take seconds in software — and they're applied consistently, every time, with a complete audit trail.

Stage 4: Settlement Statement Generation and Review

With reconciled volumes and applied adjustments in hand, it's time to generate the actual settlement statements — the documents that tell each shipper exactly what happened with their oil and what they're owed (or what they owe).

A settlement statement for a single shipper typically includes:

  • Gross volumes received at each receipt point
  • Quality adjustments (BS&W, gravity, temperature)
  • Net volumes after deductions
  • Pipeline loss allowance applied
  • Gathering fees, marketing fees, and other charges
  • Unit prices and total amounts due
  • Supporting detail: daily volumes, meter readings, quality samples

What happens manually: Someone builds or populates a statement template — usually in Excel or Word — for each shipper, pulling numbers from the reconciliation spreadsheet. With 30+ shippers, this is tedious, error-prone work. Each statement needs internal review before it goes out, and the reviewer has to verify the numbers against the reconciliation and the contract terms. Rounds of correction and re-review are common. This stage adds another 2–3 business days.

What happens with automation: The system generates statements for all shippers simultaneously from the reconciled, contract-adjusted data. Statements are formatted consistently, include all required supporting detail, and are ready for review immediately. The reviewer can approve or flag individual statements from a dashboard rather than opening dozens of spreadsheet files. Statement generation that took days now takes minutes; review takes hours instead of days.

Stage 5: Distribution, Dispute Resolution, and Payment

The final stage is getting statements to shippers, resolving any disputes, and processing payments. This is where the quality of everything upstream either pays off or creates pain.

What happens manually: Statements go out via email (or sometimes mail). Shippers review them against their own records. If the numbers don't match, the dispute process begins — phone calls, emails back and forth, pulling up source records, trying to identify where the discrepancy originated. Without an audit trail, these disputes can take days or weeks to resolve. Meanwhile, payments are delayed, and the whole process bleeds into the next month's cycle.

What happens with automation: Statements can be distributed electronically from the platform with a complete audit trail attached. When a shipper questions a number, the operator can pull up the exact source data — the specific LACT reading, the specific quality sample, the specific contract clause — and share it immediately. Disputes that used to take a week of back-and-forth resolve in hours because the evidence is right there, timestamped and logged.

Payment processing follows naturally once statements are approved. Automated systems can generate payment files, track payment status, and flag outstanding balances — closing the loop on the entire month-end cycle.

Manual vs. Automated: The Timeline Comparison

Here's what the total month-end timeline looks like side by side:

StageManual (Spreadsheets)Automated (Software)
Data Close & Cutoff2–4 daysHours
Volume Reconciliation3–5 daysHours
Quality Adjustments & Contracts3–5 daysMinutes
Statement Generation & Review2–3 daysHours
Distribution & Disputes2–5 days1–2 days
Total12–22 business days3–5 business days

That's the difference between closing settlement in the first week of the new month versus still chasing last month's numbers when the next month-end arrives. For operators managing multiple systems or growing their gathering footprint, the spreadsheet approach simply doesn't scale.

The Hidden Costs of Slow Settlement

Beyond the obvious staff time, slow month-end settlement creates costs that are easy to overlook:

  • Cash flow delays. If you can't close settlement until day 15 or 20, your payments are delayed by that same period. For an operator handling 50,000 barrels per day at $70/barrel, even a one-week delay represents significant working capital impact.
  • Producer churn. Producers have choices about where to deliver their crude. Operators who settle late, settle inaccurately, or can't explain their numbers are the first to lose producers when a competitor offers better service.
  • Compliance risk. Regulatory requirements for record-keeping and reporting get harder to meet when your source data lives in a patchwork of spreadsheets maintained by different people.
  • Staff burnout. The measurement and accounting teams who spend the first two weeks of every month in a high-pressure close cycle aren't available for the higher-value work — analyzing trends, identifying measurement anomalies, optimizing operations — that actually grows the business.

Getting From Here to There

If your current month-end process looks more like the manual column than the automated one, you're not alone. Most gathering operators started with spreadsheets because that's what was available, and the process has grown organically from there. The challenge isn't recognizing that it needs to change — it's finding software that fits the way gathering operations actually work.

Purpose-built crude oil settlement software like COYOTE Measurement is designed specifically for mid-market gathering operators. It handles the full workflow — from automated LACT and SCADA data ingestion through reconciliation, contract application, statement generation, and dispute resolution — with the audit trail and reporting that operators and their producers expect.

The operators who've made the switch consistently report the same thing: month-end close drops from weeks to days, disputes drop dramatically, and their teams finally have time to focus on running the business instead of running spreadsheets.

Ready to close settlement in days, not weeks?

See how COYOTE Measurement automates the entire month-end settlement process — from data ingestion through payment reconciliation.

Schedule a Demo

Frequently Asked Questions

How long does crude oil month-end settlement typically take?

For operators using spreadsheets, month-end settlement typically takes 10–15 business days after the measurement period closes. With automated settlement software, most operators complete the process in 3–5 business days — some close within 48 hours of data cutoff.

What is the difference between gross volume and net volume in crude oil settlement?

Gross volume is the total measured volume at a custody transfer point before any deductions. Net volume is what remains after subtracting BS&W (basic sediment and water), applying temperature corrections, and accounting for pipeline loss allowance (PLA). Net volume is the basis for payment calculations.

What causes delays in crude oil month-end settlement?

The most common causes are missing or incomplete measurement data (LACT readings, truck tickets, SCADA gaps), manual data entry errors that require re-reconciliation, disputes over volume variances between shippers and operators, and contract terms that must be manually applied in spreadsheets each month.

Can crude oil settlement be fully automated?

The data ingestion, reconciliation, quality adjustment, and statement generation stages can be fully automated. Dispute resolution and final payment approval still require human judgment, but automation reduces the volume of disputes and provides the audit trail needed to resolve them quickly.