Information processing system, information processing method, and program

Abstract

To provide an information processing system, information processing method, and program, which allow for performing processing for making on-behalf-of payments of bills issued by sellers.SOLUTION: An information processing system disclosed herein provides a service that makes on-behalf-of payments of bills issued by sellers. The information processing system comprises a reception unit for receiving request information for on-behalf-of payment of bills issued by a seller by bank transfer from a bank of a buyer, a processing unit for making on-behalf-of payment of the bills issued by the seller on the basis of the request information received by the reception unit, and a generation unit for generating a list of amounts to be requested to the buyer based on the on-behalf-of payment made by the processing unit for the bills issued by the seller.SELECTED DRAWING: Figure 4

Description

[Technical field]

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

[0002] Bills or statements for utility bills, telephone bills, insurance premiums, tuition fees, credit payments, taxes, etc. are sent to users individually by mail from electric power companies, gas companies, telephone companies, insurance companies, credit card companies, etc. It is also well known that payments for such bills or statements are made by automatic transfer or automatic remittance to a bank account owned by the user. Regarding the sending of payment invoices or statements, there is known technology that sends invoices and statements together in a single package, while reducing the enormous expenses incurred by each billing company in carrying out the sending operations (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] There is a "bill payment agency service" that uses a system called BPSP (Business Payments Solution Provider). The bill payment agency service is a service that allows you to pay the invoice you received with your credit card instead of by bank transfer. For example, when you receive an invoice and use the bill payment agency service, you pay with your card. The agency service provider transfers the money to the payee on the due date. Even if the payment methods used by the buyer and seller differ, the agency service provider will accept the card payment amount and deposit it into the seller's account, allowing you to pay the invoice you received with your credit card.

[0005] An object of the present invention is to provide an information processing system, an information processing method, and a program that can perform processing for paying an invoice issued by a seller. [Means for solving the problem]

[0006] (1) One aspect of the present invention is an information processing system that provides a service of acting on behalf of a seller to pay invoices issued by the seller, the system including: a reception unit that receives application information for acting on behalf of a buyer to pay the invoices issued by the seller by bank transfer; a processing unit that acts on behalf of the seller to pay the invoices issued by the seller based on the application information received by the reception unit; and a creation unit that creates a list of amounts to be charged to the buyer based on the acting on behalf of the seller to pay the invoices issued by the seller performed by the processing unit. The information processing system includes: (2) One aspect of the present invention is an information processing system as described in (1) above, in which the creation unit creates information indicating a total amount to be charged to the buyer and information indicating the remaining amount to be charged. (3) One aspect of the present invention is an information processing system as described in (1) above, in which the creation unit creates a list including pending transfers, which indicate invoices for which payment from the buyer has not been completed. (4) One aspect of the present invention is an information processing system as described in (1) above, wherein the creation unit creates a list including a transfer completion indicating an invoice for which payment from the buyer has been completed. (5) One aspect of the present invention is an information processing system as described in (1) above, wherein the creation unit creates a list including separate invoices indicating invoices that do not require payment from the buyer. (6) One aspect of the present invention is the information processing system described in (5) above, in which the separate claim is a bond-assigned claim. (7) One aspect of the present invention is an information processing system as described in (3) above, wherein the creation unit creates invoices in a different color for which payment by the buyer has not been completed even after the payment due date has passed.

[0007] (8) One aspect of the present invention is an information processing method executed by a computer, which accepts application information for acting on behalf of a seller to pay an invoice by bank transfer from a buyer, acts on behalf of the seller to pay the invoice based on the accepted application information, and creates a list of amounts to be charged to the buyer based on the acting on behalf of the seller to pay the invoice.

[0008] (6) One aspect of the present invention is a program that causes a computer to execute the steps of accepting application information for making payment on behalf of an invoice issued by a seller through a bank transfer from a buyer, making payment on behalf of the invoice issued by the seller based on the application information accepted in the accepting step, and creating a list of amounts to be charged to the buyer based on the payment on behalf of the invoice issued by the seller. Effect of the Invention

[0009] According to the present invention, it is possible to obtain an effect that a process for paying an invoice issued by a seller can be carried out on behalf of the seller. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing an example of the configuration of an invoice advance payment system 1 according to the present embodiment. [Diagram 2] FIG. 2 is a diagram for explaining a first service. [Diagram 3] FIG. 11 is a diagram for explaining a second service. [Figure 4] 1 is a block diagram showing an example of a terminal device 10, a terminal device 20, and an information processing system 100 included in a bill advance payment system 1 according to the present embodiment. [Figure 5A] FIG. 13 is a diagram showing an example of an initial screen of a website of a bill advance payment service. [Figure 5B] FIG. 13 is a diagram showing an example of a login screen for an invoice advance payment service. [Figure 5C] FIG. 13 is a diagram showing an example of an initial setting screen for an invoice advance payment service. [Figure 5D] FIG. 13 is a diagram showing an example of the next initial setting screen of the bill advance payment service. [Figure 6A] FIG. 13 is a diagram showing an example of an application information input screen for an invoice advance payment service. [Figure 6B] FIG. 13 is a diagram showing an example of an application information input screen for an invoice advance payment service. [Figure 6C] FIG. 13 is a diagram showing an example of a first service application details confirmation screen for an invoice advance payment service. [Figure 6D] FIG. 13 is a diagram showing an example of a first service application completion screen for the bill advance payment service. [Figure 6E] FIG. 13 is a diagram showing an example of an application error notification screen for an invoice advance payment service. [Figure 7A] FIG. 13 is a diagram showing an example of a service application information input screen for an invoice advance payment service. [Figure 7B] FIG. 13 is a diagram showing an example of a service application information input screen for an invoice advance payment service. [Figure 7C] FIG. 13 is a diagram showing one example (part 1) of a second service application content confirmation screen for the bill advance payment service. [Figure 7D]FIG. 23 is a diagram showing an example (part 2) of the second service application details confirmation screen for the bill advance payment service. [Figure 8] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 9] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 10] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 11] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 12] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 13A] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 13B] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 14A] FIG. 13 is a diagram showing an example of an application error notification screen for an invoice advance payment service. [Figure 14B] FIG. 13 is a diagram showing an example of an application error notification screen for an invoice advance payment service. [Figure 14C] FIG. 13 is a diagram showing an example of an application error notification screen for an invoice advance payment service. [Figure 15] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 16A] FIG. 13 is a diagram showing an example of an application history screen for an invoice advance payment service. [Figure 16B] FIG. 13 is a diagram showing an example of an application history screen for an invoice advance payment service. [Figure 16C] FIG. 13 is a diagram showing an example of an application history screen for an invoice advance payment service. [Figure 17A] FIG. 13 is a diagram showing an example of an application history details screen for an invoice advance payment service. [Figure 17B]FIG. 13 is a diagram showing an example of an application history details screen for an invoice advance payment service. [Figure 18] 4 is a flowchart showing an example of the operation of the bill advance payment system 1 of the present embodiment. [Figure 19] FIG. 13 is a diagram showing an example of a billing list screen of the bill advance payment service. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Next, an information processing system, an information processing method, and a program according to the present embodiment will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment. In addition, in all the drawings for explaining the embodiments, the same reference numerals are used for the parts having the same functions, and the repeated explanation is omitted. In addition, "based on XX" in this application means "based on at least XX," and includes cases where it is based on other elements in addition to XX. Furthermore, "based on XX" is not limited to cases where XX is used directly, but also includes cases where it is based on XX that has been calculated or processed. "XX" is any element (for example, any information).

[0012] (Embodiment) Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing an example of the configuration of an invoice advance payment system 1 according to this embodiment. The bill advance payment system 1 provides a buyer with a service of making payments on behalf of a seller for bills issued by the seller. The bill advance payment system 1 comprises a terminal device 10, terminal devices 20-1 to 20-n (n is an integer greater than 0), and an information processing system 100. The terminal device 10, the terminal devices 20-1 to 20-n, and the information processing system 100 can communicate with each other via a communication network NW. The communication network NW includes the Internet, a Wide Area Network (WAN), a Local Area Network (LAN), a public line, a provider device, a dedicated line, a wireless base station, and the like.

[0013] The terminal device 10 is a terminal used by a user U1. An example of the user U1 is a buyer. An example of a buyer is a person who purchases a product. As the terminal device 10, for example, a stationary computer device may be used, or a portable computer device such as a smartphone or a tablet computer (tablet PC) may be used. A credit card CA has been issued to the user U1.

[0014] Terminal device 20-1 to terminal device 20-n are terminals used by users U2-1 to U2-n, respectively. An example of user U2-1 to user U2-n is a seller. An example of a seller is a seller of goods. As terminal device 20-1 to terminal device 20-n, for example, a stationary computer device may be used, or a portable computer device such as a smartphone or a tablet computer (tablet PC) may be used.

[0015] Information processing system 100 provides a first service of accepting invoice payments on behalf of the buyer through credit card (hereinafter also referred to as "card") payment, and a second service of accepting invoice payments on behalf of the buyer through bank transfer payment. The first service is a service of paying invoices issued by a seller on behalf of the seller, and receiving payment by the buyer's card payment. The second service is a service of paying invoices issued by a seller on behalf of the seller, and receiving payment by bank transfer from the buyer. Hereinafter, any one of users U2-1 to U2-n will be referred to as user U2, and any one of terminal devices 20-1 to 20-n used by user U2 will be referred to as terminal device 20.

[0016] FIG. 2 is a diagram for explaining the first service. The contract that is the premise of the first service will be explained. User U1 has concluded a card member contract with issuer (ISS) 200 (A1). Issuer 200 concludes member contracts with consumers such as user U1, issues credit cards and the like, and provides the issued credit cards to the consumers. Issuer 200 acquires consumers, bills members, handles inquiries, collects payments, and takes security measures. The business providing the first service concludes an affiliated store contract with an acquirer (ACQ) 300 and develops, screens, and manages affiliated stores (B1). A user U1 concludes a payment consignment contract involving advance payment with the business providing the first service (C1).

[0017] The first service will be described. User U2, who is the seller, operates terminal device 20 to send an invoice to terminal device 10 used by user U1, who is the buyer (1-1). When user U1, who is the buyer, receives an invoice from user U2, who is the seller, he operates terminal device 10 to apply for advance payment of the invoice to information processing system 100 (2-1). Information processing system 100 accepts the application for advance payment of the invoice from user U1, who is the buyer, and advances payment of the invoice to user U2, who is the seller, based on the accepted application for advance payment of the invoice (3-1).

[0018] User U1, who is a buyer, operates terminal device 10 to make a payment by card settlement. By making a payment by card settlement, user U1 transfers the amount of the invoice payment made by information processing system 100 on behalf of the issuer and the associated fee to the issuer (4-1). By transferring the amount of the invoice payment on behalf of the issuer and the associated fee to issuer 200, issuer 200 transfers the amount of the invoice payment on behalf of the issuer and the associated fee minus the issuer's share to acquirer 300 (5-1). By transferring the amount of the invoice payment on behalf of the issuer and the associated fee minus the issuer's share to acquirer 300, acquirer 300 transfers the amount of the invoice payment on behalf of the issuer and the associated fee minus the issuer's and acquirer's shares to the business providing the service (6-1).

[0019] FIG. 3 is a diagram for explaining the second service. The contract that is the premise of the second service will be explained. User U1 has concluded a payment consignment contract involving advance payment with a business providing the first service (C2). The second service will be described. User U2, who is a seller, operates terminal device 20 to send an invoice to terminal device 10 used by user U1, who is a buyer (1-2). When user U1, who is a buyer, receives an invoice from user U2, who is a seller, he operates terminal device 10 to apply for advance payment of the invoice to information processing system 100 (2-2). Information processing system 100 accepts the application for advance payment of the invoice from user U1, who is a buyer, and advances payment of the invoice to user U2, who is a seller, based on the accepted application for advance payment of the invoice (3-2). Note that in this embodiment, information system 100 transfers the invoice to the seller on behalf of user U2, but this is not limiting, and information system 100 may request a separate transfer system to transfer the payment. User U1, who is a buyer, operates terminal device 10 to make payment by bank transfer. By bank transfer payment, the user U1 transfers the advance amount of the invoice paid by the information processing system 100 and the handling fee to the business providing the first service (4-2). Note that the buyer, user U1, can also transfer the amount by logging into Internet banking using a terminal other than the terminal device 10, or by visiting an ATM (Automatic Teller Machine) or at a bank counter.

