Treadstone Associates
Case File № 357 · Bruised Credit & Consolidation

Coded as a credit card, paid like a car loan

a Corner Brook bureau error

A fixed installment loan was reported to the bureau with a revolving-style credit-limit field and no scheduled-payment field, so the lender's automated system defaulted to a generic revolving-balance formula. The loan's own amortization schedule proved the real payment was nearly half the miscoded figure.

Newfoundland and LabradorInsured · PurchaseFiled August 9, 20265 min read
$700/mo

the miscoded revolving-formula payment the bureau error implied

$372/mo

the loan's real fixed installment payment, per its own amortization schedule

39.7%

corrected TDS — inside CMHC's 44% maximum

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

An applicant in Corner Brook, Newfoundland and Labrador, carries an $18,000 fixed installment debt-consolidation loan through a credit union — its own amortization schedule, its own fixed payment, running exactly as agreed since it was taken out.

Purchase price

$260,000

Corner Brook

Installment loan

$18,000

Fixed payment, 5-year term, 8.99%

Combined income

$6,300/month

Both salaried

Reported balance

$14,000

Coded with a revolving-style credit-limit field

№ 02

The problem

The credit union's own reporting to the bureau listed the loan with a revolving-style credit-limit field and a current balance, but left the scheduled fixed-payment field blank -- a furnisher data error, not a mistaken-identity dispute and not someone else's debt attached to this file. With no fixed-payment field populated, the lender's automated underwriting system fell back to its own generic formula for an account type it couldn't classify: 5% of the reported balance.

What the miscoding actually did

  • The loan's real payment, per its own amortization schedule, is $372/mo -- fixed, and already known
  • The bureau's revolving-style coding produced a system-generated $700/mo figure instead
  • Nothing about the loan itself changed. Only what the file's automated system assumed about it did

A bureau file read carefully, against the loan's own documents, showed the discrepancy immediately -- the fix was documentary, not a dispute over who owed what.

№ 03

The numbers

The two figures -- the system's assumption and the loan's real payment -- produce two different total debt service numbers on the same file.

The insured purchaseAmount
Purchase price$260,000
Minimum down payment (5% tier)$13,000
Base mortgage$247,000
CMHC premium — 4.00% in the 90.01-95% LTV band+$9,880
Total insured mortgage$256,880
Total debt serviceOn the miscoded figureOn the loan's real payment
Qualifying mortgage payment$1,768$1,768
Property tax and heat$360$360
Installment loan payment$700 (system fallback formula)$372 (actual fixed payment)
Total debt service44.9%39.7%

44.9% would have failed CMHC's 44% maximum outright, on a payment the loan was never actually charging. 39.7%, on the loan's real fixed payment, clears comfortably -- the file's true numbers were fine all along.

№ 04

The solution

A mortgage professional serving Newfoundland and Labrador went to the source document rather than accepting the bureau's own coding.

First, obtained the original loan agreement and amortization schedule from the credit union. Documentary proof of the real $372/mo fixed payment, direct from the lender that issued the loan.

Second, submitted it to the underwriter as the governing figure. A signed loan agreement with its own payment schedule outweighs a system-generated fallback formula for an account type the bureau miscoded.

Third, separately asked the furnisher to correct the account-type coding. Requested the credit union update its bureau reporting to reflect the loan as a fixed installment product, so the same fallback wouldn't recur on a future file.

Original loan agreement and amortization schedule from the credit union
Current bureau report showing the miscoded revolving-style fields
Written request to the furnisher to correct the account-type coding
Two years of income documentation for both borrowers
Lender's underwriting notes confirming the real $372/mo payment was used
№ 05

The outcome

The purchase funded insured at 4.80%, GDS at 33.8% and TDS at 39.7%, both inside CMHC's maximums, on the loan's real payment rather than a formula built for a different kind of account -- a reminder that Canada's own household debt service data reflects real payments, not system fallback formulas.

№ 06

What to take from this file

  • 01A bureau account-type miscoding is a documentation problem, not a dispute over who owes what. The fix is the loan's own paperwork, not a bureau complaint about identity.
  • 02An automated underwriting system's fallback formula for an unrecognized account type can overstate a real payment by nearly double.
  • 03A signed loan agreement with its own amortization schedule outweighs a system-generated assumption every time it's actually looked at.
  • 04Ask the furnisher to fix the coding itself, not just to explain it for one file. Otherwise the same error recurs on the next lender who pulls the bureau.
  • 05Read the bureau file against the loan's own documents before assuming a high reported payment is real. Sometimes the debt is fine and the coding is wrong.

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.80% / 8.99% rates — rates move daily; neither is a quote.
  • the 5%-of-balance fallback formula — each lender builds its own automated fallback for an account type its system cannot classify; not a published industry standard.

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.