PTD lender conditions document workflow
PTD lender conditions document workflow
The second chase
Initial approval feels like the finish line — until the lender issues PTD conditions.
Updated pay stubs. Letter of explanation for a deposit. Proof of insurance bind. Condominium status certificate. Employment confirmation before closing.
Agents who collected the original file through email often start a second chase with no structure.
Common PTD items
Conditions vary by lender and deal, but agents frequently see:
- Updated pay stub within 30 days of closing
- Letter of explanation (LOE) for large deposits or credit inquiries
- Proof of property insurance binder
- Condominium documentation (status certificate, insurance certificate)
- Employment re-verification
- Signed amendments or updated APS
Add conditions as checklist lines
In Hivi-X, add each PTD condition as an explicit checklist item on the borrower record:
- Condition description (from lender list)
- Due date if applicable
- Upload from borrower via a secure guest link (no account needed) or my-id.ca
- Approve or reject before forwarding to lender
The borrower sees one portal with outstanding items — not a new email thread per condition.
Do not lose the original file context
Keeping PTD items on the same borrower record preserves the connection between initial intake and closing conditions. Export an updated PDF package when the file is complete.
Hivi-X does not pull conditions from lender systems or submit satisfied conditions automatically.
Start a free trial and build a PTD conditions template for your common lender requests.
Answers are general operational information only — not legal, tax, regulatory, clinical, privacy, immigration, or professional advice. Requirements vary by matter, client, and regulator.
Frequently asked questions
- What are PTD conditions?
- Prior-to-funding conditions are documents or actions a lender requires before releasing mortgage funds — updated income, explanations, insurance, or property items.
- Can I reuse the original intake checklist for PTD?
- You can add PTD-specific lines to the existing borrower checklist or attach a dedicated PTD conditions template. The borrower record stays in one place.
- Does Hivi-X communicate with lenders about conditions?
- No. Hivi-X tracks what you need to collect. Lender condition lists come from your LOS or lender portal.
Build complete borrower files without the email chase
Hivi-X helps Ontario mortgage agents collect ID, income proof, down-payment evidence, and lender conditions with reusable checklists, a secure guest link (no account needed) or my-id.ca portal, self-hosted AI summaries, and exportable PDF packages for Finmo, BOSS, or Filogix.
More Mortgage guides
- Email is not document collection for mortgage brokersOntario mortgage agents lose time collecting borrower files through email, text, and shared drives. A checklist-first workflow keeps files complete before lender submission.
- Missing documents cost mortgage agents closingsIncomplete borrower files delay lender submission, trigger PTD condition chases, and erode client trust. Checklist tracking shows gaps before you submit.
- Better borrower document collection for mortgage agentsA repeatable checklist workflow replaces ad-hoc email requests and gives Ontario agents a complete view of every borrower file before lender submission.
- Stop chasing pay stubs in emailIncome verification documents arrive late, blurry, or in the wrong thread. A checklist with approve/reject review catches gaps before lender submission.
- Why a mortgage LOS alone does not fix the document chaseFinmo, BOSS, and Filogix handle origination and lender submission — but pre-LOS intake often still lives in email. Hivi-X fills that gap without replacing your LOS.
- Ontario mortgage application document checklistA practical checklist of common borrower documents for Ontario mortgage applications — ID, income, down-payment proof, and lender conditions.
- Mortgage pre-approval document workflowWhat Ontario agents typically need for pre-approval — ID, income, employment, down-payment proof — and how to package a complete file before lender submission.
- Income verification for Ontario mortgage applicationsWhat lenders scrutinize for salaried and self-employed borrowers — pay stubs, employment letters, T1, NOA — and how agents track income docs before submission.
- Self-employed borrower documents for Ontario mortgagesWhat Ontario lenders scrutinize for BFS borrowers — T1, NOA, business financials, bank statements — and how agents track the longer document list.
- Purchase vs refinance mortgage documentsSide-by-side Ontario checklist for purchase vs refinance/renewal files — APS, down-payment proof, mortgage statements, and updated income.
- Mortgage renewal and refinance intake workflowUpdated income, mortgage statements, and property tax dominate renewal files. A reusable checklist template saves re-building the list every time.
- First-time home buyer mortgage documents in OntarioFTB purchase files need standard ID and income plus APS, down-payment proof, and gifted down-payment documentation when applicable.
- FINTRAC KYC for Ontario mortgage brokersSince October 2024, mortgage brokers are FINTRAC reporting entities. What changed, ID verification, record-keeping, and how checklists support evidence.
- FSRA mortgage broker compliance fileWhat FSRA supervision expects in borrower files — principal broker accountability, fraud prevention, Form 1 support docs — and how agents organize evidence.
- Ontario mortgage broker record retentionFSRA and FINTRAC impose parallel record-keeping obligations. Organized borrower files with timestamps support retrieval during supervision or audit.
- Principal broker borrower file oversightPrincipal brokers need consistent intake across agents. Checklist-driven files with exportable indexes support supervision and fraud-prevention review.
- Form 1 disclosure documentation for mortgage filesForm 1 and related disclosures must be supported by borrower evidence — income, employment, property value, credit. Organized intake strengthens the file.
- Gift letter and down-payment documentation in OntarioGifted down payments require a gift letter, donor ID, and donor proof of funds. Multi-party document collection needs checklist tracking.
- Lender submission package workflowIntake, review, principal broker sign-off, then LOS upload. Hivi-X owns intake through export — not lender connectivity.
- Private and alternative mortgage documentationPrivate and alternative deals often need enhanced source-of-funds docs, investor disclosures, and authentication trails. Standardized intake supports principal review.
- Co-agent workflow for mortgage teamsMicro-brokerages with two or three agents need consistent intake across the team. Co-agent workflows share borrower files and checklist templates.
- Exportable PDF package for LOS uploadWhen the borrower file is complete, export an organized PDF for principal broker review or manual upload to Finmo, BOSS, or Filogix.
- Canadian-hosted document collection for mortgage brokersBorrower PII deserves Canadian hosting, encryption at rest, and self-hosted AI — not scattered email attachments on US cloud drives.
- Secure client portal for mortgage documentsBorrowers upload ID, income, and down-payment proof via secure guest link (no account needed) or the my-id.ca portal.
- Small mortgage brokerage document standardizationSolo agents and 2-person teams benefit from reusable checklist templates and consistent export formats principals can review.
- Agent document collection workflowA practical five-step workflow for Ontario mortgage agents — template, borrower file, collect, review, export — before LOS submission.
- Voice notes for mortgage advice documentationCall recaps against checklist lines help document borrower conversations on the agent-controlled file — self-hosted AI, not third-party providers.
- AI summaries for mortgage borrower filesSelf-hosted AI summarizes voice notes on borrower files — not third-party providers, and not automated upload classification.
- DocuSign vs document collection for mortgage agentsE-signing and document collection solve different problems. Hivi-X collects borrower evidence; DocuSign executes signatures on forms you already have.