Months until the balance reaches a loan-to-value threshold

How long the schedule alone takes to cross a line

The question is when a declining balance meets a fixed line. The line is a chosen share of the property’s value at origination; the balance is the one a level, fully amortising schedule produces month by month. Because the denominator is the original value and never moves, nothing the property market does can bring the crossing forward — this is the wait a borrower is committed to from the first payment, before any of the faster routes are considered.

It is solved in closed form rather than by walking the schedule. The standard balance identity is inverted for the exponent, which returns the crossing directly as a count of months. The consequence worth knowing is that the answer is fractional: it names the point at which the balance passes the line, not a billing date, not a servicer’s decision and not a whole number of payments. A reader who needs a payment number rounds it themselves, upward, and should expect a real cancellation to trail the arithmetic rather than lead it.

The threshold is an input. Where a governing rule, a loan programme or a servicer’s own practice sets the level at which a premium ends, that figure is what belongs in the box; the pack carries a customary default and describes it in its own help text as a convention made explicit, and the permitted band is wide enough to hold both the automatic and the requested-cancellation levels people commonly encounter. No level is asserted here and none is treated as binding, because the terms of a particular loan decide that and a signed calculator has no view on them.

What dominates the answer is how far the balance has to travel, and then how quickly the schedule moves it. Both are set at origination: the deposit fixes the distance, and the term fixes the pace. The early months of a long schedule are the slowest principal repayment the loan will ever see, so a thin deposit on a long term produces a wait measured in years, while the same starting position on a short term is cleared in a small fraction of that. The rate matters too, but far less than either.

Every faster route out is deliberately outside this calculation. Overpayments, a lump sum, a recast, a refinance, or a cancellation argued on a current appraised value rather than the original one — each of these shortens the wait and none of them is modelled. The figure here is the baseline they are improvements upon: what happens if nothing at all is done.

The pack also declares a reverse reading, returning the threshold that a chosen number of months would reach. That is the useful direction when the deadline is the fixed thing — a move, a review date, a budget that needs the premium gone by a certain point — and the question is what position the schedule can actually deliver by then.

When this calculation is used

• Sizing how long a mortgage-insurance premium is expected to be paid if the schedule is simply left to run.
• Comparing a shorter term against a longer one on how quickly it clears a loan-to-value line, rather than on the instalment.
• Putting a duration on a larger deposit, by re-running with a smaller loan against the same property value.
• Checking a cancellation point quoted by a servicer against the schedule it is supposed to follow.
• Deciding between waiting for amortisation and acting on the balance directly, by seeing what the passive route costs in months.

Worked example

The pack declares three vectors, two of which are built as a matched pair: they start from the same loan-to-value position and aim at the same threshold, differing chiefly in that one runs over half the term of the other. The third starts from a markedly thinner deposit and aims at the more lenient of the two thresholds used.

The matched pair is the whole argument. Same starting position, same target, only a modest difference in rate — and halving the term cuts the wait to under a third. That is more than proportional, and it is why the short-term schedule feels so different in its first year: principal repayment starts fast and never has to accelerate. The third vector then shows the other lever at work. Its threshold is the easier of the two, yet it waits years where the pair wait months, because a thinner deposit leaves the balance far further from the line and a long schedule is at its slowest exactly where it has furthest to go. A lenient threshold does not rescue a small deposit. Note also that one vector lands a hair below a whole month: the output is a crossing point, not a billing period, and rounding it is the reader’s decision. Alongside it the pack reports the balance the threshold corresponds to, which is the figure to compare a statement against.

The pack declares a distinct refusal for the case where the question does not arise: a loan that already starts at or below the threshold is declined as not applicable, rather than answered with a wait of nothing. The difference matters — a wait of nothing would read as an event about to happen, when in fact no such event is pending. Every figure shown is produced by the certified engine at mount, and none of it states when any charge will actually end.

What each input represents

Assumptions and limits

• Amortisation only: no appreciation, no overpayments, no recast, no refinance and no missed payments — the schedule is left to run exactly as written.
• The denominator is the property’s value at origination. Routes that rest on a current appraised value are a different question and are not computed here.
• The schedule is fixed-rate, level-payment and fully amortising, with the periodic rate taken as the annual rate divided by the payments in a year.
• The result is a fractional count of months from the first payment — a crossing point rather than a servicer’s date, and not a statement that any charge ends then.
• The threshold is whatever the reader enters; the terms of a particular loan, and any rule governing it, decide the level that actually applies.
• No premium amount enters the calculation, so how much the charge costs while it lasts comes from elsewhere.

What the guards protect against

• A loan that already sits at or below the threshold is refused with its own not-applicable code, and the pack pins that behaviour with a declared vector. It is not an error and not a wait of nothing — it is the calculation saying the crossing has already happened.
• The rate must be strictly greater than nothing, unlike elsewhere in this pack. The closed form divides by the periodic rate and takes a logarithm of a ratio built from it, so a rate of nothing has no solution in this form rather than an obvious one.
• The loan amount, the property value and the term must each be greater than nothing, so the schedule the crossing is measured along genuinely exists.
• The threshold is bounded to a band spanning the levels commonly written into loan terms; outside it the calculation is refused rather than answered, because the target would describe no cancellation anyone is working toward.

Provenance

Closed-form inversion of the level-payment amortisation balance identity

The level instalment derived from the loan amount, the periodic rate and the payment count; the target balance taken as the original property value times the threshold share; and the balance identity solved for the exponent, giving the crossing as a fractional number of months.

Educational reference, not financial advice, and not a lending decision or a statement of when any premium actually ends — the threshold is an input, and the terms governing a particular loan decide both the level and the process. The signed pack carries its own citation, which displays from the verified leaf once the calculator loads; the page reports the verification state of the release it mounted rather than asserting one.