KYC/AML Escalation Memo☆

When something about a borrower's or investor's money doesn't add up — funds from an unrelated third party, a down payment that doesn't match the file, an entity nobody can explain — this writes the internal memo for whoever makes the call: facts with dates, what was expected versus what happened, red flags mapped to categories, and one recommendation.

What it does

• Writes a time-stamped trigger section with facts only, no conclusions
• Compares what the file says to expect with what actually happened
• Maps each observation to a red-flag category and lists categories checked and not present
• Lists what is still needed and from where
• Ends with one recommendation: clear, enhanced due diligence, exit, or refer

When to use it

• Funds for closing or a fund subscription arrive from an unexpected source
• A borrower's story and documents don't match
• An internal alert needs to go up the chain in writing

What to have ready

• What triggered the concern, with dates, amounts and parties
• What the KYC file says about the customer
• Recent activity and any earlier alerts

How to use it

1. Download it with the button above. You'll sign in with a work email — that's how the creator knows who is using their skill.
2. Copy the install prompt from the "Run it in Claude" box, and paste it into Claude along with the file. Claude installs the skill, fills in your firm's details where the file has [BRACKETED] placeholders, and runs a quick test with you.
3. Then just ask in plain English. Claude picks the skill up on its own when a request matches it. Anything it still needs, it asks you for — it won't invent a number.

"Write an internal escalation memo: [BORROWER LLC]'s closing funds came in three wires from [UNRELATED PARTY] and don't match the bank statements in the file."

What you get back

An internal escalation memo with seven set sections and a single recommendation with a short rationale.

Good to know

• Output quality tracks input quality. A missing figure is flagged as missing — it is never estimated to fill a gap.
• Every draft is a starting point for your own review, not a finished decision.
• Runs anywhere Claude does: the Claude app, Claude Desktop, or Claude Code.
• Internal use only. It never drafts a suspicious activity report or anything for the customer, and the author's bank-style examples need translating to a lending file. Whether your firm has formal AML obligations depends on what it is and does — confirm with counsel.

Source & credit

Imported from Mohit Aggarwal's open-source PM Skills library (MIT). Author: Mohit Aggarwal — https://github.com/mohitagw15856/pm-claude-skills. LenderSkills renamed the skill for this catalogue; it also appended a legal disclaimer, and the package header lists every change. The author's content is otherwise unmodified. Full credit to the author. Mohit Aggarwal did not submit this listing and does not endorse it — the original is free at the link above.

Legal disclaimer

This skill drafts; it does not decide. Its output is not legal, tax, accounting, appraisal, or investment advice, and using it creates no attorney-client, fiduciary, or advisory relationship. Nothing it produces is a commitment to lend or an offer to sell a security. Verify every number, date, citation, and conclusion against the source documents, and have a qualified professional licensed in the relevant jurisdiction review the work before you rely on it or send it to a borrower, investor, counterparty, or regulator. Laws, rates, and market data change. The final work product is yours.