Industry Vocabulary Reference

Mortgage & Loan Processing

Mortgage and loan processing fields cover origination, underwriting, disclosures, appraisal, closing, servicing, and reporting. Use the catalog to describe recorded work, not to validate a loan submission.

Back to industry coverage library

This page shows selected examples and categories. Download the JSON for the complete vocabulary, including every field, permitted value, and policy pattern in this catalog.

How to use this reference

1. Start with the core file if you need the cross-industry governance baseline.
2. Choose an industry file for its workflow fields and permitted values.
3. Match the OTel attributes to the policy paths your rules use, then verify the recorded fields in a test session.

Catalog context

Start with one workflow, such as document extraction or underwriting review. Record the source documents, decision context, and review outcome your integration can supply.

Risk note: Check reporting values against the receiving system's current specification. This catalog is not a substitute for the required submission format or a compliance review.

Vocabulary file

• Download filename: 02_vertical_mortgage_loan_processing.json
• Kind: vertical

OTel namespaces

Referenced standards

These references explain the catalog's context. A listed standard does not establish that a configured application meets its requirements.

• 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

Source references

• 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. Route a Refer with Caution result to an underwriter before issuing a commitment. This illustrative control stops automated approval while the lender checks whether manual underwriting is permitted for the loan. (Fnma Selling Guide: Fannie Mae Selling Guide B3-2, Desktop Underwriter)
• TRID Disclosure Management: TRIDDisclosure Status. Illustrative policy: stop automated closing while the applicable disclosure waiting period remains open. Check receipt dates and correction triggers, not status alone. Send claimed emergency waivers for review. (Trid Reg Z 1026 19f: 12 CFR 1026.19(f), Closing Disclosure receipt generally at least three business days before consummation)
• Loss Mitigation & Default Management: Loss Mitigation Option Type. Hold an automated foreclosure referral when applicable loss-mitigation protections restrict the action. Check application completeness, receipt dates, foreclosure stage, and appeal status. An illustrative lender rule can require compliance review before release. (Reg X 1024 41: Regulation X 12 CFR 1024.41, Loss-mitigation review and foreclosure restrictions depend on application timing, completeness, and the foreclosure stage)
• Regulatory Reporting: Adverse Action Notice Status. Keep notice work open when a required adverse-action notice is missing, overdue, or incomplete. Route it to the responsible reviewer. This illustrative archival control complements the lender's notice deadlines and record-retention rules. (Ecoa Reg B 1002 9: Reg B 12 CFR 1002.9, Notification of action taken, ECOA notice, and statement of specific reasons)

Control ideas

These patterns describe possible controls, not active rules. Confirm applicability, implement the control, and test its effect on the application.

Enforce before the action

Pass the request and your business action to this function. The core SDK checks policy before the action runs and again before its result is released. A deny or review decision means the action never runs.

import { Veriproof } from '@veriproof/sdk-core';
import type { GovernedResult, IndustryFact, JsonValue } from '@veriproof/sdk-core';

const veriproof = Veriproof.fromEnv();

export async function runProtectedAction<TInput extends JsonValue, TValue>(
  request: TInput,
  action: (input: TInput, signal: AbortSignal) => Promise<TValue>,
): Promise<GovernedResult<TValue, TInput>> {
  // Catalog values for this vertical. Replace them with facts from the current workflow.
  const industry: IndustryFact[] = [
    { attribute: "mortgage.application.status", policyInput: "mortgage_application_status", value: "prequalification_inquiry" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "mortgage.loan.processing.evaluate",
    request,
    ({ input, signal }) => action(input, signal),
    { industry },
  );
}

• Replace the sample values with facts from the current workflow. Rules read them under input.snapshot.industry.
• Test both permitted and blocked actions. Confirm that a blocked action never reaches your business function.
• Only completed, completed_with_warning, and transformed results carry a released value.

For review decisions, follow the Human Review guide to configure continuation. Observe remains available when you need to record activity without enforcing a decision.

Set up the Mortgage & Loan Processing example. See the API reference for TypeScript, Python, or .NET.

Selected vocabulary categories

This page uses the vocabulary JSON distributed with the documentation. Check its version when comparing it with an installed SDK.

Download the vocabulary JSON for offline review or automated comparisons.

Use the SDK reference for configuration and supported APIs. Keep vocabulary selection separate from the compliance team's assessment of applicable requirements.