Lending operations / GUIDE + WORKSHEET
Track mortgage payoff statements in a controlled queue
Build a payoff request queue that records intake, the response clock, calculation sources, exceptions, review ownership, and delivery evidence.
THE STARTING POINT
For US consumer mortgages secured by a dwelling, assign each written payoff request to a servicing queue that records receipt time, requester, as-of date, source data, calculation owner, reviewer, and delivery. Regulation Z §1026.36(c)(3) requires an accurate payoff statement within a reasonable time and generally no later than seven business days; the rule identifies exceptions such as bankruptcy, foreclosure, reverse or shared-appreciation mortgages, and disasters. Route exceptions to an authorized person instead of relying on a generic timer.
Start the clock when a written request arrives
A US mortgage servicer should create a payoff task as soon as it receives a written request from a consumer or someone acting on the consumer's behalf. Record the arrival time, channel, loan identifier, requester, requested good-through date, and owner. Regulation Z sets a general seven-business-day maximum, while specified situations use a reasonable-time standard; make the applicable exception a person-reviewed state.
- 1Receive requestCapture written request, requester, and receipt time.Secure inbox or portal
- 2Match the loanLink the request to the servicing record and as-of date.Servicing system
- 3Calculate and reviewAuthorized staff check balance inputs and exception state.Servicing staff
- 4Send and recordUse approved delivery and retain the completion evidence.Secure delivery log
Keep calculation inputs with the request
A payoff task needs the servicing source record, good-through date, paid-through date, accrued interest, fees or charges, and any suspense or unapplied funds that affect the figure. Fannie Mae's Servicing Guide has separate payment and payoff procedures for loans in its program. A report can gather the data, but the authorized servicing employee remains responsible for checking the inputs and the statement before release.
- Written requestRequester, receipt time, and requested date
- Loan servicing recordBalance, paid-through date, and applicable charges
- Calculation reviewAuthorized staff verifies inputs and exception flags
- Statement deliverySecure send, timestamp, and receipt evidence
Make exceptions visible before the deadline slips
A bankruptcy flag, active foreclosure, reverse mortgage, shared-appreciation mortgage, natural disaster, or similar circumstance should create a routed exception rather than a silent deadline reset. The queue should retain the reason, source, owner, next check, and any approved timing decision. Keep the ordinary requests moving while a servicing lead or counsel reviews the case that needs a different path.
- LN-204
- Needs attention: Written request matched · calculation review
- LN-317
- Blocked: Requester authority needs confirmation
- LN-408
- Needs attention: Foreclosure exception · servicing lead assigned
- LN-512
- On track: Statement sent · delivery evidence stored
Prove the statement reached the right person
A completed payoff task should preserve the approved statement version, reviewer, recipient, delivery method, send time, and any returned or corrected message. Reconcile open requests to the servicing inbox on a set cadence so a message is not lost when staff transfer the file. If a request is withdrawn, duplicated, or replaced by a new good-through date, keep the history and close the superseded task visibly.
Scattered handling
- Receipt time is buried in an inbox
- Calculation inputs are copied by hand
- A sent message has no linked reviewer record
Tracked handling
- Every request has an owner and clock
- Inputs link to the servicing record
- Approval and delivery evidence stay together
WORKED EXAMPLE / ILLUSTRATIVE
A fictional payoff request queue
These fictional records show different request and exception states; they are not payoff calculations or legal deadlines for a specific loan.
| Fictional file | Queue state | Next owner |
|---|---|---|
| LN-204 | Written borrower request matched to loan | Servicing analyst verifies as-of date and inputs |
| LN-317 | Title agent request; authority not yet confirmed | Servicing supervisor confirms requester path |
| LN-408 | Foreclosure flag; exception review open | Servicing lead checks timing with counsel |
| LN-512 | Approved statement sent securely | Operations records delivery evidence |
MAKE IT USEFUL
Mortgage payoff request worksheet
Use one row per request, including duplicates, exceptions, and reissued as-of dates.
Your notes stay in this page and are not sent to Smithers. Download or copy them before leaving; refreshing clears them.
Before you put it to work
- Confirm whether the request is a written request covered by Regulation Z.
- Record the receipt timestamp and requester before calculating.
- Link every figure to its servicing source and good-through date.
- Route rule exceptions to a servicing lead and counsel.
- Reconcile sent statements and open requests to the intake queue.
Regulation Z §1026.36(c)(3) addresses consumer credit secured by a dwelling and names the creditor, assignee, or servicer as applicable; it is not a universal seven-business-day rule for every business-purpose or commercial loan. Other state and contract duties may apply. This is general information, not legal advice. Confirm requirements with your compliance counsel.
Source notes
These references support the specific product or technical points discussed above. Checked October 12, 2026.
IF THIS LOOKS FAMILIAR
Your tools. Your particular mess.
The worksheet is yours to use. If the difficult part is making it work with the systems you already have, that's the kind of thing we help with.
See the industry context