Information processing systems, information processing methods, and computer programs

Abstract

To achieve a mechanism for enabling a user to easily change user's setting information to each of a plurality of organizations.SOLUTION: An impact PF 22 includes a first storage part for storing a plurality of user's IDs determined by a system of a plurality of organizations, and a second storage part for storing user's setting information to each of the plurality of organizations. The impact PF 22 associates a common ID allocated to the user with a plurality of IDs of the user stored in the first storage part. The impact PF 22 displays a screen which is browsable by using a common ID and is a portal screen being a screen showing the user's setting information to each of the plurality of organizations in a customer terminal 12. The impact PF 22 reflects change in the second storage part in the case that the user's setting information to a certain organization is changed on the portal screen.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] The following Patent Document 1 proposes a specific fund designated allocation system in which an investment trust for donation is set in advance, a customer who wishes to make a donation is caused to purchase the investment trust, and the investment earnings of the investment trust are donated to a specific donation recipient. [Prior Art Documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2009-48241 [Summary of the Invention] [Problem to be Solved by the Invention]

[0004] In order to promote donations starting from dividends and the like, it is desirable that a donor can easily change donation modes set by the user at a plurality of financial institutions and the like. One object of the present disclosure is to implement a mechanism that allows a user to easily change user setting information for each of a plurality of organizations. [Means for Solving the Problem]

[0005] To solve the above problems, an information processing system in one aspect of the present disclosure includes: a first storage unit that stores multiple user IDs defined in the systems of multiple organizations; a second storage unit that stores user setting information for each of the multiple organizations; an execution unit that performs processing for each organization's system based on the user setting information stored in the second storage unit, using the user ID defined in each organization's system; an association unit that associates a common ID assigned to a user with the multiple user IDs stored in the first storage unit; a presentation unit that presents a screen viewable using the common ID and showing the user setting information for each of the multiple organizations to the user; and a change unit that, when the user setting information for a certain organization is changed on the screen, reflects that change in the second storage unit.

[0006] Another aspect of this disclosure is an information processing method. This method comprises a computer having a first storage unit that stores multiple user IDs defined in the systems of multiple organizations, and a second storage unit that stores user configuration information for each of the multiple organizations. The computer performs processing on each organization's system based on the user configuration information stored in the second storage unit, using the user ID defined in each organization's system. It associates a common ID assigned to the user with the multiple user IDs stored in the first storage unit, presents the user with a screen viewable using the common ID and showing the user configuration information for each of the multiple organizations, and reflects the change in the second storage unit when the user configuration information for a certain organization is changed on the screen.

[0007] Furthermore, any combination of the above components, as well as any conversion of the expressions of this disclosure between devices, computer programs, recording media storing computer programs, etc., are also valid forms of this disclosure. [Effects of the Invention]

[0008] The technology disclosed herein enables a mechanism that allows users to easily change their settings information for each of multiple organizations. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram showing the configuration of the information processing system according to the embodiment. [Figure 2] Figure 1 is a block diagram showing the functional blocks of the Impact PF. [Figure 3] This diagram shows an example of customer information. [Figure 4] This figure shows an example of donation application information. [Figure 5] This is a flowchart showing the operation of Impact PF. [Figure 6] This is a flowchart showing the operation of Impact PF. [Figure 7] This figure shows an example of a screen for specifying the ID to be integrated. [Figure 8] This diagram shows an example of associating a common ID for a target customer with multiple individual IDs. [Figure 9] This figure shows an example of a portal screen. [Modes for carrying out the invention]

[0010] In this embodiment, we propose a technology that helps users easily change their settings information for each of multiple organizations. Specifically, we propose an impact platform (hereinafter also referred to as "Impact PF") as a system in which this technology is implemented. The Impact PF supports donations funded by user assets managed by multiple business companies. The donations are envisioned to be to general foundations, public interest foundations, NPOs (Nonprofit Organizations), etc., aimed at solving environmental and social issues. In this embodiment, the users are customers of business companies such as financial institutions.

[0011] Figure 1 shows the configuration of the communication system 10 according to the embodiment. The communication system 10 includes a customer terminal 12, securities company equipment 14, securities back office system 16, points program operator equipment 18, bank equipment 20, and impact PF 22. The computers that make up these devices and systems are interconnected via a communication network including LAN, WAN, and the Internet.

