This article details the proposed document taxonomy, based on Athento's experience and implementation with clients in the banking sector.
Within the taxonomy, we recommend creating teams, spaces, document types and metadata, among others, in the platform.
1. Teams, spaces and types of documents
Initially, the teams must be defined with their respective spaces, in which the type of document or form used for each process will be detailed.
The most relevant and generic ones for Athento are detailed below. This taxonomy is a proposal and each client can adapt it according to the needs of the business and processes.
Teams |
Spaces |
Forms |
Onboarding or opening of products |
|
|
Petitions, requests, complaints or claims |
|
|
Portfolio |
|
|
Insurance |
|
|
Custody of historical documentation |
|
|
Customer |
This folder is part of the single client folder, where the client entity is created. |
|
Employee |
|
|
Legal |
|
|
Each of these document types will depend on the client's detailed request, in Athento it is possible to request these documents and have them classified directly by the platform.
2. Transversal or canonical metadata
Within the platform there must be key metadata that must be in the documents, in such a way that it is transversal and with them you can easily identify the client, process or those characteristics of great relevance to the Bank globally.
The metadata proposed by Athento are:
- Type and identification number
- Type of client: it is the segment or category to which the client belongs: legal, natural, SME, S.A.S. Etc.
- Document creation date: This is an attribute automatically generated by Athento.
- Request/Contract number
- Type of document
- Document Title
- Document ID: Internal name in the manager.
- Document description
- Process ID: corresponds to a process identifier, a code that must specify the process that sends or manages the document. In the banking case it can be the product ID.
- Effective start date
- Effective end date
- Document version: This version is generated automatically, however a specific metadata can be used.
- Company:(Applies in case the Bank has several subsidiaries or related companies).
3. Single customer folder
The main objective of the single client folder is to centralize the relevant information about each client in a single entity. This folder will include essential basic data, such as: name, identification, contact telephone number and e-mail, and other metadata considered relevant for the client's management.
Additionally, the client folder will serve to relate all the documentation filed with the manager by the client, using the type and identification number as the main key. This will ensure that all information is organized and easily accessible, regardless of its location within Athento.
This functionality is realized through the “Create or link files” operation (op_link_or_create_file) available in the automation library.
The document will be linked to an existing file, and in case it does not exist, a new file linked to the document will be created.
Comments
0 comments
Please sign in to leave a comment.