JP2023009842A - Information processing system and information processing method - Google Patents

Abstract

To provide an information processing system capable of realizing highly convenient services to a financial institution.SOLUTION: A storage unit 40 stores multiple data for which one of multiple company coded values corresponding to multiple management units defined in a financial institution is set. A business processing unit 42 executes the multiple data processing stored in the storage unit 40 for each classification coded value set for each data as an independent process. A settlement connecting unit 22 is connected to the system of a settlement institution and executes the processing related to the settlement in the unit of the financial institution. A GW unit 44 converts the company coded value set in the data transmitted from the business processing unit 42 to the settlement connecting unit 22, to a common company coded value indicating the financial institution.SELECTED DRAWING: Figure 2

Description

TECHNICAL FIELD The present disclosure relates to data processing technology, and more particularly to an information processing system and information processing method.

The present applicant has proposed a system that provides back-office operations of financial institutions as shared-use ASP (Application Service Provider) services (see, for example, Patent Document 1).

JP 2016-076096 A

Among financial institutions using the above system, there are financial institutions that desire to clearly separate back-office operations among a plurality of management units determined by the company. On the other hand, even in such a financial institution, it is necessary to execute the processing of payment management in cooperation with an external payment institution as the processing of a single financial institution.

The technology of the present disclosure has been made in view of the above problems, and one purpose thereof is to realize highly convenient services for financial institutions.

In order to solve the above problems, an information processing system according to one aspect of the present disclosure includes a business processing unit that executes processing related to the business of a financial institution; and a conversion unit. The business processing unit independently processes a plurality of data for which one of a plurality of classification code values corresponding to a plurality of management units defined in a financial institution is set for each classification code value set for each data. The settlement connection unit executes settlement-related processing for each financial institution, and the conversion unit converts the classification code value set in the data sent from the business processing unit to the settlement connection unit to the financial institution. to the common classification code value shown.

Another aspect of the present disclosure is an information processing method. This method comprises a step in which a first processing unit of a computer executes processing related to business of a financial institution, wherein one of a plurality of classification code values corresponding to a plurality of management units defined in the financial institution is set. a step of executing the processing of the plurality of data obtained as independent processing for each classification code value set to each data; a step of converting the obtained division code value into a common division code value indicating the financial institution; and executing processing related to settlement on a financial institution basis.

It should be noted that any combination of the above constituent elements and expressions of the present disclosure converted between devices, computer programs, recording media storing computer programs, etc. are also effective as aspects of the present disclosure.

According to the technology of the present disclosure, highly convenient services for financial institutions can be realized.

It is a figure which shows the network configuration regarding the back-office system of an Example. 2 is a block diagram showing functional blocks of the back office system of the embodiment; FIG. FIG. 10 is a diagram showing an example of a conversion rule table; FIG.

The apparatus or method subject of the present disclosure comprises a computer. The main functions of the apparatus or method of the present disclosure are realized by the computer executing the computer program. A computer has a processor that operates according to a computer program as a main hardware configuration. Any type of processor can be used as long as it can implement functions by executing a computer program. A processor is composed of one or more electronic circuits including a semiconductor integrated circuit (IC, LSI, etc.). A computer program is recorded in a non-temporary recording medium such as a computer-readable ROM, optical disk, hard disk drive, or the like. The computer program may be pre-stored in a recording medium, or may be supplied to the recording medium via a wide area network including the Internet.

First, an outline of the embodiment will be described. A back-office system (back-office system 10 to be described later) of the embodiment is an information processing system that provides ASP services for back-office operations to a plurality of financial institutions (securities companies, banks, etc.). Back-office operations are clerical operations that do not involve direct interaction with customers, and include, for example, contract management, balance management, and form creation.

Among the financial institutions that use back-office systems, there are financial institutions (hereinafter also referred to as "specified financial institutions") that have a desire to clearly separate back-office operations into multiple management units predetermined by the company. be. For this reason, the back office system of the embodiment normally allocates one section (a unit for separating processing) to one company, but allocates a plurality of sections corresponding to a plurality of management units to a specific financial institution. Separating the processing of office operations by zone.