[0020] Hereinafter, a detailed description will be given of the terminal device 10, the terminal device 20, and the information processing system 100 included in the bill advance payment system 1. Fig. 4 is a block diagram showing an example of the terminal device 10, the terminal device 20, and the information processing system 100 included in the bill advance payment system 1 according to this embodiment.

[0021] (Terminal device 10) The terminal device 10 includes a communication unit 12, a creation unit 14, a processing unit 16, an operation unit 18, a display unit 19, and a storage unit 15. The communication unit 12 is realized by a communication module. The communication unit 12 communicates with an external communication device via a network NW. The communication unit 12 communicates using a communication method such as a wired LAN. The communication unit 12 may also communicate using a wireless communication method such as a wireless LAN, Bluetooth (registered trademark), or LTE (Long Term Evolution) (registered trademark). The communication unit 12 holds communication information required to communicate with the information processing system 100 via the network NW.

[0022] The display unit 19 is, for example, a display and includes a touch panel. The storage unit 15 is realized by a hard disk drive (HDD), flash memory, random access memory (RAM), read only memory (ROM), etc., and stores information. The operation unit 18 is an input device that accepts operations by the user U1, for example, a touch panel. When the user U1 performs an operation to access a website for the bill advance payment service, the operation unit 18 accepts the operation. The creation unit 14 creates a request to access the site of the bill advance payment service based on the operation received by the operation unit 18 , and transmits the created access request from the communication unit 12 to the information processing system 100 .

[0023] The access response transmitted by the information processing system 100 in response to the access request is received by the communication unit 12. The processing unit 16 acquires the access response from the communication unit 12, and causes the display unit 19 to display an initial screen of the website of the bill advance payment service based on the acquired access response. FIG. 5A is a diagram showing an example of an initial screen of the website of the bill advance payment service. The example of the initial screen includes a box for inputting a user ID and a box for inputting a password. When the user U1 inputs a user ID and a password on the initial screen and presses the login button BU01, the operation unit 18 accepts the operation. The creation unit 14 creates a login request including the user ID and the password based on the operation accepted by the operation unit 18, and transmits the created login request from the communication unit 12 to the information processing system 100.

[0024] The login screen information transmitted by the information processing system 100 in response to the login request is received by the communication unit 12. The processing unit 16 acquires the login screen information from the communication unit 12, and displays the login screen on the display unit 19 based on the acquired login screen information. Fig. 5B is a diagram showing an example of the login screen for the invoice advance payment service. As shown in Fig. 5B, the login screen includes an initial setting button BU02 that is pressed when performing initial settings. The user U1 refers to the login screen and performs an operation of pressing (selecting) the initial setting button BU02. The operation unit 18 accepts the operation. The creation unit 14 creates an initial setting request including the user ID and information indicating the initial setting based on the operation accepted by the operation unit 18, and transmits the created initial setting request from the communication unit 12 to the information processing system 100.

[0025] The initial setting screen information sent by the information processing system 100 in response to the initial setting request is received by the communication unit 12. The processing unit 16 acquires the initial setting screen information from the communication unit 12, and causes the display unit 19 to display the initial setting screen based on the acquired initial setting screen information. Fig. 5C is a diagram showing an example of the initial setting screen for the invoice advance payment service. As shown in Fig. 5C, the initial setting screen includes a box for inputting information indicating the contracted business operator, and a box for inputting the client's name to be notified to the business partner. User U1 refers to the initial setting screen, inputs the name of the contracted business operator in a box for inputting information indicating the contracted business operator, inputs the client's name in a box for inputting the client's name to be notified to the business partner, and presses the setting button BU03 to perform the next setting. The operation unit 18 accepts the operation. The creation unit 14 creates a next initial setting request including the user ID and information indicating the next initial setting based on the operation accepted by the operation unit 18, and transmits the created next initial setting request from the communication unit 12 to the information processing system 100.

[0026] The next initial setting screen information sent by the information processing system 100 in response to the next initial setting request is received by the communication unit 12. The processing unit 16 acquires the next initial setting screen information from the communication unit 12, and causes the display unit 19 to display the next initial setting screen based on the acquired next initial setting screen information. FIG. 5D is a diagram showing an example of the next initial setting screen for the invoice advance payment service. As shown in FIG. 5D, the next initial setting screen includes a box for inputting information indicating the contracted business and a delivery address for the invoice to be issued by the business providing the service after the advance payment. The next initial setting screen displays an initial setting completion button BU04 that is pressed to complete the initial setting.

[0027] User U1 refers to the next initial setting screen, inputs the invoice destination in the invoice destination input box, and presses the initial setting completion button BU04. The operation unit 18 accepts the operation. The creation unit 14 creates an initial setting completion request including the user ID and the initial setting information entered on the initial setting screen and the next initial setting screen based on the operation accepted by the operation unit 18, and transmits the created initial setting completion request from the communication unit 12 to the information processing system 100.

[0028] The application information input screen information transmitted by the information processing system 100 in response to the initial setting completion request is received by the communication unit 12. The processing unit 16 acquires the application information input screen information from the communication unit 12, and causes the display unit 19 to display the application information input screen based on the acquired application information input screen information. FIG. 6A is a diagram showing an example of the application information input screen for the bill advance payment service. As shown in FIG. 6A, the application information input screen includes an application button ABU for displaying the application information input screen, a history button HBU for displaying the application history, a bill button BBU for displaying a list of bills, a first tab TA01 for selecting a first service that accepts bill payment on behalf of the buyer by card payment, and a second tab TA02 for selecting a second service that accepts bill payment on behalf of the buyer by bank transfer payment.

[0029] The application button ABU, history button HBU, and request button BBU are arranged in a row in the left-right direction at the top of the application information input screen. This configuration makes it easier to display the application history or request list compared to when the application button ABU, history button HBU, and request button BBU are randomly arranged on the application information input screen. In addition, the first tab TA01 and the second tab TA02 are arranged side by side on the left and right below the application button ABU, the history button HBU, and the request button BBU on the application information input screen. By configuring in this way, when the first tab TA01 and the second tab TA02 are randomly arranged on the application information input screen, the operation of selecting the first service or the second service can be made easier compared to when the first tab TA01 and the second tab TA02 are arranged above the application button ABU, the history button HBU, and the request button BBU on the application information input screen. Furthermore, the application information input screen includes a first service application information input screen AI01-1 for inputting application information for payment by the buyer's credit card. Arranged on the first service application information input screen AI01-1 from the top are a box for inputting the advance application amount, a box for inputting the due date of payment to the seller, a box for inputting payee information, and a box for inputting credit card information.

[0030] User U1 refers to the first service application information input screen AI01-1, enters the advance payment application amount in the box for entering the advance payment application amount, enters the payment due date to the seller in the box for entering the payment due date to the seller, enters payee information in the box for entering payee information, and enters credit card information in the box for entering credit card information. Figure 6B is a diagram showing an example of an application information input screen for an invoice advance payment service. Figure 6B is the first service application information input screen AI01-2 on which the advance payment application amount, the payment due date to the seller, payee information, and credit card information have been entered on the first service application information input screen AI01-1. The user U1 presses the application content confirmation button BU04 to confirm the application content. The operation unit 18 accepts the operation. The creation unit 14 creates an application content confirmation request including information indicating the user ID and the application content based on the operation accepted by the operation unit 18, and transmits the created application content confirmation request from the communication unit 12 to the information processing system 100.

[0031] The first service application content confirmation screen information transmitted by the information processing system 100 in response to the application content confirmation request is received by the communication unit 12. The processing unit 16 acquires the first service application content confirmation screen information from the communication unit 12, and displays the first service application content confirmation screen on the display unit 19 based on the acquired first service application content confirmation screen information. Fig. 6C is a diagram showing an example of the first service application content confirmation screen for the bill advance payment service. The first service application content confirmation screen shown in Fig. 6C includes a first service application content confirmation screen AI01-3 in which application information for payment by card settlement has been input.

[0032] User U1 refers to the first service application details confirmation screen AI01-3 and confirms the advance payment application amount, the due date of payment to the seller, payee information, and credit card information. User U1 presses the application button BU05 to agree and apply. The operation unit 18 accepts this operation. Based on the operation accepted by the operation unit 18, the creation unit 14 creates an application request including the user ID, information indicating the advance payment application amount, information indicating the due date of payment to the seller, payee information, and credit card information, and transmits the created application request from the communication unit 12 to the information processing system 100.

[0033] In response to an application request, the information processing system 100 transmits first service application completion screen information when it determines that there is no error in the application content, and the first service application completion screen information is received by the communication unit 12. The processing unit 16 acquires the first service application completion screen information from the communication unit 12, and causes the display unit 19 to display the first service application completion screen based on the acquired first service application completion screen information. Fig. 6D is a diagram showing an example of a first service application completion screen for the bill advance payment service. As shown in Fig. 6D, the first service application completion screen includes information indicating that the application for payment by card settlement has been completed, and information indicating the planned future flow. Examples of the information indicating the future flow include information indicating today's application acceptance notification, information indicating confirmation result notification on the same day at the earliest, information indicating an advance payment to the business partner after confirmation by our company, and information indicating a deduction from the card on the card company deduction date.

[0034] User U1 refers to the first service application completion screen and confirms that the application has been completed. User U1 performs an operation of pressing the next application button BU06 to continue applying for a payment on behalf of the user, or the application content reconfirmation button BU07 to reconfirm the application content. The operation unit 18 accepts the operation. Based on the operation accepted by the operation unit 18, the creation unit 14 creates a first service application information input request including information indicating the user ID and the application content, or an application content reconfirmation request including the user ID and information indicating that the application content is to be confirmed, and transmits the created first service application information input request or application content reconfirmation request from the communication unit 12 to the information processing system 100.

[0035] The application information input screen information transmitted by the information processing system 100 in response to the first service application information input request is received by the communication unit 12. The processing unit 16 acquires the application information input screen information from the communication unit 12, and displays the application information input screen (FIG. 6A) on the display unit 19 based on the acquired application information input screen information. The processing after the processing unit 16 displays the application information input screen (FIG. 6A) on the display unit 19 has been described above, so a description thereof will be omitted. The first service application content confirmation screen information transmitted by the information processing system 100 in response to the application content reconfirmation request is received by the communication unit 12. The processing unit 16 acquires the first service application content confirmation screen information from the communication unit 12, and displays the first service application content confirmation screen (FIG. 6C) on the display unit 19 based on the acquired first service application content confirmation screen information. The processing after the processing unit 16 displays the first service application content confirmation screen (FIG. 6C) on the display unit 19 has been described above, so a description thereof will be omitted.

[0036] The application error notification screen information transmitted by the information processing system 100 in response to an application request when it is determined that there is an error in the application content is received by the communication unit 12. The processing unit 16 acquires the application error notification screen information from the communication unit 12, and displays the application error notification screen on the display unit 19 based on the acquired application error notification screen information. FIG. 6E is a diagram showing an example of the application error notification screen of the bill advance payment service. The application error notification screen includes information RI01 notifying the reason why the card cannot be used and information RI02 notifying that the card cannot be used. Examples of the reason why the card cannot be used include the card's credit limit being exceeded and the card's expiration date having passed. In addition, the application error notification screen further includes a card change button BU08 for changing to another card other than the card used in the application, and a bank transfer switch button BU09 for switching to post-payment on bill (payment by bank transfer).

[0037] The user U1 refers to the application error notification screen and confirms that the application was not successful. The user U1 presses any one of the card change button BU08, the bank transfer switch button BU09, and the application content discard button BU10 for discarding the application content. The operation unit 18 accepts the operation. When the card change button BU08 is pressed based on the operation accepted by the operation unit 18, the creation unit 14 creates a first service application information input request including information indicating the user ID and the application details, and transmits the created first service application information input request from the communication unit 12 to the information processing system 100.

