Equipment Rental for Oilfield Operations
Oilfield accounts are the best and the hardest customers a rental yard can have. The revenue is steady, the holds run long, and the iron stays out. But the rules are different: the rack rate barely applies because nearly every job runs under a master service agreement, standby hours pile up during weather and permit holds, and the equipment ends up on a frac pad an hour past the last paved road. Get the billing structure and the logistics right and oilfield work carries the yard through slow stretches. Get them wrong and you eat standby you never charged, deliver to the wrong county, and argue rate cards at month-end. This guide walks the parts that actually bite.
Why oilfield accounts break a normal rate sheet
A standard rental yard quotes off a rack rate and negotiates from there. Oilfield work flips that. Most of your volume runs under master service agreements with producers, service companies, and midstream operators, and each MSA carries its own negotiated rate per equipment class. The rack rate becomes the exception, not the default. The trap is treating the MSA as a side note your dispatcher has to remember. Tie the negotiated rate to the customer record itself, so every rental for that account pulls the right number without anyone looking it up. A dispatcher quoting from memory is a dispatcher making errors, and on oilfield iron a single wrong class rate is real money on a real invoice. EquipFlow's accounts-and-sites model keeps MSA rates where they belong — on the account.
Standby billing is where the margin hides
On oilfield jobs the equipment sits idle more than most operators admit. Weather days, permit holds, waiting on a rig move, waiting on the company man — the unit stays on location, unavailable to anyone else, and the clock is your decision. Charging nothing for standby quietly hands the customer free risk and ties up iron you could be cycling. The fix starts in the MSA: spell out the standby rate per equipment class, who declares standby and how, and when normal billing resumes. A light tower on standby bills differently than a frac tank on standby. Then your billing has to track active hours and standby hours as separate line items at separate rates, so the invoice is unarguable. Standby caught at month-end is standby you already lost.
Remote-site logistics: it is the site, not the customer
An oilfield customer is rarely one place. The same operator runs pads across several counties at once, and in Texas that means sales tax jurisdiction is set where the iron delivers, not where the account is headquartered. Bill tax off the customer and you will be wrong on half the invoices. Set the delivery site as its own record with its own jurisdiction, its own gate hours, its own directions past the point where the road names stop. Dispatch has to route off that site detail, because a driver hunting for a frac pad in the dark burns hours you cannot rebill. The yards that run oilfield well treat every location as a known site, not a fresh guess each time a job goes out.
Matching the fleet to the work
Oilfield demand clusters around a handful of equipment classes that earn their keep on long holds. Light towers go out the moment a night crew needs the location lit, often on the same call that wakes you before dawn. Frac tanks and mobile storage tanks anchor the longest rentals on the yard — staged for weeks on a pad, billed by the month, and worth tracking unit by unit so none drifts off the books. These are not units you cycle daily, so your utilization math and your rate tiers should reward the hold without giving the iron away. Know which classes carry your oilfield revenue, keep them spec'd for the field, and stage replacements before a long hold ends, not after the call comes in.
Closing the loop: return, inspect, re-rate
A unit coming back from a remote pad after weeks of service is not ready to go straight out again. Run the return inspection before the truck leaves the customer site, tied to the rental record, with required photos that cannot be skipped — because a damage claim you discover back at the yard is a claim you cannot prove. On long oilfield holds, also confirm the rate that actually applied: standby hours reconciled, the MSA class rate honored, the right delivery jurisdiction on the invoice. The discipline is closing each rental cleanly so the next one starts clean. Yards that let returns and re-rates pile up to month-end spend the last days of every month untangling what should have been settled at the gate.
Key takeaways
MSA rates, not the rack rate, are the default for oilfield accounts — tie the negotiated class rate to the customer record so dispatch never has to remember it.
Standby is real margin you give away by accident; define the standby trigger and per-class rate in the MSA, and bill active and standby hours as separate lines.
Texas tax jurisdiction follows the delivery site, not the customer — make every oilfield location its own site record with its own jurisdiction and directions.
Light towers, frac tanks, and mobile storage tanks carry oilfield revenue on long holds — rate and track them for the hold, not the daily cycle.
Close every rental at the gate: return inspection with required photos, standby reconciled, MSA rate confirmed — so month-end is not a cleanup.
Related pages
These pages cover the EquipFlow modules, equipment types, and verticals that intersect with the topic above.
Frequently asked questions
“How do we keep dispatchers from quoting the wrong MSA rate?”
Stop relying on memory or a separate rate sheet. Attach the negotiated rate per equipment class to the customer account itself, so any rental created for that account pulls the right number automatically. A new hire then quotes the same rate a veteran would, and your bookkeeper does not rebuild rates at month-end. When an account renegotiates, you change it once on the record and every future rental reflects it.
“What belongs in the standby section of an oilfield MSA?”
Spell out the standby rate for each equipment class, since a light tower and a frac tank do not idle at the same cost. Name who can declare standby and how, set a maximum duration, and state exactly when normal billing resumes. Put it in writing before the job starts. Without that clarity every weather day and permit hold turns into a relationship argument instead of a clean line on the invoice.
“Why does tax jurisdiction matter so much for oilfield accounts?”
Because one operator runs locations across several counties, and Texas sets sales tax where the equipment delivers, not where the account is based. Bill tax off the customer and you misfile on every invoice going to a different county. Set jurisdiction at the delivery site level so each invoice carries the correct rate automatically, with no manual adjusting and no exposure when an audit asks where the iron actually worked.
“Which equipment should a yard stock to chase oilfield work?”
Lead with the classes that earn on long holds and night work. Light towers move fast whenever a crew lights a location. Frac tanks and mobile storage tanks anchor the longest rentals on the yard, staged on a pad for weeks and billed by the month. Spec everything for the field and rough roads, and stage replacements before a long hold ends so you are never scrambling when the next call lands.
“How do we stop month-end from becoming a billing cleanup?”
Close each rental at the gate instead of letting them stack up. Run the return inspection before the truck leaves the site, tied to the rental and with required photos. Reconcile standby hours and confirm the MSA class rate while the job is fresh. Then month-end is a review, not a rescue. The yards that struggle are the ones discovering unbilled standby and missed jurisdiction after the period has already closed.
See how EquipFlow handles this on a live yard.
Bring your fleet count and a rough sense of your current workflow. Twenty minutes covers the dispatch board live, MSA billing, and an honest answer on fit.
Book a demoStay in the loop
Yard ops notes, once a week.
Operator-written. Covers dispatch, billing, maintenance, and what we ship. No fluff.