On the other hand, it is necessary to consolidate payment management processing in cooperation with external payment institutions into one section even for specific financial institutions. Therefore, the back-office system of the embodiment executes settlement management processing after aggregating data of a specific financial institution over a plurality of sections into one section. As a result, it is possible to achieve both business restrictions and payment management restrictions of financial institutions, and to realize highly convenient services for financial institutions.

FIG. 1 is a diagram showing a network configuration regarding the back office system 10 of the embodiment. The back office system 10 is connected to a plurality of financial institution systems (financial institution system 11a, financial institution system 11b, and financial institution system 11c) via a communication network 18 that may include LAN, WAN, Internet, and the like. Systems of a plurality of financial institutions include securities company A's financial institution system 11a, city bank B's financial institution system 11b, and trust bank C's financial institution system 11c. Each of the financial institution systems 11a to 11c executes processing related to front office operations or middle office operations of each financial institution.

In the back-office system 10, partitions are allocated for partitioning processing for each financial institution. Specifically, a division code (company code in the embodiment) for realizing division is set in the data of each financial institution. For example, in the back-office system 10, each of securities company A and city bank B is given a different company code. A company code value indicating city bank B is set in bank B data.

On the other hand, the trust bank C of the embodiment is the above specified financial institution. Trust Bank C has a desire to clearly divide back-office operations for each of multiple types of accounts as multiple management units (in other words, for each department in charge of each account). Therefore, in the back office system 10, a plurality of company codes are assigned to the trust bank C for realizing a plurality of divisions corresponding to a plurality of types of accounts. In other words, in the back-office system 10, the trust bank C is assigned a plurality of company code values corresponding to a plurality of types of accounts that the trust bank C determines to be managed in back-office operations.

In the example, the first account at trust bank C, the investment account, is assigned a company code of "320." The investment account is an account related to asset management of the company, and can also be said to be a proprietary account. Also, the company code "321" is assigned to the commodity account, which is the second account in the trust bank C. The product account is an account related to customer asset management or customer transactions. At Trust Bank C, since it is necessary to separately manage various system processes and output forms between investment accounts and commodity accounts, they are managed in two sections, company code "320" and company code "321".

Furthermore, the company code "322" is assigned to the entrusted collateral, which is the third account in Trust Bank C. Entrusted collateral is an account related to client asset management. Transactions of entrusted collateral are managed in a separate section (company code "322") because there is an access restriction that departments managing investment accounts and commodity accounts cannot refer to them.

The back office system 10 is connected to an external settlement system (settlement system 12). The settlement institution system 12 includes a JASDEC system 13, a Bank of Japan system 14, and a SWIFT system 15 as systems of a plurality of settlement institutions. The back office system 10 communicates with the vibration control system 13 , the Bank of Japan system 14 , and the SWIFT system 15 via a communication network 18 . JASDEC system 13 is a system of the Japan Securities Depository Center. The Bank of Japan system 14 is a system of the Bank of Japan, and is also called Bank of Japan Net. A SWIFT (Society for Worldwide Interbank Financial Telecommunication) system 15 is a network system that transmits messages regarding international financial transactions between participating banks using computers and communication lines, and performs processing regarding overseas remittances, for example.

FIG. 2 is a block diagram showing functional blocks of the back office system 10 of the embodiment. Each block shown in the block diagrams of this specification can be implemented by computer processors, CPUs, memory and other elements, electronic circuits, and mechanical devices in terms of hardware, and can be implemented by computer programs and the like in terms of software. However, here, the functional blocks realized by their cooperation are drawn. Therefore, those skilled in the art will understand that these functional blocks can be realized in various ways by combining hardware and software.