[0038] The creation unit 14 creates a second service application information input request including the user ID and information indicating that the payment method should be switched to bank transfer when the bank transfer switch button BU09 is pressed based on the operation received by the operation unit 18, and transmits the created second service application information input request from the communication unit 12 to the information processing system 100. The creation unit 14 creates a first service application information discard request including information indicating that the user ID and the application contents are to be discarded when the application content discard button BU10 is pressed based on the operation accepted by the operation unit 18, and transmits the created first service application information discard request from the communication unit 12 to the information processing system 100.

[0039] The application information input screen information transmitted by the information processing system 100 in response to the first service application information input request is received by the communication unit 12. The processing unit 16 acquires the application information input screen information from the communication unit 12, and displays the application information input screen (FIG. 6A) on the display unit 19 based on the acquired application information input screen information. The processing after the processing unit 16 displays the application information input screen (FIG. 6A) on the display unit 19 has been described above, so a description thereof will be omitted. The application information input screen information transmitted by the information processing system 100 in response to the second service application information input request is received by the communication unit 12. The processing unit 16 acquires the application information input screen information from the communication unit 12, and displays an application information input screen including the second service application information input screen on the display unit 19 based on the acquired application information input screen information. The second service application information input screen will be described later. The application information input screen information transmitted by the information processing system 100 in response to the first service application information discard request is received by the communication unit 12. The processing unit 16 acquires the application information input screen information from the communication unit 12, and displays the application information input screen (FIG. 6A) on the display unit 19 based on the acquired application information input screen information. The processing after the processing unit 16 displays the application information input screen (FIG. 6A) on the display unit 19 has been described above, so a description thereof will be omitted.

[0040] (Second Service) The user U1 refers to the application information input screen (FIG. 6A) and performs an operation of pressing the second tab TA02. The operation unit 18 accepts the operation. The creation unit 14 creates a second service application information input request including the user ID and information indicating the second service based on the operation accepted by the operation unit 18, and transmits the created second service application information input request from the communication unit 12 to the information processing system 100.

[0041] The second service application information input screen information transmitted by the information processing system 100 in response to the second service application information input request is received by the communication unit 12. The processing unit 16 acquires the second service application information input screen information from the communication unit 12, and causes the display unit 19 to display the application information input screen based on the acquired second service application information input screen information. FIG. 7A is a diagram showing an example of the application information input screen for the bill advance payment service. The application information input screen includes an application button ABU, a history button HBU, a bill button BBU, a first tab TA01, and a second tab TA02. Furthermore, the application information input screen includes a second service application information input screen AI02-1 for inputting application information for payment by bank transfer. The second service application information input screen AI02-1 includes a box for inputting the advance application amount, a box for inputting the payment due date to the seller, and a box for inputting payee information.

[0042] User U1 refers to the second service application information input screen AI02-1, inputs the advance payment application amount in the box for inputting the advance payment application amount, inputs the payment due date to the seller in the box for inputting the payment due date, and inputs payee information in the box for inputting payee information. Figure 7B is a diagram showing an example of the application information input screen for the invoice advance payment service. Figure 7B is the second service application information input screen AI02-2 on which the advance payment application amount, the payment due date to the seller, and payee information have been input on the second service application information input screen AI02-1.

[0043] User U1 presses application content confirmation button BU04 to confirm the application content. Operation unit 18 accepts the operation. Based on the operation accepted by operation unit 18, creation unit 14 creates a second service application content confirmation request including the user ID and information indicating the application content, and transmits the created second service application content confirmation request from communication unit 12 to information processing system 100. Here, the application content includes information indicating the advance application amount, information indicating the due date of payment to the seller, and payee information (e.g., information identifying a bank account).

[0044] The second service application content confirmation screen information transmitted by the information processing system 100 in response to the second service application content confirmation request is received by the communication unit 12. The processing unit 16 acquires the second service application content confirmation screen information from the communication unit 12, and causes the display unit 19 to display the second service application content confirmation screen based on the acquired second service application content confirmation screen information.

[0045] FIG. 7C is a diagram showing one example (part 1) of a second service application content confirmation screen for an invoice advance payment service. FIG. 7C shows a second service application content confirmation screen AI02-3 including application information for payment by bank transfer. The application information for payment by bank transfer includes information indicating the advance application amount, information indicating the due date of payment to the seller, payee information, and information indicating the name of the person requesting the transfer. In the example shown in FIG. 7C, an alert is displayed indicating that the advance transfer by the business providing the second service may not be completed by the due date of payment to the seller, because the due date of payment to the seller (the due date of the original invoice) entered on the second service application information input screen is close to the application date.

[0046] User U1 refers to the second service application details confirmation screen AI02-3, checks the advance payment application amount, the due date of payment to the seller, payee information, the name of the person requesting the transfer, and the alert, and presses the application button BU11 to apply for deferred payment with these details. The operation unit 18 accepts this operation. Based on the operation accepted by the operation unit 18, the creation unit 14 creates an application request including the user ID, information indicating the advance payment application amount, information indicating the due date of payment to the seller, payee information, and information indicating the name of the person requesting the transfer, and transmits the created application request from the communication unit 12 to the information processing system 100.

[0047] Fig. 7D is a diagram showing an example (part 2) of the second service application details confirmation screen for the invoice advance payment service. Fig. 7D shows the second service application details confirmation screen AI02-4 including application information for payment by bank transfer. In the example shown in Fig. 7D, since the payment due date to the seller (payment due date of the original invoice) entered on the second service application information input screen was before (in the past) the application date, an alert is displayed indicating that the payment due date from the service user (buyer) to the business providing the second service after the advance payment is executed will be approaching the application date.

[0048] User U1 refers to the second service application details confirmation screen AI02-4, checks the advance payment application amount, the payment due date to the seller, the payee information, the name of the person requesting the transfer, and the alert, and performs an operation of pressing the application button BU12 to agree and apply for an advance payment. The operation unit 18 accepts the operation. The creation unit 14 creates an application request including the user ID based on the operation accepted by the operation unit 18, and transmits the created application request from the communication unit 12 to the information processing system 100.

[0049] The second service application completion screen information transmitted by the information processing system 100 when it is determined that there is no error in the application content in response to the application request is received by the communication unit 12. The processing unit 16 acquires the second service application completion screen information from the communication unit 12, and causes the display unit 19 to display a second service application completion screen (not shown) based on the acquired second service application completion screen information. The second service application completion screen includes information indicating that the application for payment by bank transfer has been completed. Returning to FIG. 4, the explanation will be continued.

[0050] The creation unit 14, the processing unit 16 and the operation unit 18 are realized by, for example, a hardware processor such as a CPU (Central Processing Unit) executing a computer program (software) stored in the storage unit 15. Furthermore, some or all of these functional units may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by a combination of software and hardware. The computer program may be stored in advance in a storage device such as a HDD or flash memory, or may be stored on a removable storage medium such as a DVD (Digital Versatile Disc) or CD-ROM, and installed by inserting the storage medium into a drive device.

[0051] (Terminal device 20) The terminal device 20 includes a communication unit 22, a creation unit 24, a processing unit 26, an operation unit 28, a display unit 29, and a storage unit 25. The communication unit 22 is realized by a communication module. The communication unit 22 communicates with an external communication device via the network NW. The communication unit 22 communicates using a communication method such as a wired LAN. The communication unit 22 may also communicate using a wireless communication method such as a wireless LAN, Bluetooth (registered trademark), or LTE (registered trademark). The communication unit 22 holds communication information required to communicate with the information processing system 100 via the network NW.

[0052] The display unit 29 is, for example, a display and includes a touch panel. The storage unit 25 is realized by a HDD, flash memory, RAM, ROM, etc., and stores information. The operation unit 28 is an input device that accepts operations by the user U2, for example, a touch panel. When the user U2 performs an operation to input an invoice, the operation unit 28 accepts the operation.

[0053] The creation unit 24 creates an invoice based on the operation received by the operation unit 28, and transmits an invoice message including the created invoice from the communication unit 22 to the terminal device 10. In response to the invoice notification, the information processing system 100 sends a transfer notification. The transfer notification sent by the information processing system 100 is received by the communication unit 12. The processing unit 16 acquires the transfer notification from the communication unit 12, and displays a deposit completion screen (not shown) on the display unit 19 based on the acquired transfer notification.

[0054] The creation unit 24, the processing unit 26, and the operation unit 28 are realized, for example, by a hardware processor such as a CPU executing a computer program (software) stored in the storage unit 25. In addition, some or all of these functional units may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by cooperation between software and hardware. The computer program may be stored in a storage device such as an HDD or flash memory in advance, or may be stored in a removable storage medium such as a DVD or CD-ROM, and installed by mounting the storage medium in a drive device.

[0055] (Information processing system 100) The information processing system 100 includes a communication unit 102, a reception unit 104, a determination unit 105, a processing unit 106, a derivation unit 107, a creation unit 108, and a storage unit 110. The communication unit 102 is realized by a communication module. The communication unit 102 communicates with an external communication device via a network NW. The communication unit 102 communicates using a communication method such as a wired LAN. The communication unit 102 may also communicate using a wireless communication method such as a wireless LAN, Bluetooth (registered trademark), or LTE (registered trademark). The communication unit 102 holds communication information required to communicate with the terminal device 10 and the terminal device 20 via the network NW.

[0056] The storage unit 110 is realized by a HDD, a flash memory, a RAM, a ROM, etc., and stores information. The storage unit 110 stores one or more user accounts, and user information that associates, for each of the one or more user accounts, a password for a user corresponding to a user ID to log in to the website of the bill advance payment service and a usable credit card number.

[0057] The communication unit 102 receives an access request transmitted by the terminal device 10. The reception unit 104 acquires the access request from the communication unit 102 and accepts the acquired access request. The creation unit 108 acquires the access request accepted by the reception unit 104 and creates an access response for displaying an initial screen (FIG. 5A) on the terminal device 10 based on the acquired access request. The creation unit 108 transmits the created access response from the communication unit 102 to the terminal device 10.

[0058] The communication unit 102 receives a login request transmitted by the terminal device 10. The reception unit 104 acquires the login request from the communication unit 102 and accepts the acquired login request. The determination unit 105 acquires the login request accepted by the reception unit 104 and acquires a user ID and password included in the acquired login request. The determination unit 105 determines whether or not the combination of the acquired user ID and password is included in the user information in the storage unit 110.

[0059] When the determination unit 105 determines that the combination of the user ID and the password is included in the user information in the storage unit 110, the creation unit 108 creates login screen information for displaying a login screen ( FIG. 5B ) on the terminal device 10. The creation unit 108 transmits the created login screen information from the communication unit 102 to the terminal device 10. When the determination unit 105 determines that the combination of the user ID and the password is not included in the user information in the storage unit 110, the creation unit 108 creates screen information for displaying that login to the terminal device 10 is not possible. The creation unit 108 transmits the created screen information from the communication unit 102 to the terminal device 10.

[0060] The communication unit 102 receives the initial setting request transmitted by the terminal device 10. The reception unit 104 acquires the initial setting request from the communication unit 102 and accepts the acquired initial setting request. The creation unit 108 acquires the initial setting request accepted by the reception unit 104 and creates initial setting screen information for displaying an initial setting screen ( FIG. 5C ) on the terminal device 10 based on the acquired initial setting request. The creation unit 108 transmits the created initial setting screen information from the communication unit 102 to the terminal device 10. The communication unit 102 receives the next initial setting request transmitted by the terminal device 10. The reception unit 104 acquires the next initial setting request from the communication unit 102 and accepts the acquired next initial setting request. The creation unit 108 acquires the next initial setting request accepted by the reception unit 104 and creates next initial setting screen information for displaying the next initial setting screen ( FIG. 5D ) on the terminal device 10 based on the acquired next initial setting request. The creation unit 108 transmits the created next initial setting screen information from the communication unit 102 to the terminal device 10.

