Corporate KYC that writes one cited file per client, asks the client once, and leaves every decision to your analysts and QC
Corporate files approved in days, not months, with every chapter cited and checked.
See one case, screen by screen ↓Corporate KYC is a solution for commercial KYC teams that builds one file per corporate client across entities, owners and products. Seven agents gather registry records, build the ownership structure, ask the client once for what is missing, write each chapter in prose with every sentence cited, screen every party and rate the relationship. A checker agent on another model disputes what does not hold; the KYC analyst signs chapters and a QC reviewer approves the file.
AI use cases in banking: a buyer's guide to agentic AI for bank and credit union operations →
Updated
A corporate KYC file spans many entities, owners and products, and its parts are gathered by different people in different systems: registry extracts pulled state by state, the ownership chart in a spreadsheet, expected activity from the relationship manager's call notes and old statements, screening in another tool and the rating in a model. Nobody reads the parts against each other until QC, if then. QC returns the file for its gaps, and the cycle repeats.
Meanwhile the client is asked the same questions by email, each missing document stalls the file for days, and the relationship manager learns the status by phoning the analyst. The risk sits in the gaps: a subsidiary that will receive wires is never screened, expected activity rests on statements that predate a new foreign subsidiary, and the file cannot show an examiner who decided what, on which evidence.
Estimated split of a Commercial Banking file's 61 days at the demo bank's 2025 median, by hand, and of the 6 days with the agents on the sample file. Our arithmetic, kept modest.
Seven agents gather, write and check each chapter; the analyst signs and QC approves the file.
Brightwater Cold Chain Holdings, Inc., a Delaware cold-chain logistics company with four subsidiaries, asks Corvane National Bank for operating accounts, ACH origination, domestic and international wires and a commercial card program. Here is its corporate KYC file on day 6, screen by screen, in the working solution.
Fourteen files are with Adaeze: 3 need her signature, 4 wait on clients, 2 have checker disputes and 2 sit with QC or the second line. Each row shows what the file waits on, a seven-cell chapter bar and the day of its service level. Eastgate Produce Exchange shows a Nevada registry error with Retry now, so a file never stalls silently.
“Nothing is past its service level.”
File KYC-26-10418 reads like the first page of a report: seven chapters, each with who is writing it now, a plain state and its sources, and six appendices. Chapters 1 and 2 are signed by Adaeze; chapter 4 is disputed; chapters 5 and 6 are drafted, with the rating at Low, 28 of 100. On the right, she can ask about the file and see what each of the seven agents is doing.
“Waiting on the client: 2 items, requested Oct 19.”
The Writer agent drafted expected activity by product from the FY2024 audited statements: deposits $34.0M a month, ACH $21.4M with a $4.2M daily limit, 58 domestic wires a month for $14.0M and no international wires. Every sentence carries a numbered source Adaeze can open. The Checker agent, on another model, disputes it under KYC-STD-07 §4.3: the client opened a Mexico subsidiary in 2025, and the chapter has no Mexico wires.
The Checker agent never edits a chapter; it disputes with the clause and the sources.
The Outreach agent merged what was missing into one secure request to Owen Kessler, Brightwater's Treasurer: the FY2025 audited statements and the expected activity with Mexico, nothing else. It lists what is already on file so it is not asked again, and shows the partial upload and "Partly answered: 3 of 5". Adaeze approved the request before it went, and Harlan Mercer is kept informed.
No rating, screening result or internal review ever reaches the client.
Both items arrive. Two minutes later the Writer agent redrafts chapter 4 on the FY2025 statements: deposits $39.5M, ACH $23.8M, 64 domestic wires for $15.2M and 22 wires a month to Mexico for $6.5M. The Checker re-reads it, disputes chapter 5 and reopens chapter 6, all in one visible trace.
“Waiting on you: the checker disputes chapter 5.”
Ten parties were screened on Oct 16 with no matches. But Brightwater Frio S. de R.L. de C.V., the new Nuevo León subsidiary, is in chapter 1 and will receive $6.5M a month in chapter 4, and it is not in the screening register. Adaeze can screen it now, override with a reason, or ask the client.
KYC-STD-07 §5.1: every entity that will transact through Corvane is screened before approval.
The Screening agent screens Brightwater Frio and its general manager, Joaquín Treviño Salas. One possible match: Brightwater Fria Trading S.A., Panama, 2009, a 71% name score. Registration, country and formation date differ, so it proposes "Not the same entity" at confidence 0.97. At 11:04 Adaeze confirms the clearance with reason code SC-02; she could have escalated to the sanctions team instead.
The Screening agent never clears a match alone.
On risk model CRR v4.2 the rating goes from Low, 28 to Moderate, 46: industry and screening base 16, ACH origination 8, a private-equity owner 4, international wires to Mexico 12 and a foreign subsidiary 6, each point cited. That is below the 65 line that sends a file to Financial Crimes Compliance, with a review every 24 months.
An override of the rating needs a reason code and QC.
Chapters 3 to 6 are checked, each with its one-line summary. Adaeze signs them with one attestation, and her name, the time and each chapter's version are recorded. At 3:52 she sends the file to Tomasz Brennan for QC; she cannot approve her own file.
“I have read these chapters and their sources, and they meet KYC-STD-07.”
Tomasz works through the QC checklist: every chapter signed, no open checker note, every party screened, owner and control person verified, the rating with its evidence, the client request closed. At Moderate, 46, the second line is not required. He approves on day 6, against Corvane's 2025 median of 61 days for a Commercial Banking file, and the products open in the core at 4:13 p.m.
A relationship manager can see the sign-off sheet, but can never approve.
Four people at Corvane National Bank who carry Brightwater's file from onboarding to approval: what their day looked like, and what it looks like now.
Seven agents gather, write and check each chapter; the analyst signs and QC approves the file.
Pulls company records for the client and every entity in its structure, across US states and abroad, and keeps extracts under 90 days old.
Builds the structure from the ownership ledger, the certification and look-through letters, finds who must be identified and verifies them.
Merges everything missing across chapters into one secure request to the client, sends reminders and keeps the relationship manager informed.
Drafts each chapter as plain prose with every sentence cited to its source passage, and redrafts when the evidence changes.
Re-reads every chapter against the bank's CDD standard, the evidence and the other chapters, and disputes what does not hold with the clause and the sources.
Screens every entity, owner and signer against OFAC lists, 314(a) requests, PEP lists and adverse media, and proposes clearances on identifiers.
Rates the relationship on the bank's risk model with every factor cited, and routes High files to Financial Crimes Compliance.
Signs chapters; a QC Reviewer approves. The agents propose; a named person decides.
Ask about any file, chapter, source or service level, or say what to prepare. Every answer cites the chapter and the source.
Why did the checker dispute chapter 5?
Because Brightwater Frio S. de R.L. de C.V. appears in chapter 1 and receives about $6.5M a month in the new chapter 4, yet it is not in the screening register. KYC-STD-07 §5.1 asks that every entity that will transact through Corvane be screened before approval.
What is Brightwater still waiting on?
On the client: 2 items requested Oct 19 from Owen Kessler, the FY2025 audited statements and the expected Mexico activity. He opened the request and saved 3 of 5 answers on Oct 20. Next reminder Thu 9:00 a.m.
Who must be identified?
One individual: Graham Ashby, 38% owner and the control person. The fund has no individual at 25%; the trust holds 9%.
Draft an update for Harlan Mercer
Here is a draft for Harlan Mercer, with no risk details, as relationship managers see progress only: “Brightwater: waiting on 2 items from Owen Kessler; a reminder goes Thursday.” I have put it in the CRM as a draft for you to send.
13 screens from the working solution, on its sample data. Pick one to see it large.
The thresholds, service levels and safeguards every file runs on are settings. Every change is a new version and takes effect only when the BSA Officer approves.
| Setting | Default | Choose from |
|---|---|---|
| Risk bands | Low below 30 · Moderate 30 to 64 · High 65 and above | Bands set on the risk model; a change is a proposal until the BSA Officer approves |
| Second-line review from score | 65 | A proposal until the BSA Officer approves; above it, Financial Crimes Compliance approves the file |
| Periodic review | Every 24 months at Moderate | Low every 36 months · Moderate every 24 · High every 12 |
| Screening fuzzy-name threshold | 0.70 | Set by the BSA Officer; the Screening agent proposes a clearance only at 0.95 confidence |
| Service level by queue | Commercial Banking 20 days | Corporate Banking 30 · Commercial Banking 20 · Business Banking 10 · Treasury add-ons 5 · Periodic reviews 30 |
| Escalations and client reminders | 75% to the team lead, 100% to the Head of Client Onboarding | Reminders on days 1, 3 and 6; the third goes to the relationship manager to call |
| Chapter 8, tax self-certification (FATCA and CRS) | Off | On for clients with foreign subsidiaries · Off |
| Relationship managers see | Progress only | No ratings, screening results or checker notes |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (the split of a file's days) · “typical” = published figures (industry surveys of KYC operations, 2023–2024: more than half of institutions take 61–150 days on a corporate review, at $2,598 on average per review in 2023; a 2024 survey of corporate treasurers: 87% have abandoned a banking application). Rules named for context: the FinCEN CDD rule, 31 CFR 1010.230; the CIP rule, 31 CFR 1020.220 (USA PATRIOT Act section 326); record retention, 31 CFR 1010.430; the FFIEC BSA/AML Examination Manual. The bank, clients, people, files and identifiers named on this page are fictional: characters and sample data in the working solution.
Corporate KYC is a solution for commercial KYC teams that builds one file per corporate client across entities, owners and products. Seven agents gather registry records, build the ownership structure, ask the client once for what is missing, write each chapter in prose with every sentence cited, screen every party and rate the relationship. A checker agent on another model disputes what does not hold; the KYC analyst signs chapters and a QC reviewer approves the file.
The client's application and the products requested, registry extracts for the client and every entity in its structure, the ownership ledger, the beneficial ownership certification and look-through letters for funds and trusts, audited statements and the client's answers on expected activity. The Outreach agent asks the client only for what is missing, in one secure request, and lists what is already on file so it is not asked again.
The Ownership agent builds the structure from the ledger, the certification and look-through letters, then finds each person owning 25% or more and one control person, as the FinCEN CDD rule (31 CFR 1010.230) requires. On the sample file it looks through a private-equity fund and a family trust and finds one individual to identify. It never decides an exclusion alone, and identifiers stay masked unless revealed with a logged reason.
It runs on another model family and re-reads every chapter against your CDD standard, the evidence and the other chapters. When something does not hold, it disputes with the clause and the sources, for example a subsidiary that will receive wires but was never screened. It never edits a chapter; the analyst settles each dispute by fixing it, overriding with a reason code or asking the client.
On the sample file, the client's onboarding was opened on day 1 and approved by QC on day 6, against the demo bank's 2025 median of 61 days for a Commercial Banking file. Published surveys put more than half of institutions at 61 to 150 days for a corporate review. Six days for a file like it is the target, measured in the live solution.
Yes. The agents gather, write, check and propose; they never sign, approve, send anything to the client, clear a screening match or override the risk model. The KYC analyst signs chapters, a QC reviewer approves the file, Financial Crimes Compliance approves files rated High, and relationship managers never approve. The BSA Officer approves every threshold, model and settings change.
Yes. Chapter templates, the clauses each chapter is checked against, risk bands, the second-line score, the screening threshold, service levels by queue, reminders, reason codes and privacy settings are all settings, versioned and on the audit trail.
The Agentic Solution Engine builds and deploys it from your requirements and documents: your CDD standard, your risk model, your chapter templates and reason codes, and a sample of past corporate files. It goes live once every quality gate has passed. We will walk you through it on your own files first.
Every owner found through every layer, with the math and the proof on file.
1-min demoCIP VerificationCIP exceptions cleared in minutes, each with its reason and its sources on file.
1-min demoEnhanced Due Diligence (EDD) ReviewEvery EDD file a cited memo, with activity checked against what the customer declared.
1-min demoWe'll run Corporate KYC on a sample of your own past corporate files and your CDD standard.