Field workflow · Digital field tickets

Digital field tickets: from the wellsite signature to the invoice, without the paper.

The paper field ticket is where one of the most operationally expensive workflows in upstream still lives: signed on a clipboard, carried for days, cost-coded by hand, and reconciled against an invoice that arrives weeks later. WorkSync digital field ticketing closes that loop from the wellsite signature to invoice reconciliation against AFE and LOE budget, on the same device the crew already uses for gauges, inspections and the daily log.

For accounts payable, operations managers, company men and field superintendents

In plain terms

What is a digital field ticket in oil and gas?

A digital field ticket in oil and gas is the record of work a vendor or service crew performed at a wellsite, meaning what was done, by whom, with what equipment, for how long and with what materials, captured on a mobile device at the location instead of on a paper form. It works by having the crew enter the work on the device, the operator’s representative sign it there with a time and location stamp, and the signed ticket travel directly into the operator’s approval queue, where it is coded to a cost line and later matched against the vendor’s invoice. The paper version is the same record, signed on a clipboard and carried, photographed or faxed to the office days later, which is where the approval delay and the invoice disputes begin.

Anatomy of a ticket

What a field ticket carries, and why each line is on it

A field ticket is a line-level record: hours, equipment, materials, chemicals and labor categories, signed by the operator’s representative. On paper, each of those lines is a place for the ticket to go wrong. As a digital ticket, each one is a key the back office can match on.
The ticket, line by line
LineWhat it records
Work performed
What was done at the wellsite, by which crew, on which job.The ticket is captured against the job it belongs to, so the cost lands on the right well.
Hours and labor categories
Crew time by labor category.The line items the vendor will invoice; captured once, in the form the invoice is matched against.
Equipment
The equipment used, by equipment ID.Equipment ID is one of the three keys the reconciliation engine matches invoices on.
Materials and chemicals
Materials and chemicals consumed on the job.A recurring source of disputed lines when it lives only on a paper ticket.
Well or lease and date
Which well or lease, and when.The other two keys the invoice is matched on, and what AFE reporting needs per well.
Cost code
The active AFE line or LOE bucket.Captured at ticket creation and carried through approval, so the cost is visible the day the work happens.
Signature, time and GPS stamp
The operator representative’s digital signature, with the time and location it was given.The paper signature was illegible, undated or lost by the time it reached the office.
Photo evidence
What a line item cannot carry.The dispute that used to be a phone call between AP, vendor billing and the company man is now a picture.

The lifecycle

Four stages. Where paper breaks each, and what the digital ticket changes.

What changes is not the paperwork, it is when the operator knows the number. The same four stages, on paper and as a digital ticket.
Paper against digital, stage by stage
Stage, on paper and as a digital ticket
Stage 01Wellsite captureOn paperThe vendor crew or service company tech records the work on a paper ticket. It lives in a clipboard for hours or days. By the time it reaches the office the signature is illegible, the date is wrong, or the ticket is lost.As a digital ticketThe crew captures the ticket on a mobile device at the wellsite. The operator company man signs digitally with a time and GPS stamp. The ticket exists in the office system before the crew leaves location.
Stage 02Approval routingOn paperPaper tickets accumulate in the company man’s truck, get faxed or photographed to the office, and wait on manual cost coding by accounts payable. Approval takes days to weeks. Tickets get lost on the way.As a digital ticketThe ticket lands in the operator’s approval queue immediately, cost-coded against the active AFE or LOE bucket. Approval happens while the work is fresh, and an audit trail traces every change.
Stage 03Invoice reconciliationOn paperWeeks later the vendor invoice arrives. AP staff match invoice lines to paper tickets by hand. Mismatched lines kick off phone calls between operator AP, vendor billing, and the company man who signed the original ticket.As a digital ticketThe reconciliation engine matches digital tickets to invoice lines automatically on equipment ID, date and well or lease ID. Mismatches surface for human review, not as the default state.
Stage 04Month-end closeOn paperTickets that were lost or delayed past the close date become unrecorded liabilities, surprising the next month’s cost report and distorting AFE-vs-actual and LOE-per-BOE at board reporting time.As a digital ticketA live cost ledger updates with every approved ticket. Close runs on real numbers, not estimates, and AFE-vs-actual and LOE-per-BOE both lock in earlier.
Figure
Where the ticket is filed
Lease Operator driving a field road at dawn with a tablet in a dash cradle beside the centre stack and a pumpjack on the horizon through the windshield
A lease operator's cab at dawn: the tablet in its dash cradle, a pumping unit on the horizon · WorkSync render

How a ticket reaches accounting

Signed at the pad, matched to the invoice, on the ledger before close.

  1. 01 · At the wellsite

    Captured and signed where the work was done

    The crew enters the work on the device. The operator representative signs on the same device, and the signature carries a time and GPS stamp. The ticket is in the office system before the truck leaves the pad.
  2. 02 · Approval queue

    Coded to a cost line and approved while it is fresh

    The ticket lands in the approval queue immediately, carrying its AFE line or LOE bucket and its well or lease. The approver sees it the day the work happened, and every change is in the audit trail.
  3. 03 · When the invoice arrives

    Matched to the invoice on three keys

    DataHub’s reconciliation engine matches invoice lines to approved tickets on equipment ID, date and well or lease ID. Only the mismatches reach a person.
  4. 04 · Close

    On the ledger before the month ends

    Each approved ticket updates the live cost ledger in the accounting system of record. Close runs on recorded cost, and AFE-vs-actual stops waiting on paper that is still in a truck.

