PMI Cancellation and Termination Is a Date Problem: How an AI Servicing Agent Tracks the Homeowners Protection Act Without Missing the 78 Percent Line

The Overcharge Nobody Meant to Make

A borrower who keeps paying private mortgage insurance after the balance crosses the line the law drew is being charged for coverage the servicer is no longer allowed to require. Nobody at the servicer decided to do that. The premium kept billing because the system that should have stopped it was looking at the wrong number, or measuring against the wrong value, or waiting for a borrower request on a loan that had already passed the point where no request is needed. The Homeowners Protection Act of 1998, codified at 12 U.S.C. 4901 and following, does not care that the overcharge was an accounting artifact. The premium came out of the borrower's payment, so the servicer owes it back, and a pattern of it is the kind of finding that turns a servicing exam into a remediation project.

We build the agent that runs across mortgage servicing on lender and subservicer platforms, and PMI termination is one of the cleanest examples of why a servicing obligation that looks like a calendar reminder is actually a daily computation against a schedule of record. The rules are not vague. The failure is almost never a misreading of the law. It is a mismatch between the number the law names and the number the servicing system happens to have in front of it.

Three Events, Three Different Tests

The HPA defines termination of borrower-paid PMI as three separate events, and a servicer that treats them as one rule gets at least one of them wrong. They key on different numbers and fire at different times.

Borrower-requested cancellation comes first. Under 12 U.S.C. 4902(a), a borrower may request cancellation on the date the principal balance is first scheduled to reach 80 percent of the original value of the property based on the amortization schedule, or the date it actually reaches 80 percent based on payments the borrower made ahead of schedule. The servicer may honor the request when the borrower has a good payment history, is current, and satisfies the servicer's requirements that the property value has not declined and that no subordinate lien has attached. Original value is defined at 12 U.S.C. 4901(12), and it is not one number for every loan. On a purchase it is the lesser of the sales price or the appraised value at the time the transaction was consummated. On a refinance there is no sales price, so it is the appraised value the lender relied on to approve the refinance. Either way it is fixed at origination and does not update when the market moves, which means an agent computing the 80 and 78 percent points has to carry the right original value for the transaction type and not assume a sales price exists.

Automatic termination is the one servicers miss most, because it does not wait for anyone. Under 12 U.S.C. 4902(b), PMI terminates automatically on the date the principal balance is first scheduled to reach 78 percent of the original value, provided the borrower is current on that date. If the borrower is not current on the 78 percent date, termination happens on the first day of the first month after the borrower becomes current. There is no request, no property revaluation, and no good-payment-history condition beyond being current. The servicer has to act on the schedule.

Final termination is the backstop that has no LTV test at all. If neither of the first two events has terminated the coverage, 12 U.S.C. 4902(c) requires termination at the midpoint of the loan's amortization period, provided the borrower is current on that date. On a 30-year loan the midpoint is the first day of month 181. A loan that never reaches 78 percent of original value on schedule, which happens on loans that were modified or that carry a long amortization, still loses its PMI at the midpoint if the borrower is current. If the borrower is delinquent at the midpoint, the statute does not terminate on that date either. Final termination is deferred to the first day of the first month after the borrower becomes current, the same current condition that governs automatic termination. A servicer watching only the 78 percent line will hold coverage on those loans past the point the statute allows, and a servicer that terminates a delinquent loan at the midpoint has moved too early.

The Number the System Has Is Usually the Wrong One

The reason these events get missed is not that servicers do not know the rule. It is that the amortization schedule the law refers to and the balance the servicing system carries are not always the same object.

The 78 and 80 percent tests run against the scheduled balance from the original amortization schedule, measured against the original value. A servicing platform, though, is built to track the actual unpaid principal balance, which diverges from the scheduled balance the moment a borrower pays extra, pays late, or the loan is modified. A borrower who made a large principal curtailment reaches 78 percent of original value on the actual-balance basis well before the scheduled date, and the automatic-termination date still keys on the schedule, while the borrower's right to request cancellation can key on the earlier actual date. A servicer that computes one date from the actual balance and applies it to the wrong event has produced a defensible-looking number that is wrong for the obligation it is being used for.

Original value is the second trap. Servicers that pull a current automated valuation, or that let the borrower's belief that their home appreciated drive the conversation, are measuring against a number the statute does not use for the automatic and borrower-requested events. Appreciation matters for a different path, the investor's own cancellation rules, but the HPA's 78 and 80 percent events are anchored to the value at origination and do not move.

