Bill collection server, method, bill collection system, and program

Abstract

To provide a bill collection server for increasing convenience of payment for bill collection services.SOLUTION: A bill collection server includes a billing data acquisition unit for receiving billing data representing an amount billed to a payer from a biller terminal, a billing notification unit for transmitting the billing data to a payer terminal of the payer, a payment request acquisition unit for receiving a request for payment of the billing data from the payer terminal, and an immediate debit request unit for requesting an immediate debit server to immediately debit the amount billed from the payer's account and deposit the amount billed into the biller's account.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a bill collection server, a bill collection method, a bill collection system, and a program. [Background technology]

[0002] Services that support the collection of bills at schools and other institutions are known. In these services, bill data is acquired from a terminal at the school and sent to a terminal at the student's parent or guardian, after which payment is made. [Prior art documents] [Patent documents]

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

[0004] However, with conventional collection support services, parents and guardians of students had to enter their credit card numbers or go to a convenience store to make payments.

[0005] Therefore, an object of the present invention is to improve the convenience of payment in the collection business. [Means for solving the problem]

[0006] A bill collection server according to one embodiment of the present invention comprises a billing data acquisition unit that receives billing data indicating the amount billed to the payer from the biller terminal, a billing notification unit that transmits the billing data to the payer terminal of the payer, a payment request acquisition unit that receives a request for payment of the billing data from the payer terminal, and an immediate withdrawal request unit that requests an immediate withdrawal server to immediately withdraw the billing amount from the payer's account and deposit it in the biller's account. [Effects of the Invention]

[0007] According to the present invention, it is possible to improve the convenience of payments in bill collection services. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram showing an overall configuration according to an embodiment of the present invention; [Figure 2] FIG. 2 is a functional block diagram of a bill collection server according to an embodiment of the present invention. [Figure 3] 10 is an example of data stored in a payer account information storage unit according to one embodiment of the present invention. [Figure 4] 10 is an example of data stored in a biller account information storage unit according to one embodiment of the present invention. [Figure 5] 10 is an example of data stored in a bill collection information storage unit according to one embodiment of the present invention. [Figure 6] FIG. 2 is a functional block diagram of a claimant terminal according to an embodiment of the present invention. [Figure 7] FIG. 2 is a functional block diagram of a payer terminal according to an embodiment of the present invention. [Figure 8] FIG. 10 is a sequence diagram of a collection process according to an embodiment of the present invention. [Figure 9] FIG. 10 is a sequence diagram of an account registration process according to an embodiment of the present invention. [Figure 10] 10 is an example of a screen displayed on a claimant terminal according to an embodiment of the present invention. [Figure 11] 10 is a diagram illustrating an example of transition of a screen displayed on a payer terminal according to an embodiment of the present invention. [Figure 12] 10 is an example of detailed data of deposits and withdrawals by group for a claimant's account in accordance with one embodiment of the present invention. [Figure 13] FIG. 2 is a hardware configuration diagram of a bill collection server according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0009] <Terminology> As used herein, "collection" refers to the act of a biller collecting money from a payer. In this specification, a "claimant" is a party that claims money from a payer. For example, a claimant may be, but is not limited to, a local government or a corporation that operates an elementary school, junior high school, high school, university, vocational school, nursery school, kindergarten, cram school, various classes, sports club, etc. In this specification, a "payer" is a person who pays money to a claimant. For example, payers include, but are not limited to, parents of students and kindergarteners at elementary schools, junior high schools, high schools, universities, vocational schools, nursery schools, kindergartens, cram schools, various classes, sports clubs, etc.

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0011] <Overall composition> 1 is a diagram showing the overall configuration of one embodiment of the present invention. The bill collection system 1 is a system for a biller 21 to collect bills from a payer 31.

[0012] The bill collection system 1 can include a bill collection server 10, a biller terminal 20, a payer terminal 30, an immediate withdrawal server 40, and an accounting system 50. Each of these will be described below.

