ONRR Reporting & Severance Tax Software Guide

Federal royalties vs. state severance tax: why operators conflate them

ONRR reporting and state severance tax filing answer different questions. ONRR administers royalty reporting for production from federal and Indian leases. Royalty calculations depend on lease terms and applicable valuation rules. State tax agencies, by contrast, collect severance taxes on taxable production within their states under state-specific rates and exemptions.

The same well can create both obligations. Production from a federal lease may also be subject to a state severance tax, depending on state law. You therefore need separate reporting workflows even when both draw on the same volume measurements and sales records. 

ONRR and state agencies use different forms and filing systems, and they review compliance under different rules. When you evaluate software, ask which workflow it supports and where your staff or a separate compliance tool must prepare the filing.

From the wellhead to the royalty check: how data flows into a report

The amount produced can be determined through measurement, but ONRR royalty reports also require a record of what happened to that production. Volumes at the well or facility are established using meter readings, tank measurements, and field tickets. They must then account for movements, processing, and allocations to link the measured volumes to the amounts assigned to each lease.

Sales records indicate the volumes that produced revenue and the prices at which they were sold. Purchaser statements and settlement records show the quantities sold, proceeds, and any adjustments. Before calculating royalties, the records should be reconciled with the allocated production. A discrepancy could result from a measurement correction, timing difference, or an allocation that requires review.

Revenue accounting links the money received from sales to the lease interests and valuation used for reporting purposes. Division orders and ownership records establish which party receives a share of the revenue, while lease terms and relevant ONRR rules calculate the federal royalty. It is important to keep these two purposes separate. The fact that an amount is paid to an owner does not mean the corresponding royalty is due. Any deduction in the royalty calculation must have its own basis and be supported by appropriate records.

The final report and remittance must be traceable to the volumes, sales, valuation, and calculation records from which they were derived. Purchaser statements, measurement records, allocation workpapers, and deduction documentation should be kept with the reported figures. When a purchaser later changes a price or you correct a volume, record the original amount, the amended amount, and the affected reporting period. This history enables you to explain a correction made in a previous period without reconstructing the transaction during an audit.

What to ask vendors about validation and error-checking

Ask vendors to show how their software compares measured and allocated production volumes with sales records and purchaser statements. The comparison should account for timing differences and documented adjustments rather than treat every mismatch as an error. In a demo, give the vendor a sample month with a volume discrepancy and ask where you would see the variance, its source records, and the person responsible for resolving it.

Check whether you can set tolerances by product, property, or reporting period. Ask what happens when a difference exceeds a tolerance. Does the software warn you, prevent an export, or leave the decision to a reviewer? Have the vendor demonstrate how you would document an accepted difference and find that decision later.

Conversions deserve a separate test because a report can contain internally consistent numbers built on the wrong units or prices. Give the vendor sample records with different volume units, a purchaser price adjustment, and a prior-period correction. Ask them to show each calculation, its input, and any warning the software produces before the numbers reach an ONRR reporting workflow. Request product documentation or a recorded walkthrough for any validation the vendor cannot demonstrate live.

What to ask vendors about 

Request that vendors demonstrate a correction to a previously reported month, not just an edit to the current record. Confirm you can see the original figures, all revisions, who made each change, and which version was used for filing. Include a corrected purchaser statement or price adjustment in the demonstration. Also ask if the software recalculates the affected royalty and retains the original figures.

You should be able to trace any reported amount back to the supporting records. Ask the vendor to provide the previous value, the change date, and the user who made the edit for any altered volume, price, or deduction. Then find out how to obtain the related contract and division order, and how to process the ticket during an audit. Confirm how long those records are kept and whether you can export them with their revision history.

Check the vendor's exports for each filing destination. Ask for sample files and any documentation for any electronic reporting format the vendor supports. Clarify whether the product produces the submission, exports data to another tool, or allows corrections after rejection. Perform the same check for each applicable state portal since filing for state severance tax follows a different workflow. Before relying on a compatibility claim, have your reporting specialist verify the sample exports against the agency's current requirements.

Where severance tax workflows fit in the evaluation

Consider the support for the severance tax separately from ONRR's royalty reporting. ONRR reports royalties from federal and Indian leases, while states handle production taxes according to their own rules. Even if software exports data for ONRR reporting, you still have to calculate the state tax, apply exemptions, and file returns via state portals.

