Information processing system and information processing method

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]

[0001] The present disclosure relates to data processing technology, and more particularly to an information processing system and an information processing method. [Background technology]

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

[0003] [Patent Document 1] JP 2016-076096 A Summary of the Invention [Problem to be solved by the invention]

[0004] Among the financial institutions using the above system, there are some that wish to clearly separate back-office operations between multiple management units defined by their own companies. However, even for such financial institutions, payment management processing that works with external payment institutions needs to be executed as processing by a single financial institution.

[0005] The technology disclosed herein has been made in consideration of the above problems, and one objective is to provide a highly convenient service for financial institutions. [Means for solving the problem]

[0006] 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, a payment connection unit that is connected to a payment institution's system and executes processing related to payments, and a conversion unit. The business processing unit processes a plurality of data items to which any of a plurality of category code values ​​corresponding to a plurality of management units defined by the financial institution is set as an independent process for each category code value set in the data, the payment connection unit executes processing related to payments on a financial institution basis, and the conversion unit converts the category code value set in the data sent from the business processing unit to the payment connection unit into a common category code value indicating the financial institution.

[0007] Another aspect of the present disclosure is an information processing method, which includes the steps of: a first processing unit of a computer executing a process related to the business of a financial institution, in which a process of a plurality of data items to which any of a plurality of category code values ​​corresponding to a plurality of management units defined by the financial institution is set is executed as an independent process for each category code value set in each data item; a second processing unit of the computer converting the category code value set in the data output from the first processing unit into a common category code value indicating the financial institution; and a third processing unit of the computer connecting to a system of a settlement institution and executing a process related to settlement on a financial institution basis based on the data to which the common category code value is set.

[0008] Any combination of the above components and any conversion of the expressions of the present disclosure between an apparatus, a computer program, a recording medium storing a computer program, etc. are also valid as aspects of the present disclosure. Effect of the Invention

[0009] According to the technology disclosed herein, it is possible to realize highly convenient services for financial institutions. [Brief description of the drawings]

[0010] [Figure 1]FIG. 2 is a diagram showing a network configuration related to a back office system of an embodiment. [Diagram 2] FIG. 2 is a block diagram showing functional blocks of a back office system according to an embodiment. [Diagram 3] FIG. 13 is a diagram illustrating an example of a conversion rule table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The subject of the device or method in the present disclosure includes a computer. The computer executes a computer program to realize the function of the subject of the device or method in the present disclosure. The computer includes a processor that operates according to a computer program as a main hardware configuration. The type of processor is not important as long as the function can be realized by executing the computer program. The processor is composed of one or more electronic circuits including a semiconductor integrated circuit (IC, LSI, etc.). The computer program is recorded on a non-transitory recording medium such as a computer-readable ROM, an optical disk, or a hard disk drive. The computer program may be stored in the recording medium in advance, or may be supplied to the recording medium via a wide area communication network including the Internet.

[0012] First, an overview of the embodiment will be described. The back office system of the embodiment (back office system 10 described below) is an information processing system that provides ASP services for back office operations to multiple financial institutions (securities companies, banks, etc.). The back office operations are administrative tasks that do not involve direct interaction with customers, and include, for example, contract management, balance management, and document creation.

[0013] Among the financial institutions using the back office system, there are some that wish to clearly separate their back office operations into multiple management units that have been predefined within their own companies (hereinafter also referred to as "specific financial institutions"). Therefore, while the back office system of the embodiment normally assigns one partition (a unit for separating processing) to one company, it assigns multiple partitions corresponding to multiple management units to a specific financial institution, and separates the processing of back office operations related to the specific financial institution for each partition.

[0014] On the other hand, the settlement management process in cooperation with an external settlement institution needs to be consolidated into one partition for a specific financial institution. Therefore, the back office system of the embodiment consolidates data of a specific financial institution across multiple partitions into one partition before executing the settlement management process. This makes it possible to balance the business constraints of financial institutions with the constraints of settlement management, and to provide a highly convenient service for financial institutions.

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