[0012] The securities company device 14 is an information processing device that supports the operations of a securities company (in this embodiment, XX Securities). The securities back office system 16 is an information processing system that provides information processing services to the securities company to support securities operations. The securities back office system 16 supports the securities company in ordering and executing financial products, managing balances, managing customers, settlement operations, custody operations, accounting operations, etc. For example, the securities back office system 16 manages financial products held by the securities company's customers and also manages the balances of customer accounts. The securities back office system 16 may be implemented by a single computer or by the cooperation of multiple computers.

[0013] The points program operator device 18 is an information processing device for a company that operates a points program (in this embodiment, YY Points). The points program can also be called a loyalty program. The points program operator device 18 manages the point balances of customers. The banking device 20 is an information processing device that supports the operations of a bank (in this embodiment, ZZ Bank). For example, the banking device 20 manages the financial products held by customers and also manages the balances of customers' accounts.

[0014] The customer terminal 12 is an information processing device operated by customers of securities companies, point program operators, and banks. The customer terminal 12 may be a laptop, tablet, or smartphone. The customer terminal 12 can also be described as a user terminal operated by users of Impact PF22.

[0015] Note that a plurality of customers, a plurality of securities companies, a plurality of point program operating companies, and a plurality of banks may participate in the communication system 10. That is, the communication system 10 may include a plurality of customer terminals 12, a plurality of securities company devices 14, a plurality of point program operating company devices 18, and a plurality of bank devices 20. The securities back-office system 16 may be connected to the plurality of securities company devices 14 and support the operations of the plurality of securities companies.

[0016] The impact PF 22 is an information processing system serving as a donation platform, and supports donations to public welfare foundations and general foundations. Specifically, the impact PF 22 executes information processing for donating at least a part of dividends and the like of financial products held by a customer to a public welfare foundation, a general foundation, or the like, based on the specification by the customer. The financial products held by the customer include securities, for example, stocks, investment trusts, and bonds. Dividends and the like can also be said to be profits obtained by the customer from holding the financial products. For example, dividends and the like include stock dividends, investment trust distributions, and bond interest. The impact PF 22 may be implemented by a single computer, or may be implemented by cooperation of a plurality of computers.

[0017] In the communication system 10 of the embodiment, a donation application is initially made in a B (impact PF 22) to B (each operating company) to C (customer terminal 12) manner, in other words, the donation application is made via each operator. In the communication system 10, the donation application is switched to a B (impact PF 22) to C (customer terminal 12) manner in accordance with the customer's consent.

[0018] Figure 2 is a block diagram showing functional blocks of the impact PF22 of Figure 1. In terms of hardware, each block shown in the block diagrams of the present specification can be implemented by elements such as a computer processor, CPU, memory, electronic circuits, and mechanical devices, and in terms of software, it is implemented by a computer program or the like. Here, functional blocks implemented through the cooperation of these components are illustrated. Therefore, it should be understood by those skilled in the art that these functional blocks can be implemented in various forms by a combination of hardware and software.

[0019] The impact PF22 includes a processing unit 30, a storage unit 32, and a communication unit 34. The processing unit 30 executes various types of data processing. The processing unit 30 may be implemented by a CPU of a computer that constitutes the impact PF22. The storage unit 32 stores data to be referenced or updated by the processing unit 30. The storage unit 32 may be implemented by a storage or memory of a computer that constitutes the impact PF22. The communication unit 34 communicates with an external device according to a predetermined communication protocol. The processing unit 30 transmits and receives data to and from the customer terminal 12, the securities back-office system 16, the point program operating company device 18, and the bank device 20 via the communication unit 34.

[0020] The storage unit 32 includes a customer information storage unit 40, a donation application information storage unit 42, and a donation history storage unit 44. As a first storage unit, the customer information storage unit 40 stores a plurality of user IDs defined by a plurality of organizations. As a second storage unit, the donation application information storage unit 42 stores user setting information for each of the plurality of organizations. The customer information storage unit 40 and the donation application information storage unit 42 may be implemented as a single table.

