Information processing device, information processing method, and information processing program

Abstract

To improve convenience of an accounting system.SOLUTION: An information processing device according to the present application includes a definition information generating unit, an acquisition unit, and an output unit. The definition information generating unit uses screen definition information concerning a screen definition of each of a plurality of transaction screens used in an accounting system to generate function definition information concerning a function of an accounting system to be provided to the outside. The acquisition unit acquires input information via an input screen generated based on the function definition information. The output unit converts the input information into data in a format that can be processed by the accounting system based on the function definition information, and outputs the converted data to the accounting system.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, an information processing method, and an information processing program. [Background technology]

[0002] Bank users sometimes have to visit a bank during business hours to complete various procedures such as opening an account, changing their address, applying for a loan, etc. To eliminate this inconvenience, there is a demand for technology that allows users to complete various procedures using smartphone applications or PC (Personal Computer) browsers. [Prior art documents] [Patent documents]

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

[0004] However, accounting systems that execute banking operations are highly reliable systems, and also perform complex information processing using a large number of transaction screens, for example 3,000 screens. From a security standpoint, allowing general users to directly operate the accounting system from outside the system is too risky. Also, providing the accounting system specifications themselves to developers of online services is also risky. Therefore, there is a demand to provide the system in an easy-to-use format, limiting the range of functions provided to general users.

[0005] The present application has been made in consideration of the above, and aims to improve the convenience of accounting systems. [Means for solving the problem]

[0006] An information processing device according to an embodiment of the present disclosure includes a definition information generation unit that generates function definition information regarding the functions of the accounting system to be provided to an external party using screen definition information regarding the screen definitions of each of a plurality of transaction screens used in the accounting system, an acquisition unit that acquires input information via an input screen generated based on the function definition information, and an output unit that converts the input information into data in a format that can be processed by the accounting system in accordance with the function definition information, and outputs the converted data to the accounting system. Effect of the Invention

[0007] According to one aspect of the embodiment, the convenience of the accounting system can be improved. [Brief description of the drawings]

[0008] [Figure 1A] FIG. 1A is an explanatory diagram illustrating an example of a function provision process for providing a function of an accounting system according to an exemplary embodiment of the present disclosure. [Figure 1B] FIG. 1B is an explanatory diagram illustrating an example of a function provision process for providing a function of an accounting system according to an exemplary embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram illustrating an example of a service collaboration system according to the embodiment. [Diagram 3] FIG. 3 is a diagram illustrating an example of a screen definition information storage unit according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the mashup information storage unit according to the embodiment. [Diagram 5] FIG. 5 is an explanatory diagram showing an example of an API definition generation process for generating an API definition. [Figure 6] FIG. 6 is an explanatory diagram illustrating an example of a request JSON receiving process for receiving a request JSON. [Figure 7] FIG. 7 is an explanatory diagram illustrating an example of a request JSON conversion process for converting a request JSON into transmission message data. [Figure 8]FIG. 8 is a flowchart showing an example of a process for providing a function of an accounting system, which is executed by the information processing device according to the embodiment. [Figure 9] FIG. 9 is a flowchart showing an example of processing for transmitting and receiving electronic data with an accounting system based on a request JSON, which is executed by an information processing device according to the embodiment. [Figure 10] FIG. 10 is a flowchart showing an example of a process for converting message data received from an accounting system into response JSON, which is executed by an information processing device according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a hardware configuration. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment. Details of one or more embodiments are described in the following description and drawings. In addition, multiple embodiments can be appropriately combined within a range that does not cause contradiction in the processing contents. In addition, the same parts in the following one or more embodiments are given the same reference numerals, and duplicated explanations are omitted.

[0010] 1. ILLUSTRATIVE EMBODIMENTS First, an exemplary embodiment of the present disclosure will be described in detail with reference to FIGS. 1A and 1B.

[0011] 1-1. Overview of Exemplary Embodiments In recent years, historically low interest rates have sapped the profitability of banks. For this reason, various banks are exploring ways to increase profits by effectively utilizing their existing bank systems. One such method is to provide each function, which is the business performed by the accounting system, to an external party. For example, it has been proposed to provide functions such as account opening, address change, and loan application provided by existing accounting systems to external businesses such as fintech companies.

[0012] When exposing accounting system functions to external businesses, the interface of the accounting system becomes an issue. For example, accounting systems may employ proprietary user interfaces in legacy formats. Such proprietary user interfaces send and receive messages in proprietary formats, such as messages in binary format. As a result, various banks are aiming to provide the functions of their accounting systems through a general interface, an application programming interface (API).

[0013] However, accounting systems have a huge number of functions, including not only account opening, address change, and loan applications, but also various deposits, credit transactions, foreign exchange transactions, trusts, public bonds, loans, etc. Generally, manually creating APIs to implement the functions of such a large number of operations requires high man-month costs and time.

[0014] Additionally, accounting systems also implement check functions to check the operation of the functions mentioned above, so reimplementing these check functions also takes time.

[0015] Therefore, an information processing device according to an exemplary embodiment executes the process described below in order to efficiently realize API implementation of each function provided by the accounting system.

[0016] Specifically, the information processing device provides the functions of an operating accounting system by providing an API, which is an example of a set of rules that stipulate procedures and data formats for calling and using from other external programs, as a service to the outside. In the exemplary embodiment shown in Figs. 1A and 1B, in order to automatically build an API that provides the functions of accounting system 200, the information processing device turns the transaction screen of operating accounting system 200 into an API. For example, the information processing device generates web APIs such as an account opening API, an address change API, and a loan application API from transaction screens such as an account opening screen, an address change screen, and a loan application screen.

[0017] The information processing device can provide service collaboration (functional collaboration) for external businesses by automatically converting a large number of transaction screens (e.g., 3,000 screens) handled in banking operations into APIs. Furthermore, the information processing device can check banking operation items (e.g., type, number of digits, required items / optional items) using APIs (e.g., account opening API, address change API, loan application API) generated from the transaction screens.

[0018] In addition to automatically generating the APIs described above, the information processing device can provide the same financial service by combining existing functions through a mashup using the APIs. For example, the information processing device can provide a financial service of changing a name and reissuing a card with the changed name by combining a name change API and a card reissue API. This allows the information processing device to improve the convenience of bank procedures.