[0013] <<Collection Server>> The bill collection server 10 receives billing data indicating the amount billed to the payer 31 from the biller terminal 20, transmits the billing data to the payer terminal 30 of the payer 31, and upon receiving a request for payment of the billing data from the payer terminal 30, requests the real-time debit server 40 to immediately debit the amount billed from the account of the payer 31 and deposit it in the account of the biller 21. The bill collection server 10 is made up of one or more computers. Note that in this disclosure, the functions of the bill collection server 10 will be explained while showing how the bill collection server 10 cooperates with the real-time debit server 40, but as will be described in detail below, the bill collection server 10 according to the present invention is not intended to be limited to cooperation with the real-time debit server 40.

[0014] <<Requester's terminal>> The claimant terminal 20 is a terminal operated by the claimant 21. For example, the claimant terminal 20 is a personal computer, a tablet, a smartphone, or the like.

[0015] <<Payer Terminal>> The payer terminal 30 is a terminal operated by the payer 31. For example, the payer terminal 30 is a personal computer, a tablet, a smartphone, or the like.

[0016] <<Immediate Withdrawal Server>> The immediate withdrawal server 40 (or simply referred to as the withdrawal server when not immediate) causes the accounting system 50 of each bank or other financial institution to execute immediate withdrawal. The immediate withdrawal server 40 is made up of one or more computers. Note that the functions of the bill collection server 10 according to the present invention are explained in terms of cooperation with the immediate withdrawal server 40, but the bill collection server 10 can be appropriately linked to any server that has the function of issuing commands to the accounting system.

[0017] <<Accounting system>> Accounting system 50 is an accounting system installed in each bank or other financial institution. Accounting system 50 consists of one or more computers. For example, accounting system 50A is the accounting system of Bank A, accounting system 50B is the accounting system of Bank B, and accounting system 50C is the accounting system of Bank C (note that accounting systems 50A, 50B, and 50C are collectively referred to as accounting systems 50).

[0018] <Function block> The functional configuration of the bill collection server 10 will be described with reference to FIG. 2, the functional configuration of the biller terminal 20 with reference to FIG. 6, and the functional configuration of the payer terminal 30 with reference to FIG.

[0019] <<Collection Server>> Figure 2 is a functional block diagram of the bill collection server 10 according to one embodiment of the present invention. The bill collection server 10 comprises a billing data acquisition unit 101, a billing notification unit 102, a payment request acquisition unit 103, an immediate debit request unit 104, a payment management unit 105, an account registration unit 106, a payer account information storage unit 107, a biller account information storage unit 108, and a bill collection information storage unit 109. By executing a program, the bill collection server 10 functions as the billing data acquisition unit 101, the billing notification unit 102, the payment request acquisition unit 103, the immediate debit request unit 104, the payment management unit 105, and the account registration unit 106.

[0020] The billing data acquisition unit 101 receives billing data indicating the amount billed to the payer 31 from the biller terminal 20. For example, the billing data acquisition unit 101 can receive billing data entered on a web screen displayed on the biller terminal 20.

