Bill supporting apparatus, bill supporting system, bill supporting method, and bill supporting program

Abstract

To provide a bill supporting apparatus for enabling a provider of goods and services to easily bill a user and receive payment through another payment method without changing a payment method that the provider himself / herself can accept.SOLUTION: A bill supporting apparatus 300 accepts registration of information on a provider who provides goods or services and first payment means information on first payment means by which the provider can accept payment of a bill, and acquires bill information on the content of the bill. The bill supporting apparatus 300 generates and outputs a settlement page for receiving input from a user of second payment means information on second payment means to be used to pay the bill and access information for the user to access the settlement page. The bill supporting apparatus 300 performs settlement processing using the second payment means to make a bill to the user and performs payment processing using the first payment means to make a payment to the provider.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to a billing support device, a billing support system, a billing support method, and a billing support program. [Background technology]

[0002] The method of issuing invoices to users is commonly known as a method for providers of goods or services to bill users for the price of the goods or services they provide. In particular, in transactions between businesses known as BtoB transactions, the amount of the transactions is relatively large and they are often conducted without meeting face-to-face, so it is common for the price to be requested and paid using invoices.

[0003] An invoice contains details about the invoice, such as the biller, billing item, and billing amount, as well as details about payment, such as the payment deadline and the transfer bank account. Based on the details on the invoice, the user takes action to transfer the invoice amount to the transfer bank account by the payment deadline. Technology has also been proposed for efficiently processing such invoices (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 5927304 Summary of the Invention [Problem to be solved by the invention]

[0005] The payment deadline for such invoices is generally set several weeks or more in the future, such as the last day of the month following the month in which the invoice date falls, taking into consideration the burden of the user's payment operation and cash flow. Therefore, the provider must wait for payment until the payment deadline after providing the product or service, which often causes problems in terms of cash flow. In order to solve such problems, it is possible to accept payments by methods other than transfer to a bank account, such as by using credit card payments. However, in order to do so, the provider must deal with contracts with credit card companies as credit affiliates, the construction and operation of a credit payment system, and the construction and operation of a system to operate in parallel with existing invoices, which creates a problem of a high burden on the provider.

[0006] The present invention has been made in consideration of the above circumstances, and aims to provide a billing support device, billing support system, billing support method, and billing support program that enable providers of goods and services to easily bill users and receive payment using other payment methods without having to change the payment methods that the providers can accept. [Means for solving the problem]

[0007] The billing support device has a provider information receiving unit, a provider payment means receiving unit, a billing information acquisition unit, a payment page generating unit, an access information generating unit, an output unit, a payment processing unit, and a payment processing unit. The provider information receiving unit receives registration of provider information related to a provider providing a product or service. The provider payment means receiving unit receives registration of first payment means information related to a first payment means capable of accepting payment of a bill generated for a user by the provider providing the product or service to the user. The billing information acquiring unit acquires billing information related to the content of the bill. The payment page generating unit outputs the billing information acquired by the billing information acquiring unit so that the user can view it, and generates a payment page for accepting input of second payment means information related to a second payment means different from the first payment means used to pay the bill from the user. The access information generating unit generates access information for the user to access the payment page generated by the payment page generating unit. The output unit outputs the access information generated by the access information generating unit. The payment processing unit executes a payment process for the amount corresponding to the claim by the second payment means based on the second payment means information input on the payment page from the user who accessed the payment page using the access information, and charges the user the amount corresponding to the claim via the second payment means. The payment processing unit executes a payment process to pay the amount corresponding to the claim to the provider using the first payment means indicated by the first payment means information.

[0008] The billing support system includes the billing support device, a provider terminal used by the provider, and a user terminal used by the user.

[0009] The billing support method includes a provider information receiving step, a provider payment means receiving step, a billing information acquisition step, a payment page generating step, an access information generating step, an output step, a payment processing step, and a payment processing step. The provider information receiving step receives registration of provider information related to a provider providing a product or service. The provider payment means receiving step receives registration of first payment means information related to a first payment means capable of accepting payment of a bill generated for a user by the provider providing the product or service to the user. The billing information acquiring step acquires billing information related to the contents of the bill. The payment page generating step outputs the billing information acquired in the billing information acquiring step so that the user can view it, and generates a payment page for accepting input of second payment means information related to a second payment means different from the first payment means used to pay the bill from the user. The access information generating step generates access information for the user to access the payment page generated in the payment page generating step. The output step outputs the access information generated in the access information generating step. The payment processing step executes a payment process for the amount corresponding to the claim by the second payment means based on the second payment means information inputted and accepted on the payment page from the user who accessed the payment page using the access information, and charges the amount corresponding to the claim from the user via the second payment means. The payment processing step executes a payment process for paying the amount corresponding to the claim to the provider using the first payment means indicated by the first payment means information.

[0010] The billing support program is configured to cause the information processing device to function as the billing support device. Effect of the Invention

[0011] The billing support device accepts registration of provider information related to a provider of a product or service. The billing support device accepts registration of first payment means information related to a first payment means that can accept payment of a bill generated for a user by the provider providing the product or service to the user. The billing support device acquires billing information related to the content of the bill, outputs the billing information so that the user can view it, and generates a payment page for accepting input of second payment means information related to a second payment means to be used for payment of the bill from the user. The billing support device generates access information for the user to access the generated payment page, and outputs the generated access information. The billing support device executes a payment process for an amount corresponding to the bill by the second payment means based on the second payment means information input on the payment page from the user who accessed the payment page using the access information, and bills the user for the amount corresponding to the bill via the second payment means. The billing support device executes a payment process for paying the amount corresponding to the bill to the provider using the first payment means indicated by the first payment means information.

[0012] This allows a provider of goods or services to easily make bills to users that can be paid by other payment methods without changing the payment methods that the provider can accept, and to receive payment by a payment method that the provider can accept. For example, even if the provider itself is not a credit card affiliate or comprehensive affiliate and cannot accept payments by credit card, but can only receive payments by transfer to a bank account, the provider can make bills to users that can be paid by credit card. By inputting the necessary information on the payment page, the user can perform payment processing using a credit card, and can enjoy various benefits of credit card payment. The provider can receive payment by transfer to a bank account that the provider can accept, through processing by the payment processing unit. [Brief description of the drawings]

[0013] [Figure 1] 1 is a diagram showing a schematic configuration of a billing support system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing a schematic configuration of a provider terminal. [Diagram 3] FIG. 2 is a block diagram showing a schematic configuration of a user terminal. [Figure 4] 1 is a block diagram showing a schematic configuration of an information processing device; [Diagram 5] 1 is a block diagram showing a schematic configuration of a financial institution system. [Figure 6] FIG. 1 is a block diagram showing a schematic configuration of a payment system. [Figure 7] 2 is a block diagram showing a schematic configuration of a control unit of the information processing device. FIG. [Figure 8] 1 is a sequence chart showing a procedure of a process executed by the billing support system. [Figure 9] FIG. 9 is a diagram showing an example of a provider information registration screen (new registration screen) that is output by the information processing device and displayed on the provider terminal in the process of step S101 in FIG. [Figure 10] FIG. 9 is a diagram showing an example of a provider information registration screen (transaction content selection screen) output by an information processing device and displayed on a provider terminal in the process of step S101 in FIG. [Figure 11] 9 is a diagram showing an example of a provider information registration screen (business information input screen) that is output by the information processing device and displayed on the provider terminal in the process of step S101 in FIG. 8. FIG. [Figure 12] 9 is a diagram showing an example of a provider information registration screen (account information input screen) that is output by the information processing device and displayed on the provider terminal in the process of step S101 in FIG. 8. FIG. [Figure 13] FIG. 9 is a diagram showing an example of a provider information registration screen (registered information confirmation screen) that is output by the information processing device and displayed on the provider terminal in the process of step S101 in FIG. [Figure 14]9 is a diagram showing an example of a screen output by an information processing device and displayed on a provider terminal when the process of step S102 in FIG. 8 is executed. FIG. [Figure 15] 9 is a diagram showing an example of a billing information input screen that is output by an information processing device and displayed on a provider terminal when the processes in steps S105 and S106 in FIG. 8 are executed. FIG. [Figure 16] 9 is a diagram showing an example of a billing information confirmation screen that is output by the information processing device and displayed on the provider terminal when the processes in steps S105 and S106 in FIG. 8 are executed. FIG. [Figure 17] 9 is a diagram showing an example of an access information output screen that is output by the information processing device and displayed on the provider terminal when the process of step S111 in FIG. 8 is executed. FIG. [Figure 18] 9 is a diagram showing an example of a payment page screen output by the information processing device in the process of step S108 in FIG. 8 and displayed on the user terminal when the process of step S114 in FIG. 8 is executed. FIG. [Figure 19] 9 is a diagram showing an example of a payment information confirmation screen that is output by the information processing device and displayed on the user terminal when the processes of steps S115 and S116 in FIG. 8 are executed. FIG. [Figure 20] 9 is a diagram showing an example of a payment result confirmation screen that is output by the information processing device and displayed on the user terminal when the process of step S121 in FIG. 8 is executed. FIG. [Figure 21] 13 is a diagram showing an example of a screen displaying a list of billing states of a plurality of billing information items, which is output by an information processing device and displayed on a provider terminal. FIG. [Figure 22] 13 is a diagram showing an example of a detailed display screen of each billing information item output by an information processing device and displayed on a provider terminal. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment of the present invention will be described with reference to the attached drawings. In the description of the drawings, the same elements are given the same reference numerals, and duplicated description will be omitted. In addition, the dimensional ratios of the drawings may be exaggerated for the convenience of explanation and may differ from the actual ratios.

[0015] <Configuration of billing support system> First, a billing support system according to an embodiment of the present invention will be described.

[0016] FIG. 1 is a diagram showing a schematic configuration of a billing support system according to an embodiment of the present invention.

[0017] As shown in FIG. 1, the billing support system 1 includes a provider terminal 100, a user terminal 200, an information processing device 300, a financial institution system 400, and a payment system 500. The provider terminal 100, the user terminal 200, and the information processing device 300 are connected to each other via a network such as the Internet so that they can communicate with each other. The financial institution system 400 and the payment system 500 are connected to the information processing device 300 via a dedicated network or the like so that they can communicate with each other. The provider terminal 100 is configured to be connectable to a financial institution system 400 such as a bank where the provider has an account. The user terminal 200 is configured to be connectable to a payment system 500 such as a credit card company with which the user has a contract for a credit card or the like. Note that the connection between each component is not limited to the above example, and each component may be connected to each other by any method.

[0018] Each component will be described in detail below.

[0019] <Provider Terminal 100> The provider terminal 100 is an information terminal such as a PC, a smartphone, or a tablet PC that is used by a provider who provides a product or service.

[0020] FIG. 2 is a block diagram showing a schematic configuration of a provider terminal.

[0021] 2, the provider terminal 100 has a CPU (Central Processing Unit) 110, a ROM (Read Only Memory) 120, a RAM (Random Access Memory) 130, a storage 140, a communication interface 150, and an operation display unit 160. Each component is connected to each other via a bus 170 so as to be able to communicate with each other.

[0022] The CPU 110 controls the above components and performs various arithmetic processing in accordance with programs recorded in the ROM 120 and the storage 140 .

[0023] The ROM 120 stores various programs and various data.

[0024] The RAM 130 serves as a working area for temporarily storing programs and data.

[0025] The storage 140 stores various programs including an operating system and various data. For example, applications are installed in the storage 140 for transmitting and receiving various information to and from the information processing device 300 via a network, displaying various information provided by the information processing device 300, and acquiring various information input by a provider.

[0026] The communication interface 150 is an interface for communicating with an external device such as the information processing device 300, and uses various wired or wireless communication standards such as Wi-Fi (registered trademark), 3G, 4G, and 5G for mobile phone communication, etc. The communication interface 150 uses a standard for short-range wireless communication such as Bluetooth (registered trademark), and communication may be performed via a nearby PC or the like.

[0027] The operation display unit 160 is, for example, a touch panel display, which displays various information and accepts various inputs from the provider.

[0028] <User terminal 200> The user terminal 200 is an information terminal such as a PC, a smartphone, or a tablet PC that is used by a user who uses a product or service provided by a provider.

[0029] FIG. 3 is a block diagram showing a schematic configuration of a user terminal.

[0030] 3, the user terminal 200 has a CPU 210, a ROM 220, a RAM 230, a storage 240, a communication interface 250, and an operation display unit 260. Each component is communicably connected to each other via a bus 270. Note that the CPU 210, the ROM 220, the RAM 230, the storage 240, the communication interface 250, and the operation display unit 260 have the same functions as the corresponding components of the provider terminal 100, and therefore duplicated explanations will be omitted.

[0031] The storage 240 stores various programs including an operating system and various data. For example, applications are installed in the storage 240 for transmitting and receiving various information to and from the information processing device 300 via a network, displaying various information provided by the information processing device 300, and acquiring various information input by a user.

[0032] <Information processing device 300> The information processing device 300 is, for example, a computer such as a server, and in this embodiment, functions as a billing support device. The information processing device 300 provides a billing support function that enables a provider of goods or services to easily bill users and receive payment by other payment methods without changing the payment methods that the provider can accept. The information processing device 300 is provided by a business providing the above-mentioned billing support service. Moreover, the information processing device 300 may be provided by one business and used by another business, or may be used jointly by multiple business operators.

[0033] FIG. 4 is a block diagram showing a schematic configuration of the information processing device.

[0034] 4, the information processing device 300 has a CPU 310, a ROM 320, a RAM 330, a storage 340, a communication interface 350, and an operation display unit 360. Each component is connected to each other so as to be able to communicate with each other via a bus 370. Note that the CPU 310, the ROM 320, the RAM 330, the storage 340, the communication interface 350, and the operation display unit 360 have the same functions as the corresponding components of the provider terminal 100, and therefore duplicated explanations will be omitted.

[0035] The storage 340 stores programs for making the CPU 310 function as a provider information receiving unit, a provider payment means receiving unit, a billing information acquiring unit, a payment page generating unit, an access information generating unit, an output unit, a payment processing unit, a payment processing unit, an invoice image acquiring unit, an image generating unit, a transmitting unit, a confirming unit, a specifying unit, a list display unit, a provider determining unit, a judging unit, a calculating unit, an instruction accepting unit, and an approved payment means accepting unit. The storage 340 also stores various information required for executing the processes by each of the above units. When the information processing device 300 is used by multiple businesses, a setting table for each business may be prepared so that various settings can be made different for each business. The functions of the information processing device 300 will be described in detail later.

[0036] <Financial institution system 400> The financial institution system 400 is a system installed in a financial institution such as a bank. The financial institution system 400 provides a first payment means for accepting payment of a claim generated by a provider to a user. The first payment means is, for example, a transfer to a bank account. The first payment means is not limited to a transfer to a bank account, but includes various methods for transferring funds between accounts at a financial institution.

[0037] FIG. 5 is a block diagram showing a schematic configuration of a financial institution system.

[0038] 5, the financial institution system 400 has a CPU 410, a ROM 420, a RAM 430, a storage 440, a communication interface 450, and an operation display unit 460. Each component is connected to each other so as to be able to communicate with each other via a bus 470. Note that the CPU 410, the ROM 420, the RAM 430, the storage 440, the communication interface 450, and the operation display unit 460 have the same functions as the corresponding components of the provider terminal 100, and therefore duplicated explanations will be omitted.

[0039] The storage 440 stores various programs including an operating system and various data. For example, applications for transmitting and receiving various information to and from the information processing device 300 via a network and for providing a first payment method are installed in the storage 440.

[0040] <Payment System 500> The payment system 500 is a system provided in an institution that provides various payment methods, such as a credit card company. The payment system 500 provides a second payment method for a user to pay a bill from a provider. The second payment method is, for example, a transfer to a bank account. The second payment method is, for example, a postpaid payment method including a credit card payment. Note that the second payment method is not limited to credit card payment and postpaid payment methods, but includes various payment methods such as various code payments using one-dimensional barcodes or two-dimensional barcodes, electronic money payment, debit card payment, ID payment in which identification information such as a credit card or electronic money is associated with various identification information (ID) including biometric information for identifying a user, bank transfer (transfer agency), and instant credit type on-the-fly transfer.

[0041] FIG. 6 is a block diagram showing a schematic configuration of the payment system.

[0042] 6, the payment system 500 has a CPU 510, a ROM 520, a RAM 530, a storage 540, a communication interface 550, and an operation display unit 560. Each component is communicably connected to each other via a bus 570. Note that the CPU 510, the ROM 520, the RAM 530, the storage 540, the communication interface 550, and the operation display unit 560 have the same functions as the corresponding components of the provider terminal 100, and therefore duplicated explanations will be omitted.

[0043] Storage 540 stores various programs including an operating system and various data. For example, applications for transmitting and receiving various information to and from information processing device 300 via a network and for providing a second payment method are installed in storage 540.

[0044] <Functional configuration of information processing device 300> FIG. 7 is a block diagram showing a schematic configuration of a control unit of the information processing device.

[0045] As shown in Figure 7, the information processing device 300 functions as a provider information receiving unit 3101, a provider payment means receiving unit 3102, a billing information acquisition unit 3103, a payment page generation unit 3104, an access information generation unit 3105, an output unit 3106, a payment processing unit 3107, a payment processing unit 3108, an invoice image acquisition unit 3109, an image generation unit 3110, a transmission unit 3111, a confirmation unit 3112, an identification unit 3113, a list display unit 3114, a provider determination unit 3115, a judgment unit 3116, a calculation unit 3117, an instruction receiving unit 3118, and a permitted payment means receiving unit 3119 by the CPU 310 reading a program stored in storage 340 and executing processing.

[0046] The provider information receiving unit 3101 receives registration of provider information related to a provider that provides a product or service. The provider information may include information related to the name, location, and contact information of the provider, as well as information related to the content of the product or service provided by the provider.

[0047] The provider payment method accepting unit 3102 accepts registration of first payment method information related to a first payment method that can accept payment of a bill generated by a provider to a user when the provider provides the user with a product or service. The first payment method can be a transfer to a bank account.

[0048] The billing information acquisition unit 3103 acquires billing information related to the contents of the bill as described above. The billing information may include information on the user who is the bill recipient and information on the billing amount. The billing information may also include information on the billing date and the payment deadline. The billing information may also include provider information related to the provider who is the source of the billing.

[0049] The payment page generation unit 3104 outputs the billing information acquired by the billing information acquisition unit 3103 so that the user can view it. The payment page generation unit 3104 also generates a payment page for accepting input of second payment means information relating to a second payment means different from the first payment means used to pay the bill from the user. The second payment means may be a postpaid payment means including credit card payment.

[0050] The access information generating unit 3105 generates access information for a user to access the payment page generated by the payment page generating unit 3104. The access information is various link information or address information for accessing the payment page, such as a URL or a shortened URL.

[0051] The output unit 3106 outputs the access information generated by the access information generating unit 3105 .

[0052] The payment processing unit 3107 executes a payment process for the amount corresponding to the invoice via the second payment means based on the second payment means information input on the payment page from a user who accessed the payment page using the access information, and bills the user for the amount corresponding to the invoice via the second payment means. For example, as an affiliated store that accepts the use of the second payment means by the user, the payment processing unit 3107 bills the user for the amount corresponding to the invoice by executing a payment process for the amount corresponding to the invoice via the second payment means.

[0053] The payment processing unit 3108 executes a payment process to pay the amount corresponding to the claim to the provider, using the first payment method indicated by the first payment method information.

[0054] The invoice image acquisition unit 3109 may acquire invoice image information indicating an image of an invoice corresponding to the billing information. In this case, the payment page generation unit 3104 may output the image of the invoice indicated by the invoice image information on the payment page so that the image can be viewed by the user.

[0055] The image generating unit 3110 may generate invoice image information based on the invoice information. In this case, the invoice image acquiring unit 3109 may acquire the invoice image information generated by the image generating unit 3110.

[0056] The sending unit 3111 may send the billing information to a bill creator who creates a bill. In this case, the bill image acquiring unit 3109 may acquire bill image information generated by the bill creator.

[0057] The confirmation unit 3112 confirms the implementation status of the settlement processing in the settlement processing unit 3107 and the payment processing in the payment processing unit 3108 for each of the multiple billing information acquired by the billing information acquisition unit 3103.

[0058] The identifying unit 3113 identifies the state of processing for each of the multiple pieces of billing information based on the implementation status confirmed by the confirming unit 3112 .

[0059] The list display unit 3114 displays information indicating the state of processing related to each piece of billing information identified by the identification unit 3113 in a list form in association with each of the multiple pieces of billing information.

[0060] The provider determination unit 3115 determines whether or not the claim by the provider can be processed based on the provider information. If the provider determination unit 3115 determines that the claim by the provider cannot be processed, the claim information acquisition unit 3103 does not acquire the claim information.

[0061] The judgment unit 3116 judges whether or not the payment processing has been completed normally by the payment processing unit 3107. The payment processing unit 3108 executes the payment processing when the judgment unit 3116 judges that the payment processing has been completed normally, and does not execute the payment processing when the judgment unit 3116 judges that the payment processing has not been completed normally.

[0062] The calculation unit 3117 calculates the amount of the fee to be charged to the provider for the claim based on the billing information and the predetermined fee setting information. The predetermined fee setting information is stored in advance in the storage 340. The fee setting may be set arbitrarily, for example, as a percentage amount such as several percent of the billing amount or a fixed amount. For example, when the information processing device 300 is used jointly by a plurality of businesses, the various setting information such as the fee setting information may be stored with different contents by, for example, setting value tables being different for each business.

[0063] The instruction receiving unit 3118 receives an early payment instruction, which is an instruction from the provider to execute the payment process earlier than a predetermined schedule. In this case, the calculation unit 3117 calculates the fee amount by adding an amount calculated based on the billing information and the predetermined fee setting information to an amount calculated based on the billing information and the predetermined early payment fee setting information. The predetermined early payment fee setting information is stored in the storage 340 in advance. As the early payment fee setting, various fee conditions can be arbitrarily set according to, for example, the degree of accelerating, the billing amount, the number of times accelerating is performed, etc.

[0064] The permitted payment method accepting unit 3119 accepts registration of permitted payment method information regarding the second payment method that the user is permitted to use. In this case, the payment page generation unit 3104 outputs to the payment page the permitted payment method information whose registration has been accepted by the permitted payment method accepting unit 3119. The payment processing unit 3107 executes payment processing when the second payment method indicated by the permitted payment method information is input by the user on the payment page, and does not execute payment processing when the user inputs a payment method other than the second payment method indicated by the permitted payment method information on the payment page.

[0065] <System processing flow> FIG. 8 is a sequence chart showing the procedure of the process executed by the billing support system. The process shown in the sequence chart or the flow chart of FIG. 8 is stored as a program in the storage of each component, and is executed by the CPU controlling each unit. FIG. 9 is a diagram showing an example of a provider information registration screen (new registration screen) output by an information processing device and displayed on a provider terminal in the process of step S101 of FIG. 8. FIG. 10 is a diagram showing an example of a provider information registration screen (transaction content selection screen) output by an information processing device and displayed on a provider terminal in the process of step S101 of FIG. 8. FIG. 11 is a diagram showing an example of a provider information registration screen (business information input screen) output by an information processing device and displayed on a provider terminal in the process of step S101 of FIG. 8. FIG. 12 is a diagram showing an example of a provider information registration screen (account information input screen) output by an information processing device and displayed on a provider terminal in the process of step S101 of FIG. 8. FIG. 13 is a diagram showing an example of a provider information registration screen (registration information confirmation screen) output by an information processing device and displayed on a provider terminal in the process of step S101 of FIG. 8. FIG. 14 is a diagram showing an example of a screen output by an information processing device and displayed on a donor terminal when the process of step S102 in FIG. 8 is executed. FIG. 15 is a diagram showing an example of a billing information input screen output by an information processing device and displayed on a donor terminal when the process of steps S105 and S106 in FIG. 8 is executed. FIG. 16 is a diagram showing an example of a billing information confirmation screen output by an information processing device and displayed on a donor terminal when the process of steps S105 and S106 in FIG. 8 is executed. FIG. 17 is a diagram showing an example of an access information output screen output by an information processing device and displayed on a donor terminal when the process of step S111 in FIG. 8 is executed. FIG. 18 is a diagram showing an example of a payment page screen output by an information processing device in the process of step S108 in FIG. 8 and displayed on a user terminal when the process of step S114 in FIG. 8 is executed. FIG. 19 is a diagram showing an example of a payment information confirmation screen output by an information processing device and displayed on a user terminal when the process of steps S115 and S116 in FIG. 8 is executed.Fig. 20 is a diagram showing an example of a payment result confirmation screen output by an information processing device and displayed on a user terminal when the process of step S121 in Fig. 8 is executed. Fig. 21 is a diagram showing an example of a screen output by an information processing device and displayed on a provider terminal, displaying a list of billing statuses of multiple billing information. Fig. 22 is a diagram showing an example of a detailed display screen of each billing information output by an information processing device and displayed on a provider terminal.

[0066] As shown in FIG. 8, the provider terminal 100 acquires provider information from the provider (step S101). For example, the provider terminal 100 accesses the information processing device 300, acquires information for displaying screens as shown in FIGS. 9 to 13, displays each screen on the operation display unit 160, and accepts input of provider information from the provider. The provider information includes, for example, information on the name, location, and contact information of the provider, as well as information on the contents of the product or service provided by the provider. The provider terminal 100 also accepts registration of first payment means information related to a first payment means that can accept payment of a bill generated for a user by the provider providing the product or service to the user. The first payment means is, for example, a transfer to the provider's bank account. The first payment means information includes information such as "bank name (financial institution code)", "branch name (branch number)", "account type", "account number", and "account holder" for identifying the provider's bank account. The provider terminal 100 may also accept registration of permitted payment means information related to a second payment means that the provider permits the user to use. The permitted payment method information may be, for example, information indicating the types of payment methods (credit cards, debit cards, electronic money, code payment, ID payment, etc.) that the provider permits the user to use, or information indicating details of the provider or brand of each payment method, etc. For example, if fees charged to the provider vary depending on the type of payment method, provider, brand, etc., the provider can select the types and brands of payment methods for which the fees are acceptable.

[0067] For example, the screen in Fig. 9(A) is a screen for new registration, and accepts input of an email address from the provider. When the "New Registration" button is selected on the screen in Fig. 9(A), an email for user authentication is sent to the entered email address, and the screen in Fig. 9(B) is displayed. The provider follows the instructions on the screen in Fig. 9(B), checks the email sent, and selects the URL written in the email, and the screen in Fig. 10, which is a screen for carrying out the official registration procedure, is displayed on the operation display unit 160.

[0068] The screen in Fig. 10 is a screen for selecting transaction details. On the screen in Fig. 10, input of provider information such as the provider's business type and the details of the products and services provided by the provider is accepted. When a trader and handled products are selected on the screen in Fig. 10 and the "Next" button is selected, the screen in Fig. 11 is displayed on the operation display unit 160.

[0069] The screen in Fig. 11 is a screen for inputting information about the provider as a business operator. The screen in Fig. 11 accepts input of information about the provider, such as the provider's name (corporate name), corporate number, location, representative's name, representative's date of birth, etc. When various information is input on the screen in Fig. 11 and the "Next" button is selected, the screen in Fig. 12 is displayed on the operation display unit 160.

[0070] The screen in Fig. 12 is a screen for the provider to enter account information for accessing the information processing device 300 and using the billing support service. The screen in Fig. 12 accepts input of provider information such as the name of the person in charge, contact phone number, contact email address (also used as a login ID), password, etc. When various information is entered on the screen in Fig. 12 and agreement to the terms of use and privacy policy is confirmed, and the "Confirm input contents" button is selected, the screen in Fig. 13 is displayed on the operation display unit 160.

[0071] The screen in Fig. 13 is a screen for confirming the registration information (provider information) entered by the provider. The screen in Fig. 13 displays a list of the information entered by the provider on the screens in Figs. 9 to 12. When the "Register" button is selected on the screen in Fig. 13, the provider terminal 100 displays the screen in Fig. 14 and transmits the provider information and first payment method information acquired by input from the provider to the information processing device 300 (step S102).

[0072] Next, the information processing device 300 performs an examination of the provider (step S103). Specifically, the information processing device 300 judges whether or not the claim by the provider can be processed based on the provider information transmitted from the provider terminal 100 in the process of step S102. For example, the information processing device 300 acquires registry information based on the corporation number included in the provider information, and judges whether or not the business information included in the provided information matches the registry information. For example, if the business information does not match the registry information, the information processing device 300 judges that the claim by the provider cannot be processed. In addition, the information processing device 300 searches a predetermined article database, an antisocial forces database, or the like for the information of the representative included in the provider information, and judges whether there is a corresponding record. For example, if the information of the representative is found in a predetermined article database, or the like, the information processing device 300 judges that the claim by the provider cannot be processed. In addition, the information processing device 300 judges whether or not the business type of the provider and the contents of the products and services handled included in the provider information correspond to a high-risk business type, a prohibited product or service, or the like. For example, if the provider's business type is a high-risk business type, or if the product or service handled by the provider is a prohibited product or service, the information processing device 300 determines that the claim by the provider cannot be processed. The information processing device 300 may also search for and access the provider's homepage to confirm its existence, or confirm the existence of the provider's bank account indicated by the first payment method information. If the information processing device 300 determines that the claim by the provider cannot be processed based on the results of the above-mentioned various determinations and confirmations, it does not proceed to the subsequent steps and does not execute the process of acquiring claim information from the provider. On the other hand, if it determines that the claim by the provider can be processed, the information processing device 300 registers the provider information in the storage 340 as a user of the claim support service, and executes the subsequent processes.

[0073] When the provider provides a product or service to the user or concludes a contract to provide the product or service (step S104), the provider bills the user.

[0074] The provider terminal 100 acquires billing information related to the contents of the bill to the user from the provider (step S105). The provider terminal 100 also acquires bill image information showing an image of the bill corresponding to the billing information (step S106). For example, the provider terminal 100 accesses the information processing device 300, acquires information for displaying a screen as shown in Fig. 15, displays the screen on the operation display unit 160, and accepts input of the billing information and the bill image information from the provider.

[0075] The screen of FIG. 15 is a screen for accepting input of billing information and invoice image information from the provider. In the screen of FIG. 15, input of information on the user who is the billing destination, invoice number, billing date, payment deadline, billing amount, etc. is accepted as billing information. As billing information, provider information including more detailed information and supplementary information on the provider who is the billing source may be further accepted. In addition, in the screen of FIG. 15, input of invoice image information showing an image of an invoice corresponding to the billing information is accepted. For example, the provider can input invoice image information by dragging and dropping an image file of an invoice created by the provider into a predetermined area indicated as "invoice upload" on the screen of FIG. 15, or by selecting the "select file" button and selecting an image file. On the screen of FIG. 15, when a check is entered in a predetermined confirmation item and then the "check input contents" button is selected, the screen of FIG. 16 is displayed on the operation display unit 160.

[0076] The screen in Fig. 16 is a screen for confirming the billing information entered by the provider. The screen in Fig. 16 displays a list of the information entered by the provider on the screen in Fig. 15. When the "issue link" button is selected on the screen in Fig. 16, the provider terminal 100 transmits the billing information and invoice image information acquired by input from the provider to the information processing device 300 (step S107).

[0077] The invoice image information may be generated by the information processing device 300 based on the invoice information transmitted to the information processing device 300. In this case, the information processing device 300 acquires information necessary for creating an invoice, such as information on the invoice format, and an image of the provider's logo and seal, from the provider in advance, and stores the information in the storage 340.

[0078] The invoice image information may be generated by transmitting invoice information to a bill creator who provides a service of creating an invoice. In this case, the information processing device 300 obtains the invoice image information by receiving it from the bill creator.

[0079] Based on the billing information transmitted from the provider terminal 100, the information processing device 300 generates a payment page for the user, who is the destination of the bill, to perform payment processing (step S108). The information processing device 300 generates the payment page so that the billing information transmitted from the provider terminal 100 is output to the payment page and can be viewed. The payment page also has an input field or the like for accepting input of second payment means information related to the second payment means used by the user to pay the bill. The payment page also displays an invoice image corresponding to the billing information, or a link for displaying the invoice image, or the like.

[0080] The information processing device 300 generates and outputs access information, such as a URL for the user to access the payment page generated in the process of step S108 (step S109).

[0081] The information processing device 300 transmits the access information generated in the process of step S109 to the provider terminal 100 (step S110).

[0082] The provider terminal 100 acquires the access information transmitted from the information processing device 300 (step S111). For example, a screen as shown in FIG. 17 is displayed on the operation display unit 160 of the provider terminal 100 based on the information transmitted from the information processing device 300.

[0083] The screen in FIG. 17 displays the billing information to be charged to the user and access information for accessing the payment page where the user can pay the bill. The billing information displayed includes the name of the provider who made the bill, the invoice number, the billing date, the billing amount, the payment deadline, and other information. The access information displays a URL for accessing the payment page as an "invoice confirmation / credit card payment link," and provides guidance to the user, such as "Click this link to confirm the invoice and make a post-payment by credit card." The access information can be displayed in any format, such as a shortened URL or a two-dimensional barcode that encodes the URL, rather than in the form of a URL.

[0084] The provider terminal 100 transmits the access information transmitted from the information processing device 300 to the user terminal 200 (step S112). For example, the provider copies information such as the access information on the screen of Fig. 17 displayed on the operation display unit 160 of the provider terminal 100, pastes it into an e-mail or a message of another communication tool, and transmits it to the user terminal 200 of the user. This enables the provider to bill the user and further receive payment from the user using a second payment means such as a credit card.

[0085] In the above example, the information processing device 300 transmits the access information to the provider terminal 100, and the provider terminal 100 transmits the access information to the user terminal 200. However, the method of transmitting the access information is not limited to this. For example, the information processing device 300 may transmit the access information directly to the user terminal 200 (step S110'). In this case, the information processing device 300 acquires contact information such as an email address that can transmit information to the user terminal 200 from the provider in advance, and stores the contact information in the storage 340.

[0086] The user terminal 200 acquires the access information transmitted from the provider terminal 100 (step S113). For example, the user terminal 200 acquires the access information such as a URL by receiving an e-mail or the like transmitted from the provider terminal 100. For example, the user performs an operation to select a URL displayed in an e-mail or the like. In this case, the user terminal 200 accesses the connection destination indicated in the URL using a web browser or the like, acquires information for displaying a payment page, and displays a payment page screen as shown in FIG. 18 on the operation display unit 260 (step S114). The connection destination accessed by the user terminal 200 is a device in which information for displaying a payment page is stored, such as the information processing device 300 or another web server.

[0087] The payment page screen of FIG. 18 displays information about the provider who is the biller, and billing information such as the invoice number, billing date, billing amount, and payment deadline. The payment page screen of FIG. 18 also accepts input from the user of attribute information including information about the user's name and contact information, and second payment method information about the second payment method used by the user to pay the bill. The user's attribute information includes, for example, information about the user's business type, representative name, corporate name, contact information such as email address, etc. The second payment method information includes, for example, information about the credit card number, expiration date, CVC number, cardholder, etc. The payment page screen of FIG. 18 also displays permitted payment method information that the user is permitted to use. In the example of FIG. 18, the brand name of the credit card that is permitted to be used is displayed as the permitted payment method information. After various information is input and a check is entered in a predetermined confirmation item on the screen of FIG. 18, when the "Confirm Payment Details" button is selected, the screen of FIG. 19 is displayed on the operation display unit 260.

[0088] The screen in Fig. 19 is a screen for confirming the information entered by the user. The screen in Fig. 19 displays a list of the information entered by the user on the screen in Fig. 19. When the "Pay" button is selected on the screen in Fig. 19, the user terminal 200 acquires payment information including the second payment method information acquired by input from the user (step S115), and transmits it to the information processing device 300 (step S116).

[0089] The information processing device 300 executes a payment process using the second payment means based on the billing information and the second payment means information transmitted from the user terminal 200 (step S117), and bills the user for the amount corresponding to the bill via the second payment means. Specifically, the information processing device 300 executes the payment process using the second payment means, with the user as a user who uses the second payment means and the business providing the billing support service via the information processing device 300 as an affiliated store that accepts the use of the second payment means. For example, when the second payment means is a credit card payment, the user is a credit card holder, and the business providing the billing support service is a credit card affiliated store that has concluded an affiliated store contract with a credit card company and accepts the use of credit cards. This allows the information processing device 300 to execute a process of billing the user for the amount corresponding to the billing information via credit card payment. Note that the information processing device 300 may execute the payment process only when the second payment means indicated by the permitted payment means information is input by the user on the payment page. For example, if a payment method other than the second payment method indicated by the permitted payment method information is entered by the user on the payment page, the information processing device 300 may not execute the payment process and may ask the user to use the other second payment method.

[0090] The information processing device 300 transmits a payment processing request including the second payment method information, amount information, etc. to the payment system 500 that provides a payment service by the second payment method (step S118). The payment processing request is, for example, an authorization processing request in a credit card payment or a gathering processing request that combines an authorization processing and a sales transmission processing.

[0091] The payment system 500 judges whether or not it is possible to provide a payment service (whether or not payment can be executed) based on the payment processing request transmitted from the information processing device 300, and performs the payment processing if it is judged to be possible (step S119). The payment system 500 transmits result information indicating the result of the payment processing to the information processing device 300 (step S120).

[0092] The information processing device 300 judges whether the payment process has been completed normally based on the judgment result transmitted from the payment system 500, and transmits the judgment result to the user terminal 200 as payment result information (step S121). A screen such as that shown in FIG. 20 is displayed on the user terminal 200, and the user is notified that the payment process (processing for making a payment to a business providing a billing support service) has been completed normally. If the payment system 500 judges that the payment is not possible in the process of step S119, result information indicating an error is transmitted to the user terminal 200, and the user is notified that the payment process has not been completed normally. In this case, for example, the user terminal 200 may accept input of second payment means information of another second payment means from the user on the payment page, and execute the payment process of step S117 again.

[0093] If the payment process in step S117 is not completed normally, the information processing device 300 repeats the payment process until it is completed normally, or interrupts or ends the process.

[0094] If the settlement process in step S117 is completed normally, the information processing device 300 executes the payment process (step S122). Specifically, the information processing device 300 executes a process to pay the amount corresponding to the billing information to the provider using the first payment means indicated by the first payment means information acquired from the provider. For example, if the first payment means is a transfer to a bank account, the information processing device 300 executes a process to transfer the amount corresponding to the billing information to the provider's bank account based on the first payment means information.

[0095] The information processing device 300 transmits information for carrying out the above-mentioned transfer to the financial institution system 400 as a payment processing request (step S123).

[0096] The financial institution system 400 executes a process for transferring the amount corresponding to the billing information to the bank account of the provider based on the payment process request sent from the information processing device 300, and executes the payment process to the provider (step S124). The financial institution system 400 transmits information indicating the result of the payment process to the information processing device 300 (step S125).

[0097] The information processing device 300 transmits the information indicating the result of the payment processing transmitted from the financial institution system 400 to the provider terminal 100 (step S126).

[0098] The provider terminal 100 outputs the information indicating the result of the payment process transmitted from the information processing device 300 by displaying it on the operation display unit 160 (step S127). This allows the provider to grasp the result and status of the payment process related to the claim.

[0099] <Display list of billing processing status> The information processing device 300 checks the implementation status of the settlement process and the payment process for each of the multiple billing information transmitted from the provider terminal 100, and identifies the status of the process for each of the multiple billing information based on the confirmed implementation status. The information processing device 300 displays information indicating the status of the process for each of the identified billing information in a listable manner in association with each of the multiple billing information. For example, the information processing device 300 displays information indicating the status of the process for each of the billing information in a listable manner in association with each of the multiple billing information on a screen such as that shown in FIG. 21. For example, when the menu of "Billing History" displayed on the screen of FIG. 15 or FIG. 17 is selected on the provider terminal 100, the provider terminal 100 accesses the information processing device 300 to obtain information, and displays a screen such as that shown in FIG. 21 on the operation display unit 160.

[0100] The screen in FIG. 21 displays, in association with each billing information, information such as ID, which is identification information for each billing information, invoice number, billing destination, payment deadline, payment date or scheduled payment date, billed amount, deposit amount, and status. Status displays the processing state for each bill, identified according to the implementation status of the settlement and payment processing, such as billed, payment in progress, payment completed, payment failed, link broken, bill canceled, etc. When each billing information is selected on the screen in FIG. 21, a screen such as that shown in FIG. 22 is displayed. Detailed information on the content and status of each bill is displayed on the screen in FIG. 22.

[0101] <Calculation and billing of claims assistance processing fees> The information processing device 300 calculates the amount of the fee for the billing support processing to be charged to the provider by the business providing the billing support service for each billing based on the predetermined fee setting information for each billing information transmitted from the provider terminal 100. For example, as displayed on the screens of Figs. 15 and 16, the fee setting may be set to a percentage such as 2% of the billing amount or an amount according to the billing amount. For example, in the example of Figs. 15 and 16, when the billing amount is 10,000 yen, the fee for the billing support processing is calculated to be 200 yen. The information processing device 300 executes a payment process to pay the provider an amount obtained by subtracting the amount of the fee for the billing support processing from the amount of the executed settlement process. Therefore, in the above example, the information processing device 300 executes a settlement process of 10,000 yen, and executes a process to pay the provider 9,800 yen, which is the amount obtained by subtracting 200 yen from 10,000 yen. For example, if the fee for a payment service (such as a credit card merchant fee) relating to payment processing such as credit card payment is 1% of the payment amount, the amount paid by a billing support service provider to a payment service provider for a payment processing of 10,000 yen is 100 yen. In this case, the billing support service provider will earn a profit of 100 yen, calculated by subtracting the 100 yen fee for the payment service from the 200 yen fee income for billing support processing.

[0102] <Calculation and billing of early deposit processing fee> The information processing device 300 can receive an early payment instruction from the provider for each billing information transmitted from the provider terminal 100, which is an instruction to execute payment processing earlier than a predetermined schedule and make a payment to the provider. When the information processing device 300 receives an early payment instruction, it adds the amount of an early payment fee calculated based on the billing information and predetermined early payment fee setting information to the billing support processing fee. The early payment fee setting can be, for example, a percentage such as several percent of the billing amount, or a percentage or amount according to the degree of early payment.

[0103] The present invention is not limited to the above-described embodiment, but can be modified in various ways within the scope of the claims.

[0104] For example, in the above embodiment, an example has been described in which a fee for the billing assistance service is collected from the biller, but this is not limiting. The fee may be collected from the user, or from both the user and the biller. Also, the fee may be set differently for each business providing the billing assistance service. Furthermore, the fee may be set differently for each second payment means used.

[0105] Also, although an example has been described in which the information processing device 300 acquires billing information from the provider terminal 100, the present invention is not limited to this. For example, the information processing device 300 may acquire billing information from a business to which the provider entrusts billing operations and invoice issuance operations, and provide a billing support service.

[0106] In addition, each of the components of the provider terminal 100, user terminal 200, information processing device 300, financial institution system 400, and payment system 500 of the billing support system 1 may include components other than those described above, or may not include some of the components described above.

[0107] In addition, the functions of each component may be realized by other components. For example, some of the functions described as being possessed by the information processing device 300 may be executed by other components such as the provider terminal 100, the user terminal 200, the financial institution system 400, or the payment system 500. Alternatively, some of the functions described as being possessed by the provider terminal 100, the user terminal 200, the financial institution system 400, or the payment system 500 may be executed by other components such as the information processing device 300.

[0108] Furthermore, each of the provider terminal 100, the user terminal 200, the information processing device 300, the financial institution system 400, and the payment system 500 may be composed of multiple devices, or may be composed of a single device.

[0109] In addition, the process in the billing support system according to the above embodiment may include steps other than those in the above flowchart or sequence chart, or may not include some of the above steps. The order of the steps is not limited to the above embodiment. Furthermore, each step may be combined with other steps and executed as one step, may be included in other steps and executed, or may be divided into multiple steps and executed.

[0110] In addition, some steps may be omitted from the above-described flowcharts or sequence charts, and other steps may be added. Some of the steps may be executed simultaneously, and one step may be divided into a plurality of steps and executed.

[0111] As described above, according to the information processing device 300 of the present embodiment, registration of provider information related to a provider providing a product or service is accepted. The information processing device 300 accepts registration of first payment means information related to a first payment means capable of accepting payment of a claim generated from a user by the provider providing the product or service to the user. The information processing device 300 acquires billing information related to the contents of the claim, outputs the billing information so that the user can view it, and generates a payment page for accepting input of second payment means information related to a second payment means used to pay the claim from the user. The information processing device 300 generates access information for the user to access the generated payment page, and outputs the generated access information. The information processing device 300 executes a payment process for an amount corresponding to the claim by the second payment means based on the second payment means information input on the payment page from the user who accessed the payment page using the access information, and bills the user for the amount corresponding to the claim via the second payment means. The information processing device 300 executes a payment process for paying the amount corresponding to the claim to the provider using the first payment means indicated by the first payment means information.

[0112] This allows a provider of goods or services to easily make bills to users that can be paid by other payment methods without changing the payment methods that the provider can accept, and to receive payment by a payment method that the provider can accept. For example, even if the provider itself is not a credit card affiliate or comprehensive affiliate and cannot accept payments by credit card, but can only receive payments by transfer to a bank account, the provider can make bills to users that can be paid by credit card. By inputting the necessary information on the payment page, the user can perform payment processing using a credit card, and can enjoy various benefits of credit card payment. The provider can receive payment by transfer to a bank account that the provider can accept, through processing by the payment processing unit.

[0113] Moreover, the information processing device 300 acquires invoice image information showing an image of an invoice corresponding to the billing information, and outputs an image shown by the invoice image information on the settlement page so that the user can view it. As a result, a user who receives a bill from a provider can check the image of the invoice and the contents of the billing information while performing the payment process simply by viewing the settlement page for performing the payment of the bill. In the conventional payment process of a bill, the user had to manually input the account number, amount, etc. into a screen for requesting transfer to a bank account while separately preparing and checking the document and image of the invoice, and then execute the payment process. According to the information processing device 300 of the present embodiment, the user can execute the payment process using the payment means mainly used by the user, such as the user's credit card, while checking the billing information and the invoice image. As a result, the user can execute the payment process much more efficiently than before.

[0114] Furthermore, the information processing device 300 generates invoice image information based on the billing information, and outputs an image shown by the generated invoice image information so that the user can view it. This allows a business providing a billing support service to generate invoice image information on behalf of the provider based on the billing information received from the provider, and provide it to the user. This eliminates the need for the provider to create a written invoice, generate invoice image information, and upload it to the information processing device 300, greatly improving the efficiency of the provider's billing operations.

[0115] In addition, the information processing device 300 transmits the billing information to a bill creator who creates a bill, acquires bill image information created by the bill creator, and outputs the information so that the user can view it. This allows a business providing a billing support service to efficiently conduct business in cooperation with a business that creates bills on behalf of the user.

[0116] Furthermore, the information processing device 300 acquires multiple billing information, checks the implementation status of the settlement processing and payment processing for each of the acquired multiple billing information, and identifies the processing status for each of the multiple billing information based on the confirmed implementation status. The information processing device 300 displays information indicating the processing status for each identified billing information in a list form in association with each of the multiple billing information. This allows the provider to immediately grasp the contents of the multiple bills, the deadline and progress of the payment processing for each bill, etc., and allows accounting processing such as billing processing and deposit management to be performed easily, reliably, and efficiently.

[0117] The provider information also includes information on the provider's name, location, and contact information, as well as information on the contents of the products or services provided by the provider. This allows the business providing the billing support service to easily and reliably convey information on the provider who is the source of the billing to the user who is the recipient of the billing.

[0118] Furthermore, the information processing device 300 judges whether or not a claim by the provider can be processed based on the provider information, and does not acquire the billing information if it is judged that a claim by the provider cannot be processed. This allows a business providing a billing support service to accurately grasp the attributes and business content of the provider, and the content of the products and services provided, and judge whether or not the billing support service can be provided, and the billing support service can be provided to an appropriate business.

[0119] Moreover, the information processing device 300 further includes a judgment unit that judges whether the payment process has been completed normally, and executes the payment process when it is judged that the payment process has been completed normally, and does not execute the payment process when it is judged that the payment process has not been completed normally. This allows the business providing the billing support service to pay the bill to the provider after it is certain that the bill will be paid by the user. Furthermore, the business providing the billing support service can make an early payment to the provider while suppressing the risk of the user not paying the bill by making a payment to the provider after a credit card payment or the like has been completed, even before the user has made a payment.

[0120] Furthermore, the information processing device 300 executes a process of calculating the amount of a fee to be charged to the provider for the billing based on the billing information and the predetermined fee setting information, and paying the amount obtained by subtracting the amount of the fee from the amount of the executed settlement process to the provider. This allows the business providing the billing support service to easily and reliably collect the fee for the billing support service without having to separately bill for the fee. As for the provider, since there is no need for a separate billing and payment for the fee for the billing support service, the provider can easily utilize the billing support service without any hassle.

[0121] Furthermore, the information processing device 300 can receive an early payment instruction from the provider, which is an instruction to execute payment processing earlier than a predetermined schedule. When an early payment instruction is received, the information processing device 300 calculates the amount of the fee by adding an amount calculated based on the billing information and the predetermined fee setting information to an amount calculated based on the billing information and the predetermined early payment fee setting information. This allows the business providing the billing support service to smoothly accept and process the early payment according to the provider's desire, and also to charge the additional fee related to the early payment together with the fee for the billing support service. Therefore, the business providing the billing support service does not need to charge the fee related to the early payment separately, and can easily and reliably collect the fee related to the early payment by including it in the fee for the billing support service. As for the provider, since there is no need to be charged a fee related to the early payment service separately and make a payment, the provider can easily utilize the early payment service without any trouble.

[0122] The billing information also includes information about the user to whom the billing is to be made and information about the billing amount. This allows the business providing the billing support service to easily and reliably obtain information about the user to whom the billing is to be made and information about the billing amount, enabling the business to provide the billing support service appropriately.

[0123] The billing information also includes information regarding the billing date and the payment deadline, which allows a business providing a billing support service to easily and reliably obtain and manage information regarding the billing date and information regarding the payment deadline, thereby enabling more appropriate management of the status of billing.

[0124] The billing information also includes provider information about the provider who is the source of the billing. This allows the business providing the billing support service to easily and reliably obtain information about the provider who is the source of the billing, and to provide the billing support service appropriately.

[0125] The information processing device 300 can also accept registration of permitted payment method information regarding a second payment method that the user is permitted to use, and outputs the permitted payment method information whose registration has been accepted to the payment page. The information processing device 300 also executes payment processing when the second payment method indicated by the permitted payment method information is input by the user on the payment page. The information processing device 300 does not execute payment processing when the user inputs a payment method other than the second payment method indicated by the permitted payment method information on the payment page. This allows the provider to specify the second payment method that the user is permitted to use, and allows the user to use the second payment method that suits the provider's wishes, for example, in terms of fees, deposit schedules, etc.

[0126] The first payment means is a transfer to a bank account, and the second payment means is a postpaid payment means including credit card payment. The information processing device 300, as an affiliated store that accepts the use of the second payment means by the user, executes a payment process for the amount corresponding to the claim by the second payment means, thereby billing the user for the amount corresponding to the claim. This allows the provider to make a claim that can be paid by credit card to the user, even if the provider itself is not an affiliated store or comprehensive affiliated store of credit cards and cannot accept payments by credit card, but can only accept payments by transfer to a bank account. The user can perform payment processing using a credit card by inputting necessary information on the payment page, and can enjoy various benefits of credit card payment. The provider can receive payment by transfer to a bank account that the provider can accept, through processing by the payment processing unit.

[0127] Furthermore, the payment page accepts input of attribute information including the user's name and contact information in addition to the second payment method information. This allows the business providing the billing support service to easily identify the user who made the payment, even if the holder of the second payment method is different from the user. [Explanation of symbols]

[0128] 1. Billing support system, 100 provider terminals, 110 CPUs, 120 ROMs, 130 RAM, 140 storage, 150 communication interface, 160 Operation display section, 170 Bus, 200 user terminals, 210 CPUs, 220 ROMs, 230 RAM, 240 Storage, 250 communication interface, 260 operation display section, 270 Bus, 300 Information processing device, 310 CPU, 3101 Provider Information Reception Department, 3102 provider payment means reception unit, 3103 Billing information acquisition department; 3104 payment page generation unit, 3105 access information generation unit, 3106 Output section, 3107 payment processing unit, 3108 Payment Processing Unit, 3109 Invoice image acquisition unit, 3110 Image generation unit, 3111 Transmitting unit, 3112 Verification Department, 3113 Specific Department; 3114 List display section, 3115 Provider Judgment Department; 3116 Judgment Department; 3117 Calculation unit, 3118 Instruction Reception Department, 3119 Authorized payment instrument acceptance unit; 320 ROM, 330 RAM, 340 Storage, 350 communication interface, 360 operation display section, 370 Bus, 400 Financial Institution Systems, 410 CPU, 420 ROM, 430 RAM, 440 Storage, 450 communication interface, 460 Operation display section, 470 Bus, 500 payment systems, 510 CPU, 520 ROM, 530 RAM, 540 Storage, 550 communication interface, 560 Operation display section, 570 bus.

Claims

1. a provider information receiving unit that receives registration of provider information relating to a provider of a product or service; a provider payment method receiving unit that receives registration of first payment method information related to a first payment method that can accept payment of a bill generated from a user by the provider providing the user with a product or service; a billing information acquisition unit that acquires billing information relating to the content of the bill; a payment page generating unit that outputs the billing information acquired by the billing information acquiring unit so as to be viewable by the user, and generates a payment page for receiving input of second payment means information relating to a second payment means different from the first payment means used to pay the bill from the user; an access information generating unit that generates access information for the user to access the payment page generated by the payment page generating unit; an output unit that outputs the access information generated by the access information generation unit; a payment processing unit that executes a payment process for the amount corresponding to the claim by the second payment means based on the second payment means information input on the payment page from the user who accessed the payment page using the access information, and charges the amount corresponding to the claim to the user via the second payment means; a payment processing unit that executes a payment process to pay the provider an amount corresponding to the invoice, using the first payment means indicated by the first payment means information; A billing support device having the above configuration.

2. The billing information includes an invoice image acquisition unit that acquires invoice image information indicating an image of the invoice corresponding to the invoice information, The billing support device according to claim 1 , wherein the payment page generation unit outputs the image indicated by the invoice image information on the payment page so as to be viewable by the user.

3. The method further includes an image generating unit that generates the invoice image information based on the invoice information, The billing support device according to claim 2 , wherein the bill image acquisition unit acquires the bill image information generated by the image generation unit.

4. A sending unit that sends the billing information to a bill creator who creates the bill, The billing support device according to claim 2 , wherein the bill image acquisition unit acquires the bill image information generated by the bill creator.

5. The billing information acquisition unit acquires a plurality of pieces of billing information, a confirmation unit that confirms an implementation status of the settlement process in the settlement processing unit and the payment process in the payment processing unit for each of the plurality of billing information acquired by the billing information acquisition unit; an identification unit that identifies a processing status for each of the plurality of pieces of billing information based on the implementation status confirmed by the confirmation unit; a list display unit that displays information indicating a state of the processing related to each of the billing information identified by the identification unit in a list form in association with each of the multiple billing information; The claim support device according to any one of claims 1 to 4, further comprising:

6. 5. The billing support device according to claim 1, wherein the provider information includes information on the name, location, and contact information of the provider, as well as information on the contents of the goods or services provided by the provider.

7. a provider determination unit that determines whether or not the claim by the provider can be processed based on the provider information; The claim support device according to claim 6 , wherein the claim information acquisition unit does not acquire the claim information when the provider determination unit determines that the provider cannot process the claim.

8. a determination unit that determines whether the payment processing has been normally completed by the payment processing unit, A billing support device as described in any one of claims 1 to 4, wherein the payment processing unit executes the payment processing when the judgment unit determines that the payment processing has been completed normally, and does not execute the payment processing when the judgment unit determines that the payment processing has not been completed normally.

9. a calculation unit that calculates a fee to be charged to the provider for the claim based on the claim information and predetermined fee setting information; A billing support device according to any one of claims 1 to 4, wherein the payment processing unit performs a process of paying to the provider an amount obtained by subtracting the amount of the fee from the amount of the payment process performed in the payment processing unit.

10. an instruction receiving unit for receiving an early payment instruction from the provider, the early payment instruction being an instruction for executing the payment processing earlier than a predetermined schedule; A billing support device as described in claim 9, wherein when the early payment instruction is accepted by the instruction accepting unit, the calculation unit adds an amount calculated based on the billing information and the specified fee setting information to an amount calculated based on the billing information and specified early payment fee setting information to calculate the fee amount.

11. 5. The billing support device according to claim 1, wherein the billing information includes information about the user to whom the billing is to be made and information about the billing amount.

12. 5. The billing support device according to claim 1, wherein the billing information includes information regarding a billing date and a payment deadline.

13. 5. The billing support device according to claim 1, wherein the billing information includes provider information relating to the provider who is the source of the billing.

14. the payment method information storing unit storing the second payment method and the first payment method ... second payment method storing unit storing the second payment method and the first payment method storing unit storing the second payment method and the second payment method storing unit storing the second payment method and the second payment method storing unit storing 5. The billing support device according to claim 1, wherein the payment page generation unit outputs, to the payment page, the permitted payment method information whose registration has been accepted by the permitted payment method acceptance unit.

15. The billing support device of claim 14, wherein the payment processing unit executes the payment processing when the second payment means indicated by the permitted payment means information is input by the user on the payment page, and does not execute the payment processing when a payment means other than the second payment means indicated by the permitted payment means information is input by the user on the payment page.

16. 5. A billing support device according to claim 1, wherein the first payment method is a transfer to a bank account, and the second payment method is a postpaid payment method including credit card payment.

17. A billing support device as described in any of claims 1 to 4, wherein the payment processing unit, as an affiliated store that accepts use of the second payment means by the user, bills the user for the amount corresponding to the bill by executing payment processing for the amount corresponding to the bill using the second payment means.

18. 5. The billing support device according to claim 1, wherein the settlement page accepts input of attribute information including information on the user's name and contact details in addition to the second payment method information.

19. A claim support device according to any one of claims 1 to 4, a provider terminal used by the provider; A user terminal used by a user; A billing support system having:

20. a provider information receiving step of receiving registration of provider information relating to a provider of a product or service; a provider payment means receiving step of receiving registration of first payment means information relating to a first payment means that can accept payment of a bill generated from the user by the provider providing the user with a product or service; a billing information acquisition step of acquiring billing information relating to the content of the bill; a payment page generating step of outputting the billing information acquired in the billing information acquiring step so as to be viewable by the user, and generating a payment page for receiving input of second payment means information relating to a second payment means different from the first payment means used to pay the bill from the user; an access information generating step of generating access information for the user to access the payment page generated in the payment page generating step; an output step of outputting the access information generated in the access information generating step; a payment processing step of executing a payment process for the amount corresponding to the invoice by the second payment means based on the second payment means information input by the user on the payment page, and charging the amount corresponding to the invoice to the user via the second payment means; a payment processing step of executing a payment process to pay the amount corresponding to the claim to the provider by using the first payment means indicated by the first payment means information; A claim assistance method having the following:

21. A billing support program for causing an information processing device to function as the billing support device according to any one of claims 1 to 4.

Images