[0019] [1-2. Function provision processing] The function providing process according to the above-described exemplary embodiment will be described below with reference to FIGS. 1A and 1B.

[0020] 1A and 1B are explanatory diagrams illustrating an example of a function provision process for providing a function of an accounting system 200 according to an exemplary embodiment of the present disclosure. In an exemplary embodiment, the function provision process is performed by an information processing device 100 illustrated in Fig. 1A and 1B. Although not illustrated in Fig. 1, the information processing device 100, the accounting system 200, the business device 300, and the user device 400 illustrated in Fig. 1A and 1B are connected by a network N such as the Internet.

[0021] The information processing device 100 is an example of a server device managed by a company that provides service collaboration for external businesses. The service collaboration for external businesses enables various contents of the external business to be linked with the functions of the accounting system 200. As an example, when the external business is an automobile dealer, the contents are contents related to loan applications and balance inquiries. In this example, a car buyer can apply for a car loan using, for example, website content developed by the automobile dealer in accordance with the API specifications.

[0022] The accounting system is implemented by a mainframe or server installed in a bank or a data center owned by the bank. In this example, accounting system 200 is managed by the bank. Accounting system 200 accepts and records various information such as customer notifications at bank counters (e.g., withdrawals, address changes). Accounting system 200 also manages customer money and customer information.

[0023] The business entity device 300 is an example of a server device managed by an external business entity. As described above, the external business entity develops various financial services, such as an application for a car loan, in accordance with the specifications of the published API, and provides the services to users using the business entity device 300.

[0024] The user device 400 is shown as a smartphone. In this example, the user device 400 is managed by a user who uses various contents developed by external businesses in accordance with API specifications.

[0025] As shown in FIG. 1A, first, the information processing device 100 acquires screen definition information that defines transaction screens handled in banking operations from the accounting system 200 (step S1). In the example of FIG. 1A, the information processing device 100 acquires a set 20 of screen definition information that corresponds to a set 10 of transaction screens. For example, the set 10 of transaction screens includes a large number of transaction screens. Each transaction screen corresponds to a respective piece of screen definition information. The screen definition information is definition information that defines input fields, etc. of a transaction screen written in a development language such as JAVA (registered trademark) or COBOL.

[0026] The transaction screens described above are displayed on the bank employee's terminal and used for data entry by the bank employee. For example, the set of transaction screens 10 includes a transaction screen for opening an account, a transaction screen for changing an address, and a transaction screen for applying for a loan. The bank employee uses such transaction screens to perform banking operations.

[0027] Next, the information processing device 100 generates an API definition and a mashup API from the acquired screen definition information (step S2). For example, the information processing device 100 generates a set 30 of API definitions from the set 20 of screen definition information. The API definitions are item definitions for APIs generated from the screen definition information, and are written in various script languages ​​such as JavaScript (registered trademark). The set 30 of API definitions defines item information related to input items of the screen definition information included in the set 20 of screen definition information.

[0028] In addition, the information processing device 100 generates a mashup API 40 from the set 20 of screen definition information. The mashup API 40 is a definition that determines the operation when APIs are combined and used, and defines the behavior of the set 30 of API definitions. An example of the screen definition information is described in detail below with reference to FIG. 3. Also, an example of the mashup API is described in detail below with reference to FIG. 4.

[0029] Next, the information processing device 100 generates an API connection condition specification from the generated API definition and the mashup API (step S3). The API connection condition specification is a specification describing connection conditions referenced by an external business using the API definition. The specification may include, for example, how the API definition cooperates with other API definitions as a definition of the operation of the mashup API. For example, the external business can develop various applications that implement a JSON (JavaScript Object Notation) interface in accordance with the API connection conditions described in the API connection condition specification. In this way, the information processing device 100 can automatically document the API definition so that the external business can develop various applications using the JSON interface. An example of a process for generating an API connection condition specification will be described in detail below with reference to FIG. 5.

[0030] Next, the information processing device 100 provides the generated API connection condition specification to the business operator device 300 (step S4). An external business operator related to the business operator device 300 uses the API connection condition specification to develop financial services that can utilize the functions of the accounting system 200. For example, the business operator develops applications related to financial services using a JSON interface. Then, the business operator device 300 provides the financial services provided by the accounting system 200 to the user device 400 (step S5).

[0031] 1B, after step S5 in FIG. 1A, the user device 400 requests the business device 300 to execute a function of the accounting system 200 (step S6). Then, the information processing device 100 receives a request JSON related to the execution of the function of the accounting system 200 from the business device 300 (step S7). An example of a process for receiving the request JSON is described in detail below with reference to FIG. 6.

[0032] Next, the information processing device 100 converts the received request JSON into transmission message data (step S8). In the example of FIG. 1B, the information processing device 100 maps the received request JSON 50 into transmission message data 60 according to the set of API definitions 30 and the mashup API 40. The transmission message data 60 is binary data, which is an example of data in a legacy format. An example of the process of mapping the request JSON into transmission message data will be described in detail below with reference to FIG. 7 and FIG. 9.

[0033] Next, the information processing device 100 checks the items of the transmission message data by referring to the API definition (step S9). For example, the information processing device 100 reads the set 30 of API definitions and determines whether the type and number of digits of the transmission message data 60 are appropriate, and whether any required items are missing.

[0034] Next, the information processing device 100 transmits the transmission message data 60 to the accounting system 200 (step S10). Then, the information processing device 100 receives reception message data related to the execution result of the function of the accounting system 200 from the accounting system 200 (step S11).

[0035] Next, the information processing device 100 converts the received message data into a response JSON (step S12). In the example of Fig. 1B, the information processing device 100 maps the received message data 70 into a response JSON 80 according to the set 30 of API definitions. An example of the process of mapping the received message data into a response JSON is described in detail below with reference to Fig. 10.

[0036] After that, the information processing device 100 transmits the response JSON 80 to the business device 300 (step S13). Then, the business device 300 provides the execution result of the function of the accounting system 200 to the user device 400 (step S14).

[0037] As described above, the information processing device 100 generates an API definition corresponding to the function of each transaction screen from a large number of transaction screens used for business in the existing accounting system 200. When a user requests a function of the accounting system 200, the information processing device 100 converts the request JSON into binary data used in the accounting system 200 by referring to the generated API definition, and transmits this data to the accounting system 200.

