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 collection server, method, collection system, and program.

Background Art

[0002] Conventionally, services for assisting collection operations in schools and the like are known. In services for assisting collection operations, data of invoices is acquired from terminals such as schools and notified to terminals of guardians of students and the like, and then payments are made.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in conventional services for assisting collection operations, guardians of students and the like had to enter the numbers of credit cards or go to convenience stores for payments.

[0005] Therefore, an object of the present invention is to improve the convenience of payment in collection operations.

Means for Solving the Problems

[0006] A collection server according to an embodiment of the present invention includes a billing data acquisition unit that receives billing data indicating an amount to be billed to a payer from a 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 payment request for the billing data from the payer terminal, and an immediate debit request unit that requests an immediate debit server to immediately debit the amount to be billed from the payer's account and deposit it into the biller's account.

Effects of the Invention

[0007] According to the present invention, the convenience of payment in the collection business can be improved.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Mode for Carrying Out the Invention

[0009] <Explanation of Terms> · In this specification, "collection" means that the claimant collects money from the payer. · In this specification, a "claimant" is a person who claims money from a payer. For example, the claimant may be a local government, or a corporation operating a primary school, junior high school, high school, university, vocational school, nursery, kindergarten, cram school, various classrooms, sports club, etc., but is not limited thereto. · In this specification, a "payer" is a person who pays money to a claimant. For example, the payer may be a parent or guardian of a student in a primary school, junior high school, high school, university, vocational school, nursery, kindergarten, cram school, various classrooms, sports club, etc., but is not limited thereto.

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

[0011] <Overall Configuration> FIG. 1 is a diagram showing the overall configuration according to an embodiment of the present invention. The collection system 1 is a system for a claimant 21 to collect money from a payer 31.

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

[0013] <<Collection Server>> The collection server 10 receives claim data indicating the amount to be claimed from the payer 31 from the claimant terminal 20, transmits the claim data to the payer terminal 30 of the payer 31, and when receiving a payment request for the claim data from the payer terminal 30, requests the immediate debit server 40 to immediately debit the claim amount from the account of the payer 31 and deposit it into the account of the claimant 21. The collection server 10 consists of one or more computers. In the present disclosure, the collection server 10 will be described with its function while showing the cooperation mode with the immediate debit server 40. However, as will be described in detail below, the collection server 10 according to the present invention is not intended to be limited to the cooperation with the immediate debit server 40.

[0014] <<Claimer 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 Debit Server>> The immediate debit server (if not immediate, simply also referred to as the debit server) 40 causes the accounting system 50 of financial institutions such as each bank to perform an immediate debit. The immediate debit server 40 consists of one or more computers. Note that although the collection server 10 according to the present invention is described in terms of its cooperation with the immediate debit server 40, the collection server 10 can be appropriately cooperated in terms of its function as long as it is a server having a function of instructing the accounting system.

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

[0018] <Functional Block> The functional configuration of the collection server 10 will be described with reference to FIG. 2, the functional configuration of the claimant terminal 20 will be described with reference to FIG. 6, and the functional configuration of the payer terminal 30 will be described with reference to FIG. 7.

[0019] <<Collection Server>> FIG. 2 is a functional block diagram of the collection server 10 according to an embodiment of the present invention. The collection server 10 includes 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 claimant account information storage unit 108, and a collection information storage unit 109. The 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 by executing a program.