[0061] The communication unit 102 receives the initial setting completion request transmitted by the terminal device 10. The reception unit 104 acquires the initial setting completion request from the communication unit 102 and accepts the acquired initial setting completion request. The processing unit 106 acquires the user ID included in the initial setting completion request accepted by the reception unit 104 and the initial setting information input on the initial setting screen and the next initial setting screen. The processing unit 106 associates the acquired user ID and initial setting information and stores them in the storage unit 110. The creation unit 108 creates application information input screen information for displaying an application information input screen (FIG. 6A) on the terminal device 10. The creation unit 108 transmits the created application information input screen information from the communication unit 102 to the terminal device 10.

[0062] The communication unit 102 receives the application content confirmation request transmitted by the terminal device 10. The acceptance unit 104 acquires the application content confirmation request from the communication unit 102 and accepts the acquired application content confirmation request. The judgment unit 105 acquires information indicating the user ID and application content included in the application content confirmation request accepted by the acceptance unit 104. The judgment unit 105 judges whether or not there is an error in the application content based on the acquired information indicating the application content. For example, the judgment unit 105 judges whether or not the card can be used. The creation unit 108 creates first service application content confirmation screen information for displaying a first service application content confirmation screen (FIG. 6C) on the terminal device 10 when the determination unit 105 determines that there is no error in the application content. The creation unit 108 transmits the created first service application content confirmation screen information from the communication unit 102 to the terminal device 10.

[0063] The communication unit 102 receives the application request sent by the terminal device 10 in response to the transmitted first service application content confirmation screen information. The acceptance unit 104 acquires the application request from the communication unit 102 and accepts the acquired application request. The processing unit 106 acquires the user ID, information indicating the advance application amount, information indicating the due date of payment to the seller, payee information, and credit card information contained in the application request accepted by the acceptance unit 104, and stores them in the memory unit 110 in association with each other.

[0064] The creation unit 108 creates first service application completion screen information for displaying a first service application completion screen (FIG. 6D) on the terminal device 10. The creation unit 108 transmits the created first service application completion screen information from the communication unit 102 to the terminal device 10. The processing unit 106 provides the first service by performing processing based on the user ID, information indicating the amount of the advance payment application, information indicating the due date of payment to the seller, payee information, and credit card information stored in the storage unit 110.

[0065] On the other hand, when the determination unit 105 determines that there is an error in the application content, the creation unit 108 creates application error notification screen information for displaying an application error notification screen (FIG. 6E) on the terminal device 10. The creation unit 108 transmits the created application error notification screen information from the communication unit 102 to the terminal device 10. A case will be described where the communication unit 102 receives a first service application information input request transmitted by the terminal device 10 in response to the application error notification screen information. The reception unit 104 acquires the first service application information input request from the communication unit 102 and accepts the acquired first service application information input request. The creation unit 108 creates application information input screen information for displaying an application information input screen on the terminal device 10 based on the first service application information input request accepted by the acceptance unit 104. The creation unit 108 transmits the created application information input screen information from the communication unit 102 to the terminal device 10.

[0066] A case will be described where the communication unit 102 receives a second service application information input request transmitted by the terminal device 10 in response to the application error notification screen information. The reception unit 104 acquires the second service application information input request from the communication unit 102 and accepts the acquired second service application information input request. The creation unit 108 creates application information input screen information for displaying an application information input screen including a second service application information input screen on the terminal device 10 based on the second service application information input request accepted by the acceptance unit 104. The creation unit 108 transmits the created application information input screen information from the communication unit 102 to the terminal device 10.

[0067] The communication unit 102 receives the first service application information discard request transmitted by the terminal device 10 in response to the application error notification screen information. The reception unit 104 acquires the first service application information discard request from the communication unit 102 and accepts the acquired first service application information discard request. The processing unit 106 discards the user ID and application details included in the first service application information discard request accepted by the acceptance unit 104. The creation unit 108 creates application information input screen information for displaying an application information input screen ( FIG. 6A ) on the terminal device 10 based on the first service application information discard request accepted by the acceptance unit 104. The creation unit 108 transmits the created application information input screen information from the communication unit 102 to the terminal device 10.

[0068] The communication unit 102 receives the second service application content confirmation request transmitted by the terminal device 10. The acceptance unit 104 acquires the second service application content confirmation request from the communication unit 102, and accepts the acquired second service application content confirmation request. The derivation unit 107 acquires information indicating the due date of payment to the seller included in the second service application content confirmation request, and derives the period from the application date to the due date of payment to the seller. The determination unit 105 acquires information indicating the period from the application date to the due date of payment to the seller from the derivation unit 107, and determines whether or not the period from the application date to the due date of payment to the seller is equal to or greater than a predetermined threshold. If the period from the application date to the due date of payment to the seller is less than the predetermined threshold, the determination unit 105 creates an alert. For example, the determination unit 105 creates an alert indicating that there is a possibility that the on-the-spot transfer by the business providing the second service will not be completed by the due date of payment to the seller. The derivation unit 107 also acquires information indicating the due date of payment to the seller included in the second service application content confirmation request, and derives the due date of payment from the buyer to the service provider. The determination unit 105 acquires information indicating the due date of payment from the buyer to the service provider from the derivation unit 107, and determines whether or not the period from the application date to the due date of payment from the buyer to the service provider is less than a predetermined number of days. If the period from the application date to the due date of payment from the buyer to the service provider is less than a predetermined number of days, the determination unit 105 creates an alert. For example, the determination unit 105 creates an alert indicating that the due date of payment from the service user to the second service provider after the execution of the advance payment will be close to the application date. Here, if the period from the application date to the due date of payment from the buyer to the service provider is less than a predetermined number of days, this also includes the case where the due date of payment to the seller is before (in the past) the application date. The creation unit 108 creates second service application content confirmation screen information for displaying a second service application content confirmation screen (FIG. 7C) on the terminal device 10 based on the determination result by the determination unit 105. The second service application content confirmation screen includes an alert as necessary. The creation unit 108 transmits the created second service application content confirmation screen information from the communication unit 102 to the terminal device 10.

[0069] The communication unit 102 receives the application request sent by the terminal device 10 in response to the transmitted second service application content confirmation screen information. The acceptance unit 104 acquires the application request from the communication unit 102 and accepts the acquired application request. The processing unit 106 acquires the user ID, information indicating the advance application amount, information indicating the due date of payment to the seller, payee information, and information indicating the name of the person requesting the transfer, which are included in the application request accepted by the acceptance unit 104, and stores them in the memory unit 110 in association with each other.

[0070] The creation unit 108 creates second service application completion screen information for displaying a second service application completion screen (FIG. 7D) on the terminal device 10. The creation unit 108 transmits the created second service application completion screen information from the communication unit 102 to the terminal device 10. The processing unit 106 provides the second service by performing processing based on the user ID, information indicating the amount applied for on-the-spot payment, information indicating the due date of payment to the seller, payee information, and information indicating the name of the person requesting the transfer, all of which are stored in the memory unit 110.

[0071] The reception unit 104, the determination unit 105, the processing unit 106, the derivation unit 107, and the creation unit 108 are realized by, for example, a hardware processor such as a CPU executing a computer program (software) stored in the storage unit 110. Furthermore, some or all of these functional units may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by a combination of software and hardware. The computer program may be stored in advance in a storage device such as a HDD or flash memory, or may be stored on a removable storage medium such as a DVD or CD-ROM and installed by inserting the storage medium into a drive device.

[0072] (Operation of bill advance payment system 1) 8 is a flow chart showing an example of the operation of the bill advance payment system 1 of this embodiment. With reference to FIG. 8, the initial setting of the bill advance payment system 1 will be described. (Step S1-1) The terminal device 10 logs in to the bill advance payment site provided by the information processing system 100. (Step S2-1) The creation unit 108 creates login screen information. (Step S3-1) The communication unit 102 transmits the login screen information created by the creation unit 108 to the terminal device 10.

[0073] (Step S4-1) The communication unit 12 receives login screen information. The processing unit 16 acquires the login screen information from the communication unit 12 and causes the display unit 19 to display the login screen. (Step S5-1) The operation unit 18 accepts an operation of pressing the initial setting button BU02 by the user U1. The creation unit 14 creates an initial setting request based on the operation accepted by the operation unit 18. (Step S6-1) The communication section 12 transmits the initial setting request created by the creation section 14 to the information processing system 100. (Step S7-1) The communication unit 102 receives an initial setting request. The reception unit 104 receives the initial setting request received by the communication unit 102. The creation unit 108 acquires the initial setting request from the reception unit 104 and creates initial setting screen information.

[0074] (Step S8-1) The communication unit 102 transmits the initial setting screen information created by the creation unit 108 to the terminal device 10. (Step S9-1) The communication unit 12 receives the initial setting screen information. The processing unit 16 acquires the initial setting screen information from the communication unit 12 and causes the display unit 19 to display the initial setting screen. (Step S10-1) The operation unit 18 accepts an operation by the user U1 to input a contracted business name, input a client name, and press the setting button BU03 for performing the next setting. The creation unit 14 creates the next initial setting request based on the operation accepted by the operation unit 18.

[0075] (Step S11-1) The communication section 12 transmits the next initial setting request created by the creation section 14 to the information processing system 100. (Step S12-1) The communication unit 102 receives the next initial setting request transmitted by the terminal device 10. The reception unit 104 acquires and accepts the next initial setting request from the communication unit 102. The creation unit 108 acquires the next initial setting request from the reception unit 104 and creates next initial setting screen information. (Step S13-1) The communication unit 102 transmits the next initial setting screen information created by the creation unit 108 to the terminal device 10. (Step S14-1) The communication unit 12 receives the next initial setting screen information transmitted by the information processing system 100. The processing unit 16 acquires the next initial setting screen information from the communication unit 12, and causes the display unit 19 to display the next initial setting screen.

[0076] (Step S15-1) The operation unit 18 receives an operation by the user U1 to input an invoice delivery address and press the initial setting completion button BU04. The creation unit 14 creates an initial setting completion request based on the operation received by the operation unit 18. (Step S16-1) The communication section 12 transmits the initial setting completion request created by the creation section 14 to the information processing system 100. (Step S17-1) The communication unit 102 receives an initial setting completion request transmitted by the terminal device 10. The reception unit 104 acquires and accepts the initial setting completion request from the communication unit 102. The processing unit 106 acquires the initial setting completion request from the reception unit 104, and stores the request in the storage unit 110 in association with the user ID included in the acquired initial setting completion request and the initial setting information input on the initial setting screen and the next initial setting screen.

[0077] (Step S18-1) The creation unit 108 creates application information input screen information. (Step S19-1) The communication unit 102 transmits the application information input screen information created by the creation unit 108 to the terminal device 10. (Step S20-1) The communication unit 12 receives the application information input screen information transmitted by the information processing system 100. The processing unit 16 acquires the application information input screen information from the communication unit 12, and causes the display unit 19 to display the application information input screen.

[0078] 9 is a flow chart showing an example of the operation of the bill advance payment system 1 of this embodiment. The first service process will be described with reference to FIG. (Step S1-2) The terminal device 10 logs in to the bill advance payment site provided by the information processing system 100. (Step S2-2) The creation unit 108 creates application information input screen information. (Step S3-2) The communication unit 102 transmits the application information input screen information created by the creation unit 108 to the terminal device 10.

[0079] (Step S4-2) The communication unit 12 receives the application information input screen information. The processing unit 16 acquires the application information input screen information from the communication unit 12 and causes the display unit 19 to display the application information input screen. (Step S5-2) The creation unit 14 judges whether or not an operation of pressing the second tab TA02 by the user U1 has been accepted by the operation unit 18. The process performed when an operation of pressing the second tab TA02 by the user U1 has been accepted by the operation unit 18 will be described later. (Step S6-2) If the operation unit 18 does not accept the operation of pressing the second tab TA02 by the user U1, the creation unit 14 accepts the operation of pressing the application content confirmation button BU04 by the user U1 to confirm the application content. The creation unit 14 creates an application content confirmation request based on the operation accepted by the operation unit 18. (Step S7-2) The communication unit 12 transmits the application content confirmation request created by the creation unit 14 to the information processing system 100. (Step S8-2) A payment on behalf setting process is performed between the terminal device 10 and the information processing system 100.

