JP6842491B2 - Customer data maintenance systems, methods and programs - Google Patents

Description

The present invention relates to customer data maintenance systems, methods and programs.

Under the Deposit Insurance Law, it is necessary to determine the deposit amount of the same customer within the same financial institution. The financial institution aggregated and integrated (name identification) its own customer information and submitted the prepared customer data to the Deposit Insurance Corporation of Japan.

The general name identification process is, for example, a method of converting two personal information having at least the same name and address into duplicate personal information, or at least an individual having duplicated two personal information having the same name and telephone number information. A method of using information is known (see Patent Document 1).

Japanese Unexamined Patent Publication No. 2005-11049

Since the submission time of customer data for the Deposit Insurance Corporation of Japan is not fixed, it is necessary to keep the latest and accurate customer data as much as possible, not the customer data based on the customer information at a specific time. Even when customer information is newly registered, there is a possibility that data that is not subject to submission to the Deposit Insurance Corporation of Japan and data that lacks the information required for name identification may be mixed. In addition, it is necessary to appropriately determine whether or not correction is necessary according to the characteristics of customer data. From the above, a system for appropriately preparing customer data for the Deposit Insurance Corporation of Japan is desired.

An object of the present invention is to provide a customer data maintenance system, a method and a program for such a problem. More specifically, it is intended to provide a customer data maintenance system, method and program for the Deposit Insurance Corporation of Japan, in which customer data can be modified via different routes.

The system for preparing customer data for the Deposit Insurance Corporation of Japan, which is one aspect of the present invention, executes name identification on customer information collected from a plurality of business systems, and checks suspicious points on the identified customer information. Execute, divide the check result of the suspicious part check according to the subsequent response method, the divided check result contains information indicating the data item whose contents need to be confirmed, and the customer data according to the divided check result It has a processor configured to accept modifications of.

According to the present invention, it is possible to confirm and modify the contents by different routes according to the characteristics of the items of the customer data for the Deposit Insurance Corporation of Japan. In addition, it is possible to notify the confirmation of the contents of customer data by an alarm at the time of contact with the customer.

It is a figure which illustrates the structure of the customer data maintenance system which concerns on one Embodiment of this invention. It is a figure which illustrates the customer data maintenance processing flow which concerns on one Embodiment of this invention. It is a figure which illustrates the structure of the system which concerns on one Embodiment of this invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In a plurality of drawings, the same reference numerals represent the same elements, and duplicate description will be omitted.

FIG. 1 is a diagram illustrating a configuration of a customer data maintenance system according to an embodiment of the present invention. FIG. 1 schematically illustrates a management information system 100, a customer ID management system 110, a headquarters system 120, a branch office system 130, a core banking system 140, and a network 150.

The management information system 100 is a system for supporting the management of a financial institution, and can aggregate and manage data held by a plurality of business systems. The plurality of business systems include, for example, a financial institution headquarters system 120, a branch office system 130, and a core banking system 140. The management information system 100 can also include a customer ID management system 110.

The customer ID management system 110 can collect customer information including a name, an address, a telephone number, and the like and store it in the customer ID master database 111. The customer ID management system 110 can also perform name identification of customer data at predetermined periods (for example, quarterly). Name identification involves data cleansing and matching as part of the process. Data cleansing unifies the data representation (hyphen, parentheses, etc.) of each item (name, address, telephone number, etc.) of customer information. Matching uses each item (name, address, phone number, etc.) after data cleansing to compare whether multiple customer information indicates the same customer. Name identification can be performed by assigning the same customer ID to the same customer determined by data cleansing and matching.

The customer ID management system 110 can perform a suspicious part check by the suspicious part check unit 112 in order to identify the customer data whose contents need to be confirmed by using the customer information identified by the name. The question check is, for example, whether the customer is not covered by deposit insurance (for example, a financial institution), whether the corporate name or personal name conforms to the prescribed format, the date of establishment of the corporation or the individual. It may include checking whether the date of birth is before the specified period, etc. The check result of the suspicious part check can include information indicating a data item for which content confirmation is required (suspicious) among each item of customer data.

The customer ID management system 110 can divide the check result of the suspicious part check for each subsequent response method. The divided check results can be, for example, a check result (total amount), a check result (alarm format), a check result (for sales office processing), and the like. The divided check result may be a more subdivided or integrated check result, and items may be further extracted or processed. The divided check results are transmitted to one or more business systems, respectively.

