JP2025039178A - Information processing system, information processing method, and program - Google Patents

Abstract

[Problem] To provide an information processing system, information processing method, and program capable of performing processing to advance payment of an invoice. [Solution] The information processing system comprises a reading unit that reads an invoice, a generation unit that generates a code image showing the contents of the invoice based on the invoice read by the reading unit, a display control unit that causes the code image generated by the generation unit to be displayed on a display unit, and a processing unit that performs payment processing with the issuer of the invoice based on a payment request from a terminal device that read the code image displayed by the display control unit. [Selected Figure] Figure 9

Description

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

Bills or statements for utility bills, telephone bills, insurance premiums, school 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 bills or statements, there is known a technique for sending bills and statements together in a single package, while reducing the enormous expenses incurred by each billing company in carrying out the sending work (see, for example, Patent Document 1).

JP 2003-030569 A

According to the technology described above, a proxy delivery of invoices etc. to a specified bank account is accepted, the information accepted that should be transferred is compiled, and a consolidated billing document is created. In other words, by using the process described above, invoices issued over a given period of time are sent as a consolidated invoice, rather than as individual invoices as in the past. This technology is carried out by a company that performs proxy delivery services, which did not previously exist. However, even if this technology is used, there is still a possibility that individual invoices will arrive from companies that are not included in the scheme, and it has not been sufficient to reduce the complexity of processing individual invoices.

The object of the present invention is to provide an information processing system, information processing method, and program that can perform processing to advance payment of bills.

(1) One aspect of the present invention is an information processing system comprising a reading unit that reads an invoice, a generation unit that generates a code image indicating contents of the invoice based on the invoice read by the reading unit, a display control unit that displays the code image generated by the generation unit on a display unit, and a processing unit that performs payment processing with the issuer of the invoice based on a payment request from a terminal device that reads the code image displayed by the display control unit.
(2) One aspect of the present invention is an information processing system as described above in (1), wherein the terminal device acquires information indicating the payment date of the invoice set by a user, and if the acquired information indicating the payment date of the invoice indicates the current day, sends the payment request to the information processing system.
(3) One aspect of the present invention is an information processing system as described in (1) above, wherein the terminal device acquires information indicating the invoice payment date set by the user, and if the acquired information indicating the invoice payment date indicates that it is not the current day, creates billing data including information indicating the invoice payment date, and the information processing system further includes a creation unit that creates, based on the billing data created by the terminal device, service fee notification screen information for notifying the payment fee for advancing the payment of the invoice by paying the invoice if the information indicating the invoice payment date does not indicate that it is after the payment due date of the invoice.
(4) One aspect of the present invention is an information processing system, in which the terminal device transmits the payment request to the information processing system based on information indicating the payment date of the invoice, as described in (3) above.
(5) One aspect of the present invention is an information processing system as described in (1) above, wherein the terminal device acquires information indicating the invoice payment date set by the user, and if the acquired information indicating the invoice payment date indicates that it is not the current day, creates billing data including information indicating the invoice payment date, and the information processing system further includes a creation unit that creates, based on the billing data created by the terminal device, service fee notification screen information for notifying the payment fee for advancing the payment of the invoice by deferred payment when the information indicating the invoice payment date indicates that it is after the payment due date of the invoice.
(6) One aspect of the present invention is an information processing system, in which, in the information processing system described above in (5), the terminal device transmits the payment request to the information processing system based on the service fee notification screen information created by the information processing system.
(7) One aspect of the present invention is an information processing system in which, in the information processing system described in (5) above, the generation unit generates multiple code images indicating the contents and payment method of the invoice based on the invoice read by the reading unit, and the processing unit performs payment processing to the issuer of the invoice based on information indicating the payment method and a payment request from a terminal device that reads any of the multiple code images displayed by the display control unit.

(8) One aspect of the present invention is an information processing method executed by a computer, which causes a reading unit to read an invoice, generates a code image indicating the contents of the invoice based on the invoice read by the reading unit, displays the generated code image on a display unit, and performs a payment process with the issuer of the invoice based on a payment request from a terminal device that read the displayed code image.

(9) One aspect of the present invention is a program that causes a computer to execute the steps of: causing a reading unit to read an invoice; causing a code image indicating the contents of the invoice based on the invoice read by the reading unit; causing a display unit to display the generated code image; and causing the issuer of the invoice to perform a payment process based on a payment request from a terminal device that read the displayed code image.

The present invention has the advantage of being able to carry out processing to advance payment of bills.

FIG. 1 is a diagram for explaining an overview of a payment-on-reimbursement system according to an embodiment of the present invention. FIG. 13 is a diagram for explaining an example of a case where a payer makes an advance payment for a portion of an invoice in the advance payment system according to the present embodiment. FIG. 2 is a functional configuration diagram for explaining an example of the functional configuration of each device included in the advance payment system according to the present embodiment. 5 is a diagram showing an example of information stored in a billing information storage unit according to the embodiment; FIG. This is a diagram to explain an example of a case in which a biller in this embodiment issues an invoice from the head office and each branch office. FIG. 13 is a diagram showing an example of information stored in the billing information storage unit when a payer issues a bill from the head office and each branch office according to the present embodiment. FIG. 13 is a functional configuration diagram showing a modified example of the payment device according to the present embodiment. 4 is a functional configuration diagram showing an example of a detailed functional configuration of a payment-advancement device control unit according to the present embodiment. FIG. FIG. 2 is a functional configuration diagram showing an example of a detailed functional configuration of the advance payment device and the payer device according to the present embodiment. 10 is a flowchart showing an example of a series of processes performed by the advance payment device according to the present embodiment. FIG. 13 is a diagram showing an example of a screen configuration of a payment list screen presented by the payer device according to the embodiment. 10 is a flowchart showing an example of a series of processes performed by the advance payment device according to the present embodiment. FIG. 13 is a diagram showing an example of a display screen presented on the payer device according to the embodiment, which is displayed before an application for advance payment is made. FIG. 13 is a diagram showing an example of a display screen presented on the payer device according to the present embodiment, the screen configuration being displayed after an application for advance payment has been made. 1 is a flowchart (part 1) showing an example of a series of processes performed by the advance payment system according to the present embodiment. 11 is a flowchart (part 2) showing an example of a series of processes performed by the advance payment system according to the present embodiment. 11 is a flowchart (part 3) showing an example of a series of processes performed by the advance payment system according to the present embodiment. 13 is a flowchart (part 1) showing another example of a series of processes performed by the advance payment system according to the present embodiment. 13 is a flowchart (part 2) showing another example of a series of processes performed by the advance payment system according to the present embodiment. 11 is a flowchart (part 3) showing the flow of a series of processes performed by the advance payment system according to the present embodiment. 2 is a block diagram showing an example of an internal configuration of the payment device according to the present embodiment. FIG.

[Embodiment]
Hereinafter, the information processing system, the information processing method, and the program according to the aspects of the present invention will be described in detail with reference to the accompanying drawings, showing preferred embodiments. Note that the aspects of the present invention are not limited to these embodiments, and include various modifications or improvements. In other words, the components described below include those that a person skilled in the art can easily imagine, and those that are substantially the same, and the components described below can be appropriately combined. In addition, various omissions, substitutions, or modifications of the components can be made without departing from the gist of the present invention. In addition, in the following drawings, the scale and number of each structure may be different from the scale and number of the actual structure in order to make each structure easier to understand.

[Outline of Information Processing System]
FIG. 1 is a diagram for explaining an overview of the advance payment system according to this embodiment. The advance payment system is an example of an information processing system. First, an overview of the advance payment system 1 will be explained with reference to the diagram. The advance payment system 1 is used by a claimant C, a payer P, and an advance payer R. Of these, there are at least multiple claimants C. The diagram shows claimants C1, C2, and C3 as examples of multiple claimants C. The advance payment system 1 may also include multiple payers P. The diagram shows, as an example, a case where the advance payment system 1 includes only payer P.