[0021] The customer information storage unit 40 stores basic information about the customer (hereinafter also referred to as "customer information"). Figure 3 shows an example of customer information. Customer information includes business company information, individual ID, name, date of birth, and common ID. The business company is the customer's asset that serves as the source of the donation; in other words, it is the company that manages the customer's asset on which the donation is set up. Business companies include, for example, financial institutions such as securities companies and banks, as well as point program operating companies. Customer assets include, for example, financial products purchased by the customer and points held by the customer.

[0022] Individual IDs are customer IDs defined in the systems or devices of each business company, and are different for each business company and each customer. For example, individual ID "123" is the customer ID defined in the securities company device 14 of XX Securities. Individual ID "456" is the customer ID defined in the point program operating company device 18 of YY Points. Individual ID "789" is the customer ID defined in the banking device 20 of ZZ Bank. A common ID is an ID that combines multiple individual IDs assigned to a customer by multiple business companies, and is a common ID across multiple business companies. In this embodiment, Impact PF22 assigns a common ID to a customer based on the customer's consent.

[0023] Returning to Figure 2, the donation application information storage unit 42 stores donation application information as customer setting information for each business company. Figure 4 shows an example of donation application information. The donation application information is information indicating the type of donation set by the customer. The donation application information in this embodiment includes information on the business company that manages the assets of the customer for whom the donation has been set, an individual ID, the recipient of the donation, and the donation amount.

[0024] Returning to Figure 2, the donation history storage unit 44 stores donation history information, which is information showing the history of donations to public interest foundations, general foundations, etc., or in other words, information showing donation records. The donation history information may include the date and time of donation, individual ID (e.g., ID=123), the donating company (e.g., XX Securities), the name of the recipient organization (e.g., XX Foundation), and the donation amount (e.g., 1000 yen).

[0025] The processing unit 30 includes a donation application acceptance unit 50, an individual ID acquisition unit 52, a donation type determination unit 54, a donation execution unit 56, a receipt issuance unit 58, a consent acceptance unit 60, an ID integration unit 62, an authentication unit 64, a portal screen provision unit 66, and a modification unit 68.

[0026] The functions of the multiple functional blocks provided by the processing unit 30 may be implemented in a computer program (also referred to here as a "donation support program"). The donation support program may be stored on a recording medium, or installed on the Impact PF22 computer via the recording medium. Alternatively, the donation support program may be downloaded via a communication network and installed on the Impact PF22 computer. The processor (CPU, etc.) of the Impact PF22 computer may perform the functions of the multiple functional blocks by reading the donation support program into main memory and executing it.

[0027] The donation application reception unit 50 receives donation application information that customers have entered into each business company, which is transmitted from the securities back office system 16, the points program operating company device 18, or the bank device 20. The donation application reception unit 50 stores the received donation application information in the donation application information storage unit 42.

[0028] The individual ID acquisition unit 52 acquires customer information associated with the individual ID indicated in the donation application information from the device of the business company indicated in the donation application information. The individual ID acquisition unit 52 stores the customer information associated with the individual ID indicated in the donation application information in the customer information storage unit 40.

[0029] When the donation method determination unit 54 detects that a customer's donation timing has arrived, it refers to the donation application information of that customer stored in the donation application information storage unit 42 and determines the method of the customer's donation. A customer on whom a donation process is performed will also be referred to below as the "target customer".

[0030] The donation execution unit 56 performs donation-related processing based on the donation application information of the target customer stored in the donation application information storage unit 42, and performs processing on the systems of each business company using the individual ID indicated by the donation application information. In this embodiment, the donation execution unit 56 performs donation processing in the manner determined by the donation manner determination unit 54. For example, the donation execution unit 56 may work in cooperation with the device of the business company indicated by the donation application information to transfer the donation amount from the target customer's account to the account of the recipient foundation.

[0031] As shown in Figure 4, the donation application information storage unit 42 stores donation application information that specifies the type of donation to be made using the customer's assets as the source of funds for each of the multiple operating companies. The donation execution unit 56 executes processing on each operating company's system to make a donation using the customer's assets as the source of funds for each of the multiple operating companies in the manner specified in the donation application information.