The back office system 10 includes a management section 20, a payment connection section 22, and a data linkage section 24. The functions of the functional blocks provided in the back office system 10 may be implemented in a computer program. For example, the management unit 20, the payment connection unit 22, and the data linking unit 24 may be implemented as application software independent of each other. This computer program may be installed in the storage of the computer that constitutes the back office system 10 via a recording medium or network. The CPU of the computer may display the functions of the plurality of functional blocks by reading the computer program into the main memory and executing it. Also, the back office system 10 may be realized by one computer, or may be realized by cooperation of a plurality of computers.

The payment connection unit 22 is connected to the payment institution system 12 and executes processing related to payment (hereinafter also referred to as “payment management processing”). The settlement connection unit 22 includes a JASDEC connection unit 30 , a Bank of Japan connection unit 32 , and a SWIFT connection unit 34 . The JASDEC connection unit 30 is connected to the JASDEC system 13 and executes online processing related to the settlement transfer business of JASDEC. The Bank of Japan connection unit 32 is connected to the Bank of Japan system 14 and executes online processing related to the settlement of funds and government bonds between the Bank of Japan and its counterparty financial institutions. The SWIFT connection unit 34 is connected to the SWIFT system 15 and executes online processing related to overseas remittance. Each of the JASDEC connection unit 30, the Bank of Japan connection unit 32, and the SWIFT connection unit 34 sets a unique reference number for each data to be transmitted to the settlement system 12. FIG.

The payment connection unit 22 executes payment management processing for each financial institution. For example, the JASDEC connection unit 30, the Bank of Japan connection unit 32, and the SWIFT connection unit 34 each execute settlement management processing for securities company A, city bank B, and trust bank C, respectively. As will be described later, the management unit 20 separates the processing for the trust bank C into a plurality of sections and executes them, but the settlement connection unit 22 aggregates the processing for the trust bank C into one section and executes them.

Settlement management processing includes reconciliation processing with the settlement system 12 (for example, verification of transaction details, balances, etc.). One company code is set for each financial institution in the data processed by the payment connection unit 22 . The first reason is that the reconciliation process and the like must be consolidated for each financial institution. The second reason is that although it is necessary to set a unique reference number for the data sent to the settlement institution system 12, if one financial institution uses multiple company codes, there is a possibility of duplication of reference numbers. This is because the processing for preventing duplication is complicated.

The management unit 20 executes processing related to back-office operations of financial institutions. The management unit 20 includes a storage unit 40 , a business processing unit 42 and a GW (GateWay) unit 44 . The storage unit 40 stores data relating to a plurality of financial institutions (for example, securities company A, city bank B, and trust bank C) that use the back office system 10 . The data stored in the storage unit 40 includes agreement data such as spot transactions, exchange transactions, derivative transactions, and the like.

Data stored in the storage unit 40 is usually set with one company code assigned to the financial institution (for example, securities company A or city bank B) that is the source of the data. However, in the data of a specific financial institution (trust bank C in this embodiment), one of a plurality of company code values corresponding to a plurality of management units determined by the specific financial institution is set. That is, the storage unit 40 stores a plurality of data in which any one of a plurality of company code values corresponding to a plurality of management units in a specific financial institution is set as the data of the specific financial institution.

The business processing unit 42 reads a plurality of data stored in the storage unit 40 . The business processing unit 42 executes back-office business processing of each financial institution in accordance with the company code value set in each of the plurality of read data. For example, the business processing unit 42 executes processing such as contract management, balance management, and form creation for each set of data set with the same company code. The processing contents of the business processing unit 42 may differ for each financial institution, that is, for each company code.

The business processing unit 42 processes a plurality of data in which any one of a plurality of company code values corresponding to a plurality of management units determined by a specific financial institution is set, for each company code value set in each data. Run as an independent process. That is, the business processing unit 42 executes independent (in other words, divided) business processing for each financial institution, and for specific financial institutions, independent business processing for each management unit in the specific financial institution.

