“You’ve Known Me Eleven Years”: Asking Where the Money Came From

The sentence that changes the temperature

The review is going well. It's a client of eleven years, a substantial relationship, someone who has recommended three other clients to the firm.

Then the adviser gets to the item on his list.

"Before we finish — I need to go through some questions about the background to the funds coming in next month. It's part of a periodic review we're doing."

"...Sorry, what? You've known me eleven years."

He is offended, and his offence is genuine and entirely understandable. The questions still have to be asked, the answers still have to be good enough, and the adviser cannot make this comfortable by explaining why it's happening — because in many cases he isn't permitted to, and in others he doesn't fully know.

Asking a question you can't socially justify

Every other conversation in these series has a shared purpose: the professional and the counterparty both want something resolved. This one doesn't. The client wants the questions to stop, and the professional's job is to continue them anyway.

Four features define a source of wealth conversation.

The subject is the client's integrity, however carefully it's framed. No version of "account for how you came by this" avoids the implication, and pretending otherwise is why advisers deliver it so badly.

The explanation available is limited. What may be said about why questions are being asked, and what may be said about what happens next, is governed by the firm's policy and legal position and varies by jurisdiction. Advisers frequently have less latitude than the client assumes and more than they use.

A plausible answer is not automatically a sufficient one. The instinct in a good relationship is to accept what you're told, because it sounds fine and because the alternative is rude. That instinct is the failure.

And the relationship cost is real and immediate. He may reduce contact, complain, or leave. Nobody acknowledges that out loud in training, which is why advisers quietly avoid asking properly.

The apology is the problem

Almost every version of this that goes wrong begins with an apology, and it goes wrong in a specific, predictable way.

"Sorry, I know this is a pain, we just have to tick these boxes, it's a total formality —"

That framing tells the client three things: this doesn't matter, I'm not really asking, and a short answer will do. He gives one, the adviser writes it down, and the file now holds a sentence that explains nothing and would embarrass the firm if anyone looked closely.

The alternative isn't sternness. It's flatness.

"I need to ask you about the background to these funds. It's not about you specifically — we do it across the book, and I'd rather do it properly than lightly."

No apology, no drama, and a clear signal that a real answer is expected. Advisers find this hard because the apology is a social reflex under discomfort, and unlearning it is most of the skill.

And don't say it's routine if it isn't

The universal framing is useful and it has to be true. If these questions are being asked of this client for a particular reason, saying "we ask everyone" is a false statement made to a client to reduce awkwardness — which is both dishonest and, depending on the circumstances, may be exactly what the firm's policy prohibits.

Where the reason can't be given, the honest position is narrower and better: "I'm not going to be able to give you much more than that, and I know that's unsatisfying." Uncomfortable, accurate, and it doesn't create a problem the firm has to live with.

The questions themselves

Open before specific. "Tell me how the business came to be worth what it sold for" produces a narrative. A checklist of closed questions produces a series of one-word answers that document nothing.

Separate the story from the transaction. Where the wealth came from over a lifetime and where this particular money came from last month are different questions with different answers, and conflating them is the most common structural error.

Follow the thing that doesn't fit — once, neutrally. Dates that don't line up, a figure that doesn't match, a sale that happened after the transfer. "Just so I've got the order right — the sale completed in March and the transfer was in January?" Curious, not accusatory, and asked as though you've simply written it down wrong.

Don't signal what you're thinking. No change in tone, no pause that reads as significance, no indication of what may follow. This matters for reasons well beyond politeness, and it's what advisers most often get wrong when something starts to feel off.

Write down what he said, in his words. Including the part that didn't reconcile, and including the question you asked. A file note that summarises "client confirmed source of wealth is business sale proceeds" is worth almost nothing. One that records the narrative he gave, with dates, is worth a great deal.

And escalate on facts, not feelings. "Something felt odd" is not a finding. What he said, what it doesn't match, and what's missing — that is. Escalation is a process step, not an accusation, and advisers who understand that escalate earlier and more accurately.

Four ways it goes wrong

The apologiser, who undermines the question in the asking and receives a correspondingly thin answer. The most common by a wide margin.

The accepter, who treats plausible as sufficient because the relationship makes probing feel insulting.

The over-explainer, who eases the client's irritation by saying more about the process than the firm's position permits.

The signaller, whose tone shifts when something doesn't add up, telling the client exactly what has been noticed.

Why this isn't trained

Training covers typologies, not conversations. Annual modules teach risk indicators and categories. The interaction — asking a real person a question that implies distrust — is left to the individual.

