Extract closing disclosures to structured JSON
Closing disclosures detail a mortgage's final terms: interest rate, monthly payment, closing costs, and cash due. The TRID format packs hundreds of data points into five pages. Sensible extracts closing disclosure data into validated JSON for post-closing QC and compliance.
Why closing disclosures require precision extraction
TRID-regulated fields, strict tolerances, dense fee tables, and multi-party allocations demand precision.
Closing disclosures contain federally regulated fields where errors create compliance risk. Sensible maps every TRID field with validation.
Sections A through H list fee lines with borrower, seller, and lender columns. Sensible extracts each line and validates section totals.
TRID requires certain fees stay within tolerance between Loan Estimate and Closing Disclosure. Sensible extracts both for programmatic checks.
Fields we extract
Extract any data you need from closing disclosures into your desired output schema
Loan amount, interest rate, monthly P&I, prepayment penalty, balloon payment, loan product, loan term, loan purpose
Origination charges, points, appraisal fee, title insurance, recording fees, transfer taxes, prepaids, initial escrow, total closing costs
Total closing costs, closing costs paid before closing, deposit, funds from borrower, seller credits, adjustments, cash to close
Pre-TRID settlement statement still used for commercial and reverse mortgages.
Preliminary estimate of closing costs provided before final disclosure.
Five-page TRID-compliant closing disclosure required for most residential mortgages.
Supported closing disclosure formats
Closing disclosure configs are available in Sensible's financial services template library. Custom fields and post-closing QC rules can be added to fit your workflow.
CFPB Closing Disclosure (standard 5-page format), Closing Disclosure alternatives, closing cost worksheets
HUD-1 Settlement Statement, HUD-1A, revised HUD-1 (still used for commercial, HELOC, and reverse mortgages)
Common Questions
Details on closing disclosure extraction and QC.
Yes. Both documents output structured JSON with matching field names. You can compare fees, rates, and terms between the two to check for tolerance violations programmatically.
Sensible extracts each fee line from Sections A through H including origination charges, third-party services, taxes, prepaids, and escrow items with both borrower-paid and seller-paid amounts.
Sensible captures loan amount, interest rate, monthly P&I payment, prepayment penalty, balloon payment indicator, loan product type, loan term, and projected payment schedule.
Yes. Sensible extracts all five pages of the CFPB Closing Disclosure form including loan terms, projected payments, closing costs, cash to close, and loan calculations.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Documents are deleted after 30 days by default. You can configure shorter retention periods or request immediate deletion via API.
Yes. Sensible offers a free tier with 50 documents per month. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDF, PNG, JPG, and TIFF files. PDFs can be native or scanned.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence scoring.
Most documents process in 2 to 10 seconds depending on complexity and page count.