The Trust Operations Guide to Oil & Gas Royalties

The monthly cycle: receipt, verification, posting

Royalty income arrives as checks or ACH from each operator, each with a stub detailing wells, production months, products, volumes, prices, taxes, deductions, and the account's decimal. The cycle is: log receipts against the inventory of expected payors (a missing check is invisible unless something expects it), verify the stub's decimal against the account's division order file, check deductions against the lease's terms, then post income by account and — where the system supports it — by property. Posting royalties as undifferentiated "miscellaneous income" works until the first beneficiary question or audit, at which point the absence of property-level detail becomes everyone's weekend.

Reading the stub like an auditor

Three stub patterns deserve standing attention. Decimal drift: the same property paying a different decimal than last month signals a unit revision, a transfer error, or an operator mistake — all worth a query. Deduction creep: post-production deductions appearing where the lease prohibits them, or growing as a share of gross, is recoverable money leaking monthly. Vanishing payors: an operator that simply stops paying (well offline, operator sold, funds moved to suspense) is the easiest miss in the department because nothing arrives to notice. The expected-payor log converts all three from luck to process.

Suspense and unclaimed property, from the bank's side

When operators hold funds in suspense — title questions after a trustee change, an unsigned division order, an address mismatch — the money is the account's, but only pursuit retrieves it. Operations should keep a suspense ledger by operator and reason, send the curing documentation, and follow until released. The longer game matters too: funds unclaimed long enough escheat to the state as unclaimed property, recoverable thereafter only by claim. Departments inheriting old accounts should sweep state unclaimed-property databases for predecessor trustees and decedents — recovered funds are found money for beneficiaries and a quiet demonstration of diligence.

Transfers, distributions, and the division order loop

Every account event — trustee succession, beneficiary distribution of in-kind interests, account termination — re-runs the title loop: recorded instruments, operator notification, new division orders, and a suspense sweep for the gap. Operations owns the loop's completion, because every unfinished transfer becomes next year's suspense and the year after's escheatment. The operator's side of this same process is covered in our division order guide; trust teams that understand both sides close loops in weeks instead of quarters.

Taxes: ad valorem through 1099s

Mineral interests generate county ad valorem bills (often tiny, easily lost, and lien-bearing when missed) that operations must capture into the payment cycle. At year-end, operator 1099s report royalties gross — before the severance taxes and deductions visible on stubs — so reconciliation to posted net income requires the stub detail, not just the deposit history. Accounts with working interests add JIB cost flows and different reporting. Capturing the stub data monthly is what makes January a report run instead of a reconstruction; our operator-side 1099 guide explains the gross-versus-net mechanics from the issuer's desk.

Beneficiary questions, answered from the system

Royalty income generates predictable beneficiary questions: why did the check shrink (decline, prices, a well down), why does the 1099 exceed the cash received (gross versus net), what is this suspense letter, should the family lease or sell. Operations cannot delegate the answers to hope. The departments that handle this well maintain property-level income detail and activity context so trust officers answer from data — and route the sell-or-keep conversations to the fiduciary, never to the caller's urgency. This is exactly the layer Valor supplies: the mineral.tech® platform gives officers the answer while the question is still on the phone.