Biller C issues an invoice to payer P. Multiple billers C each issue an invoice to payer P at any time and in any format. In the example shown, biller C1 issues invoice A to payer P, biller C2 issues invoice B to payer P, and biller C3 issues invoice C to payer P.

The payer P receives an invoice from the claimant C. The payer P receives invoices issued by each of the multiple claimants C. In the illustrated example, the payer P receives invoice A from the claimant C1, invoice B from the claimant C2, and invoice C from the claimant C3. The payer P decides whether or not to make an advance payment for each received invoice. Advance payment here is a method in which the payer R makes a payment to the claimant C on behalf of the payer P. The illustrated example shows an example of an advance payment being made for all received invoices (i.e., invoice A, invoice B, and invoice C). The payer P transmits information about the invoices for which advance payment is to be made to the payer R. The payer P may also transmit information about all received invoices to the payer R, together with information about which invoices are to be paid in advance.

The advance payer R obtains information about the invoices to be paid on behalf of the payer P from the payer P. In the example shown, the advance payer R obtains information about invoices A, B, and C from the payer P as information about the invoices to be paid on behalf of the payer P. The advance payer R makes payment to the biller C based on the obtained invoice information. Specifically, in the example shown, the advance payer R makes payment to the biller C1 who issued invoice A based on invoice A, makes payment to the biller C2 who issued invoice B based on invoice B, and makes payment to the biller C3 who issued invoice C based on invoice C.

The payer R issues an invoice to the payer P for the total amount of the invoices that he/she has paid on behalf of (invoice A, invoice B, and invoice C in the illustrated example). The payer P may add a fee when making the payment to the payer R. The payer P pays the payer R the total amount of the invoices that he/she has requested to be paid on behalf of (invoice A, invoice B, and invoice C in the illustrated example) and the necessary fee. By adopting such a configuration, the payer P can make a lump-sum payment to the payer R instead of paying each of the multiple claimants C. Therefore, according to this embodiment, the payer P can reduce the conventional hassle of processing each invoice separately.

Figure 2 is a diagram for explaining an example of a case where a payer makes an advance payment for some invoices in the advance payment system according to this embodiment. This figure is a modified example of the example shown in Figure 1. The example shown in Figure 2 shows an example of a case where payer P makes an advance payment for some of the invoices he has received. In the specific example shown, payer P receives invoice A from biller C1, invoice B from biller C2, and invoice C from biller C3. Of these received invoices, payer P pays invoice C to biller C3 himself, and makes an advance payment for the remaining invoices A and B.

In this case, payer P sends information about invoice A and invoice B to advance payer R. Alternatively, payer P sends information about invoice A, invoice B, and invoice C, as well as information about invoice A and invoice B to advance payer R. Advance payer R makes payment to invoice C1 who issued invoice A based on invoice A, and makes payment to invoice C2 who issued invoice B based on invoice B. Advance payer R issues an invoice to payer P for the total amount of invoices for which it has made advance payments (invoice A and invoice B in the illustrated example). Payer P pays to advance payer R the total amount of invoices for which it has requested advance payment (invoice A and invoice B in the illustrated example), as well as the necessary fees.

[Functional configuration]
Fig. 3 is a functional configuration diagram for explaining an example of the functional configuration of each device included in the advance payment system according to this embodiment. With reference to the same figure, an example of the functional configuration of each device included in the advance payment system 1 will be explained. The advance payment system 1 includes an advance payment device 10, a payer device 20, and a claimant device 30. Each functional unit included in the advance payment device 10, the payer device 20, and the claimant device 30 is realized, for example, by using an electronic circuit. Furthermore, each functional unit may include internal storage means such as a semiconductor memory or a magnetic hard disk device, as necessary. Furthermore, each function may be realized by a computer having a CPU (Central Processing Unit) and software. Furthermore, all or part of each functional unit may be realized using hardware such as an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field-Programmable Gate Array). Furthermore, all or part of each functional unit may be realized by a combination of software and hardware. All or part of the functions of the advance payment device 10, the payer device 20, and the claimant device 30 may exist on, for example, a cloud server. Furthermore, each of the advance payment device 10, the payer device 20, and the claimant device 30 may be composed of multiple devices (computers), and each functional block may be distributed across multiple devices.

The advance payment device 10 includes a billing information acquisition unit 11, a billing information storage unit 12, an advance payment device control unit 13, an output unit 14, an acquisition unit 15, and a transfer execution unit 16.

The billing information acquisition unit 11 acquires billing information BI, which is information about a bill issued by a biller C to a payer P. The billing information acquisition unit 11 acquires multiple billing information BI. The multiple billing information BI may be issued by multiple billers C respectively, or may be issued by a specific biller C. The billing information BI includes at least information identifying the biller C who issued the invoice.

Note that there may be at least two types of billing information BI acquired by the billing information acquisition unit 11. That is, the billing information acquisition unit 11 may be configured to acquire billing information BI in a plurality of modes. The plurality of modes includes, first, billing information BI provided by the biller C as electronic data as a first mode. The billing information BI as electronic data may be information obtained by performing optical character recognition (OCR) on a paper bill, for example. In addition, as a second mode, billing information BI input to the advance device 10 by the payer P operating an input device (which may be, for example, the payer device 20). Note that the modes of billing information BI may include modes other than those exemplified above.

The billing information acquisition unit 11 is thus configured to be able to acquire billing information BI in a number of different types, making it possible to handle billing from a number of billers C who issue bills in different formats. The billing information acquisition unit 11 may acquire the billing information BI directly from the biller C, or may acquire the billing information BI indirectly from the payer P after the biller C issues the bill to the payer P. Acquisition of the billing information BI may also include acquiring bills stored in a specified database. The bills stored in the specified database may be, for example, bill information stored by an existing platformer. In other words, the advance payment device 10 can also perform advance payment processing by linking with an existing platform. The billing information BI stored in a specified database in the existing platform may be arranged in a unified format, for example.

The link with the system of the other platform may be performed, for example, through an API (Application Programming Interface). Furthermore, in order to link with the system of the other platform, the payer R may provide an SDK (Software Development Kit) to the existing system of the other platform, or the SDK may be provided by OEM. As a linking method, the service according to this embodiment may be embedded in the system of the other platform that is to be a partner, or information may be linked from the system of the other platform that is to be a partner to the pay-by-payment device 10 according to this embodiment.

The acquisition of billing information BI is not limited to the above-mentioned examples, such as acquisition from a system of another platform or direct input of information into the advance payment device 10, but may be accomplished by other methods.

The billing information storage unit 12 accumulates multiple billing information BI acquired by the billing information acquisition unit 11. The billing information storage unit 12 is configured to include a hard disk drive (HDD: Hard Disk Drive), a solid state drive (SSD: Solid State Drive), a flash memory, a read only memory (ROM), etc. Note that the billing information storage unit 12 does not have to exist as a hardware configuration equipped in the advance payment device 10, and may exist in, for example, a server device connected via a network.

Now, with reference to Figures 4 to 6, we will explain an example of billing information BI stored in the billing information storage unit 12.

[Billing Information]
FIG. 4 is a diagram showing an example of information stored in the billing information storage unit according to this embodiment. With reference to the same figure, an example of billing information BI stored in the billing information storage unit 12 will be described. In the example shown in the figure, the billing information BI is associated with a "biller", a "payer", a "billing amount", a "scheduled payment date", a "status", and "advance payment selection information". Identification information of the bill (document) may be associated with the billing information BI. The "biller" is information specifying the biller C who issued the billing information BI. The "payer" is information specifying the payer P to whom the billing information BI is issued. The "billing amount" is information indicating the billing amount of the billing information BI. The "scheduled payment date" is information indicating the scheduled payment date of the billing information BI to the biller C. The "status" is information indicating the status of the billing information BI. The "advance payment selection information" is information indicating whether or not the billing information BI has been selected as an advance payment by the payer P.

