1---2name: compare-borrower-disclosures-against-due-diligence-findings3task_id: banking-finance/compare-borrower-disclosures-against-due-diligence-findings4description: Cross-references borrower disclosure schedules against due diligence findings and produces a severity-organized discrepancy memorandum with issue-specific recommended next steps for each gap.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/compare-borrower-disclosures-against-due-diligence-findings8---910# Skill: Borrower Disclosure vs. Due Diligence Discrepancy Memorandum1112## 1. Subject-matter triage1314- Treat the source set as a comparison exercise across multiple document types: borrower disclosure schedules, diligence report, officer’s certificate, and environmental assessment.15- Before drafting, enumerate the disclosure schedules, diligence findings, and any distinct contracts, assets, permits, liens, or environmental items actually in scope so each discrepancy is tied to a specific source item.16- Separate true discrepancies from:17 - omissions,18 - affirmative misstatements,19 - mischaracterizations,20 - stale certifications,21 - incomplete diligence,22 - and cross-document inconsistencies.23- If only one item is implicated on a topic, say so explicitly; do not imply a broader population that is not in the sources.24- Where the transaction structure appears to interact with consent or transfer restrictions, treat that as a separate issue even if the discrepancy is otherwise about disclosure completeness.25- For environmental matters, distinguish operational issues from regulatory exposure and closing-condition risk.2627## 2. Failure modes the skill is correcting2829- Treating every mismatch as a generic omission instead of classifying whether the borrower affirmatively said something that diligence contradicts.30- Missing encumbrances because only one diligence stream was checked, or failing to reconcile multiple search outputs against the disclosure schedules.31- Overlooking whether financing structure, change of control, assignment, or similar mechanics could trigger consent, termination, acceleration, or other rights in key contracts.32- Identifying a gap without stating why it matters to the transaction, including the legal, operational, or closing consequence.33- Failing to distinguish pre-closing fixes from items that can be documented or cured after closing.34- Forgetting to pair each issue with a concrete follow-up step and a responsible actor.35- Drafting a list of observations instead of a severity-ranked memorandum.36- Using conclusory labels without tying them to the controlling document language or recognized legal framework.3738## 3. Legal frameworks / domain conventions that apply3940- Compare disclosures against the full diligence record, not just one report; reconcile across schedules, certificates, searches, and assessments.41- For liens and encumbrances, verify priority and perfection across available search sources and confirm whether any undisclosed security interest, judgment lien, tax lien, or similar claim affects closing mechanics.42- For material contracts, check whether any consent, termination, anti-assignment, change-of-control, or similar provision is implicated by the contemplated financing structure.43- For debt or creditor rights, assess whether demand, acceleration, or similar features affect repayment priority, liquidity, or closing risk.44- For licenses, permits, certifications, and approvals, evaluate expiration, renewal timing, and whether any condition must be satisfied before closing.45- For environmental findings, identify whether the issue is disclosure-only, remediation-related, permit-related, or a closing-condition problem.46- When a legal proposition is stated, anchor it to the controlling authority or governing document language reflected in the source set; do not state a legal conclusion without naming the rule, clause, statute, regulation, or similar authority that supports it.47- Treat every material discrepancy as requiring a procedural response: corrected disclosure, consent request, covenant, closing condition, indemnity, bringdown certificate, or similar protection.4849## 4. Analytical scaffolds50511. Build a source map first:52 - disclosure schedule by topic,53 - diligence finding by topic,54 - officer’s certificate statement,55 - environmental assessment point,56 - and any cross-referenced document language that interacts with the issue.572. For each discrepancy, identify the error type:58 - omission,59 - affirmative misstatement,60 - mischaracterization,61 - stale certification,62 - or other material inconsistency.633. For each issue, close the analysis with:64 - the scale or magnitude drawn from the source documents,65 - the document or clause that intersects with it,66 - and the transaction consequence for the client.674. For every contract- or relationship-based issue, ask whether the contemplated financing, transfer, or control arrangement could trigger consent, default, termination, or similar rights.685. For every lien, encumbrance, or creditor-rights issue, compare all available diligence sources and assess whether the disclosure is incomplete, inconsistent, or insufficiently prioritized.696. For each environmental issue, identify whether it is a factual discrepancy, an unresolved compliance matter, or a closing-risk item requiring remediation or further diligence.707. Assign each issue an ordinal severity level and use that same scale consistently throughout the memorandum.718. End each issue with a concrete next step that matches the risk level and the transaction stage.7273## 5. Vertical / structural / temporal relationships7475- Organize the memorandum from highest severity to lowest severity.76- Define the severity scale once at the outset and use only those labels throughout.77- Split issues into pre-closing matters and items that may be addressed post-closing, but keep both under the same severity framework.78- If an issue depends on timing, state the relevant deadline, closing milestone, expiration date, or bringdown point from the source documents.79- Where one disclosure item affects multiple diligence findings, make the hierarchy explicit so the reader can see the primary issue and any dependent issue beneath it.80- Where multiple findings point to the same disclosure gap, consolidate them into one entry only if the downstream consequence is the same; otherwise separate them by consequence.8182## 6. Output structure conventions8384- Produce a formal discrepancy memorandum in conventional memo form, not a raw issue log.85- Use a short heading that identifies the transaction and the purpose of the memorandum.86- Begin with a legend defining the severity scale.87- Include an executive summary that distinguishes critical pre-closing issues from lower-severity matters.88- Present the body in severity order, with each entry containing:89 - the disclosure source section or schedule item,90 - the corroborating diligence source,91 - the error type,92 - the severity label,93 - the consequence,94 - and the recommended next step.95- Include a compact comparison table that maps discrepancy to severity and action, then follow with narrative analysis for each item.96- For each issue, make the recommended action imperative, assign it to a responsible role if identifiable from the source set, and tie it to a transaction milestone or deadline.97- If a source item is not implicated, do not manufacture an issue; state that no discrepancy was identified for that topic when useful.98- Conclude with a brief Recommended Actions section that prioritizes immediate follow-up, cure steps, and any items requiring closing conditions or post-closing monitoring.99- Name the output file as `discrepancy-memorandum.docx`.