Industry Vocabulary Reference

Mortgage & Loan Processing

Comprehensive enumeration library for the Mortgage and Loan Processing vertical. Covers the full lifecycle of residential and commercial mortgage lending where agentic AI is actively deployed as of March 2026: origination, automated underwriting, disclosure compliance, appraisal, closing, secondary market delivery, loan servicing, loss mitigation, default and foreclosure, and regulatory reporting. Designed for use as OTel span attributes in an agentic AI SDK and as policy vocabulary in an OPA Rego GRC portal.

Back to industry coverage library

How to use this reference

1. Start with the core file if you need the cross-industry governance baseline.
2. Then move into the vertical file to see the regulated workflow vocabulary, policy surfaces, and implementation pressure unique to this market.
3. Use the OTel attributes and policy paths here as the common language across SDK instrumentation, governance review, and evidence export.

March 2026 deployment context

As of March 2026, agentic AI in mortgage and loan processing is deployed across: automated document ingestion and data extraction from URLA/1003, AUS interface orchestration (DU/LPA), TRID disclosure generation and tolerance monitoring, HMDA LAR data collection and anomaly detection, appraisal ordering and UAD data validation, closing disclosure generation and three-day waiting period enforcement, eClosing workflow orchestration, secondary market delivery data validation (ULDD), loan boarding automation, servicing payment processing, loss mitigation workflow routing, and default/foreclosure timeline management. CFPB Circular 2022-3 (2022) and ECOA Reg B apply to all automated credit decisions. Regulation C violations constitute 38% of all Federal Reserve compliance violations (2024).

Risk note: HMDA Regulation C violations are the most-cited Federal Reserve compliance finding for three consecutive years (2022-2024). The #1 source of violations is incorrect or missing LAR data field values. Agentic AI systems generating or validating HMDA LAR entries must use the exact enumerated values defined in this library.

Loading Model

• Mirrored file: 02_vertical_mortgage_loan_processing.json
• Kind: vertical

OTel Namespaces

Primary Standards

• MISMO v3.6.2 Reference Model (Candidate Recommendation, October 2025)
• MISMO v3.4 — Uniform Loan Application Dataset (ULAD) / Fannie Mae DU / Freddie Mac LPA
• CFPB Regulation Z / TRID — TILA-RESPA Integrated Disclosure Rule (12 CFR 1026)
• CFPB Regulation C / HMDA — Home Mortgage Disclosure Act (12 CFR 1003)
• CFPB Regulation B / ECOA — Equal Credit Opportunity Act (12 CFR 1002)
• CFPB Regulation X / RESPA — Real Estate Settlement Procedures Act (12 CFR 1024)
• CFPB Regulation X / RESPA Servicing Rule — Loss Mitigation Procedures
• Fannie Mae Selling Guide / Freddie Mac Seller/Servicer Guide
• FHFA Uniform Mortgage Data Program (UMDP) — Uniform Appraisal Dataset (UAD) v3.6
• FHA Single Family Housing Policy Handbook 4000.1
• VA Lenders Handbook (VA Pamphlet 26-7)
• USDA RD Instruction 1980-D
• MERS — Mortgage Electronic Registration System
• CFPB Circular 2022-3 — Adverse action reason codes for complex AI models

Source URLs

• https://www.mismo.org/standards-resources/mismo-product/mismo-version-3.6.2-reference-model
• https://www.consumerfinance.gov/compliance/compliance-resources/mortgage-resources/tila-respa-integrated-disclosures/
• https://www.consumerfinance.gov/compliance/compliance-resources/mortgage-resources/hmda-reporting-requirements/
• https://www.consumerfinance.gov/rules-policy/regulations/1002/
• https://ffiec.cfpb.gov/documentation/publications/loan-level-datasets/lar-data-fields
• https://singlefamily.fanniemae.com/originating-underwriting/mortgage-products/desktop-underwriter-du
• https://sf.freddiemac.com/tools-learning/loan-product-advisor/overview

Subdomains

Implementation examples

