The AI Agent Behind the Mortgage Point-of-Sale: URLA Intake, the TRID Application Trigger, and Preventing the Conditions Before Underwriting Ever Sees Them

The Front Door Decides the Loan's Cycle Time

A mortgage that takes 45 days to close and a mortgage that takes 28 days are usually the same loan with the same borrower and the same file. The difference is how much of the file arrived complete at the front door versus how much the processor chased down after the fact. Every condition that underwriting adds because a document was missing, a figure was inconsistent, or an income source was undocumented is a condition that could have been prevented at application, when the borrower was in the session and available to answer.

The mortgage point-of-sale, the borrower-facing intake surface that produces the Uniform Residential Loan Application (Form 1003 / URLA), is where that prevention happens or does not. Most POS software collects the application and hands it downstream. The agent we build sits behind the POS and does the work that decides whether the file arrives clean: it reads what the borrower entered as they enter it, identifies the documents the profile will require, and collects them while the borrower is still there. It also has to know, to the field, the moment the intake becomes a legal application, because that moment starts clocks the lender cannot restart.

We build the agent that runs across mortgage origination on lender platforms. What follows is where it operates in the POS, the decisions it makes, and the two compliance boundaries that make the front door a regulated event and not just a form.

The URLA Tells the Agent Which Documents the Loan Will Need

The redesigned URLA has more than a thousand possible fields across borrower information, employment and income, assets and liabilities, real estate owned, loan and property details, and declarations. A borrower does not fill in a thousand fields. The profile they present, a W-2 wage earner buying a primary residence with a conventional loan, or a self-employed borrower refinancing a second home, determines which fields matter and which documents the file will need to support them.

The agent's first job is to read the emerging profile and translate it into the document set the loan will require, before the borrower has finished. A borrower who enters rental income on the real-estate-owned section needs lease agreements and the schedule E treatment that goes with them. A borrower who enters employment with a start date inside the last 30 days needs an offer letter and a first pay stub the file does not have yet. A borrower who checks the declaration for an ownership interest in the property being financed has told the agent something about the transaction type that changes the disclosure set.

None of that is underwriting. It is the recognition that a specific answer on the application implies a specific document, and the useful moment to ask for that document is now, in the session, not in a condition three weeks later. The agent's document checklist is generated from the borrower's actual entries rather than from a static list, which is the difference between asking every borrower for everything and asking each borrower for exactly what their file needs.

What the Agent Decides and What It Does Not

The agent at the POS makes intake decisions. It does not make credit decisions, and the line between the two is the line that keeps the front door compliant.

Intake decisions are about completeness and consistency. Is the stated income consistent with the employment entered? Does the asset total support the down payment and reserves the loan structure implies? Is a document the borrower uploaded the document the field actually requires, a full tax return rather than a single W-2, a complete bank statement rather than a summary screenshot? These the agent handles, because they are questions about the file's completeness that have determinate answers and do not require judgment about the borrower's creditworthiness.

Credit decisions, whether the income qualifies, whether the debt-to-income ratio clears, whether the loan will be approved, belong to the underwriter and to the automated underwriting system the lender runs. The agent does not tell the borrower they are approved, does not tell them they qualify, and does not quote a decision. When a borrower asks the agent "will I get approved," the agent's answer describes what happens next in the process, not a prediction of the outcome, because a prediction is a representation about credit that the lender is accountable for and that the agent is not positioned to make. This is the same discipline we apply to the ability-to-repay analysis in underwriting: the agent produces the inputs, the human owns the determination.

The Moment Intake Becomes an Application

The most consequential thing that happens at the POS is invisible to the borrower. At a specific point, the information collected crosses from a rate inquiry into a legal application, and that crossing starts the TRID disclosure clock.

Under Regulation Z at 12 CFR 1026.2(a)(3), an application for a closed-end mortgage means the submission of six pieces of information: the borrower'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. When those six are in hand, an application exists. Once an application exists, 1026.19(e) requires the creditor to deliver or place in the mail the Loan Estimate no later than three business days after receiving it. The lender cannot collect a seventh piece of information to delay the trigger, and it cannot define the application away with fine print. The six-element test is the rule, and we have written on the full TRID timing architecture that follows from it.

This matters at the POS because a modern intake flow collects those six elements early and often out of order, and a borrower can satisfy the six-element test in the middle of a session without any human at the lender noticing. If the agent is the thing watching the session, the agent is the thing that has to recognize the trigger. Our agent tracks the six elements as discrete signals and marks the timestamp at which the sixth arrives. That timestamp is the event that starts the three-business-day clock, and it is written to the file as the application date the LE delivery has to measure against. An intake surface that does not track the trigger is an intake surface that discovers it missed the LE deadline after the deadline has passed.

