The knowledge standard for a mortgage SAR

Suspicious activity reporting is an information-reporting duty, not a criminal conviction. For a covered residential mortgage lender or originator, the trigger is whether the institution knows, suspects, or has reason to suspect that a transaction or pattern meets a regulatory category. The institution does not need to prove that a crime occurred before filing.

Who is covered

The Bank Secrecy Act regulations include residential mortgage lenders and originators among the financial businesses subject to SAR rules. Coverage depends on the entity's activities and regulatory definition. A loan originator should follow the company's written escalation process and should not decide alone that suspicious facts are harmless simply because the loan has not closed.

The three suspicious-activity categories

• The transaction involves funds derived from illegal activity or is intended to hide or disguise those funds or assets.
• The transaction is designed to evade Bank Secrecy Act requirements, such as reporting or recordkeeping.
• The transaction has no business or apparent lawful purpose, and after examining available facts the institution knows of no reasonable explanation.

Proof is not the threshold

“Knows, suspects, or has reason to suspect” is a reporting threshold. It is not the same as proving fraud, identifying the exact predicate offense, or showing that a borrower will default. A single odd fact may have a reasonable explanation. The institution evaluates the available facts, the customer profile, related transactions, and the purpose of the activity.

Transactions can be attempted

A suspicious transaction may be conducted or attempted. An application that is withdrawn or declined can still contain facts that merit review. The absence of a closing or funded loan does not automatically eliminate the possibility of a reportable transaction.

Apply the threshold carefully

1. Identify the transaction or pattern and the facts that triggered concern.
2. Check whether those facts point to illegal proceeds, evasion, or no apparent lawful purpose.
3. Review reasonable explanations and available information under the institution's procedures.
4. Escalate promptly to the designated BSA/AML officer or compliance team.
5. Do not tell the subject that a SAR was filed or disclose information that would reveal its existence.

Exam traps

• Waiting for proof beyond reasonable doubt.
• Assuming an unfunded loan application cannot lead to a SAR review.
• Treating every unusual transaction as automatically reportable without examining available facts.
• Using a credit-risk indicator by itself as proof of money laundering.
• Disclosing the SAR or its existence to the borrower.

Key takeaway

The covered institution reports when it knows, suspects, or has reason to suspect a qualifying suspicious transaction. Proof of a crime is not required, but facts and reasonable explanations must be assessed.

Suspicion is not proof of a crime

A suspicious activity report does not require a conviction or proof of a particular offense. A covered loan or finance company evaluates whether activity is suspicious under the rule applicable to that institution, considering facts, circumstances, thresholds, and exceptions. The MLO’s role is to recognize and promptly route facts; the designated BSA function decides whether a filing is required.

A red flag is a reason to review, not a conclusion that a borrower committed fraud. Consider the customer profile, transaction purpose, source of funds, timing, parties, and explanations together. Document verified facts and distinguish them from analysis.

Patterns, escalation, and confidentiality

Potential indicators can include unexplained third-party payments, inconsistent source-of-funds explanations, rapid ownership changes, documents conflicting with independent records, or attempted transactions lacking a credible economic purpose. No one indicator automatically requires a SAR. Preserve the application, communications, payment records, ownership information, and chronology, then use internal escalation channels.

Do not tell the subject that a SAR is being considered or has been filed, and do not conduct an ad hoc investigation that risks tipping them off. Follow BSA officer instructions for routine requests. The applicable rule defines institution coverage, reporting threshold, timing, and exceptions, so do not import a bank threshold into every mortgage-company question.

Write a factual disposition

Keep a record of the review, escalation, and disposition even when no SAR is filed. If filed, the narrative should explain who did what, when, where, how, and why the conduct was unusual, using a clear chronology and supporting records. Avoid unsupported conclusions and preserve the difference between verified facts and the institution’s assessment.

Remember that SAR confidentiality and record-retention rules continue after filing. Supporting documentation is maintained separately and made available to authorized agencies on request. Customer-facing staff should use approved explanations for delays or document requests without revealing a report or its existence.

Practical review points

A practical escalation note records the activity, date, participants, amount or attempted amount, why it differs from expected behavior, steps taken to understand it, and any conflicting explanation. Do not coach the customer on what to say, alter records, or put SAR deliberations in an ordinary customer-facing note. The BSA officer should apply the correct rule for the institution and decide whether the facts meet the reporting standard; frontline staff should preserve evidence and maintain confidentiality.

Additional application detail

Not every unusual transaction is reportable, and a lack of a plausible explanation does not itself prove an offense. The designated reviewer weighs the full record against the legal reporting standard and institution-specific procedures. Prompt escalation matters because the filing clock, if triggered, is measured under the applicable rule; frontline staff should not delay escalation while trying to reach their own conclusion.

Final review scenario

The loan-or-finance-company rule has institution-specific triggers and deadlines, including a reporting duty for qualifying suspicious transactions under the regulation. The SAFE MLO exam may test the general standard, but operational staff should consult the current text rather than rely on a bank-specific summary. Keep threshold calculations and deadlines with the BSA reviewer’s workpaper so they can be reproduced during examination.

Additional boundary example

Example: a closing payment comes from a third party with no apparent relationship to the borrower, and the stated source changes after the lender asks for an explanation. The mismatch warrants escalation and documentation; it does not by itself prove money laundering or automatically establish that a SAR must be filed. Record the payment details, explanations, checks performed, and unresolved inconsistencies, then let the designated BSA reviewer apply the rule for the institution. Avoid questioning the customer in a way that reveals SAR deliberations, and do not tell them a report was filed.