Know what every check paid you, and why.
Drop in your revenue statements. Every line is read, proved against the check total, and kept in a running ledger of gross, taxes, deductions and net — by well, by operator and by month.
| WELL | GROSS | NET |
|---|---|---|
| Sample Fed 12-24 1H | $5,631.40 | $5,249.20 |
| Blue Mesa 11-02 2H | $5,246.64 | $4,856.64 |
| Sample Fed 11-25 1H | $3,561.07 | $3,292.34 |
| Blue Mesa 11-02 1H | $3,255.03 | $3,040.62 |
| Total | $17,694.14 | $16,438.80 |
From a stack of stubs to one ledger
Drop the statement
A PDF from your operator, or the CSV or Excel detail from an owner portal. Drop one or a whole month’s worth at once — they queue up and open one at a time.
Check it against the check
Each statement opens for review, grouped by well. Nothing is added until the lines add up to the check amount, so a misread line cannot slip into your books.
Keep the ledger
Your ledger is saved with your account and follows your login. See it by well, by check, by operator, by month or by year, and print what your accountant asks for.
Your own statement is the evidence
A reading is a proposal for you to review, never a record on its own. The check total is what proves it.
Read from the statement’s own printed text
Most statements produced by an operator’s system carry their own text. Those are read straight from the printed figures and proved against every property total and the check total. No AI is involved.
The AI reader, for what is left
A scan, or a layout that cannot be proved from its text, can be sent to an AI reader — only after you tick the consent box before the read. The software re-adds every tax and deduction row itself and flags any line that does not prove.
Answers you used to dig through stubs for
By well, with volumes and prices
Gross, taxes, deductions and net for every well, broken out by oil, gas and NGL with the volume paid and the average price.
By check
Every remittance as one row — check date and payor — that opens to its properties. Edit a whole check with live totals.
1099 reconciliation
Totals by payor and payee for the payment year, keyed to the check date a 1099 goes by, ready to set beside January’s forms.
Reversals kept honest
Prior-period adjustments and rebooks stay as the statement printed them, signs and all, so each month still ties.
Analysis
Net revenue by month, average sales price, and taxes and deductions as a share of gross — compared by operator, well or product.
Reports and exports
Check register, owner statement, and detail by property or payor. Print-ready, or as CSV. Save the whole ledger to a file any time.
Pick the plan that fits
An entity is one owner’s books: yourself, a trust, an LLC. Each has its own ledger. Every statement read uses one scan. A file read again does not use another, up to three reads of it, and lines entered by hand or imported from CSV or Excel are never counted. The year of scans runs from the day you first sign in.
Already subscribe to oilstats.us? Revenue Tracking is built into your map — sign in there.
Your statements are yours
- The statement file is read on our server and then discarded. Only the ledger lines you approve are saved, with your account.
- Owner numbers are kept as the last four digits only.
- Your ledger is used to serve your account. It is not pooled with other customers’ data, not sold, and not used to train AI models.
- A statement goes to the AI reader only if you ticked the consent box before it was read.
Revenue Tracking reads and totals what your statements say. It does not audit them, compute ownership interests, or give tax, legal or accounting advice. Check every reading against the statement before you rely on it.