Gas Auto-Actualization: Running and Reviewing Daily Pipeline Allocations

Last updated: October 2, 2026

Gas Auto-Actualization pulls each gas day's pipeline schedule into Molecule, matches every scheduled quantity to the right physical deal, and actualizes the clean matches for you. You review and accept only the exceptions — usually cuts and a few unmatched rows — on a single Allocations screen. This guide covers setup, the daily run, how to read and accept results, how the matching works, and how to fix rows that don't match.

Applied volumes feed settlement, invoicing, positions, and P&L exactly as manually entered actualizations do. Nothing downstream changes; the numbers just arrive faster and with less typing.

Before you start

Gas Auto-Actualization is enabled per account. Molecule turns it on for your account and confirms which of your pipelines are supported. Contact support@molecule.io to get started.
Schedules come from ProcessIQ. Molecule pulls each pipeline's published schedule through ProcessIQ, so no one has to download or email files. Your account's ProcessIQ connection must be configured before the first run.
Setup screens need admin access. Users who manage pipelines and locations need the Gas Actualizations admin permission.
Your deals need scheduling fields. Matching depends on the pipeline and location on each physical gas deal. See Prepare your counterparties and trades below.

How it works

For each pipeline and gas day, a run:

Pulls the schedule from the pipeline through ProcessIQ.
Cleans it up into one row per scheduled path.
Finds the matching deal for each scheduled quantity, by counterparty, location, and buy/sell direction.
Spreads the scheduled volume across the matching deals, including sharing out cuts.
Applies clean, full matches automatically — no clicks needed.
Sends everything else to you on the Allocations screen to review, adjust, and accept.

A few rules hold throughout:

Only the final intraday cycle (ID3) is used. Pipelines publish several nomination cycles per day; actualization always works from the ID3 numbers, so there's no cycle to choose.
Fuel is already accounted for. The pipeline's delivery quantities are already net of fuel, so Molecule doesn't add or calculate fuel.
Re-running is safe. Running a gas day again updates the existing figures instead of duplicating them, and anything you've already accepted isn't overwritten.

Set up pipelines and locations

Admins configure these once and maintain them under Gas Actualizations in the sidebar.

Pipelines

Open Gas Actualizations → Pipelines. Each pipeline has:

Short name — shown as the Hub on the Allocations screen (for example, REX). Required and unique in your account.
Name — required and unique in your account.
ProcessIQ ID — the pipeline's ID in ProcessIQ, used to pull its schedule. Required and unique in your account.
Default counterparty — optional. When a side of a scheduled path comes through blank or "N/A", it's treated as this counterparty. The counterparty must have a DUNS number on file.

Create, edit, and delete pipelines from each row's action menu. A pipeline that schedule data still refers to can't be deleted.

Locations

On the Pipelines screen, click a pipeline's locations count to open its locations. Each location has a code, name, zone, and upstream/downstream names.

The fastest way to load locations is to import the pipeline's location data (LocData) file:

On the pipeline's locations screen, click Import .
Choose the pipeline's LocData CSV. The file needs LOC_ID , LOC_NM , and LOC_ZONE columns; other columns are ignored.
When the import finishes, you'll see how many locations were imported and the list refreshes.

Re-importing is safe. It updates locations that already exist (matched by location code) and adds new ones. Locations missing from the file aren't deleted.

One bad row stops the whole file. If any row has a problem, nothing from that file is imported, and the error shows the row number and what went wrong. Fix the row and import again.

Zones come from the import. Each location needs a zone, and zones are created automatically from the file's LOC_ZONE values. If a pipeline has no zones yet, import its LocData file before adding locations by hand.

A location that's used on a trade can't be deleted.

Prepare your counterparties and trades

Counterparties need their DUNS numbers. The pipeline identifies counterparties by DUNS number, and matching is exact. Make sure each counterparty you schedule with carries the DUNS number the pipeline reports for it. A counterparty can carry more than one.
Physical deals need their scheduling fields. Fill in the pipeline scheduling fields — hub, pipeline, delivery point, and especially location — on every physical gas deal. Existing deals need these filled in before your first automated gas day.

Run the daily allocation

Open Gas Actualizations → Allocations .
Choose the Hub (pipeline) and the as-of date (gas day) at the top. The first pipeline is selected for you.
Click Run Auto-Allocate . A progress bar shows the run moving through its stages — pulling the schedule, cleaning it, matching and allocating, a final sweep, and applying. Buttons are disabled while it runs, and the grid refreshes on its own when it finishes.
Scan the location list for rows that need attention (see Read the results below).
Click a location name to open its detail, review the exceptions, and accept.

If a run can't finish, you'll see a message saying why — for example, that the schedule pull from the pipeline failed, or that some rows couldn't be applied.

Use Refresh at any time to reload the latest results, and Export to download the current location list as a spreadsheet.

Read the results

The location list

Each row rolls up one location:

Loc / Loc Name — the location code and name. Click the name to open the detail.
Pipeline — the hub.
Sch Qty — the total scheduled quantity: what the pipeline says flowed.
Traded Qty — the total contract volume on the matched deals. A deal matched to more than one path is counted once.
Allocated — how much of the scheduled quantity has been placed on deals.
Unallocated — scheduled quantity not yet placed on any deal. Zero means the location is fully handled; a positive number is a gap to close.
Variance — the difference between the traded (contract) volume and the allocated volume.
Sublegs — how many deal lines are involved. A subleg is the settlement line of a deal that the volume lands on.
Alloc Method — how the volume was placed: Full Match , Prorata Cut (shared out because of a cut), or No Subleg (nothing to place it on).
Status — the location's overall state.