Specific examples of the above-mentioned "status" may include the following:
Unpaid: No payment has been made to claimant C, and no selection has been made as to whether or not to make an advance payment.
· Applied: The payer P has selected advance payment, and the advance payer R is determining whether or not to allow advance payment.
Waiting for on-the-spot payment: This is the state in which the payer P selects on-the-spot payment, and the advance payer R determines that on-the-spot payment is possible, and then waits for the advance payment to be made.
Advance payment completed: This is the state after the payer P selects advance payment, the advance payer R determines that advance payment is possible, and the advance payment is then executed.
Unpaid (waiting for transfer): This is the state in which the payer P is waiting for the remittance from the payer R to the payer R after the payer R has made an advance payment.
Paid (transfer completed): This is the state after the payer R has made an advance payment and the payer P has further transferred the payment to the payer R.

In addition, the above-mentioned "status" may include an error-related status. An error-related status may include a case where processing is interrupted for some reason, or where the information in the billing information BI is incomplete. The above-mentioned "status" may also include a pattern in which insurance/guarantee has been fulfilled. The above-mentioned "status" may also include a wide range of statuses regarding the processing status of other billing information BI.

Specifically, in the illustrated example, billing information BI1 shows a case where the "biller" is A Shoji, the "payer" is A Co., Ltd., the "billing amount" is ¥50,000, the "scheduled payment date" is 4/28/2023, the "status" is "unpaid," and the "advance payment selection information" is "○." Also, billing information BI2 shows a case where the "biller" is B Shoji, the "payer" is B Co., Ltd., the "billing amount" is ¥20,000, the "scheduled payment date" is 4/30/2023, the "status" is "unpaid," and the "advance payment selection information" is "-." Additionally, billing information BI3 shows that the "biller" is C Shoji, the "payer" is C Co., Ltd., the "billing amount" is 30,000 yen, the "scheduled payment date" is 4/30/2023, the "status" is unpaid, and the "advance payment selection information" is -.

Figure 5 is a diagram for explaining an example of a case where a biller according to this embodiment issues an invoice from the head office and each branch office. Here, depending on the biller C, there may be multiple issuers even though they are the same biller C. As an example, the figure shows an example of a case where biller C issues an invoice from the head office and each branch office. That is, the figure shows a case where an invoice is issued from multiple roles. Specifically, as the biller C, there is a head office C1 and multiple branches C2. As the multiple branches C2, there are branches C2-1, C2-2, and C2-3. In such a situation, an invoice may be issued from each issuer. In the example shown, invoice A1 is issued from the head office C1, invoice A21 is issued from the branch office C2-1, invoice A22 is issued from the branch office C2-2, and invoice A23 is issued from the branch office C2-3. In such a case, an identification number may be assigned to each role, and the invoice information BI may include the identification number, making it possible to identify each role.

Figure 6 is a diagram showing an example of information stored in the billing information storage unit when a payer in this embodiment issues invoices from the head office and each branch office. The example shown in the figure shows an example of billing information BI, similar to Figure 4. The example shown in Figure 6 differs from the example shown in Figure 4 in that while all billers C are A Shoji, they are distinguished as the head office, the XX branch office, or the △△ branch office. In this way, biller information may be structured in a hierarchical structure, with each one identifiable.

[Functional configuration]
Returning to FIG. 3, the functional configuration of the payment advance device 10 will be described further.

The advance device control unit 13 selects the billing information BI for an invoice issued to a specific payer from among the multiple billing information BI acquired by the billing information acquisition unit 11 and stored in the billing information storage unit 12. This process may be triggered by, for example, an execution instruction from the payer device 20. When the advance device control unit 13 acquires an execution instruction from the payer device 20, it selects the billing information BI associated with the payer P corresponding to the payer device 20 from among the multiple billing information BI stored in the billing information storage unit 12. The advance device control unit 13 outputs the selected billing information BI to the payer device 20 via the output unit 14. In the following description, the advance device control unit 13 may be simply referred to as the control unit.

The output unit 14 outputs the billing information BI selected by the advance device control unit 13 to the payer device 20. The billing information BI selected by the advance device control unit 13 is the billing information BI associated with a specific payer P. The output unit 14 outputs information to the payer device 20 corresponding to the specific payer P. Note that the billing information BI for a specific payer P may be referred to as specific billing information SBI.

The acquisition unit 15 acquires information indicating whether or not to make an advance payment from the payer device 20 in accordance with the specific billing information SBI output by the output unit 14. Whether or not to make an advance payment is included in the advance payment information RPI, for example. The advance payment information RPI may include information on the payment method after the advance payment. In other words, when an advance payment is selected, the acquisition unit 15 may further acquire information on the payment method after the advance payment. In addition, it is preferable that the acquisition unit 15 acquires information on the payment method after the advance payment for each biller C. The acquisition unit 15 outputs the acquired advance payment information RPI to the advance payment device control unit 13.

It is preferable that the information on the payment method after advance payment acquired by the acquisition unit 15 includes at least either payment by credit card or payment by bank transfer. In addition, the information on the payment method after advance payment acquired by the acquisition unit 15 may broadly include payment agency, Business Payments Solution Provider (BPSP), a format specified by the Japan Bankers Association for transfers via Internet banking, external transfer, etc. Examples of external transfers include transfers at a bank counter and transfers using an automated teller machine (ATM).

The advance payment device control unit 13 acquires the advance payment information RPI from the acquisition unit 15, and updates the billing information BI stored in the billing information storage unit 12 according to the acquired advance payment information RPI. In other words, the advance payment device control unit 13 updates the billing information BI, which corresponds to information on whether or not an advance payment will be made.

The transfer execution unit 16 executes a transfer process for the claimant C based on the billing information BI stored in the billing information storage unit 12 and indicating that an advance payment is to be made. Whether or not a case is subject to transfer processing is determined, for example, by the advance device control unit 13 referring to the billing information storage unit 12. The advance device control unit 13 outputs a control signal CI to the transfer execution unit 16, and the transfer execution unit 16 executes transfer processing (makes payment to the transfer destination account) for the case subject to transfer processing indicated by the control signal CI. The transfer execution unit 16 executes transfer processing for the claimant who issued the invoice. As a result of executing the transfer processing, the transfer execution unit 16 outputs transfer information TI to the claimant device 30 indicating that the transfer processing has been executed.

Next, the functional configuration of the payer device 20 will be described. The payer device 20 is a terminal device operated by the payer P. The payer device 20 acquires information from the payer P as to whether or not to make an advance payment based on information from the advance device 10. The payer device 20 outputs the information acquired from the payer P as to whether or not to make an advance payment to the advance device 10. The payer device 20 comprises a payer device control unit 21, a presentation unit 22, and an operation reception unit 23.

The payer device control unit 21 acquires specific billing information SBI indicating billing information BI to be paid by the payer P from the advance payment device 10. The payer device control unit 21 presents the billing information BI to be paid by the payer P to the payer P. The payer device control unit 21 outputs the information to be presented by the presentation unit 22 as presentation information DI.

The presentation unit 22 presents the billing information BI output from the advance payment device 10 to the payer P. The presentation unit 22 may include a display unit (not shown) capable of visually displaying the billing information BI to the payer P. The display unit may be, for example, a liquid crystal display, an organic electroluminescence (EL) display, etc.

The operation reception unit 23 accepts operations from the payer P. The operation reception unit 23 accepts operations from the payer P via an input device such as a keyboard, touch panel, or microphone (not shown). The payer P selects whether or not to make an advance payment for each invoice based on the information displayed on the presentation unit 22. The operation reception unit 23 accepts the operation by the payer to select whether or not to make an advance payment according to the presented billing information BI. The payer device control unit 21 outputs advance payment information RPI, including information on whether or not to make an advance payment, to the advance payment device 10 based on the operation accepted by the operation reception unit 23.

Next, the functional configuration of the claimant device 30 will be described. The claimant device 30 obtains transfer information TI indicating that a transfer has been made from the advance device 10. The claimant device 30 may also have other functions such as issuing claim information BI to the payer device 20.