Find out from each vendor which states and types of tax their software natively supports. For each state where you do business, ask for a demonstration starting with production and sales records and ending with a completed return or specified export. Find out who updates the rates, exemptions, forms, and effective dates, and how the software handles corrections for previous periods. Where native coverage ends, determine what manual work or third-party tax engine is needed.

For current rates, exemptions, forms, and deadlines, check with each state's tax agency. Do not assume federal royalty calculations meet state severance tax requirements.

Providence as a data foundation for ONRR and severance reporting

Providence brings field data, production, accounting, revenue distribution, payout, and financial reporting into one platform. For ONRR reporting, those records provide a starting point for checking whether measured volumes, recorded sales, and booked revenue agree before you prepare a royalty report. State severance tax work can draw on the same underlying data, even though it follows separate rules and filing requirements.

The Single Instance Architecture used by Providence maintains field, production, and accounting data within a single system, keeping the data in sync in real time. If a purchaser's statement changes the sales volume or price, use the linked records to compare the difference with both production and accounting data. Request that Avatar show you how the reconciliation works using your own sample records, including a prior-period adjustment. Also, ask Avatar what change history and supporting documents are available for audit purposes. Although shared data helps identify discrepancies, it does not prove the software applies the ONRR validation rules or retains every record an auditor might request.

Consider the preparation and submission of forms as a separate issue when making a purchase. The documentation from Providence does not show that it prepares or files ONRR reports or state severance tax returns. Find out what data Providence can provide for your compliance process, in what format, and whether you will need a dedicated reporting product or a manual process to complete and submit each filing.

Software evaluation checklist

Use the same sample lease, reporting month, and correction scenario when you evaluate each vendor. Ask for a demonstration, then record what the software handles natively, what requires an export, and what requires manual work or a third party.

• Production-to-revenue integration: Trace measured volumes through sales, pricing, and revenue records for one lease.

• Validation and variance checks: Show how the system compares production with purchaser statements and flags volume or price differences.

• Corrections and audit trail: Correct a prior-period entry and show the original value, revised value, user, date, and supporting record.

• Export and filing formats: Demonstrate the actual export. Confirm which ONRR reporting requirements or state portal formats it supports.

• State severance tax coverage: List the states supported natively, including forms, rates, and exemptions. Identify work handled outside the system.

• ONRR filing scope: Demonstrate form preparation and submission if included. Otherwise, identify the required compliance tool or manual process.

Score each criterion against demonstrated capabilities rather than a general claim of “compliance support.” Keep ONRR royalty reporting and state severance tax filing separate in your notes, even when both use the same production and sales records.

Frequently asked questions

• Is ONRR reporting the same as severance tax filing? No. ONRR reporting covers royalties on federal and Indian leases. States administer severance taxes under their own rules, forms, and deadlines.
• How often must ONRR reports be filed? Royalty reporting generally follows a monthly cycle. Check ONRR’s official website for the current requirements and deadlines that apply to your leases and report types.
• What if production volumes do not reconcile with sales volumes? Investigate measurement, allocation, and timing differences before reporting. Keep the purchaser statements and adjustment records that explain any remaining difference or later correction.
• Can one system handle federal and state reporting? Possibly, but shared production and accounting data do not prove that a system prepares or files both types of return. Ask the vendor to demonstrate ONRR support and coverage for each state you need. Check current state requirements and rates with the relevant tax agencies.
• What records should operators retain for an ONRR audit? Keep records that support reported volumes, sales values, deductions, and royalty payments. These may include measurement records, purchaser statements, contracts, calculation workpapers, and correction history. Check ONRR’s official recordkeeping guidance for the applicable requirements.

Choosing a system that holds up under audit

When selecting software, check whether the reported royalty amount can be traced back to production measurements, purchaser statements, valuation inputs, and any corrections. Ask each vendor to demonstrate a previous-period price adjustment and show which records were altered, who made the changes, and what the original report stated. Since federal royalty reporting and state tax filing follow different rules, carry out a separate test for a state severance tax return.

Providence combines data on production, accounting, revenue distribution, payouts, and financial reporting. Before using any operational platform for compliance, check how you will prepare, examine, and file your ONRR reports and state returns. You may still need to use a specialized compliance tool or follow a documented manual process.