The GW unit 44 provides a gateway function for data output from the management unit 20 to the outside or data input to the management unit 20 from the outside. The GW unit 44, as a conversion unit, converts the company code value (i.e., the value assigned to the specific financial institution) set to the data of the specific financial institution transmitted (output) from the management unit 20 to the payment connection unit 22 according to a predetermined conversion rule. (one of the multiple company code values provided) to a common company code value that indicates a specific financial institution. In addition, the GW unit 44 transfers the common company code value indicating the specific financial institution set in the data transmitted (input) from the payment connection unit 22 to the management unit 20 according to a predetermined conversion rule to the specific financial institution. Convert to one of several assigned company code values.

The data linkage unit 24 relays data transmitted and received between multiple functional blocks within the back office system 10 . For example, the data linking unit 24 relays data transmitted from the management unit 20 to the payment connection unit 22 and data transmitted from the payment connection unit 22 to the management unit 20 .

The operation of the back office system 10 configured as above will be described. Here, with reference to FIG. 2, operations related to data processing of a specific financial institution (trust bank C) will be described. As described above, trust bank C is assigned a plurality of company code values (320, 321, 322) corresponding to a plurality of types of accounts.

The trust bank C system (financial institution system 11c) transmits a plurality of contract data to the back office system 10 via the communication network 18 and registers them. A plurality of agreement data of trust bank C registered from the financial institution system 11c are stored in the storage unit 40 of the back office system 10. FIG. A company code value (one of 320, 321, or 322) corresponding to the account to which the contract data belongs is set to a plurality of contract data of trust bank C stored in the storage unit 40. FIG. The business processing unit 42 executes business processing based on each of the plurality of contract data of the trust bank C stored in the storage unit 40 in a manner corresponding to the company code set for each contract data.

For example, the business processing unit 42 classifies a plurality of contract data of the trust bank C by company code, and executes contract management processing and report creation processing for each company code. Further, the business processing unit 42 performs access control to a plurality of agreement data of the trust bank C using company codes. For example, when the business processing unit 42 receives a contract data reference request from a terminal of a specific department of the trust bank C, the business processing unit 42 permits reference to contract data in which a company code pre-associated with that department is set. , Prohibits referencing contract data for which other company codes are set. As a result, as shown in FIG. 2, division 320 (company code 320), division 321 (company code 321), and division 322 (company code 322) are constructed as mutually independent logical divisions in the processing of trust bank C. .

Of the shaded objects in FIG. 2, objects flowing from left to right indicate payment data, and objects flowing from right to left indicate payment result data.
The business processing unit 42 passes the data of the trust bank C (referred to as “settlement data”) for which settlement management processing is to be performed to the GW unit 44 of the management unit 20 . The GW unit 44 refers to a pre-stored conversion rule table that defines company code conversion rules, and converts the company code value of the settlement data input from the business processing unit 42 into a common company code indicating trust bank C. Convert to value. A common company code value that indicates trust bank C is "320" for investment accounts in the example. As a modification, the common company code value indicating trust bank C may be different from the multiple company code values (320, 321, 322) assigned to multiple types of accounts.

FIG. 3 shows an example of a conversion rule table. The transmission/reception direction indicates the direction in which data flows. The transmission/reception direction “send” indicates data sent from the back office system 10 to the settlement institution, that is, data input from the business processing unit 42 to the GW unit 44 . The transmission/reception direction “receiving” indicates data sent from the settlement institution to the back office system 10 , that is, data input from the data linking unit 24 (settlement connecting unit 22 ) to the GW unit 44 .

The original company code is the value of the company code set in the data input to the GW section 44 . The transaction code indicates the transaction code value set in the data input to the GW unit 44 . The distribution item is an item used for distribution of company codes, and in the embodiment, it is a branch/department code or a reference number. The condition code indicates the value of the sorting item. The destination company code is the value of the company code to be converted, in other words, the company code to be set in the data output from the GW unit 44 .

The combination of the transaction code, department code, and reference number in the conversion rule defines the company code conversion conditions. In the conversion condition of the record with the original company code of 320 and the allocation destination company code of 321, a condition specifying that the data is of the account type "merchandise account" is set. Also, in the conversion condition of the record with the original company code of 320 and the allocation destination company code of 322, a condition specifying that the data is of the account type "entrusted collateral" is set. As shown in FIG. 3, the conversion rule table contains a plurality of records with the same combination of original company code value and allocation destination company code value, but with different conversion conditions (for example, the record in the first row and the record in the first row). 3 rows of records) can be set.