The check result (total amount) can be used, for example, by a person in charge at the headquarters of a financial institution to determine whether or not to correct customer data. The check result (total amount) may indicate data items that need to be judged by the headquarters of a financial institution, such as whether or not the customer is not covered by deposit insurance.

The check result (alarm format) can be used as an alarm registration condition indicating a data item whose contents need to be confirmed when a customer is contacted. The contact may include, for example, a customer visiting a window of a financial institution or the like, Internet banking, or logging in to a securities account. The displayed content of the alarm can be used, for example, by a customer or a person in charge of a business office of a financial institution to determine whether or not to correct the customer data. The content to be confirmed by the customer can be, for example, the date of birth, katakana notation, telephone number, or the like.

The check result (processed by the branch office) can be used, for example, by the person in charge of the branch office of the financial institution to determine whether or not to correct the customer data. The check result (for branch office processing) may indicate data items that need to be confirmed, such as seal delivery, among customer data.

Each check result may be displayed on the screen of a terminal or the like used by the person in charge so as to guide the confirmation by each person in charge about the data item whose contents need to be confirmed.

The headquarters system 120 is one of the business systems, and can receive the check result (total amount) and the check result (alarm format) from the customer ID management system 110. A person in charge of the headquarters of a financial institution can check the contents of the check result (total amount) and correct the customer data by using a terminal that can access the headquarters system 120. The alarm registration unit 121 can register an alarm to be displayed on a terminal or the like installed in the store based on the check result (alarm format).

The branch office system 130 is one of the business systems, and can receive the check result (processed by the branch office). The person in charge of the branch office of the financial institution can check the contents of the check result (processed by the branch office) and correct the customer data by using the terminal that can access the branch office system 130.

The alarm display unit 131 can display the alarm registered by the alarm registration unit 121 of the headquarters system 120. The alarm may be displayed on a terminal installed at the store, for example, when the customer visits the store (when the customer is identified at a counter or the like). The alarm may also be displayed on the ATM when the customer operates an ATM (Automated Teller Machine) installed in a store such as a financial institution or a convenience store. The alarm may also be displayed on the terminal of the person in charge of the call center when the customer makes an inquiry to the call center for any matter, and the person in charge of the call center corrects / confirms the data to the customer based on the displayed contents of the alarm. May be urged. The customer checks the display of the alarm and determines whether correction is necessary. The person in charge of the branch office of the financial institution can modify the customer data by using the terminal that can access the branch office system 130 according to the judgment of the customer. Customer data may be modified by the customer. The alarm may also be displayed on the customer's terminal, such as when the customer logs in to Internet banking or a securities account, or when the screen transitions to a predetermined screen. The customer can check the displayed contents of the alarm and correct the customer data.

If, as a result of each of the above-mentioned content confirmations, correction is not necessary, for example, a flag indicating "confirmed" may be included in the customer data so that the content confirmation is not determined to be necessary in the next and subsequent suspicious part checks.

The accounting system 140 is one of the business systems, and can store the modified customer data in the customer information database 141 and transmit the customer data to the management information system 100 as needed.

The network 150 can be a well-known network capable of intercommunication between the management information system 100 and the business system (including the headquarters system 120, the branch office system 130, and the accounting system 140), and is particularly limited. There is no.

FIG. 2 is a diagram illustrating a customer data maintenance processing flow according to an embodiment of the present invention. In the following, we will explain the situation where name identification is performed at predetermined intervals and customer data for the Deposit Insurance Corporation of Japan is prepared.

Step S201: The customer ID management system 110 collects customer information including a name, an address, a telephone number, and the like and stores it in the customer ID master database 111. The customer ID management system 110 executes name identification of customer information at predetermined period (for example, quarterly).

Step S202: The customer ID management system 110 uses the identified customer information to perform a questionable spot check to identify customer information whose contents need to be confirmed. The check result of the suspicious part check includes information indicating a data item for which content confirmation is required (suspicious) among each item of customer data.

Step S203: The customer ID management system 110 divides the check result of the suspicious part check into each subsequent response method. The divided check results can be, for example, a check result (total amount), a check result (alarm format), a check result (for branch processing), and the like, and are transmitted to one or more business systems. The check result (alarm format) can be used as an alarm registration condition indicating a data item whose contents need to be confirmed when a customer is contacted. For example, the alarm is registered by the alarm registration unit 121 of the headquarters system 120.

