Rate Cards

Rate cards define how charges are calculated during settlement. Each rate card carries a type, an effective-dated version, the rate structure (flat, tiered, or minimum), an optional scope (partner / carrier / facility / product), and — importantly — the billing volume basis that determines which measured volume a charge is priced on.

Open Admin → Rate Cards in the app (/rates).

Rate card types

Type	Bills	Typical basis
Customer Invoice	A receivable to a customer/shipper	Net (NSV)
Gathering	A gathering/handling fee	Net (NSV)
Carrier Settlement	A payable to a carrier for hauling	Gross Observed (GOV) — contract-dependent

Volume basis — which volume you bill on

Crude oil is measured through a standard, ordered volume chain. Because different contracts settle on different points in that chain, each rate card declares the basis it bills on so the charge is always priced on the correct volume.

flowchart LR
  GOV["GOV — Gross Observed Volume<br/>observed temperature, includes S&W"]
  GSV["GSV — Gross Standard Volume<br/>corrected to 60°F, includes S&W"]
  NSV["NSV — Net Standard Volume<br/>GSV minus BS&W — the saleable oil"]
  GOV --> GSV --> NSV

Basis	Label in the app	What it is
NSV	Net (NSV)	Net Standard Volume — temperature-corrected, BS&W deducted. The saleable barrels.
GSV	Gross Standard (GSV)	Gross Standard Volume — corrected to 60°F, still includes S&W.
GOV	Gross Observed (GOV)	Gross Observed Volume — at observed temperature, includes S&W.

The transaction already stores each volume in the chain (corrections are done upstream at the LACT/import), so the basis is a selection, not a recalculation: billing reads the matching stored volume, prices the charge on it, and persists the amount on that same basis.

Note

If a transaction is missing the volume for the selected basis (for example an NSV card but no net volume), the charge is skipped with a warning rather than billed on a fallback volume — so a load is never silently mis-billed.

Setting the basis when you create a rate card

Admin → Rate Cards → New, then choose a rate card type.

1. In the Details card, use the Bill on which volume? selector.
2. The options are listed net-first: Net (NSV), Gross Standard (GSV), Gross Observed (GOV).
3. The field is defaulted by charge type and stays overridable:
   • Customer Invoice and Gathering pre-fill Net (NSV).
   • Carrier Settlement does not pre-fill — you must choose a basis before the card can be saved.

Field	Behavior
Bill on which volume?	Required. Determines which measured volume the amount is billed on.
Customer Invoice / Gathering	Pre-filled to Net (NSV); change if your contract differs.
Carrier Settlement	No default — the form blocks submission until you pick a basis.

Caution

Carrier settlement cards require an explicit basis. This prevents a hauling card from silently defaulting to net barrels when your contract pays on gross.

Existing carrier cards after the volume-basis release

Carrier settlement cards created before this feature are intentionally marked Not configured because their contracts cannot be inferred safely. Before the next payable settlement run, review every existing carrier card and save the contract’s GOV, GSV, or NSV basis. Until a card is configured, payable charge generation skips it with a warning instead of guessing a billing volume.

Customer Invoice and Gathering cards from before the release are migrated to NSV, matching their established default. Review any contract that is an exception.

Viewing and changing the basis

The rate card detail page shows the current basis under Billing Basis.

1. Open a rate card from the list (/rates).
2. On the Overview tab, find Billing Basis.
3. Click Edit next to it to change the basis inline, then Save. A confirmation appears and the detail view updates.

For a carrier card, the inline editor will not let you save an empty basis — the card must always keep an explicit choice.

How billing uses the basis

When charges are generated, each rate card bills on its own basis:

• The charge quantity is the transaction’s volume for that basis (NSV → net volume, GSV → gross standard, GOV → gross observed).
• The amount is priced on that same volume (amount = quantity × rate, honoring any minimum/tier), and the stored amount always equals the rate breakdown total — the two never disagree.
• A minimum-charge card is billed at its floor, never scaled below it.

A single truck receipt can produce two settlements on different bases — for example a customer receivable on NSV (the commodity) and a carrier payable on GOV (the hauling) — each priced on the basis its own rate card declares.

Related topics

• Products — API gravity thresholds referenced by rate cards
• Partners — the carriers and customers a rate card is scoped to
• Settlements & Invoicing — generating charges and invoices from rate cards