Note that some advance payers R may not be registered as agents for electronic payments, etc. In such cases, the advance payer device 10 may be configured to perform the transfer operation with the intervention of an operator OP. Below, an example of a modified advance payer device 10 configured to perform the transfer operation with the intervention of an operator OP will be described with reference to the drawings.

[An example of a case where an operator is involved in a transfer process]
7 is a functional configuration diagram showing a modified example of the advance payment device according to this embodiment. With reference to the same figure, an example of the functional configuration of the advance payment device 10A, which is a modified example of the advance payment device 10, will be described. The advance payment device 10A differs from the advance payment device 10 in that it further comprises an application instruction output unit 17 and a transfer data file import unit 18. In the description of the advance payment device 10A, the same components as those in the advance payment device 10 are given the same reference numerals and description thereof may be omitted. In addition, in the description of the advance payment device 10A, description of the same components as those in the advance payment device 10 may be omitted.

The application instruction output unit 17 outputs billing information BI indicating that an advance payment is to be made to the operator. The billing information BI output by the application instruction output unit 17 may be information searched for in the billing information storage unit 12 by the advance payment device control unit 13 and passed to the application instruction output unit 17, for example.

The operator OP creates a transfer data file that describes the transfer execution information based on the information output from the application instruction output unit 17. The transfer data file may be created in a specified format that can be recognized by the advance payment device 10A, or in a specified format specified by a specified Internet banking service.

The transfer data file import unit 18 imports a transfer data file based on instructions from the operator OP. When importing a transfer data file, the transfer data file import unit 18 may refer to the information output by the application instruction output unit 17 and determine whether there are any omissions in the confirmation results by the operator OP.

The transfer execution unit 16 executes the transfer process based on the transfer data file imported by the transfer data file import unit 18. For example, the transfer execution unit 16 may import the transfer data file imported by the transfer data file import unit 18 into Internet banking and execute the transfer process by general transfer or transfer.

[Payment Status Update]
Here, it is preferable that the billing information BI stored in the billing information storage unit 12 is associated with information on the payment status. The information on the payment status is information on the payment status of the bill when the payer P selects advance payment. The information on the payment status includes at least the status of unpaid (unpaid). The information on the payment status may also include a wide range of other statuses such as those described with reference to FIG. 4. The information on the payment status may be acquired from the payer device 20 by, for example, the acquisition unit 15 shown in FIG. 3.

The information on the payment status may be updated manually by the payer P, or automatically by the advance payment device 10. When the payer P processes the transfer at a bank counter or at an automated teller machine (ATM), it is preferable for the payer P to manually update the payment information. In this case, the acquisition unit 15 acquires information on the payment status for the billing information BI from the payer device 20 based on the operation of the payer P who is presented with the billing information BI and selects whether or not to make an advance payment.

When the information on the payment status can be manually changed by the payer P, the payer device 20 may present it to the payer P in a manner that allows the payer P to recognize that it is changeable. Specifically, the payer device 20 acquires the billing information BI associated with the information on the payment status from the advance device 10, and presents it to the payer P based on the acquired information. Depending on the information on the payment status, the payer device 20 may present it in different manners depending on whether the status is changeable by the payer P or not. For example, when the status is changeable by the payer P (for example, in the case of an external transfer), the payer device 20 may display it by changing (activating) the status display color. Furthermore, the payer device 20 may notify the payer P of the status change method during onboarding.

In the case of a status such as payment agency or advance payment, the advance device 10 may automatically update information regarding the payment. In the case of a status that is automatically updated in this way, for example, the payer device 20 may indicate the status by changing the status display color (deactivating it).

The following describes a case where the advance payment device 10 automatically updates information related to a payment. An example of a case where the advance payment device 10 automatically updates information related to a payment is when it performs a payment agent or advance payment. When the advance payment device 10 automatically updates information related to a payment, it automatically clears the data based on information acquired by batch processing or transfer completion data obtained by detecting a deposit.

Figure 8 is a functional configuration diagram showing an example of the detailed functional configuration of the advance payment device control unit according to this embodiment. With reference to the figure, an example of the detailed functional configuration of the advance payment device control unit 13 in the case where payment-related information is automatically updated by the advance payment device 10 will be described. The advance payment device control unit 13 comprises a virtual account allocation unit 131, a deposit detection unit 132, a payment status acquisition unit 133, a payment status reconciliation unit 134, and a notification information creation unit 135.

The virtual account allocation unit 131 refers to the billing information BI acquired by the billing information acquisition unit 11 and stored in the billing information storage unit 12, and assigns a different virtual account to each payer. By assigning a different virtual account to each payer, the virtual account allocation unit 131 identifies the payer P who made the deposit when a deposit is made from payer P. The virtual account allocation unit 131 outputs information identifying payer P and information on the virtual account corresponding to that payer P to the payment status reconciliation unit 134 as virtual account information VAI.

The deposit detection unit 132 detects that a deposit has been made from the payer P to the virtual account. The deposit detection unit 132 outputs information regarding the deposit as deposit information PI to the payment status reconciliation unit 134. The deposit information PI may include, for example, information identifying the payer P who made the deposit, the amount of the deposit, information identifying the billing information BI, etc.

When a payment is made manually by the payer P, the payment status acquisition unit 133 acquires information indicating that the payment has been made from the payer device 20. The payment status acquisition unit 133 outputs information indicating that a payment has been made manually by the payer P to the payment status reconciliation unit 134 as payment status information PSI. The payment status information PSI may include, for example, information identifying the payer P who made the deposit, and information identifying the payment amount, the payment method, and the billing information BI.

The payment status reconciliation unit 134 acquires virtual account information VAI from the virtual account allocation unit 131, acquires deposit information PI from the deposit detection unit 132, and acquires payment status information PSI from the payment status acquisition unit 133. Based on this acquired information, the payment status reconciliation unit 134 updates the billing information BI stored in the billing information storage unit 12. The billing information BI is updated by outputting update information UPI to the billing information storage unit 12. More specifically, the payment status reconciliation unit 134 changes information related to the payment status to "paid" based on, for example, information on deposits to the virtual account. Changing information related to the payment status to "paid" can also be said to be the erasure of debt data.

The notification information creation unit 135 creates service fee information for notifying the payer P of the fee for the advance payment. For example, when an advance payment of the invoice of the payer P to the claimant C is made and the status of the billing information BI is changed from "advance payment made" to "unpaid (waiting for transfer)", the notification information creation unit 135 creates service fee information for notifying the payer P of the fee for the advance payment. When the status of the billing information BI is changed from "unpaid" to "paid", the notification information creation unit 135 updates the service fee information. The notification information creation unit 135 may also create the service fee information before an advance payment of the invoice of the payer P is made to the claimant C.
When the status of the billing information BI is "unpaid," the notification information creation unit 135 issues a warning (alarm) in accordance with the payment due date. The notification information creation unit 135 issues a warning to the payer P in accordance with the period until the payment due date, based on information on the payment status of the billing information BI stored in the billing information storage unit 12. The notification information creation unit 135 issues a warning to the payer P, for example, when the period until the payment due date is within three days. The warning may be issued, for example, by presenting information to the payer P via the presentation unit 22 provided in the payer device 20.

