When an email attachment has not reached the file record

“Sent by email” describes a delivery attempt. It does not tell the next processor where the document is in the file, whether someone reviewed it or which condition it answers. Reconcile the incoming message with the LOS record before treating the request as finished.

This check is especially useful when a thread contains several attachments or a replacement arrives under the same filename. A readable file history needs to identify the actual version used.

Start with the message that delivered it

Confirm that the message belongs to the right file through your approved procedures. Review the sender, the context of the request and each attachment. A familiar subject line cannot establish that every document in the thread belongs in that file.

Record the receipt time and retain the communication where your team expects to find it. If an attachment cannot be opened or the approved transfer fails, keep that as an unresolved action. Do not let a reply timestamp stand in for document availability.

Use the lender’s approved channels and file-handling procedures throughout. This article proposes a reconciliation check, not a new place to store borrower information.

Compare the attachment with what is already filed

Look for an existing copy before creating another document entry. Similar names are a starting point for review, not proof that two attachments are identical. Compare the document itself, its period and the pages available in each version.

If a replacement corrects an earlier problem, preserve the reason for replacement and make the current evidence easy to identify. Follow your team’s retention and version procedures rather than deleting a previous copy just to make the list look clean.

Then inspect the condition association. A document may be filed yet still leave the reviewer searching for the condition it supports. Record any part of the request that remains unresolved.

Illustrative reconciliation check

This is a sample exchange. A borrower replies to the original document email with an attachment named “statement.pdf.” Later, they send another attachment with the same name and say it includes the missing page.

Open the later attachment and verify that it contains the page identified in the correction request. Compare it with the earlier version. After review, file the appropriate evidence using the team’s naming and version rules, associate it with the condition and retain the correction history.

A useful note says what changed: “Replacement statement received in the later reply includes the previously missing page. Reviewed version is associated with the statement condition.” The note should refer to the actual retained evidence. It should not assert that the underwriter has accepted it.

Close the gap between inbox and record

Before moving on, open the filed document from the LOS rather than relying on the upload confirmation. Confirm that the reviewer can reach the intended version and understand the related condition. If the document still needs review, leave that task assigned.

For a vendor demonstration, send a sample replacement with the same filename. Ask the vendor to follow it from receipt to the file record. Write down any comparison, copying or association your team still performs.

The mortgage back-office automation guide helps identify which document tasks to test. Book a walkthrough to inspect an attachment through checking and filing.