Field ticket approval, while the work is fresh

Approval is the stage that paper slows most. A paper ticket cannot be approved until it is physically in the office, legible, and coded to a cost line by someone who has to work out which AFE or which LOE bucket it belongs to. A digital ticket arrives in the approval queue already carrying that: the cost code was captured when the ticket was created, the well or lease was captured with it, and the signature is dated and placed. The approver is looking at the work the day it happened, not a photograph of a clipboard a week later, and every change made in the queue is traced in an audit trail.

That is what lets the approved ticket become the record the invoice is paid against. Cost coding is carried through from ticket creation to invoice reconciliation, and the ticket flows into the accounting system of record (Enertia, PakEnergy, W Energy, Oildex, Quorum, P2 or SAP) through DataHub, whose reconciliation engine matches tickets to invoice lines on equipment ID, date and well or lease ID. The signed ticket is the source of truth for both sides of the invoice, which is why disputed line items fall: the two parties are reading the same record.

Digital field ticket management for a mixed vendor base

Not every vendor will be on the same app, and the flow does not require it. Three capture modes are supported: the vendor uses the WorkSync app, which is the native flow; the vendor stays on its own e-ticketing system and the tickets arrive by API; or the vendor stays on paper, and a scan or photo goes through OCR into the same approval flow. The reconciliation engine runs against all three, so a mixed vendor base reconciles the same way, and the operator manages one queue rather than three.

A distinction worth making

A run ticket is not a field ticket.

The two are searched for together and confused often, because both are tickets signed at a lease. A run ticket is the record of a volume hauled: the oil or water taken from a lease tank, with the tank, the opening and closing gauges, the gravity and temperature corrections, the truck and the driver. It is a production and sales document. A field ticket is the record of work a service crew performed and will invoice for. It is a cost document.

They meet in different parts of the back office. The run ticket feeds allocation and statutory production reporting, which is why it belongs on the production allocation page and the Texas RRC Form PR page, beside the pumper's gauges. The field ticket feeds AFE and LOE accounting, which is this page. Keeping the two apart is what stops a hauled volume and a service cost from being argued about in the same month-end meeting.

Where the ticket is captured

Against the job the site is owed, so the cost lands on the right well.

A field ticket in WellOPS is not a blank form. It is captured against the work the site screen already lists: the job that put the visit on the plan, on the well the screen names, priced by what the well is doing against its own history. A ticket captured that way already knows which well and which job it belongs to, which is the whole cost-coding problem solved at the moment of capture rather than in accounts payable a month later. Vendor and company-labor tickets are captured the same way, so cost lands on the right well either way.

It is the same app the pumper already has open for the gauges, the inspection and the daily log. The exception, the maintenance job, the capture, the cost and the safety paperwork sit on one screen with one login. The field does not need an eighth app. It needs one. The capture layer itself is described on the Field Data Capture module page, and how a ticket signed with no cell signal reaches the office is on the offline capture page.

Rendered from the synthetic field fixture · synthetic demo data · no customer screen

WellOPS site screen, Alderridge F-7HWhy you are here: High Fluid Level, critical, 95.7 BOE a day deferred, $5,627/d, 70% confidence. Recommended: Retune the pump off controller and reset the fillage setpoint. Synthetic demo data.6:44SYNTHETIC DATAAlderridge F-7HCRITICALRank #1 of 46Lease Alderridge · Pad Alderridge 1 · Rod pumpOverviewWork · 1ProductionInfoWHY YOU'RE HEREHigh Fluid LevelHigh fluid level, flagged 23:06, open 31hDEFERRED95.7 BOE/dVALUE AT RISK$5,627/dCONFIDENCE70%EXPECTED BACK$3,939/dRECOMMENDED ACTIONRetune the pump off controller and resetthe fillage setpoint.Go to work · 1 must-do leftPRODUCTION · BOE/DEXPECTED255.9CURRENT143.3DEVIATION-44%MUST COMPLETE1 itemCRITICAL~71mHigh Fluid LevelRetune the pump off controller and resetScoreRouteSitesMapMore
The site screen, and the work the ticket is captured against. Synthetic demo data.

Where it fits

One piece of the upstream cost-control loop.

Field ticketing is the cost side of the same wellsite visit that produces the daily log. The ticket's cost code ties it to AFE tracking, where AFE-vs-actual stops waiting on paper, and to the controllable LOE that a per-well cost view makes visible. The ticket is tied to the ranked work in Work Engine, so the cost of a job sits beside the production it recovered, and the matching that closes the loop at the invoice is DataHub's. The broader discipline is upstream optimization; the reference deployment, a top 25 private producer across 5,000+ wells in live deployments, is on the case study.