Our agent recomputes the scheduled balance from the amortization schedule of record every day and compares it to the original value on file, not to the current UPB and not to a current valuation. It carries the automatic-termination date, the borrower-requested-cancellation date, and the midpoint final-termination date as three distinct fields on the loan, each computed from the input the statute names for that event. When a borrower prepays, the agent recomputes the actual-balance crossing separately and keeps it distinct from the scheduled date, so the right date drives the right event. The point is not that the arithmetic is hard. It is that the arithmetic has to run against the correct inputs on every loan every day, and a human queue does not.

The Disclosures Are Their Own Obligation

Termination is half the statute. The HPA also requires disclosures on a schedule, and those are missed for the same reason: they depend on the loan's state and its dates, and a servicer that is not computing the dates is not generating the notices.

At consummation of a residential mortgage subject to the Act, the borrower gets an initial disclosure of the cancellation and termination terms and, for fixed-rate loans, a written amortization schedule that shows the dates the 80 and 78 percent points arrive. After that, 12 U.S.C. 4903 requires an annual written statement telling the borrower of the right to cancel or terminate PMI and giving an address and telephone number to reach the servicer about it. When PMI is cancelled or terminated, the servicer has to notify the borrower that the coverage has ended and that no further premiums are due. A servicer that terminates the coverage in the system but never sends the notice has completed the accounting and skipped the consumer-facing obligation the statute wrote alongside it.

The agent generates each of these from the loan's own state. The annual statement fires on the loan's cycle with the current cancellation and termination dates computed fresh, so the borrower is told the actual upcoming dates rather than a boilerplate paragraph. The termination notice is queued the moment the agent marks the coverage ended, keyed to the event that ended it, so the notice and the accounting entry describe the same thing. We log the disclosure, its trigger, and its delivery as a record, because in a servicing exam the question is not whether the servicer believes it sent the notice but whether the file shows it.

The Refund Window Is Short and Strict

When PMI ends, the money side has its own clock. Under the Act, once coverage is terminated or cancelled, the servicer may not require further premiums more than 30 days after the termination date, or after the date the borrower becomes current if that is later, and any unearned premiums the borrower already paid have to be returned within 45 days of termination. A servicer that stops billing but sits on the unearned premium, or that keeps escrowing for PMI a month past the line, has turned a clean termination into a second finding.

This is where the daily computation pays for itself. The agent does not treat termination as a status change and move on. It closes the loop: it stops the premium billing effective the termination date, flags the escrow line for adjustment so the borrower's payment recomputes, and marks the unearned-premium refund with its own 45-day deadline. In a servicing operation running tens of thousands of PMI loans, the illustrative math is not subtle. If even a low single-digit percentage of terminations each month leave a premium billing for one extra cycle, the aggregate refund and remediation is a number the head of servicing has to explain, and the fix is not more staff on a queue but a computation that runs on every loan on the day the line is crossed.

The Investor Rules Sit On Top, Not Instead

The HPA is the floor. Fannie Mae and Freddie Mac impose their own PMI cancellation standards that in places are more generous to the borrower than the statute, allowing cancellation based on current value with a new appraisal once enough time has passed, or at lower LTV thresholds on a seasoning schedule. A servicer of GSE loans has to satisfy both, which means the agent cannot simply implement the statute and stop. It has to carry the investor's rule set for each loan and apply the standard that governs, because a borrower on a Fannie loan who qualifies for cancellation under the investor's current-value path is entitled to it even though the HPA's original-value test has not been met.

Our agent holds the investor rule set alongside the statutory dates and evaluates both, so a borrower is offered the cancellation they are actually entitled to under whichever standard reaches first, and the servicer is not exposed for having applied only the floor. The interaction between statute and investor guide is exactly the kind of thing that gets lost when termination is handled as a manual queue, because the person working the queue is applying one checklist, and the loan is subject to two.

The Honest Read

PMI termination reads like a reminder and behaves like a controls problem. The law is specific: automatic termination at 78 percent of original value on the scheduled date, borrower-requested cancellation at 80 percent with conditions, final termination at the midpoint with no LTV test, disclosures on a schedule, and a refund window measured in days. Servicers miss it not because they misread the statute but because the number their system carries, the actual balance measured against a current value, is not the number the statute names, and because a manual queue cannot recompute every loan against its schedule every day.

An AI agent earns its place here by doing the boring, exact thing: recompute the scheduled balance against the original value on every loan daily, carry the three termination events as distinct dates keyed to the inputs the statute assigns each one, layer the investor's rules on top of the floor, and close the money and disclosure loops on the day the line is crossed. At Sei, we treat PMI termination as a computation the servicer owes the borrower on a specific date, not a task someone will get to. The borrower stops paying for coverage the law no longer allows the servicer to require, on the day the law says, and the file shows why. That is the whole obligation, and it is small enough to state and large enough to fail at scale.