- Shipped
- October 28, 2026 at 2:45 AM UTC
- Author
- Kamo
- Commit
- 17a7a23
Report Studio had no mortgage reports; the MLOS had one real compliance report (the HMDA LAR page) and a set of work screens that could not filter, export or schedule. This adds a Mortgage Lending folder and eighteen reports, all organization-scoped, all gated on View Mortgage Pipeline, all with drill-through, saved views, scheduling and CSV/Excel/PDF export: - Regulatory: HMDA LAR Review, HMDA Edit Checks, Fair Lending Outcomes (screening by applicant group, four-fifths flag), Mortgage Call Report Worksheet, TRID Disclosure Timing (general vs specific business days, mailbox rule), Adverse Action Timeliness (Reg B 30 days) - Pipeline & Production: Pipeline Aging, Production & Cycle Time, Fallout & Pull-Through - Lock Desk: Rate Lock Expiration, Lock Extensions, Relocks & Breaks - Underwriting & Operations: Conditions Aging & Waivers, Document Requirements, Vendor Order Turnaround - Audit: Loan Status Change Audit, SI Decision & Override Audit, Licensing Compliance, Configuration Change Audit Framework: ReportFolder.MORTGAGE, and ReportRowFilter — a member's filter applied to finished rows, with the same operator meanings as the SQL path, for reports whose columns are calculated (days in status, deadline results). MortgageReportSupport keeps every loan read a scalar projection bounded by the organization (LoanFile -> AppMortgage -> organization), since most mortgage tables carry no organization column and entity loads fire a query per one-to-one child. Each report's help text says what it cannot see: no itemised fees (no tolerance check), no intent-to-proceed record, notices sent outside the system, unfilled LAR