[0080] 10 is a flow chart showing an example of the operation of the bill advance payment system 1 of this embodiment. The advance payment setting process in step S8-2 of FIG. 9 will be described in detail with reference to FIG. (Step S8-2-1a) The communication unit 102 receives the application content confirmation request transmitted by the terminal device 10. The reception unit 104 acquires and accepts the application content confirmation request from the communication unit 102. The determination unit 105 acquires the user ID and information indicating the application content included in the application content confirmation request from the reception unit 104. The determination unit 105 confirms the application content based on the acquired information indicating the application content. (Step S8-2-2a) The judgment unit 105 judges whether or not there is an error in the acquired application content. A case where there is an error in the application content will be described later.

[0081] (Step S8-2-3a) If the determining unit 105 determines that there is no error in the application content, the creating unit 108 creates first service application content confirmation screen information. (Step S8-2-4a) The communication unit 102 transmits the first service application content confirmation screen information created by the creation unit 108 to the terminal device 10. (Step S8-2-5a) The communication unit 12 receives the first service application content confirmation screen information. The processing unit 16 acquires the first service application content confirmation screen information from the communication unit 12 and causes the display unit 19 to display the first service application content confirmation screen. (Step S8-2-6a) The operation unit 18 accepts an operation of pressing the application button BU05 by the user U1 for agreeing and applying. The creation unit 14 creates an application request based on the operation accepted by the operation unit 18.

[0082] (Step S8-2-7a) The communication unit 12 transmits the application request created by the creation unit 14 to the information processing system 100. (Step S8-2-8a) The communication unit 102 receives the application request transmitted by the terminal device 10. The reception unit 104 acquires and accepts the application request from the communication unit 102. The processing unit 106 acquires from the reception unit 104 the user ID, information indicating the advance application amount, information indicating the due date of payment to the seller, payee information, and credit card information contained in the application request, and stores them in the memory unit 110 in association with each other. (Step S8-2-9a) The creation unit 108 creates first service application completion screen information. (Step S8-2-10a) The communication unit 102 transmits the first service application completion screen information created by the creation unit 108 to the terminal device 10. (Step S8-2-11a) The communication unit 12 receives the first service application completion screen information. The processing unit 16 acquires the first service application completion screen information from the communication unit 12 and causes the display unit 19 to display the first service application completion screen.

[0083] Fig. 11 is a flow chart showing an example of the operation of the bill advance payment system 1 of this embodiment. With reference to Fig. 11, a process to be performed when it is determined in step S8-2-2a of Fig. 10 that there is an error in the application content will be described. (Step S8-2-1b) The generating unit 108 generates application error notification screen information. (Step S8-2-2b) The communication unit 102 transmits the application error notification screen information created by the creation unit 108 to the terminal device 10. (Step S8-2-3b) The communication unit 12 receives the application error notification screen information. The processing unit 16 acquires the application error notification screen information from the communication unit 12 and causes the display unit 19 to display the application error notification screen. (Step S8-2-4b) The operation unit 18 judges whether or not the operation of pressing the card change button BU08 has been accepted. (Step S8-2-5b) When the operation unit 18 accepts the pressing of the card change button BU08, the preparation unit 14 prepares a first service application information input request.

[0084] (Step S8-2-6b) The communication unit 12 transmits the first service application information input request created by the creation unit 14 to the information processing system 100. (Step S8-2-7b) If the operation of pressing the card change button BU08 has not been accepted, the operation unit 18 judges whether or not the operation of pressing the bank transfer switch button BU09 has been accepted. The process when the operation unit 18 accepts the operation of pressing the bank transfer switch button BU09 will be described later. (Step S8-2-8b) The creation unit 14 judges whether or not an operation to press the discard application content button BU10 has been accepted when the operation unit 18 has not accepted the operation to press the discard application content button BU10. When the operation to press the discard application content button BU10 has not been accepted, the process returns to step S8-2-4b.

[0085] (Step S8-2-9b) When the operation unit 18 accepts the operation of pressing the card change button BU08, the preparation unit 14 prepares a first service application information discard request. (Step S8-2-10b) The communication unit 12 transmits the first service application information discard request created by the creation unit 14 to the information processing system 100.

[0086] Fig. 12 is a flow chart showing an example of the operation of the invoice advance payment system 1 of this embodiment. With reference to Fig. 12, a process will be described in the case where the operation unit 18 accepts an operation of pressing the second tab TA02 by the user U1 in step S5-2 of Fig. 9, or where the operation unit 18 accepts an operation of pressing the bank transfer switch button BU09 in step S8-2-7b of Fig. 11. (Step S1-3) The preparation unit 14 prepares a second service application information input request. (Step S2-3) The communication unit 12 transmits the second service application information input request created by the creation unit 14 to the information processing system 100.

[0087] (Step S3-3) The communication unit 102 receives the second service application information input request. The reception unit 104 acquires and accepts the second service application information input request from the communication unit 102. The creation unit 108 creates second service application information input screen information based on the second service application information input request accepted by the reception unit 104. (Step S4-3) The communication unit 102 transmits the second service application information input screen information created by the creation unit 108 to the terminal device 10. (Step S5-3) The communication unit 12 receives the second service application information input screen information. The processing unit 16 acquires the second service application information input screen information from the communication unit 12 and causes the display unit 19 to display the second service application information input screen.

[0088] (Step S6-3) The operation unit 18 accepts an operation of pressing the application content confirmation button BU04 by the user U1. The creation unit 14 creates a second service application content confirmation request based on the operation accepted by the operation unit 18. (Step S7-3) The communication unit 12 transmits the second service application content confirmation request created by the creation unit 14 to the information processing system 100. (Step S8-3) The communication unit 102 receives the second service application content confirmation request. The reception unit 104 acquires and accepts the second service application content confirmation request from the communication unit 102. The creation unit 108 creates second service application content confirmation screen information based on the user ID, information indicating the advance application amount, information indicating the due date of payment to the seller, and payee information contained in the second service application content confirmation request accepted by the reception unit 104. Details of the process by which the creation unit 108 creates the second service application content confirmation screen information will be described later.

[0089] (Step S9-3) The communication unit 102 transmits the second service application content confirmation screen information created by the creation unit 108 to the terminal device 10. (Step S10-3) The communication unit 12 receives the second service application content confirmation screen information transmitted by the information processing system 100. The processing unit 16 acquires the second service application content confirmation screen information from the communication unit 12, and causes the display unit 19 to display the second service application content confirmation screen. (Step S11-3) The operation unit 18 accepts an operation of pressing the application button BU11 by the user U1. The creation unit 14 creates an application request based on the operation accepted by the operation unit 18. (Step S12-3) The communication unit 12 transmits the application request created by the creation unit 14 to the information processing system 100.

[0090] (Step S13-3) The communication unit 102 receives the application request. The acceptance unit 104 acquires and accepts the application request from the communication unit 102. The processing unit 106 acquires the user ID, information indicating the advance application amount, information indicating the due date of payment to the seller, payee information, and information indicating the name of the person requesting the transfer, which are included in the application request accepted by the acceptance unit 104, and stores these in the memory unit 110 in association with each other. (Step S14-3) The creation unit 108 creates second service application completion screen information. (Step S15-3) The communication unit 102 transmits the second service application completion screen information created by the creation unit 108 to the terminal device 10. (Step S16-3) The communication unit 12 receives the second service application completion screen information. The processing unit 16 acquires the second service application completion screen information from the communication unit 12 and causes the display unit 19 to display the second service application completion screen.

[0091] Fig. 13A is a flow chart showing an example of the operation of the invoice advance payment system 1 of this embodiment. Details of the process of step S8-3 in Fig. 12 will be described with reference to Fig. 13A. (Step S8-3-1a) The communication unit 102 receives a second service application content confirmation request. The acceptance unit 104 acquires and accepts the second service application content confirmation request from the communication unit 102. The derivation unit 107 acquires information indicating the due date of payment to the seller included in the second service application content confirmation request, and derives the period from the application date to the due date of payment to the seller. The judgment unit 105 acquires information indicating the period from the application date to the due date of payment to the seller from the derivation unit 107, and judges whether the number of days (period) from the application date to the due date of payment to the seller is equal to or greater than a predetermined threshold value. (Step S8-3-2a) When the determining unit 105 determines that the number of days until the due date of payment to the seller is equal to or greater than the threshold, the creating unit 108 creates second service application content confirmation screen information. (Step S8-3-3a) When the judgment unit 105 judges that the number of days until the due date of payment to the seller is not greater than the threshold (is less than the threshold), the creation unit 108 creates second service application content confirmation screen information including an alert to notify that the number of days until the due date of payment to the seller is not greater than the threshold (is less than the threshold).

[0092] Fig. 13B is a flow chart showing an example of the operation of the invoice advance payment system 1 of this embodiment. Details of the process of step S8-3 in Fig. 12 will be described with reference to Fig. 13B. (Step S8-3-1b) The communication unit 102 receives the second service application content confirmation request. The reception unit 104 acquires and accepts the second service application content confirmation request from the communication unit 102. The derivation unit 107 acquires information indicating the due date of payment to the seller, which is included in the second service application content confirmation request, and derives the due date of payment from the buyer to the business providing the service. The determination unit 105 acquires information indicating the due date of payment to the seller from the buyer and information indicating the due date of payment from the buyer to the business providing the service from the derivation unit 107, and determines whether the payment due date, which is the period from the due date of payment from the buyer to the seller to the due date of payment from the buyer to the business providing the service, is equal to or greater than a predetermined threshold value. (Step S8-3-2b) When the determining unit 105 determines that the number of days until the payment due date is equal to or greater than the threshold, the creating unit 108 creates second service application content confirmation screen information. (Step S8-3-3b) When the judgment unit 105 judges that the number of days until the payment due date is not greater than or equal to the threshold (is less than the threshold), the creation unit 108 creates second service application content confirmation screen information including an alert to notify that the number of days until the payment due date is not greater than or equal to the threshold (is less than the threshold).

[0093] In the above-described embodiment, the information processing system 100 creates application error notification screen information including information RI01 for notifying the reason why the card cannot be used and information RI02 for notifying that the card cannot be used when it is determined that there is an error in the application content confirmation request sent by the terminal device 10, but this example is not limited to this. For example, in the information processing system 100, the processing unit 106 may acquire an application content confirmation request accepted by the acceptance unit 104, request a payment service provider to make a card payment based on the acquired application content confirmation request, and create application error notification screen information based on the response from the payment service provider.

[0094] The process in this case will be described in detail. The judgment unit 105 acquires the response from the payment business operator acquired by the processing unit 106, and judges the type of error included in the acquired response from the payment business operator. The judgment unit 105 judges whether or not there is a high possibility of an error occurring even if the card requested to make a card payment to the payment business operator or another card other than the card is reapplied based on the judgment result of the type of error included in the response from the payment business operator. For example, if the type of error is due to a malfunction of the network NW, the judgment unit 105 judges that there is a high possibility of an error occurring even if the card requested to make a card payment to the payment business operator or another card other than the card is reapplied. In this case, the creation unit 108 creates application error notification screen information including information for encouraging payment by bank transfer, and transmits the created application error notification screen information from the communication unit 102 to the terminal device 10. 14A is a diagram showing an example of an application error notification screen for the bill advance payment service. The application error notification screen further includes information for notifying the user that an error has occurred, a bank transfer switch button BU13 for switching to bank transfer, and a discard application button BU10 for discarding the application contents.

[0095] Furthermore, the determination unit 105 determines whether or not there is a high possibility of an error occurring even if a reapplication is made with the card that has been requested to make card payment to the payment business operator, based on the determination result of the type of error included in the response from the payment business operator. For example, if the type of error is that the card's credit limit has been exceeded or that the card's expiration date has passed, the determination unit 105 determines that there is a high possibility of an error occurring even if a reapplication is made with the card that has been requested to make card payment to the payment business operator. In this case, the creation unit 108 creates application error notification screen information including information for encouraging reapplication using a card other than the card for which the payment company has been requested to make the card payment, and information for encouraging payment by bank transfer, and transmits the created application error notification screen information from the communication unit 102 to the terminal device 10. 14B is a diagram showing an example of an application error notification screen for the bill advance payment service. The application error notification screen further includes information for notifying that an error has occurred, a bank transfer switch button BU13 for switching to payment by bank transfer, another card selection button BU14 for selecting a card other than the card for which the payment service provider has been requested to make the card payment, and an application content discard button BU10 for discarding the application content.