[0020] The billing data acquisition unit 101 receives billing data indicating the amount to be billed to the payer 31 from the claimant terminal 20. For example, the billing data acquisition unit 101 can receive the billing data input on the web screen displayed on the claimant 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 the web screen displayed on the payer terminal 30 (for example, the web may be displayed on the communication network application between a school or the like and the guardians of students, 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 payment request for the billing data (specifically, the billing data transmitted by the billing notification unit 102 to the payer terminal 30) from the payer terminal 30. For example, the payment request acquisition unit 103 can receive the payment request input on the web screen displayed on the payer terminal 30 (for example, the web may be displayed on the communication network application between a school or the like and the guardians of students, or a link to the web may be notified by SMS (Short Message Service) or email).

[0023] The immediate debit request section (when it is not immediate, it is simply also referred to as the debit request section) 104 requests the immediate debit server 40 to immediately debit the amount to be billed (specifically, the amount to be billed indicated by the billing data for which the payment request acquisition section 103 has received a payment request) from the account of the payer 31 and deposit it into the account of the claimant 21. Specifically, the immediate debit request section 104 transmits the amount to be billed, the information on the account of the payer 31, and the information on the account of the claimant 21 to the immediate debit server 40. Although the collection server 10 according to the present invention is explaining its function in cooperation with the immediate debit server 40, the collection server 10 can be appropriately functionally linked as long as it is a server having a function of instructing an accounting system.

[0024] The payment management section 105 manages the status of collections. Specifically, the payment management section 105 receives information on the success or failure of payment (specifically, the success or failure of immediate debit from the account of the payer 31 and deposit into the account of the claimant 21) from the immediate debit server 40.

[0025] The account registration section 106 receives information on the account 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 section 106 can receive information on the account of the payer 31 input on a web screen displayed on the payer terminal 30 (for example, the web may be displayed on a communication network application between a school or the like and the guardian of a student, or a link to the web may be notified by SMS (Short Message Service) or email).

[0026] Information on the account of the payer 31 is stored in the payer account information storage section 107. Note that the information on the account of the payer 31 is assumed to be registered in advance (described later with reference to FIG. 9).

[0027] Information on the account of the claimant 21 is stored in the claimant account information storage section 108. Note that the information on the account of the claimant 21 is assumed to be registered in advance.

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

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

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

[0031] For example, the "information on the payer's account" is the bank name, branch name, account number, and the like.

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

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

[0034] For example, the "information on the claimant's account" is the bank name, branch name, account number, and the like.

[0035] FIG. 5 is an example of the data stored in the collection information storage unit 109 according to an embodiment of the present invention. The collection information storage unit 109 stores a "claim data ID", a "claim amount", "information for identifying the payer", "information for identifying the claimant", and a "collection status".

[0036] The "claim data ID" is an identifier assigned to each claim data.

[0037] The "claim amount" is the amount claimed by the claimant 21 from the payer 31. The claim amount indicated by the claim data received by the claim data acquisition unit 101 is stored.

[0038] The "information for identifying the payer" is the payer ID, payer name, etc.

[0039] The "information for identifying the claimant" is the claimant ID, claimant name, etc.

[0040] The "collection status" is information on whether the payment for the claim data has been made. The information on the success or failure of the payment received by the payment management unit 105 is stored.

[0041] <<Claimant Terminal>> FIG. 6 is a functional block diagram of a claimant terminal 20 according to an embodiment of the present invention. The claimant terminal 20 includes 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 collection server 10 to register the information of the account of the claimant 21.

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

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

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

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

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

[0048] The payment request unit 303 sends a payment request for the claim data received by the claim acquisition unit 302 to the collection server 10, and requests the immediate debit server 40 to immediately debit the amount to be claimed (specifically, the amount to be claimed indicated by the claim data received by the claim acquisition unit 302) from the account of the payer 31 and deposit it into the account of the claimant 21, causing the collection server 10 to execute this.

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

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

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

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

[0053] In step 102 (S102), claim data indicating the amount to be claimed from the payer 31 is input into the claimant terminal 20. Note that the claim data may include items, quantities, unit prices, etc. Specifically, the claim data and information for identifying the payer 31 (for example, the payer ID, payer name, etc.) are input into the claimant terminal 20.

[0054] For example, claimant 21 inputs claim data and information for identifying the payer 31 on a screen displayed on the claimant terminal 20 (for example, a web screen, a screen of an application program installed on the claimant terminal 20, etc.). Note that information for identifying the claim data and the payer 31 may be input to the claimant terminal 20 by reading a pre-created file (for example, a file storing each claim data indicating the amount of each claim to a plurality of payers 31).

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

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

[0057] In step 105 (S105), the collection server 10 transmits the claim 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 collection server 10 to pay the claim data received in S105.

[0059] In step 107 (S107), the collection server 10 identifies the account of the payer 31 and the account of the claimant 21. Note that the collection server 10 may display the identified account of the payer 31 on the payer terminal 30.

[0060] The collection server 10 refers to the collection information storage unit 109 to identify information for identifying the payer 31 of the claim data for which payment was requested in S106. Next, the collection server 10 refers to the payer account information storage unit 107 to identify the account of the payer 31 associated with the information for identifying the payer 31. Note that a plurality of accounts of the payer 31 may be registered in the payer account information storage unit 107 so that the payer 31 can specify any one of the plurality of accounts in S106.

[0061] The collection server 10 refers to the collection information storage unit 109 to identify information for identifying the claimant 21 of the claim data for which payment was requested in S106. Next, the collection server 10 refers to the claimant account information storage unit 108 to identify the account of the claimant 21 associated with the information for identifying the claimant 21.

[0062] In step 108 (S108), the collection server 10 requests the immediate debit server 40 to immediately debit the claim amount from the account of the payer 31 and deposit it into the account of the claimant 21. Specifically, the collection server 10 transmits the claim amount, the information of the account of the payer 31, and the information of the account of the claimant 21 to the immediate debit server 40.

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

[0064] In step 110 (S110), the accounting system 50 immediately debits the claim amount from the account of the payer 31. Thereafter, the amount of the claim immediately debited from the account of the payer 31 is deposited into the account of the claimant 21 after being stored for a certain period at a financial institution such as a bank where the account of the claimant 21 is opened.

[0065] In step 111 (S111), the accounting system 50 transmits the result of the immediate debit (that is, information on the success or failure of the payment (specifically, the success or failure of being immediately debited from the account of the payer 31 and credited to the account of the claimant 21)) to the immediate debit server 40.

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

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

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

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

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

[0071] In step 201 (S201), the payer terminal 30 requests the collection server 10 to register the account of the payer 31 as the debit account when executing the immediate debit. Specifically, the payer terminal 30 transmits the information of the account of the payer 31 (for example, bank name, branch name, account number, etc.) input to the payer terminal 30 to the collection server 10.

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

[0073] In step 203 (S203), the immediate debit server 40 requests the accounting system 50 (specifically, the accounting system of a financial institution such as a 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 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 immediate debit.

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

[0076] In step 206 (S206), the collection server 10 registers the account of the payer 31 whose result was received 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 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 an embodiment of the present invention.

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

[0080] The claimant 21 can select, on a screen like that shown in FIG. 10 displayed on the claimant terminal 20, the method for transmitting the billing data to the payer terminal 30 (e.g., the method for notifying the URL (Uniform Resource Locator) of the web page where the billing data is displayed. The web page may be displayed on an application for the communication network between a school, etc. and the guardians of students, etc., or a link to the web page may be notified via SMS (Short Message Service) or email).

[0081] After input on a screen like that shown in FIG. 10 displayed on the claimant terminal 20, the claimant 21 can select a button such as a billing statement issuance button, etc. to cause the claimant terminal 20 to transmit the billing data to the collection server 10.

[0082] FIG. 11 is an example of the screen transition of the payer terminal 30 according to an embodiment of the present invention.

[0083] In step 1001 (S1001), it is displayed on the home screen of the payer terminal 30 that the billing data has been received (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 "notification" on the screen of S1001, it proceeds to step 1002.

[0084] In step 1002 (S1002), the billing data (specifically, the name, quantity, unit price, 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 of S1002, it proceeds to step 1003.

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

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

[0087] <Linkage with Contact Network Application> In one embodiment of the present invention, the collection server 10 can manage by associating information on payer 31 (specifically, name of student, grade, group, attendance number, etc.) managed by a contact network application between a school or the like and a guardian of the student, etc., with information on payer 31 (specifically, account information, contact information (phone number, email address, etc.), etc.) managed by the collection server 10. The collection server 10 can acquire the name of the student, grade, group, attendance number, etc. input on the web screen displayed on the contact network application, and identify the account information, contact information, etc. using the acquired information. Therefore, the contact network application can provide a service to support the collection business without the need to manage personal information such as the account information and contact information of payer 31.

[0088] <Effect> As described above, in one embodiment of the present invention, payer 31 such as a guardian of a student can immediately debit from a desired account registered in advance to complete the payment.

[0089] <Other Embodiments> [Type of Settlement] In one embodiment of the present invention, it is not limited to immediate debit. For example, instead of immediate debit, it may be set to debit on a predetermined debit designation date.

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

[0091] Specifically, when there is a deposit into the account of the claimant 21 such as a school, the collection server 10 distributes the deposited amount to each group (for example, a plurality of groups such as each grade, PTA, savings, etc.). When there is a withdrawal from each group (that is, the collection server 10 receives a request for a remittance such as a transfer from the account of the claimant 21 to the accounts of various payees from the claimant terminal 20 and requests the accounting system 50 to make the remittance), the collection server 10 records when, who, where, how much, and for what purpose the withdrawal was made. In this way, the account of the claimant 21 such as a school can be unified and managed by the claimant 21, and the management of the passbook and seal can be facilitated.

[0092] FIG. 12 is an example of data on the details of deposits and withdrawals by group of the account of the claimant 21 according to one embodiment of the present invention. The collection server 10 divides the details of deposits and withdrawals of the account opened by the claimant 21 (for example, a school) at a financial institution into a plurality of groups (for example, a group called Class 1, Grade 1 and a group called Class 2, Grade 1), and can store data on the details of deposits and withdrawals of each group based on the information of students managed by a contact network application or the like.

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

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

[0095] The collection server 10 can include a control unit 1001, a main memory unit 1002, an auxiliary storage unit 1003, an input unit 1004, an output unit 1005, and an interface unit 1006. Each 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 (ROM (Read Only Memory)) and a volatile memory (RAM (Random Access Memory)). The ROM stores various programs, data, etc. necessary for the control unit 1001 to execute various programs installed in the auxiliary storage unit 1003. The RAM provides a working area that is expanded when various programs installed in the auxiliary storage unit 1003 are 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 various programs are executed.

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

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

[0101] The interface unit 1006 is a communication device that connects to a network and communicates with other devices.

[0102] In one embodiment of the present invention, billing data indicating the amount to be billed to the payer is received from the claimant terminal, the billing data is transmitted to the payer's payer terminal, a payment request for the billing data is received from the payer terminal, and the server such as an immediate debit server is requested to immediately debit the amount to be billed from the payer's account and deposit it into the claimant's account. In one embodiment of the present invention, instead of immediate debit, it may be debited on a predetermined debit designation date.

[0103] In one embodiment of the present invention, the collection server divides the details of the deposits and withdrawals of the claimant's account into a plurality of groups for management and stores the data.

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

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

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

[0107] In one embodiment of the present invention, the collection server receives the 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 collection server, the method including: receiving billing data indicating the amount to be billed to a payer from a claimant terminal; transmitting the billing data to the payer's payer terminal; receiving a payment request for the billing data from the payer terminal; and requesting a server such as an immediate account transfer server to immediately debit the amount to be billed from the payer's account and credit the claimant's account. In one embodiment of the present invention, the debit may be made not immediately but on a predetermined debit designated date.

[0109] In one embodiment of the present invention, there is provided a collection system including a collection server, a claimant terminal, and a payer terminal. The collection server receives billing data indicating the amount to be billed to a payer from the claimant terminal, transmits the billing data to the payer's payer terminal, receives a payment request for the billing data from the payer terminal, and requests a server such as an immediate debit server to immediately debit the amount to be billed from the payer's account and credit the claimant's account. In one embodiment of the present invention, the debit may be made not immediately but on a predetermined debit designated date.

[0110] In one embodiment of the present invention, there is provided a program for causing a payer terminal to execute processes including: receiving billing data indicating the amount to be billed to a payer from a collection server; transmitting a payment request for the billing data to the collection server; and requesting the collection server to request a server such as an immediate debit server to immediately debit the amount to be billed from the payer's account and credit the claimant's account. In one embodiment of the present invention, the debit may be made not immediately but on a predetermined debit designated date.

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

Explanation of Reference Numerals

[0112] 1 Collection system 10 Collection server 20 Claimant terminal 21 Claimant 30 Payer Terminal 31 Payer 40 Immediate Debit Server 50 Accounting System 101 Claim Data Acquisition Unit 102 Claim Notification Unit 103 Payment Request Acquisition Unit 104 Immediate Debit Request Unit 105 Payment Management Unit 106 Account Registration Unit 107 Payer Account Information Storage Unit 108 Claimant Account Information Storage Unit 109 Collection Information Storage Unit 201 Registration Unit 202 Claim Data Notification Unit 203 Management Unit 301 Registration Unit 302 Claim Acquisition Unit 303 Payment Request Unit 304 Management Unit 1001 Control Unit 1002 Main Memory Unit 1003 Auxiliary Memory Unit 1004 Input Unit 1005 Output Unit 1006 Interface Unit

Claims

1. A claim data acquisition unit that receives claim data indicating the amount to be claimed from the claimant terminal; A claim notification unit that transmits the claim data to the payer terminal of the payer; A payment request acquisition unit that receives a payment request for the claim data from the payer terminal; An immediate debit request unit that requests an immediate debit server to immediately debit the claim amount from the payer's account and deposit it into the claimant's account; A collection server comprising the above.

2. A payer account information storage unit storing information on the payer's account; A claimant account information storage unit storing information on the claimant's account; The collection server according to claim 1, comprising the above.

3. The immediate debit request unit according to claim 2 transmits the claim amount, information on the payer's account, and information on the claimant's account to the immediate debit server. The collection server according to claim 2.

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

5. Receives information on the payer's account from the payer terminal; The collection server according to claim 1, comprising an account registration unit that requests the immediate debit server to register the payer's account.

6. A method executed by a collection server, comprising: Receiving claim data indicating the amount to be claimed from the claimant terminal; Transmitting the claim data to the payer terminal of the payer; Receiving a payment request for the claim data from the payer terminal; Requesting an immediate account transfer server to immediately debit the claim amount from the payer's account and deposit it into the claimant's account; A method including the above.

7. A collection system including a collection server, a claimant terminal, and a payer terminal, wherein The collection server A claim data acquisition unit that receives claim data indicating the amount to be claimed from the claimant terminal; A claim notification unit that transmits the claim data to the payer terminal of the payer; A payment request acquisition unit that receives a payment request for the claim data from the payer terminal; An immediate debit request unit that requests an immediate debit server to immediately debit the claim amount from the payer's account and deposit it into the claimant's account; A collection system comprising the above.

8. On the payer terminal, A process of receiving claim data indicating the amount to be claimed from the collection server; A process for causing the collection server to execute: sending a request for payment of the claimed data to the collection server and requesting the immediate debit server to immediately debit the claimed amount from the payer's account and deposit it into the claimant's account A program for executing the process.

Images