Information processing system, information processing method, and program

Abstract

This invention provides an information processing system, method, and program that appropriately supplements the items necessary for processing remittances for invoices. [Solution] The supplementary system 10 includes an invoice information acquisition unit 120 that acquires invoice information from a predetermined system, which includes item information indicating at least one item relating to a claim for payment to a target payee; a missing item determination unit 130 that identifies the necessary items for enabling remittance processing to a payment service provider by referring to an item requirement database stored for each payment service provider and determines whether or not there are missing items; a supplementary information determination unit 140 that, if it is determined that there are missing items, refers to a payment-related database stored for each payee to determine whether or not there is supplementary information corresponding to the missing items in the payment-related information of the payee included in the invoice information; and a payment information generation unit 160 that, if it is determined that there is supplementary information, adds the supplementary information to the invoice information and generates payment information for executing remittance processing.

Description

Technical Field

[0001] The present invention relates to an information processing system, an information processing method, and a program.

Background Art

[0002] An information processing apparatus that executes a remittance process based on text data read from a claim by OCR (Optical Character Recognition) processing is disclosed (for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The information processing apparatus described in Patent Document 1 classifies text data generated by OCR processing for each description item of the claim to generate classified text data. The information processing apparatus determines whether there are items necessary for performing a remittance process on the claim based on the classified text data. When the information processing apparatus determines that all necessary items are present, it generates payment data for performing a remittance process on the claim. On the other hand, when the information processing apparatus determines that some of the necessary items are missing, it generates payment data by complementing some of the necessary missing items using payment performance data.

[0005] However, in the information processing apparatus described in Patent Document 1, since it is complemented using payment performance data, there is a problem that necessary items cannot be appropriately complemented in cases where there is no payment performance in the first place.

[0006] Therefore, the present invention aims to appropriately supplement the items necessary for processing remittances for invoices. [Means for solving the problem]

[0007] An information processing system according to one aspect of the present invention includes: an invoice information acquisition unit that acquires invoice information including item information indicating at least one item relating to a claim for payment to a target payee from a predetermined system; a missing item determination unit that identifies the necessary items of a payment business included in the invoice information by referring to an item requirement database stored for each payment business, which contains necessary items that are items necessary to enable remittance processing to a payment business, and determines whether or not there are missing items among the items included in the necessary items that are not included in the item information; a supplementary information determination unit that, when it is determined that there are missing items, refers to a payment-related database stored for each payee, which contains payment-related information relating to payments to payees, and determines whether or not there is supplementary information corresponding to the missing items in the payment-related information of the target payee included in the invoice information; and a payment information generation unit that, when it is determined that there is supplementary information, adds the supplementary information to the invoice information to generate payment information for executing the remittance processing.

[0008] An information processing method according to one aspect of the present invention involves a computer obtaining invoice information from a predetermined system, which includes item information indicating at least one item relating to a claim for payment to a target payee; identifying the necessary items of a payment service provider included in the invoice information by referring to an item requirements database stored for each payment service provider, which is an item necessary to enable the execution of a remittance process to a payment service provider; determining whether there are any missing items among the necessary items that are not included in the item information; if it is determined that there are missing items, the computer refers to a payment-related database stored for each payee, which is payment-related information relating to payments to payees, to determine whether there is supplementary information corresponding to the missing items in the payment-related information of the target payee included in the invoice information; and if it is determined that there is supplementary information, the computer adds the supplementary information to the invoice information to generate payment information for executing the remittance process.

[0009] A program according to one aspect of the present invention causes a computer to perform the following actions: obtain invoice information from a predetermined system, which includes item information indicating at least one item relating to a claim for payment to a target payee; identify the necessary items of a payment service provider included in the invoice information by referring to an item requirement database stored for each payment service provider, which is an item necessary to enable the execution of a remittance process to a payment service provider; determine whether there are any missing items among the necessary items that are not included in the item information; if it is determined that there are missing items, refer to a payment-related database stored for each payee, which is payment-related information relating to payments to payees, to determine whether there is supplementary information corresponding to the missing items in the payment-related information of the target payee included in the invoice information; and if it is determined that there is supplementary information, add the supplementary information to the invoice information to generate payment information for executing the remittance process. [Effects of the Invention]

[0010] According to the present invention, it is possible to appropriately supplement the items necessary for processing remittances for invoices. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows an example of the configuration of a complementary system. [Figure 2] This figure shows an example of the item requirements database D111. [Figure 3] This figure shows an example of the payment-related database D112. [Figure 4] This is a diagram showing an example of the payment history database D113. [Figure 5] This is a diagram showing an example of the fee database D114. [Figure 6] This is a flowchart showing the processing procedure for the complementary system 10. [Figure 7] This diagram shows the process of generating payment information by adding supplementary information to invoice information. [Figure 8] This figure shows an example of a computer hardware configuration. [Modes for carrying out the invention]

[0012] ===Complementary System 10=== <<Overview of the structure>> Referring to Figure 1, an overview of the configuration of the complementary system 10 according to this embodiment will be described. Figure 1 is a diagram showing an example of the configuration of the complementary system 10.

[0013] The supplementary system 10 is a system that, when the payment invoice data (hereinafter referred to as "invoice information") is missing items (hereinafter referred to as "necessary items") required for the payment system 400 of a payment service provider such as a financial institution to process the remittance for the invoice (hereinafter referred to as "remittance processing"), supplements the invoice information with the missing items (hereinafter referred to as "missing items") to generate data (hereinafter referred to as "payment information") that allows the payment system 400 to process the remittance (for example, the processing of settlement in the payment system 400). The necessary items differ for each payment service provider. Necessary items usually include multiple items, but may also include only one item. In other words, there is no particular limit to the number of items that can be considered as necessary items.

[0014] As a result, when necessary items are not included in the invoice information, the supplementary system 10 can appropriately supplement the missing items in the invoice information without requiring manual verification and addition of items, thereby enabling the payment system 400 to properly execute the remittance process.

[0015] Here, we will explain an example of a situation that the complementary system 10 aims to solve. In recent years, in inter-company transactions, invoices are issued by numerous trading partners (payees). Payment processing is then carried out based on these issued invoices. The information on the invoices differs depending on the trading partner that issued the invoice, including the content of the items. Furthermore, payment processing needs to support multiple payment methods such as bank transfers and credit card payments, and the information items required for each payment method differ from one another. In addition, the required and optional items may differ depending on the financial institution such as banks and credit card companies, or the payment service provider.

[0016] Thus, in the invoice information, there coexist differences in items due to differences in the issuer and differences in necessary items due to differences in payment methods or financial institutions. Therefore, there may be missing items in the invoice information that lack the information (necessary items) required for payment processing in financial institutions or payment service providers. In a system that enables seamless execution of payment processing with multiple payment methods or multiple financial institutions, the existence of such missing items hinders the automation and efficiency of payment processing, leading to additional confirmation work and manual input work, and significantly reducing business efficiency.

[0017] Particularly, in an operator who contracts with a variety of trading partners and connects multiple payment systems to provide services, the problem of missing items is likely to become apparent. Since this problem relates to the core of corporate operations such as the stability of payment processing, the continuity of service provision, payment risk management, and the consistency of accounting processing, it is an extremely important issue.

[0018] In this embodiment, in view of the above background, it is possible to solve the problem of missing items in invoice information caused by differences in the issuer or differences in payment methods or financial institutions, and to achieve seamless payment processing.

[0019] The complementary system 10 includes, for example, a complementary device 100, an operator device 200, an accounting system 300, and a payment system 400.

[0020] The complementary device 100 is a device that complements missing items in invoice information. The complementary device 100 may be connected to, for example, a plurality of operator devices 200, a plurality of accounting systems 300, and a plurality of payment systems 400, respectively.

[0021] The operator device 200 is, for example, a device that transmits invoice information regarding payments from a predetermined operator (hereinafter referred to as the "payer") to another operator (hereinafter referred to as the "payee") to the complementary device 100. The operator device 200 may be the device of the payer or may be a device that mediates the issuance of invoices at the request of the payer.

[0022] The payer is, for example, the person making the payment in the case of an invoice. The payee is, for example, the person receiving the payment in the case of an invoice.

[0023] The accounting system 300 is a system that enables certified public accountants and tax accountants to perform accounting processing (hereinafter referred to as "accounting processing") on invoice information and payment information described later, for example, by accessing the supplementary device 100.

[0024] The payment system 400 is a system that enables a payment service provider to process a payment for the invoice information indicated by the invoice information, for example, by accessing the supplementary device 100, by transferring funds to the payee's account (including processing payments based on a bank transfer request from the payer). The payment method in the payment system 400 is not limited to bank transfers, but may also be electronic payment methods such as credit card payments or digital currency payments. Furthermore, if multiple payment systems 400 are connected to the supplementary device 100, the payment methods of each payment system 400 may be partially or entirely different.

[0025] For convenience, in the following, payment information linked to invoice information will be referred to as "payment information." Furthermore, information resulting from accounting processing applied to invoice information will be referred to as "journal entry information."

[0026] The complementary device 100, the operator device 200, the accounting system 300, and the payment system 400 may be, but are not limited to, cloud computing, server computers, personal computers (but are not limited to, desktops, laptops, tablets, etc.), media computer platforms (e.g., cable, satellite set-top boxes, digital video recorders), handheld computer devices (e.g., PDAs (Personal Digital Assistants), email clients, etc.), or other types of computers or communication platforms.

[0027] <<Process Overview>> Next, with reference to Figure 1, an overview of the processing of the complementary system 10 will be described. The complementary system 10 according to this embodiment is a system that can seamlessly perform processes such as receiving invoice information, issuing payment instructions, executing settlements, and recording journal entries, for example, by coordinating with the settlement system 400 and the accounting system 300 that performs accounting processing.

[0028] In step S10, the supplementary device 100 obtains invoice information from the business device 200, for example, through a business that performs OCR processing on invoices.

[0029] Invoice information is, for example, text data obtained by processing image data of an invoice using OCR (Optical Character Recognition). Invoice information includes, for example, information indicating multiple item names included in the invoice, and text data corresponding to each of those item names (hereinafter referred to as "item data"). Hereinafter, for convenience, the information indicating item names and the item data will be collectively referred to as "item information".

[0030] The item information may include identifying information that can identify the payee of the invoice (hereinafter referred to as the "payee") (hereinafter referred to as "payee identifying information"). The item information may also include identifying information that can identify the payer (hereinafter referred to as the "payer identifying information"). Thus, the item information consists of multiple data items that constitute information regarding payments related to the payee listed on the invoice. The item information may include, for example, payee information, invoice amount, invoice number, payment due date, and bank transfer information. However, the content of the item information on an invoice may differ depending on the invoice issuer (payee).

[0031] The target payee identification information refers to information that indicates at least one of the following: the business registration number of the target payee (hereinafter referred to as the "target payee business registration number") and the account information of the target payee (hereinafter referred to as the "target payee account information"). In other words, the target payee identification information is information that can uniquely identify the target payee.

[0032] The recipient account information includes, for example, the recipient's bank code, branch code, account number, account type, and account holder name.

[0033] The target payer identification information refers to information that indicates at least one of the following: the business registration number of the target payer (hereinafter referred to as the "target payer business registration number") and the account information of the target payer (hereinafter referred to as the "target payer account information"). In other words, the target payer identification information is information that can uniquely identify the target payer.

[0034] The target payer account information includes, for example, the bank code, branch code, account number, account type, and account holder name of the target payer.

[0035] In step S11, the supplementary device 100 refers to the item requirements database D111, described later, and identifies a payment service provider (hereinafter referred to as the "specified payment service provider") that will execute the remittance process, for example, based on the bank name and bank code. The supplementary device 100 determines whether the necessary items for enabling the remittance process to be executed in the payment system 400 of the specified payment service provider are included in the invoice information. That is, the supplementary device 100 determines whether the necessary items are included in the item information. Then, the supplementary device 100 identifies the missing items, which are the necessary items that are not included in the invoice information.

[0036] In step S12, the supplementary device 100 refers to the payment-related database D112, which will be described later, and determines whether or not there is supplementary information corresponding to the missing item based on the target payee identification information.

[0037] In step S13, if the supplementary device 100 determines that there is no supplementary information in the payment-related database D112, it refers to the payment history database D113 (described later) and identifies information indicating past payment history to the target payee (hereinafter referred to as "past performance information") based on the target payee identification information. The supplementary device 100 identifies supplementary information based on the identified past performance information.

[0038] In step S14, the supplementary device 100 adds supplementary information to the invoice information to generate information that can be used by the specified payment service provider to perform remittance processing (hereinafter referred to as "payment information"). The supplementary device 100 sends a remittance request (for example, a request to perform settlement to the account of the target payee) along with the payment information to the payment system 400 of the specified payment service provider. Alternatively, the supplementary device 100 may send a remittance request to the payment system 400 without sending the payment information. In this case, the payment system 400 may access the payment information from the supplementary device 100 and perform the remittance processing.

[0039] This enables the complementary system 10 to appropriately generate payment information corresponding to the invoice information, thereby allowing the payment system 400 of the specified payment service provider to quickly execute the remittance process for the invoice.

[0040] ===Complementary Device 100=== Referring to Figure 1, the functional configuration of the complementary device 100 will be described.

[0041] The supplementary device 100, for example, interacts with at least one payment system 400 and at least one accounting system 300 (e.g., via API). Based on the invoice information, the supplementary device 100 generates payment information that can be used to transfer funds to the payment system 400 of a specific payment service provider. In doing so, if the invoice information does not include the necessary items, the supplementary device 100 performs a process to add those items.

[0042] As shown in Figure 1, the supplementary device 100 includes, for example, a storage unit 110, an invoice information acquisition unit 120, a missing item determination unit 130, a supplementary information determination unit 140, a performance determination unit 150, a payment information generation unit 160, and an information transmission unit 170.

[0043] The storage unit 110 may include, for example, an item requirements database D111, a payment-related database D112, a payment history database D113, and a fee database D114.

[0044] Refer to Figure 2 to explain the item requirements database D111. Figure 2 shows an example of the item requirements database D111. The item requirements database D111 is a database used by the supplementary device 100 to determine whether or not the invoice information contains the necessary items.

[0045] As shown in Figure 2, the item requirements database D111 includes items such as [Payment service provider identification information] and [Required items].

[0046] The [Payment Service Provider Identification Information] field stores identification information (hereinafter referred to as "Payment Service Provider Identification Information") that can identify the payment system 400 of the payment service provider. The Payment Service Provider Identification Information can be any information that can identify the financial institution that is the payment service provider, such as a bank code or the name of the bank.

[0047] The [Required Items] section contains the necessary information required to process a remittance to a payment service provider. Specifically, required items include, for example, "Invoice Number," "Business Registration Number," "Payee Account Number," "Payee Account Information," and "Fee Burden Category." Payee account information includes, for example, bank code, branch code, account type, and account holder name.

[0048] Referring to Figure 3, the payment-related database D112 will be described. Figure 3 is a diagram showing an example of the payment-related database D112. The payment-related database D112 is a database for identifying supplementary information to be added to the invoice information in the supplementary device 100.

[0049] As shown in Figure 3, the payment-related database D112 includes items such as [Payee Business Registration Number], [Payee Account Number], [Payee Account Information], [Fee Burden Category], and [Discounted Payment Account].

[0050] The [Payee Business Registration Number] field stores the payee business registration number. The [Payee Account Number] field stores the account number of an account to which the payee can make payments. The account number may be, for example, a bank account number or an identification code for a money transfer service provider's account. The [Payee Account Information] field stores information indicating the payee's bank code (e.g., "0001"), branch code (e.g., "001"), account type (e.g., "Savings"), account holder name (e.g., "TARO YAMADA"), etc. (hereinafter referred to as "Payee Account Information"). The [Fee Burden Classification] field stores information indicating whether the payee or the payer bears the fees required for the transfer from the payer to the payee (hereinafter referred to as "Fee Burden Classification Information"). The [Payer's Low-Cost Account] field stores the account number of the payer's account that has the lowest fees in relation to the payee's account number (hereinafter referred to as "Payer's Low-Cost Account").

[0051] In the following, "payee identification information" refers to at least one of the payee business registration number and payee account information. In other words, payee identification information is information that can uniquely identify a payee.

[0052] Furthermore, in the following, the information stored in each of the following items—[Payee Account Number], [Payee Account Information], [Fee Burden Category], and [Discounted Payment Source Account]—is collectively referred to as "Payment-Related Information." Payment-related information is, for example, master information of the payee. Payment-related information may also be, for example, basic information that does not differ from invoice to invoice and is uniquely determined for the payee of an invoice. In this way, payment-related database D112 stores payment-related information for each payee. Note that the payee is registered in advance. Registered in advance means that it is registered before the payment process is executed. Registration may occur, for example, when a new payee is added, and may be done by manual input or automatic input.

[0053] Referring to Figure 4, the payment history database D113 will be described. Figure 4 is a diagram showing an example of the payment history database D113. The payment history database D113 is a database for identifying supplementary information to be added to invoice information in the supplementary device 100. The payment history database D113 stores the history of remittance processing performed based on payment information that has the necessary items. In other words, the payment history database D113 stores information about the necessary items (information that can become supplementary information).

[0054] As shown in Figure 4, the payment history database D113 includes items such as [Payee Business Registration Number], [Payee Account Number], [Payee Account Information], [Payment Date and Time], [Payer], [Payee], [Fee Burden Category], [Payer Account Holder], and [Supplementary History].

[0055] The [Payee Business Registration Number] field stores the payee business registration number. The [Payee Account Number] field stores the account number of the account to which the payment was sent to the payee. The account number may be, for example, a bank account number or an identification code for a money transfer service provider's account. The [Payee Account Information] field stores payee account information such as the bank code, branch code, account type, and name of the target payee. The [Payment Time] field stores information indicating the time (e.g., date and time) when the payment was sent from the payer to the payee in the past (hereinafter referred to as "payment time information"). The [Payer] field stores identification information that can identify the payer (e.g., business registration number, company name, etc.). The [Payee] field stores information indicating the payee (e.g., business registration number, company name, etc.). The [Fee Burden Classification] field stores information indicating whether the fee required for the transfer from the payer to the payee was borne by the payee or the payer. The [Discounted Payment Account] field stores the account number of the discounted payment account. The [Supplement History] field stores at least information indicating whether or not payment information was generated by adding supplemental information to the invoice information (e.g., the number of times and date of supplementation), and information about the supplemental information that was added (e.g., information indicating the items that were supplemented).

[0056] In the following, the information stored in each of the following fields—[Payee Account Information], [Payment Date and Time], [Payer], [Payee], [Fee Burden Category], and [Payer Discount Account]—is collectively referred to as past performance information for payments to the target payee. Thus, the payment performance database D113 stores past performance information for each billing transaction where a remittance process was actually executed based on the payment information. Note that a billing transaction may be an invoice unit or a payment unit that combines multiple invoices. For example, the past performance information for each billing transaction is stored in association with the billing ID (e.g., invoice number).

[0057] Although it has been explained that payment-related database D112 and payment history database D113 are separate databases, this is not limited to that. Payment-related database D112 and payment history database D113 may be composed of a single database.

[0058] Refer to Figure 5 to explain the fee database D114. Figure 5 is a diagram showing an example of the fee database D114. The fee database D114 is a database for identifying the undervalued payment source account for the recipient account.

[0059] As shown in Figure 5, the fee database D114 includes, for example, the following items: [Payer Information], [Upper and Lower Limits], and [Fee].

[0060] The [Payer Information] field stores information indicating the "Paying Institution Name" and "Payee Classification." "Paying Institution Identification Information" is information that identifies the financial institution (such as a bank or money transfer service provider) that provides the payer's account (e.g., bank code, bank name, or money transfer service provider name). "Payee Classification" is information that indicates the relationship between the financial institution of the account used by the payer and the financial institution of the account used by the payee. This relationship information could indicate, for example, that the financial institutions of the payer and payee are the same bank, the same branch, different financial institutions, or different branches.

[0061] The [Upper and Lower Limits] field stores information indicating the upper and lower limits of the amount that the payer can pay to the payee.

[0062] The [Fees] field stores information indicating the transfer fee when a transfer is made from the payer's account to the recipient's account (hereinafter referred to as "fee information").

[0063] Furthermore, information such as [Payer Information], [Upper and Lower Limits], and [Fees] (hereinafter referred to as "fee-related information") may be stored for each business that makes the payment, i.e., a service user (service user identification information) that processes payments using the supplementary device 100. When such a business uses the supplementary device 100 according to this embodiment, one or more pieces of fee-related information associated with that business can be sorted according to predetermined criteria (for example, in descending order of frequency of use or number of uses, or in order based on the most recent usage date and time), and can be displayed in a list format on the display screen.

[0064] Furthermore, the fee database D114 may be a database that links payer account information, payee account information, and fees. In this case, there may be multiple combinations of payer account information and payee account information. Fee information is set for each of these combinations. For example, payer account information may be set individually for each of the multiple accounts held by the service user.

[0065] The invoice information acquisition unit 120 acquires invoice information, including payee identification information that can identify the target payee, from a predetermined system (for example, a system of a business operator that performs OCR processing). The predetermined system may be, for example, a service provided by an external business operator (including cloud services), and may be SaaS (Software as a Service).

[0066] The missing item determination unit 130 refers to the item requirement database D111 to identify the necessary items for enabling the remittance processing of a specific payment service provider, and determines whether the necessary items are present in the item information of the invoice information.

[0067] Specifically, the missing item determination unit 130 identifies information included in the invoice information that can identify a specific payment service provider to execute the remittance process (for example, at least one of the following: bank name "Bank A" and bank code "001"). The missing item determination unit 130 may also refer to the item requirement database D111 shown in Figure 2 to identify the payment service provider identification information "Bank A" which is related to the information that can identify a specific payment service provider (hereinafter referred to as "specific payment service provider identification information"). The missing item determination unit 130 identifies the following items as necessary items, for example, related to the identified payment service provider identification information: "invoice number", "business registration number", "payee account number", "bank code", "branch code", "account type", "account holder name", and "fee burden category".

[0068] In other words, the missing item determination unit 130 identifies the required items at a specific payment service provider based on specific payment service provider identification information (for example, a bank code or the name of the payment service provider) that can identify the specific payment service provider that performs the remittance processing. The missing item determination unit 130 then compares the items in the item information with the required items. The missing item determination unit 130 identifies the required items that are not included in the item information as missing items.

[0069] Furthermore, if multiple specified payment service providers are identified (for example, if the invoice information includes multiple bank names corresponding to the payee), the missing item determination unit 130 may identify the target payer account information included in the invoice information, refer to the fee database D114, and identify the specified payment service provider among the multiple specified payment service providers that has the lowest fee for the remittance processing from the target payer to the target payee. Specifically, the missing item determination unit 130 identifies the target payer account included in the invoice information (it may also identify the bank and branch corresponding to the account), and identifies the specified payment service provider among the multiple specified payment service providers that has the lowest fee in relation to the identified target payer account (for example, a branch of the same financial institution as the financial institution of the target payer account). As a result, the supplementary system 10 can select the specified payment service provider with the lowest fee among multiple specified service providers that can perform remittance processing on the invoice information without requiring human intervention, thus enabling the payment system 400 to quickly execute the remittance processing while protecting the payer's interests.

[0070] For convenience, in the following example, the missing item determination unit 130 determines that the item information does not include the "account type" item, and identifies the "account type" item as a missing item.

[0071] If the missing item determination unit 130 determines that there are missing items, the supplementary information determination unit 140 refers to the payment-related database D112 and determines whether or not there is supplementary information corresponding to the missing items in the payment-related information related to the payee identification information of the invoice information.

[0072] Specifically, the supplementary information determination unit 140 identifies, for example, the business registration number "00001" and the payee account number "1234567," which are payee identification information included in the invoice information. The supplementary information determination unit 140 refers to, for example, the payment-related database D112 shown in Figure 3 to identify the payee account information and fee burden classification information related to the business registration number "00001" and the payee account number "1234567." For example, the supplementary information determination unit 140 identifies the account type "ordinary" in the payee account information, which corresponds to the missing item, the "account type" item. In other words, the supplementary information determination unit 140 determines that there is supplementary information corresponding to the missing item and identifies the account type "ordinary" as supplementary information.

[0073] Furthermore, the supplementary information determination unit 140 determines that if there is no account type in the payee account information corresponding to the missing item, "account type," then there is no supplementary information in the payment-related database D112. In this case, the supplementary device 100 refers to the payment history database D113 and executes a process to determine whether or not supplementary information can be identified.

[0074] If the performance determination unit 140 determines that there is no supplementary information in the payment-related database D112, the performance determination unit 150 refers to the payment performance database D113 to determine whether or not there is supplementary information related to the target payee identification information.

[0075] Specifically, the performance determination unit 150 identifies, for example, the business registration number "00001," which is the target payee identification information included in the invoice information. The performance determination unit 150 refers to, for example, the payment performance database D113 shown in Figure 4 to identify, for example, the target payee account information related to the business registration number "00001." The performance determination unit 150 identifies the account type "normal" in the target payee account information, which corresponds to the missing item, the "account type" item. In other words, the performance determination unit 150 determines that there is supplementary information corresponding to the missing item in the payment performance database D113 and identifies the account type "normal" as supplementary information. This makes it possible for the supplementation system 10 to supplement the items more reliably.

[0076] The performance determination unit 150 may, instead of the target payee identification information, determine whether or not supplementary information exists based on information from the target payee account information, such as the payee account number, bank code, branch code, and account type.

[0077] In other words, the performance determination unit 150 determines whether or not supplementary information exists in the payment performance database D113 based on information that can uniquely identify the payee, and identifies the supplementary information.

[0078] If the payment information generation unit 160 determines that all the necessary supplementary information is available in the payment-related database D112, it adds the supplementary information to the invoice information to generate payment information for the payment system 400 of the specified payment service provider to perform a remittance process for the invoice (for example, including a process to settle the invoice, which may also be a process to deposit funds into the account of the target payee).

[0079] Specifically, the payment information generation unit 160 generates payment information by adding the supplementary information "ordinary" as the account type to invoice information that, for example, lacks the "account type" item. As a result, the supplementary system 10 can quickly and appropriately add missing item information to invoice information without requiring human intervention, enabling the payment system 400 to properly execute the remittance process.

[0080] Furthermore, if the payment information generation unit 160 determines that there is no supplementary information in the payment-related database D112 and that such supplementary information is available in the payment history database D113, it may add the supplementary information obtained from the payment history database D113 to the invoice information to generate payment information for the payment system 400 of the specified payment service provider to perform the remittance processing for the invoice.

[0081] Specifically, if the payment information generation unit 160 cannot identify the "account type" item of the target payee in the payment-related database D112, for example, it refers to the payment history database D113 and adds the supplementary information account type "ordinary," which is identified based on the target payee identification information of the target payee, such as the business registration number "00001," to the invoice information to generate payment information. As a result, the supplementary system 10 can reliably add missing item information to the invoice information without requiring human intervention when the item information necessary for remittance processing is missing from the invoice information, and enables the payment system 400 of the specified payment business operator to properly execute the remittance processing.

[0082] Furthermore, if the payment information generation unit 160 determines that there is no supplementary information in the payment-related database D112 and that there are multiple candidates for supplementary information in the payment history database D113, it may identify the latest information among the candidates for supplementary information as supplementary information based on the time information in the payment history database D113, and generate payment information by adding this supplementary information to the invoice information.

[0083] Specifically, if the payment information generation unit 160 cannot identify the "account type" item of the target payee in the payment-related database D112, for example, it refers to the payment history database D113 and identifies information on multiple account types that can serve as supplementary information based on the target payee identification information of the target payee, such as the business registration number "00001". Information on multiple account types may include, for example, "ordinary," "current," and "business." From the information on multiple account types that can serve as supplementary information, the payment information generation unit 160 identifies the information on the account type related to the most recent remittance process executed from the present as supplementary information. As a result, when the invoice information is missing item information for processing a remittance, the supplementary system 10 can extract the most appropriate information from the history database D113 as supplementary information and supplement the invoice information without requiring human intervention, thereby enabling the payment system 400 of the specified payment business operator to properly execute the remittance process.

[0084] Furthermore, if the payment information generation unit 160 determines that there are missing items, and the missing item is the target payer account information, it may identify the target payer account information that results in the lowest transfer fee from the target payer to the target payee as supplementary information, and add this supplementary information to the invoice information to generate payment information. The payment information generation unit 160 may also store the target payer account information that results in the lowest fee as a payer discount account in the payment-related database D112.

[0085] Specifically, if the payment information generation unit 160 determines, for example, that there are missing items in the missing item determination unit 130, it refers to the item requirement database D111 to determine whether the missing item is the target payer account information of the target payer. If the payment information generation unit 160 determines that the missing item is the target payer account information (for example, the payer account number of the target payer), it refers to the fee database D114 and, based on the target recipient account information, identifies the target payer account information, including the target payer account number, as supplementary information that results in the lowest fee from the target payer account number to the target recipient account number. The payment information generation unit 160 adds this supplementary information to the invoice information to generate payment information. As a result, when the item information necessary for remittance processing is missing in the invoice information, the supplementary system 10 can supplement the invoice information with supplementary information that results in the lowest fee without requiring human intervention, thereby ensuring the profit of the payer while allowing the settlement system 400 to properly execute the remittance processing.

[0086] Furthermore, if the performance determination unit 150 determines that there are multiple pieces of information that could serve as supplementary information, and the missing item is the target payer account information, the payment information generation unit 160 may identify the target payer account information that results in the lowest transfer fee from the target payer to the target payee as supplementary information, and add this supplementary information to the invoice information to generate payment information. In other words, the supplementary device 100 automatically selects the information that results in the lowest fee for the target payer from the information that could serve as supplementary information in the payment performance database D113 and executes the transfer process, thereby enabling the settlement system 400 to execute the transfer process appropriately while protecting the interests of the target payer.

[0087] Furthermore, if the payment information generation unit 160 determines in the performance determination unit 150 that there are multiple pieces of information that could serve as supplementary information, it may identify the piece of information that has been added to invoice information the most times in the past, and add that piece of information to the invoice information as supplementary information to generate payment information.

[0088] Specifically, if the payment information generation unit 160 cannot identify the "account type" item of the target payee in the payment-related database D112, it refers to the payment history database D113 and identifies multiple item information that can serve as supplementary information (for example, the item data "regular" for the item name "account type", the item data "current" for the item name "account type", etc.) based on the target payee identification information, for example, the business registration number "00001". The payment information generation unit 160 refers to the [Supplementary History] item in the payment history database D113 and identifies the number of times each of the identified multiple item information has been used to supplement. The payment information generation unit 160 identifies the item information that has been identified most frequently as supplementary information and adds this supplementary information to the invoice information to generate payment information.

[0089] For example, if multiple pieces of information that could serve as supplementary information are identified, it becomes possible to identify more appropriate supplementary information by selecting the information that has been used most frequently as supplementary information by the user.

[0090] In other words, when the invoice information is missing item information necessary for processing a remittance, the supplementation system 10 can supplement the invoice information by extracting the most appropriate information from the payment history database D113 based on past supplementation trends, with minimal human intervention, thereby enabling the payment system 400 to properly execute the remittance process.

[0091] The information transmission unit 170 transmits various types of information to the accounting system 300 and the payment system 400, respectively.

[0092] ===Business equipment 200=== Referring to Figure 1, the functional configuration of the operator device 200 will be described. As shown in Figure 1, the operator device 200 includes, for example, a storage unit 201, an information transmission / reception unit 202, and a display processing unit 203.

[0093] The memory unit 201 stores various types of information (for example, invoice information).

[0094] The information transmission / reception unit 202 is a functional unit that transmits and receives various types of information. Specifically, the information transmission / reception unit 202 transmits invoice information to the supplementary device 100 and receives an accounting completion notification from the supplementary device 100.

[0095] The display processing unit 203 is a functional unit that displays various screens. Specifically, the display processing unit 203 may display a screen indicating that an accounting completion notification has been received.

[0096] ===Accounting System 300=== Referring to Figure 1, the functional configuration of the accounting system 300 will be described. As shown in Figure 1, the accounting system 300 includes, for example, a storage unit 301, an information transmission / reception unit 302, a journal entry processing unit 303, and a display processing unit 304.

[0097] The memory unit 301 stores various types of information (for example, invoice information).

[0098] The information transmission / reception unit 302 is a functional unit that transmits and receives various types of information.

[0099] The journal entry processing unit 303 is a functional unit that generates journal entry information. Specifically, the journal entry processing unit 303 generates first journal entry information by performing accounting processing on invoice information when it receives a first accounting eligibility notification. The journal entry processing unit 303 generates second journal entry information by performing accounting processing on settlement information when it receives a second accounting eligibility notification.

[0100] The display processing unit 304 is a functional unit that displays various screens. Specifically, the display processing unit 304 may display a screen indicating that the first payment approval notice and the second payment approval notice have been obtained.

[0101] ===Payment System 400=== Referring to Figure 1, the functional configuration of the payment system 400 will be described. As shown in Figure 1, the payment system 400 includes, for example, a storage unit 401, an information transmission / reception unit 402, a payment processing unit 403, and a display processing unit 404.

[0102] The memory unit 401 stores various types of information (for example, payment information and settlement information).

[0103] The information transmission / reception unit 402 is a functional unit that transmits and receives various types of information. Specifically, the information transmission / reception unit 402 acquires payment information and settlement requests from the supplementary device 100.

[0104] The settlement processing unit 403 is a functional unit that generates settlement information based on payment information. Specifically, upon receiving a settlement request, the settlement processing unit 403 executes a transfer process to the payment information and generates settlement information (for example, information indicating that the transfer to the target payee's account has been completed). The settlement processing unit 403 transmits the settlement information to the supplementary device 100, for example, through the information transmission / reception unit 402.

[0105] Furthermore, the settlement processing unit 403 may perform a credit check on the business operator based on the billing information or payment information. Specifically, the settlement processing unit 403 aggregates billing information related to a given business operator to identify its cash flow situation and assess its credit risk. The settlement processing unit 403 may also transmit information regarding the cash flow situation and credit risk to the supplementary device 100 through the information transmission / reception unit 402.

[0106] Furthermore, the settlement processing unit 403 may make loan proposals to businesses based on payment information or settlement information. Specifically, the settlement processing unit 403 may refer to the cash flow situation and credit risk identified based on payment information or settlement information, and if certain conditions are met, present loan terms that correspond to the cash flow situation and credit risk.

[0107] The display processing unit 404 is a functional unit that displays various screens. Specifically, the display processing unit 404 may display a screen indicating that a payment request has been received.

[0108] ===Processing Procedure=== The processing procedure of the supplementary system 10 will be explained with reference to Figures 6 and 7. Figure 6 is a flowchart showing the processing procedure of the supplementary system 10. Figure 7 shows the situation in which payment information is generated by adding supplementary information to invoice information. For convenience, the process of generating payment information by adding supplementary information to invoice information will be referred to as the "supplementary process" below.

[0109] In step S110, the supplementary device 100 obtains invoice information from, for example, the business operator's device 200. The supplementary device 100 stores the invoice information in the storage unit 110. By obtaining invoice information that shows the details of the invoice from the business operator, the supplementary device 100 can proceed with the processing necessary to execute accounting processing in the accounting system 300 and remittance processing in the settlement system 400.

[0110] Here, as shown in Figure 7, the invoice information will, as an example, include at least the following items: payee account number, bank code, branch code, account number, account holder name, fee burden category, and payer account number.

[0111] In step S120, when the supplementary device 100 obtains, for example, invoice information, it sends an accounting availability notification to the accounting system 300.

[0112] In step S121, the accounting system 300 accesses, for example, the supplementary device 100 and performs accounting processing on the invoice information.

[0113] In step S122, if the accounting system 300 has completed the accounting process, it notifies the supplementary device 100 of the completion of the accounting process.

[0114] In step S130, the supplementation device 100 performs supplementation processing on the invoice information for which accounting processing has been performed.

[0115] In step S131, the supplementary device 100 identifies a specific payment service provider that corresponds to the target payee identification information (e.g., the target payee business registration number or bank code) of the invoice information.

[0116] In step S132, the supplementary device 100 refers to the item requirements database D111 to identify the required items T20 corresponding to the specific payment service provider.

[0117] Here, as shown in Figure 7, the required items T20 are, for example, the following items: payee account number, bank code, branch code, account type, account number, account holder name, fee burden category, and payer account number.

[0118] In step S133, the supplementary device 100 compares the item information T10 of the invoice information with the required items T20 to determine whether the required items are included in the invoice information.

[0119] If it is determined that the invoice information contains the necessary items (step S133: YES), the supplementary device 100 transmits the invoice information as payment information to the payment system 400 of the specified payment service provider.

[0120] If it is determined that the invoice information does not include at least one of the required items (step S133: NO), in step S134, the supplementary device 100 refers to the payment-related database D112 and determines whether it can identify the missing item, the "account type" of the target payee, based on, for example, the target payee business registration number and the target payee account number.

[0121] Here, when the supplementation device 100 generates payment information by adding missing items to the invoice information, it may send a supplementation notification to the business device 200 that there are missing items in the invoice information, that these missing items can be supplemented in the payment-related database D112, and the details of the supplementation. The business making the payment receives the supplementation notification via the business device 200. The business then performs an operation to indicate permission for supplementation (hereinafter referred to as the "permission operation") by operating an input interface such as a keyboard or mouse provided on the business device 200. When the supplementation device 100 obtains information from the business device 200 indicating that the permission operation has been performed, it supplements the invoice information by adding the missing items and generates payment information.

[0122] Here, as shown in Figure 7, the missing item is the "Account Type" item.

[0123] If it is determined that the missing items can be identified (step S134: YES), the supplementation device 100 adds the missing items to the invoice information and generates payment information.

[0124] If it is determined that the missing item cannot be identified (step S134: NO), in step S135, the supplementary device 100 refers to the payment history database D113 and determines whether it can identify the missing item, the "account type" of the target payee, based on, for example, the target payee business registration number (or target payee account information).

[0125] If it is determined that the missing items can be identified (step S135: YES), the supplementation device 100 adds the missing items to the invoice information and generates payment information.

[0126] Here, when the supplementation device 100 generates payment information by adding missing items to the invoice information, it may send information to the business device 200 indicating that there are missing items in the invoice information. The supplementation device 100 may also send information to the business device 200 indicating that the missing items can be supplemented in the payment history database D113. Furthermore, if supplementation is possible, the supplementation device 100 may send a supplementation availability notification to the business device 200, which associates the information indicating that supplementation is possible with information indicating the content of the supplementation. The business making the payment receives the supplementation availability notification via the business device 200. The business device 200 then receives operation input from the user to an input interface such as a keyboard or mouse and obtains operation information indicating permission for supplementation (hereinafter referred to as "permission operation information"). When the supplementation device 100 obtains permission operation information from the business device 200, it supplements the invoice information by adding the missing items and generates payment information.

[0127] If it is determined that the missing items cannot be identified (step S135: NO), in step S136, the supplementary device 100 sends a notification to the business device 200 that contains information indicating that there are missing items in the invoice and which items are missing. This allows the billing party to quickly create a new invoice.

[0128] In step S140, the supplementary device 100 transmits, for example, payment information and a remittance request to the payment system 400 of the specified payment service provider.

[0129] In step S141, the payment system 400 executes a remittance process based on the payment information.

[0130] In step S142, the settlement system 400 transmits settlement information resulting from the completion of the remittance process to the supplementary device 100. At this time, the settlement system 400 may also notify the supplementary device 100 of the completion of the remittance process.

[0131] In this way, the complementary system 10 can automatically complete accounting and remittance processes while ensuring security, triggered by the acquisition of billing information from the business operator.

[0132] Although the supplementation device 100 has been described as performing the supplementation process after step S104, it is not limited to this. The supplementation system 10 may be executed between steps S110 and S120. That is, the supplementation process may be performed before accounting processing is performed on the invoice information.

[0133] Furthermore, the supplementary device 100 according to this embodiment may perform a structure unification process when it receives invoice information in order to absorb differences in the data format of the item information contained in the invoice information. The structure unification process includes both or either a standardization process for item names and a standardization process for data values. First, in the standardization process for item names, the names of each item contained in the invoice information are converted to a predefined unified item name. For example, date items that are expressed with different names depending on the issuer, such as "invoice date," "issue date," and "payment request date," are treated as the unified item name "invoice date." Similarly, differences in expression such as "amount," "invoice amount," and "total invoice amount" are also unified to the unified item name "invoice amount."

[0134] Next, in the data value standardization process, the representation format of the values ​​stored in each item is converted to a predetermined standard format. For example, for date values, multiple representations such as "YYYY / MM / DD," "YYYY-MM-DD," and "Reiwa ○ year ○ month ○ day" are unified into the ISO format "YYYY-MM-DD." Also, for monetary values, variations in notation such as "1,000," "¥1,000," and "1000 yen" are eliminated, and they are uniformly recorded as integer values ​​regardless of the presence or absence of currency symbols and digit separators. As a result, the supplementary device 100 can hold invoice information, even if the configuration differs depending on the issuer, in a normalized state within a common data structure. Consequently, the efficiency of subsequent processing, such as the identification of missing items, is improved. Note that these structural unification processes may also be performed in advance for the necessary items of each payment service provider.

[0135] ===Hardware Configuration=== Referring to Figure 8, an example of a hardware configuration when the complementary device 100, business device 200, accounting system 300, and payment system 400 are implemented by computer 1000 will be described. Note that the various functions of the complementary device 100, business device 200, accounting system 300, and payment system 400 can be implemented by dividing them among multiple devices.

[0136] Figure 8 shows an example of a computer hardware configuration. As shown in Figure 8, the computer 1000 includes, for example, a processor 1001, memory 1002, storage device 1003, input I / F unit 1004, data I / F unit 1005, communication I / F unit 1006, and display unit 1007.

[0137] The processor 1001 is a control unit that controls various processes in the computer 1000 by executing programs stored in the memory 1002.

[0138] Memory 1002 is a storage medium such as RAM (Random Access Memory). Memory 1002 temporarily stores the program code of the program executed by the processor 1001, as well as data required during program execution.

[0139] The storage device 1003 is a non-volatile storage medium such as a hard disk drive (HDD) or flash memory. The storage device 1003 stores the operating system and various programs for realizing the above configurations.

[0140] The input interface unit 1004 is a device for receiving input from the user. Specific examples of the input interface unit 1004 include keyboards, mice, touch panels, various sensors, and wearable devices. The input interface unit 1004 may be connected to the computer 1000 via an interface such as USB (Universal Serial Bus).

[0141] The data I / F unit 1005 is a device for inputting data from outside the computer 1000. Specific examples of the data I / F unit 1005 include drive devices for reading data stored on various storage media. The data I / F unit 1005 may also be located outside the computer 1000. In that case, the data I / F unit 1005 would be connected to the computer 1000 via an interface such as USB.

[0142] The communication interface unit 1006 is a device for performing data communication via the Internet N with external devices of the computer 1000, either via wired or wireless connection. The communication interface unit 1006 may also be located outside the computer 1000. In that case, the communication interface unit 1006 is connected to the computer 1000 via an interface such as USB.

[0143] The display unit 1007 is a device for displaying various types of information. Specific examples of the display unit 1007 include liquid crystal displays, organic EL (Electro-Luminescence) displays, and displays for wearable devices. The display unit 1007 may be located outside the computer 1000. In that case, the display unit 1007 is connected to the computer 1000 via, for example, a display cable. Furthermore, if a touch panel is used as the input I / F unit 1004, the display unit 1007 can be integrated with the input I / F unit 1004.

[0144] ===Summary=== <1> The supplementary system 10 includes: an invoice information acquisition unit 120 that acquires invoice information from a predetermined system, which includes item information indicating at least one item relating to a claim for payment to a target payee; a missing item determination unit 130 that identifies the necessary items of a payment business operator included in the invoice information by referring to an item requirement database D111 which stores necessary items that are necessary for executing a remittance process to a payment business operator, and determines whether there are missing items that are items included in the necessary items but are not included in the item information; a supplementary information determination unit 140 that, if it is determined that there are missing items, refers to a payment-related database D112 which stores payment-related information relating to payments to payees for each payee, and determines whether there is supplementary information corresponding to the missing items in the payment-related information of the target payee included in the invoice information; and a payment information generation unit 160 that, if it is determined that there is supplementary information, adds the supplementary information to the invoice information and generates payment information for executing a remittance process. As a result, when the invoice information does not include necessary items that differ for each payment service provider, the supplementary system 10 can appropriately supplement the missing items in the invoice information without requiring manual verification and addition of items, thereby enabling the payment system 400 to properly execute the remittance process.

[0145] <2> The supplementary system 10 further includes a performance determination unit 150 that, when the supplementary information determination unit 140 determines that there is no supplementary information, refers to a payment performance database D113 that stores payment recipient identification information (payment recipient) and past performance information indicating past performance of remittance processing in association with each other, and determines whether or not there is supplementary information related to the target payment recipient identification information (target payment recipient). The payment information generation unit 160 generates payment information by adding the supplementary information to the invoice information when the performance determination unit 150 determines that there is supplementary information. This makes it possible for the supplementary system 10 to supplement items more reliably.

[0146] <3> In the supplementary device 100, the performance determination unit 150 refers to the payment performance database D113, which stores payment recipient identification information (payment recipient), past performance information, and time information indicating the time when the remittance process was executed, to determine whether there is supplementary information related to the target payment recipient identification information (target payment recipient). If the performance determination unit 150 determines that there are multiple candidates that could be supplementary information, the payment information generation unit 160 identifies the information related to the most recent performance among the candidates that could be supplementary information as supplementary information based on the time information, and generates payment information by adding the supplementary information to the invoice information. <2> The supplementary device 100 described above. As a result, when the supplementary system 10 is missing item information for processing remittances in the invoice information, it can extract the most appropriate information from the performance database D113 as supplementary information without requiring human intervention, thereby enabling the payment system 400 of the specific payment service provider to properly execute remittance processing.

[0147] <4> In the supplementary device 100, if the payment information generation unit 160 determines that there are missing items in the missing item determination unit 130, it determines whether the missing item is an item related to the payer account information used for remittance processing at the target payer, which is the payer to the target payee. If it determines that the missing item is an item related to the payer account information, it refers to the fee database D114, which stores fee information indicating the fee for remittance processing from the payer's account to the payee's account, and identifies the target payer account information of the target payer that results in the lowest remittance processing fee from the target payer's account to the target payee's account as supplementary information, and adds this supplementary information to the invoice information to generate payment information. <2> The supplementary device 100 described above. This allows the supplementary system 10 to supplement invoice information in a way that minimizes fees, without requiring human intervention, when the invoice information is missing item information necessary for processing the remittance. Thus, it is possible to ensure that the remittance processing of the payment system 400 is performed appropriately while protecting the interests of the payer.

[0148] <5> In the supplementary device 100, if the performance determination unit 150 determines that there are multiple pieces of information that can serve as supplementary information, the payment information generation unit 160 identifies the piece of information that has been added to invoice information the most times in the past, adds that piece of information to the invoice information as supplementary information, and generates payment information. <2> The supplementary device 100 described above. As a result, when the supplementary system 10 is missing item information for processing remittances in the invoice information, it can supplement the invoice information by extracting the most appropriate information from the performance database D113 based on past supplementary trends, without requiring human intervention, thereby enabling the payment system 400 to properly execute the remittance process.

[0149] The embodiments described above are provided to facilitate understanding of the present invention and are not intended to limit its interpretation. The elements, arrangement, materials, conditions, shapes, and sizes of the embodiments are not limited to those exemplified and can be modified as appropriate. Furthermore, configurations shown in different embodiments can be partially substituted or combined. [Explanation of symbols]

[0150] 10...Complementary system, 100...Complementary device, 110...Storage unit, 120...Invoice information acquisition unit, 130...Missing item determination unit, 140...Complementary information determination unit, 150...Performance determination unit, 160...Payment information generation unit, 170...Information transmission unit, 200...Business equipment, 300...Accounting system, 400...Settlement system.

Claims

1. An invoice information acquisition unit acquires invoice information from a predetermined system, which includes item information indicating at least one item related to the invoice for payment to the target payee. A missing item determination unit, To enable the remittance process to the payment service provider, the necessary items are identified by referring to an item requirements database stored for each payment service provider, and the necessary items for the payment service provider included in the invoice information are identified. A missing item determination unit determines whether there are any missing items among the items included in the required items that are not included in the item information, When it is determined that there are missing items, the supplementary information determination unit refers to a payment-related database in which payment-related information, which is information regarding payments to payees, is stored for each payee, and determines whether or not there is supplementary information corresponding to the missing items in the payment-related information of the target payee, which is the payee included in the invoice information. If it is determined that the supplementary information exists, a payment information generation unit adds the supplementary information to the invoice information and generates payment information for executing the remittance process, An information processing system equipped with the following features.

2. If the supplementary information determination unit determines that there is no supplementary information, the system further includes a performance determination unit that determines whether or not there is supplementary information related to the target payee by referring to a payment performance database that stores the payee and past performance information indicating past performance of the remittance process in association with each other. The payment information generation unit, when the performance determination unit determines that the supplementary information exists, generates the payment information by adding the supplementary information to the invoice information. The information processing system according to claim 1.

3. The performance determination unit refers to the payment performance database, which stores the payee, the past performance information, and the time information indicating when the remittance process was executed in association with each other, and determines whether or not there is supplemental information related to the target payee. If the payment information generation unit determines in the performance determination unit that there are multiple candidates that could be the supplementary information, it identifies the information related to the most recent performance among the candidates that could be the supplementary information as the supplementary information based on the time information, and generates the payment information by adding the supplementary information to the invoice information. The information processing system according to claim 2.

4. The payment information generation unit, If the missing item determination unit determines that there is a missing item, it determines whether the missing item is an item relating to the payer account information used for the remittance process at the payer that is the payer to the payee. If it is determined that the missing item is an item relating to the payer account information, the fee database, which stores fee information indicating the fee for the remittance process from the payer's account to the recipient's account, is referenced to identify the target payer's account information that results in the lowest remittance fee from the target payer's account to the target recipient's account, as the supplementary information. The payment information is generated by adding the supplementary information to the invoice information. The information processing system according to claim 2.

5. The payment history database further associates and stores information indicating the number of times a predetermined item included in the past performance information has been used with respect to the past invoice information, which is past invoice information of the payee. The payment information generation unit, If the performance determination unit determines that there are multiple pieces of information that can serve as supplementary information, it identifies the item in the past performance information that has been used the most frequently among the pieces of information that can serve as supplementary information, by referring to the payment performance database. The payment information is generated by adding information indicating the items included in the past performance information to the invoice information as supplementary information. The information processing system according to claim 2.

6. Computers Obtain invoice information from a designated system that includes item information indicating at least one item related to the invoice for payment to the target payee, To enable the remittance process to the payment service provider, the necessary items are identified by referring to an item requirements database stored for each payment service provider, and the necessary items for the payment service provider included in the invoice information are identified. To determine whether there are any missing items among the required items that are not included in the aforementioned item information, If it is determined that there are missing items, the payment-related database, in which payment-related information concerning payments to payees is stored for each payee, is referred to to determine whether or not there is supplementary information corresponding to the missing items in the payment-related information of the target payee, which is the payee included in the invoice information. If it is determined that the aforementioned supplementary information exists, the supplementary information is added to the invoice information to generate payment information for executing the remittance process, An information processing method that performs the following.

7. On the computer, Obtain invoice information from a designated system that includes item information indicating at least one item related to the invoice for payment to the target payee, To enable the remittance process to the payment service provider, the necessary items are identified by referring to an item requirements database stored for each payment service provider, and the necessary items for the payment service provider included in the invoice information are identified. To determine whether there are any missing items among the required items that are not included in the aforementioned item information, If it is determined that there are missing items, the payment-related database, in which payment-related information concerning payments to payees is stored for each payee, is referred to to determine whether or not there is supplementary information corresponding to the missing items in the payment-related information of the target payee, which is the payee included in the invoice information. If it is determined that the aforementioned supplementary information exists, the supplementary information is added to the invoice information to generate payment information for executing the remittance process, A program that executes the command.

Images