8 min read
VeriFount is not an eKYC tool: where source-of-wealth work actually sits
Identity verified is not a wealth story written. The Source-of-Wealth memo is the next job — and it is still a writing task.
Most of the software a compliance team is offered wants to finish the front of the pipe. Capture the passport. Match the face. Screen the name. Route a form. Tick the onboarding box. That work is real, and on a payments or retail book it is most of the job. On a private-wealth desk it is the prologue.
VeriFount is an AI SoW agent for compliance teams. It assumes identity is already done. It drafts the Source-of-Wealth memo: a written corroboration, every material sentence cited to a document or a registry, a score of the paper, and a list of gaps a person may raise. A human still decides. It never onboards a client, never files a suspicious transaction report, and never contacts the client or the relationship manager.
This essay is about where that work sits — after eKYC, beside onboarding software, and still mostly done by an analyst with a zip file and a Word document.
| eKYC / identity | Onboarding vendors | VeriFount | |
|---|---|---|---|
| Job | Are they who they say they are? | Get the pack to go-live. | Does the wealth story hold up? |
| Output | Pass / fail + fields | Workflow closed | Cited memo, score, gaps a person may raise |
| Data | ID, biometrics, lists | Forms, pack, live screens | Registries (SG, HK, India, Indonesia) + the firm’s papers |
| Buyer | Operations | Operations | Head of Compliance — sits beside eKYC |
Identity is a gate. Wealth is a story.
eKYC and identity tools answer a binary question: is this person who they say they are. Passports, liveness, watchlists. The output is a pass or a fail, plus a handful of extracted fields. Onboarding vendors take the next operational step: collect the pack, route the file, close the workflow so an account can go live. VeriFount records papers as collected, verified, or gap — desk status beside eKYC, not a check by the agent.
Source of wealth is a different question. How did this person come to have assets of this order, and can the firm show its work later. The answer is a narrative. It has to survive a change of officer and an inspection that does not know the family. A face match does not write that narrative. A completed onboarding form does not either. Identity verified is not a wealth story written, and it is not a wealth story a reviewer can defend.
On mid-market private-wealth desks the pack is often already there. The relationship manager has forwarded probate papers, an ACRA extract, bank statements, a sale agreement, or a covering note that says the family has banked with the group for years. Someone still has to turn that pile into corroboration. That someone is usually an analyst, and the work still takes the better part of a day or more. It does not happen only at onboarding. Periodic review asks for it again. An adverse-media hit asks for it again. The file that was “done” in the portal is not done on the desk.
Who still writes it by hand
The desks that feel this most sharply are not the largest private banks. Those firms can staff a specialised financial-crime team and build internal tooling. The desks that cannot are mid-size multi-family offices, licensed trust companies, private banks below the top tier, and corporate service providers — especially in Singapore and the Gulf, where source-of-wealth expectations are heavy and the supervisor is not theoretical.
A Head of Compliance at one of those firms is not shopping for another identity vendor. They already have one, or their administrator does. They are shopping for fewer hours per file, and for a memo that is easier to stand behind when someone asks why this person was taken, or why this review was closed. The buyer is compliance, not operations. The job is analyst time and a defensible file, not a faster selfie.
Why the writing load is harder to ignore
This is not legal advice, and it is not a recap of any criminal case. It is public context. After Singapore’s 2023 money-laundering case, MAS has been clear that source-of-wealth checks need more depth than a form and a screen. Firms have responded the way firms do: they hire more compliance people. Analysts remain expensive and scarce. A desk that spends fewer hours reconstructing each pack, without lowering the quality of the write-up, is a straightforward return. There is no need to invent a percentage. Anyone who has sat a thematic review knows the texture of the questions: which independent paper, why this gap was accepted, who signed, and when.
The same shape of work exists outside Singapore. ADGM and DIFC books in the Gulf, Cayman and BVI fund and trust files, UK wealth, Australian wealth packs — the jurisdiction groups the VeriFount demo already walks. The rulebooks differ. The writing task does not: a cited story of the wealth, a score of the evidence, a person still on the stamp.
Four differences, without a roast
It is worth being precise about what eKYC and onboarding vendors do, because they do it well, and because VeriFount is not trying to replace them.
Different job. They check people are who they say they are — identity, face match, list screening, form routing. VeriFount assumes that work is done and drafts a cited memo for a reviewer. The agent never verifies.
Different output. They produce a pass or fail and extracted fields, or a closed onboarding workflow. VeriFount produces a written memo. Every claim is cited to a document or a registry. There is a source quality score. Gaps and questions for the client stay on the desk, to be raised by a human. VeriFount does not contact the client.
Different data. The hard part of a Singapore or Gulf wealth file is rarely the passport image. It is company registries across Singapore, Hong Kong, India, Indonesia, plus the firm’s own documents and the screening tools already in the stack. That is what the evidence locker is for.
Different buyer. Operations buys eKYC. The Head of Compliance buys time and a file that can be reconstructed. VeriFount sits alongside existing eKYC. It does not replace it.
What the agent should actually return
On Monday morning the useful artefact is not another green chip. It is a draft the named officer can read. Sentences that open into papers. Amber where the 2022 dividend has no board minute. A Source Quality Index that scores independence, official source, recency, completeness, and consistency — the paper, not the person. A list of relationship-manager questions that have not been sent. An audit trail in the firm’s time zone.
Approving that draft means the write-up is fit to keep on file. It does not mean the firm takes the client. It does not mean a suspicious transaction report has been considered or filed. Those acts stay with people who can hold them.
The point of the product, even in this shape, is the layer after identity: the Source-of-Wealth memo, written, cited, and still decided by a person. If a vendor cannot say where it sits — after eKYC, not instead of it — it is selling a different machine than the one a wealth-compliance team can put next to the tools they already bought.
Editorial from KnowledgeBase. Not legal advice. MAS Notice SFA04-N02 / FAA-N06 labels are draft templates, not filings. Prototype. Practice data only. VeriFount never onboards, never files an STR, and never contacts a client. Hosting can be deployed in-region. This prototype keeps state in the browser — no database, no outbound API.
Related
Continue in KnowledgeBase
What an AI KYC drafting agent should do — and the three things it must never do
A useful agent writes the file. It does not take the client, file the report, or speak to the person. Those three refusals are the product.
9 min read
Why Source-of-Wealth files still take days
The pack arrives in an afternoon. The corroboration does not. Locker chaos and inspection anxiety are the same problem.
8 min read
How to read a VeriFount memo
Citations, evidence scores, and a human stamp. Approval means the draft is fit to keep — not that the firm has taken the client.
8 min read
On the desk
Read a cited draft. A person signs.
Request early access, or walk a sample case. Never onboard, never an STR, never a message to the client.