[0032] The receipt issuance unit 58 generates a receipt addressed to the customer and sends the receipt data to the customer terminal 12. The receipt may include, for example, the name of the recipient organization, the donation amount, and the date of the donation.

[0033] The consent receiving unit 60 receives information (hereinafter also referred to as "consent information") indicating that the customer has agreed to the integration of multiple individual user IDs across multiple business companies. The consent receiving unit 60 may also receive consent information transmitted from the business company's system or the customer terminal 12.

[0034] The ID integration unit 62 assigns a common ID to the customer subject to ID integration, provided that consent information has been received by the consent reception unit 60. The common ID is a common ID across multiple business companies and is unique to each customer. As an alternative, the common ID may be determined by the customer, or the common ID determined by the customer may be notified to the impact PF 22 from the customer terminal 12.

[0035] Furthermore, the ID integration unit 62 stores the common ID assigned to the customer in the customer information storage unit 40, provided that consent information has been received by the consent reception unit 60. The ID integration unit 62, acting as an association unit, associates the common ID with multiple individual IDs of the customer that are pre-stored in the customer information storage unit 40.

[0036] The authentication unit 64 performs authentication processing using a common ID. The ID integration unit 62 may issue a password corresponding to the customer's common ID. The authentication unit 64 may also authenticate a customer who requests the portal screen described later using the common ID and password.

[0037] The portal screen providing unit 66, as a presentation unit, presents to the customer a screen that can be viewed using a common ID and shows the customer's setting information for each of the multiple business companies (hereinafter also referred to as the "portal screen"). In this embodiment, the portal screen is a screen that displays the customer's setting information managed by each of the multiple business companies in a consolidated manner. In this embodiment, the customer's setting information is donation application information. The donation application information includes information indicating the type of donation, such as the donation amount. If the authentication unit 64 successfully authenticates the customer who requested the portal screen, the portal screen providing unit 66 transmits data of the portal screen showing one or more donation application information associated with that customer to the customer terminal 12.

[0038] The modification unit 68 reflects changes in customer settings information for a particular business company on the portal screen to the donation application information storage unit 42. In this embodiment, the modification unit 68 updates the donation application information stored in the donation application information storage unit 42 to reflect the changed donation method on the portal screen.

[0039] The operation of the communication system 10 with the above configuration will now be explained. In this scenario, the customer will be using XX Securities, YY Points, and ZZ Bank. The customer terminal 12 transmits donation application information to the securities company device 14 in response to the customer's operation. The donation application information is entered into Impact PF 22 via the securities company device 14 and the securities back-office system 16. The donation application information entered into Impact PF 22 includes the business company name, individual ID, recipient, and donation amount, as shown in Figure 4.

[0040] Figure 5 is a flowchart showing the operation of Impact PF. The donation application reception unit 50 of Impact PF 22 receives donation application information (e.g., individual ID=123) transmitted from the securities back office system 16 (Y in S10). The donation application reception unit 50 stores the donation application information in the donation application information storage unit 42 (S12). The individual ID acquisition unit 52 of Impact PF 22 acquires customer information from the securities back office system 16 as customer information corresponding to the donation application information, which is customer information of XX Securities and is linked to the individual ID indicated by the donation application information (e.g., individual ID=123). The individual ID acquisition unit 52 stores the customer information corresponding to the donation application information in the customer information storage unit 40 (S14).

[0041] Similarly, customers make donation applications through YY Points. The customer terminal 12 sends donation application information to the points program operator's device 18, and the points program operator's device 18 sends the donation application information to Impact PF 22. The donation application information storage unit 42 of Impact PF 22 stores the donation application information (e.g., individual ID=456). The customer information storage unit 40 of Impact PF 22 stores customer information (e.g., individual ID=456) corresponding to the donation application information.

[0042] Similarly, a customer submits a donation application through ZZ Bank. The customer terminal 12 sends the donation application information to the banking device 20, and the banking device 20 sends the donation application information to the Impact PF 22. The donation application information storage unit 42 of the Impact PF 22 stores the donation application information (e.g., individual ID=789). The customer information storage unit 40 of the Impact PF 22 stores customer information (e.g., individual ID=789) corresponding to the donation application information.

