Oil & gas · Accounting & financial ops

Billing and financial operations for oil and gas

In field services the lag between doing the work and billing for it is the working-capital problem. It is almost never a decision to bill slowly. It is that the ticket has to physically arrive, be read, be coded, and be re-keyed before an invoice can exist at all. Removing three of those four steps is an accounting outcome produced by an engineering change.

Start a buildIndustry overview
08Invoicing & AR · Reconciliation
Accounting & financial ops08
Invoicing & ARReconciliationClose reporting
Oil & gasIllustrative

Accounting & financial operations

Invoicing, receivables, reconciliation, and reporting that closes.

Accounting & financial ops · Oil & gasOne pairing of the matrix
Service
Accounting & financial operations
Industry
Oil & gas
Covers
Service companies · Working-interest operators · Field & wireline · Midstream services
Architecture
Unchanged from every other vertical — only the breaks differ
Engagement
A defined build, or run under management

What usually breaks

Before anything gets built.

The same failures recur across oil & gas. Strygon maps the specific system before proposing anything, but these are the ones worth checking for.

Paper in the field

Tickets are written by hand at the location and travel back in a truck. Anything illegible, lost, or disputed three weeks later is revenue the company already spent to earn.

Coding after the fact

Costs get coded to the well, lease, or AFE by someone in the office guessing from a ticket, long after the person who did the work could have said.

Invisible until month end

Spend against an AFE is only knowable once the period closes, so an overrun is discovered when it is far too late to do anything about it.

Recurring in oil & gasObserved pattern · the specific system still gets mapped

The approach

What Strygon does about it.

Accounting & financial operations, aimed at those failures specifically rather than at a generic checklist.

01Accounting & financial ops
The ticket is the invoice's source recordAccounting & financial ops
01
Part of the scoped build

The ticket is the invoice's source record

Approved field tickets become billable lines without anyone re-entering them, so billing follows the work by days instead of by weeks.

02Accounting & financial ops
AFE spend visible before the period closesAccounting & financial ops
02
Part of the scoped build

AFE spend visible before the period closes

Costs land against the AFE as they are captured, which makes an overrun something to catch rather than something to discover at month end.

03Accounting & financial ops
Reconciliation with a real exception queueAccounting & financial ops
03
Part of the scoped build

Reconciliation with a real exception queue

Payments match by reference and anything that does not match is queued for a person, rather than being forced into a bucket to make the report balance.

The approach for this pairingScoped in writing before work starts

What gets built

Concrete deliverables.

Everything in accounting & financial operations, applied to how oil & gas actually runs.

All of accounting & financial opsIndustry overview
Invoicing triggered by the event that earned it, not by a calendar reminder
Receivables and dunning sequences that chase payment automatically
Payment matching and reconciliation, with a real exception queue
Two-way sync with QuickBooks, Xero, or NetSuite where an API exists
Revenue reporting joined to the CRM, so cash is traceable to its source
Close-cycle checklists and the reporting the owner actually reads
In scopeScoped in writing before work starts

Also for this industry

Other parts of the same system.

Custom software
Custom software02
Internal toolsData pipelines
Applied hereIllustrative

Custom software

The work happens where there is no signal. Any tool that assumes a connection is a tool the field will go around, and paper wins by default.

Read the custom software read
CRM & automation
CRM & automation03
Pipeline architectureSpeed-to-lead
Applied hereIllustrative

CRM & automation infrastructure

Service work is won on relationships and a callback. The pipeline is usually a phone and a memory, and it does not survive the operator's procurement cycle.

Read the crm & automation read
Local & private AI
Local & private AI01
Self-hosted inferenceRetrieval on private data
Applied hereIllustrative

Local & private AI models

Handwritten tickets, scanned reports, and daily logs are the record. Reading them is exactly the work a model is good at, and exactly the data an operator will not send anywhere.

Read the local & private ai read

Start

Start with what’s broken.

Send the situation in a paragraph. Strygon comes back with a read on what’s likely wrong and what it would take to fix, before anyone talks about price.

Most builds start withleads dying in an inbox., three half-finished pipelines., follow-up nobody owns., numbers that never agree., four vendors blaming each other.

Or email hello@strygon.com

What to send
A paragraph. What broke, and where it shows up.
What comes back
A read on what is likely wrong and what fixing it takes.
Price
The last conversation, not the first