• Automated Underwriting System (AUS): AUSRecommendation. OPA rule: require human underwriter HITL decision before any commitment issuance when aus_recommendation contains 'Refer'. Block autonomous final approval for all Refer with Caution outcomes regardless of other conditions. (Fnma Selling Guide: Fannie Mae Selling Guide B3-2 — Desktop Underwriter)
• TRID Disclosure Management: TRIDDisclosure Status. OPA rule: block any loan closing action when trid_disclosure_status is NOT ThreeBusinessDayWaitingPeriod_Satisfied or Consummated. Block consummation within 3 business days of ClosingDisclosure_Revised_APRChange. (Trid Reg Z 1026 19e: 12 CFR 1026.19(e) — Loan Estimate delivery within 3 business days of application)
• Loss Mitigation & Default Management: Loss Mitigation Option Type. OPA rule: block autonomous initiation of Foreclosure_Initiated when a complete LossMitigationApplication is under review (anti-dual-tracking per Reg X 1024.41). Require HITL sign-off with compliance_officer role before any foreclosure referral. (Reg X 1024 41: Regulation X 12 CFR 1024.41 — Loss mitigation procedures: application acknowledgement (5 days), evaluation (30 days from complete application), prohibition on dual tracking)
• Regulatory Reporting: Adverse Action Notice Status. OPA rule: block loan application file archival when adverse_action_notice_status is Required_PendingGeneration, Overdue_30DayDeadlineMissed, Deficient_Missing_Reason_Codes, or Deficient_Missing_FCRA_Notice. (Ecoa Reg B 1002 9: Reg B 12 CFR 1002.9 — Notification of action taken, ECOA notice, and statement of specific reasons)

Illustrative policy patterns

package mortgage.trid

closing_allowed_statuses := {
  "ThreeBusinessDayWaitingPeriod_Satisfied",
  "Consummated"
}

redisclosure_triggers_requiring_new_wait := {
  "ClosingDisclosure_APRBecameInaccurate",
  "ClosingDisclosure_ProductChanged",
  "ClosingDisclosure_PrepaymentPenaltyAdded"
}

deny[msg] {

package mortgage.aus

refer_outcomes := {
  "Refer/Eligible",
  "Refer/Ineligible",
  "Refer with Caution/Eligible",
  "Refer with Caution/Ineligible",
  "Caution",
  "Out of Scope",
  "Error"
}

deny[msg] {
  input.mortgage_aus_recommendation in refer_outcomes

From enum to evidence

The same vocabulary should carry from instrumentation through review. The OTel attribute names here become emitted metadata, those attributes become policy inputs, and those same labels should still be intelligible when a reviewer opens the decision record later.

import { VeriproofClient, VeriproofSdkOptions, SessionMetadata } from '@veriproof/sdk-core';
import { MortgageApplicationStatus, MortgageApplicationStatusMeta, HMDAActionTaken, HMDAActionTakenMeta, HMDALoanPurpose, HMDALoanPurposeMeta } from '@veriproof/sdk-core/verticals/mortgage-loan-processing';

const client = new VeriproofClient(
  VeriproofSdkOptions.createProduction({
    apiKey: process.env.VERIPROOF_API_KEY!,
    applicationId: 'mortgage-loan-processing-production',
  }),
);

const session = client
  .startSession('mortgage-loan-processing.review')
  .withSessionMetadata(SessionMetadata.forTransaction('txn-1001').withEnvironment('production'))
  .addStep('evaluate_workflow', { output: { status: 'completed' } })
  .withMetadata(MortgageApplicationStatusMeta.otelAttribute, MortgageApplicationStatus.prequalification_inquiry)
  .withMetadata(HMDAActionTakenMeta.otelAttribute, HMDAActionTaken.1)
  .withMetadata(HMDALoanPurposeMeta.otelAttribute, HMDALoanPurpose.1)

await session.complete();

• SDK: emit the OTel attribute shown on this page during the decision workflow.
• Policy: reference the matching `opa_policy_path` in governance rules.
• Evidence: surface the same label and value in the portal and exported record so reviewers are not translating between systems.

For a step-by-step getting-started walkthrough specific to this vertical, open the Mortgage & Loan Processing SDK quick start. For the full core API reference, continue with TypeScript, Python, or .NET.

Highlighted Enum Categories

This reference page is rendered from the mirrored JSON file inside the docs app, not from a hand-written website model.

If you need the machine-readable asset for offline review, automation, or internal diffing, use the mirrored JSON download above.

Next: open the corresponding SDK reference under SDK documentation and then compare it with the public-site industry page to see how the same vocabulary is framed commercially.