[0043] If the donation application information is not accepted (N in S10), the processes in S12 and S14 are skipped.

[0044] In this embodiment, the timing of the donation is when the customer's assets managed by each business company increase. For example, the timing of the donation is when stock dividends, bond interest payments, or investment trust distributions are deposited into the customer's account managed by a financial institution. Alternatively, the timing of the donation is when new points are added to the customer's points managed by a points program operator.

[0045] The securities back-office system 16 notifies Impact PF22 of the occurrence of an event that triggers a donation. For example, the securities back-office system 16 notifies Impact PF22 that dividends have been deposited into a customer's securities account opened with XX Securities. This notification includes an individual ID (for example, individual ID = 123). Based on the above notification, the donation method determination unit 54 of Impact PF22 detects that it is time to make a donation from the customer's securities account. When the donation method determination unit 54 detects that it is time to make a donation (Y in S16), it refers to the donation application information associated with the individual ID indicated in the above notification to identify the recipient and the donation amount (S18).

[0046] The donation execution unit 56 of Impact PF22 executes a process to donate the amount specified in S18 to the recipient specified in S18 (S20). For example, the donation execution unit 56 may call the securities back office system 16's API (Application Programming Interface) for transfer instructions, thereby causing the securities back office system 16 to execute the transfer process of the donation amount from the XX Securities customer's account to the recipient foundation's account. The donation execution unit 56 stores donation history information showing the details of the donation in S20 in the donation history storage unit 44 (S22).

[0047] Similarly, the Impact PF22 donation method determination unit 54 detects, based on a notification from the points program operator device 18 (e.g., individual ID=456), that it is time for the customer to make a donation from the points they hold. The Impact PF22 donation execution unit 56 works in conjunction with the points program operator device 18 to execute the donation process in the manner indicated by the donation application information linked to the individual ID indicated by the notification. For example, the donation execution unit 56 may call an API provided by the points program operator device 18 to cause the points program operator device 18 to execute the process of transferring the amount indicated by the donation application information from the YY Points business company to the recipient foundation, and the process of deducting points equivalent to that amount from the customer's points.

[0048] Similarly, the ImpactPF22 donation method determination unit 54 detects, based on a notification from the banking device 20 (e.g., individual ID=789), that it is time for the customer to make a donation from their bank account. The ImpactPF22 donation execution unit 56 works in conjunction with the banking device 20 to execute the donation process in the manner indicated by the donation application information linked to the individual ID indicated by the notification. For example, the donation execution unit 56 may call an API provided by the banking device 20 to cause the banking device 20 to transfer the donation amount from the ZZ Bank customer's account to the recipient foundation's account.

[0049] If the timing for donation has not yet been detected (N in S16), the processing in S18-S22 is skipped.

[0050] The receipt issuing unit 58 of Impact PF22 detects when it is time to issue a receipt (Y in S24). The receipt issuance timing may be a specific date and time within a predetermined unit period (for example, 0:00 on the 1st of each month), or it may be when data requesting receipt issuance is received from the customer terminal 12. Based on the donation history information stored in the donation history storage unit 44, the receipt issuance unit 58 generates a receipt addressed to the customer, including the name of the recipient organization and the donation amount. The receipt issuance unit 58 sends the generated receipt data to the customer terminal 12 (S26). If it has not yet been detected that it is time to issue a receipt (N in S24), the process in S26 is skipped.

[0051] Figure 6 is also a flowchart illustrating the operation of Impact PF22. The customer terminal 12 sends data to Impact PF22 requesting the integration target ID specification screen in response to customer operations. The consent reception unit 60 of Impact PF22 receives the data requesting the integration target ID specification screen sent from the customer terminal 12 (Y in S30). The consent reception unit 60 sends the data for the integration target ID specification screen to the customer terminal 12 (S32). The customer terminal 12 displays the integration target ID specification screen on its display.

