Crude Oil Settlement Software

If you run a mid-size gathering operation and you're still settling volumes with spreadsheets, you already know the pain. Month-end takes too long, disputes pile up, and your best analysts spend their time copying data between systems instead of catching problems.

This guide is for operators who've decided it's time to evaluate settlement software but aren't sure what to look for, what questions to ask vendors, or how purpose-built platforms compare to the enterprise ERP systems that larger operators use. We'll cover 8 must-have features, the right questions to ask during a demo, and why "good enough" software can quietly cost you more than doing nothing.

Who This Guide Is For

This guide is written for mid-size crude oil gathering operators — companies running anywhere from a handful of LACT units up to hundreds, processing a few thousand tickets per month, and settling with multiple producers, shippers, or purchasers.

You might be a measurement manager looking to replace a spreadsheet workflow that's held together with duct tape. Or a VP of operations who's been told the company needs "better software" but isn't sure what that means in practice. Or a field operations leader who's tired of spending the first week of every month reconciling volumes instead of running the operation.

Whatever your role, the goal is the same: evaluate settlement software with confidence and pick the right platform for your operation.

Why the Mid-Market Is Underserved

Enterprise settlement platforms — the FLOWCALs and Quorums of the world — were designed for the largest operators. They come with six- or seven-figure price tags, 12-18 month implementations, and enough configuration options to require a dedicated team of administrators. If you're running 50 LACT units across a couple of gathering systems, that's more software than you need and more money than you should spend.

On the other end of the spectrum, a lot of mid-size operators have stayed on spreadsheets — not because they work well, but because the jump to enterprise software felt too big. The spreadsheet is free, the team knows how it works, and "it's always been done this way."

The problem is that spreadsheets don't scale. As volume grows, complexity grows faster. More LACT units, more contracts, more producers asking questions about their settlements. The spreadsheet that worked for 10 leases starts breaking at 50, and by the time you're at 100, your month-end close is a multi-day ordeal involving 3 analysts and a prayer.

That gap between "spreadsheets" and "enterprise ERP" is exactly where purpose-built, cloud-based settlement platforms live. And it's where the most opportunity exists for mid-size operators to gain a real operational advantage.

8 Must-Have Features in Crude Oil Settlement Software

Not all settlement software is created equal. Here are the eight capabilities that separate a platform that actually solves your problems from one that just moves them into a different interface.

1. Automated Data Ingestion

The software should pull measurement data directly from your flow computers, SCADA systems, and field data capture tools — not require manual uploads or re-keying. Look for native support for common data formats: TransLog, Microload, CSV/Excel, and API integrations with major SCADA vendors.

Why it matters: Manual data entry is the single largest source of settlement errors. Every time a human transcribes a number from a flow computer report into a spreadsheet, there's a chance of a transposition error, a missed reading, or a pasted-over cell. Automated ingestion eliminates that entire category of mistakes.

2. Contract-Driven Settlement Calculations

Your contracts define how volumes are allocated, how gathering fees are applied, how pipeline loss allowance is calculated, and how quality adjustments (BS&W, API gravity) affect pricing. The software should encode those terms and apply them automatically — not rely on your analyst to remember that Producer A gets a 0.25% shrinkage exemption while Producer B doesn't.

Why it matters: Contract terms are where disputes are born. When settlements are calculated by hand, it's easy to misapply a rate, forget an exemption, or apply last quarter's terms to this quarter's volumes. Software that enforces contract logic consistently eliminates those errors.

3. Real-Time Volume Reconciliation

Don't wait until month-end to find out something is wrong. The platform should reconcile volumes on a rolling basis — flagging discrepancies as they happen, not weeks after the fact. When a meter starts drifting or a ticket goes missing, you should know about it within hours, not at month-end close.

Why it matters: A discrepancy caught on Day 3 is a quick fix. A discrepancy caught on Day 31 is a dispute. Real-time reconciliation compresses your close cycle and gives your team time to address issues before they become financial arguments.

4. Anomaly Detection and Validation

The software should automatically flag measurement anomalies: duplicate tickets, volume shorts and longs that exceed tolerance, unexpected quality readings, timing gaps in meter data, and unknown shipper or carrier codes. These are the errors that cause disputes — and the software should catch them before your settlements go out.

Why it matters: Manual review misses things. An analyst processing 500 tickets can't visually scan every one for anomalies. Automated validation rules catch issues that humans reliably miss — especially under the time pressure of month-end close.

5. Full Audit Trail

Every change to measurement data — from initial ingestion through final settlement — should be logged with a timestamp, user, and reason. When a producer calls to dispute a settlement, you should be able to trace exactly how you arrived at every number on their statement, who approved it, and what the original measurement values were.

Why it matters: Spreadsheets have no audit trail. Once a cell is overwritten, the original value is gone. In a regulated industry where custody transfer accuracy is both a legal and financial requirement, the inability to show your work is a liability.

6. Multi-Product and Multi-Mode Support

If your operation handles crude, NGL, butane, or condensate — or if you measure volumes across pipeline, truck, and rail — the software needs to handle all of it natively. Look for platforms that don't force you into a single commodity or transport mode.

Why it matters: Many mid-size operators handle multiple products or transport modes. A platform that only handles pipeline crude forces you to maintain a separate system (or spreadsheet) for truck deliveries or NGL volumes, fragmenting your data and your process.

