Application inputs & LTV
The per-loan data a statement can't provide, and the derived loan-to-value.
Application inputs & LTV
Some loans need data that isn't in a bank statement — the amount sought, the value
of the collateral, the business's turnover. LoanPilot captures these at upload and
exposes them to the rules engine as application.* variables.
The inputs
| Input | Used for |
|---|---|
| Requested amount | LTV, and amount-tiered rule values |
| Collateral value (gold / property) | LTV = requested ÷ collateral |
| Annual GST turnover | MSME / working-capital sizing |
| Down payment | Vehicle / consumer-durable loans |
The list comes from the engine catalogue, so adding an input is a one-line, data-only change on the server — it then appears in the upload form automatically.
Loan-to-value (LTV)
application.ltv_pct is derived as requested amount ÷ collateral value, as a
percent. The Gold and LAP templates ship an LTV cap that uses it:
- Gold: LTV above 75% → manual review
- LAP: LTV above 70% → manual review
Dormant until entered
An LTV rule only fires when both the requested amount and the collateral value
were entered. With either missing, application.ltv_pct is unknown and the rule
does nothing — it never blocks a file for lack of input.
The captured inputs and the derived LTV are shown on the Decision tab's Loan details card.