Sixth in a series on the oilfield job playbook. The work is done and the tickets are approved. Now the job has to become money. This article is about doing that fast, and doing it so the invoice gets paid on the first pass.
The last article ended with approved tickets: complete, signed, checked against the agreement, and released for billing. This article is about what happens next.
Here is the truth about billing in oilfield services. The invoice is not where the work happens. Everything hard was already done in the field and at close-out. Billing is where all that work either turns into cash quickly, or sits in a dispute queue for sixty days.
The difference between those two outcomes is not luck. It is a handful of habits.
Build the invoice from records, not from memory
An invoice should never be written. It should be assembled.
Every number on it already exists somewhere: the rate in the agreement, the days on the delivery and return records, the hours and quantities on the signed tickets, the serial numbers on all of them. The invoice pulls those records together. Nobody retypes anything.
Why does this matter so much? Because retyping is where errors are born. A rate typed from memory. A day count added up by hand. A serial number copied wrong. Each one is a reason for the customer to reject the invoice, and every rejection restarts the clock on getting paid.
The invoice package that goes to the customer should include:
- The invoice itself.
- The signed field tickets behind it.
- Delivery and return records for rentals.
- Damage or loss documentation, if any.
- The customer’s PO, AFE, and cost codes on everything.
Think of it from the reviewer’s chair. Someone in the customer’s accounts payable office has to approve this invoice. Give them everything they need to say yes, attached, the first time. Make them go ask questions, and your invoice goes to the bottom of the pile.
Know your invoice types
Different work produces different invoices. Keeping them straight keeps billing clean.
- Service invoice. Built from signed field tickets. Labor, services, and consumables.
- Rental invoice. Built from the rental period, delivery to return, at the day or period rate.
- Recurring rental invoice. For long rentals, billed on a cycle, monthly or every 28 days, so cash comes in during the job instead of only at the end.
- Sales invoice. For damage, lost equipment, lost-in-hole, and consumable buyouts. Backed by the evidence package from the last article.
- Subrental pass-through. Third-party equipment you rented in, passed through with your agreed markup.
- Credit memo. The correction document. When something was overbilled, fix it with a credit memo, not by editing history. A clean paper trail matters more than a clean-looking ledger.
Two of these deserve a warning.
Long rentals: do not wait for the job to end before you bill. A six-month rental billed once at the end means six months of your money sitting in someone else’s account. Bill on the cycle.
Multi-well jobs: many operators need charges split by well, by AFE, or by cost code. Find out how they need it split before the first invoice, not after the first rejection.
Check three things before it goes out
Before any invoice leaves the building, someone checks three matches:
- Rate. Does every rate on the invoice match the agreement for this customer and this job?
- Quantity. Do the days, hours, and item counts match the signed tickets and the delivery and return records?
- Detail. Do the serial numbers, item codes, PO, and AFE match what the customer’s system expects?
This is a five-minute check on a clean job. It is also the difference between first-pass approval and a rejection.
A rejected invoice does not just come back. It comes back weeks later, with a question, to a team that has moved on to other jobs. Now someone has to dig up the records, answer the question, fix the invoice, and resubmit to the bottom of the queue. One rejection can cost you a month.
The math is simple. Five minutes of checking beats thirty days of waiting.
Submit fast, and submit their way
Two rules for getting the invoice into the customer’s hands.
Fast. The target is simple: invoice within a day or two of the signed ticket. Every day between the signature and the submission is a day added to your collection cycle, and it is a day you chose to add. The field did its part by capturing in real time. Billing keeps the gain by not sitting on it.
Their way. Most operators tell you exactly how they want invoices: through a billing portal, with specific fields, coded to their cost structure. Meet the format exactly. An invoice in the wrong format is not an invoice, it is a rejection you mailed to yourself.
It helps to keep a one-page profile for each customer: how they want invoices submitted, what codes they require, who approves, and what has caused rejections before. New billing staff get up to speed in a day instead of learning each customer by trial and error.
Watch two numbers
You cannot manage billing on feel. Two numbers tell you the truth.
Days Sales Outstanding (DSO). How many days, on average, between the work and the money. This is the single most honest measure of the whole chain, because a problem anywhere shows up here. Tickets missing signatures? DSO grows. Invoices sitting before submission? DSO grows. Disputes? DSO grows. Watch it monthly, by customer.
First-pass approval rate. What share of invoices get approved without a question or a rejection. This measures quality. When it drops, find out which customer, which job type, and which error, and fix the cause, not just the invoice.
A supporting habit: once a month, look for revenue that never made it out the door. Signed tickets with no invoice. Rental days between the delivery and return records that nobody billed. Damage that was documented but never charged. This unbilled revenue review takes an hour and routinely pays for itself.
When something goes wrong, fix it clean
Mistakes happen. A wrong rate slips through, a day gets double-counted, a customer disputes a line.
The rule is the same every time: correct with a credit memo, keep the original record, and write down why. Never quietly edit an invoice that has already gone out. Your paper trail is your credibility, with the customer and with your own auditors.
For disputes, speed matters more than being right. Answer with the records: the signed ticket, the photos, the agreement clause. That is exactly why all that evidence was captured. A dispute answered in two days with documents usually ends there. A dispute that sits for two weeks hardens into a standoff.
The takeaway
Billing does not create value. It collects the value the whole chain already created. The job is to collect it fast and clean.
Assemble invoices from records, never retype. Attach everything the reviewer needs to say yes. Check rate, quantity, and detail before it goes out. Submit within a day or two, in exactly the format the customer requires. Bill long rentals on a cycle. Correct mistakes with credit memos. And watch DSO and first-pass approval, because those two numbers grade the whole playbook.
Get billing right and nothing about the work changes, but the money shows up weeks sooner. For most companies, that is the cheapest cash flow improvement available.
Next in the series, the final article: KPIs, dashboards, and reports. The numbers that tell you whether the whole lifecycle is working, and how to watch them without drowning in data.