The payer P may also make the payment using a payment app installed in the payer device 20. A case where a payment is made using a payment app will be described. The payment app is pre-installed in the payer device 20. The payment app causes the payer device 20 to make any of immediate payment, invoice payment, and invoice deferred payment to the advance device 10, according to an operation by the payer P.
9 is a functional configuration diagram showing an example of a detailed functional configuration of the advance payment device and the payer device according to this embodiment. With reference to the same figure, an example of a detailed functional configuration of the advance payment device 10 and the payer device 20 in a case where the payer device 20 makes a payment using a payment app will be described. The advance payment device 10 further comprises a reading unit 111 and a display unit 112, and the advance payment device control unit 13 further comprises a generating unit 136, a display control unit 137, and a determining unit 138. The payer device 20 further comprises a reading unit 24.
In the advance payment device 10, the reading unit 111 reads an invoice. The reading unit 111 may be configured to include an OCR function. The generating unit 136 generates identification information of the invoice corresponding to the invoice read by the reading unit 111, assigns the generated identification information of the invoice to the invoice, and stores it in the invoice information storage unit 12 as the invoice information BI. The generating unit 136 also generates code image information indicating the location of the invoice and the URL (Uniform Resource Locator) of the advance payment site provided by the advance payment device 10 based on the invoice to which the identification information of the invoice is assigned. Examples of the code image are a QR (Quick Response) code and a barcode. The display control unit 137 acquires the code image information from the generating unit 136, and displays the code image on the display unit 112 based on the acquired code image information.

In the payer device 20, the operation reception unit 23 receives an operation by the payer P to start the payment app, and the payer device control unit 21 starts the payment app based on the operation received by the operation reception unit 23. The payer device control unit 21 operates the payment app to cause the reading unit 24 to read the code image displayed by the advance payment device 10, and executes a process to access the URL of the advance payment site provided by the advance payment device 10 based on the read code image.

The payer device control unit 21 obtains setting image information for setting the payment date from the advance payment device 10 by accessing the URL of the advance payment site, and displays the setting screen based on the obtained setting screen information. The payer P refers to the setting screen and inputs the payment date. The payer device control unit 21 obtains information indicating the payment date input by the payer P, and determines whether the payment date set by the payer P is today based on the obtained information indicating the payment date.
If the payer device control unit 21 determines that the payment date is today, it performs an immediate payment process to the payment application in response to an operation by the payer P. The payer device control unit 21 creates a payment request including the identification information of the invoice, and transmits the created payment request to the advance device 10. The transfer execution unit 16 obtains from the invoice information storage unit 12 an invoice that corresponds to the identification information of the invoice included in the payment request from the payer device 20, and performs a payment process to the issuer of the invoice based on the obtained invoice.

If the payer device control unit 21 determines that the payment date is not today, it creates billing data including bill (document) identification information and information indicating the payment date, and transmits the created billing data to the advance payment device 10. The billing data may also include the contents of the invoice.
The determination unit 138 retrieves an invoice corresponding to the invoice identification information from the invoice information storage unit 12 based on the invoice identification information and information indicating the payment date included in the invoice data from the payer device 20, and determines whether the information indicating the payment date included in the retrieved invoice is after the payment due date of the invoice. If the determination unit 138 determines that the information indicating the payment date is not after the payment due date of the invoice, the notification information creation unit 135 creates service fee notification screen information for notifying the payment due in advance when the invoice is paid in advance by the invoice payment, and transmits the created service fee notification screen information to the payer terminal 20.
The payer device control unit 21 displays a service fee notification screen based on the service fee notification screen information from the advance payment device 10. The payer device control unit 21 performs payment processing to the payment application based on information indicating the payment date of the invoice. The payer device control unit 21 creates a payment request including invoice (statement) identification information, and transmits the created payment request to the advance payment device 10. The transfer execution unit 16 retrieves an invoice corresponding to the invoice (statement) identification information included in the payment request from the payer device 20 from the invoice information storage unit 12, and performs payment processing to the issuer of the invoice based on the retrieved invoice.

When the determination unit 138 determines that the information indicating the payment date is after the payment deadline of the invoice, the notification information creation unit 135 creates service fee notification screen information to notify the payment fee for the advance payment when the invoice is paid in advance through deferred invoice payment, and transmits the created service fee notification screen information to the payer device 20.
The payer device control unit 21 displays the service fee notification screen based on the service fee notification screen information from the advance payment device 10. The payer device control unit 21 immediately performs payment processing to the settlement application. The payer device control unit 21 creates a payment request including invoice identification information, and transmits the created payment request to the advance payment device 10. The transfer execution unit 16 obtains an invoice corresponding to the invoice identification information included in the payment request from the payer device 20 from the invoice information storage unit 12, and performs payment processing to the issuer of the invoice based on the obtained invoice.

[An example of a series of processes performed by the advance payment device]
Next, an example of a series of processes performed by the advance payment device 10 and the payer device 20 according to this embodiment will be described with reference to Fig. 10 to Fig. 15C. In describing this example of the processes, an example of the screen configuration of the processing screen will also be described with reference to the drawings.

Figure 10 is a flowchart showing an example of a series of processes performed by the advance payment device according to this embodiment. First, an example of the processes performed by the advance payment device 10 will be described with reference to the same figure.

(Step S11) First, the billing information acquisition unit 11 acquires billing data BI. The billing data BI may be acquired from another existing platform, or may be directly input by the payer P.

(Step S12) The acquired billing data BI is stored in the billing information storage unit 12. The advance payment system 1 according to this embodiment is capable of linking with various other existing platforms. The billing information storage unit 12 may store a mixture of billing information BI acquired from multiple platforms and billing information BI directly input by the payer P. It is preferable that the format of the billing information BI stored in the billing information storage unit 12 be unified to a predetermined format. In order to unify the format, it is preferable that the advance payment system 1 according to this embodiment link through an API or provide an SDK to other existing platform providers and payers P.

(Step S13) Next, the advance payment device control unit 13 extracts the billing information BI for a specific payer P from the billing information BI stored in the billing information storage unit 12. The output unit 14 outputs the extracted information to the payer device 20 corresponding to the specific payer P. The payer device 20 presents a list of invoices for which the payer P is the payment target.

Figure 11 is a diagram showing an example of the screen configuration of a payment list screen presented by the payer device according to this embodiment. With reference to the figure, an example of the screen configuration of the payment list screen D10 will be described. The payment list screen D10 has a screen configuration of tabs D111 and D112. Tab D111 is a tab for displaying the unpaid list. Tab D112 is a tab for displaying the payment history. Tabs D111 and D112 are mutually exclusive. In the example shown, tab D111 is selected, and therefore the unpaid list is displayed.

Symbol D12 shows the unpaid amount. The unpaid amount is presented, for example, including fees. In the example shown, the unpaid amount is "103,000 yen." It is preferable that the amount of fees included in the unpaid amount is presented so that it can be easily seen. In the example shown, the fees are "3,000 yen."

The symbol D13 displays a list of unpaid items. The unpaid list displays billing information BI that is unpaid (i.e., payment from payer P to biller C or advance payer R has not been completed). The billing information BI is associated with "client name", "billing amount", "scheduled payment date", "status", and "advance payment option". Of these, "client name", "billing amount", and "scheduled payment date" are items that are determined at the time the billing information acquisition unit 11 acquires the billing information BI. "Status" and "advance payment option" are items that can be changed by payer P or advance payment device 10.

When the "Status" button is active, the payer P can change the status. For example, the payer P changes the status to "paid" after making a deposit to the biller C at a payment bank counter or ATM. When the "Status" button is inactive, the payer P cannot change the status. The "Status" button becomes inactive, for example, in cases of payment agency or advance payment. In these cases, the status is changed by the biller device 30, and therefore the payer P cannot change the status.

The payer P can select advance payment for each billing information BI. Each billing information BI is provided with a check box for selecting whether or not to make an advance payment, and the payer P can select each one independently. In the example shown, none of the check boxes are checked (i.e., advance payment is not selected). A bulk selection check box D14 may also be provided. By selecting the bulk selection check box D14, the payer P can select advance payment for all billing information BI, reducing the effort of selecting each one one by one. In the example shown, the bulk selection check box D14 is not checked (i.e., advance payment is not selected all at once).