[0038] This allows the information processing device 100 to realize service collaboration for external businesses. Furthermore, the information processing device 100 allows a user to combine and use the functions of the accounting system 200 by using the generated API definition set 30 and the mashup API 40.

[0039] The information processing device 100 that performs such an accounting system function provision process will be described in detail below.

[0040] [2. Service Collaboration System] Next, with reference to FIG. 2, a functional configuration example of a system including an information processing device 100 that realizes the processes described above with reference to FIGS. 1A and 1B will be described.

[0041] [2-1. Service integration system configuration] Fig. 2 is a diagram showing an example of a service collaboration system 1 according to an embodiment. As shown in Fig. 2, the service collaboration system 1 includes components such as an information processing device 100, an accounting system 200, a business device 300, and a user device 400. Although not shown in Fig. 2, the service collaboration system 1 may include a plurality of information processing devices 100, a plurality of business device 300, and a plurality of user devices 400. In addition, the service collaboration system 1 may include other components such as a business related to the information processing device 100 and devices of end users.

[0042] The information processing device 100, the accounting system 200, the business device 300, and the user device 400 are each connected to a network N by wire or wirelessly. The network N is, for example, the Internet, a Wide Area Network (WAN), a Local Area Network (LAN), etc. The components of the service collaboration system 1 can communicate with each other via the network N.

[0043] The information processing device 100 is an information processing device that executes processing for providing the functions of the accounting system 200. The information processing device 100 can generate an interface (i.e., a counter) for using the functions of the accounting system 200 from a transaction screen of the accounting system 200. For example, the information processing device 100 can generate an API that provides the functions of the accounting system 200 to the financial services of the business device 300, and a specification of this API. In addition, the information processing device 100 can publish the specification of the API to an external business. The information processing device 100 may be any type of information processing device, including a server. A plurality of information processing devices 100 may each provide the functions of various servers, such as a web server, an application server, and a database server. A configuration example of the information processing device 100 will be described in detail in the next section.

[0044] Accounting system 200 is an information system that handles banking operations such as deposits, loans, and transfers. Accounting system 200 includes elements such as business applications, CIF (Customer Information File), and control applications. Accounting system 200 may be any type of information system that includes hardware such as servers and storage.

[0045] The business operator device 300 is an information processing device that provides financial services through an interface for utilizing the functions of the accounting system 200. A business operator can develop a financial service (e.g., a website, a smartphone application) that calls the API of the accounting system 200 based on the API specification generated by the information processing device 100. The business operator device 300 may be any type of information processing device, including a server.

[0046] The user device 400 is an information processing device used by a user. The user device 400 can request access to financial services provided by the business device 300. The user device 400 may be any type of information processing device, including a client device such as a smartphone, a desktop PC, a notebook PC, a tablet PC, etc.

[0047] 2-2. Configuration of information processing device Next, of the devices shown in Fig. 2, the information processing device 100 that executes the functions described in Fig. 1A and Fig. 1B will be described in detail. As shown in Fig. 2, the information processing device 100 has a communication unit 110, a storage unit 120, and a control unit 130. Note that the information processing device 100 may have an input unit such as a keyboard or a mouse that accepts various operations from an administrator who uses the information processing device 100, and a display unit such as a display that displays various information.

[0048] (Communication unit 110) The communication unit 110 is realized by, for example, a network interface card (NIC). The communication unit 110 is connected to a network by wire or wirelessly. The communication unit 110 is communicatively connected to the accounting system 200, the business operator device 300, and the user device 400 via the network N. The communication unit 110 can transmit and receive information between the accounting system 200, the business operator device 300, and the user device 400 via the network.

[0049] (Storage unit 120) The storage unit 120 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. As shown in Fig. 2, the storage unit 120 has a screen definition information storage unit 121, a mashup information storage unit 122, an API definition storage unit 123, and an API connection condition specification storage unit 124.

[0050] (Screen definition information storage unit 121) The screen definition information storage unit 121 stores screen definition information related to items, item definitions, values, etc., for each transaction screen used when executing each business of the accounting system 200. In one example, the screen definition information may be text data or may be defined by a table of a relational database. For example, if there are 3,000 transaction screens, 3,000 pieces of screen definition information are generated.

[0051] Fig. 3 is a diagram showing an example of the screen definition information storage unit 121 according to the embodiment. In the example of Fig. 3, the screen definition information stored in the screen definition information storage unit 121 has items such as "item name", "item logical name", "type", "number of digits", "mandatory check target item", "system logical item name", etc.

[0052] "Item name" indicates the name of the item. "Item logical name" indicates the logical name understood by the program. "Type" indicates the type of item, and "Number of digits" indicates the number of digits of the item. "Item that must be checked" indicates whether the item is a required item to be checked. "System logical item name" indicates a string used to identify the item in accounting system 200.

[0053] For example, the first line in Figure 3 shows that the item logical name of the item named "CIF number" is "cifno", the item type of the item named "CIF number" is "numeric", the number of digits of the item named "CIF number" is "10", the item named "CIF number" is not a required item to be checked, and the system logical item name of the item named "CIF number" is "F0001".

[0054] (Mashup information storage unit 122) The mashup information storage unit 122 stores mashup information used to generate the mashup API. The mashup information may be defined by text data or a table of a relational database.

[0055] Fig. 4 is a diagram illustrating an example of the mashup information storage unit 122 according to the embodiment. In the example of Fig. 4, the mashup information stored in the mashup information storage unit 122 has tables such as "executed transaction", "execution conditions", "default values, setting definitions", "handover data", and "copy data".

[0056] "Executed transaction" indicates the executed transaction corresponding to the transaction screen. For example, the executed transaction identified by the executed transaction ID "00001" is a CIF opening. "Execution conditions" indicates the execution conditions of the executed transaction. For example, if the registration number is in the request data, the executed transaction identified by the executed transaction ID "00042" is executed. "Default value, setting definition" indicates the default value of the executed transaction. For example, in the executed transaction identified by the executed transaction ID "00001", the default value of the subject is "normal". "Transfer data" indicates how the items of the executed transaction are transferred to other executed transactions by the mashup. For example, the "branch number" of the executed transaction identified by the executed transaction ID "00010" is transferred to the executed transaction identified by the executed transaction ID "00031". "Copy data" indicates how the items of the executed transaction are copied to other executed transactions by the mashup. For example, the item "Main transaction purpose" of the executed transaction identified by the executed transaction ID "00001" is copied as the item "Transaction purpose" to the executed transaction identified by the executed transaction ID "00031."

