Loan-to-value, down payment, and credit profile are three inputs a provider weighs together when reviewing a DSCR scenario. This site publishes no pricing tiers, because those tiers are provider decisions that change. What can be taught here is the mechanics: what each input measures, why it matters to a risk review in general, and the exact questions that turn a modeled scenario into verified facts.
What LTV measures, and which value it uses
LTV is the loan amount divided by the property's value, expressed as a percentage, simple enough until you ask which value sits in the denominator. On a purchase, the question is whether the provider uses the purchase price, the appraised value, or the lower of the two. On a refinance, the question is whether the property's ownership history affects which value counts. Two scenarios with identical loan amounts can carry different LTVs because the definition of value, not the loan, is what moved.
Down payment and LTV: two views of one number
On a purchase, down payment and LTV are complements by definition: financing 75 percent of value means putting 25 percent down. Thinking in both directions catches errors. A down payment figure that ignores seller credits or closing costs can imply an LTV the provider won't recognize. Down payment also isn't the whole cash requirement: closing costs and post-closing reserves, the liquid funds you must still hold after closing, are separate line items the provider counts independently.
Why credit profile can move pricing at all
The general concept is risk-based pricing: a lender prices for the repayment risk it expects to carry, and a credit score is one compressed summary of repayment history. That's why providers may tier rate or maximum leverage by credit profile as a matter of design. Which score model they use, which bureau they pull, and whose score governs when an entity has several members are all provider-specific questions, not published constants.
Leverage feeds straight into the coverage ratio
This is where the three inputs meet the DSCR itself. Leverage works like a volume dial: turning it up raises the monthly payment, and because the payment sits in the denominator of the coverage ratio, a higher payment pulls the ratio down. Take this illustrative example only: a $300,000 purchase with rent modeled at $2,600 and an illustrative 30-year rate of 7.5 percent, not a quote from anyone. A $225,000 loan carries a principal-and-interest payment near $1,573. Add $500 of illustrative taxes, insurance, and dues, and the payment is about $2,073; divide $2,600 by $2,073 and coverage lands near 1.25x. Borrow $240,000 instead and the payment climbs to about $2,178, so the same $2,600 of rent now covers it at roughly 1.19x.
| Illustrative loan amount | Modeled PITIA | Modeled coverage |
|---|---|---|
| $225,000 | ≈ $2,073 | ≈ 1.25x |
| $240,000 | ≈ $2,178 | ≈ 1.19x |
More leverage means a higher payment and a lower ratio, mechanically and always. Where any provider draws its leverage and coverage lines is that provider's decision alone. Rebuild this comparison with your own inputs in the DSCR Calculator.
Questions to verify before relying on any scenario
- What maximum LTV applies to this specific scenario, given the property type, occupancy use, and loan purpose?
- Which value does the provider use on a purchase: contract price, appraised value, or the lower of the two?
- Which credit score model and bureau pull does the provider use, and whose score counts when an entity has multiple members or guarantors?
- Does credit profile change maximum leverage, pricing, or both under this provider's current guidelines?
- What total cash does the provider expect to verify beyond the down payment, including closing costs and reserves?
Leverage is a dial, not an entitlement; the provider decides where it stops.
On an actual scenario, that means computing an LTV and its matching down payment from either direction, explaining why borrowing more lowers the coverage ratio, stating in one sentence why credit profile can move pricing at all, and asking a provider the five questions that pin down which definitions actually govern the file.