Post-Production Cost Evidence Packet for Royalty Records

Direct answer for mineral owners

Build one evidence row for each reported post-production-cost entry. Preserve the source, payor, displayed property identifier, product, period, exact label and code, amount, unit, stated basis, source location, related adjustment, and retrieval date. Mark support only matched, conflict, missing, or unresolved, then add a neutral question. Do not interpret a lease, decide whether a deduction is allowed, audit a payment, calculate royalty cash flow, or determine value.

Key takeaways for mineral owners

Keep the original statement or remittance page and transcribe the reported label, code, amount, period, product, and identifiers without renaming the entry.
Attach payor legends, correspondence, adjustment notices, and source locations to the exact row they support instead of relying on a detached summary.
Use only matched, conflict, missing, or unresolved for evidence status; none of those labels decides payment correctness or legal permissibility.
Keep regulator production data, tax references, private lease copies, and owner payment records in separate source lanes.
Stop before lease interpretation, royalty auditing, owner-decimal validation, cash-flow modeling, valuation, or transaction advice.

Evidence-only boundary. This article explains how to preserve and connect reported post-production-cost entries in royalty records. It does not interpret a lease, decide whether a cost or deduction is permitted, audit a payment, resolve a dispute, establish an owner decimal, calculate royalty cash flow, reach owner-specific legal or tax conclusions, appraise mineral rights, or recommend a transaction. MRX provides educational information and resources only and does not buy mineral rights.

A post-production cost evidence packet royalty records workflow starts with the source, not a conclusion. Create one row for each reported entry. Preserve the statement or remittance page, payor, property identifier, product, production period, exact label, exact code, reported amount, unit, volume, stated calculation basis, source location, related adjustment, and retrieval date.

Then assign only one evidence status: matched, conflict, missing, or unresolved. A status describes the record connection. It does not say that a charge is allowed, correct, improper, recoverable, or owed.

Why an evidence packet is different from a statement explanation

A royalty statement can place a short code beside an amount, combine several products or periods, or carry an adjustment from an earlier month. A detached spreadsheet may preserve the number while losing the page, code legend, property identifier, or production period that gives the entry context.

The packet prevents that separation. It keeps a reproducible trail from the transcribed row back to the original page and forward to any payor-provided definition, adjustment notice, or written response.

This is a narrower job than decoding a royalty check statement. That guide explains how common statement components relate. The packet in this article records provenance only. It also stops before the reconciliation work in the royalty-check breakdown guide.

Start with the payment record required by the source

For covered Texas royalty payments, Chapter 91 of the Texas Natural Resources Code identifies information that may accompany payment, including source identity, the month and year of sale, volume, price, taxes, other deductions, the owner decimal, and net value. Sections 91.504 and 91.505 also address written requests for certain information or answers from a payor, while Section 91.507 contains an enforcement process for specified missing information.

Those provisions are legal source material, not a fill-in-the-blank remedy. Preserve the current statute, the exact payment facts, and the date and method of any request. A qualified Texas attorney should interpret the statute, the governing documents, deadlines, rights, and remedies for a particular situation.

Build one row per reported entry

Do not combine different products, production periods, properties, or adjustment references merely because the displayed labels look alike. A one-row-per-entry structure lets another person reproduce the match without accepting your conclusion.

Packet field	What to preserve
Source identity	Statement, remittance page, filename or stable reference, statement date, page, line, table, or source location
Payor and account context	Payor name and owner or account reference exactly as displayed; redact sensitive identifiers from working copies
Property reference	Property, lease, well, unit, county, field, or regulator identifier exactly as reported; do not infer a missing match
Product and period	Product label and production, sales, or adjustment period exactly as displayed
Reported entry	Exact cost label, code, amount, unit, volume, and stated calculation basis when shown
Related record	Payor legend, written definition, correspondence, reversal, rebooking, suspense, or adjustment reference
Evidence status	`matched`, `conflict`, `missing`, or `unresolved`
Neutral question	One question that identifies the source or explanation needed to resolve the row
Retrieval date	When the source was obtained; keep this separate from statement, production, and adjustment dates

Use placeholders such as not stated or not displayed when a field is absent. Do not guess a definition, amount, unit, date, or identifier.

Keep five source lanes separate

Royalty statement or remittance detail

This is the observation lane. Transcribe what the selected page displays. Retain the complete page when practical so headers, footnotes, column labels, and adjacent adjustment references are not lost.

Do not convert a displayed label into a different category. If the statement says only a code, preserve only that code until a source tied to the same payor supplies a definition.

Payor legend and written definitions

A legend, portal definition, or written response belongs in the support lane. Record its title, version or date, source location, payor, and the exact code or label it addresses. A definition from one payor does not automatically define another payor’s code.

If a response refers to several properties or periods, do not attach it to every row without a stated connection. Mark the row unresolved and ask which entries the response covers.

Adjustments, reversals, suspense, and correspondence

Keep the original notice and the earlier statement row it references. Record whether the later entry identifies the same property, product, period, and code. A reversal and a repost should remain separate observations even when they appear to offset one another.

The status matched means the recorded identifiers support that document connection. It does not mean the adjustment was calculated correctly.

Regulator production context

