Treadstone Associates
Case File № 433 · Bruised Credit & Consolidation

Not bad credit

stale credit. A Brantford file paid its cards to zero, and the bureau hadn't caught up

Two credit cards were paid to zero a week before this Brantford application, but the bureau still showed both near their old balances -- each issuer only reports as of its own statement-closing date, and the next natural cycle landed after closing. A rapid rescore, not a payoff, is what actually met the deadline.

OntarioInsured · PurchaseFiled August 9, 20265 min read
592 → 615

credit score before and after a rapid rescore confirmed two already-paid-down card balances

14 days

left to close when the stale score was pulled -- well short of the next natural reporting cycle

3 days

how long the rapid rescore itself actually took, against a 24-day wait for the cards' own statement dates

Anonymized illustration. The borrowers, dollar figures, and rates in this file are an illustrative composite — no real client is identifiable, and any rate shown is illustrative, not a quote. The rules are real: every regulatory figure is cited to its source in the Sources section, and the math computes exactly as shown.

№ 01

The client

A first-time buyer in Brantford, Ontario, is purchasing at $340,000. Two credit cards were paid to a zero balance a full week before applying -- and a bureau pull still returned a credit score of 592, below CMHC's 600 floor.

Purchase price

$340,000

Brantford

Cards paid to zero

1 week before applying

Both fully paid down

Score as pulled

592

Below CMHC's 600 floor

Days to closing

14

A hard deadline

Next natural reporting cycle

24 days out

Past the closing date

№ 02

The problem

Paying a credit card to zero doesn't update a bureau file the moment the payment posts. Each issuer reports a card's balance as of its own monthly statement-closing date -- and neither of these two cards' closing dates had come around yet when the file was pulled. The bureau was showing balances that were already out of date, not a genuine credit problem.

Why waiting wasn't an option

  • Both cards' next statement-closing dates, and the reporting that follows them, were 24 days out
  • Closing on this purchase was 14 days out -- ten days short of even the earliest natural update
  • The utilization driving the low score was real when the cards carried balances -- it just wasn't true anymore, and the bureau hadn't been told

The applicant hadn't done anything wrong. The bureau simply hadn't caught up to what was already true.

№ 03

The numbers

Once the timing problem was correctly separated from a credit problem, the insured math itself was straightforward, consistent with broader credit-score statistics for Canadian mortgage borrowers.

The insured purchaseAmount
Purchase price$340,000
Minimum down payment (5%)$17,000
Base mortgage$323,000
CMHC premium (4.00% at 90.01-95% LTV)+$12,920
Total insured mortgage$335,920
Ratio check at the qualifying rateFigure
Minimum qualifying rate on a 4.90% contract rate6.90%
Payment at the qualifying rate, 25 years$2,332
GDS (payment + $270 tax + $115 heat) ÷ $7,600 income35.8%
TDS (GDS numerator + $260 car loan) ÷ $7,600 income39.2%

35.8% GDS and 39.2% TDS were never close to a problem. The bureau's stale balances were the only obstacle, and they weren't even accurate anymore.

№ 04

The solution

A mortgage agent licensed under Ontario's Mortgage Brokerages, Lenders and Administrators Act identified the score drop as a timing problem before treating it as a credit one.

First, confirmed with both issuers exactly when each card's statement closes, and confirmed both balances were genuinely at zero. The paydown was real; the bureau simply hadn't been told yet.

Second, calculated the actual timeline: 24 days to the next natural update against 14 days to close. Waiting was never going to work, whatever the underlying credit was worth.

Third, arranged a rapid rescore with both issuers, confirming the updated balances directly to the bureau outside the normal monthly cycle. A distinct fix from disputing a genuinely wrong item, covered generally in disputed credit items during an application -- this wasn't a dispute at all, just an update.

Statements confirming both cards' balances were paid to zero before the bureau pull
Confirmation from each issuer of its own statement-closing date
Rapid rescore request submitted through the bureau, with proof of payment for both accounts
Updated credit report confirming the corrected score before the closing deadline
Lender's written confirmation that the rescored file cleared the 600 floor
№ 05

The outcome

The score moved from 592 to 615 in three business days, clearing the 600 floor with time to spare before closing. The purchase funded insured with GDS at 35.8% and TDS at 39.2%.

A rapid rescore corrects data that's already true faster than the normal reporting cycle would -- it does not change anything about the applicant's actual credit behaviour, which was never in question here.

№ 06

What to take from this file

  • 01A low score isn't always a credit problem -- sometimes it's a timing problem. Paid-down balances don't update the bureau until each issuer's own statement-closing date.
  • 02Calculate the actual timeline before assuming a wait will work. A natural reporting cycle that lands after closing is no fix at all.
  • 03A rapid rescore is a different tool from a bureau dispute. It updates data that's already true faster, rather than contesting data that's wrong.
  • 04Confirm both the payment and the reporting date before concluding a low score reflects current reality.

Sources

Every regulatory figure in this file traces to one of these primary sources. Client details and anything that varies by lender are illustrative, as flagged below.

Illustrative in this file — lender-specific, not rules:

  • 4.90% contract rate — rates move daily; not a quote.
  • the rapid rescore's turnaround and the natural reporting cycle's length — both vary by issuer and by which bureau is pulled -- illustrative of how the mechanism works, not a published universal timeline.

Authority & provenance

How this case file was built

We publish the origin, the verification method and the reviewer for every case file, so you can judge how far to trust it before you rely on it with a client.

Where it comes from

Derived from files handled by Treadstone’s fulfillment desk and from scenarios contributed by partner brokerages. Names, employers, exact amounts and dates are changed so no client or file is identifiable.

Provenance: Composite — a pattern seen repeatedly on fulfilled files, not a single transaction.

What is verified

Every regulatory figure traces to a primary source listed above and was checked against it on the date shown. The arithmetic is recomputed by machine on every rebuild.

Anything that varies by lender is labelled illustrative rather than stated as a rule.

Who reviewed it

Reviewed for Canadian regulatory accuracy before publication, and re-checked whenever a cited rule changes.

Reviewed by: Nicholas Parson, Treadstone Associates — reviews every case file before publication.

First published 9 August 2026Rules last verified 9 August 2026Next scheduled review 9 February 2027

This case file is professional reference material for licensed mortgage professionals. It is not advice to a borrower, and it is not a lender commitment. Insurer rules, qualifying rates and provincial taxes change — confirm the current position with the insurer, regulator or lender before you rely on any figure here in a live file.

Treadstone fulfillment

Files like this are daily work for our desk.

Document collection, ratio math under multiple treatments, lender placement notes, and submission-ready packaging — for Canadian mortgage brokers who would rather be in front of clients.