A master service agreement for oilfield services is usually short and reasonable. The value sits in what is attached to it: a rate schedule, a personnel category table, an equipment list, escalation language and exhibits negotiated by different people at different times. The MSA governs liability and indemnity. The exhibits govern how much you pay, and that is where margin leaves the business.
The leak is rarely fraud. It is drift. A rate schedule is agreed in a spreadsheet, emailed, signed as a PDF and never loaded anywhere an invoice can be tested against it. Field supervisors approve tickets because the work happened, which it did. Accounts payable matches the invoice to a purchase order, which matches. Nobody compares the line to the rate exhibit in force on the service date.
Oilfield services contract compliance is the unglamorous work of closing that gap: turning rate exhibits into structured, comparable data, tying each field ticket and invoice line to the governing schedule version, and testing escalation claims against the trigger the contract actually names. The prize is not a renegotiation. It is paying the rate you agreed, which most teams find sits in the detail.
Where the money actually goes
Leakage in service spend is cumulative and boring, which is why it survives. Each item below is small on one ticket and material across a drilling program. None of them require a supplier to behave badly, only for nobody on your side to hold the schedule as data.
- Standby and day rates, standby is usually billed at a discount with a daily cap and a duty to release equipment, and the release condition is the part that gets skipped during weather delays.
- Mobilization and demobilization, mob and demob are often lump sums tied to a defined origin and destination, and repeat charges appear when a crew moves between your own pads.
- Personnel category creep, a supervisor rate billed for a technician task is hard to see, because the ticket records a name and hours rather than the contracted category.
- Escalation and indexation, schedules commonly allow an annual adjustment against a named index or a notice mechanism, and claims arrive applied from the wrong date or against the wrong base.
- Consumables and pass-through, fluids, bits, chemicals and rented items billed at cost plus handling need the underlying invoice attached, or the markup cannot be tested at all.
Minimum volume commitments belong on the same list, because they run both ways. An unmet commitment can create a true-up nobody budgeted, and a commitment already met can still be billed if the counter lives in a supplier spreadsheet. Version control sits underneath all of it. A schedule superseded in March keeps governing invoices until someone loads the replacement.
Before auditing rates, answer one question for each major supplier. Which rate schedule version was in force on the date the service was performed, and can you produce it. Teams that cannot answer inside a minute are not testing invoices against a contract, they are testing them against a memory of a contract, which is how escalation applied early goes unnoticed for a year.
Turning a rate exhibit into data
Structuring a rate exhibit is data work, not legal work. The aim is records a system can compare an invoice line against, with conditions attached to each rate rather than buried three pages away.
- Normalize the rate structure first. Agree one internal shape for rate lines, code, description, unit, rate, currency and effective dates, then map each supplier exhibit into it. Comparing suppliers is impossible while one bills by the hour and another by the operating day.
- Version the schedule, not the document. Every rate line needs its own effective dates, so a service date selects the governing version automatically. This single control prevents most escalation disputes, because the claim either matches a loaded version or it does not.
- Push the schedule to where approval happens. Field approvers should see contracted categories and rates on the ticket screen. Approval without the rate in view confirms only that the work occurred, which nobody disputes.
- Make escalation a tracked obligation. Record the index, the base, the notice requirement and the earliest permitted adjustment date as an obligation with an owner. Then an escalation claim is checked against a record rather than argued from recollection.
- Test a sample every period. Pull a fixed sample of lines per supplier each month and test them against the schedule. A small, consistent sample finds patterns faster than an annual recovery audit.
A five step roadmap
Step 1, Pick the spend that matters
Start where rate structure is complex and volume is high, usually drilling, well services, wireline, rentals, chemicals and labor supply. Rank suppliers by spend and by the number of rate lines in the exhibit. Two or three contracts normally carry most of the exposure, and that is where structuring pays back first.
Step 2, Structure the rate exhibits
Convert the governing exhibit into records rather than a stored file. Each line needs a code, description, unit, rate, currency and effective dates. Capture the conditions too: standby percentage, minimum charge hours, release requirements, mob and demob triggers and markup ceilings on pass-through items. Note where the exhibit is silent, because silence becomes a dispute.
Step 3, Connect tickets and invoices
Tie each field ticket and invoice line to a rate line and to the schedule version in force on the service date. Where that reference cannot be made automatically, route the exception instead of approving it. Field approval confirms the work happened. Compliance confirms the agreed price was applied, and those are different checks.
Step 4, Audit escalation and commitments
Escalation claims need three tests. Does the contract permit an adjustment, has the stated trigger occurred, and is the calculation applied to the right base from the right date. Give minimum volume and take-or-pay style commitments the same treatment, tracking the counter on your side rather than accepting a supplier statement at period end.
Step 5, Feed findings into the next renewal
Log every exception with its root cause, then use the log in the next negotiation. Ambiguous standby language, missing release conditions, undefined personnel categories and open-ended handling percentages are all fixable at renewal when someone can show what they cost. Without the log, the next schedule repeats the last one.
Test every invoice against the schedule
See how rate exhibits, field tickets and invoices can be held together so exceptions surface before payment.
What a useful exception looks like
The goal is not a report of everything wrong. It is a short queue of priced exceptions an analyst can act on. A useful exception names the invoice line, the rate line it should have matched, the governing schedule version, the money difference and the person who can approve or reject. Anything vaguer becomes an argument about intent. The same principle drives AP invoice automation, where value comes from routing the few lines that fail a test.
Leak, detection and prevention
The table below maps common leaks to a detection method you can run this quarter and a control that prevents recurrence. Detection buys back money once. The control is what stops an external firm finding the same thing next year.
| Leak | Where it hides | Detection method | Prevention control |
|---|---|---|---|
| Standby billed at full day rate | Tickets during weather or waiting on orders | Compare ticket status codes against the standby rate line | Standby rate and release condition coded in the schedule |
| Repeat mobilization charges | Mob and demob lines on sequential pads | Flag a second mob for the same crew within one program | Mob defined per campaign with a named origin |
| Personnel category creep | Named hours on tickets with no category | Map ticket roles to contracted categories and test rates | Category list published to field approvers |
| Escalation applied early | Invoice rates above the loaded schedule | Rate variance report against effective dated lines | Escalation tracked as a dated obligation with a trigger |
| Pass-through markup drift | Consumables and rentals at cost plus handling | Require the supporting invoice before approval | Markup ceiling stated per category in the exhibit |
Rate schedule compliance is not a project with an end date. It is a control between the field and accounts payable, and it works when the contracted price is visible at the moment someone approves a charge. Operators that already hold joint operating and EPC commitments as structured data have most of the pattern, and the value leakage checklist is a practical way to test what you can evidence today.
For related guidance, see The operator’s guide to oilfield master service agreements, Drilling rig day rate contracts, a rate administration sheet and The operator’s guide to oilfield MSA insurance control.