[0057] (API definition storage unit 123) The API definition storage unit 123 stores a set of API definitions 30 and a mashup API 40. The API definitions included in the set of API definitions 30 are definition information of APIs based on item information related to input items that accept input of information required to execute a function on a transaction screen corresponding to the function to be provided to the outside. Specifically, the API definition defines a method or arrangement for the business device 300 to use the function of the accounting system 200 provided by the information processing device 100. For example, the API definition is definition information such as parameters to be sent as a request and values ​​that can be specified for each item of the screen definition information.

[0058] The mashup API 40 is definition information that defines the behavior of the application interface, and is definition information of a mashup that defines the transition of input screens required when executing a published function. For example, the mashup API 40 defines the order in which executed transactions corresponding to each executed transaction are executed and the combination of functions. For example, the mashup API 40 defines that transaction screen A, transaction screen B, and transaction screen C are executed when opening an account.

[0059] (API connection condition specification storage unit 124) The API connection condition specification storage unit 124 stores a connection condition specification, which is a specification of connection conditions that a user (business device 300) who uses a function provided externally refers to when using an API. That is, this connection condition specification defines each URL (Uniform Resource Locator) for using an API corresponding to each transaction screen for each transaction screen, and can also include conditions for use (domain designation), etc.

[0060] (Control unit 130) The control unit 130 is a controller, and is realized by a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) executing various programs (corresponding to an example of an information processing program) stored in a storage device inside the information processing device 100 using a RAM or the like as a working area. The control unit 130 may also be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a GPGPU (General Purpose Graphic Processing Unit).

[0061] As shown in FIG. 2, the control unit 130 has a collection unit 131, a definition information generation unit 132, a specification information generation unit 133, a provision unit 134, an acquisition unit 135, and an output unit 136, and realizes or executes the functions and actions of information processing described below. In addition, the control unit 130 can realize the function provision processing of the accounting system 200 described above with reference to FIG. 1A and FIG. 1B. One or more processors of the information processing device 100 can realize the functions of each control unit in the control unit 130 by executing instructions stored in one or more memories of the information processing device 100. Note that the internal configuration of the control unit 130 is not limited to the configuration shown in FIG. 2, and may be other configurations as long as they perform the information processing described later. For example, the output unit 136 may perform all or part of the information processing described later for units other than the output unit 136.

[0062] (Collection Department 131) The collection unit 131 collects various information used in processing to provide the functions of the accounting system 200. In at least one embodiment, the collection unit 131 collects screen definition information related to screen definitions of transaction screens used in the accounting system 200. The collection unit 131 acquires screen definition information that defines the contents and functions of various screens.

[0063] In one example, the collection unit 131 acquires screen definition information that defines transaction screens handled in banking operations from the accounting system 200. As described above with reference to FIG. 1A, the collection unit 131 acquires, for example, a set 20 of screen definition information corresponding to a set 10 of transaction screens. For example, the set 10 of transaction screens includes a large number of transaction screens. The multiple transaction screens respectively correspond to multiple pieces of screen definition information.

[0064] Then, the collection unit 131 stores the acquired screen definition information in the screen definition information storage unit 121. The collection unit 131 can receive the screen definition information from an administrator who uses the information processing device 100 via a user interface.

[0065] Furthermore, the collection unit 131 may receive mashup information via a user interface from an administrator who uses the information processing device 100. Then, the collection unit 131 stores the received mashup information in the mashup information storage unit 122.

[0066] (Definition information generation unit 132) The definition information generating unit 132 generates an API definition and a mashup API using the screen definition information stored in the screen definition information storage unit 121, and stores them in the API definition storage unit 123. Specifically, the definition information generating unit 132 generates an API definition that defines parameters and values ​​that can be specified when used as an API for each item defined in the screen definition information so that the business device 300 can acquire and use it. For example, using the screen definition information in FIG. 3 as an example, the definition information generating unit 132 defines "cifno" as a parameter and "10-digit number" as a value for "CIF number", and defines "tenban" as a parameter and "6-digit number" as a value for "store number". That is, when the external business device 300 generates an input screen for "CIF number", it is possible to realize normal data transmission and reception between the external business device 300 and the accounting system 200 by setting "parameter=cifno" and "value=10-digit number".

[0067] Similarly, specifically, the definition information generating unit 132 generates a mashup API that defines the order in which transactions are executed, using screen definition information, mashup information stored in the mashup information storage unit 122, and the like. For example, the definition information generating unit 132 uses the mashup information, information previously defined by an administrator, and the like, to specify that a transaction screen X, a transaction screen Y, and a transaction screen Z are required when executing a certain business A (function A). Then, the definition information generating unit 132 generates a mashup API that specifies that the API of the transaction screen Y and the API of the transaction screen Z are successively called after the API of the transaction screen X is read. As an example, the mashup API is defined to request a user who opens an account to input input items in the order of the transaction screen X, the transaction screen Y, and the transaction screen Z. The definition information generating unit 132 may receive a part of the mashup API from an administrator who uses the information processing device 100, via a user interface.

[0068] As described above, the definition information generation unit 132 uses the screen definition information to generate API definitions and mashup APIs in order to use multiple functions that are made public outside the accounting system 200.

[0069] (Specification information generating unit 133) The specification information generating unit 133 generates an API connection condition specification based on the API definition. Specifically, the specification information generating unit 133 generates an API connection condition specification that specifies URLs for referencing each API defined in the API definition in order to use a function to be made public to the outside. For example, the specification information generating unit 133 refers to the API definition, acquires the names of each function to be made public and each API generated for each transaction screen corresponding to each function, and generates an API connection condition specification by associating these with each URL for using each API. The specification information generating unit 133 can also define parameters and designated values ​​of each item according to the API definition in the API connection condition specification.

[0070] Therefore, when an external business device 300 executes an account opening, it can realize a service using the API by specifying the URL of the API corresponding to the account opening. At this time, the business device 300 specifies parameters and values ​​according to the API definition. Note that the generation method can use an OpenAPI Generator such as API documentation.

[0071] (Provider 134) The providing unit 134 provides information on various interfaces. For example, the providing unit 134 provides the API connection condition specification generated by the specification information generating unit 133 to the outside including the business operator device 300. For example, the providing unit 134 can provide the API connection condition specification to the outside by publishing it on the Internet, or can publish the API connection condition specification only to the business operator device 300 with which a contract has been made in advance.