7. Producer-Facing Reports and Portals

Your producers need to see their volumes, settlements, and supporting documentation. The best platforms offer self-service portals where producers can review their statements, download supporting data, and ask questions — without calling your office.

Why it matters: Settlement disputes often start as information requests. A producer who can't see the data behind their statement calls your team, which triggers an email chain, which triggers a meeting. A self-service portal short-circuits that cycle and reduces the administrative load on your team.

8. Cloud-Based Deployment

On-premise installations add IT overhead, limit remote access, and require internal resources for updates and maintenance. Cloud-based platforms deploy faster, scale without hardware investments, and give your team access from any location — which matters when your analysts aren't always in the office.

Why it matters: Mid-size operators typically don't have large IT departments. A cloud platform eliminates the server administration, backup management, and version upgrade work that on-premise systems require.

Purpose-Built Software vs. Enterprise ERP

One of the first decisions you'll face is whether to extend your existing ERP system (if you have one) or adopt a purpose-built settlement platform. Here's how they compare for mid-size gathering operators:

The takeaway: enterprise ERPs solve enterprise problems. If you're a mid-size operator, you're paying for capabilities you don't need and spending months implementing features that a purpose-built platform delivers out of the box.

10 Questions to Ask During a Demo

When you're evaluating vendors, these questions will help you separate the platforms that understand your workflow from the ones that are just showing you a nice interface:

1. How does data get into the system? Ask about specific integrations with your flow computers and SCADA. "We have an API" is not the same as "we natively parse TransLog files."
2. How are contract terms configured? Can your measurement team set up new contracts, or does every change require vendor support?
3. What happens when a ticket is missing or duplicated? The system should flag it automatically, not require someone to notice during a manual review.
4. Show me the audit trail for a single settlement line item. If they can't trace from final number back to raw measurement data in under a minute, the audit trail isn't real.
5. How does reconciliation work on a daily basis? You want rolling reconciliation, not a batch process that only runs at month-end.
6. What does month-end close actually look like? Ask for a walkthrough with real data. How many clicks? How many manual steps? How long does it take?
7. Can producers see their own data? Ask about producer portals, self-service reporting, and how disputes are handled within the system.
8. What does implementation look like for an operation my size? Get a specific timeline, not a range. Ask about data migration, training, and go-live support.
9. How are updates and new features delivered? Cloud platforms should update automatically. If the vendor talks about "upgrade projects," that's a red flag.
10. What's the total cost of ownership over 3 years? Include implementation, training, support, and any per-user or per-transaction fees. Compare this to your current cost of manual settlement (analyst hours, dispute resolution, delayed closes).

The Hidden Cost of "Good Enough"

The biggest competitor to settlement software isn't another vendor — it's the spreadsheet you're already using. It's familiar, it's "free," and it works... until it doesn't.

Here's what "good enough" actually costs a typical mid-size gathering operator:

• Analyst time: 3 analysts × 3 hours/day × $35/hour × 250 days = $78,750/year just on data handling and reconciliation
• Month-end overtime: The first week of every month is a fire drill. Extra hours, weekend work, and the opportunity cost of not doing anything else
• Dispute costs: Every unresolved dispute is a phone call, a meeting, a re-calculation, and sometimes a revenue concession. At scale, this adds up to hundreds of thousands in unrecovered revenue
• Error-driven losses: A single transposition error on a high-volume LACT can misstate settlement by thousands of dollars. How many of those are you catching?
• Turnover risk: When the one analyst who understands the spreadsheet leaves, the institutional knowledge goes with them

Add it up and a mid-size operator is often spending $150,000-$300,000 per year on manual settlement processes — far more than the cost of a purpose-built platform that eliminates most of that work.

What to Look For in a Vendor

Beyond features, the vendor relationship matters. Here's what separates a good partner from a company that's just selling software:

• Industry expertise. Do they understand crude oil gathering, or are they a general-purpose platform that added an oil and gas module? Ask about their team's operational experience.
• Implementation support. You need more than a login and a user manual. Good vendors provide hands-on onboarding, data migration assistance, and a clear go-live plan.
• Responsive support. When something breaks during month-end close, you can't wait 48 hours for a support ticket response. Ask about SLAs, support hours, and escalation paths.
• Product velocity. Is the vendor actively developing the product? Ask how often they release updates and what's on the roadmap. A platform that hasn't changed in 18 months is a platform that's being maintained, not improved.
• Customer references. Talk to operators who are similar to you — same size, same products, same use cases. A reference from a 10,000-well major doesn't tell you how the platform works for a 100-LACT gatherer.

Making the Business Case

If you're the one making the recommendation internally, here's a framework for building the case:

1. Quantify the current cost. Add up analyst hours, overtime, dispute costs, and error-related losses. Be conservative — even a conservative number is usually large enough to justify the investment.
2. Define the timeline. Most purpose-built platforms can be live within 4-8 weeks. That means ROI starts within a quarter, not next year.
3. Identify the risk of doing nothing. What happens when your volume doubles? When your best analyst leaves? When a producer audit finds a systematic error in your settlements? The cost of inaction isn't zero.
4. Get a pilot commitment. Many vendors will let you start with a single gathering system or a subset of your operation. This reduces risk and gives you real data to make the full deployment decision.

Frequently Asked Questions