Retail, broker or correspondent channels
Each channel has its own intake, conditions and status flow, so a broker or correspondent channel adds portal and partner work.
- Ask first: which channels go live in the first release?
Financial Services / Mortgage Lending
Mortgage lending software that proves every TRID and HMDA checkpoint
A mortgage loan file is judged on dates: when the application was complete, when each disclosure went out and when the borrower received it. Agnotic Technologies builds mortgage lending software for lenders, credit unions and brokers that records each of those events as it happens, so the file proves its own compliance at closing and at audit.
URLA
Application captured as data
TRID clocks
Started by system events
HMDA
Collected as the file moves
Trusted by global innovators
Industry Overview
What is mortgage lending software?
Mortgage lending software is the loan origination system a mortgage lender uses to take a residential application, issue the Loan Estimate and Closing Disclosure on time, order appraisal, title and flood, clear conditions and close. Agnotic Technologies builds it around the loan file, recording each TRID and HMDA checkpoint as a dated system event.
Sizing
What sizes a mortgage automation project?
A mortgage automation project is sized by the channels you lend through, the loan products, whether the current LOS is extended or replaced, the verification and document vendors, investor delivery data, which HMDA and TRID checkpoints are already handled, and the loan history to migrate. Agnotic Technologies works through each driver with your operations and compliance leads.
Loan products
Conventional, government and jumbo products each bring their own conditions, disclosures and investor rules to configure and test.
- Ask first: which products carry most of your volume?
Extend or replace the current LOS
Extending adds an event and deadline service beside your LOS; replacing adds data migration and a parallel run.
- Ask first: does your LOS expose events through an API or a MISMO export?
Verification and document vendors
Every income, employment, asset, credit, appraisal, title and flood vendor adds an order, a result mapping and a condition link.
- Ask first: which vendors stay, and which are being replaced?
Investor delivery data
Selling loans adds the delivery data set, data checks against each investor's rules and the hand-off file.
- Ask first: who buys your loans, and in which delivery format?
HMDA and TRID checkpoints already handled
Checkpoints your LOS already proves with dated events are reused; the rest are built as new events and alerts.
- Ask first: which checkpoints did your last audit or exam flag?
Loan history to migrate
Open pipeline loans and closed files you must keep for audit need mapping, document moves and a reconciliation.
- Ask first: how many open loans and years of closed files move?
Industry Challenges
Where do mortgage loan files fail an audit?
Most findings are not about the rate or the fees. They are about a date nobody can prove.
The six items that make an application arrive over two days, and the system keeps only the later date, so a late Loan Estimate looks on time.
A changed circumstance is typed into a comment, so the revised Loan Estimate has no documented reason and the fee increase cannot be defended.
The Closing Disclosure is emailed, but the file holds no evidence of when the borrower received it, so the waiting period is in doubt.
HMDA fields are filled in after closing from memory, so the demographic data does not match how it was actually collected.
Appraisal, title and flood orders are tracked in email, and a condition is cleared without the document that should have cleared it.
Withdrawn and denied applications are purged from the system and then missing from the loan application register.
Automation and sign-off
What can be automated in mortgage processing?
Mortgage processing automation can classify documents, place verification orders, import automated underwriting findings, match conditions to evidence and check disclosure timing. Agnotic Technologies builds that mortgage automation into the loan file, while underwriters and closers keep the sign-offs that need human judgment.
| Task | What the software does | What a person still signs off |
|---|---|---|
| Borrower document classification | Sorts uploads into document types, reads key fields and flags missing pages or out-of-date statements | A processor confirms low-confidence classifications; the underwriter reviews the documents a decision relies on |
| Income and employment verification | Places verification orders once the application is complete and attaches each result to the borrower and the condition it serves | The underwriter decides whether the verified income supports the loan |
| Automated underwriting findings | Submits the file to Fannie Mae Desktop Underwriter or Freddie Mac Loan Product Advisor and imports the recommendation, messages and conditions as tracked items | The underwriter confirms the submitted data is accurate and that every message and condition is met |
| Condition clearing | Proposes a match between each condition and the document that should clear it, with the reason for the match | An underwriter or processor clears the condition; the software never clears its own match |
| Disclosure timing checks | Computes Loan Estimate and Closing Disclosure due dates from recorded events and blocks a closing date that breaks the waiting period | The closer confirms the receipt evidence and approves the closing package |
Our Approach
How should a mortgage lender approach its origination system?
Three design choices decide whether the loan file can prove compliance on its own.
Model events, not statuses
A status such as 'disclosed' says little. We record the event, its timestamp, its source and the user, so any deadline can be recalculated later from facts.
Use the industry data standards
Application data follows the URLA (Form 1003) fields and moves between systems in the MISMO format, so pricing, credit, appraisal and settlement partners read the same data.
Stop at the servicing hand-off
Origination ends when the loan is boarded to servicing, with a clean data export. Payment, statement and delinquency rules live in the servicing system.
Capabilities
What do we build into mortgage lending software?
How to build mortgage lending software around the loan file, from the first application field to the closing package.
Digital URLA application
Borrower and loan officer flows that capture URLA fields as data, including co-borrowers, employment, assets and declarations.
Disclosure engine
Loan Estimate and Closing Disclosure generated from loan data, with due dates computed from the application and closing events.
Changed circumstance log
Each change recorded with its reason, the date the lender learned of it and the revised disclosure it produced.
Third-party orders
Appraisal, title, flood, credit and verification orders sent and tracked, with each result attached to the condition it clears.
Condition evidence
Every condition linked to the document that cleared it and the user who cleared it, so the file shows why, not only when.
HMDA data capture
Demographic questions in the application flow, action taken and loan fields edited as the file moves, with a register export.
Rate lock tracking
Lock date, expiry and extensions recorded against the disclosure version each one changed.
Closing package and servicing export
Closing documents assembled for the settlement agent, then final terms and escrow setup exported to your servicer.
Engineering Stack
Standards and systems behind mortgage lending software
Chosen to fit your channels, your partners and your current LOS.
Data standards
URLA (Form 1003) fieldsMISMO Residential Reference ModelHMDA loan application register format
Partners
Pricing and eligibility engineCredit report providersAppraisal managementTitle, flood and settlement agents
Documents
Disclosure and closing document generationElectronic signatureDocument classification
Platform
Event store for loan file historyRole-based accessEncryption in transit and at restAudit logs
TRID clocks
Which event starts each mortgage disclosure clock?
A disclosure deadline is only as accurate as the event that starts it. This is how we map each clock to a system event.
| Clock | Event that starts it | Deadline | Evidence the file keeps |
|---|---|---|---|
| Loan Estimate | Application complete: the sixth item received | Delivered or mailed by the third business day | Application-complete timestamp and delivery record |
| Loan Estimate before closing | Scheduled consummation date | Delivered or mailed by the seventh business day before consummation | Closing date history and Loan Estimate delivery date |
| Revised Loan Estimate | The lender learns of a valid changed circumstance | Within three business days | Changed circumstance log with reason and date learned |
| Closing Disclosure | Scheduled consummation date | Received by the borrower three business days before consummation | Delivery method, receipt date and any receipt confirmation |
| HMDA loan application register | End of the calendar year | Submitted by March 1 of the following year | Edited register fields, action taken and action dates |
Measured Impact
What should a mortgage operation measure?
Measures we build into loan file dashboards with your compliance and operations leads.
Disclosure timing
Loan Estimates on time
Files where delivery met the deadline computed from the application event.
Changed circumstances
Revised disclosures
Revisions by reason, and any without a documented reason.
Condition cycle
Open to cleared
How long conditions wait and which third-party orders hold them.
HMDA edits
Data quality
Fields failing edits during the year, not only before the filing.
Use Cases
Where do mortgage lenders start?
First releases we scope with mortgage teams.
01
Digital application front end
A borrower URLA flow that feeds your existing origination system through MISMO data.
02
Disclosure timing service
Event capture and deadline alerts added beside your current LOS.
03
HMDA data quality
Edits and a register workbench that run all year, not only in February.
04
Broker and wholesale portal
Submission, conditions and status for mortgage brokers.
05
New mortgage lenders
A lean origination system for one product and one channel, with the compliance events in place from the first loan.
06
Credit union mortgage desk
Member mortgage applications alongside the credit union's consumer lending tools.
Integrations
Which systems does mortgage lending software connect to?
The partners and systems a mortgage loan file exchanges data with.
Rates and products
Pricing and eligibility engine
Credit
Credit reporting agencies
Valuation
Appraisal management company
Closing
Title and settlement agents
Property
Flood determination
Disclosures
Document and e-signature
Boarding
Loan servicing system
Credit union and bank lenders
Core banking
What we check
Which TRID and HMDA checkpoints must a mortgage loan file pass?
Each checkpoint should be proved by a dated event in the system, not by a person's note. Each item names the event we record.
Application
- Each of the six application items is time-stamped when it arrives, and the file records when the application became complete.
- URLA data is stored as structured fields, not only as a signed PDF.
- The borrower's intent to proceed is recorded with its date and method before any fee other than a credit report fee is charged.
Loan Estimate
- The Loan Estimate due date is calculated from the application-complete event in business days.
- Delivery method and the date the borrower is considered to have received the Loan Estimate are recorded.
- Each changed circumstance is logged with its reason and the date the lender learned of it, and the revised Loan Estimate is tied to it.
Processing
- Appraisal, title, flood and verification orders carry an order date, a received date and the condition each one clears.
- Appraisal delivery to the applicant is recorded with its date, as your valuation policy requires.
- Rate lock date, expiry and extensions are linked to the disclosure version they changed.
Closing Disclosure and closing
- The Closing Disclosure is generated from final loan data and the borrower's receipt date is recorded.
- Scheduling consummation fewer than three business days after the borrower received the Closing Disclosure is blocked.
- Changes that need a new waiting period, such as a loan product change or an added prepayment penalty, trigger a corrected Closing Disclosure and restart the clock.
HMDA data
- Ethnicity, race and sex are stored with how each was collected, including visual observation or surname where that applies.
- Action taken and action date are recorded for every application, including withdrawn, denied and incomplete files.
- HMDA fields are edited as the file moves, so the register is ready well before the March 1 filing.
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
Service Organization Control 2
Verified controls for security, availability, and confidentiality of enterprise data systems.
Information Security Management
Adhering to the international gold standard for managing information security risks.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we cut setup work so your first release reaches users sooner.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does a mortgage software engagement work?
We start with one channel or one product. Timing depends on scope; we agree a fixed first release on the scoping call.
01
Scoping call
We map your channels, products, current LOS and the checkpoints your last audit or exam flagged.
02
Event model workshop
Your compliance and operations leads confirm which events start each clock and what evidence proves each checkpoint.
03
Fixed-scope first release
Application capture, the Loan Estimate clock and the HMDA fields for one product, running beside your current process.
04
Rollout
The Closing Disclosure workflow, third-party orders, condition evidence and the servicing export.
05
Support
Rule and form updates, partner interface changes and year-end HMDA preparation.
Facts and sources
Mortgage rules the loan file is built around
Regulation Z (TRID) and Regulation C (HMDA) facts, each linked to its primary source.
For TRID disclosures, a mortgage application consists of six pieces of information: the consumer's name, income, social security number to obtain a credit report, the property address, an estimate of the property value and the loan amount sought.
Source: 12 CFR 1026.2(a)(3)(ii) (eCFR)The creditor must deliver or mail the Loan Estimate no later than the third business day after it receives the consumer's application, and no later than the seventh business day before consummation.
Source: 12 CFR 1026.19(e)(1)(iii) (eCFR)When a creditor uses a revised estimate after a changed circumstance, it must provide the revised disclosure within three business days of receiving information sufficient to establish the reason for the revision.
Source: 12 CFR 1026.19(e)(4)(i) (eCFR)The creditor must ensure that the consumer receives the Closing Disclosure no later than three business days before consummation.
Source: 12 CFR 1026.19(f)(1)(ii)(A) (eCFR)A financial institution must submit its annual HMDA loan application register by March 1 of the year after the data were collected, have it certified as accurate and complete, and keep a copy for at least three years.
Source: 12 CFR 1003.5(a)(1)(i) (eCFR)Fannie Mae's Selling Guide keeps the lender responsible for the accuracy of the data it submits to Desktop Underwriter and for making sure the loan meets every verification message and approval condition in the DU Underwriting Findings report.
Source: Fannie Mae Selling Guide B3-2-01
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Around the mortgage loan file
This page covers the mortgage file to closing. These pages cover the systems on either side of it.
Loan origination software
Product-agnostic origination: application intake, documents and the underwriting workflow.
Loan servicing software
What happens after closing: payment application, statements, delinquency and payoff.
Credit risk scoring software
Scoring and decision models that feed the underwriting step.
KYC compliance software
Identity verification for borrowers and co-borrowers at application.
Real estate document management software
Storage and retrieval for the property documents a mortgage file collects.
More in Financial Services
More Financial Services Solutions
Explore other production-grade engineering platforms we deliver across financial services.
Frequently Asked Questions
Lending mortgage cost follows the seven sizing drivers on this page, and extending or replacing your LOS usually weighs most. We size them on the scoping call rather than with a mortgage automation calculator.
It depends on whether we extend your current system or replace it. We agree a fixed first release on the scoping call, often application capture and the Loan Estimate clock for one product.
Often, yes. If your LOS exposes events or data through an API or a MISMO export, we build an event and deadline service beside it that records each checkpoint and alerts your team before a clock runs out.
We build the data and timing layer and generate the forms from loan data, using your document provider or templates your compliance team approves. The form content follows Regulation Z; the deadlines come from the recorded events.
Demographic questions are asked in the application flow, each answer is stored with how it was collected, and the data is kept off underwriting screens. HMDA edits run as the file moves, so errors are fixed while the loan officer still has the file open.
Yes. For brokers and new mortgage lenders we usually start with application capture, disclosure timing and a submission flow to wholesale partners, then add more as volume grows.
Yes. Origination ends when the loan is boarded to servicing. We export final terms, escrow setup and documents to your servicer, and our loan servicing software page covers the work after that.
No. Desktop Underwriter or Loan Product Advisor findings tell you what to verify; they do not verify it. We import each message and condition as a tracked item, and an underwriter clears it against the evidence. Fannie Mae's Selling Guide keeps the lender responsible for the data it submits and for meeting every condition in the findings.
Industries