[0072] (Acquisition part 135) The acquisition unit 135 acquires various input information. Specifically, the acquisition unit 135 acquires the input information via an input screen generated based on the API connection condition specification. For example, the acquisition unit 135 converts information input on an input screen provided by the business operator device 300 into a JSON format and acquires the information. Then, the acquisition unit 135 processes the acquired input information as a request JSON indicating a request from a user, as a service collaboration target.

[0073] (Output unit 136) The output unit 136 converts the input information acquired by the acquisition unit 135 into data in a format that can be processed by the accounting system 200 in accordance with the API definition and the mashup API, and outputs the converted data to the accounting system 200.

[0074] In one example, the output unit 136 converts the request JSON received by the acquisition unit 135 into transmission message data in accordance with the API definition and the mashup API. As described above with reference to FIG. 1B, the output unit 136 maps the request JSON 50 to the transmission message data 60 in accordance with the set of API definitions 30 and the mashup API 40. Then, the output unit 136 outputs the transmission message data 60 to the accounting system 200.

[0075] In addition, the output unit 136 receives data in a format that can be processed by the accounting system 200 from the accounting system 200 as a response to the output data, converts the received data into response information in a format corresponding to the input information in accordance with the API definition and the mashup API, and transmits this response information.

[0076] In one example, as described above with reference to FIG. 1B, the output unit 136 transmits the transmission message data 60 to the accounting system 200. Then, the output unit 136 receives reception message data related to the execution result of the function of the accounting system 200 from the accounting system 200. Then, the output unit 136 converts the received reception message data into response JSON. As described above with reference to FIG. 1B, the output unit 136 maps the reception message data 70 to the response JSON 80 in accordance with the set 30 of API definitions. Then, the output unit 136 transmits the response JSON 80 to the request source.

[0077] In addition, the output unit 136 can also determine whether the transmission message data 60, which is in a format that can be processed by the accounting system 200, satisfies specified conditions regarding data input, based on the API definition generated by the definition information generation unit 132 and the mashup API.

[0078] In one example, the output unit 136 refers to the API definition to identify mandatory check target items among the items included in the transmission message data 60. Then, the output unit 136 determines whether the data type and number of digits of each item corresponding to the mandatory check target items are appropriate information specified by the API definition and whether any mandatory items are missing. Then, if the information is appropriate, the output unit 136 outputs the transmission message data 60 to the accounting system 200.

[0079] (An example of function provision processing) Above, the function provision process according to an exemplary embodiment is described with reference to Figures 1A and 1B. Here, the function provision process is described in more detail with reference to Figures 5, 6 and 7.

[0080] FIG. 5 is an explanatory diagram showing an example of an API definition generation process for generating an API definition. As shown in FIG. 5, the definition information generation unit 132 of the control unit 130 generates a set 30 of API definitions from the set 20 of screen definition information. For example, the definition information generation unit 132 generates the set 30 of API definitions, which are a plurality of tables corresponding to the set 20 of screen definition information. For example, the definition information generation unit 132 extracts items such as an item name, an item logical name, a type, a number of digits, a required check target item, and a system logical item name from the screen definition information included in the set 20 of screen definition information, and generates an ID for identifying the item name. Then, the definition information generation unit 132 associates items such as an item logical name, a type, a number of digits, a required check target item, and a system logical item name with an ID for identifying the item name, and generates a table having items associated with this ID.

[0081] Furthermore, the definition information generating unit 132 generates mashup information 25 from the set 20 of screen definition information. Then, the definition information generating unit 132 generates a mashup API 40 from the mashup information 25. The definition information generating unit 132 generates an API connection condition specification 45 based on the set 30 of API definitions and the mashup API 40.

[0082] More specifically, the definition information generating unit 132 generates, from the mashup information 25, a mashup API 40, which is a file that defines the contents of a database corresponding to the mashup information 25. As in the case of the set of API definitions 30, the definition information generating unit 132 generates, from the mashup information 25, a mashup API 40 having a plurality of tables such as "executed transaction", "execution conditions", "default values, setting definitions", "transferred data", and "copy data" described above with reference to FIG. 4. For example, the mashup API 40 defines the order in which each executed transaction is executed. As an example, the mashup API 40 defines that an executed transaction "open account" identified by an executed transaction ID "00010" is executed after an executed transaction "open CIF" identified by an executed transaction ID "00001".

[0083] After the definition information generation unit 132 generates the set of API definitions 30 and the mashup API 40, the specification information generation unit 133 generates an API connection condition specification 45 from the set of API definitions 30 and the mashup API 40. For example, the specification information generation unit 133 automatically generates the API connection condition specification 45 from the set of API definitions 30 and the mashup API 40 using an API documentation technique such as OpenAPI Generator.

[0084] Fig. 6 is an explanatory diagram showing an example of a request JSON reception process for receiving a request JSON. As shown in Fig. 6, the acquisition unit 135 of the control unit 130 acquires the request JSON 50a via a user interface UI created using the API connection condition specification. The user interface UI is, for example, a screen for a financial service developed by a business operator. In this way, the input items on the screen for the financial service are mapped to the items of the request JSON 50a.

[0085] Fig. 7 is an explanatory diagram showing an example of a request JSON conversion process for converting a request JSON into transmission message data. As shown in Fig. 7, the output unit 136 of the control unit 130 maps the request JSON 50 to transmission message data 60 based on the set 30 of API definitions and the mashup API 40. The request JSON 50 includes items such as "cifno":"1234567890". "cifno" is the logical name of the item and corresponds to the key value of the request JSON. Meanwhile, "1234567890" corresponds to the value of the request JSON.

[0086] The output unit 136 converts the JSON interface into a binary format message based on the set 30 of API definitions and the mashup API 40. For example, the output unit 136 maps the values ​​"value V1 '1234567890', value V2 '123456', and value V3 '01'" contained in the request JSON to the values ​​"value V1 '1234567890', value V2 '123456', and value V3 '01'" contained in the transmission message data 60. In the example of FIG. 7, "PT" contained in the transmission message data 60 is a delimiter. Also, "F0001", "F0002", and "F0003" contained in the transmission message data 60 are system logical item names. In this way, the output unit 136 maps data associated with alphabetical item names used in the JSON interface to legacy format message data and outputs it to the accounting system 200.