[0096] Furthermore, the determination unit 105 determines whether or not there is a low possibility of an error occurring when resubmitting an application using the card that has been requested to make card payment to the payment business operator, based on the determination result of the type of error included in the response from the payment business operator. For example, when an error occurs in personal authentication using 3D Secure, the determination unit 105 determines that there is a low possibility of an error occurring when resubmitting an application using the card that has been requested to make card payment to the payment business operator. In this case, the creation unit 108 creates application error notification screen information including information for encouraging the payment company to reapply using a card other than the card for which the card payment has been requested, information for encouraging payment by bank transfer, and information for encouraging the payment company to reapply using the card for which the card payment has been requested, and transmits the created application error notification screen information from the communication unit 102 to the terminal device 10. 14C is a diagram showing an example of an application error notification screen for the bill advance payment service. The application error notification screen includes information for notifying the user that an error has occurred, a bank transfer switch button BU13 for switching to payment by bank transfer, another card selection button BU14 for selecting a card other than the card for which the payment service provider has been requested to make the card payment, a same card application button BU15 for applying for the same card as the card for which the payment service provider has been requested to make the card payment, and a discard application content button BU10 for discarding the application content.

[0097] The process flow for creating application error notification screen information based on a response from the settlement service provider will be described below. The process for setting up advance payment in step S8-2 in FIG. 15 is a flow chart showing an example of the operation of the bill advance payment system 1 of this embodiment. With reference to FIG. 15, the advance payment setting process of step S8-2 in FIG. (Step S8-2-1c) The communication unit 102 receives the application content confirmation request. The acceptance unit 104 acquires and accepts the application content confirmation request from the communication unit 102. The processing unit 106 acquires the application content confirmation request accepted by the acceptance unit 104, requests the payment company to make a card payment, and acquires a response such as an error code from the payment company. (Step S8-2-2c) The determination unit 105 acquires the response from the payment service provider acquired by the processing unit 106, and determines the type of error included in the response from the payment service provider. The creation unit 108 creates application error notification screen information based on the result of the error type determination by the determination unit 105. Steps S8-2-3c to S8-2-11c can be applied to steps S8-2-2b to S8-2-10b in FIG. 11, so a description thereof will be omitted.

[0098] (View application history) (Terminal device 10) A case will be described where the user U1 presses the history button HBU on the application information input screen (FIG. 6A). The operation unit 18 accepts the operation. The creation unit 14 creates an application history request including information indicating the user ID and application history based on the operation accepted by the operation unit 18, and transmits the created application history request from the communication unit 12 to the information processing system 100. The application history screen information transmitted by the information processing system 100 in response to the application history request is received by the communication unit 12. The processing unit 16 acquires the application history screen information from the communication unit 12, and causes the display unit 19 to display the application history screen based on the acquired application history screen information.

[0099] 16A is a diagram showing an example of an application history screen for an invoice advance payment service. The application history screen displays the application history divided into a number of different categories based on the status of the payment by credit card settlement of the applied buyer. The application history screen includes an application button ABU, a history button HBU, a billing button BBU, a Display Application Content Before Advance Payment Execution button BPBU for displaying the application content before advance payment is executed, a Display Application Content After Advance Payment Execution button APBU for displaying the application content after advance payment is executed, and a Display Application Content Not Allowed for Advance Payment Execution button SBBU for displaying the application content for which advance payment cannot be executed.

[0100] Furthermore, the application history screen includes a payment due date selection button PDSBU for selecting the due date of payment to the business partner, and pre-advance payment history BPHI. Immediately after the application history screen is launched, the pre-advance payment history BPHI is displayed. One or more applications included in the pre-advance payment history BPHI include applications with incomplete input, applications awaiting confirmation (currently being confirmed), applications awaiting advance payment transfer, and canceled applications. One example of an input error is an incorrect name. Applications awaiting confirmation (currently being confirmed) and applications awaiting advance payment transfer include information indicating the due date of payment of the invoice issued by the seller and information indicating the due date of payment for the service.

[0101] The user U1 performs an operation of pressing the "Display application content after advance payment execution" button APBU on the application history screen (FIG. 16A). The operation unit 18 accepts the operation. The creation unit 14 creates an application history request including the user ID and information indicating after advance payment execution based on the operation accepted by the operation unit 18, and transmits the created application history request from the communication unit 12 to the information processing system 100. The application history screen information transmitted by the information processing system 100 in response to the application history request is received by the communication unit 12. The processing unit 16 acquires the application history screen information from the communication unit 12, and causes the display unit 19 to display the application history screen based on the acquired application history screen information.

[0102] Fig. 16B is a diagram showing an example of an application history screen for an invoice advance payment service. On the application history screen in Fig. 16A, the post-advance payment history APHI is displayed in place of the pre-advance payment history BPHI. That is, when the post-advance payment application content display button APBU is pressed on the application history screen, the post-advance payment history APHI is displayed. One or more applications included in the post-advance payment history APHI include applications after the advance payment has been made. The post-advance payment application includes information indicating the advance payment date and information indicating the payment due date for the service. The user U1 performs an operation of pressing the button SBBU for displaying the application content of the non-performance of advance payment on the application history screen. The operation unit 18 accepts the operation. The creation unit 14 creates an application history request including the user ID and information indicating the non-performance of advance payment on the basis of the operation accepted by the operation unit 18, and transmits the created application history request from the communication unit 12 to the information processing system 100.

[0103] The application history screen information transmitted by the information processing system 100 in response to the application history request is received by the communication unit 12. The processing unit 16 acquires the application history screen information from the communication unit 12, and causes the display unit 19 to display the application history screen based on the acquired application history screen information. Fig. 16C is a diagram showing an example of an application history screen for the bill advance payment service. On the application history screen in Fig. 16A, the advance payment impossibility history SBHI is displayed in the portion of the pre-advance payment history BPHI. That is, when the advance payment impossibility application content display button SBBU is pressed on the application history screen, the advance payment impossibility history SBHI is displayed. One or more applications included in the advance payment impossibility history SBHI include an application for advance payment impossibility.

[0104] The user U1 performs an operation of pressing one or more application sections in the pre-payment history BPHI included in the application history screen. The operation unit 18 accepts the operation. The creation unit 14 creates an application information request including the user ID and application identification information based on the operation accepted by the operation unit 18, and transmits the created application information request from the communication unit 12 to the information processing system 100. The application history detail screen information transmitted by the information processing system 100 in response to the application information request is received by the communication unit 12. The processing unit 16 acquires the application history detail screen information from the communication unit 12, and causes the display unit 19 to display the application history detail screen based on the acquired application history detail screen information.

[0105] Fig. 17A is a diagram showing an example of an application history details screen for the bill advance payment service. Fig. 17A shows, as an example, an application history details screen for the application content before the advance payment was made using the second service. The application history details screen includes information indicating the advance application amount, information indicating the fee, information indicating the due date of payment to the seller, information indicating the due date of payment to the service, information indicating the payee, and information indicating the name of the requester.

[0106] In addition, the user U1 performs an operation of pressing (selecting) one or more application portions in the post-payment history APHI included in the application history screen. The operation unit 18 accepts the operation. The creation unit 14 creates an application information request including the user ID and application identification information based on the operation accepted by the operation unit 18, and transmits the created application information request from the communication unit 12 to the information processing system 100. The application history detail screen information transmitted by the information processing system 100 in response to the application information request is received by the communication unit 12. The processing unit 16 acquires the application history detail screen information from the communication unit 12, and causes the display unit 19 to display the application history detail screen based on the acquired application history detail screen information. Fig. 17B is a diagram showing an example of an application history details screen for an invoice advance payment service. Fig. 17B shows, as an example, an application history details screen for the application content after advance payment has been made using the first service. The application history details screen includes information indicating the advance payment application amount, information indicating the fee, information indicating the date of payment to the business partner, information indicating the payee, credit card information, and information indicating the requester's name. In Fig. 17B, payment to the business partner (buyer) has been made, so compared to Fig. 17A, the due date for payment to the business partner has been switched to the payment date.

[0107] (Information processing system 100) The communication unit 102 receives the application history request transmitted by the terminal device 10. The reception unit 104 acquires the application history request from the communication unit 102 and accepts the acquired application history request. The creation unit 108 creates application history screen information based on the application history request accepted by the reception unit 104. The creation unit 108 transmits the created application history screen information from the communication unit 102 to the terminal device 10. The communication unit 102 receives the application history request sent by the terminal device 10 in response to the application history screen information it sent. The acceptance unit 104 acquires the application history request from the communication unit 102 and accepts the acquired application history request. The processing unit 106 acquires the user ID and information indicating after advance payment has been made, which are included in the application history request accepted by the acceptance unit 104. The processing unit 106 creates application history screen information based on the acquired user ID and information indicating after advance payment has been made. The creation unit 108 transmits the created application history screen information from the communication unit 102 to the terminal device 10. The processing unit 106 acquires the user ID and information indicating after advance payment has been performed, which are included in the application history request accepted by the acceptance unit 104. The processing unit 106 creates application history screen information based on the acquired user ID and information indicating that advance payment cannot be performed. The creation unit 108 transmits the created application history screen information from the communication unit 102 to the terminal device 10.

[0108] The communication unit 102 receives the application information request sent by the terminal device 10 in response to the transmitted application history screen information. The reception unit 104 acquires the application information request from the communication unit 102 and accepts the acquired application information request. The processing unit 106 acquires the user ID and application identification information included in the application information request accepted by the reception unit 104. The processing unit 106 creates application history detail screen information based on the acquired user ID and application identification information. The creation unit 108 transmits the created application history detail screen information from the communication unit 102 to the terminal device 10.

[0109] An explanation will be given of the process of displaying the application history of the bill advance payment system 1. Fig. 18 is a flowchart showing an example of the operation of the bill advance payment system 1 of this embodiment. (Step S1-4) The terminal device 10 logs in to the bill advance payment site provided by the information processing system 100. (Step S2-4) The creation unit 108 creates application information input screen information. (Step S3-4) The communication unit 102 transmits the application information input screen information created by the creation unit 108 to the terminal device 10. (Step S4-4) The communication unit 12 receives the application information input screen information. The processing unit 16 acquires the application information input screen information from the communication unit 12 and causes the display unit 19 to display the application information input screen.

[0110] (Step S5-4) The creation unit 14 creates an application history request based on the operation of pressing the history button HBU accepted by the operation unit 18 on the application information input screen. (Step S6-4) The communication unit 12 transmits the application history request created by the creation unit 14 to the information processing system 100. (Step S7-4) The communication unit 102 receives the application history request. The acceptance unit 104 acquires and accepts the application history request from the communication unit 102. The creation unit 108 creates application history screen information based on the application history request accepted by the acceptance unit 104. (Step S8-4) The communication unit 102 transmits the application history screen information created by the creation unit 108 to the terminal device 10. (Step S9-4) The communication unit 12 receives the application history screen information. The processing unit 16 acquires the application history screen information from the communication unit 12 and causes the display unit 19 to display the application history screen.

[0111] (Step S10-4) The creation unit 14 creates an application information request based on an operation of pressing any one of the portions of one or more applications accepted by the operation unit 18 on the application history screen. (Step S11-4) The communication unit 12 transmits the application information request created by the creation unit 14 to the information processing system 100. (Step S12-4) The communication unit 102 receives the application information request. The acceptance unit 104 acquires and accepts the application information request from the communication unit 102. The processing unit 106 acquires the user ID and application identification information included in the application information request accepted by the acceptance unit 104, and creates application history detail screen information. (Step S13-4) The communication unit 102 transmits the application history detail screen information created by the creation unit 108 to the terminal device 10. (Step S14-4) The communication unit 12 receives the application history detail screen information transmitted by the information processing system 100. The processing unit 16 acquires the application history detail screen information from the communication unit 12, and causes the display unit 19 to display the application history detail screen.

