BS&W, API Gravity, and GSV - The Measurement Data Your Settlement Software Must Track

Every crude oil settlement comes down to three questions: How much fluid moved? How much of that fluid was actually oil? And what was the corrected volume at standard conditions? The answers live in three data points that every gathering operator deals with daily: BS&W (basic sediment and water), API gravity, and GSV (gross standard volume). If your settlement software doesn't track all three correctly — and understand how they interact — you're building financial statements on unreliable numbers.

This post explains what each of these measurements is, how they connect to each other, and what happens in your settlement calculations when any of them are wrong.

BS&W: The Quality Deduction

BS&W stands for Basic Sediment and Water. It represents the percentage of a crude oil stream that isn't actually crude oil — it's water, sand, emulsified solids, and other impurities that come out of the well along with the oil.

Why does it matter? Because nobody pays for water. When a shipper delivers 1,000 barrels through a LACT unit and the BS&W reading is 1.5%, the buyer is paying for 985 barrels of oil — not 1,000. That 15-barrel difference at $70/bbl is $1,050. Across a gathering system processing 50,000 barrels a day, even a 0.1% BS&W error represents thousands of dollars in misallocated settlements every month.

How BS&W Is Measured

BS&W is measured two ways at the LACT unit:

Inline BS&W probes use capacitance or microwave technology to estimate water content in real time as crude flows through the measurement skid. They provide continuous readings and trigger automatic diversions — if BS&W exceeds a threshold (typically 0.5% to 2%, depending on the contract), the LACT diverts the oil back to the tank for re-processing rather than allowing high-water crude into the pipeline.

Lab analysis of composite samples is the definitive method. The automatic sampler on the LACT collects proportional samples throughout a batch. The lab then uses centrifuge testing (per API MPMS Chapter 10) to determine the exact BS&W percentage. When the lab result differs from the inline probe reading, the lab result is typically used for settlement.

What Goes Wrong

BS&W problems are among the most common causes of crude oil settlement disputes:

• Probe calibration drift. Inline probes can drift over time or read differently across crude oil types. If the probe reads 0.5% but the lab says 1.8%, every barrel in that batch was settled at the wrong deduction.
• Late lab results. Lab analysis can take days. If your software settles on probe data and then a lab correction comes in, you need the ability to re-open and recalculate the affected settlement period.
• Misapplied thresholds. Different contracts specify different BS&W limits. One shipper's contract might deduct at actual BS&W; another might apply a penalty schedule above 1%. Your software needs contract-level BS&W rules, not a single global setting.

API Gravity: The Density That Drives Corrections

API gravity measures how dense crude oil is relative to water. It's expressed on an inverse scale defined by the American Petroleum Institute: lighter crudes have higher API gravity numbers, heavier crudes have lower numbers. Water is 10° API. Most crude oils fall between 20° and 45° API, with light sweet crudes (like West Texas Intermediate at ~39.6° API) being the most valuable.

API gravity affects settlement in two distinct ways:

1. Volume Correction

Crude oil expands when it's hot and contracts when it's cold. A barrel of oil measured at 90°F in a summer field is physically larger than that same barrel at 60°F. The industry standard is to correct all volumes to 60°F so that everyone is comparing apples to apples — regardless of when or where the oil was measured.

The correction factor comes from API MPMS Chapter 11.1 (the CTL — Correction for Temperature of Liquid tables). To look up the right factor, you need two inputs: the observed temperature and the API gravity of the crude. Different API gravities produce different correction factors at the same temperature. A 30° API crude at 90°F gets a different correction than a 40° API crude at 90°F.

This means an incorrect API gravity doesn't just mischaracterize the oil — it applies the wrong temperature correction to the volume. The error compounds.

2. Pricing

Many crude oil contracts include gravity-based pricing adjustments. Lighter crude (higher API gravity) is easier to refine and yields more valuable products, so it commands a premium. Heavier crude is discounted. Some contracts use a simple gravity band (e.g., $0.10/bbl deduction for every degree below 35° API). Others use a full gravity-adjusted pricing table. Either way, an API gravity error changes what the buyer pays per barrel — on top of changing the volume calculation.

How API Gravity Is Determined

API gravity is determined from the composite sample collected at the LACT unit. The lab measures the density of the sample (typically using a hydrometer or digital density meter) and converts it to API gravity using the formula:

Some operations use inline densitometers (Coriolis meters measure density directly) for a continuous reading, but the lab result from the composite sample is the authoritative number for settlement.

GSV and NSV: From Raw Volume to Settled Volume

The volume journey from LACT meter to settlement statement goes through several stages. Each stage applies a correction, and the terms can be confusing. Here's the chain:

GOV — Gross Observed Volume

This is the raw volume reading from the meter at the conditions present in the pipe — whatever temperature and pressure the oil happened to be at when it flowed through. GOV is the starting point, but it's not usable for settlement because the same physical quantity of oil will produce different GOV readings depending on when you measure it.

GSV — Gross Standard Volume

GSV is GOV corrected to standard conditions — 60°F and equilibrium vapor pressure. The correction uses three factors from the API MPMS tables:

• CTL (Correction for Temperature of Liquid): Adjusts the volume from observed temperature to 60°F. Requires API gravity and observed temperature as inputs.
• CPL (Correction for Pressure of Liquid): Adjusts for the difference between observed pressure and equilibrium pressure. Smaller effect than CTL for most crude oil applications, but not zero. (Note: for crude oil at moderate pressures typical of gathering operations, CPL is very close to 1.0000 and often negligible. It becomes more significant in high-pressure pipeline and terminal operations.)
• MF (Meter Factor): The calibration correction from the most recent proving run. Accounts for any systematic bias in the meter's readings.

GSV represents the total volume of fluid (oil + impurities) at standard conditions. It's standardized and comparable across different measurement points and different times of year.

NSV — Net Standard Volume

NSV is the volume the buyer pays for. It's GSV minus the BS&W deduction:

NSV is the number that appears on settlement statements. It's the volume that gets multiplied by the price to determine what each party owes or is owed. Everything upstream — meter readings, temperature corrections, quality sampling — exists to produce an accurate NSV.

How These Three Data Points Connect

BS&W, API gravity, and GSV aren't independent values you can track in isolation. They form a chain where each one depends on or feeds into the others:

1. API gravity determines the CTL factor used to calculate GSV from GOV. Wrong API gravity → wrong CTL → wrong GSV.
2. GSV is the base for the BS&W deduction. The BS&W percentage is applied to GSV to produce NSV. Wrong GSV → wrong NSV even if BS&W is perfect.
3. BS&W determines the net volume. Wrong BS&W → wrong NSV even if GSV is perfect.
4. Errors compound. If API gravity is off by 2 degrees and BS&W is off by 0.3%, both errors hit the final NSV simultaneously. On a 10,000-barrel batch, the combined error can easily reach several thousand dollars.

This is why settlement software can't treat these as three independent fields in a database. It needs to understand the calculation chain, validate each input against expected ranges, and propagate corrections automatically when a lab result overrides an inline reading.

What Your Settlement Software Must Do

Given how these measurements interact, here's what to demand from your software:

Automated API table lookups. Your software should apply the correct CTL and CPL factors from API MPMS Chapter 11 automatically — based on the crude type, observed temperature, observed pressure, and API gravity. Manual table lookups are a relic of the spreadsheet era, and they're a guaranteed source of errors at scale.

Lab result override workflow. When lab BS&W or API gravity results come back and differ from inline readings, the software should accept the lab value, recalculate GSV and NSV for the affected batches, and flag the changed settlements for review. This needs to happen without re-entering data or rebuilding the entire settlement period manually.

Contract-specific BS&W rules. Different shippers, different contracts, different BS&W penalty structures. The software must apply the right deduction method to the right volumes based on the governing contract — not a one-size-fits-all percentage.

Validation ranges per measurement point. A BS&W reading of 15% from a probe that usually reads 0.8% is almost certainly a malfunction, not a real measurement. Your software should flag anomalous readings automatically — across BS&W, API gravity, temperature, and volume — before they flow into settlement.

Full audit trail from meter to statement. Every NSV on a settlement statement should trace back through the GSV calculation (showing CTL, CPL, and MF applied), the BS&W deduction (showing source — probe or lab), the API gravity used (and whether it was inline or lab), and the original GOV from the meter. When a dispute arises, you need to show the math.

Recalculation without re-entry. Meter reproving, lab corrections, and contract amendments all require recalculating previously settled volumes. Your software must recalculate affected NSVs automatically when an upstream input changes — and track what changed, when, and why.

The Cost of Getting It Wrong

Settlement errors from mishandled BS&W, API gravity, or GSV calculations don't announce themselves. They accumulate quietly — a few hundred dollars here, a few thousand there — until someone runs a reconciliation or a shipper raises a dispute.

By the time a problem surfaces, it often spans months of settlements. Unwinding months of compounded errors in spreadsheets is exactly the kind of work that consumes entire weeks of your team's time — time they should be spending on operations, not forensic accounting.

The alternative is software that handles the calculation chain correctly from the start: ingesting raw LACT data, applying API corrections with the right gravity, deducting BS&W per contract terms, and producing settlements that both buyer and seller can trust.