The relationship cost is unacknowledged. Nobody says out loud that asking properly may damage a valuable relationship, so nobody teaches how to weigh it, and advisers resolve it privately by asking badly.

Seniority runs the wrong way. The most awkward clients to question are frequently the largest and longest-standing, so scrutiny is softest exactly where relationship pressure is highest.

And peer role play produces a cooperative subject. A colleague gives a clean, complete, well-ordered answer. Real ones are offended, vague, defensive about being asked, or fluent in a way that should prompt another question — and none of that is available in a two-person exercise between colleagues who want it to go smoothly.

What due diligence interview training can rehearse

A simulation can hold a counterpart who is genuinely affronted, or plausible but inconsistent, and score the interview on what determines its value: whether the question was apologised for, whether a narrative was obtained, whether the inconsistency was followed. Foretell AI supplies the counterparty configuration, transcripts and rubric-based scoring; the policy, permitted disclosures, escalation routes and all regulatory determinations stay with the firm.

Four to build:

Design caution — read before building. This scenario sits on regulated territory. Modules must use the firm's own policies, escalation routes and permitted wording; nothing here describes thresholds, typologies or red-flag criteria, and scenario libraries should not either. What may and may not be disclosed to a client about an enquiry is a legal and policy determination that varies by jurisdiction, and the exercise rehearses conversation quality only — it confers no compliance assurance and is not a substitute for the firm's obligations.

Designing the module

Pass one — the ask. Score whether the question was apologised for, minimised, or attributed falsely to routine.

Pass two — the narrative. Score whether an open question was asked first, whether source of wealth and source of funds were separated, and whether the answer obtained was specific.

Pass three — the inconsistency. Score whether it was noticed, whether it was followed neutrally, and whether the adviser's tone changed.

Rubric on observable behavior: Was an apology or minimiser used? Was the framing accurate? Was an open question asked before closed ones? Were the two sources distinguished? Was the discrepancy followed? Was the client's own language recorded? Was escalation framed on facts?

Apology-and-minimiser count is the measure to start with. It's trivially countable, it's the strongest predictor of a worthless file note, and most firms have never looked at it.

The operator case

The auditable output is the narrative in the file, and it is usually poor. Read fifty recent records and count how many tell you anything specific. That exercise tends to end the debate about whether this is a priority.

Scrutiny is inversely distributed to risk. The largest and longest relationships get the softest questioning, because that is where the social cost of asking is highest. That's a structural weakness produced by an entirely human incentive.

Advisers need to be told, by someone senior, that asking will never be held against them. Otherwise every awkward interview is weighed against a relationship the adviser is accountable for, silently, in the moment.

And permitted wording should exist. Most firms tell advisers what they may not say and leave them to construct what they may. Two or three approved sentences remove both the over-explaining and the false "we ask everyone."

For financial crime and compliance programmes, the reframing is useful: the control is not the question list but whether the conversation produced information — and a compliant interview that yielded nothing has satisfied the process and defeated the purpose.

Frequently asked questions

How should an adviser ask a client about source of wealth? Flatly, without apology, with an open question first to obtain a narrative rather than a checklist answer — and without describing it as routine unless that's accurate.

What's the difference between source of wealth and source of funds? One is how the client's wealth was built over time; the other is where a specific transaction's money came from. They need separate questions, and conflating them is the most common structural error in these interviews.

What should you do if a client is offended by due diligence questions? Acknowledge the reaction without apologising for the question, stay inside what you're permitted to say about why, and continue. The offence is understandable and it doesn't change what the interview needs to produce.

What if a client's answer doesn't add up? Follow it once, neutrally, as though you may have written something down wrong — then record what was said and escalate on the facts through the firm's process. Don't signal what you've noticed.

The short version

Eleven years of relationship does not answer the question, and the apology that makes the asking bearable is what makes the answer worthless.

Ask it flatly. Get a story, not a checklist. Separate the lifetime from the transaction. Follow what doesn't line up, once, without changing your voice. Write down what he actually said.

And if the file note you end up with wouldn't tell a stranger anything, the interview didn't happen — whatever the record says.

Foretell AI lets banks and wealth firms build conversational simulations — including source of wealth interviews, offended-client scenarios and inconsistency follow-up like the one above — with configurable counterparties, transcripts, recordings, and rubric-based evaluation. If your file notes record that a question was asked but not what the answer contained, we're happy to walk through how other firms have structured it.