When payment data is input from the business processing unit 42, the GW unit 44 refers to the record of the transmission/reception direction “transmit” in the conversion rule table (for example, the lower two records in FIG. 3). The GW unit 44 changes the company code value set in the payment data to 320 when the original company code value of the payment data is 321 or 322 and the transaction code value is S0001. The GW unit 44 transmits the payment data with the company code value changed to 320 to the payment connection unit 22 via the data linking unit 24 .

If the original company code value of the payment data is not 321 or 322, or if the transaction code value is not S0001, for example, if the original company code of the payment data is 320, the GW unit 44 converts the input payment data to Without changing the company code, it is transmitted to the payment connection unit 22 via the data linking unit 24 as it is. In this way, the GW unit 44 consolidates the company codes of the payment data to be transmitted to the payment connection unit 22 into 320 .

The data linking unit 24 receives payment data output from the GW unit 44 of the management unit 20 , and transfers the payment data to the JASDEC connection unit 30 when the destination indicated by the payment data is the JASDEC system 13 . Further, when the destination indicated by the settlement data output from the GW section 44 is the Bank of Japan system 14 , the data linkage section 24 transfers the settlement data to the Bank of Japan connection section 32 . Further, when the destination indicated by the payment data output from the GW unit 44 is the SWIFT system 15 , the data cooperation unit 24 transfers the payment data to the SWIFT connection unit 34 .

JASDEC connection unit 30 executes payment management processing for each trust bank C, including cooperation with JASDEC system 13, based on the payment data (company code is 320) received from data linking unit . JASDEC connection unit 30 transmits settlement result data (company code is 320) indicating the settlement result in JASDEC system 13 to management unit 20 via data linkage unit 24 .

The Bank of Japan connection unit 32 executes settlement management processing for each trust bank C, including linkage with the Bank of Japan system 14, based on the settlement data (company code is 320) received from the data linkage unit . The Bank of Japan connection unit 32 transmits settlement result data (company code is 320) indicating the settlement result in the Bank of Japan system 14 to the management unit 20 via the data linkage unit 24 .

The SWIFT connection unit 34 executes settlement management processing for each trust bank C, including linkage with the SWIFT system 15, based on the settlement data (company code is 320) received from the data linkage unit 24. FIG. The SWIFT connection unit 34 transmits settlement result data (company code is 320) indicating the settlement result in the SWIFT system 15 to the management unit 20 via the data linkage unit 24 .

The data linkage unit 24 receives settlement result data output from the JASDEC connection unit 30, the BOJ connection unit 32, and the SWIFT connection unit 34, and transfers the settlement result data to the management unit 20 (GW unit 44). The company code set in the data processed by the payment connection unit 22 and the data cooperation unit 24 is 320, and the payment connection unit 22 and the data cooperation unit 24 construct a section 320. FIG.

The GW unit 44 converts the company code of the settlement result data input from the data linking unit 24 by referring to the conversion rule table shown in FIG. Specifically, when the payment result data is input from the data linking unit 24, the GW unit 44 refers to the record of the transmission/reception direction “receiving” in the conversion rule table (for example, the top four records in FIG. 3).

When the original company code value of the settlement result data is 320, the transaction code value is R0001, and the department code is 20, the GW unit 44 changes the company code value set in the settlement result data from 320 to 321. do. Also, when the original company code value of the settlement result data is 320, the transaction code value is R0003, and the reference number is B, the GW unit 44 changes the company code value set in the settlement result data from 320 to 321. change to The GW unit 44 passes the settlement result data with the company code value changed to 321 to the business processing unit 42 . The business processing unit 42 stores the settlement result data in the storage unit 40 and continues the back-office processing of the section 321 (merchandise account).