[0052] Figure 7 shows an example of the screen for specifying the IDs to be merged. The screen for specifying the IDs to be merged 70 includes fields for inputting the individual IDs to be merged and the information of the business company that assigned those individual IDs to the customer. The screen for specifying the IDs to be merged 70 is a screen that allows specifying multiple pairs of business companies and individual IDs. The customer terminal 12 transmits the IDs to be merged information entered by the customer on the screen for specifying the IDs to be merged 70 to the Impact PF 22. The IDs to be merged information is information indicating that the customer has agreed to merge multiple individual IDs. In this embodiment, the IDs to be merged information includes multiple pairs of individual IDs to be merged and the business company that assigned those individual IDs to the customer. A customer who has agreed to merge multiple individual IDs will also be referred to as the "target customer" below.

[0053] The consent reception unit 60 receives the integration target ID information transmitted from the customer terminal 12 (Y in S34). The ID integration unit 62 of the impact PF22 refers to the customer information stored in the customer information storage unit 40 and determines whether the multiple individual IDs indicated by the integration target ID information are IDs assigned to the same person. Specifically, the ID integration unit 62 determines that the multiple individual IDs are IDs assigned to the same person if the customer name and date of birth pair associated with each of the multiple individual IDs to be integrated matches.

[0054] If the ID integration unit 62 determines that multiple individual IDs to be integrated are assigned to the same person (Y in S36), it determines a unique common ID for the target customer (S38). The ID integration unit 62 associates the common ID assigned to the target customer in S38 with the multiple individual IDs of the target customer stored in the customer information storage unit 40 (S40). Figure 8 shows an example in which the common ID of the target customer is associated with multiple individual IDs of the target customer.

[0055] If it is determined that the multiple individual IDs to be merged are not assigned to the same person (N in S36), processes S38 and S40 are skipped. If the merged ID information sent from customer terminal 12 is not accepted (N in S34), processes S36 to S40 are skipped. If data requesting the merged ID specification screen is not accepted from customer terminal 12 (N in S30), processes S32 to S40 are skipped.

[0056] Customer terminal 12 transmits data to Impact PF22 that includes a common ID specified by the customer and requests a portal screen, in response to customer operations. When the authentication unit 64 of Impact PF22 receives the data requesting a portal screen transmitted from customer terminal 12 (Y in S42), it authenticates the requesting customer based on the common ID indicated by that data. For example, customer terminal 12 may transmit data including a common ID and password pair to Impact PF22, and the authentication unit 64 of Impact PF22 may authenticate the requesting customer using the common ID and password pair.

[0057] If authentication of the requesting customer is successful, the portal screen provider unit 66 of Impact PF22 refers to the customer information storage unit 40 to identify multiple individual IDs of the requesting customer associated with the requesting customer's common ID. The portal screen provider unit 66 refers to the donation application information storage unit 42 to identify multiple donation application information of the requesting customer associated with the multiple individual IDs of the requesting customer. The portal screen provider unit 66 transmits the portal screen data, including the multiple donation application information of the requesting customer, to the customer terminal 12 (S44). The customer terminal 12 displays the portal screen on its display.

[0058] Figure 9 shows an example of a portal screen. Figure 9 shows the portal screen 80 provided to a customer with the common ID "abc". The portal screen 80 contains donation application information processed by the customer through each business company, and Figure 9 shows three donation application information entries. The portal screen 80 also includes a change object 82, which is a screen element for modifying donation application information. A customer viewing the portal screen 80 selects the change object 82 of the donation application information they wish to modify and enters the modified donation application information into the portal screen 80. The customer terminal 12 transmits the modified donation application information to Impact PF22 in response to the customer's operation. The modified donation application information transmitted from the customer terminal 12 to Impact PF22 includes the common ID and the donating business company, and may also include the changed recipient organization and / or the changed donation amount.

[0059] The change unit 68 of Impact PF22 receives change information for donation application information transmitted from the customer terminal 12 (Y in S46). Based on the received change information, the change unit 68 changes the donation application information stored in the donation application information storage unit 42 (S48). For example, the change unit 68 may refer to the customer information storage unit 40 and identify the individual ID of the donation application information to be changed based on the combination of the common ID and the business company indicated by the change information. Based on the identified individual ID, the change unit 68 may identify the donation application information to be changed from the donation application information stored in the donation application information storage unit 42. The change unit 68 may update the recipient and / or donation amount indicated by the donation application information to be changed to match the content indicated by the change information.

