Why is rig crew reimbursements in remote locations for oil and gas companies?

Rig crew reimbursements break down in remote oil and gas locations because of spotty cell service, rotating hitches, paper receipts and AFE or well coding done days later from memory. Vergo takes receipts by text message, with no app to load, and proposes the AFE, well and GL account from your own history, so claims are coded while the hitch is still under way.

October 2, 2026
See it with your ERP
Book Demo

Key takeaways

  • Vergo handles rig crew reimbursements by text message: no app to download or load, and a text sent from a dead zone goes out as soon as the phone picks up signal.
  • Remote drilling and production locations often lack reliable connectivity, which makes app- and portal-based expense capture impractical at the point of spend.
  • Rotating hitches mean the employee who spent the money may be off rotation before receipts reach accounting, creating documentation gaps.
  • Late, miscoded or incomplete rig crew reimbursements distort AFE and well cost reports, delay month-end close and create JIB and audit exposure.

Where should you go next?

Why Rig Crew Reimbursements Break Down in Remote Locations

Remote oil and gas operations are structurally different from office work. A rig crew in the Permian, the Bakken or a remote gathering system may be 90 minutes from the nearest town, rotating on 14-and-7 or 14-and-14 hitches, and disconnected from the accounting office managing the AFE. When a hand buys fuel, safety supplies or a replacement part at a rural supply store, the receipt goes into a shirt pocket or glovebox, and the coding happens days later, from memory, by someone who may not know the right AFE, well or account. That disconnect is not negligence. It comes from geography, connectivity gaps and workflows designed for office staff, not rotating rig crews. Because Vergo runs on plain text messages, a receipt photo sent from location goes out when the phone reaches signal, with no app to open and no login to remember.

What Makes This Problem Persistent

Most expense workflows assume the submitter is near a scanner, has cell service, knows the AFE number and can navigate an approval chain in real time. None of that holds on a remote location. Many rigs and well pads have no reliable LTE or Wi-Fi. Rotating hitches mean the person who spent the money may be off rotation before the receipt reaches accounting. Crews buy fuel, PPE, hand tools, groceries for the camp and emergency parts, sometimes on one receipt, which requires splitting across accounts and wells. Per diem rates are often set by location or crew position and blended with reimbursable expenses, which makes reconciliation painful. The toolpusher or rig manager typically collects receipts and batches them by hand, creating approval bottlenecks and lost documentation before packets reach the office.

The Real Impact on Oil and Gas Accounting

When rig crew reimbursements arrive late, incomplete or miscoded, the effects reach every layer of upstream accounting. Expenses booked to the wrong AFE, well or cost center hide true drilling, completion or lease operating costs until they are reclassified. Accounting teams lose days each close chasing outstanding expense packets and approvals. Purchases with missing receipts or no stated business purpose become findings in internal audits, JIB audits and joint venture reviews, which are routine in upstream partnerships. Large batches submitted weeks after the spend create cash outflows that were never in the forecast. And per diem that is not documented under an IRS accountable plan becomes taxable wages, a risk that scales quickly across large rotating crews.

A Practical Example

A driller on a 14-day hitch traditionally hands a stack of receipts to the toolpusher on day 13. The toolpusher drops them at the office on crew change. An AP clerk keys 22 line items, guessing at the AFE for three of them. Two receipts are illegible, and the close is held open. With a text-based workflow, the same driller photographs each receipt at the fuel stop or supply store and texts it; if the pad has no signal, the message sends on the drive back to camp. Vergo proposes the AFE, well and account from past charges, the driller confirms with a reply, and the rig manager approves from his phone that evening. The approved claim flows to payroll, and the controller sees coded spend by AFE the next morning with the receipt attached.

How Vergo handles this

Vergo handles rig crew reimbursements through a text-based workflow that needs no app download and no portal login. Employees submit receipts and details by text message, which the phone sends as soon as it has service. Vergo proposes the coding by inference from your own accounting structure and history, so new vendors are coded on first sight and nobody on the crew has to memorize AFE numbers or accounts. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project, or skip approval flows entirely and let policy flags catch only what breaks a rule. Transactions are ready to code the moment they happen, with no waiting for clearing, and once they clear they sync into your accounting or ERP software, with approved claims flowing to your existing payroll or AP. Reimbursements run through the same coding model as card spend and AP invoices, so you get one reconciliation instead of three.

Related Questions

Frequently Asked Questions

Why do rig crew reimbursements take so much longer to process than other expense types?

Rig crew reimbursements combine three delays: distance from accounting, rotating hitches that push submission to crew change, and mixed purchases that must be split across accounts and wells. One hand on a 14-day hitch can accumulate dozens of receipts before anyone in accounting sees one, so batch submission creates bottlenecks that are structural, not behavioral.

How do remote-location reimbursements affect AFE and well cost accuracy?

When field expenses are submitted weeks after the spend, they are missing from AFE actuals and well-level costs when managers review them. Drilling and completion AFEs look under budget, lease operating expense per well looks better than it is, and the errors carry across reporting periods until someone reclassifies them.

What IRS accountable plan requirements affect rig crew per diem reimbursements?

Under IRS accountable plan rules, reimbursements must have a business connection, be substantiated with receipts and business purpose, and any excess must be returned. Per diem arrangements that are not documented this way fail substantiation and become taxable wages, creating payroll tax liability for every affected crew member.

How do joint interest billing audits expose problems in rig crew reimbursement records?

JIB audits let working interest partners verify that costs charged to the joint account are supported and correctly classified. Reimbursements with missing receipts, vague business purpose or the wrong AFE or well are routinely challenged and disallowed, reducing recoverable costs and creating partner disputes.

Can a reimbursement workflow work with spotty cell service on remote rigs?

Yes, if it does not depend on an app or web portal. Vergo works over ordinary text messages: a crew member photographs a receipt and texts it, and if there is no signal the phone sends it as soon as coverage returns. Vergo then proposes the AFE, well and account, and the employee confirms with a reply.

How should controllers structure approvals for rig crew reimbursements across multiple AFEs?

A common approach is two tiers: the rig manager or toolpusher approves receipt validity and the AFE or well, then accounting reviews account coding and budget variance. Thresholds tiered by amount let small routine purchases pass after the first approval while larger or split transactions escalate, cutting review volume without losing control of high-value items.

CTA Succes Clicker
Get Started

Expense & invoice automation for your ERP

Book Demo
Book Demo