[0112] (View billing list) (Terminal device 10) A case will be described where the user U1 presses the request button BBU on the application information input screen (FIG. 6A). The operation unit 18 accepts the operation. The creation unit 14 creates a request list request including the user ID and information indicating a request based on the operation accepted by the operation unit 18, and transmits the created request request from the communication unit 12 to the information processing system 100. The billing list screen information transmitted by the information processing system 100 in response to the billing request is received by the communication unit 12. The processing unit 16 acquires the billing list screen information from the communication unit 12, and causes the display unit 19 to display the billing list screen based on the acquired billing list screen information.

[0113] 19 is a diagram showing an example of a billing list screen of the bill advance payment service. The billing list screen shows a list of amounts to be billed to user U1 for making a bank transfer payment on behalf of the buyer in the second service. The claim list screen includes an application button ABU, a history button HBU, and a claim button BBU. The claim list screen includes information indicating the transfer destination and a claim list INL. The claim list INL may include at least one of awaiting transfer, which is a claim for which payment from the buyer has not been completed, transferred, which is a claim for which payment from the buyer has been completed, and another claim, which is a claim for which payment from the buyer is not required. Here, an example of a claim for which payment from the buyer is not required is a claim for which a bond has been transferred. In addition, a claim for which payment from the buyer has not been completed even though the payment due date has passed may be displayed in a different color from a claim for which payment from the buyer has been completed.

[0114] (Information processing system 100) The communications unit 102 receives the invoice list request sent by the terminal device 10. The reception unit 104 acquires the invoice list request from the communications unit 102 and accepts the acquired invoice list request. The creation unit 108 creates invoice list screen information including a list of amounts to be invoiced to the buyer based on the payment of the invoice issued by the seller by the processing unit 106, based on the invoice list request accepted by the reception unit 104. The creation unit 108 transmits the created invoice list screen information from the communications unit 102 to the terminal device 10.

[0115] The effects of this embodiment will be described. According to the information processing system 100 of the embodiment, the information processing system 100 includes a first tab TA01 for selecting a first service that accepts the payment of an invoice on behalf of the buyer by card payment and a second tab TA02 for selecting a second service that accepts the payment of an invoice on behalf of the buyer by bank transfer, and includes a creation unit 108 that creates first application information input screen information for inputting application information for payment by card payment, a communication unit 102 as an output unit that outputs the first application information input screen information, a reception unit 104 that accepts the first application information input by the buyer on the first application information input screen displayed by processing the first application information input screen information, and a processing unit 106 that performs processing to pay the invoice on behalf of the buyer by card payment based on the first application information. By configuring in this way, the information processing system 100 can create first application information input screen information including the first tab TA01 and the second tab TA02, making it easier for the buyer to select the first service than when the first tab TA01 and the second tab TA02 are not used. In the information processing system 100, the reception unit 104 receives information associated with the second tab selected by the buyer, the creation unit 108 creates second application information input screen information for inputting application information for payment by bank transfer, including the first tab TA01 and the second tab TA02, based on the information associated with the second tab TA02, and the output unit outputs the second application information input screen information. By configuring in this way, when the buyer selects the second tab, the information processing system 100 can create second application information input screen information including the first tab TA01 and the second tab TA02, making it easier for the buyer to select the second service than if the first tab TA01 and the second tab TA02 were not used. In the information processing system 100, the reception unit 104 receives the second application information input by the buyer on the second application information input screen displayed by processing the second application information input screen information, and the processing unit 106 performs processing to pay the invoice by bank transfer on behalf of the buyer based on the second application information. By configuring in this way, the information processing system 100 can pay the invoice by bank transfer on behalf of the buyer based on the second application information input by the buyer selecting the second tab on the second application information input screen. In the information processing system 100, the output unit outputs first application information input screen information immediately after the buyer logs in. By configuring in this way, the information processing system 100 allows the buyer to input the first application information without having to perform an operation to display the first application information input screen. In the information processing system 100, the creation unit 108 creates first application information input screen information in which the first tab and the second tab are arranged side by side. By configuring in this way, the information processing system 100 can allow the buyer to easily select the first service and the second service compared to a case in which the first tab and the second tab are arranged in a position other than the left and right.

[0116] The information processing system 100 also includes a creating unit 108 as a first creating unit that creates first application information input screen information for inputting application information for performing invoice payment on behalf of the buyer by card payment, an output unit that outputs the first application information input screen information, a receiving unit 104 that receives the first application information input by the buyer on the first application information input screen displayed by processing the first application information input screen information, a determining unit 105 that determines whether or not it is possible to perform invoice payment on behalf of the buyer by card payment based on the first application information, and the creating unit 108 as a second creating unit that creates error notification screen information for notifying an error including a card selection button for selecting another card other than the card when the determining unit 105 determines that it is impossible to perform invoice payment on behalf of the buyer by card payment. The output unit outputs the error notification screen information. By configuring in this way, the information processing system 100 can notify the buyer of the fact when it is determined that it is impossible to perform invoice payment on behalf of the buyer by card payment. In the information processing system 100, the determination unit 105 determines whether the invoice payment amount via card payment included in the first application information exceeds the card's credit limit. By configuring in this way, the information processing system 100 can determine whether it is possible to pay the invoice via card payment on behalf of the buyer. The information processing system 100 further includes a processing unit 106 that performs processing to pay the invoice by card payment on behalf of the buyer when the determination unit 105 determines that it is possible to pay the invoice by card payment on behalf of the buyer. By configuring in this manner, the information processing system 100 can pay the invoice by card payment on behalf of the buyer. In the information processing system 100, the error notification screen obtained by the buyer processing the error notification screen information includes information for notifying the buyer that the card cannot be used. By configuring in this way, the information processing system 100 can notify the buyer that the cause of the error is that the card cannot be used.

[0117] The information processing system 100 also includes a creation unit 108 as a first creation unit that creates first application information input screen information for inputting application information for a buyer's card payment to be substituted for the payment of an invoice, an output unit that outputs the first application information input screen information, a reception unit 104 that receives the first application information input by the buyer on the first application information input screen, a determination unit 105 that determines whether or not it is possible to substitute for the buyer's card payment based on the first application information received by the reception unit 104, and the creation unit 108 as a second creation unit that creates error notification screen information for notifying an error including a selection button for selecting a payment means other than the card when the determination unit 105 determines that it is impossible to substitute for the amount of the invoice to be paid by the buyer's card payment included in the first application information. The output unit outputs the error notification screen information created by the creation unit 108. By configuring in this manner, the information processing system 100 can notify an error including a selection button for selecting a payment method other than the card if it is determined that the amount of the invoice to be paid by card payment from the buyer cannot be paid on behalf of the buyer by card payment. In the information processing system 100, the creation unit 108 creates error notification screen information that further includes a bank transfer selection button for changing to payment of the invoice by bank transfer when it is determined by the determination unit 105 that the amount of the invoice to be paid by card, which is included in the first application information, is such that it is impossible to act on behalf of the buyer to pay by card. By configuring in this way, the information processing system 100 can change the payment of the invoice to payment by bank transfer when it is determined that the amount of the invoice to be paid by card of the buyer is such that it is impossible to act on behalf of the buyer to pay by card. In the information processing system 100, when the determination unit 105 determines that the payment amount by card settlement included in the first application information exceeds the card's credit limit, the creation unit 108 creates error notification screen information further including a card selection button for selecting a card other than the card. By configuring in this manner, the information processing system 100 allows the buyer to select a card other than the card when the payment amount by card settlement of the buyer exceeds the card's credit limit. The information processing system 100 further includes a processing unit 106 that pays the invoice through the buyer's card payment when the determination unit 105 determines that the invoice can be paid on behalf of the buyer through the buyer's card payment. By configuring in this way, the information processing system 100 can perform processing to pay the invoice on behalf of the buyer through the buyer's card payment.

[0118] The information processing system 100 also includes a reception unit 104 that receives application information for performing bill payment on behalf of the buyer by card payment, a processing unit 106 that requests card payment to a payment service provider based on the application information and obtains a response from the payment service provider, and a creation unit 108 that creates notification screen information for notifying the buyer based on the response from the payment service provider. By configuring in this way, the information processing system 100 can create notification screen information for notifying the buyer based on the response from the payment service provider that requested card payment, so that it can notify user U1 of appropriate information compared to a case where a uniform notification is given. The information processing system 100 further includes a determination unit 105 that determines the type of error included in the response from the payment service provider, and the creation unit 108 creates notification screen information based on the result of the determination of the type of error by the determination unit 105. With this configuration, the information processing system 100 can create notification screen information for notifying the buyer based on the type of error included in the response from the payment service provider that has requested card payment, and therefore can notify user U1 of appropriate information compared to the case where a uniform notification is given. In the information processing system 100, the determination unit 105 determines whether or not there is a high possibility of an error occurring even if the payment company is resubmitted using the card that has been requested to make the card payment with the payment company or a card other than that card, based on the type of error, and the creation unit 108 creates notification screen information including a bank transfer selection button for changing to payment of the invoice by bank transfer when the determination unit 105 determines that there is a high possibility of an error occurring. By configuring in this way, the information processing system 100 can change to payment of the invoice by bank transfer when there is a high possibility of an error occurring even if the payment company is resubmitted using the card that has been requested to make the card payment with the payment company or a card other than that card. In the information processing system 100, the determination unit 105 determines whether or not there is a high possibility of an error occurring even if a reapplication is made with the card that has been requested to make the card payment to the payment business operator, based on the type of error, and the creation unit 108 creates notification screen information including a card selection button for selecting a card other than the card or a bank transfer selection button for changing to paying the invoice by bank transfer when the determination unit 105 determines that there is a high possibility of an error occurring. By configuring in this manner, the information processing system 100 can allow a card other than the card to be selected or change to paying the invoice by bank transfer when there is a high possibility of an error occurring even if a reapplication is made with the card that has been requested to make the card payment to the payment business operator. In the information processing system 100, the determination unit 105 determines whether or not there is a low possibility of an error occurring even if the payment business operator is resubmitted using the card that has been requested to make the card payment, based on the type of error, and when the determination unit 105 determines that there is a low possibility of an error occurring, the creation unit 108 creates notification screen information including a reapplication selection button for resubmitting using that card, a card selection button for changing to another card other than that card, or a bank transfer selection button for changing to payment of the invoice by bank transfer. By configuring in this way, the information processing system 100, when there is a low possibility of an error occurring when resubmitting using the card that has been requested to make the card payment to the payment business operator, can cause the user to resubmit using that card, change to another card other than that card, or change to payment by bank transfer.

[0119] The information processing system 100 also includes a receiving unit 104 that receives application information for having the invoice paid on behalf of the buyer by bank transfer, a derivation unit 107 that derives the due date of payment from the buyer to the service based on the application information, and a creation unit 108 that creates notification information for notifying the buyer of the due date of payment from the buyer to the service. By configuring in this way, the information processing system 100 can derive the due date of payment from the buyer to the service based on the application information and notify the buyer. In the information processing system 100, the derivation unit 107 derives the due date of payment from the buyer to the service after the execution of the on-the-spot payment based on the due date of payment to the seller included in the application information. By configuring in this way, the information processing system 100 can derive the due date of payment from the buyer to the service after the execution of the on-the-spot payment based on the due date of payment to the seller and notify the buyer. In the information processing system 100, the creation unit 108 creates application information input screen information including notification information. By configuring in this way, the information processing system 100 can notify the buyer of the notification information via the application information input screen.