When the original company code value of the settlement result data is 320, the transaction code value is R0001, and the department code is 30, the GW unit 44 changes the company code value set in the settlement result data from 320 to 322. do. Also, when the original company code value of the settlement result data is 320, the transaction code value is R0003, and the reference number is C, the GW unit 44 changes the company code value set in the settlement result data from 320 to 322. change to The GW section 44 passes the settlement result data with the company code value changed to 322 to the business processing section 42 . The business processing unit 42 stores the settlement result data in the storage unit 40 and continues the back office processing of the section 322 (entrusted collateral).

If the transaction code, department code, and reference number of the payment result data do not match the conditions of the conversion rule table, the GW unit 44 processes the input payment result data as it is without changing the company code. It is passed to the processing unit 42 . The business processing unit 42 stores the settlement result data in the storage unit 40 and continues the back-office processing of the block 320 (investment account).

According to the back-office system 10 of the embodiment, while executing back-office operations in different sections for each of a plurality of management objects (for example, a plurality of types of accounts) determined by the user's financial institution, a single Settlement management processing is executed after collecting data of financial institutions into one section. As a result, it is possible to achieve both business restrictions and payment management restrictions of financial institutions, and to realize highly convenient services for financial institutions.

Further, according to the back-office system 10 of the embodiment, when the number of management units in a financial institution using the back-office system 10 increases, in other words, the number of company codes (that is, the number of sections) assigned to the financial institution increases. Even if it increases, it can be easily dealt with by editing the conversion rule table stored in the GW unit 44 .

For example, consider the case where a new company code "323" corresponding to a new type of account is added. In this case, in the conversion rule table, at least one record is added to the conversion rule table, which is a record for conversion of transmission data to the settlement institution, and has the sending and receiving direction "sending", the original company code "323", and the allocation destination company code "320". be done. In addition, in the conversion rule table, at least one record is added as a record for conversion of data received from the settlement institution, with the transmission direction "receive", the original company code "320", and the allocation destination company code "323". be.

The present disclosure has been described above based on the embodiments. It should be understood by those skilled in the art that the contents described in the examples are illustrative, and that various modifications can be made to combinations of components and treatment processes, and such modifications are also within the scope of the present disclosure.

Any combination of the above-described examples and modifications is also useful as an embodiment of the present disclosure. A new embodiment resulting from the combination has the effects of each combined embodiment and modified example. It should also be understood by those skilled in the art that the functions to be fulfilled by each constituent element described in the claims are realized by each constituent element shown in the embodiments and modified examples singly or in conjunction with each other.

10 back office system 12 settlement institution system 20 management unit 22 settlement connection unit 24 data linkage unit 40 storage unit 42 business processing unit 44 GW unit.

Claims (4)

a business processing unit that executes processing related to the business of a financial institution;
a payment connection unit that is connected to a system of a payment institution and executes processing related to payment;
a conversion unit;
with
The business processing unit processes a plurality of data set with one of a plurality of classification code values corresponding to a plurality of management units determined in the financial institution, for each classification code value set in each data. run as an independent process,
The payment connection unit executes processing related to the payment for each financial institution,
The conversion unit converts the classification code value set in the data transmitted from the business processing unit to the payment connection unit into a common classification code value indicating the financial institution.
Information processing system. The conversion unit converts the common classification code value set in the data transmitted from the payment connection unit to the business processing unit into one of the plurality of classification code values according to a predetermined rule.
The information processing system according to claim 1. The plurality of classification code values correspond to the plurality of types of accounts as the plurality of management units,
The information processing system according to claim 1 or 2. A step in which a first processing unit of a computer executes processing related to operations of a financial institution, wherein a plurality of classification code values set to any of a plurality of division code values corresponding to a plurality of management units determined in the financial institution a step of performing data processing as an independent process for each classification code value set for each data;
a step in which the second processing unit of the computer converts the classification code value set in the data output from the first processing unit into a common classification code value indicating the financial institution;
a step in which the third processing unit of the computer is connected to a system of a settlement institution, and based on the data in which the common classification code value is set, executes processing related to settlement for each financial institution;
An information processing method comprising:

Images