The Offer That Looks Like a Gift and Is a Decision
When a loan casefile runs through the automated underwriting system and comes back with value acceptance offered, the lender has been handed something that feels like free time. No appraisal to order, no two-week wait, no appraiser availability problem in a rural county, a faster clear-to-close and a cheaper loan. The reflex across most shops is to take it every time it is offered, because the whole point of the waiver is speed and cost, and turning down free speed feels like leaving money on the table.
The reflex skips a decision the lender actually owns. Accepting value acceptance is not accepting a value the agency computed and stands behind. It is the lender electing to accept the value it submitted, with the representation-and-warranty consequences that follow for the life of the loan. The agency's offer removes the appraisal requirement. It does not remove the lender's exposure if the value turns out to be wrong, and on some files the right answer is to decline the waiver and order the appraisal anyway, because the waiver is cheaper only until it is the reason a loan gets repurchased. An agent that takes every waiver offered is not automating a decision. It is automating the absence of one.
What the Programs Actually Are
The two agency programs are more different from each other than the shorthand suggests, and the difference changes the risk. Fannie Mae offers value acceptance, the option formerly called the appraisal waiver, under Selling Guide B4-1.4-10, where an eligible casefile in Desktop Underwriter can close with no appraisal and no new look at the property, on the value the lender submits. Separately it offers value acceptance plus property data under Selling Guide B4-1.4-11, which still waives the appraisal but requires an interior and exterior property data collection to the Uniform Property Dataset, submitted through the Property Data API, with the loan delivered under the applicable special feature code. Freddie Mac runs the parallel options through Loan Product Advisor as automated collateral evaluation, ACE and ACE+ PDR, where ACE+ PDR likewise pairs the model-based waiver with an on-site property data report collected by a trained data collector.
The distinction that matters operationally is whether anyone looked at the property. Plain value acceptance accepts the value with no fresh observation of the collateral, so the lender is relying entirely on the model and the data behind it. The property-data variants put a human at the property to collect condition data, which catches the thing a model cannot see, a property that is not in the condition the data assumes, incomplete construction, a safety issue. So "we took the waiver" is not one fact. It is at least three different risk postures depending on which program was offered and accepted, and the agent has to know which one it is looking at, because the eligibility rules, the delivery requirements, and the residual risk are different for each.
Where the Agent Sits, and the Line It Does Not Cross
The agent's job on this desk is the decision and the documentation around the waiver, and explicitly not the valuation. We are careful about this line because it is the same line that governs the rest of the collateral desk: an AI agent can run the collateral review and the AVM-rule obligations, and it cannot form an opinion of value, because that is an appraiser's licensed act and appraisal independence draws a hard boundary around it. The value-acceptance agent never computes a value, never adjusts the submitted value, and never nudges a number toward what a waiver needs.
What it does is decide whether to accept the offered waiver on this file, against the lender's encoded collateral policy. The agency offering value acceptance is a necessary condition, not a sufficient one, because the lender is allowed to set a higher bar than the agency and most prudent lenders do. The agent reads the file for the signals the lender's policy says should push toward ordering an appraisal despite the offer: a property type or market where model confidence is weaker, a value that sits at the edge of the eligibility parameters, a purchase where the contract price and the submitted value diverge, a cash-out where the equity reliance is high, a property with a data history that looks thin. On a file that clears the lender's policy, the agent accepts the waiver and documents the basis. On a file that trips a policy signal, it declines the waiver and routes to order the appraisal, or surfaces the call to a human as a named exception when the policy leaves room for judgment.
The Delivery Requirements Are a Compliance Surface, Not a Checkbox
Taking the waiver is only half the obligation. The loan then has to be delivered correctly, and the delivery requirements for these programs are specific enough that getting them wrong converts a valid waiver into a defective loan. Value acceptance plus property data requires the property data collection to actually exist, conform to the dataset, have been submitted through the right channel, and be delivered under the right special feature code. A loan delivered as a property-data waiver without the conforming data record behind it is a representation the lender cannot support.
So the agent treats the delivery requirements as part of the decision, not as a downstream clerical step. When it accepts a property-data variant, it confirms the property data report is present, conforms, and was submitted, and that the delivery metadata matches the program actually used, the same data-integrity discipline we apply at investor delivery and purchase suspense. A waiver that is correct in the decision and wrong in the delivery is still a defect, and it is the kind of defect that surfaces in a post-purchase review rather than before funding, which is the expensive place to find it.
Why the Whole Thing Is Governed as a Model Decision
The policy that decides when to accept a waiver is a set of encoded rules producing a consequential credit-and-collateral decision at volume, which makes it a model-adjacent control we govern under the same framework as the rest of the stack, in the spirit of SR 11-7. The lender's waiver-acceptance policy has an owner and a version, so when the lender tightens its bar after a market shifts or an investor pushes back, that change is deliberate, recorded, and applied consistently to every file after it, rather than drifting across individual underwriters' habits.
There is a measurable feedback loop to close, too. A lender accepting waivers should be watching what happens to the loans where it did, because the waiver decision has an observable downstream signal in repurchase requests, in post-purchase valuation reviews, and in default severity on the files where the collateral turned out weaker than the accepted value. We build the record so that the waiver decision on each file is tied to the policy signal that drove it, which is what lets the lender later ask the only question that validates the policy: on the files where we took the waiver, how often was the collateral what we accepted it to be. A waiver policy that is never checked against outcomes is a cost-saving measure that might be a risk-building one, and the only way to know is to have kept the record that lets you look.
The Honest Read
Value acceptance is real speed and real savings, and taking it reflexively on every offer is how a lender converts a tool into a liability it will not see for two years. The agency removes the appraisal requirement. It does not remove the lender's representation-and-warranty exposure on the value, and the lender's own policy, not the agency's offer, is what should decide whether to accept the waiver on a given file. An agent is well suited to this because the decision is high-volume, rule-shaped, and benefits enormously from being made consistently and documented, as long as it never crosses into forming the value itself.
We built the value-acceptance desk at Sei to make the decision the lender owns rather than the default the agency offers, to know the difference between a bare waiver and a property-data waiver and deliver each correctly, and to keep the record that lets the lender test its own waiver policy against what the collateral actually turned out to be. The waiver that is right on the file and right on the delivery and documented well enough to defend is the one worth taking. The rest is speed borrowed against a future review.
Ramkumar Venkataraman
CTO & Co-Founder