The Railroad Commission’s Production Data Query can supply production and identifier context at its available reporting level. Its PDQ FAQs explain that Texas oil production is reported at the lease level, gas at the gas-well level, online data has a reporting lag, and records may change as revised, corrected, or delinquent reports arrive.

Record the query criteria, displayed identifiers, period, retrieval date, and stated limitations. Do not use a regulator volume to prove an owner payment amount, deduction, decimal, realized price, or entitlement. Reporting levels and timing may differ.

Tax and private-instrument sources

Keep tax references in their own lane. The Texas Comptroller maintains separate first-party pages for crude oil production tax and natural gas production tax. Those pages can identify the official administration and reporting context in effect when accessed. They do not prove that a line on one owner’s statement was labeled, calculated, allocated, or withheld correctly.

Retain lease and amendment copies as private source artifacts, but do not summarize their legal effect in the packet. The live guide on how lease royalty rates influence mineral value explains why deduction language is only one part of a broader economic record. Contract interpretation belongs with a qualified attorney.

Apply the four evidence statuses consistently

Matched

Use matched only when the selected support can be tied to the reported entry using the recorded source, payor, property reference, product, period, and code or label. State which fields made the match.

Conflict

Use conflict when two identified sources display different values, codes, periods, definitions, or identifiers for what appears to be the same entry. Preserve both versions. Do not choose a winner inside the packet.

Missing

Use missing when the row refers to a document, legend, page, notice, or definition that is not in the packet. Identify the missing item precisely enough to request it.

Unresolved

Use unresolved when available sources do not establish a reliable connection, or when the record could support more than one explanation. Unresolved is not evidence of error or wrongdoing.

Write neutral clarification questions

A useful question asks for a source or connection instead of assuming a result. Examples include:

“Which dated payor legend defines this exact displayed code?”
“Which property, product, and production period does this adjustment reference?”
“Which source page states the volume, unit, and calculation basis for this entry?”
“Does this written response apply to this account and statement period?”
“Which earlier row is being reversed or rebooked?”
“Can the payor identify the Railroad Commission lease or gas-well reference associated with this property label?”

Avoid loaded questions such as “Why was this illegal charge taken?” or “When will the money be refunded?” Those questions assume conclusions the packet has not established.

Preserve original files and a redacted working copy

Keep the original file unchanged. Name working copies consistently and record a file hash when the packet will be shared across reviewers. The MRX source-trace guide explains how to keep an observation connected to its exact source and retrieval date.

Remove full bank details, taxpayer identifiers, signatures, access credentials, and unrelated personal information from the working copy when they are not needed. Preserve an authorized original separately. The document-redaction checklist provides a separate pre-sharing review boundary.

Stop before interpretation or calculation

The packet is complete when every selected entry has a source location, transcribed fields, evidence status, and neutral question for each gap. Stop if the next step would require you to:

interpret lease, amendment, title, division-order, or contract language;
decide whether a cost is permitted, reasonable, correct, improper, recoverable, or owed;
validate an owner decimal, title, payment entitlement, or damages theory;
reconcile a full statement or perform a royalty audit;
calculate a revised check, royalty cash flow, damages amount, offer, or value;
apply a tax rule to an owner; or
recommend a demand, settlement, signature, sale, hold, or other action.

Those tasks may require a qualified Texas attorney, royalty auditor, accountant, land professional, appraiser, engineer, tax professional, or other specialist. Give the reviewer the original sources and the packet so they can reproduce the evidence trail.

Source notes and research limitations

Texas Natural Resources Code, Chapter 91 supports the bounded description of payment information and written information-request provisions; it does not resolve an owner-specific legal question in this article.
The RRC PDQ FAQs support the production-reporting level, lag, revision risk, and query limitations.
The RRC Production Data Query is the current first-party query surface retained only for identifier and period context.
The Comptroller’s crude oil and natural gas production-tax pages support keeping official tax-administration references separate from other statement evidence.

For a bounded review of records you are authorized to share, request an underwriter review. Bring the original documents with the packet; do not replace them with the transcription.

Frequently asked questions

What is a post-production cost evidence packet?

It is a source-preserving set of royalty-record rows and supporting documents. Each row captures one reported entry, the exact source and period, identifiers, any stated calculation basis, support status, and a neutral question for missing or conflicting evidence.

Should I rename a payor code into a common cost category?

No. Preserve the code and label exactly as displayed. Add a payor-provided written definition as a separate cited field. Do not supply a definition from another company, statement, lease, or internet glossary.

Does matched support prove that a deduction is permitted?

No. Matched means only that the selected supporting document can be connected to the reported entry by the recorded identifiers and period. It does not interpret a lease, validate payment accounting, establish entitlement, or decide whether the entry is legally permitted.

Can Railroad Commission production data verify my royalty deduction?

No. Railroad Commission data can provide reported production and identifier context at its available reporting level. It does not provide owner payment accounting, interpret a lease, establish an owner decimal, or validate a particular statement cost.

Who can review an unresolved cost entry?

Depending on the question, consider a qualified Texas attorney, royalty auditor, accountant, land professional, or other appropriate specialist. Give the reviewer the packet and the original documents rather than only a retyped summary.