Step S204: The person in charge or the like who can access the business system confirms the contents of the divided check results and corrects the customer data as necessary. For example, a person in charge of the headquarters of a financial institution can check the contents of the check result (total amount) and correct the customer data by using a terminal that can access the headquarters system 120. For example, a person in charge of a branch office of a financial institution can check the contents of the check result (processed by the branch office) and correct the customer data by using a terminal that can access the branch office system 130. .. For example, a person in charge of a branch office of a financial institution can access the branch office system 130 according to the customer checking the display contents of the alarm displayed on the terminal installed in the store and determining whether or not correction is necessary. Customer data can be modified using a flexible terminal. Customer data may be modified by the customer. In this way, customer data can be modified separately via a plurality of business systems.

Step S205: Core banking system 140 stores the modified customer data in the customer information database 141.

By doing so, it is possible to confirm and correct the contents by different routes according to the characteristics of the items of the customer data for the Deposit Insurance Corporation of Japan. In addition, it is possible to notify the content confirmation by an alarm at the time of contacting the customer of the customer data.

FIG. 3 is a diagram illustrating a configuration of a system according to an embodiment of the present invention. As illustrated in FIG. 3, the control unit 301, the main storage unit 302, the auxiliary storage unit 303, the operation unit 304, the IF unit 305, and the display unit 306 are connected by a bus 307 or the like. FIG. 3 illustrates a general-purpose configuration of the management information system 100, the headquarters system 120, the branch office system 130, and the accounting system 140.

The control unit 301 is a central processing unit (CPU), and can control each component of the business system and calculate data. The main storage unit 302 is a main memory, and can store various input data, computer-executable instructions, data after arithmetic processing by the instructions, and the like. The auxiliary storage unit 303 is a storage device such as a hard disk (HDD), and is used when storing data and programs for a long period of time. The control unit 301 can read the program stored in the auxiliary storage unit 303 into the main storage unit 302 and execute the program.

The operation unit 304 is composed of a keyboard, a mouse, a touch panel, and the like, and can receive various operations and input data of the application. The IF unit 305 is an interface for transmitting / receiving data to / from another system or device. The display unit 306 is composed of a display or the like, and can provide various screens or the like of an application.

Although each process is described separately for the sake of explanation, it may be implemented so that each process is integrated and linked, and a part or all of the processes possessed by each is performed by the other.

Although the principle of the present invention has been described above with reference to the exemplary embodiments, it is possible to realize various embodiments in which the configuration and details are changed without departing from the gist of the present invention. That is, the present invention can adopt, for example, an embodiment as a system, an apparatus, a method, a program, a storage medium, or the like.

100 Management information system 110 Customer ID management system 111 Customer ID master database 112 Suspicious part check department 120 Headquarters system 121 Alarm registration department 130 Branch office system 131 Alarm display unit 140 Accounting system 141 Customer information database 150 Network

Claims (5)

It is a system that prepares customer data for the Deposit Insurance Corporation of Japan.
Perform name identification on customer data collected from multiple business systems
For the customer data that has been identified, perform a questionable part check to identify data items that need to be confirmed by the customer or the person in charge.
The check result of the questionable part check is divided for each subsequent response method, and the divided check result includes the first check result and the second check result, and the first check result and the second check result Each check result contains information indicating data items whose contents need to be confirmed.
In response to a first corresponding method associated with said first check result, the reception correction of customer data, in accordance with the second corresponding method associated with said second check result, a modification of the customer data with a processor configured Ru accepted system. Based on the first check result, an alarm indicating a data item for which confirmation of the content is required when the customer's contact occurs is registered.
The alarm is displayed on the terminal associated with the first response method.
The system of claim 1, further comprising a processor further configured to accept modification of the customer data by the customer in response to the display. A method of organizing customer data for the Deposit Insurance Corporation of Japan, which is carried out by a computer.
Performing name identification on customer data collected from multiple business systems,
Performing a suspicious part check to identify data items that need to be confirmed by the customer or the person in charge for the customer data that has been identified.
The check result of the questionable part check is divided for each subsequent response method, and the divided check result includes the first check result and the second check result, and the first check result and the first check result Each of the second check results is divided and divided, which includes information indicating a data item whose contents need to be confirmed.
In response to a first corresponding method associated with said first check result, the reception correction of customer data, in accordance with the second corresponding method associated with said second check result, a modification of the customer data acceptance and a Rukoto, method. Based on the first check result, registering an alarm indicating a data item for which confirmation of the content is required when the customer's contact occurs , and
Displaying the alarm on the terminal associated with the first response method
The method of claim 3, further comprising accepting the customer to modify the customer data in response to the display. A program for causing a computer to execute the method according to claim 3 or 4.

Images