[0060] If no change information regarding the donation application is received from the customer terminal 12 (N in S46), the process in S48 is skipped. Also, if no data requesting the portal screen is received from the customer terminal 12 (N in S42), the processes in S44 to S48 are skipped.

[0061] According to the Impact PF22 embodiment, customers can view a portal screen displaying their configuration information (in the embodiment, donation application information indicating the type of donation) for each of multiple business companies using a common ID. Furthermore, according to the Impact PF22 embodiment, customers do not need to access the equipment of each individual business company when changing configuration information; they can change the configuration information for any business company from the portal screen. This improves the convenience of changing configurations.

[0062] Furthermore, according to the embodiment of Impact PF22, subject to customer consent, multiple individual customer IDs defined by multiple business companies are integrated into a common ID. This makes it possible to switch from using Impact PF22 via business companies (B2B2C) to direct use of Impact PF22 (B2C), subject to customer consent.

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

[0064] The technical concept described in the embodiment can be applied to various systems other than systems that support donations, etc. For example, the technical concept described in the embodiment is impact investing that aims to achieve both the resolution of environmental and social issues and investment returns, and can be applied to supporting impact investing that uses user assets managed by multiple operating companies as its source. In that case, the investment destinations and investment amounts of impact investments set by the customer and managed by each of the multiple operating companies may be displayed together on the portal screen. Furthermore, it may be possible to change the investment destinations and / or investment amounts of impact investments set for any operating company from the portal screen. In addition, the technical concept described in the embodiment can also be applied when changing information (e.g., user address information) that a user has individually set for multiple operating companies using the portal screen.

[0065] <Note> Based on the above description of embodiments and modifications, the following technology is disclosed. [Technology 1] A first storage unit that stores multiple user IDs defined in the systems of multiple organizations, A second storage unit that stores the user's configuration information for each of the aforementioned multiple organizations, An execution unit that performs processing on the systems of each organization based on the user's configuration information stored in the second storage unit, using the user's ID defined in the system of each organization; An association unit that associates the common ID assigned to the user with a plurality of user IDs stored in the first storage unit, A display unit that presents to the user a screen viewable using the aforementioned common ID, and which displays the user's settings information for each of the multiple organizations, When the user's settings information for a certain organization is changed on the aforementioned screen, the change unit reflects that change in the second storage unit, An information processing system equipped with the following features. This information processing system allows users to view screens (hereinafter referred to as "portal screens") displaying their configuration information for multiple organizations (such as business companies) using a common ID. Furthermore, this system allows users to change configuration information for any organization using the portal screen, rather than accessing the devices of each individual organization. This enhances the convenience of changing configurations. [Technology 2] The system further includes a reception unit that receives information indicating that the user has agreed to integrate the aforementioned multiple IDs. The association unit, on the condition that it has received the information indicating that an agreement has been reached, associates the common ID assigned to the user with the multiple IDs of the user stored in the first storage unit. The information processing system described in Technology 1. According to this information processing system, subject to user consent, multiple user IDs defined by multiple organizations can be integrated into a common ID. [Technology 3] The second storage unit stores user setting information regarding the manner of donations to each of the plurality of organizations, using the assets owned by the user as the source of funds. The execution unit executes a process on the system of each of the multiple organizations to make a donation to each of the organizations, using the assets owned by the user as the source of funds, in a manner determined by the user's configuration information. An information processing system as described in Technology 1 or 2. This information processing system allows users to easily change the type of donation they make to each of multiple organizations, using their assets as the source of funding, through a portal screen. [Technology 4] A computer comprising a first storage unit that stores multiple user IDs defined in the systems of multiple organizations, and a second storage unit that stores the user's configuration information for each of the multiple organizations, The processing for each organization's system based on the user's configuration information stored in the second storage unit is executed using the user's ID defined in each organization's system. The common ID assigned to the user is associated with the multiple IDs of the user stored in the first storage unit. A screen viewable using the aforementioned common ID, and showing the user's settings information for each of the multiple organizations, is presented to the user. If the user's settings information for a certain organization is changed on the aforementioned screen, the change is reflected in the second storage unit. Information processing methods. This information processing method produces the effects described in Technology 1. [Technology 5] A computer comprising: a first storage unit that stores multiple user IDs defined in the systems of multiple organizations; and a second storage unit that stores the user's configuration information for each of the multiple organizations, A function that executes processing for each organization's system based on the user's configuration information stored in the second storage unit, using the user's ID defined in each organization's system, A function to associate the common ID assigned to the user with multiple IDs of the user stored in the first storage unit, A screen viewable using the aforementioned common ID, and a function that presents the user with a screen showing the user's settings information for each of the multiple organizations, The function includes, when the user's settings information for a certain organization is changed on the aforementioned screen, reflecting that change in the second storage unit, A computer program to achieve this. This computer program makes it possible to realize a computer that achieves the effects described in Technology 1. [Explanation of Symbols]

