Back to workflow library
Revenue & finance

Revenue statement management

Turn royalty and revenue statements into canonical line items, validated totals, explainable exceptions, approved records, and auditable recovery work—without flattening the detail accountants need to trust the result.

Statement review package

Mesa Energy · Owner 10482 · Check 78631

Review required
LineProd. monthVolumeAmount
Oil2026-08182.45 BBL$12,806.14
Gas2026-081,948.20 MCF$4,792.57
Tax2026-08—($893.41)
Deduction2026-08—($514.22)
Statement rollup
Calculated net$16,191.08
Printed check$16,191.08

One exception needs review

Gas price comparison is missing compatible location and contract context.

Line-item complete

Preserve the statement grain and source order

Deterministically validated

Use tested calculations for totals and rules

Exception driven

Focus specialists on supported review candidates

The operating problem

The check total is only the beginning.

A statement becomes useful when every material row can be connected to the right asset, period, party, calculation, validation, and accountable next action.

Every statement arrives differently

PDFs, spreadsheets, exports, scans, and operator-specific layouts create a new preparation problem before reconciliation can begin.

The detail disappears into a header

When source rows, products, deductions, taxes, and production periods are flattened too early, reviewers cannot explain how totals were formed.

Identity and timing do not line up

Payors, operators, properties, wells, products, owner numbers, check dates, and production months vary across systems and require explicit resolution.

Exceptions arrive without a path to resolution

A flagged variance is only a screening signal. Accountants still need the calculation, source evidence, related statement, owner, and next action.

The Sense workflow

From remittance file to accountable resolution.

AI helps interpret variable documents. Parsers preserve source grain. Tested services calculate and validate. Revenue professionals retain authority over material exceptions, statement status, and external action.

Receive and preserve

Automated

Accept approved PDF, CSV, XLSX, manual, or API inputs while preserving the original file, source format, remittance identifiers, ingestion history, and tenant permissions.

Output

Governed source statement and intake record

Parse at source grain

AI + parsing

Read tables, rows, labels, and statement metadata without collapsing valid source detail. Spreadsheet rows retain file order; document extraction remains connected to its evidence.

Output

Candidate statement header and line-item rows

Normalize canonical line items

Deterministic

Map each source row into a consistent line-item model for product, production period, volumes, prices, gross value, deductions, taxes, net value, and source-specific attributes.

Output

Complete canonical line-item population

Resolve operating context

Rules + matching

Resolve the actual remitter, operator, owner number, property, well, product, and production month using source identifiers, aliases, effective dates, and reviewable candidate matches.

Output

Connected line items with match evidence

Roll up and validate

Deterministic

Recalculate statement totals from persisted detail and run arithmetic, completeness, duplicate, sign, date, unit, range, and relationship checks without overwriting the printed check amount.

Output

Recomputed totals and validation findings

Run revenue assurance rules

Rules + evidence

Apply configured audit rules and compatible comparison data to surface supported review candidates. Unresolved units, product context, contract terms, or location differentials remain visible.

Output

Explainable exceptions with supporting evidence

Review and decide

Human controlled

Present the source statement, affected rows, calculation, related asset context, prior review history, and exact proposed action so revenue professionals can correct, reconcile, approve, reject, or reopen.

Output

Accountable statement decision and audit history

Advance exceptions to resolution

Workflow

Convert a verified exception into linked recovery or follow-up work, assign responsibility, preserve correspondence and approvals, and distinguish potential consequence from realized outcome.

Output

Owned case, status, resolution, and documented outcome

Control framework

Fast enough to operate. Precise enough to defend.

Revenue assurance depends on preserving the distinction between source data, calculated results, screening signals, reviewer decisions, and realized outcomes.

One source row stays one line item

Withholding, subtotals, deductions, taxes, and supporting rows are classified rather than silently discarded when they matter to statement reconstruction.

Printed and calculated values remain distinct

The workflow can compare the remittance amount with recalculated detail without rewriting the original source value or hiding a difference.

A variance is not a recovery

Screening results remain candidates until a qualified reviewer confirms the evidence, business context, communication, and final resolution.

Corrections preserve history

Line edits, recalculation, validation, status decisions, linked cases, and reruns retain the responsible user, time, reason, and downstream result.

Model the impact

Build the case from your statement volume.

Estimate capacity using your current statement count, preparation time, target reduction, and loaded cost. Keep capacity separate from unverified recovery value, then validate each assumption against a representative pilot.

Illustrative capacity model

Use measured operating assumptions. These estimates model preparation capacity, not promised savings or recoveries.

Modeled annual capacity

2,508

accounting hours redirected

209

hours available each month

$175,560

equivalent labor capacity

Modeled population: 7,200 statements and 4,560 current preparation hours annually. Validate the baseline and exception burden in a representative pilot.
Structured outputs

A statement record the next workflow can use.

Approved statement intelligence becomes reusable context for reconciliation, audit, asset review, owner support, exception management, and recovery work.

Source statement and remittance metadata
Canonical statement line items
Payor, operator, property, and well matches
Product, production-month, volume, and price detail
Gross revenue, deduction, tax, and net rollups
Validation findings and exception queues
Reconcile, approve, reject, and reopen history
Linked recovery cases and documented outcomes
Connected revenue operations

Preserve accounting truth. Coordinate the work around it.

Statements, remittances, and source files
Accounting, land, ownership, and asset systems
Deterministic rollups, validation, and audit rules
Exceptions, approvals, recovery cases, and outcomes

Integration scope depends on source formats, available APIs, permissions, and write controls. Sense keeps tenant context, source lineage, and approved changes explicit throughout the workflow.

FAQ

Revenue statement workflow questions.

What statement formats can the workflow support?

The workflow can be configured for PDF documents, CSV and XLSX spreadsheets, manual entry, and approved API sources. Each format follows a source-aware parser and validation path so a document extraction envelope is not confused with a spreadsheet row model.

Does Sense replace the accounting or land system?

Not necessarily. Sense can operate as the intelligence and workflow layer around existing systems, preserving canonical line-item detail, connected context, exceptions, and decisions while exchanging approved data through governed integrations.

How does Sense distinguish a payor from an operator?

The workflow treats the printed remitter or payor as a separate business concept from the operator. If the payor is absent or unresolved, Sense keeps that uncertainty visible instead of substituting an operator as a guess.

Can Sense automatically identify underpayments?

Sense can run configured audit rules and assemble supported variances for review. A price or volume comparison may be a screening signal, not a confirmed underpayment. Contract terms, location, quality, units, timing, ownership, and other context may need specialist validation before recovery work begins.

What happens when a statement is imported again?

A production implementation should use stable remittance identity and statement-scoped replacement so a retry does not create a second set of line items. Re-import behavior, uniqueness rules, and exception reuse should be tested on the organization’s actual sources before launch.

How should the workflow be measured?

Measure statement throughput, preparation and review touch time, line-item completeness, match and correction rates, queue age, exception precision, approval reversals, write reliability, and verified business outcomes. Do not treat every detected variance as recovered value.

Start with one statement population

Bring the real formats, line items, exceptions, and approval rules.

Design the workflow