[0016] In the back office system 10, a section for dividing up processing is assigned to each financial institution. Specifically, a section code (in this embodiment, a company code) for implementing the section is set in the data of each financial institution. For example, in the back office system 10, a different company code is assigned to each of securities company A and city bank B, i.e., a company code value indicating securities company A is set in the data of securities company A, and a company code value indicating city bank B is set in the data of city bank B.

[0017] On the other hand, trust bank C in the embodiment is the specified financial institution mentioned above. Trust bank C wishes to clearly separate back office operations for multiple types of accounts as multiple management units (in other words, for each department in charge of each account). Therefore, the back office system 10 assigns multiple company codes to trust bank C to realize multiple partitions corresponding to the multiple types of accounts. In other words, the back office system 10 assigns multiple company code values ​​to trust bank C that correspond to the multiple types of accounts that trust bank C has determined as targets for management in its back office operations.

[0018] In the embodiment, the company code "320" is assigned to the investment account, which is the first account at trust bank C. The investment account is an account related to the company's own asset management and can also be considered a proprietary account. The company code "321" is assigned to the commodity account, which is the second account at trust bank C. The commodity account is an account related to the management of assets held by customers or customer transactions. Since trust bank C needs to manage various system processes and output reports separately between the investment account and the commodity account, they are managed in two sections, company code "320" and company code "321".

[0019] Furthermore, the company code "322" is assigned to the third account at Trust Bank C, the entrusted collateral. The entrusted collateral is an account related to the asset management of customers. Transactions of entrusted collateral are managed in a separate section (company code "322") because there are access restrictions that prohibit them from being viewed by the departments that manage investment accounts and commodity accounts.

[0020] The back office system 10 is connected to an external settlement institution's system (settlement institution system 12). The settlement institution system 12 includes a plurality of settlement institution systems, such as the security system 13, the Bank of Japan system 14, and the SWIFT system 15. The back office system 10 communicates with the security system 13, the Bank of Japan system 14, and the SWIFT system 15 via a communication network 18. The security 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 the Bank of Japan Net. The SWIFT (Society for Worldwide Interbank Financial Telecommunication) system 15 is a network system that transmits messages related to international financial transactions between participating banks using computers and communication lines, and performs processing related to overseas remittances, for example.

[0021] 2 is a block diagram showing the functional blocks of the back office system 10 of the embodiment. Each block shown in the block diagram in this specification can be realized in terms of hardware by elements such as a computer processor, CPU, and memory, electronic circuits, and mechanical devices, and in terms of software by a computer program, etc., but here, the functional blocks realized by the cooperation of these are depicted. Therefore, it will be understood by those skilled in the art that these functional blocks can be realized in various forms by combining hardware and software.

[0022] The back office system 10 includes a management unit 20, a payment connection unit 22, and a data linking unit 24. The functions of the multiple functional blocks included 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 a computer constituting the back office system 10 via a recording medium or a network. The CPU of the computer may perform the functions of the multiple functional blocks by reading the computer program into a main memory and executing it. In addition, the back office system 10 may be realized by one computer, or may be realized by multiple computers working together.

[0023] The settlement connection unit 22 is connected to the settlement institution system 12, and executes settlement-related processing (hereinafter also referred to as "settlement management processing"). The settlement connection unit 22 includes a security connection unit 30, a Bank of Japan connection unit 32, and a SWIFT connection unit 34. The security connection unit 30 is connected to the security system 13, and executes online processing related to the security organization's settlement and transfer operations. 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 counterpart financial institutions. The SWIFT connection unit 34 is connected to the SWIFT system 15, and executes online processing related to overseas remittances. Each of the security connection unit 30, the Bank of Japan connection unit 32, and the SWIFT connection unit 34 sets a unique reference number for each piece of data to be transmitted to the settlement institution system 12.