[0066] 12 Customer terminal, 22 Impact PF, 40 Customer information storage unit, 42 Donation application information storage unit, 56 Donation execution unit, 60 Consent acceptance unit, 62 ID integration unit, 66 Portal screen provision unit, 68 Change unit, 80 Portal screen.

Claims

1. A first storage unit that stores multiple user IDs defined in the systems of multiple organizations, A second storage unit that stores the user's configuration information for each of the aforementioned multiple organizations, An execution unit that performs processing on the systems of each organization based on the user's configuration information stored in the second storage unit, using the user's ID defined in the system of each organization; An association unit that associates the common ID assigned to the user with a plurality of user IDs stored in the first storage unit, A display unit that presents to the user a screen viewable using the aforementioned common ID, and which displays the user's settings information for each of the multiple organizations, When the user's settings information for a certain organization is changed on the aforementioned screen, the change unit reflects that change in the second storage unit. Equipped with, The second storage unit stores user setting information regarding the manner of donations to each of the plurality of organizations, using the assets owned by the user as the source of funds. The execution unit executes a process on the system of each of the multiple organizations to make a donation to each of the organizations, using the assets owned by the user as the source of funds, in a manner determined by the user's configuration information. Information processing system.

2. The system further includes a reception unit that receives information indicating that the user has agreed to integrate the aforementioned multiple IDs. The association unit, on the condition that it has received the information indicating that an agreement has been reached, associates the common ID assigned to the user with the multiple IDs of the user stored in the first storage unit. The information processing system according to claim 1.

3. A computer comprising a first storage unit that stores multiple user IDs defined in the systems of multiple organizations, and a second storage unit that stores the user's configuration information for each of the multiple organizations, The processing for each organization's system based on the user's configuration information stored in the second storage unit is executed using the user's ID defined in each organization's system. The common ID assigned to the user is associated with the multiple IDs of the user stored in the first storage unit. A screen viewable using the aforementioned common ID, and a screen showing the user's settings information for each of the multiple organizations, is presented to the user. If the user's settings information for a certain organization is changed on the aforementioned screen, the change is reflected in the second storage unit. The second storage unit stores user setting information regarding the manner of donations to each of the plurality of organizations, using the assets owned by the user as the source of funds. The aforementioned actions include performing a process on the systems of each of the multiple organizations to make a donation to each of the organizations, using the assets owned by the user as the source of funds, in a manner determined by the user's configuration information. Information processing methods.

4. A computer comprising: a first storage unit that stores multiple user IDs defined in the systems of multiple organizations; and a second storage unit that stores the user's configuration information for each of the multiple organizations, A function that executes processing for each organization's system based on the user's configuration information stored in the second storage unit, using the user's ID defined in each organization's system, A function to associate the common ID assigned to the user with multiple IDs of the user stored in the first storage unit, A screen viewable using the aforementioned common ID, and a function that presents the user with a screen showing the user's settings information for each of the multiple organizations, The function includes, when the user's settings information for a certain organization is changed on the aforementioned screen, reflecting that change in the second storage unit, To make it happen, The second storage unit stores user setting information regarding the manner of donations to each of the plurality of organizations, using the assets owned by the user as the source of funds. The function to be executed performs a process on the system of each of the multiple organizations to make a donation to each of the organizations, using the assets owned by the user as the source of funds, in a manner determined by the user's configuration information. Computer program.

Images