Status colors

Green — Applied, Accepted, or Auto-Applied. Done. No action needed.
Orange — Proposed. The system placed a volume but wants you to confirm it — usually a cut. Review, adjust if needed, and accept.
Red — Unmatched. The system couldn't place the volume. Check the Reason and fix the cause (see Fix unmatched rows ).

The location detail

Clicking a location name opens its allocations, with one card per counterparty. Each card header shows that counterparty's Sch Qty, Traded Qty, Allocated, Unallocated, and Variance, so you can see at a glance whether it's fully handled.

Inside each card, every scheduled path has a row:

ID — a direction arrow and the trade. A green arrow pointing right is a receipt (a buy); a red arrow pointing left is a delivery (a sell). Matched rows link to the trade; rows with no match read Unmatched .
Trade Qty , Allocated , Unallocated , and Variance — the same measures as the location list, for that row.
Subleg — the deal line the volume lands on, or No Subleg if nothing matched.
Status and Reason — the row's state and, for unmatched rows, why it didn't match.

Review and accept

Adjust a proposed quantity

You can edit a row only when it's Proposed and has a subleg. Green rows are already applied, and red rows need their cause fixed first.

On a proposed row, type a new value in the Allocated cell. It can't go below zero or above the path's scheduled quantity. Unallocated updates as you type, and your edited value is what gets applied when you accept. This is how you fine-tune a cut before committing it.

Accept selected rows or the whole gas day

Accept specific rows or locations: tick the rows you want (or a location's checkbox to select all of its reviewable rows) and click Accept (N) . Only those are applied; everything else stays as it is.
Accept the whole gas day: with nothing ticked, click Accept (all) . Every proposed row for that hub and day is applied at once, including any quantities you've edited.

Accepted rows turn green, the grid refreshes, and the volumes land on the deals. Rows that were already applied aren't affected.

How matching works

Knowing the rules helps you judge whether a match looks right.

Finding the counterparty. For each side of a scheduled path:

If the side is blank or "N/A" , it's treated as the pipeline's default counterparty.
Otherwise, the pipeline's DUNS number is matched exactly to the counterparty that carries it in Molecule. Names aren't used.
If neither works, the row is Unmatched with the reason No counterparty match .

Finding the deal. Once the counterparty is known, Molecule looks for a deal line that meets all of these:

the same counterparty
a physical deal
the right direction — a receipt matches a buy , a delivery matches a sell
a contract window that covers the gas day
the same location as the scheduled path

If no deal fits, the row is Unmatched with the reason No Subleg match.

Placing the volume.

One matching deal receives the whole scheduled quantity.
Enough volume for every matching deal: each deal receives its full contract amount. This is a Full Match , applied automatically.
Not enough volume (a cut): the shortfall is shared out. Single-day (swing) deals absorb the cut first, then multi-day (baseload) deals, in proportion to their size. Cut rows come to you as Proposed for review.

Paths with only one side — only a receipt or only a delivery — are normal. The populated side is matched, and the empty side doesn't create a false match.

Fix unmatched rows

Unmatched rows and leftover gaps are almost always fixed in your counterparty or trade setup, not on the Allocations screen. Fix the source, run the gas day again, then accept.

No counterparty match (or Unresolved counterparty on a group) — the pipeline's DUNS number doesn't belong to any counterparty in Molecule, and there's no default counterparty to fall back on. Add the DUNS number to the right counterparty, or set the pipeline's default counterparty, then re-run.
No Subleg match — the counterparty was found, but no deal fits the location, direction, and gas day. Check that a physical deal exists for that counterparty and location, in the right direction, with a contract window covering the day, and that its scheduling fields — especially location — are filled in correctly. Correct the trade, then re-run.
Unallocated volume left after accepting — some scheduled quantity still isn't on a deal. This usually means a missing or incorrectly set up deal for that counterparty and location; resolve it the same way as No Subleg match .
Proposed (a cut) — sanity-check how the reduced volume was shared across deals, adjust the Allocated values if the real cut landed differently, then accept.

Not covered here

Manually linking a trade to an unmatched row. The Allocations screen doesn't yet let you choose a trade for an unmatched scheduled quantity, split a row, or pick a different subleg. Resolve unmatched rows by fixing the counterparty or trade setup and re-running.
Name-based matching. Counterparties are matched only by DUNS number or the pipeline's default counterparty. A close-but-different name won't match.
Fuel, imbalance, and makeup trades. Gas Auto-Actualization doesn't create these; it applies volumes to your existing deals.
Cross-pipeline netting. Each pipeline's schedule is matched and applied on its own.
Manual actualization. For entering actualized volumes by hand, see Actualization .

FAQ

The counterparty name on an unmatched row looks right. Why didn't it match?

Matching uses the DUNS number, not the name. Check that the counterparty in Molecule carries the exact DUNS number the pipeline reports.

Will running a gas day again overwrite what I've already accepted?

No. Re-running updates figures that haven't been accepted yet, and accepted rows are protected.

Why weren't my cut rows applied automatically?

Only clean, full matches apply on their own. When the scheduled volume is short, Molecule proposes how to share the cut and waits for you to confirm or adjust it.

Do I need to enter fuel?

No. The pipeline's delivery quantities are already net of fuel.

Which nomination cycle does the run use?

Always the final intraday cycle (ID3). Earlier cycles aren't used for actualization.

If anything here doesn't match what you see on your screen, contact support@molecule.io and we'll help you get set up.