[0120] The information processing system 100 also includes a receiving unit 104 that receives application information for paying an invoice on behalf of the buyer by bank transfer, and a creation unit 108 that creates notification information to be notified to the buyer based on the application date when the application information was received and the due date of payment to the seller included in the application information. By configuring in this way, the information processing system 100 can create notification information to be notified to the buyer based on the application date when the application information was received and the due date of payment to the seller included in the application information, and notify the buyer. The information processing system 100 further includes a determination unit 105 that determines whether the application date is after the due date of payment to the seller, and the creation unit 108 creates notification information based on the determination result by the determination unit 105. By configuring in this manner, the information processing system 100 can create notification information based on whether the application date is after the due date of payment to the seller, and notify the buyer. In the information processing system 100, when the determination unit 105 determines that the application date is after the due date of payment to the seller, the creation unit 108 creates notification information notifying the buyer that the due date of payment to the seller has passed. By configuring in this way, the information processing system 100 can notify the buyer that the due date of payment to the seller has passed. The information processing system 100 further comprises a derivation unit 107 that derives the period from the application date to the due date of payment to the seller, and a determination unit 105 that determines whether the period is equal to or greater than a predetermined threshold, and when the determination unit 105 determines that the period is less than the predetermined threshold, the creation unit 108 creates notification information that notifies the user that the on-the-spot transfer to the seller may not be completed by the due date. By configuring in this way, the information processing system 100 can notify the user that the on-the-spot transfer to the seller may not be completed by the due date, thereby alerting the user U1.

[0121] The information processing system 100 also includes a receiving unit 104 that receives application information for performing payment of an invoice on behalf of the buyer by bank transfer, and a creating unit 108 that creates notification information for notifying the buyer of information regarding the due date of payment for the service amount, based on the application date when the application information was received and the due date of payment to the seller included in the application information. By configuring in this way, the information processing system 100 can notify the buyer of information regarding the due date of payment for the service amount. The information processing system 100 further comprises a derivation unit 107 that derives the payment due date of the amount resulting from having acted on behalf of the buyer to pay the invoice via bank transfer based on the application information, and a creation unit 108 creates notification information for notifying the buyer of information regarding the payment due date of the amount for the service based further on the information indicating the payment due date of the amount resulting from having acted on behalf of the buyer to pay the invoice via bank transfer derived by the derivation unit 107. By configuring in this manner, the information processing system 100 can create and notify the buyer of information regarding the payment due date of the amount for the service. The information processing system 100 further includes a determination unit 105 that determines whether the application date is after the due date of payment to the seller and before the due date of payment from the buyer to the service, and the creation unit 108 creates notification information for notifying the buyer of information regarding the due date of payment for the service when the determination unit 105 determines that the application date is after the due date of payment to the seller and before the due date of payment from the buyer to the service. By configuring in this manner, the information processing system 100 can create and notify notification information for notifying the buyer of information regarding the due date of payment for the service when it is determined that the application date is after the due date of payment to the seller and before the due date of payment from the buyer to the service. In the information processing system 100, the creation unit 108 creates notification information for notifying the buyer that the payment for the service is coming due soon. By configuring in this way, the information processing system 100 can notify the buyer that the payment for the service is coming due soon, thereby reducing the chance of the buyer forgetting to pay. In the information processing system 100, the creation unit 108 creates application content confirmation screen information including notification information. With this configuration, the information processing system 100 can notify the notification information on the application content confirmation screen.

[0122] The information processing system 100 also includes a creation unit 108 that creates application history list information including the history of applications for requests to act on behalf of a buyer to pay invoices issued by a seller, and an output unit that outputs the application history list information, and the creation unit 108 creates different categories of application history list information based on the status of the agent's payment of the buyer's invoice. By configuring in this way, the information processing system 100 can create and notify application history list information based on the status of the agent's payment of the invoice by card settlement of the buyer. In the information processing system 100, the application history list information includes application contents of before advance payment, after advance payment, or impossible advance payment. By configuring in this way, the information processing system 100 can notify application contents of before advance payment, after advance payment, or impossible advance payment. In the information processing system 100, the application contents before the execution of the advance payment include application contents that are incomplete or are under review. By configuring in this way, the information processing system 100 can notify the application contents that are incomplete or are under review. In the information processing system 100, the application contents before the execution of the advance payment include application contents that are pending an advance payment transfer or that are not possible to be advanced. By configuring in this way, the information processing system 100 can notify the application contents that are pending an advance payment transfer or that are not possible to be advanced. In the information processing system 100, the content of the application that has been cancelled is included in the content of the application before the advance payment is made. By configuring in this way, the information processing system 100 can notify the content of the application that has been cancelled. In the information processing system 100, the creation unit 108 creates application history list information including the history of applications for requests for proxy payment of invoices issued by sellers by buyers' card payments or bank transfers. By configuring in this way, the information processing system 100 can notify the history of applications for requests for proxy payment of invoices issued by buyers by card payments or bank transfers.

[0123] The information processing system 100 also comprises a creation unit 108 that creates application history list information including the history of applications for requests to act on behalf of the buyer for card payment, and an output unit that outputs the application history list information, the application history list information including the application contents before the advance payment is made, which includes information indicating the payment due date of the invoice issued by the seller. By configuring in this way, the information processing system 100 can create the application history list information and notify the buyer, thereby making it possible to inform user U1 of the application history list. In the information processing system 100, the application content before the advance payment is made further includes information indicating the due date of payment for the service. By configuring in this way, the information processing system 100 can inform the user U1 of the due date of payment for the service. In the information processing system 100, the application history list information includes the application contents after the advance payment is made, and the application contents after the advance payment is made include information indicating the advance payment date. By configuring in this way, the information processing system 100 can inform the user U1 of the application contents after the advance payment is made. In the information processing system 100, the application content after the advance payment is executed further includes information indicating the due date of payment for the service. By configuring in this way, the information processing system 100 can inform the user U1 of the application content after the advance payment is executed.

[0124] The information processing system 100 also includes an acceptance unit 104 that accepts application information for making payment of an invoice issued by the seller by bank transfer from the buyer, and a processing unit 106 that makes payment of the invoice issued by the seller based on the application information and bills the buyer for the amount of the bank transfer payment, and if the billed amount is not transferred within a predetermined period of time, the processing unit 106 obtains the amount from the settlement service used by the buyer.By configuring in this way, the information processing system 100 can obtain the billed amount from the settlement service used by the buyer even if the billed amount is not transferred within a predetermined period of time. In the information processing system 100, the processing unit 106 subtracts the invoiced amount from the amount credited to the buyer's account according to the settlement amount of the settlement service used by the buyer. By configuring in this way, the information processing system 100 can obtain the amount for making the payment to the buyer by bank transfer by subtracting the invoiced amount from the amount credited to the buyer's account. The information processing system 100 further includes a derivation unit 107 that derives a due date for payment from the buyer to the service based on the application information received by the reception unit 104, and the processing unit 106 acquires the amount from the settlement service used by the buyer when the invoiced amount is not transferred even after the due date for payment from the buyer to the service has passed. By configuring in this way, the information processing system 100 can acquire the invoiced amount from the settlement service used by the buyer even when the invoiced amount is not transferred even after the due date for payment from the buyer to the service derived based on the application information has passed. In the information processing system 100, the amount included in the invoice includes the payment amount of the invoice issued by the seller and a fee for the payment. By configuring in this way, the information processing system 100 can obtain the amount including the payment amount of the invoice issued by the seller and the fee for the payment, which is requested from the settlement service used by the buyer, even if the requested amount is not transferred within a predetermined period of time.

[0125] The information processing system 100 also includes a receiving unit 104 that receives application information for making payments on behalf of invoices issued by the seller through bank transfers from the buyer, a processing unit 106 that makes payments on behalf of the invoices issued by the seller based on the application information, and a creation unit 108 that creates a list of amounts to be invoiced to the buyer based on the payment on behalf of the invoices issued by the seller.By configuring in this way, the information processing system 100 can create a list of amounts to be invoiced to the buyer based on the payment on behalf of the invoices issued by the seller, and notify the buyer. In the information processing system 100, the creation unit 108 creates information indicating the total amount to be invoiced to the buyer and information indicating the remaining amount to be invoiced. By configuring in this way, the information processing system 100 can notify the buyer of the total amount to be invoiced to the buyer and the remaining amount to be invoiced. In the information processing system 100, the creation unit 108 creates a list including pending transfers, which indicate invoices for which payment from the buyer has not been completed. By configuring in this way, the information processing system 100 can notify the buyer of invoices for which payment from the buyer has not been completed. In the information processing system 100, the creation unit 108 creates a list including a transfer completion indicating invoices for which payment from the buyer has been completed. By configuring in this way, the information processing system 100 can notify the buyer of invoices for which payment from the buyer has been completed. In the information processing system 100, the creation unit 108 creates a list including separate invoices indicating invoices for which payment from the buyer is not required. By configuring in this way, the information processing system 100 can notify the buyer of invoices for which payment from the buyer is not required. The separate claim is a bond-assigned claim in the information processing system 100. By configuring in this way, the information processing system 100 can notify the buyer of the bond-assigned claim. In the information processing system 100, the creation unit 108 creates invoices in a different color for which payment by the buyer has not been completed even if the payment due date has passed. By configuring in this way, the information processing system 100 can notify the buyer of invoices in a different color for which payment by the buyer has not been completed even if the payment due date has passed.

[0126] The above describes in detail the embodiments and modified examples of the present invention with reference to the drawings. However, the specific configuration is not limited to this embodiment, and also includes design changes and the like that do not deviate from the gist of the present invention. For example, a computer program for implementing the functions of each of the above-mentioned devices may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed. Note that the "computer system" referred to here may include hardware such as an OS and peripheral devices.

[0127] In addition, the term "computer-readable recording medium" refers to writable non-volatile memory such as a flexible disk, an optical magnetic disk, a ROM, or a flash memory, a portable medium such as a DVD (Digital Versatile Disc), or a storage device such as a hard disk built into a computer system. Furthermore, the term "computer-readable recording medium" includes devices that retain a program for a certain period of time, such as volatile memory (e.g., DRAM (Dynamic Random Access Memory)) within a computer system that serves as a server or client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line.

[0128] The program may be transmitted from a computer system in which the program is stored in a storage device or the like to another computer system via a transmission medium, or by a transmission wave in the transmission medium. Here, the "transmission medium" that transmits the program refers to a medium that has a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing part of the functions described above. Furthermore, the above-mentioned functions may be realized in combination with a program already recorded in the computer system, that is, a so-called differential file (differential program). [Explanation of symbols]

[0129] 1...invoice advance payment system, 10...terminal device, 12...communication unit, 14...creation unit, 15...storage unit, 16...processing unit, 18...operation unit, 19...display unit, 20-1 to 20-n...terminal devices, 22...communication unit, 24...creation unit, 25...storage unit, 26...processing unit, 28...operation unit, 29...display unit, 100...information processing system, 102...communication unit, 104...reception unit, 105...determination unit, 106...processing unit, 108...creation unit, 110...storage unit

Claims

1. An information processing system that provides a service of making payments on behalf of an invoice issued by a seller, a reception unit that receives application information for making payment of the invoice issued by the seller by bank transfer from the buyer; a processing unit that performs payment of the invoice issued by the seller based on the application information received by the receiving unit; a creation unit that creates a list of amounts to be charged to the buyer based on the payment of the invoice issued by the seller performed by the processing unit; An information processing system comprising:

2. 2. The information processing system according to claim 1, wherein said creation unit creates information indicating a total amount to be charged to said buyer, and information indicating a remaining amount to be charged.

3. 2. The information processing system according to claim 1, wherein said creating unit creates a list including pending transfers indicating invoices for which payment from said buyers has not been completed.

4. 2. The information processing system according to claim 1, wherein said creating unit creates a list including a transfer completion indicating an invoice for which payment from said buyer has been completed.

5. The information processing system according to claim 1 , wherein the creation unit creates a list including separate invoices indicating invoices for which payment from the buyer is not required.

6. The information processing system according to claim 5 , wherein the separate claim is a bond-assigned claim.

7. 4. The information processing system according to claim 3, wherein said creation section creates invoices in a different color for which payment by said buyer has not been completed even if the payment due date has passed.

8. 1. A computer-implemented information processing method, comprising: Accept application information for the buyer to pay the seller's invoices by bank transfer, making payment of the invoice issued by the seller based on the received application information; An information processing method for creating a list of amounts to be charged to the buyer based on the payment of the invoice issued by the seller.

9. On the computer, receiving application information for making payment of an invoice issued by the seller by bank transfer from the buyer; a step of making payment of the invoice issued by the seller based on the application information received in the receiving step; generating a list of amounts to be charged to the buyer based on the payment of the invoices issued by the seller; A program to execute.

Images