The agent does not send the Loan Estimate, because LE content and delivery involve fee tolerances and a good-faith standard that sit with the lender's disclosure engine and its compliance review. The agent's role is to detect the trigger, stamp it, and route the event to the disclosure workflow with the clock already running, so the three days are counted from the correct moment and not from whenever someone happened to look.

The Second Clock: The Complete Application and Adverse Action

There is a second timing event at the front door that a POS agent has to respect, and it comes from fair lending rather than from disclosure. Under ECOA and Regulation B at 12 CFR 1002.9, a creditor has 30 days after receiving a completed application to notify the applicant of the action taken. The definition of a completed application at 1002.2(f) turns on the lender having received all the information it regularly obtains and considers in making a decision. The date the application becomes complete is the date the 30-day clock starts.

This is where the agent's document-collection work and the compliance clock intersect. If the agent tells a borrower a document is outstanding, the application is not yet complete for that item, and the file has to reflect why. Regulation B allows the lender to treat an application as incomplete and send a notice of incompleteness under 1002.9(c), but the notice has to specify the information needed and a reasonable time to provide it. An agent that requests documents casually, without the file recording what was requested and when, produces a gap between what the borrower was told and what the compliance record can support. Our agent logs each document request, the borrower's response, and the completeness state of the application as a structured record, so the point at which the application became complete, or the point at which an incompleteness notice was warranted, is a fact in the file rather than a reconstruction after the fact.

The Appraisal-Copy Right the Front Door Sets Up

One more front-door obligation gets set in motion at the POS, and it keys on a different application than the TRID clock does. Under Regulation B at 1002.14, a creditor on a first-lien loan secured by a dwelling has to provide the applicant with copies of all appraisals and other written valuations promptly upon completion, or three business days before consummation, whichever is earlier, and has to notify the applicant of the right to receive those copies within three business days of application. The application that starts that notice clock is the Regulation B application defined at 1002.2(f), which is not the same event as the Regulation Z six-element application the Loan Estimate keys on. A lender's application procedures can recognize a Regulation B credit request before all six TRID elements have arrived, and when they do, the valuation-rights notice clock runs from the Regulation B event, not the TRID one.

The agent's job here is narrow and worth getting right: it tracks the Regulation B application as its own trigger, separate from the six-element TRID trigger, and queues the valuation-rights notice the moment the Regulation B trigger fires, so the three-business-day window is measured from the correct event. Treating the two applications as one is exactly how the notice gets queued late and misses its deadline. The valuation itself, and the eventual reconsideration-of-value process if the borrower disputes the appraisal, sit downstream on the collateral desk, but the borrower's right to it originates at the front door and the agent has to trigger the notice on time.

The Failure Mode We Engineer Against

The pattern that produces the worst front-door outcomes is the POS that treats intake as data capture and pushes everything else downstream. The application is collected, the file moves to processing, and the processor discovers the rental income has no leases, the recent job change has no offer letter, the large deposit has no explanation, and the borrower who was available and engaged during the session is now hard to reach. Each gap becomes a condition, each condition becomes a round trip, and the loan that could have been clean at day one is clean at day 20. The MBA's Quarterly Mortgage Bankers Performance Report has put the fully loaded cost to originate above $11,000 per loan in recent quarters, and a large share of that cost is the human time spent chasing files that arrived incomplete.

The architecture we run inverts it. The agent reads the profile as it forms, requests the documents the profile implies while the borrower is in the session, checks each document against the field it supports, and marks the compliance triggers, the TRID application event, the completeness state, the valuation-rights notice, at the moment they occur. The file that reaches processing is the file the profile required, assembled when the borrower was available and the sources were fresh. The processor's job becomes review rather than retrieval, and the conditions underwriting would have added are conditions that were closed at the door.

The borrower experience in this model is that the questions they are asked are the questions their situation calls for, the documents they are asked for are the documents their file needs, and the process feels like it is paying attention rather than like a form that will generate a phone call next week. That experience is also the compliant one, because the same discipline that prevents the condition, reading the profile and asking for exactly what it implies, is the discipline that keeps the clocks accurate and the file's fair-lending record complete.

The Honest Read

The mortgage point-of-sale is usually sold as a borrower-experience surface, and it is one. It is also a regulated intake event where three separate clocks start, TRID disclosure, ECOA action timing, and valuation-rights notice, and where the file's eventual quality is mostly determined. An AI agent at the POS earns its place by doing the intake work that prevents conditions and by tracking the compliance triggers that a data-capture form ignores until they have already been missed.

The agent does not decide credit at the front door. It assembles the file the loan will need, catches the inconsistency while the borrower can still resolve it, and stamps the regulatory events at the moment they happen so the downstream clocks are measured from the truth. At Sei, that is how we think about the POS: not as the place we collect the application, but as the place we decide whether the rest of the loan will be easy or hard. The judgment about the borrower stays with the underwriter. The discipline that gets the underwriter a complete, on-the-clock file is the agent's to run.