[0024] The payment connection unit 22 executes payment management processing for each financial institution. For example, the security connection unit 30, the Bank of Japan connection unit 32, and the SWIFT connection unit 34 execute payment management processing for each of securities company A, city bank B, and trust bank C. As described below, the management unit 20 separates and executes processing related to trust bank C into multiple partitions, but the payment connection unit 22 aggregates and executes processing related to trust bank C into a single partition.

[0025] The settlement management process includes reconciliation with the settlement institution system 12 (e.g., matching transaction details, balances, etc.). One company code is set for each financial institution in the data processed by the settlement connection unit 22. The first reason is that reconciliation processes, etc. must be compiled on a financial institution basis. The second reason is that a unique reference number must be set in the data sent to the settlement institution system 12, but if one financial institution uses multiple company codes, there is a possibility that duplication of reference numbers will occur, and the process of preventing such duplication is complicated.

[0026] The management unit 20 executes processing related to the back office operations of the financial institution. The management unit 20 includes a memory unit 40, a business processing unit 42, and a GW (GateWay) unit 44. The memory unit 40 stores data related to multiple financial institutions (e.g., securities company A, city bank B, and trust bank C) that use the back office system 10. The data stored in the memory unit 40 includes contract data for spot transactions, foreign exchange transactions, derivative transactions, and the like.

[0027] Data stored in memory unit 40 is usually set with one company code assigned to the financial institution (e.g., securities company A or city bank B) that generated the data. However, data for a specific financial institution (trust bank C in this embodiment) is set with one of multiple company code values ​​corresponding to multiple management units defined by the specific financial institution. In other words, memory unit 40 stores multiple pieces of data, in which one of multiple company code values ​​corresponding to multiple management units in the specific financial institution is set, as data for the specific financial institution.

[0028] The business processing unit 42 reads out a plurality of data stored in the memory unit 40. The business processing unit 42 executes back-office business processing for each financial institution according to the company code value set for each of the read out plurality of data. For example, the business processing unit 42 executes processing such as contract management, balance management, and document creation for each set of data for which the same company code is set. The processing contents of the business processing unit 42 may differ for each financial institution, i.e., for each company code.

[0029] The business processing unit 42 processes a plurality of data sets to which any of a plurality of company code values ​​corresponding to a plurality of management units defined in a specific financial institution is set, as an independent process for each company code value set in each data set. That is, the business processing unit 42 executes an independent (in other words, separated) business process for each financial institution, and for a specific financial institution, executes an independent business process for each management unit in the specific financial institution.

[0030] The GW unit 44 provides a gateway function for data output from the management unit 20 to the outside, or data input from the outside to the management unit 20. As a conversion unit, the GW unit 44 converts a company code value (i.e., any one of multiple company code values ​​assigned to a specific financial institution) set in data of a specific financial institution sent (output) from the management unit 20 to the payment connection unit 22 into a common company code value indicating the specific financial institution, according to a predetermined conversion rule. The GW unit 44 also converts a common company code value indicating a specific financial institution set in data sent (input) from the payment connection unit 22 to the management unit 20 into any one of multiple company code values ​​assigned to the specific financial institution, according to a predetermined conversion rule.

[0031] The data linking unit 24 relays data transmitted and received between multiple functional blocks in 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.

[0032] The operation of the back office system 10 configured as above will be explained. Here, the operation related to the processing of data of a specific financial institution (trust bank C) will be explained with reference to Fig. 2. As mentioned above, trust bank C is assigned multiple company code values ​​(320, 321, 322) corresponding to multiple types of accounts.

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

[0034] For example, the business processing unit 42 classifies a plurality of contract data of trust bank C by company code, and executes contract management processing and report creation processing for each company code. The business processing unit 42 also performs access control to a plurality of contract data of trust bank C using the company code. For example, when the business processing unit 42 receives a request to refer to contract data from a terminal of a specific department of trust bank C, it allows the referencing of contract data set with a company code previously associated with that department, while prohibiting the referencing of contract data set with other company codes. As a result, as shown in FIG. 2, partition 320 (company code 320), partition 321 (company code 321), and partition 322 (company code 322) are constructed as mutually independent logical partitions in the processing of trust bank C.

