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. Use Sensible to get structured closing disclosure data for post-closing QC and compliance.

Quick links:

Closing disclosures blog post

Financial services template library

API documentation

Schedule a demo

Why closing disclosures require precision extraction

TRID-regulated fields, strict tolerances, dense fee tables, and multi-party allocations demand precision.

TRID Compliance Fields

TRID-regulated fields carry tolerance requirements. An error in the wrong fee category creates compliance liability. Sensible anchors extraction to the official form structure so regulated fields map correctly every time.

Fee Table Extraction

Sections A through H. Borrower-paid, seller-paid, lender columns. Each fee line is extracted with its correct party attribution, eliminating manual reconciliation of the closing cost tables.

Buyer vs. Seller Disambiguation

The same document contains separate sections for buyer and seller charges. Fields like "Total Closing Costs" appear twice with different values. Sensible preserves which side each fee belongs to, so your QC process can validate buyer and seller figures independently.

Fields we extract

TRID-regulated fields are mapped precisely. Configure additional fields for your post-closing QC workflow.

Loan terms

Loan amount, interest rate, monthly P&I, prepayment penalty, balloon payment, loan product, loan term, loan purpose

Closing costs

Origination charges, points, appraisal fee, title insurance, recording fees, transfer taxes, prepaids, initial escrow, total closing costs

Cash to close

Total closing costs, closing costs paid before closing, deposit, funds from borrower, seller credits, adjustments, cash to close


{ /* SenseML: closing disclosure extraction */
  "fields": [
    {
      "method": {
        "id": "queryGroup",
        "queries": [
          {
            // Loan amount
            "id": "loan_amount",
            "description": "loan amount, amount financed",
            "type": { "id": "currency" }
          },
          {
            // Interest rate
            "id": "interest_rate",
            "description": "interest rate, your interest rate, note rate",
            "type": {
              "id": "custom",
              "pattern": "[0-9]{1,2}\\.?[0-9]{0,3}%"
            }
          },
          {
            // Monthly principal and interest
            "id": "monthly_pi",
            "description": "monthly principal and interest, P&I payment, monthly payment",
            "type": { "id": "currency" }
          },
          {
            // Total closing costs
            "id": "total_closing_costs",
            "description": "total closing costs, closing costs, total costs",
            "type": { "id": "currency" }
          }
          // Additional fields for cash to close, property address, lender, etc.
        ]
      }
    }
  ]
}
HUD-1 Settlement Statement

Pre-TRID settlement statement still used for commercial and reverse mortgages.

Closing Cost Worksheet

Preliminary estimate of closing costs provided before final disclosure.

TRID Closing Disclosure

Five-page TRID-compliant closing disclosure required for most residential mortgages.

Supported closing disclosure formats

Pre-built configurations cover TRID-era closing disclosures and HUD-1 settlement statements. Sensible's financial services template library handles both, with hybrid extraction for lender-specific layout variations.

TRID-era documents

CFPB Closing Disclosure (standard 5-page format), Closing Disclosure alternatives, closing cost worksheets

Pre-TRID documents

HUD-1 Settlement Statement, HUD-1A, revised HUD-1 (still used for commercial, HELOC, and reverse mortgages)

Trusted by operations and engineering teams at

Common Questions

Answers about TRID compliance fields, fee table extraction, and tolerance checks.

Can Sensible compare Loan Estimates to Closing Disclosures?

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.

How does Sensible handle the fee tables on closing disclosures?

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.

What loan terms does Sensible extract?

Sensible captures loan amount, interest rate, monthly P&I payment, prepayment penalty, balloon payment indicator, loan product type, loan term, and projected payment schedule.

Does Sensible extract TRID compliance fields from closing disclosures?

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.

Do you support webhooks?

Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.

Does Sensible support human review?

Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.

What security certifications does Sensible have?

Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.

How long is document data retained?

Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.

Is there a free trial?

Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.

How is pricing structured?

Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.

How do I integrate with Sensible?

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.

What file formats does Sensible support?

Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.

How accurate is the extraction?

Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.

How fast is document processing?

Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.

Resources

Documentation Links

Docs: Insurance template quick startDocs: Validation and human reviewDocs: API and delivery options

Related insurance documents

Docs: Insurance template quick startDocs: Validation and human reviewDocs: API and delivery options