There’s a $20,000 deposit in your bank statement. The underwriter will ask. If you can’t explain it with a paper trail, the closing is delayed 30-60 days.
Large deposits are a red flag for mortgage underwriters. This page covers what counts as a large deposit, the 5 common explanations, the paper trail needed for each, and the recon cutoff tool’s per-mortgage-deposit handling.
The mortgage large-deposit threshold is typically $1,000-$2,000 (varies by lender). Some lenders flag any deposit over $500. Common explanations: gift, tax refund, asset sale, insurance payout, inheritance, bonus, equity from home sale. Each needs a paper trail.
The recon cutoff tool’s per-mortgage-deposit handling flags large deposits in advance, so the borrower can prepare explanations. The recon cutoff tool’s per-60-day-seasoning tracking handles the timing requirement. The recon cutoff tool’s per-paper-trail-generation creates the documentation checklist for each deposit type.
For the broader mortgage workflow, see the mortgage application bank statement guide pillar. For the gift funds path, see the gift funds guide. For the asset verification, see the asset verification guide.
What Counts as a Large Deposit
The threshold for a “large deposit” varies by lender. The 3 most common thresholds.
What most guides miss about mortgage applications is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).
Choosing between tools based on UI alone misses the actual quality lever.
The 3 Thresholds
Some lenders flag deposits over $500 (strictest), $1,000 (most common), or $2,000 (loosest). The recon cutoff tool’s per-threshold handling shows the threshold by lender type and flags deposits automatically.
The 6 Common Explanations
6 common explanations cover 95% of large deposits. Each needs a specific paper trail.
Explanation 1: Gift From Family
Gift from family is the most common. The paper trail: a signed gift letter, the giver’s bank statement showing the transfer, the giver’s ID. The recon cutoff tool’s per-gift-explanation handling generates the gift letter template.
Explanation 2: Tax Refund
Tax refund is the second most common. The paper trail: a copy of the tax return showing the refund, the IRS confirmation. The recon cutoff tool’s per-tax-refund-explanation handling includes the tax return.
Explanation 3: Asset Sale
Asset sale (car, jewelry, equipment) is the third. The paper trail: a bill of sale, the buyer’s name, the deposit confirmation. The recon cutoff tool’s per-asset-sale-explanation handling generates the bill of sale template.
Explanation 4: Insurance Payout
Insurance payout (auto, home, life) is the fourth. The paper trail: a copy of the claim, the payout amount, the insurance company’s check image. The recon cutoff tool’s per-insurance-explanation handling stores the claim.
Explanation 5: Inheritance
Inheritance is the fifth. The paper trail: a copy of the will or trust, the executor’s letter, the deposit confirmation. The recon cutoff tool’s per-inheritance-explanation handling stores the will.
Explanation 6: Retirement Loan or Distribution
Retirement loan or distribution (from 401k or IRA) is the sixth. The paper trail: the loan approval letter, the distribution confirmation, the deposit confirmation. The recon cutoff tool’s per-retirement-explanation handling includes the documentation.
From Bank Statement to QuickBooks-Ready File
That manual cleanup you just read about? This tool skips it. Turn your PDF into QBO for QuickBooks without storing your data anywhere.
Start ConvertingThe 3 Common Large-Deposit Mistakes
3 mistakes mortgage applicants make on large deposits.
Mistake 1: Ignoring the deposit. Hoping the underwriter won’t notice is a mistake. The underwriter always notices. The fix: prepare the explanation in advance. The recon cutoff tool’s per-deposit-flag identifies the deposit and generates the template.
Mistake 2: Vague explanation. “It was a gift” is not enough. The fix: provide the gift letter, the giver’s bank statement, and the giver’s ID. The recon cutoff tool’s per-paper-trail-handling generates the complete paper trail.
Mistake 3: Inconsistent amounts. The deposit in the bank statement doesn’t match the explanation. The fix: verify the amount before submitting. The recon cutoff tool’s per-verify-handling checks the amount against the explanation.
A common failure mode bookkeepers report is treating this as a single operation rather than a chain of dependent steps. The temptation is to find a tool that ‘just works’ and stop investigating the mechanism.
The result is a wrong-fix cycle: the tool gives partial output, the bookkeeper spends 30+ minutes troubleshooting, the fix is for the wrong step, and the same error recurs on the next statement. The fix: identify which step failed and apply the right intervention to that step.
The Per-Deposit Workflow
The per-deposit workflow runs in 5 steps. The 5 steps take 15-30 minutes per deposit.
Step 1: Identify the Deposit
The recon cutoff tool’s per-deposit-flag-handling identifies deposits over the threshold. The flag shows the date, amount, and payee. The recon cutoff tool’s per-deposit-list emits the list of large deposits.
Step 2: Determine the Explanation
The borrower determines the explanation: gift, tax refund, asset sale, insurance, inheritance, retirement. The recon cutoff tool’s per-explanation-categories-handling lists the 6 common categories.
Step 3: Gather the Paper Trail
The borrower gathers the paper trail: gift letter + donor’s statement, tax return + IRS confirmation, bill of sale, insurance claim, or will. The recon cutoff tool’s per-paper-trail-handling lists the docs needed for each category.
Step 4: Generate the Explanation Letter
The recon cutoff tool’s per-explanation-letter-handling generates the letter from the template. The letter is signed by the borrower and the donor (if applicable). The recon cutoff tool’s per-letter-archive stores the letter.
Step 5: Attach to the Application
The explanation letter and the paper trail go to the application. The recon cutoff tool’s per-application-export-handling emits the complete set: bank statement + letter + paper trail. The recon cutoff tool’s per-archive stores the set.
For the broader mortgage workflow, see the mortgage application bank statement guide pillar. For the asset verification, see the asset verification guide . For the gift funds, see the gift funds guide . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
Related: complete mortgage application bank statement guide
This topic is one node in the broader mortgage-application bank-statement cluster on this site. he consolidated hub, with the full decision framework covering FHA, VA, conventional Fannie Mae and Freddie Mac, DSCR, and conventional loans, lives in the complete mortgage application bank statement guide.
For related reading on the broader statement-reading clusters, see the complete MCC guide and the complete US bank payment rails guide. he expanded bank statement anatomy pairs naturally with this hub as a primer.
More on the broader cluster
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes.
Decision framework for this topic
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Related reading and broader clusters
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Turn That PDF Into a Spreadsheet in Minutes
You've seen how to do it manually — now let the tool handle the heavy lifting. Upload your bank statement and get Excel, CSV, or QBO in a few clicks.
Try It Free