[0021] The billing notification unit 102 transmits the billing data received by the billing data acquisition unit 101 to the payer terminal 30. For example, the billing notification unit 102 can display the billing data on a web screen displayed on the payer terminal 30 (for example, the web may be displayed on a communication network application between the school etc. and the student's guardian etc., or a link to the web may be notified by SMS (Short Message Service) or email).

[0022] The payment request acquisition unit 103 receives a request for payment of the billing data (specifically, the billing data sent to the payer terminal 30 by the bill notification unit 102) from the payer terminal 30. For example, the payment request acquisition unit 103 can receive a payment request entered on a web screen displayed on the payer terminal 30 (for example, the web may be displayed on a communication network application between the school etc. and the student's guardian etc., or a link to the web may be notified by SMS (Short Message Service) or email).

[0023] The immediate debit request unit (or simply referred to as the debit request unit when not immediate) 104 requests the immediate debit server 40 to immediately debit the bill amount (specifically, the bill amount indicated by the billing data for which the payment request acquisition unit 103 has received the payment request) from the account of the payer 31 and deposit it into the account of the biller 21. Specifically, the immediate debit request unit 104 transmits the bill amount, information on the account of the payer 31, and information on the account of the biller 21 to the immediate debit server 40. Note that, although the functions of the bill collection server 10 according to the present invention have been described in connection with the immediate debit server 40, the bill collection server 10 can be linked to any server that has the function of issuing commands to an accounting system as long as it is a server that has the function of issuing commands to an accounting system.

[0024] The payment management unit 105 manages the status of collection. Specifically, the payment management unit 105 receives information on the success or failure of payment (specifically, the success or failure of immediate deduction from the account of the payer 31 and credit to the account of the biller 21) from the immediate deduction server 40.

[0025] The account registration unit 106 receives account information of the payer 31 from the payer terminal 30 and requests the immediate debit server 40 to register the account of the payer 31. For example, the account registration unit 106 can receive account information of the payer 31 entered on a web screen displayed on the payer terminal 30 (for example, the web may be displayed on a communication network application between the school etc. and the student's parents etc., or a link to the web may be notified by SMS (Short Message Service) or email).

[0026] The payer account information storage unit 107 stores information about the account of the payer 31. It is assumed that the information about the account of the payer 31 has been registered in advance (this will be explained later with reference to FIG. 9).

[0027] The claimant account information storage unit 108 stores account information for the claimant 21. It is assumed that the account information for the claimant 21 has been registered in advance.

[0028] The billing information storage unit 109 stores information on whether or not payment of billing data has been completed. Specifically, the billing information storage unit 109 stores billing data received by the billing data acquisition unit 101 and information on the success or failure of payment received by the payment management unit 105.

[0029] 3 shows an example of data stored in the payer account information storage unit 107 according to one embodiment of the present invention. The payer account information storage unit 107 stores "information for identifying the payer" and "payer account information."

[0030] For example, "information for identifying the payer" is an identifier (payer ID) assigned to each payer, the payer's name, etc.

[0031] For example, "payer's account information" includes the bank name, branch name, account number, etc.

[0032] 4 shows an example of data stored in the claimant account information storage unit 108 according to one embodiment of the present invention. The claimant account information storage unit 108 stores "information for identifying the claimant" and "claimant account information."

[0033] For example, "information for identifying the claimant" is an identifier (claimant ID) assigned to each claimant, claimant name, etc.

[0034] For example, "claimant's account information" includes the bank name, branch name, account number, etc.

[0035] 5 shows an example of data stored in the bill collection information storage unit 109 according to one embodiment of the present invention. The bill collection information storage unit 109 stores a "billing data ID," a "billing amount," "information for identifying the payer," "information for identifying the biller," and a "billing status."

[0036] "Billing data ID" is an identifier given to each billing data.

[0037] "Billing amount" is the amount billed by the biller 21 to the payer 31. The billing amount indicated by the billing data received by the billing data acquisition unit 101 is stored.

[0038] "Information for identifying the payer" includes the payer ID, payer name, etc.

[0039] "Information for identifying the claimant" includes the claimant ID, claimant name, etc.

[0040] "Collection status" is information on whether or not payment of billing data has been completed. Information on the success or failure of payment received by the payment management unit 105 is stored.

[0041] <<Requester's terminal>> 6 is a functional block diagram of the claimant terminal 20 according to one embodiment of the present invention. The claimant terminal 20 comprises a registration unit 201, a claim data notification unit 202, and a management unit 203. The claimant terminal 20 functions as the registration unit 201, the claim data notification unit 202, and the management unit 203 by executing a program.

[0042] The registration unit 201 requests the bill collection server 10 to register the account information of the biller 21.

[0043] The billing data notification unit 202 transmits billing data indicating the amount billed to the payer 31 to the bill collection server 10.

[0044] The management unit 203 receives the status of collection from the collection server 10 and displays it on the biller terminal 20.

[0045] <<Payer Terminal>> 7 is a functional block diagram of a payer terminal 30 according to one embodiment of the present invention. Payer terminal 30 comprises a registration unit 301, a claim acquisition unit 302, a payment request unit 303, and a management unit 304. Payer terminal 30 functions as registration unit 301, claim acquisition unit 302, payment request unit 303, and management unit 304 by executing a program.

[0046] The registration unit 301 requests the bill collection server 10 to register the account information of the payer 31.

[0047] The bill acquisition unit 302 receives bill data indicating the amount billed to the payer 31 from the bill collection server 10.

[0048] The payment request unit 303 sends a request for payment of the billing data received by the billing acquisition unit 302 to the billing collection server 10, and causes the billing collection server 10 to request the immediate deduction server 40 to immediately debit the billing amount (specifically, the billing amount indicated by the billing data received by the billing acquisition unit 302) from the account of the payer 31 and deposit it into the account of the biller 21.

[0049] The management unit 304 receives the status of collection from the collection server 10 and displays it on the payer terminal 30.

[0050] <Processing method> The bill collection process will be described with reference to FIG. 8, and the account registration process will be described with reference to FIG.

[0051] <<Collection Processing>> FIG. 8 is a sequence diagram of a bill collection process according to one embodiment of the present invention.

[0052] In step 101 (S101), the biller terminal 20 logs in to a service that supports bill collection operations provided by the bill collection server 10. Specifically, the biller 21 inputs information for identifying the biller (such as a biller ID) into the biller terminal 20, and the biller terminal 20 transmits the information for identifying the biller (such as a biller ID) to the bill collection server 10.

[0053] In step 102 (S102), billing data indicating the amount billed to the payer 31 is input to the biller terminal 20. The billing data may include the nominal amount, the quantity, the unit price, etc. Specifically, the billing data and information for identifying the payer 31 (e.g., the payer ID, the payer name, etc.) are input to the biller terminal 20.

[0054] For example, the claimant 21 inputs information for identifying the billing data and the payer 31 on a screen displayed on the claimant terminal 20 (e.g., a web screen, the screen of an application program installed on the claimant terminal 20, etc.). Note that the billing data and the information for identifying the payer 31 may be input into the claimant terminal 20 by reading a file created in advance (e.g., a file storing billing data indicating the amounts billed to each of multiple payers 31).

[0055] In step 103 (S103), the claimant terminal 20 transmits the claim data entered in S102 and information for identifying the payer 31 to the bill collection server 10.

[0056] In step 104 (S104), the collection server 10 stores the billing amount indicated by the billing data received in S103, the information for identifying the payer 31 received in S103, and the information for identifying the biller 21 received in S101 in the collection information storage unit 109.

[0057] In step 105 (S105), the bill collection server 10 transmits the billing data received in S103 to the payer terminal 30 of the payer 31 specified by the information for identifying the payer 31 received in S103.

[0058] In step 106 (S106), the payer terminal 30 requests the bill collection server 10 to pay the bill based on the bill data received in S105.

[0059] In step 107 (S107), the bill collection server 10 identifies the account of the payer 31 and the account of the biller 21. The bill collection server 10 may cause the payer terminal 30 to display the identified account of the payer 31.

[0060] The bill collection server 10 refers to the bill collection information storage unit 109 and specifies information for identifying the payer 31 of the bill data for which payment has been requested in S106. Next, the bill collection server 10 refers to the payer account information storage unit 107 and specifies the account of the payer 31 linked to the information for identifying the specified payer 31. Note that multiple accounts of the payer 31 may be registered in the payer account information storage unit 107, and the payer 31 may be allowed to specify any one of the multiple accounts in S106.

[0061] The bill collection server 10 refers to the bill collection information storage unit 109 to identify information for identifying the biller 21 of the billing data for which payment was requested in S106. Next, the bill collection server 10 refers to the biller account information storage unit 108 to identify the account of the biller 21 linked to the information for identifying the identified biller 21.

[0062] In step 108 (S108), the bill collection server 10 requests the real-time debit server 40 to immediately debit the bill amount from the account of the payer 31 and deposit it into the account of the biller 21. Specifically, the bill collection server 10 transmits the bill amount, information about the account of the payer 31, and information about the account of the biller 21 to the real-time debit server 40.

[0063] In step 109 (S109), the immediate withdrawal server 40 requests the accounting system 50 (specifically, the accounting system of a financial institution such as a bank where the payer 31's account is opened) to immediately withdraw the amount claimed from the payer 31's account and deposit it into the biller 21's account.

[0064] In step 110 (S110), the accounting system 50 immediately debits the billing amount from the account of the payer 31. After that, the billing amount immediately debited from the account of the payer 31 is saved for a certain period of time at a financial institution such as a bank where the account of the biller 21 is opened, and then deposited into the account of the biller 21.

[0065] In step 111 (S111), the accounting system 50 transmits the result of the immediate debit (i.e., information on the success or failure of the payment (specifically, the success or failure of the immediate debit from the payer 31's account and the credit to the biller 21's account)) to the immediate debit server 40.

[0066] In step 112 (S112), the immediate deduction server 40 transmits the result of the immediate deduction received in S111 to the bill collection server 10.

[0067] In step 113 (S113), the bill collection server 10 executes settlement based on the result of the immediate deduction received in S112. Specifically, the bill collection server 10 refers to the bill collection information storage unit 109 and changes the collection status of the billing data for which the immediate deduction was executed from "unpaid" to "paid."

[0068] In step 114 (S114), the bill collection server 10 transmits the result of the immediate withdrawal received in S112 to the biller terminal 20.

[0069] In step 115 (S115), the result of the immediate withdrawal received in S112 is transmitted to the payer terminal 30.

[0070] <<Account registration process>> FIG. 9 is a sequence diagram of an account registration process according to one embodiment of the present invention.

[0071] In step 201 (S201), the payer terminal 30 requests the bill collection server 10 to register the account of the payer 31 as a withdrawal account when executing immediate withdrawal. Specifically, the payer terminal 30 transmits to the bill collection server 10 the account information of the payer 31 entered into the payer terminal 30 (e.g., bank name, branch name, account number, etc.).

[0072] In step 202 (S202), the bill collection server 10 requests the real-time debit server 40 to register the account of the payer 31 received in S201 as a debit account when executing real-time debit. Specifically, the bill collection server 10 transmits the account information of the payer 31 received in S201 to the real-time debit server 40.

[0073] In step 203 (S203), the immediate debit server 40 requests the accounting system 50 (specifically, the accounting system of the financial institution such as the bank where the account of the payer 31 is opened) to register the account of the payer 31 received in S202 as the debit account when executing the immediate debit. Specifically, the immediate debit server 40 transmits the account information of the payer 31 received in S202 to the accounting system 50.

[0074] In step 204 (S204), the accounting system 50 registers the account of the payer 31 received in S203 as the debit account when executing the immediate debit.

[0075] In step 205 (S205), the accounting system 50 transmits the result of the registration in S204 to the bill collection server 10.

[0076] In step 206 (S206), the bill collection server 10 registers the account of the payer 31 that received the result in S205 (specifically, stores the account information of the payer 31 in the payer account information storage unit 107).

[0077] In step 207 (S207), the bill collection server 10 transmits the result of the registration in S206 to the payer terminal 30.

[0078] FIG. 10 is an example of a screen displayed on the claimant terminal 20 according to one embodiment of the present invention.

[0079] The biller 21 can input billing data (specifically, the billing title (e.g., books, stationery), quantity (e.g., 1, 2), unit price (e.g., 1,000 yen, 500 yen)) and information for identifying the payer 31 (e.g., payer ID, payer name, etc.) on a screen such as that shown in Figure 10 displayed on the biller terminal 20. After input, the total billing amount may be calculated and displayed.

[0080] On a screen such as that shown in Figure 10 displayed on the claimant terminal 20, the claimant 21 can select the method of sending the claim data to the payer terminal 30 (for example, a method of notifying the URL (Uniform Resource Locator) of the web where the claim data will be displayed.The web may be displayed on a communication network application between the school, etc. and the student's parents, etc., or a link to the web may be notified via SMS (Short Message Service) or email).

[0081] After entering information on a screen such as that shown in Figure 10 displayed on the biller terminal 20, the biller 21 can select an invoice issue button or the like to send the billing data from the biller terminal 20 to the collection server 10.

[0082] FIG. 11 shows an example of transition of screens displayed on the payer terminal 30 according to one embodiment of the present invention.

[0083] In step 1001 (S1001), a message indicating that the billing data has been received is displayed on the home screen of the payer terminal 30 (when the payer terminal 30 receives the billing data in S105 of FIG. 8, the screen of S1001 is displayed). When the payer 31 selects a button such as "Notify" on the screen of S1001, the process proceeds to step 1002.

[0084] In step 1002 (S1002), the billing data (specifically, the nominal amount, quantity, unit price, and total billing amount) is displayed (the billing data received by the payer terminal 30 in S105 of FIG. 8 is displayed). When the payer 31 selects a button such as "Pay" on the screen in S1002, the process proceeds to step 1003.

[0085] In step 1003 (S1003), information on the account from which the immediate withdrawal will be made is displayed (the account of the payer 31 identified in S107 of FIG. 8 is displayed). When the payer 31 selects a button such as "Pay" on the screen in S1003, the process proceeds to step 1004. Note that the immediate withdrawal may be made after authentication.

[0086] In step 1004 (S1004), the billing data for which immediate withdrawal was executed in S1003 is displayed in the payment list as having been paid.

[0087] <Linkage with communication network applications> In one embodiment of the present invention, the bill collection server 10 can link and manage information about the payer 31 (specifically, the student's name, grade, class, attendance number, etc.) managed by a communication network application between schools, etc. and the student's parents, etc., with information about the payer 31 (specifically, account information, contact information (telephone number, email address, etc.)) managed by the bill collection server 10. The bill collection server 10 can acquire the student's name, grade, class, attendance number, etc. entered on a web screen displayed on the communication network application, and use the acquired information to identify the account information, contact information, etc. Therefore, the communication network application can provide a service that supports bill collection work without the need to manage personal information such as the payer's 31's account information and contact information.

[0088] <Effects> In this way, in one embodiment of the present invention, the payer 31, such as a student's parent or guardian, can make a payment by immediately withdrawing the amount from a desired account that has been registered in advance.

[0089] <Other embodiments> [Payment type] In one embodiment of the present invention, the payment is not limited to immediate withdrawal. For example, the payment may be withdrawn on a predetermined designated date instead of immediate withdrawal.

[0090] [Management of claimant's account] In one embodiment of the present invention, the bill collection server 10 can manage and store data by dividing the details of deposits and withdrawals into multiple groups for the account (account opened at a financial institution) of the biller 21, such as a school, based on data regarding remittances sent and received between the bill collection server 10 and the accounting system 50.

[0091] Specifically, when a deposit is made into the account of a biller 21 such as a school, the bill collection server 10 distributes the deposited amount to each group (for example, multiple groups such as each grade, PTA, savings, etc.). When a withdrawal is made from each group (in other words, the bill collection server 10 receives a request for remittance, such as a transfer from the biller's 21 account to various payee accounts, from the biller terminal 20, and requests the remittance from the accounting system 50), the bill collection server 10 records when, who, where, how much, and for what purpose the withdrawal was made. In this way, the accounts of the biller 21 such as a school can be consolidated into one, allowing the biller 21 to manage them centrally, facilitating the management of passbooks and seals.

[0092] 12 is an example of detailed deposit and withdrawal data by group for the account of the claimant 21 according to one embodiment of the present invention. The bill collection server 10 can divide the details of deposits and withdrawals for an account opened by the claimant 21 (for example, a school) at a financial institution into multiple groups (for example, a group called 1st year class 1 and a group called 1st year class 2), and store detailed deposit and withdrawal data for each group based on student information managed by a communication network application or the like.

[0093] [Payment processing from biller's account] In one embodiment of the present invention, the collection server 10 can receive a request for remittance, such as a transfer from the account of the claimant 21 (e.g., a school account) to the account of various payees (e.g., a travel agency), from the claimant terminal 20 and request the remittance from the accounting system 50.

[0094] <Hardware configuration> 13 is a hardware configuration diagram of the bill collection server 10 according to one embodiment of the present invention. The same applies to the biller terminal 20, the payer terminal 30, the immediate withdrawal server 40, and the accounting system 50.

[0095] The bill collection server 10 can include a control unit 1001, a main memory unit 1002, an auxiliary memory unit 1003, an input unit 1004, an output unit 1005, and an interface unit 1006. Each of these will be described below.

[0096] The control unit 1001 is a processor (for example, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), etc.) that executes various programs installed in the auxiliary storage unit 1003.

[0097] The main memory unit 1002 includes a non-volatile memory (Read Only Memory (ROM)) and a volatile memory (Random Access Memory (RAM)). The ROM stores various programs, data, etc. required for the control unit 1001 to execute various programs installed in the auxiliary memory unit 1003. The RAM provides a working area into which the various programs installed in the auxiliary memory unit 1003 are expanded when executed by the control unit 1001.

[0098] The auxiliary storage unit 1003 is an auxiliary storage device that stores various programs and information used when the various programs are executed.

[0099] The input unit 1004 is an input device through which the operator of the bill collection server 10 inputs various instructions to the bill collection server 10 .

[0100] The output unit 1005 is an output device that outputs the internal state of the bill collection server 10 and the like.

[0101] The interface unit 1006 is a communication device for connecting to a network and communicating with other devices.

[0102] In one embodiment of the present invention, a bill collection server is provided that receives billing data indicating the amount billed to the payer from the biller terminal, transmits the billing data to the payer terminal of the payer, receives a request for payment of the billing data from the payer terminal, and requests a server such as an immediate deduction server to immediately debit the billing amount from the payer's account and deposit it in the biller's account. In one embodiment of the present invention, the billing amount may be debited on a predetermined designated deduction date rather than immediately.

[0103] In one embodiment of the present invention, the bill collection server manages and stores data on details of deposits and withdrawals from the biller's account, dividing the details into multiple groups.

[0104] In one embodiment of the present invention, the collection server includes a payer account information storage unit in which information about the payer's account is stored, and a biller account information storage unit in which information about the biller's account is stored.

[0105] In one embodiment of the present invention, the collection server transmits the bill amount, the payer's account information, and the biller's account information to a server such as an immediate debit server.

[0106] In one embodiment of the present invention, the collection server receives payment success or failure information from a server such as an immediate debit server.

[0107] In one embodiment of the present invention, the collection server receives information of the payer's account from the payer terminal and requests a server, such as an immediate debit server, to register the payer's account.

[0108] In one embodiment of the present invention, there is provided a method executed by a bill collection server, the method including the steps of receiving bill data indicating a bill amount to be billed to a payer from a biller terminal, transmitting the bill data to the payer terminal of the payer, receiving a request for payment of the bill data from the payer terminal, and requesting a server such as an instant account transfer server to immediately debit the bill amount from the payer's account and credit it to the biller's account. In one embodiment of the present invention, the debit may be made on a predetermined designated debit date rather than immediately.

[0109] In one embodiment of the present invention, there is provided a bill collection system including a bill collection server, a biller terminal, and a payer terminal, in which the bill collection server receives bill data indicating the bill amount to the payer from the biller terminal, transmits the bill data to the payer terminal of the payer, receives a request for payment of the bill data from the payer terminal, and requests a server such as an immediate deduction server to immediately debit the bill amount from the payer's account and deposit it in the biller's account. In one embodiment of the present invention, the bill collection system may be debited on a predetermined designated deduction date rather than immediately.

[0110] In one embodiment of the present invention, a program is provided to cause a payer terminal to execute the following processes: receiving billing data indicating the amount billed to the payer from a bill collection server; transmitting a request for payment of the billing data to the bill collection server; and causing the bill collection server to execute a request to a server such as an immediate deduction server to immediately debit the billing amount from the payer's account and deposit it in the biller's account. In one embodiment of the present invention, the deduction may be made on a predetermined designated deduction date instead of an immediate deduction.

[0111] Although the embodiments have been described above, changes in form and details are possible without departing from the spirit and scope of the claims. [Explanation of symbols]

[0112] 1. Collection system 10. Collection Server 20 Claimant terminal 21 Claimant 30 Payer Terminal 31 Payer 40 Instant Withdrawal Server 50 Accounting Systems 101 Billing Data Acquisition Department 102 Claim Notification Department 103 Payment request acquisition unit 104 Immediate Withdrawal Request Section 105 Payment Management Department 106 Account Registration Department 107 Payer account information storage unit 108 Claimant account information storage unit 109 Collection information storage unit 201 Registration Department 202 Billing Data Notification Department 203 Management Department 301 Registration Department 302 Billing Acquisition Department 303 Payment Request Section 304 Management Department 1001 control section 1002 Main memory 1003 Auxiliary storage unit 1004 Input section 1005 Output section 1006 Interface section

Claims

1. a payer account information storage unit in which information on the payer's account is stored; a billing data acquisition unit that receives billing data indicating the amount billed to the payer from the biller terminal; a billing notification unit that transmits the billing data to a payer terminal of the payer; a payment request acquisition unit that receives a request for payment of the billing data from the payer terminal; an immediate debit request unit that refers to the payer account information storage unit to identify the payer's account linked to the billing data, and requests an immediate debit server to immediately debit the billing amount from the payer's account and deposit it into the biller's account; Equipped with A bill collection server in which details of deposits to the biller's account are stored in a plurality of groups.

2. The bill collection server according to claim 1, wherein the immediate debit request unit requests the immediate debit server to immediately debit the bill amount from an account designated by the payer among the plurality of accounts of the payer and deposit the amount into the account of the biller.

3. a claimant account information storage unit in which information on the claimant's account is stored; The bill collection server according to claim 1 , comprising:

4. 4. The bill collection server according to claim 3, wherein the immediate deduction request unit transmits the bill amount, information on the payer's account, and information on the biller's account to the immediate deduction server.

5. 5. The bill collection server according to claim 4, further comprising a payment management unit that receives information on the success or failure of the payment from the immediate withdrawal server.

6. receiving information about the payer's account from the payer terminal; 2. The bill collection server according to claim 1, further comprising an account registration unit that requests the immediate debit server to register the payer's account.

7. A method executed by a bill collection server having a payer account information storage unit in which information on a payer's account is stored, receiving billing data indicating the amount billed to the payer from a biller terminal; transmitting the billing data to a payer terminal of the payer; receiving a request for payment of the billing data from the payer terminal; a step of referring to the payer account information storage unit to identify the payer's account linked to the billing data, and requesting an instant account transfer server to immediately debit the billing amount from the payer's account and deposit it into the biller's account; Including, A method in which details of credits to the biller's account are stored in the bill collection server in a plurality of groups.

8. A bill collection system including a bill collection server, a biller terminal, and a payer terminal, The bill collection server a payer account information storage unit in which information on the payer's account is stored; a billing data acquisition unit that receives billing data indicating the amount billed to the payer from the biller terminal; a billing notification unit that transmits the billing data to a payer terminal of the payer; a payment request acquisition unit that receives a request for payment of the billing data from the payer terminal; an immediate debit request unit that refers to the payer account information storage unit to identify the payer's account linked to the billing data, and requests an immediate debit server to immediately debit the billing amount from the payer's account and deposit it into the biller's account; Equipped with A bill collection system in which details of deposits to the biller's account are divided into a plurality of groups and stored in the bill collection server.

9. At the payer terminal, receiving billing data indicating the amount billed to the payer from a bill collection server having a payer account information storage unit in which information on the payer's account is stored; A process of causing the bill collection server to send a request for payment of the billing data to the billing server, refer to the payer account information storage unit to identify the payer's account linked to the billing data, and request an immediate debit server to immediately debit the billing amount from the payer's account and deposit it into the biller's account. Execute A program in which details of deposits to the biller's account are divided into a plurality of groups and stored in the bill collection server.

Images