In the illustrated example, billing information BI11, billing information BI12, and billing information BI13 are displayed as unpaid billing information BI. Specifically, the "client name" of billing information BI11 is A Shoji, the "billing amount" is 50,000 yen, the "scheduled payment date" is April 28, 2023, the "status" is "unpaid," and "advance payment selection" is not selected. Additionally, the "client name" of billing information BI12 is B Shoji, the "billing amount" is 20,000 yen, the "scheduled payment date" is April 30, 2023, the "status" is "unpaid," and "advance payment selection" is not selected. In addition, the "customer name" in billing information BI13 is C Shoji, the "billing amount" is 30,000 yen, the "scheduled payment date" is April 30, 2023, the "status" is unpaid, and "advance payment option" is not selected.

Returning to FIG. 10, we will continue to explain an example of a series of processes performed by the advance payment device 10 according to this embodiment.

(Step S14) When the payer device 20 presents the billing information BI and advance payment is selected (i.e., step S14; YES), the advance device 10 proceeds to step S15. On the other hand, when advance payment is not selected (i.e., step S14; NO), the advance device 10 proceeds to step S16.

(Step S15) If advance payment is selected, the advance payment device 10 performs advance payment processing for the billing information BI for which advance payment has been selected. The detailed flow of the advance payment processing will be described later with reference to FIG. 12.

(Step S16) If advance payment is not selected, the payer P performs the payment process by a payment agent, a transfer via internet banking, an ATM, or other method. As a result of making a payment by these methods, the payer P changes the status to "paid."

Figure 12 is a flow chart showing an example of a series of processes performed by the advance payment device according to this embodiment. The detailed flow of the advance payment process will be described with reference to this figure. The series of processes shown in this figure are the details of the process of step S15 described with reference to Figure 10.

(Step S21) First, the advance payment device 10 acquires the payment method from the payer P for each billing information BI. Here, the selection of the payment method may be performed individually for each billing information BI, or may be performed collectively for multiple billing information BI.

(Step S22) If the request is made in bulk (i.e., step S22; YES), the process proceeds to step S24. If the request is made individually (i.e., step S22; NO), the process proceeds to step S23.

(Step S23) If an individual request is made, a request is made for each payment statement.

(Step S24) An advance payment application is made for billing information BI for which advance payment was selected in the selection of payment method in step S21. In the advance payment application, the method of payment to the advance payer R resulting from the advance payment is specified. Examples of the method of payment to the advance payer R include invoice payment and credit card payment. An example of the screen configuration of the display screen presented on the payer device 20 before the advance payment application is made and an example of the screen configuration of the display screen presented on the payer device 20 after the advance payment application is made will be described with reference to the drawings.

Figure 13 is a display screen presented on the payer device according to this embodiment, showing an example of the screen configuration displayed before an advance payment application is made. With reference to the figure, an example of the screen configuration of the advance payment application screen D20 will be described. The advance payment application screen D20 has the symbols D21 to D26 as screen components.

Reference symbol D21 is an advance payment method selection button. In the figure, reference symbols D211 and D212 are shown as examples of advance payment method selection buttons. When reference symbol D211 is selected, payer P makes payment to advance payer R by invoice payment (bank transfer). When reference symbol D212 is selected, payer P makes payment to advance payer R by credit card payment. Either of the advance payment method selection buttons may be selected exclusively. Note that buttons showing other payment method options may also be provided as advance payment method selection buttons.

Reference symbol D22 is a display showing the number of invoices that are the subject of the advance payment application. In the example shown, one invoice is the subject of the advance payment application. The advance payment device 10 according to this embodiment can advance pay multiple invoices collectively. When multiple invoices are advanced payed collectively, reference symbol D22 shows the number of invoices that have been combined. By making an advance payment for multiple invoices collectively and selecting invoice payment by payer P, payer P can combine multiple invoices into one invoice, reducing the cumbersome work of dealing with multiple invoices.

Reference symbol D23 is a display section that displays the deadline (payment due date) when payment to the advance payer R will be made as a result of the advance payment. In the illustrated example, the payment due date is set to May 31, 2023. Reference symbol D24 is a display section that displays the total amount of one or more invoices that are the subject of the advance payment application. If one invoice is selected, the total payment amount is the amount claimed for that invoice, and if multiple invoices are selected, the total payment amount is the total amount of the selected multiple invoices. In the illustrated example, 20,600 yen is displayed as the total payment amount. Note that reference symbol D24 may also explicitly display the fee, which is part of the total payment amount. In the illustrated example, the fee is 600 yen.

Reference symbol D25 is a button for displaying the terms of use for advance payment. Payer P can refer to the terms of use for advance payment by operating this button. Reference symbol D26 is a button for applying for advance payment. If there are no errors in the content displayed on the advance payment application screen D20, payer P can apply for an advance payment by operating reference symbol D26.

Figure 14 shows an example of the screen configuration of the display screen presented on the payer device according to this embodiment, which is displayed after an advance payment application has been made. With reference to the figure, an example of the screen configuration of the advance payment application completion screen D30 will be described. As shown in the figure, the advance payment application completion screen D30 displays content that explicitly indicates that the advance payment application has been completed.

The advance payment application completion screen D30 may also show the future flow of the process. The future flow of the process is as follows: (1) The advance payer R sends an email to the payer P on the same day to inform them of the acceptance of the application. (2) The advance payer R then conducts an internal review, and informs the payer P of the results of the internal review on the following business day. (3) If the internal review determines that the advance payment is possible, the advance payer R transfers the payment to the biller C by the payment due date. (4) At the beginning of the following month, the advance payer R sends an invoice to the payer P. At the same time as sending the invoice, the payer P is informed of the payment due date.

Returning to FIG. 12, we will continue to explain the detailed flow of the advance payment process performed by the advance payment device 10 according to this embodiment.

(Step S25) When an application for advance payment is made, the advance payment device control unit 13 checks the transfer history information (transfer execution data) TRI stored in the transfer history storage unit 121.

(Step S26) If it is determined that the transfer is possible (advance payment is possible) as a result of checking the transfer performance information (transfer execution data) TRI (i.e., step S26; YES), processing proceeds to step S28. On the other hand, if it is determined that the transfer is not possible (advance payment is not possible) (i.e., step S26; NO), processing proceeds to step S27.

(Step S27) If it is determined that the advance payment is not possible, the advance payment device 10 outputs information indicating that the advance payment is not possible to the payer device 20, and notifies the payer P that the advance payment is not possible.

(Step S28) If it is determined that the advance payment is possible, the advance payment device 10 executes a transfer process for the claimant C, which is indicated in the billing information BI that is the subject of the advance payment. The advance payment device 10 may execute the transfer process on the payment due date indicated in the billing information BI that is the subject of the advance payment. By configuring the advance payment device 10 to execute the transfer process on the payment due date, it becomes possible to cancel the application for advance payment up until the payment due date.

15A is a flowchart (part 1) showing an example of a series of processes performed by the advance payment system according to the present embodiment. With reference to the same figure, a case where the payer device 20 makes a payment using a payment app will be described. It is assumed that the payment app is running on the payer device 20.
(Step S31) The reading unit 111 reads the invoice presented by the payer P.
(Step S32) The generation unit 136 generates bill (statement) identification information corresponding to the invoice read by the reading unit 111, assigns the generated bill (statement) identification information to the invoice, and stores it as billing information BI in the billing information storage unit 12. The generation unit 136 also generates code image information indicating the invoice and the location of the advance payment site based on the invoice to which the bill (statement) identification information has been assigned.
(Step S33) The display control unit 137 acquires the code image information from the generation unit 136, and causes the display unit 112 to display the code image.

(Step S34) The payer device control unit 21 causes the reading unit 24 to read the code image.
(Step S35) The payer device control unit 21 executes a process of accessing the advance payment site based on the code image read by the reading unit 24.
(Step S36) The payer device control unit 21 obtains setting image information for setting the payment date, displays the setting screen based on the obtained setting screen information, and obtains information indicating the payment date input by the payer P.