[0087] [3. Function provision processing flow] Next, a procedure of a function providing process performed by the information processing device 100 according to the embodiment will be described with reference to FIGS. 8, 9, and 10. FIG.

[0088] FIG. 8 is a flowchart showing an example of a process for providing the functions of the accounting system 200, which is executed by the information processing device 100 according to the embodiment.

[0089] As shown in FIG. 8, first, the information processing device 100 (for example, the definition information generating unit 132) generates an API definition based on the screen definition information (step S101).

[0090] Next, the information processing device 100 (e.g., the specification information generating unit 133, the providing unit 134) generates and provides an API connection condition specification based on the generated API definition, etc. (step S102). For example, the information processing device 100 provides the generated API connection condition specification to the business device 300.

[0091] Next, the information processing device 100 (for example, the acquisition unit 135) receives the request JSON via an application developed using the generated API connection condition specification (step S103). For example, the information processing device 100 receives the request JSON from the business device 300 via an application developed using a JSON interface.

[0092] Next, the information processing device 100 (e.g., the output unit 136) transmits and receives electronic data to and from the accounting system 200 based on the received request JSON (step S104). The transmission and reception of electronic data to and from the accounting system 200 based on the request JSON will be described in detail below with reference to FIG. 9.

[0093] Next, the information processing device 100 (e.g., the output unit 136) converts the message data received from the accounting system 200 into response JSON (step S105). The conversion of the message data received from the accounting system 200 into response JSON will be described in detail below with reference to FIG. 10.

[0094] Next, the information processing device 100 (for example, the output unit 136) transmits the response JSON to the business device 300 (Step S106).

[0095] FIG. 9 is a flowchart showing an example of processing for transmitting and receiving electronic data to and from the accounting system 200 based on the request JSON, which is executed by the information processing device 100 according to the embodiment.

[0096] 9, first, the information processing device 100 (e.g., the output unit 136) reads the mashup API (step S201). For example, the information processing device 100 acquires the mashup API from the API connection condition specification storage unit 124 described above with reference to FIG.

[0097] Next, the information processing device 100 acquires the JSON data by storing the received request JSON in memory (step S202).

[0098] Next, the information processing device 100 reads the API definition (step S203). For example, the information processing device 100 acquires the API definition from the API definition storage unit 123 described above with reference to FIG.

[0099] Next, the information processing device 100 acquires item information from the API definition (step S204). For example, the information processing device 100 acquires item information (for example, item name, item logical name, type, number of digits, required check target item, system logical item name) corresponding to the screen definition information described above with reference to FIG.

[0100] Next, the information processing device 100 determines whether the item logical name of the acquired item information matches the key value of the acquired JSON data (step S205). The key value of the JSON data is, for example, a key such as "cifno" (i.e., the first key) included in the request JSON 50 described above with reference to FIG. 7.

[0101] When it is determined that the item logical name of the item information matches the key value of the JSON data (step S205: Yes), the information processing device 100 acquires a system logical item name from the item information (step S206). The system logical item name is, for example, an item name such as "F0001", "F0002", "F0003", etc., included in the screen definition information described above with reference to FIG.

[0102] Next, the information processing device 100 constructs transmission message data based on the acquired system logical item name and the value associated with the key value of the JSON data (step S207). The value associated with the key value of the JSON data is a value such as "1234567890", "123456", "01", etc., included in the request JSON 50 described above with reference to FIG.

[0103] Next, the information processing device 100 determines whether other API definition items remain (step S208). If it is determined that other API definition items remain (step S208: Yes), the processing procedure returns to step S205. In this case, the information processing device 100 executes step S205 again for the other API definition items.

[0104] In step S205, when it is determined that the item logical name of the item information does not match the key value of the JSON data (step S205: No), the information processing device 100 determines whether a default value definition is in the mashup API (step S209). The default value definition is, for example, a value such as "Subject=Normal", "Tax=Separate Taxation", or "Subject=Normal" included in the mashup information described above with reference to FIG.

[0105] If it is determined that the default value definition exists in the mashup API (step S209: Yes), the information processing device 100 sets the default value in the area for the transmitted message data (step S210).

[0106] If it is determined that the default value definition is not in the mashup API (step S209: No), the information processing device 100 determines whether the copy value definition is in the mashup API (step S211). The copy value definition is, for example, a value corresponding to the item logical name of the item information used in the executed transaction identified by the "copy source transaction ID" included in the mashup information described above with reference to FIG. 4.

[0107] If it is determined that the copy value definition is in the mashup API (step S211: Yes), the information processing device 100 sets the copy value in the area for the transmission message data (step S212). If it is determined that the copy value definition is not in the mashup API (step S211: No), the processing procedure proceeds to step S208.

[0108] If it is determined in step S208 that no other API definition items remain (step S208: No), the information processing device 100 determines whether other JSON data items remain in the JSON data (step S213). The other JSON data items are, for example, keys such as "tenban" (i.e., the second key) included in the request JSON 50 described above with reference to FIG. 7. If it is determined that other JSON data items remain in the JSON data (step S213: Yes), the processing procedure returns to step S204. In this case, the information processing device 100 executes step S204 again for the other JSON data items.

[0109] If it is determined that no other JSON data items remain in the JSON data (step S213: No), the information processing device 100 checks the items of the transmission message data (step S214). For example, the information processing device 100 refers to the API definition and checks the type and number of digits of the transmission message data.

[0110] Next, the information processing device 100 transmits the transmission message data to the accounting system 200 (step S215).

[0111] Next, the information processing device 100 receives and stores the received message data from the accounting system 200 (step S216). For example, the information processing device 100 stores the received message data in a predetermined storage area (for example, a memory, a solid state drive (SSD)) in the storage unit 120. In this manner, the information processing device 100 holds the received message data.

[0112] Next, the information processing device 100 determines whether other executed transactions remain in the JSON data (step S217). The other executed transactions are, for example, other executed transactions identified by the "executed transaction ID" included in the mashup information described above with reference to Fig. 4. For example, the first executed transaction may be a CIF opening, and the second executed transaction may be an account opening.

