When two financing sources disagree: a claim-level resolution process

Two authoritative-looking sources can disagree because they cover different transactions, apply to different dates, or have not been updated together. The correct response is to resolve the claim, not to count how many websites repeat each number.

Begin by writing the exact decision the conflicting information would affect. If the disagreement concerns a financing limit, identify whether the reader is evaluating eligibility, building a sensitivity case or merely describing an historical observation. Those are different uses of evidence.

A discrepancy observed during this library’s research

On October 21,2026, the Fannie Mae supplemental-loan HTML term sheet displayed a maximum LTV description of up to 70%, with qualifications for asset class and use of proceeds. The PDF linked from that same page displayed up to 75% on page 2, also with qualifications. Its footer carried a 2026 copyright notice.

This observation does not establish which number controls a particular loan. A copyright year is not an effective date, and neither summary alone resolves all transaction conditions. The discrepancy is useful because it demonstrates why an official-domain link is not sufficient evidence for an unqualified eligibility claim.

The library’s supplemental-financing guide therefore uses explicitly hypothetical sizing inputs and does not prescribe either displayed number as a universal current limit. The conflict is recorded for review rather than hidden in a citation list.

Step 1: confirm that the sources answer the same question

Compare program, property category, transaction purpose, loan position, geography and measurement definition. A purchase limit and a cash-out limit may legitimately differ. A combined-debt limit and an incremental-loan limit are not interchangeable. An underwriting assumption can also differ from a contractual servicing test without either being erroneous.

If the scopes differ, split the original broad claim into precise claims. Record the conditions beside each result. Do not describe a resolved scope difference as an unexplained contradiction, and do not use a source outside its scope merely because its number is convenient.

Step 2: establish authority and timing

Identify the controlling document family and the relevant update mechanism. A rule, program guide, bulletin, term sheet and lender explanation can play different roles. The newest-looking webpage is not automatically the document with authority to change the requirement.

Record publication date, stated effective date, applicability trigger and retrieval date separately. A bulletin may apply to commitments after a specified date while older loans retain a prior provision. If the trigger is unknown, keep the transaction conclusion open and identify the evidence needed to close it.

When a direct document cannot be retrieved, disclose what was inspected: an official indexed excerpt, a summary, or an archived copy. That evidence may support a narrow observation, but it should not be represented as a complete review of unseen conditions.

Step 3: put the disagreement into a claim ledger

Assign a stable claim identifier. Record the competing statements, exact URLs and sections, source versions, affected resource IDs, affected model assumptions, responsible reviewer and next action. Preserve the source excerpts necessary for verification within appropriate permissions; a bare homepage link is not enough.

Use explicit states such as unresolved, scope reconciled, superseded or confirmed for a stated application. A resolved record should explain the reasoning and supporting authority. “Reviewer chose the conservative value” is an assumption decision, not evidence that the lower figure is the current rule.

Step 4: isolate the uncertain input in dependent work

If a model depends on the disputed figure, label it as an assumption or prevent it from producing an eligibility conclusion. A sensitivity comparison can show what changes under two inputs, provided neither scenario is presented as an approved option.

For an article, remove an unsupported definitive sentence and retain the qualified explanation that the evidence supports. For a downloadable template, change the field instruction if it previously prefilled the disputed requirement. For a case study, state that its assumed threshold is illustrative and independent of any program claim.

This keeps useful work available without disguising uncertainty. It also avoids a common maintenance failure: correcting an article while leaving the old number embedded in a calculator default, chart or downloadable example.

Step 5: close the record with a bounded conclusion

A completed resolution might identify a superseding bulletin and the exact transactions to which it applies. Another might establish that the two summaries concern different categories. If the responsible program or lender must clarify the point, preserve that written clarification and its scope.

Do not claim an issuer confirmation unless one actually occurred. If the evidence remains insufficient, the appropriate conclusion is that the requirement has not been established for the intended use. That is a research result, not a license to fill the gap with an AI-generated explanation.

Recheck the resources that depended on the claim

Once the issue is resolved, update the source register, affected prose, model assumptions and worked examples. Recalculate material outputs and invalidate approvals attached to changed content. Retain the prior version and correction note so the evolution is traceable.

The goal is a reader-facing answer that is both useful and supported. A precise statement of what is known, what varies and what evidence changes the answer is more durable than an apparently definitive number with an unresolved source conflict.