What problem does it solve?
Winning a corporate mandate is only the start. Before the client can pay a supplier, the bank has to open accounts in several entities and currencies, capture authorised signatories and their limits from mandates and board resolutions, set up users and roles in the corporate portal, configure payment entitlements and approval rules, connect host to host or API channels, and collect missing documents. These steps can involve relationship managers, onboarding teams, operations and technical implementation, each working in its own systems.
Where the same data is entered in several systems, or a case waits for one team or for the client, those handoffs are the natural first places to measure elapsed time and rekeying errors. Mistakes in signatory or entitlement setup are also a fraud and control risk. An agent can read the documents, prepare the setup and chase what is missing, but entitlements are a control: segregation of duties and four eyes approval must stay in place.
How does it work?
- Open a case. When onboarding is approved, the agent opens a setup case with a checklist based on the products, entities and countries in the deal.
- Read the documents. The agent extracts signatories, signing rules, limits and authorised users from mandates, resolutions and forms, and flags inconsistencies.
- Prepare the setup. It drafts account opening requests, users, roles and payment entitlements in the target systems' formats, restricted to what the approved mandate allows.
- Chase what is missing. It sends the client specific requests for missing or unclear items, tracks replies and reads returned documents on arrival.
- Approve and apply. Operations staff review and approve each setup batch under four eyes; only then are changes applied, and the client and banker get status updates throughout.
- Audience
- Customer facing
- Autonomy
- Copilot
- Adoption
- Emerging
- Channels
- Internal tools, Email, Web chat
What is it worth?
Benchmarks are computed from the public deployments below: one data point per organization per KPI, with who made each claim.
| KPI | Median | Reported range | Data points | Claimed by |
|---|---|---|---|---|
| Cycle time | Not pooled | 8 days | 1 | 1 organization |
Value drivers: Speed and cycle time, Customer experience, Lower cost to serve, Risk and loss reduction.
Indicative value
A corporate bank activating 1,500 new corporate clients a year
USD 225,000 to USD 1.4 million
Operations time released, valued at loaded cost per year
How this is calculated
Formula: clients * opsHours * reduction * hourlyCost. The low scenario uses every low input, the high scenario every high input.
| Input | Low | High | Basis |
|---|---|---|---|
| New corporate clients activated per year clients, clients per year | 1,500 | 1,500 | The reference bank. |
| Operations and implementation hours per client setup opsHours, hours per client | 15 | 30 | Editorial assumption, replace with your own time study. |
| Share of those hours saved reduction, fraction of time | 0.2 | 0.4 | Editorial assumption; no measured public benchmark was found. |
| Loaded cost of an operations hour hourlyCost, USD per hour | 50 | 80 | Editorial assumption, replace with your own loaded cost. |
What it leaves out: Values operations time only. It leaves out earlier revenue from clients who start transacting sooner, fewer setup errors and the related fraud risk, and the cost of integrating with account and entitlement systems.
Who already uses it?
2 public deployments, strongest evidence first. Grades: A regulator or audit, B the organization itself, C vendor case study, D anonymous or estimate.
Citi
United States · Banking · 2025
Citi added AI driven automation to CitiDirect Commercial Banking, its digital platform for mid sized corporate clients, covering data extraction, form filling and client query routing. The KYC process for renewals is now, in Citi's words, "fully integrated" with automated notifications and prefilled information, and a "Digital Servicing Hub" centralizes client queries, updates and document submission. Citi says the fully digitized onboarding process, with real time status updates, has significantly reduced onboarding turnaround times, though it gives no figure for that reduction. The platform now covers more than 57 percent of Citi's commercial banking client base and is live in the United States, Hong Kong, India, Singapore, the United Kingdom, Canada, Australia and Brazil.
No outcome disclosed.
Standard Chartered
United Kingdom · Banking · 2018
Standard Chartered partnered with Instabase to automate client onboarding, credit documentation and know your customer checks in Corporate and Institutional Banking. The machine learning and natural language processing solution reads documents and unstructured forms, and automates client due diligence by sourcing sanctions and adverse media information from public and private registries, so cases are processed automatically overnight instead of by staff copying and pasting from registries by hand. The bank says average client onboarding time in that business fell from 41 to 8 days since 2015, and expects the Instabase solution to bring it down further. The solution went live in Singapore, India and the United Kingdom, with Bangladesh among its first markets and further rollout planned.
- Cycle time: 8 days, average onboarding time in Corporate and Institutional Banking, at the time of the 2018 announcement
"In Corporate & Institutional Banking (CIB), average client onboarding times have dramatically reduced from 41 to 8 days since 2015, and will continue to fall with the use of Instabase to digitise the bank."
Claimed by: organization
How do you implement it?
A model agnostic playbook: what to prepare, the order to build in, and what goes wrong.
Data you need
- Product and country checklists for corporate onboarding
- Mandate, resolution and signatory templates and their required fields
- Entitlement models of the corporate portal and payment channels
Systems to integrate
- Client lifecycle or onboarding case management
- Core banking account opening
- Corporate portal user and entitlement administration
- Payment channel and host to host setup
- CRM and email for client communication
Complexity: High
Many systems (accounts, portal entitlements, payment channels, CRM) and strict controls on who may grant what. The agent must work through approved interfaces and never bypass segregation of duties.
- 1
Map the journey and the handoffs
Chart every step from approval to first transaction, with owner, system and waiting time, and pick the steps with the most rekeying and waiting.
- 2
Start with document reading and chasing
Automate extraction from mandates and forms and the chasing of missing items first; these save time without touching entitlements.
- 3
Prepare, do not grant
Let the agent prepare setup batches that humans approve under four eyes, and cap them to the approved mandate so it cannot propose rights beyond it.
- 4
Give everyone the same status
Publish one case status to the client, the banker and operations, generated from the case, so nobody chases by email.
Guardrails
- The agent cannot grant access or entitlements beyond the approved mandate
- Four eyes approval on every signatory, user and payment entitlement change
- Segregation of duties between the person who prepares and the person who approves
- Every change is logged with the source document it was based on
KPIs to instrument
- Elapsed days from approval to first transaction
- Operations hours per client setup
- Setup errors found after go live
- Number of document requests per client and time to receive them
Human in the loop
Operations staff approve every setup batch under four eyes before it is applied, and handle any inconsistency the agent flags. The relationship manager owns client communication on sensitive items, and control functions review entitlement changes periodically.
Common failure modes
- Entitlements beyond the mandate
- An extraction error gives a user higher limits than approved. Cap proposals to the mandate and require four eyes on every entitlement.
- Chasing that annoys the client
- Automated reminders repeat or ask for documents already sent. Track what was received and let the banker pause chasing.
- Silent partial setups
- One system is updated and another fails, leaving an inconsistent state. Apply changes as tracked tasks with reconciliation at the end.
What are the risks and rules?
EU AI Act
Limited risk (transparency)
Operational setup of accounts and entitlements for corporate clients is not listed in Annex III and makes no decision about a natural person's access to a service or creditworthiness. The agent chases documents directly with client staff, so Article 50(1) applies: the provider must design the system so that they are informed that they are interacting with an AI system, unless that is obvious from the context. A purely internal version without client contact would be minimal risk.
Rules that apply
Guidance
- Regulation (EU) 2024/1689 (AI Act), Article 50, transparency obligations for providers and deployers of certain AI systems (European Union, Europe). Applies to the conversational chasing of documents with client staff.
- NIST AI Risk Management Framework (NIST, North America). A structure for mapping and managing the risks of an agent that prepares changes in control relevant systems.
Controls to put in place
- Segregation of duties and four eyes approval enforced by the target systems, not by the agent
- Audit trail of every prepared and applied change with its source document
- Periodic entitlement reviews for new clients
- Inventory entry for the agent with its permitted actions
Frequently asked questions
- Can AI grant access to a new corporate client's users?
- It should only prepare the setup. Granting users, signatories and payment entitlements stays behind four eyes approval and segregation of duties, and the agent must not propose rights beyond the approved mandate.
- Where should a bank look first for time savings in corporate onboarding?
- We found no public benchmark that splits onboarding time by step, so map your own journey first. Handoffs between teams, rekeying the same data into several systems and waiting for client documents are the usual candidates to measure; reading mandates automatically and chasing missing items address those steps without touching the approval controls.
- Are there published results?
- We found published results for the wider corporate onboarding journey that this operational setup step sits inside, but not for the step measured on its own. Standard Chartered says machine learning document processing cut average client onboarding time in Corporate and Institutional Banking from 41 to 8 days. Citi says AI enhancements to CitiDirect Commercial Banking, including automated KYC renewals and a digitized onboarding process, have significantly reduced onboarding turnaround times, without giving a figure. Neither source measures the mandate reading, signatory or entitlement setup step by itself, so pilot with document reading and chasing, and measure days from approval to first transaction.
How to cite this page
Blits.ai AI Use Case Library, "AI orchestration of corporate account opening and channel setup", last verified 27 September 2026, https://www.blits.ai/ai-use-cases/corporate-account-onboarding-orchestration. Licensed under CC BY 4.0. Method: how we verify use cases.
Changelog
- 27 September 2026: First published