[0113] If it is determined that other executed transactions remain in the JSON data (step S217: Yes), the processing procedure returns to step S203. In this case, the information processing device 100 executes step S203 again for the other executed transactions. If it is determined that other executed transactions do not remain in the JSON data (step S217: No), the processing procedure ends. Note that the information processing device 100 may refer to the mashup API and set the handover data to the received message data or the received message data. The handover data is, for example, data such as the handover item names included in the mashup information described above with reference to FIG. 4. In this manner, the information processing device 100 may update the transmitted message data.

[0114] FIG. 10 is a flowchart showing an example of a process for converting message data received from the accounting system 200 into response JSON, which is executed by the information processing device 100 according to the embodiment.

[0115] First, the information processing device 100 (for example, the output unit 136) acquires stored response message data (step S301). For example, the information processing device 100 acquires the response message data from a predetermined storage area in the storage unit 120.

[0116] Next, the information processing device 100 reads the API definition (step S302). For example, the information processing device 100 acquires the API definition from the API definition storage unit 123 described above with reference to FIG.

[0117] Next, the information processing device 100 acquires the first item information from the API definition (step S303).

[0118] Next, the information processing device 100 extracts the second item information from the response message data (step S304).

[0119] Next, the information processing device 100 determines whether the system logical item name of the first item information matches the system logical item name of the second item information (step S305).

[0120] When it is determined that the system logical item name of the first item information matches the system logical item name of the second item information (step S305: Yes), the information processing device 100 acquires the logical item name from the API definition (step S306).

[0121] Next, the information processing device 100 sets the system logical item name and the data of the item information in the area for the response JSON (step S307). For example, the information processing device 100 merges the system logical item name and the data of the item information into the JSON data.

[0122] Next, the information processing device 100 determines whether other API definition items remain in the response message data (step S308). If it is determined that other API definition items remain in the response message data (step S308: Yes), the processing procedure returns to step S305. In this case, the information processing device 100 executes step S305 again for the other API definition items.

[0123] In step S305, if it is determined that the system logical item name of the first item information does not match the system logical item name of the second item information (step S305: No), the process proceeds to step S308.

[0124] In step S308, if it is determined that no other API definition items remain in the response message data (step S308: No), the information processing device 100 determines whether any other response message data items remain in the response message data (step S309).

[0125] If it is determined that other response message data items remain in the response message data (step S309: Yes), the process returns to step S303. In this case, the information processing device 100 executes step S303 again for the other response message data items. If it is determined that other response message data items do not remain in the response message data (step S309: No), the process ends.

[0126] [4. Other] In addition, among the processes described in the above embodiments, some of the processes described as being performed automatically can be performed manually. Alternatively, all or some of the processes described as being performed manually can be performed automatically using a known method. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed arbitrarily unless otherwise specified. For example, the various information shown in each drawing is not limited to the illustrated information.

[0127] In addition, each component of each device shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc.

[0128] 2 may be held in a storage server or the like instead of being held by the information processing device 100. In this case, the information processing device 100 accesses the storage server to acquire various information such as screen definition information and mashup information.

[0129] [5. Hardware Configuration] The information processing device 100 according to the embodiment described above is realized by a computer 1000 having a configuration as shown in Fig. 11, for example. Fig. 11 is a diagram showing an example of a hardware configuration. The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which a calculation device 1030, a primary storage device 1040, a secondary storage device 1050, an output IF (Interface) 1060, an input IF 1070, and a network IF 1080 are connected by a bus 1090.

[0130] The arithmetic device 1030 operates based on programs stored in the primary storage device 1040 and the secondary storage device 1050 and programs read from the input device 1020, and executes various processes. The primary storage device 1040 is a memory device, such as a RAM, that temporarily stores data used by the arithmetic device 1030 for various calculations. The secondary storage device 1050 is a storage device in which data used by the arithmetic device 1030 for various calculations and various databases are registered, and is realized by a ROM (Read Only Memory), a HDD (Hard Disk Drive), a flash memory, or the like.

[0131] The output IF 1060 is an interface for transmitting information to be output to an output device 1010 that outputs various types of information, such as a monitor or a printer, and is realized by a connector conforming to a standard such as USB (Universal Serial Bus), DVI (Digital Visual Interface), or HDMI (registered trademark) (High Definition Multimedia Interface). The input IF 1070 is an interface for receiving information from various input devices 1020, such as a mouse, keyboard, and scanner, and is realized by a USB, for example.