(Step S37) The payer device control unit 21 determines whether the payment date set by the payer P is today.
(Step S38) If the payment date is today, the payer device control unit 21 performs real-time payment processing to the payment application in response to an operation by the payer P.
(Step S39) The payer device control unit 21 creates a payment request.
(Step S40) The payer device control unit 21 transmits the created payment request to the advance payment device 10.
(Step S41) The transfer execution unit 16 performs a payment process to the issuer of the invoice based on a payment request from the payer device 20.

15B is a flowchart (part 2) showing an example of a series of processes performed by the on-behalf-payment system according to the present embodiment. With reference to the same figure, the case where the payer device 20 makes a payment using the payment application will be further described.
(Step S42) If the payment date is not today in step S37, the payer device control unit 21 creates billing data including bill identification information and information indicating the payment date.
(Step S43) The payer device control section 21 transmits the billing data to the advance payment device 10.
(Step S44) The determination unit 138 determines whether the information indicating the payment date included in the billing data is after the payment deadline of the billing statement, based on the information indicating the payment date included in the billing data.

(Step S45) If the determination unit 138 determines that the information indicating the payment date is not after the invoice payment deadline, the notification information creation unit 135 creates service fee notification screen information to notify the fee for advance payment when an invoice is paid in advance through invoice payment.
(Step S46) The notification information generating unit 135 transmits the service fee notification screen information to the payer terminal 20.
(Step S47) The payer device control unit 21 causes the presentation unit 22 to display a service fee notification screen.
(Step S48) The payer device control unit 21 stores the billing data and the service fee notification screen information.
(Step S49) The payer device control unit 21 determines whether the invoice payment date has arrived. If the invoice payment date has not arrived, the process returns to step S49.

(Step S50) When the payment date of the invoice arrives, the payer device control unit 21 performs a payment process to the payment application.
(Step S51) The payer device control unit 21 creates a payment request.
(Step S52) The payer device control unit 21 transmits the created payment request to the advance payment device 10.
(Step S53) The transfer execution unit 16 performs a payment process to the issuer of the invoice based on the payment request from the payer device 20.

15C is a flowchart (part 3) showing an example of a series of processes performed by the on-behalf-payment system according to the present embodiment. With reference to the same figure, the case where the payer device 20 makes a payment using the payment application will be further described.
(Step S54) If the determination unit 138 determines in step S44 that the information indicating the payment date is after the payment deadline of the invoice, the notification information creation unit 135 creates service fee notification screen information to notify the fee for the advance payment when the invoice is paid in advance under the invoice deferred payment system.
(Step S55) The notification information generating unit 135 transmits the service fee notification screen information to the payer terminal 20.
(Step S56) The payer device control unit 21 causes the presentation unit 22 to display a service fee notification screen.

(Step S57) The payer device control unit 21 stores the billing data and the service fee notification screen information.
(Step S58) The payer device control unit 21 performs a payment process to the payment application.
(Step S59) The payer device control unit 21 creates a payment request.
(Step S60) The payer device control unit 21 transmits the created payment request to the advance payment device 10.
(Step S61) The transfer execution unit 16 performs a payment process to the issuer of the invoice based on a payment request from the payer device 20.

When the payer device 20 makes a payment using a payment app, the generation unit 136 of the advance payment device 10 may generate code image information indicating the contents of the invoice and the payment method, based on the invoice read by the reading unit 111.
Specifically, the generating unit 136 creates code image information corresponding to each of a plurality of payment methods. Here, the plurality of payment methods include same-day payment, invoice payment, and invoice deferred payment. Below, the description will be continued on the case where the generating unit 136 generates three types of code image information, namely, code image information corresponding to same-day payment, code image information corresponding to invoice payment, and code image information corresponding to invoice deferred payment. However, the generating unit 136 may generate one or two types of code image information, or may generate four or more types of code image information. The display control unit acquires the code image information from the generating unit 136, and causes the display unit 112 to display a code image based on the acquired code image information.

16A is a flowchart (part 1) showing another example of a series of processes performed by the advance payment system according to the present embodiment. With reference to the same figure, a case will be described in which the payer device 20 makes a payment using a payment method selected by the payer P using a payment app. It is assumed that the payment app is running on the payer device 20.
(Step S61) The reading unit 111 reads the invoice presented by the payer P.
(Step S62) The generating unit 136 generates three types of code image information indicating the contents and payment method of the invoice based on the invoice read by the reading unit 111.
(Step S63) The display control unit 137 acquires the three types of code image information from the generation unit 136, and causes the display unit 112 to display the three types of code images.

(Step S64) The payer device control unit 21, based on the operation of the payer P, causes the reading unit 24 to read a desired code image from the three types of code images.
(Step S65) The payer device control unit 21 executes a process of accessing the advance payment site provided by the advance payment device 10 based on the code image read by the reading unit 24.
(Step S66) The payer device control unit 21 acquires setting image information for setting the payment date, displays the setting screen based on the acquired setting screen information, and acquires information indicating the payment date input by the payer P.

(Step S67) The payer device control unit 21 determines whether or not a code image corresponding to same-day payment has been read.
(Step S68) When the payer device control unit 21 has read the code image corresponding to same-day payment, the payer device control unit 21 performs a payment process to the payment application according to an operation by the payer P.
(Step S69) The payer device control unit 21 creates a payment request.
(Step S70) The payer device control unit 21 transmits the created payment request to the advance payment device 10.
(Step S71) The transfer execution unit 16 performs a payment process to the issuer of the invoice based on a payment request from the payer device 20.

16B is a flowchart (part 2) showing another example of a series of processes performed by the on-behalf system according to the present embodiment. With reference to the same figure, the case where the payer device 20 makes a payment using the payment application will be further described.
(Step S72) If the payer device control unit 21 has not read a code image corresponding to same-day payment in step S67, it creates billing data including the contents of the bill, information indicating the payment method, and information indicating the payment date.
(Step S73) The payer device control section 21 transmits the billing data to the advance payment device 10.
(Step S74) The determination unit 138 determines whether the information indicating the payment method indicates bill payment, based on the information indicating the payment method included in the billing data.

(Step S75) If the determination unit 138 determines that it is a bill payment, the notification information creation unit 135 creates service fee notification screen information to notify the payment fee for the advance payment when the bill payment is made in advance.
Steps S76 to S83 are similar to steps S46 to S53 in FIG. 15B, and therefore description thereof will be omitted.

16C is a flowchart (part 3) showing the flow of a series of processes performed by the on-behalf-payment system according to this embodiment. With reference to this figure, the case where the payer device 20 makes a payment using the payment application will be further described.
(Step S84) If the determination unit 138 determines in step S74 that the information indicating the payment method is not invoice payment, the notification information creation unit 135 creates service fee notification screen information to notify the fee for the advance payment when the invoice is paid in advance by invoice deferred payment.
Steps S85 to S91 are similar to steps S55 to S61 in FIG. 15C, and therefore description thereof will be omitted.

Fig. 17 is a block diagram showing an example of the internal configuration of the advance payment device 10 according to this embodiment. At least some of the functions of the advance payment device 10 can be realized using a computer. As shown in the figure, the computer is configured to include a central processing unit 901, a RAM 902, an input/output port 903, input/output devices 904 and 905, etc., and a bus 906. The computer itself can be realized using existing technology. The central processing unit 901 executes instructions included in a program read from the RAM 902, etc. The central processing unit 901 writes data to the RAM 902, reads data from the RAM 902, and performs arithmetic and logical operations according to each instruction. The RAM 902 stores data and programs. Each element included in the RAM 902 has an address and can be accessed using the address. Note that RAM is an abbreviation for "random access memory." The input/output port 903 is a port through which the central processing unit 901 exchanges data with external input/output devices, etc. The input/output devices 904 and 905 are input/output devices. The input/output devices 904 and 905 exchange data with the central processing unit 901 via the input/output port 903. The bus 906 is a common communication path used inside the computer. For example, the central processing unit 901 reads and writes data in the RAM 902 via the bus 906. Also, for example, the central processing unit 901 accesses the input/output port via the bus 906. Also, all or part of each functional unit provided in the advance payment device 10 may be realized using hardware such as an ASIC, PLD, or FPGA. Also, all or part of each functional unit may be realized by a combination of software and hardware.

