Operations
Land Software Protects the Lease. Nothing Protects the Pay Deck.
By Better Software · Thu Sep 17 2026 · 9 min read
Every land platform you have been quoted is built to stop you losing a lease. If your acreage is held by production, that is a bounded risk. The unbounded risk is the ownership record: the division of interest that decides who gets paid, at what decimal, for which production month. Nothing on the market reconciles that record against what accounting actually paid. When it breaks, the failure mode is not a missed rental. It is statutory interest, fee-shifting litigation, and suspense balances aging into unclaimed-property liability. Here is how to tell which problem you actually have.
Two different records, two different risks
Most operators use “land” as shorthand for a leasehold control system. That is not wrong. It is just incomplete. The leasehold record and the ownership record solve different problems, fail in different ways, and touch different people.
| Record | What it controls | What failure costs | How you detect it | Who feels it |
|---|---|---|---|---|
| Leasehold record | Leases, expirations, rentals, shut-ins, acreage, obligations | Lease expiry, missed payment, lost acreage | Calendar / obligation tracking | Land, leases, acreage management |
| Ownership record | Division order, division of interest, pay deck, owner changes, suspense, as-of-date ownership | Wrong pay, suspense, interest, escheat, owner disputes | Reconciliation against actual paid decimals | Land, division order, revenue, accounting, owners |
The first risk is bounded because a lease either expires or it does not. The second is unbounded because every owner change, title correction, probate filing, address update, assignment, or acquisition can change who should be paid, when, and how much. In a small operator with a few hundred owners, the records can look “close enough” for years. Then one acquisition imports a seller’s unresolved pay deck and suspense balances, and the gap becomes visible in the worst possible way: by complaint, not by control.
What the land platforms actually do
The category is not fake. It is just optimized for leasehold protection, mapping, documents, and obligations. The commercial pages for W Energy, Enertia, Quorum, PakEnergy, and IFS iLandMan all present land as a system for leases, title, documents, and upstream asset administration. Some mention ownership data. Some mention division orders. None of the product pages reviewed present a control that says: “show me every owner whose land-record decimal differs from the revenue system’s paid decimal for a given production month.” That is the gap.
| Vendor | Primary land claim on public page | Division orders named? | Size class implied | Pricing |
|---|---|---|---|---|
| W Energy | Upstream land, ownership, lease administration | Yes, in separate content about division order processing | Mid-market upstream operators | Demo-gated |
| Enertia | Land contracts, mapping, documents, lease records | No explicit operator-side DOI reconciliation claim | Upstream and land-centric teams | Demo-gated |
| Quorum | Upstream land within broader energy suite | Not as a reconciliation control | Enterprise / multi-asset | Demo-gated |
| PakEnergy | Land management, documents, leases, obligations | Not as a paid-vs-owed control | Upstream operators | Demo-gated |
| IFS iLandMan | Land management for upstream oil and gas | No clear public DOI reconciliation workflow | Enterprise upstream | Demo-gated |
The honest read: these are good leasehold systems. They are not ownership reconciliation systems. Native integration between land and accounting may reduce manual entry, but integration is an architectural claim, not a control. A system can pass data cleanly from one side of the seam to the other and still fail to tell you whether the two sides agree.
“A spreadsheet and a filing cabinet work fine” — when that is true, and when it is dangerous
Steel-manning the argument: if you have a small lease inventory, few owner changes, no active acquisition program, minimal suspense, and one person who knows every title oddity by memory, Excel and a filing cabinet can be adequate for leasehold tracking. On the lease side, that is often true.
On the ownership side, the test is different.
Ten-minute self-test
- How many owners are currently in pay?
- How many owner changes happened in the last 12 months: deaths, probates, affidavits of heirship, assignments, address updates?
- How much royalty is currently in suspense?
- How many properties came from acquisitions in the last three years?
- Can you reconstruct who owned a specific interest during June 2024 without a week of manual work?
- Can you compare what land says you owe against what revenue actually paid for that month?
If the answer to any of those is “not quickly,” then your problem is not whether land software can store leases. Your problem is that you do not have an as-of-date ownership control.
The reconciliation nobody sells you
This is the missing control: for each production month, for each property, compare the division of interest in the land record to the decimals actually paid in the revenue system. The output is an exception report with owner, property, month, land decimal, paid decimal, delta, and dollar impact.
That sounds simple because the math is simple. The hard part is the data model. You need an effective-dated ownership ledger, not a current-state owner table. You need to know what the ownership looked like as of the production month, not just what it looks like today. That means tracking owner life-events and title events as dated changes: death, probate, affidavit of heirship, assignment, transfer, address change, title opinion revisions, recoupment, and operator change.
Why no vendor builds it? Because most land systems sit on one side of the seam and most accounting systems sit on the other. Each can export data. Neither is designed to assert that the other side is wrong. That is why “integrated” is not the same thing as “reconciled.”
Suspense, from the operator’s side
In operator terms, an oil and gas suspense account is where you park revenue when you are not yet able to pay the owner. Common causes include an unsigned division order, a title defect, an heirship gap, an unlocated owner, a stale address, minimum-pay thresholds, or carried-over issues from an acquisition.
Suspense is not just a temporary holding bucket. It is a managed liability. It should be aged, reason-coded, and reviewed against a release workflow. If it sits long enough, it can become an unclaimed property problem, with escheat exposure under state law. If the owner’s address is unknown, the reporting obligation may flow to the state of incorporation or another state-specific destination depending on the facts and the statute. The point is not the destination. The point is that aged suspense is not harmless.
Definition: an operator-side suspense account is unpaid production revenue held because the operator cannot yet establish, document, or execute the correct payment path to the owner.
Procedure: age the balance, code the reason, trace it back to the ownership event, and reconcile it monthly to the pay deck.
Decision rule: if you cannot explain why a balance is still in suspense after one payment cycle, you do not have a payment issue — you have a record-keeping issue.
What owners complain about tells you where the data broke
Owner forums are useful because they describe failure modes in plain language. The complaints are familiar: “show their math” on an NRI decimal; a decimal that credits 12.5 of 40 acres; royalty suspended after an heirship gap with no end date; funds held after an operator change because checks went to a three-year-old address; unclaimed balances surviving an assignment.
Each complaint maps to a data defect. If an owner says the decimal is wrong, your division of interest either disagrees with the title chain or was never reconciled to the pay deck. If royalty is suspended after an heirship gap, your workflow has no effective-dated owner resolution. If funds were sent to an old address, your owner-change pipeline did not propagate. If an assignment happened and the balance remained unresolved, your transfer control failed to close the loop.
Build, buy, or neither
The right answer is not “buy more land software” by default. It depends on what you actually need to control.
| Need | Buy | Build | Neither |
|---|---|---|---|
| Lease obligations, expirations, rentals, shut-ins | Yes | No | No |
| Document OCR, mapping, obligation calendars | Yes, if active leasing matters | Only if highly custom | No |
| As-of-date ownership model | Rarely out of the box | Yes | No |
| DOI-to-paid reconciliation | No common off-the-shelf control | Yes | No |
| Suspense ledger with aging and reason codes | Sometimes partial | Often yes | No |
| Owner-change pipeline and escheat readiness | Usually partial | Yes | No |
| Sub-threshold operator with very few owners and little suspense | No | No | Maybe |
“Neither” is a real answer for a tiny operator with minimal owner complexity. But if you have hundreds or thousands of owners in pay, a steady acquisition cadence, meaningful suspense, and no way to answer who owned what as of a given production month, spreadsheets are no longer a strategy. They are an explanation for why the question takes a week.
FAQ
What is a division order?
A division order is the instruction set for paying revenue from production. It states who gets paid and in what decimal, based on the ownership interest established by title and lease terms.
What is a division order title opinion?
A division order title opinion is the legal title work used to determine ownership and payment decimals before proceeds are disbursed. It is one of the inputs to the pay deck, not the pay deck itself.
What is a division order in oil and gas?
In oil and gas, the division order is the document or record that tells the operator how to divide production proceeds among owners. It ties title findings to payment.
Are division orders required in Texas?
Sometimes operators rely on division orders before paying, but the answer is fact- and statute-specific. The relevant issue is whether the operator can lawfully establish the pay position and whether payment timing triggers interest exposure under applicable law.
What is an oil and gas suspense account?
It is the account where revenue is held when the operator cannot yet pay the correct owner. Common reasons include title defects, missing documents, heirship gaps, and unresolved owner identity or address issues.
How long can an operator hold royalty in suspense?
That depends on the reason the funds are suspended, the applicable state law, and whether the operator has exercised reasonable diligence. The practical answer is: not indefinitely. Aging suspense becomes both a payment dispute and a compliance risk.
Who owned this interest during a past production month, and how would I prove it?
You prove it with an as-of-date ownership ledger: an effective-dated record of title events, owner changes, and DOI changes, linked to the production month and reconciled to the paid decimals.
Closing
Land software protects the leasehold. That matters. But if your business has thousands of owners in pay, the more expensive failure is the one on the other side of the record: who owned the interest, what decimal should have been paid, what actually got paid, and what is now sitting in suspense. That is the control gap.
The transferable lesson is not that Better has an upstream land product. It does not. The transferable lesson is the pattern: an effective-dated ownership ledger with a reconciliation control on top, which is the same shape Better has built in energy information workflows and regulated ledger work. The problem is not more storage. It is reconciliation.