[0132] The input device 1020 may be a device that reads information from, for example, an optical recording medium such as a CD (Compact Disc), a DVD (Digital Versatile Disc), or a PD (Phase change rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory. The input device 1020 may also be an external storage medium such as a USB memory.

[0133] The network IF 1080 receives data from other devices via the network N and sends it to the arithmetic device 1030, and also transmits data generated by the arithmetic device 1030 to other devices via the network N.

[0134] The arithmetic unit 1030 controls the output device 1010 and the input device 1020 via the output IF 1060 and the input IF 1070. For example, the arithmetic unit 1030 loads a program from the input device 1020 or the secondary storage device 1050 onto the primary storage device 1040 and executes the loaded program.

[0135] For example, when the computer 1000 functions as the information processing device 100 , the arithmetic unit 1030 of the computer 1000 executes a program loaded onto the primary storage device 1040 to realize the functions of the control unit 130 .

[0136] As described above, the information processing device 100 according to the embodiment includes the definition information generating unit 132 , the acquiring unit 135 , and the output unit 136 .

[0137] In the information processing device 100 according to the embodiment, the definition information generation unit 132 generates function definition information related to the functions of the accounting system 200 to be provided to the outside, using screen definition information related to the screen definitions of each of a plurality of transaction screens used in the accounting system 200. Also, in the information processing device 100 according to the embodiment, the acquisition unit 135 acquires input information via an input screen generated based on the function definition information. Also, in the information processing device 100 according to the embodiment, the output unit 136 converts the input information into data in a format processable by the accounting system 200 in accordance with the function definition information, and outputs the converted data to the accounting system 200.

[0138] In addition, in the information processing device 100 of the embodiment, the definition information generation unit 132 uses the screen definition information to generate function definition information including definition information of an application interface based on input items that accept input of information necessary for executing a function on a transaction screen corresponding to a function to be provided to the outside.

[0139] In addition, in the information processing device 100 according to the embodiment, the definition information generation unit 132 uses the screen definition information to generate function definition information that defines the behavior of the application interface and includes mash definition information that defines the transition of the input screen required when the function is executed.

[0140] In addition, the information processing device 100 according to the embodiment has a specification information generation unit 133 that generates a specification of connection conditions that a user who uses a function provided externally refers to when using the application interface, based on definition information of the application interface.

[0141] In addition, in the information processing device 100 according to the embodiment, the output unit 136 determines, based on the function definition information generated by the definition information generation unit 132, whether the data acquired via the input screen and converted into a format processable by the accounting system 200 satisfies the conditions necessary for executing the function to be provided to the outside, and outputs the data to the accounting system 200 if the conditions are satisfied.

[0142] In addition, in the information processing device 100 according to the embodiment, the output unit 136 receives response data in a format that can be processed by the accounting system 200 from the accounting system 200 as a response to the data, converts the response data into response information in a format corresponding to the input information according to the function definition information, and transmits the response information.

[0143] In addition, in the information processing device 100 according to the embodiment, the function of the accounting system 200 provided to the outside is one of the multiple functions of the accounting system 200 provided to the outside, and the definition information generating unit 132 uses the screen definition information to generate multiple function definition information related to the multiple functions of the accounting system 200 to be provided to the outside, together with function definition information related to a function combination, which is function definition information for combining and executing the multiple functions. In addition, in the information processing device 100 according to the embodiment, the acquisition unit 135 acquires input information corresponding to the multiple function definition information generated by the definition information generating unit 132. In addition, in the information processing device 100 according to the embodiment, the output unit 136 converts the input information acquired by the acquisition unit 135 into data in a format that can be processed by the accounting system 200 in accordance with the multiple function definition information and the function definition information related to the function combination generated by the definition information generating unit 132, outputs the converted data to the accounting system 200, and outputs new data to the accounting system 200 by applying a response to the output data to the multiple function definition information and the function definition information related to the function combination.

[0144] Through each of the above-mentioned processes, the information processing device 100 can improve the convenience of the accounting system 200.

[0145] Although some of the embodiments of the present application have been described in detail above with reference to the drawings, these are merely examples, and the present invention can be embodied in other forms that include various modifications and improvements based on the knowledge of those skilled in the art, including the forms described in the disclosure of the invention. In addition, the present invention has the effect of improving the convenience of the accounting system for users other than banks, thereby enabling the creation of new services. In addition, the functions of the accounting system can be reused in various channels, which reduces the development costs associated with building new services and improves the development speed.

[0146] Moreover, the above-mentioned "section, module, unit" can be read as "means" or "circuit", etc. For example, an output section can be read as output means or an output circuit. [Explanation of symbols]

[0147] 1 Service integration system 100 Information processing device 110 Communications Department 120 Storage section 121 Screen definition information storage section 122 Mashup information storage unit 123 API definition storage 124 API connection condition specification memory section 130 Control section 131 Collection Department 132 Definition information generation section 133 Specification information generation unit 134 Provision Department 135 Acquisition Department 136 Output section 200 Accounting Systems 300 Operator equipment 400 User device

Claims

1. a definition information generating unit that generates function definition information related to functions of the accounting system to be provided to an external party, using screen definition information related to screen definitions of each of a plurality of transaction screens used in the accounting system; an acquisition unit that acquires input information via an input screen generated based on the function definition information; an output unit that converts the input information into data in a format that can be processed by the accounting system in accordance with the function definition information, and outputs the converted data to the accounting system; Equipped with The definition information generating unit generates the function definition information including definition information of an application interface based on an input item that receives an input of information necessary for executing the function on a transaction screen corresponding to the function to be provided to the outside, using the screen definition information.

23. An information processing apparatus comprising:

2. The definition information generating unit generates the function definition information, using the screen definition information, which is definition information that defines the behavior of the application interface and includes mash definition information that defines a transition of an input screen required when the function is executed.

2. The information processing apparatus according to claim 1,

3. The system further includes a specification information generating unit that generates, based on definition information of the application interface, a specification of connection conditions to be referred to by a user utilizing the function provided to the outside when using the application interface.

2. The information processing apparatus according to claim 1,

4. The output unit determines whether or not the data acquired via the input screen and converted into a format processable by the accounting system satisfies a condition necessary for executing the function to be provided to the outside, based on the function definition information generated by the definition information generation unit, and outputs the data to the accounting system if the condition is satisfied.

4. The information processing device according to claim 1, wherein the information processing device is a computer.

5. The output unit receives, as a response to the data, response data in a format that can be processed by the accounting system from the accounting system, converts the response data into response information in a format that corresponds to the input information in accordance with the function definition information, and transmits the response information.

5. The information processing apparatus according to claim 1, wherein the information processing apparatus further comprises:

6. The definition information generating unit generates the function definition information, which includes application interface definition information including definition information regarding each of a plurality of application interfaces, and the mash definition information including definition information regarding the order of execution transactions executed by each of the plurality of application interfaces, using each screen definition information of each transaction screen used in each of the plurality of functions to be provided to the outside; the acquiring unit acquires the input information via the input screen using any one of the plurality of application interfaces; The output unit repeats the process of converting the input information into transmission message data that can be processed by the accounting system and outputting the converted transmission message data to the accounting system in accordance with definition information of an application interface corresponding to the order, until all executed transactions are executed in accordance with the order defined by the mash definition information.

3. The information processing apparatus according to claim 2.

7. The computer generating function definition information relating to functions of the accounting system to be provided to an external party using screen definition information relating to screen definitions of each of a plurality of transaction screens used in the accounting system; acquiring input information via an input screen generated based on the function definition information; converting the input information into data in a format that can be processed by the accounting system in accordance with the function definition information, and outputting the converted data to the accounting system; Including processing, The generating process uses the screen definition information to generate the function definition information including definition information of an application interface based on input items that accept input of information necessary for executing the function on a transaction screen corresponding to the function to be provided to the outside.

23. An information processing method comprising:

8. On the computer, generating function definition information relating to functions of the accounting system to be provided to an external party using screen definition information relating to screen definitions of each of a plurality of transaction screens used in the accounting system; acquiring input information via an input screen generated based on the function definition information; converting the input information into data in a format that can be processed by the accounting system in accordance with the function definition information, and outputting the converted data to the accounting system; Execute the process, The generating process uses the screen definition information to generate the function definition information including definition information of an application interface based on input items that accept input of information necessary for executing the function on a transaction screen corresponding to the function to be provided to the outside.

2. An information processing program comprising:

Images