[0035] Among 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 data of trust bank C for which settlement management processing is to be performed (referred to as "settlement data") to the GW unit 44 of the management unit 20. The GW unit 44 refers to a pre-stored conversion rule table that defines the 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 value indicating trust bank C. In the embodiment, the common company code value indicating trust bank C is "320" for investment accounts. As a variant, the common company code value indicating trust bank C may be a value different from the multiple company code values ​​(320, 321, 322) assigned to multiple types of accounts.

[0036] 3 shows an example of a conversion rule table. The transmission / reception direction indicates the direction in which data flows. The transmission / reception direction "transmission" indicates data transmitted from the back office system 10 to the settlement institution, i.e., data input from the business processing unit 42 to the GW unit 44. The transmission / reception direction "reception" indicates data transmitted from the settlement institution to the back office system 10, i.e., data input from the data linking unit 24 (payment connection unit 22) to the GW unit 44.

[0037] The original company code is the value of the company code set in the data input to the GW unit 44. The transaction code indicates the value of the transaction code set in the data input to the GW unit 44. The allocation item is an item used for allocating company codes, and in this embodiment is a department / branch code or a reference number. The condition code indicates the value of the allocation item. The destination company code is the value of the company code to which the data is converted, in other words, the company code that should be set in the data output from the GW unit 44.

[0038] The combination of transaction code, branch code, and reference number in the conversion rules determines the conversion conditions for the company code. The conversion conditions for a record with an original company code of 320 and a destination company code of 321 are set to specify that the data is of account type "product account." In addition, the conversion conditions for a record with an original company code of 320 and a destination company code of 322 are set to specify that the data is of account type "entrusted collateral." As shown in Figure 3, the conversion rule table may contain multiple records that have the same combination of original company code and destination company code values ​​but different conversion conditions (for example, the record in the first row and the record in the third row).

[0039] When payment data is input from the business processing unit 42, the GW unit 44 refers to the record of the sending / receiving direction "send" in the conversion rule table (for example, the bottom two records in FIG. 3). 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 changes the company code value set in the payment data to 320. 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 linkage unit 24.

[0040] 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 transmits the input payment data to the payment connection unit 22 via the data linkage unit 24 without changing the company code. In this way, the GW unit 44 aggregates the company codes of the payment data to be transmitted to the payment connection unit 22 to 320.

[0041] The data linking unit 24 accepts payment data output from the GW unit 44 of the management unit 20, and when the destination indicated by the payment data is the security system 13, transfers the payment data to the security connection unit 30. When the destination indicated by the payment data output from the GW unit 44 is the Bank of Japan system 14, the data linking unit 24 transfers the payment data to the Bank of Japan connection unit 32. When the destination indicated by the payment data output from the GW unit 44 is the SWIFT system 15, the data linking unit 24 transfers the payment data to the SWIFT connection unit 34.

[0042] The security connection unit 30 executes a payment management process for each trust bank C, including linkage with the security system 13, based on the payment data (company code is 320) received from the data linkage unit 24. The security connection unit 30 transmits payment result data (company code is 320) indicating the payment result in the security system 13 to the management unit 20 via the data linkage unit 24.

[0043] 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 24. 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.

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

[0045] The data linking unit 24 accepts the payment result data output from the security connection unit 30, the Bank of Japan connection unit 32, and the SWIFT connection unit 34, and transfers the payment 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 linking unit 24 is 320, and in the payment connection unit 22 and the data linking unit 24, a section 320 is constructed.

[0046] The GW unit 44 refers to the conversion rule table shown in Fig. 3 and converts the company code of the payment result data input from the data linking unit 24. Specifically, when payment result data is input from the data linking unit 24, the GW unit 44 refers to records of the sending / receiving direction "receive" in the conversion rule table (for example, the top four records in Fig. 3).