The payer device 20 and the claimant device 30 may have an internal configuration as shown in FIG. 17, similar to the claimant device 30.

The information processing system of this embodiment includes a reading unit 111 that reads an invoice, a generation unit 136 that generates a code image showing the contents of the invoice based on the invoice read by the reading unit 111, a display control unit 137 that causes the display unit 112 to display the code image generated by the generation unit 136, and a transfer execution unit 16 as a processing unit that performs payment processing with the issuer of the invoice based on a payment request from a payer device 20 as a terminal device that read the code image displayed by the display control unit 137. With this configuration, the payer P can have the information processing system perform payment processing with the issuer of the invoice by having the payer device 20 read the code image showing the contents of the invoice, making the operation easier than when inputting the contents of the invoice.

In the information processing system, the terminal device acquires information indicating the invoice payment date set by the user, and if the acquired information indicating the invoice payment date indicates the current day, it transmits a payment request to the information processing system. By configuring in this way, if the information indicating the invoice payment date indicates the current day, the terminal device can transmit a payment request to the information processing system, so that the information processing system can make an immediate payment to the issuer of the invoice based on the payment request from the terminal device.

In the information processing system, the terminal device acquires information indicating the invoice payment date set by the user, and if the acquired information indicating the invoice payment date indicates that it is not the current day, creates billing data including the information indicating the invoice payment date, and the information processing system further includes a creation unit that creates, based on the billing data created by the terminal device, service fee notification screen information for notifying the user of the fee for advance payment when the invoice payment is advanced by invoice payment if the information indicating the invoice payment date does not indicate that it is after the invoice payment due date, based on the billing data created by the terminal device. By configuring in this way, if the information indicating the invoice payment date does not indicate that it is after the invoice payment due date, that is, if the information indicating the invoice payment date is before the invoice payment due date, service fee notification screen information for notifying the user of the fee for advance payment can be created and notified to the user.

In the information processing system, the terminal device transmits a payment request to the information processing system based on information indicating the invoice payment date. By configuring it in this way, it is possible to advance payment of the invoice by invoice payment on the invoice payment date.

In the information processing system, the terminal device acquires information indicating the invoice payment date set by the user, and if the acquired information indicating the invoice payment date indicates that it is not the current day, creates billing data including information indicating the invoice payment date, and the information processing system further includes a creation unit that creates, based on the billing data created by the terminal device, service fee notification screen information for notifying the user of the fee for advance payment when the invoice is paid in advance through deferred payment when the information indicating the invoice payment date indicates that it is after the invoice payment due date. By configuring in this way, service fee notification screen information for notifying the user of the fee for advance payment when the invoice is paid in advance through deferred payment when the information indicating the invoice payment date indicates that it is after the invoice payment due date can be created and notified to the user.

In the information processing system, the terminal device transmits a payment request to the information processing system based on the service fee notification screen information created by the information processing system. By configuring it in this way, if the information indicating the payment date of the invoice indicates that it is after the invoice payment due date, the invoice can be immediately paid in advance by deferred invoice payment.

In the information processing system, the generation unit 136 generates one or more code images indicating the contents and payment method of the invoice based on the invoice read by the reading unit 111, and the processing unit performs payment processing with the issuer of the invoice based on the information indicating the payment method and the payment request from the terminal device that reads one or more code images displayed by the display control unit 137. By configuring in this way, the information processing system can advance payment of the invoice using the payment method desired by the user.

The entire or part of the functions of each unit of the advance payment device 10 in the above-described embodiment may be realized by recording a program for realizing these functions on a computer-readable recording medium, and reading and executing the program recorded on the recording medium into a computer system. Note that the term "computer system" here includes hardware such as the OS and peripheral devices.

Furthermore, "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, as well as storage units such as hard disks built into computer systems. Furthermore, "computer-readable recording medium" may also include devices that dynamically store programs for a short period of time, such as communication lines when transmitting programs via networks such as the Internet or communication lines such as telephone lines, and devices that store programs for a certain period of time, such as volatile memory within a computer system that serves as a server or client in such cases. Furthermore, the above-mentioned programs may be ones that realize some of the functions described above, or may be ones that can realize the functions described above in combination with programs already recorded in the computer system.

Although the embodiment of the present invention has been described above, the present invention is not limited to the above embodiment, and various modifications can be made without departing from the spirit of the present invention.

1...Advance payment system, C...Billant, P...Payer, R...Advance payment, 10...Advance payment device, 11...Billing information acquisition unit, 12...Billing information storage unit, 13...Advance payment device control unit, 14...Output unit, 15...Acquisition unit, 16...Transfer execution unit, 111...Reading unit, 112...Display unit, 20...Payer device, 21...Payer device control unit, 22...Presentation unit, 23...Operation reception unit, 24...Reading unit, 30...Billant device, BI...Billing information, UPI...Update information, TI...Transfer information, 17...Application instruction output unit, 18...Transfer data file import unit, 131...Virtual account allocation unit, 132...Deposit detection unit, 133...Payment status acquisition unit, 134...Payment status clearing unit, 135...Notification information creation unit, 136...Generation unit, 137...Display control unit, 138...Determination unit

Claims (9)

A reading unit that reads an invoice;
a generating unit that generates a code image indicating the contents of the invoice based on the invoice read by the reading unit;
a display control unit that causes the code image generated by the generation unit to be displayed on a display unit;
a processing unit that performs a payment process to an issuer of the invoice based on a payment request from a terminal device that reads the code image displayed by the display control unit. The information processing system according to claim 1, wherein the terminal device acquires information indicating the payment date of the invoice set by the user, and if the acquired information indicating the payment date of the invoice indicates the current day, transmits the payment request to the information processing system. the terminal device acquires information indicating the payment date of the invoice set by the user, and if the acquired information indicating the payment date of the invoice indicates that the payment date is not the current day, creates invoice data including the information indicating the payment date of the invoice;
The information processing system includes:
2. The information processing system according to claim 1, further comprising a creation unit that creates service fee notification screen information for notifying a fee for an advance payment of an invoice when the information indicating the payment date of the invoice does not indicate a date after the payment due date of the invoice based on the billing data created by the terminal device and the invoice is paid in advance by paying the invoice. The information processing system according to claim 3, wherein the terminal device transmits the payment request to the information processing system based on information indicating the payment date of the invoice. the terminal device acquires information indicating the payment date of the invoice set by the user, and if the acquired information indicating the payment date of the invoice indicates that the payment date is not the current day, creates invoice data including the information indicating the payment date of the invoice;
The information processing system includes:
2. The information processing system of claim 1, further comprising a creation unit that creates service fee notification screen information for notifying a fee for advance payment when the invoice is paid in advance by deferred payment based on the billing data created by the terminal device if information indicating the payment date of the invoice indicates a date that is after the payment due date of the invoice. The information processing system according to claim 3, wherein the terminal device transmits the payment request to the information processing system based on the service fee notification screen information created by the information processing system. the generating unit generates a plurality of code images indicating the contents and payment method of the invoice based on the invoice read by the reading unit;
The information processing system according to claim 1 , wherein the processing unit performs a payment process with the issuer of the invoice based on information indicating a payment method and a payment request from a terminal device that reads any one of the multiple code images displayed by the display control unit. 1. A computer-implemented information processing method, comprising:
The invoice is read by the reader,
generating a code image showing the contents of the invoice based on the invoice read by the reading unit;
Displaying the generated code image on a display unit;
An information processing method for performing a payment process to the issuer of the invoice based on a payment request from a terminal device that reads the displayed code image. On the computer,
A step of having a reading unit read the bill;
generating a code image showing the contents of the invoice based on the invoice read by the reading unit;
A step of displaying the generated code image on a display unit;
and a step of having the issuer of the invoice carry out payment processing based on a payment request from a terminal device that reads the displayed code image.

Images