The pilot covers one active drilling, completion or workover program. Vendors are onboarded in days, the reconciliation engine runs within the 4-week stand-up, and the two results that matter, reconciliation time coming back to the close roles and disputed line items falling, are measured on your own tickets rather than assumed from a benchmark. Under the Impact Guarantee, license fees only when the metrics move.

Frequently asked

What AP and ops managers ask about digital tickets

What are digital field tickets?
Field tickets are the line-level vendor records of work performed in the field: hours, equipment, materials, chemicals, labor categories. Historically these were paper tickets signed at the wellsite, scanned, mailed, faxed, or photographed back to the office for invoice processing. Digital field tickets replace that chain with a direct mobile-to-office capture flow with signature, GPS stamp, time stamp, photo evidence, and direct routing into the operator's approval workflow and invoice reconciliation.
What does paper field ticketing actually cost?
Three compounding costs. (1) Reconciliation time: each missing or illegible paper ticket spawns 30-60 minutes of phone calls between operator AP, vendor billing, and the company man. Operators with 200+ AFE-active wells routinely have 1-2 FTEs in field-ticket reconciliation. (2) Disputed invoices: 8-15% of vendor invoices get disputed at the operator side because the underlying paper trail does not reconcile (illustrative industry figures). (3) Unrecorded liabilities: tickets that get lost or delayed past month-end show up as surprises in the following month's close, distorting the cost model.
How does WorkSync digital field ticketing work?
Vendors and operators capture tickets on a shared mobile app at the wellsite. Operator company man signs digitally with timestamp + GPS. Ticket carries equipment ID, labor categories, materials/chemicals, and photo evidence. The ticket lands in the operator's approval queue immediately, gets coded against the active AFE or LOE budget line, and reconciles against the eventual vendor invoice automatically. No paper.
How does this integrate with our accounting / AFE / ERP system?
Digital tickets flow into Enertia, PakEnergy, W Energy, Oildex, Quorum, P2, or SAP via the DataHub. Cost coding (AFE line, LOE bucket, well/lease) is captured at ticket creation and carried through invoice reconciliation. The DataHub's reconciliation engine matches tickets to invoices on equipment ID, date, and well/lease ID.
Does this work with vendors who are not on the WorkSync app?
Yes. Three capture modes are supported. (1) The vendor uses the WorkSync app, which is the native flow. (2) The vendor stays on its own e-ticketing system and the tickets arrive by API. (3) The vendor stays on paper, and a scan or photo goes through OCR into the same approval flow. The reconciliation engine runs against all three, so a mixed vendor base reconciles the same way.
What is the ROI on digital field tickets?
Two compounding wins. (1) Reconciliation time comes back to the month-end close roles that were spending it chasing paper. (2) Disputed line items fall, because the signed digital ticket is the source of truth for both sides of the invoice. Both are measured on your own tickets during the 4-week pilot rather than assumed from a benchmark, under the Impact Guarantee: license fees only when the metrics move.
What are electronic field tickets in oil and gas?
Electronic field tickets and digital field tickets are the same thing: the vendor or service crew's record of work performed at a wellsite, captured on a device at the location rather than on a paper form. The ticket carries the hours, equipment, materials, chemicals and labor categories, the operator representative's signature with a time and GPS stamp, and photo evidence where it helps. Because it is a record rather than a piece of paper, it can travel straight into the operator's approval queue and be matched to the invoice later, which is the part the paper version cannot do.
How does field ticket approval work with digital tickets?
The ticket lands in the operator's approval queue the moment it is signed at the wellsite. It is coded against the active AFE or LOE budget line, routed to the approver, and every change to it is recorded in an audit trail. Approval that waited on a paper ticket reaching the office, being photographed, and being cost-coded by hand now happens while the work is still fresh, and the approved ticket is already in the form the invoice will be matched against.
Is a run ticket the same as a field ticket?
No. A run ticket is the record of a volume of oil or water hauled from a lease tank: the tank, the opening and closing gauges, the gravity and temperature corrections, the truck and the driver. A field ticket is the record of work a service crew performed and will invoice for. They meet in different places: the run ticket is a production and sales document that feeds allocation and statutory production reporting, while the field ticket is a cost document that feeds AFE and LOE accounting. WorkSync treats them that way. Field tickets follow the approval and invoice-reconciliation flow on this page; the volume side is covered on the production allocation and Texas RRC Form PR reporting pages.
How does a digital field ticket reach accounting?
Through DataHub, with the cost coding attached. The AFE line, the LOE bucket and the well or lease are captured when the ticket is created, carried through approval, and delivered to the accounting system of record (Enertia, PakEnergy, W Energy, Oildex, Quorum, P2 or SAP) by direct integration. When the vendor invoice arrives, the reconciliation engine matches its lines to the approved tickets on equipment ID, date and well or lease ID, so the ticket that was signed at the wellsite is the record the invoice is paid against. Nothing is re-keyed between the pad and the ledger.

Are your best people working on your most valuable work today?

Replace paper tickets in 4 weeks.

Pilot covers one active drilling, completion, or workover program. Vendors onboarded in days. Reconciliation engine running by Day 14.