[0047] If the original company code value of the payment result data is 320, the transaction code value is R0001, and the branch code is 20, the GW unit 44 changes the company code value set in the payment result data from 320 to 321. Also, if the original company code value of the payment 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 payment result data from 320 to 321. The GW unit 44 passes the payment result data with the company code value changed to 321 to the business processing unit 42. The business processing unit 42 stores the payment result data in the memory unit 40 and continues the back office processing of section 321 (product account).

[0048] If the original company code value of the payment result data is 320, the transaction code value is R0001, and the branch code is 30, the GW unit 44 changes the company code value set in the payment result data from 320 to 322. Also, if the original company code value of the payment 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 payment result data from 320 to 322. The GW unit 44 passes the payment result data with the company code value changed to 322 to the business processing unit 42. The business processing unit 42 stores the payment result data in the memory unit 40 and continues the back-office processing of section 322 (entrusted collateral).

[0049] If the transaction code, department / branch code, and reference number values ​​of the payment result data do not match the conditions in the conversion rule table, the GW unit 44 passes the entered payment result data to the business processing unit 42 without changing the company code. The business processing unit 42 stores the payment result data in the memory unit 40 and continues back-office processing of the section 320 (investment account).

[0050] According to the back office system 10 of the embodiment, back office operations are performed in different partitions for multiple management targets (e.g., multiple types of accounts) defined by the user's financial institution, while the data of a single financial institution across multiple partitions is consolidated into one partition and settlement management processing is performed. This makes it possible to balance the financial institution's operational constraints and settlement management constraints, and to realize a highly convenient service for the financial institution.

[0051] In addition, according to the back office system 10 of the embodiment, if the number of management units in a financial institution using the back office system 10 increases, in other words, if the number of company codes assigned to the financial institution (i.e., the number of sections) increases, this can be easily accommodated by editing the conversion rule table stored in the GW unit 44.

[0052] For example, consider the case where a new company code "323" corresponding to a new type of account is added. In this case, at least one record is added to the conversion rule table for converting data sent to the settlement institution, with a transmission / reception direction of "send", an original company code of "323", and a destination company code of "320". Also, at least one record is added to the conversion rule table for converting data received from the settlement institution, with a transmission / reception direction of "receive", an original company code of "320", and a destination company code of "323".

[0053] The present disclosure has been described above based on examples. The contents described in the examples are merely examples, and it will be understood by those skilled in the art that various modifications are possible in the combination of components and processing steps, and that such modifications are also within the scope of the present disclosure.

[0054] Any combination of the above-mentioned 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 of the combined examples and modifications. In addition, it will be understood by those skilled in the art that the functions to be performed by each component described in the claims can be realized by each component shown in the examples and modifications alone or in cooperation with each other. [Explanation of symbols]

[0055] 10 back office system, 12 payment institution system, 20 management unit, 22 payment connection unit, 24 data linkage unit, 40 memory unit, 42 business processing unit, 44 GW unit.

Claims

1. a business processing unit that executes processing related to the business of the financial institution; a payment connection unit that is connected to a payment institution's system and executes processing related to payment; A conversion unit; Equipped with The business processing unit processes a plurality of data items to which any one of a plurality of classification code values ​​corresponding to a plurality of management units defined by the financial institution is set as an independent process for each classification code value set for each data item; The payment connection unit executes a process related to the payment on a per-financial institution basis, The conversion unit converts a 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.

2. 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 .

3. The plurality of category code values ​​correspond to a plurality of types of accounts as the plurality of management units.

3. The information processing system according to claim 1 or 2.

4. A step in which a first processing unit of the computer executes processing related to the business of the financial institution, in which processing of a plurality of data items to which any of a plurality of category code values ​​corresponding to a plurality of management units defined by the financial institution is set is executed as an independent process for each category code value set for each data item; A step in which a second processing unit of the computer converts a classification code value set in the data output from the first processing unit into a common classification code value indicating the financial institution; a third processing unit of the computer connecting to a payment institution's system and executing a process related to payment for each financial institution based on the data to which the common classification code value is set; An information processing method comprising:

Images