Skip to content

From the first document to account opening, with the application already complete

The new customer uploads the documents from the app or brings them to the branch, and opening stalls every time one is missing or a detail on the form does not match.

One expired document, and the application goes back to the customer

Whether it comes from the app or the branch, the opening request brings with it an identity document and the tax code (codice fiscale) and, for a company, the company registry extract (visura), the articles of association and the beneficial owner's details as well. The onboarding officer checks that they are legible and still valid, compares them with what the customer wrote on the form and copies the data into the customer register in core banking. When something does not add up they write to the customer and wait, while the application sits in the queue, and sometimes after the second request the customer gives up.

The agent guides the customer through the documents, the onboarding officer decides on opening

In the example, the agent reads the documents as soon as the customer uploads them, checks their expiry and their consistency with the form and pre-fills the customer record. If something is missing it tells the customer straight away, in the channel they came through, introducing itself as an AI system and explaining which document is needed. The onboarding officer thus receives a complete application, with the differences already highlighted, and it is for them to verify the outcome of the customer due diligence checks and decide whether to open the account.

  1. The customer asks to open an account from the app or in branch
  2. The agent checks the uploaded documents and pre-fills the customer record
  3. Tells the customer what is missing, introducing itself as an AI system
  4. The onboarding officer checks the application and decides on account opening

Illustrative example

Data, modules and decisions in opening an account

ItemIn this case
DataIn this caseApplication forms, identity and company documents, the customer register in core banking, the list of documents required by type of customer and product
ModulesIn this caseData Foundation, Agents, Workspace
Who decidesIn this caseThe onboarding officer on account opening; whoever is accountable for onboarding on the agent's rules and the wording addressed to the customer
What we measureIn this caseThe time from request to opening, applications abandoned halfway and repeated document requests, against the starting point
AI Act risk classIn this caseThe agent does not assess creditworthiness, the high-risk use in Annex III that concerns banks. If someone applies for a credit facility or a credit card along with the account, that assessment stays outside the case. Because the agent writes to the customer, the customer must know they are dealing with an AI system. We classify the case with risk and compliance before development
Where to startIn this caseWith Deployment on a single channel and a single type of customer, for example individuals opening an account from the app, where the documents required are always the same

If every branch asks for different documents

When the list of documents changes from one branch to the next and is not written down anywhere, the agent does not know what to ask for, so putting it in writing with whoever is accountable for onboarding comes before building. In the same way, if the customer register in core banking already contains the same customer twice, a pre-filled record would add a third, and the first job becomes sorting out the data with Data Foundation.

The checks that follow are in the sheet on customer due diligence, anti-money laundering and fraud, the other cases are in Banking & payments and all the sheets are in the use cases.

Let's follow together an opening request left halfway

At the first meeting we go through an application abandoned by the customer with the onboarding team, to see which document it stalled on.