Lease Bonus Payment Proof Packet

A lease bonus is not proven by a canceled check alone. The file has to show what was owed, why it was owed, who was authorized to receive it, when it was released, and whether the funds cleared. When those facts live in four systems and one inbox, the land team cannot answer a simple owner question without rebuilding the transaction.

This guide describes a lease bonus payment proof packet for land administrators. It is an administrative control, not a title opinion, lease interpretation, ownership decision, or substitute for a qualified specialist.

Lease Bonus Payment Proof Packet: what it must answer

The packet should answer six questions: which lease, tract, and interest created the obligation; what rate and acreage produced the amount; who approved the payment and in what capacity; which instrument was issued and to whom; whether the payee received it and the funds cleared; and, if the payment failed, who owns the next action.

If the packet cannot answer all six, it is a payment record rather than a proof packet. That distinction matters during owner inquiries, audit, acquisition due diligence, and project handoffs.

Build the obligation record first

Create one obligation record per lease and tract combination, not one per email thread. Give it a stable identifier that survives personnel and software changes. Record the lease identifier, county and state, recording reference if available, tract identifier, gross and net acres used, bonus rate, and the arithmetic that produced the amount.

Keep the source of each input beside the value. Acreage may come from a survey, a tract schedule, or a prior lease exhibit. The rate may come from a term sheet or an approved negotiation memo. If two sources disagree, show both and leave the obligation open until the authorized person decides.

Name the approval role in the record. A common failure is a payment approved by someone who can sign checks but cannot approve the underlying land deal. The land approver confirms the commercial obligation. Treasury confirms funds and banking details. The administrator confirms the packet is complete.

Capture payee and authority evidence

Payee setup is where many packets break. The name on the lease, tax form, bank account, and land system may differ. Do not normalize the differences away. Keep the legal name, known variants, tax classification, and the evidence used to connect them.

For an individual, collect the tax form, mailing address, and payment method. For joint owners, record each share and whether all signatures are required. For an entity, record the legal name and the document showing signer authority. For a trust or estate, record the fiduciary capacity and appointment document.

Use a controlled payee status: verified, pending evidence, name mismatch, joint payee, returned, or blocked. Each status needs an owner and a next review date. A packet with a pending payee should not be released because a deadline is close. The IRS Form W-9 page is a useful reference for the taxpayer information a payer normally requests, but it is not proof of signer authority.

Separate release, delivery, and clearing

Three events are often collapsed into one date. Release is when treasury issued the instrument. Delivery is when the payee received it or when it entered the mail. Clearing is when value left the payer's account.

Release evidence may be an approval record, a payment batch report, or a check number and issue date. Delivery evidence may be a tracked mail receipt, an email delivery record, or a signed acknowledgment. Clearing evidence may be a bank debit, ACH trace, cleared check image, or positive pay confirmation. A check image without a clearing entry proves that an instrument was printed, not that value moved.

For ACH, retain the batch identifier, payee reference, amount, effective date, and return status. For checks, record the number, issue date, void date, and clearing date. If a check is stale or returned, preserve the original event and add the exception rather than overwriting it.

Reconcile the lease file to the payment file

The lease file and payment file should agree on the same identifiers. A monthly reconciliation compares open obligations, released payments, cleared payments, returned items, and voided instruments.

Any incomplete row needs a reason code, an owner, and a due date. Do not close the packet because the lease was signed or the check was printed. Close it when the evidence standard is met or an authorized person formally accepts the remaining risk.

Handle the exceptions that repeat

Most bonus exceptions fall into a few categories. A payee name differs from the lease name. A joint owner has not signed. An entity's authority document is missing. Acreage changed after the offer. A payment was returned because the address was stale. A check was voided and reissued.

Write a standard response for each. For a name mismatch, request the connecting document and route it to the reviewer. For a missing joint signature, do not split the payment without approval. For a stale address, update the contact record and document the source. For an acreage change, recompute and show the before and after values.

Review open exceptions weekly at 15, 30, and 45 days. Look at the reason mix, not only the count. Growing name mismatches may point to weak intake, while growing returns may point to an address verification gap.

Measure the packet and launch in one project

Track the percentage of obligations with a complete packet before release, median days from execution to release and from release to clearing, returned or reissued payments, and the age of open payee exceptions. Report counts with denominators and aging bands.

Begin with one project and one payment method. Write the field list, status list, and evidence standard. Run ten historical payments through the template and note where evidence is missing. Pilot new payments for two weeks, then hold a weekly exception review. Train the people who request payments, not only those who process them, because most packet defects begin with an incomplete request.

For teams that need help maintaining the evidence while senior land staff stay in the field, a defined lease data entry service can handle indexing and reconciliation. Review authority stays with the client. Teams that also manage signed division orders can use the division order signature follow-up queue to keep owner paperwork moving after the bonus is paid.

Frequently asked questions

Is a canceled check enough to prove bonus payment?

No. It can show that an instrument cleared, but not that the obligation was calculated correctly, that the payee was authorized, or that the payment was applied to the right tract.

What should happen when the payee name differs from the lease name?

Preserve both names, request the document that connects them, and route the question to the authorized reviewer. Do not change either record merely to make the payment run.

How long should the packet be retained?

Follow the client's retention schedule and any contractual or regulatory requirement.