Who This Is For
Processors and closers, pre-funding QC managers, and Directors of Mortgage Ops who have watched a file reach the closing table with a paystub, a bank statement or a verbal VOE that went out of date while everyone was waiting on something else.
Every Document in the File Has Two Dates
A document in a loan file has the date it arrived and the date it speaks for. Underwriting cares about the second one, and the agencies set a limit on how old it can be when the loan closes.
Fannie Mae's rule is in Selling Guide B1-1-03: credit documents, which include the credit report and the income, employment and asset documentation, can be no more than four months old on the note date. When the file holds several documents of the same type, the most recent one is the one measured. Tax returns are treated separately, because their validity depends on filing windows rather than age. FHA sets a 120-day limit in Handbook 4000.1, and FHA measures it to the disbursement date, not the note date. VA's Lender's Handbook uses 120 days as well, with a longer window for new construction. Then there are the items with their own short clocks. Fannie expects the verbal verification of employment within 10 business days before the note date. An appraisal more than four months old on the note date needs an update, and one more than 12 months old needs a new appraisal, under B4-1.2-02. Many investors tighten all of these with overlays, and 90 days is a common one.
None of this is obscure. Every processor knows the rules. The problem is the denominator. On the day a paystub arrives, nobody knows the note date for certain, so nobody knows the paystub's expiry date for certain either. Expiry is a function of two dates, and one of them keeps moving.
How a File Goes Stale Without Anyone Touching It
Here is an illustrative file, with the dates simplified. The application comes in on March 3. The borrower uploads two paystubs, the most recent with a pay date of February 28, and two months of bank statements, the latest closing on February 25. Closing is scheduled for April 15, well inside every window.
Then the appraisal comes in low and the borrower files a reconsideration of value. Title finds an old judgment that needs a payoff letter. The lock gets extended. Closing moves to May 20, then to June 3. Nobody touched the paystub or the bank statements, and nobody needed to, until the closing date passed the point where the bank statement is too old under the investor's 90-day overlay and the paystub fails Fannie's four-month test. If the file is FHA and it is a refinance with a right of rescission, disbursement is at least three business days after consummation under Regulation Z 1026.23, so a document that passes at signing can fail at disbursement. We wrote about the rescission clock separately.
In a manual operation this gets caught in one of two places. A careful closer re-checks dates when the closing gets scheduled. Or pre-funding QC catches it the day before funding, and the borrower gets an urgent request for a new paystub on a Friday afternoon. The second is common, because nobody owns the job of re-checking documents every time a date moves. It belongs to everyone, so in practice it belongs to the person who finds it last.
Reading the Right Date Off the Page
Before an agent can track age, it has to know which date on the document counts, and that is a per-document-type rule we had to write down explicitly.
A paystub has a pay period start, a pay period end and a pay date. A bank statement has a statement period and a closing date. A VOE form has a date the employer signed it and, sometimes, a date the information is "as of." A credit report has a pull date. A gift letter has a signature date that does not matter for age at all. When we started encoding these, the hardest part was that experienced processors did not always agree on which date governed for a given form, because the habit had been learned by imitation rather than written down. So we wrote it down, per document type, in the Rulebook, with the agency or investor citation that supports it, and the lender reviewed the list before it went live.
The Indexing Agent classifies each document as it lands, and the extraction captures the governing date as its own field in the Loan Graph, cited to the page and the region it was read from. We treat that date as a decision field, which means it goes through Triple Check like income or a liability does. That choice cost us some throughput and we made it on purpose. A misread date is a quiet failure. If the model reads a February pay date as January, nothing breaks and nobody notices; the file just carries a wrong expiry date until a person happens to look. So for the governing date, the checker re-reads the page image rather than trusting the first extraction, and a disagreement holds the document for a person.
The Expiry Calendar Is Recomputed Every Time a Date Moves
With a governing date on every document, the age test is arithmetic. What makes it useful is when the arithmetic runs.
We keep one expiry date per document, computed against the current scheduled closing date (or disbursement date, for programs that measure there) and the strictest window that applies to that loan: the agency rule, the investor overlay or the lender's own SOP. The Orchestrator treats a change to the closing date as an event. When the date moves, every document's age test is re-run against the new date in the same minute, and anything that will expire before the new date, or within the lead time we keep before it, becomes a refresh task.
The lead time matters more than the window. Borrowers do not send a new paystub the hour you ask. The Document Concierge asks early enough that a normal response time still lands inside the window, and it asks for exactly the document that will expire, named, with the reason. A borrower who gets "we need your most recent paystub because your closing moved to June 3" sends it. A borrower who gets a list of six items with no explanation calls the loan officer to ask why.
The same event logic runs in the other direction. If closing moves earlier, the agent drops refresh tasks that are no longer needed, so the borrower is not asked for a document the file does not need. The failure we designed against is a request left open after the date it was based on has changed, so the borrower sends a bank statement nobody needs and wonders why they were asked.
When the Refresh Does Not Arrive
Sometimes the borrower does not send it. The file then has a document that will fail the age test at closing and no replacement. That is a credit question, and the agent's job is to make it visible early rather than to resolve it.
Two rules matter here. Regulation Z's ability-to-repay rule at 12 CFR 1026.43(c) requires the creditor to verify the income or assets it relies on using reasonably reliable third-party records, and a stale record is a weaker record, which is why the agencies set the windows in the first place. And if the lender needs the refreshed document to decide the application and the borrower has gone quiet, Regulation B's notice of incompleteness under 1002.9(c) is the tool, not an indefinite hold. The agent creates the condition with the failing rule named, tells the processor how many days remain before the closing date makes the problem a defect, and puts the incompleteness question in front of the person who owns it. It does not decide to waive a window, and it does not decide to send an incompleteness notice. We covered how conditions and incompleteness interact in more depth elsewhere.
Where Pre-Close QC Picks It Up
Even with the calendar running, the last check belongs to pre-close QC, because the closing date is only final when the closing package is drawn. The Pre-Close QC Agent re-performs the age test on every document against the final note date and the expected disbursement date, re-checks the verbal VOE timing, and confirms the appraisal age against the update rule. It also checks the case the calendar cannot see: a refreshed document that arrived but was filed next to the old one instead of replacing it, so the file has two paystubs and the stale one is the one the underwriter cited. The rule in B1-1-03 is that the most recent document is the one measured, so the check confirms the decision was made on the most recent document, and that the most recent one is in the file.
In our pre-close QC deployment at Better Mortgage, across Conventional, FHA, VA and HELOC files covering over twenty document types, 78% of items clear at high confidence with a citation trail and review time per file fell from 4 hours 50 minutes to 47 minutes. Document age is the sort of check that belongs in the 78%: it is arithmetic on a cited date, and a reviewer reading dates by eye on their fortieth file of the day is exactly the control that fails.
What We Would Tell a Lender Building This Themselves
Write down the governing date for every document type before you automate anything, and get underwriting and QC to sign the same list. Measure against the strictest window that applies to the specific loan, and version the windows with an effective date, because investors change overlays and the change should apply to new files without rewriting history on old ones (our notes on Rulebook change management cover how). Treat a closing-date change as an event that triggers work. And verify the date itself as carefully as the number next to it, because the date decides whether the number is still allowed to count.
Ramkumar Venkataraman
CTO & Co-Founder