JP2025088002A - Bill collection server, method, bill collection system, and program - Google Patents

Abstract

[Problem] To improve the convenience of payments for collection services.
[Solution] A collection server in 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 deduction request unit that requests an immediate deduction server to immediately debit the billing amount from the payer's account and deposit it in the biller's account.
[Selected figure] Figure 2

Description

The present invention relates to a bill collection server, a method, a bill collection system, and a program.

Conventionally, there are known services that support the collection of fees at schools and other institutions. In such services, invoice data is obtained from a terminal at the school or other institution and notified to a terminal at the student's guardian or other person, after which payment is made.

Patent No. 7015082

However, with traditional collection support services, parents and guardians had to enter their credit card numbers or go to a convenience store to make payments.

Therefore, the present invention aims to improve the convenience of payment in collection services.

The bill collection server according to one embodiment of the present invention includes a billing data acquisition unit that receives billing data indicating the billing amount 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.

The present invention can improve the convenience of payment in collection services.

1 is a diagram showing an overall configuration according to an embodiment of the present invention; FIG. 2 is a functional block diagram of a bill collection server according to an embodiment of the present invention. 1 is an example of data stored in a payer account information storage unit according to one embodiment of the present invention. 1 is an example of data stored in a biller account information storage unit according to one embodiment of the present invention. 4 is an example of data stored in a bill collection information storage unit according to one embodiment of the present invention. FIG. 2 is a functional block diagram of a claimant terminal according to an embodiment of the present invention. FIG. 2 is a functional block diagram of a payer terminal according to an embodiment of the present invention. FIG. 4 is a sequence diagram of a bill collection process according to an embodiment of the present invention. FIG. 4 is a sequence diagram of an account registration process according to one embodiment of the present invention. 13 is an example of a screen displayed on a claimant terminal according to an embodiment of the present invention. 13 is an example of a transition of a screen displayed on a payer terminal according to an embodiment of the present invention. 13 is an example of detailed data of deposits and withdrawals by group for a claimant's account in one embodiment of the present invention. FIG. 2 is a hardware configuration diagram of a bill collection server according to an embodiment of the present invention.

<Terminology>
- As used herein, "collection" refers to the act of a biller collecting money from a payer.
In this specification, a "biller" is a person who bills a payer for money. For example, a biller may be a local government or a corporation that operates an elementary school, a junior high school, a high school, a university, a vocational school, a nursery school, a kindergarten, a cram school, various classes, a sports club, etc., but is not limited to these.
In this specification, a "payer" is a person who pays money to a biller. For example, a payer may be a guardian of a student or a kindergartener at an elementary school, a junior high school, a high school, a university, a vocational school, a nursery school, a cram school, a variety of classes, a sports club, etc., but is not limited to these.

The following describes an embodiment of the present invention based on the drawings.

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

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 is described below.

<<Collection Server>>
The bill collection server 10 receives billing data indicating the bill amount 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 deduction server 40 to immediately debit the billing amount from the account of the payer 31 and deposit it into the account of the biller 21. The bill collection server 10 is composed of one or more computers. Note that in this disclosure, the functions of the bill collection server 10 will be described while showing a mode of cooperation with the real-time deduction 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 deduction server 40.

<<Biller 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.

<<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.

<<Instant Withdrawal Server>>
The immediate withdrawal server 40 (when not immediate, simply referred to as the withdrawal server) causes the accounting system 50 of each financial institution such as a bank to execute immediate withdrawal. The immediate withdrawal server 40 is composed of one or more computers. Note that, although the function of the bill collection server 10 according to the present invention is explained in cooperation with the immediate withdrawal server 40, the bill collection server 10 can be appropriately linked with the function as long as it is a server having a function of issuing commands to the accounting system.

<<Accounting system>>
The accounting system 50 is an accounting system installed in each bank or other financial institution. The accounting system 50 is made up 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).

<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 will be described with reference to FIG. 6, and the functional configuration of the payer terminal 30 will be described with reference to FIG.

<<Collection Server>>
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 includes a billing data acquisition unit 101, a billing notification unit 102, a payment request acquisition unit 103, an immediate withdrawal 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. 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 withdrawal request unit 104, the payment management unit 105, and the account registration unit 106 by executing a program.

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.

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 can be displayed on a communication network application between the school etc. and the student's guardian etc., or a link to the web can be sent via SMS (Short Message Service) or email).

The payment request acquisition unit 103 receives a request for payment of billing data (specifically, 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).

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

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 payer 31's account and crediting to the biller 21's account) from the immediate deduction server 40.

The account registration unit 106 receives the account information of the payer 31 from the payer terminal 30, and requests the immediate withdrawal server 40 to register the account of the payer 31. For example, the account registration unit 106 can receive the 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 guardian etc., or a link to the web may be notified by SMS (Short Message Service) or email).

The payer account information storage unit 107 stores information about the account of the payer 31. Note that the account information of the payer 31 is assumed to have been registered in advance (as will be explained later with reference to FIG. 9).

The claimant account information storage unit 108 stores information about the account of the claimant 21. Note that the account information of the claimant 21 is assumed to have been registered in advance.

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.

Figure 3 is 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."

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

For example, "payer account information" includes the bank name, branch name, account number, etc.

Figure 4 is 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."

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

For example, "claimant's account information" would be the bank name, branch name, account number, etc.

Figure 5 is an example of data stored in the billing information storage unit 109 according to one embodiment of the present invention. The billing 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".

The "billing data ID" is an identifier assigned to each piece of billing data.

"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.

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

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

"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.

<<Biller 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.

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

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

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

<<Payer terminal>>
7 is a functional block diagram of a payer terminal 30 according to one embodiment of the present invention. The payer terminal 30 comprises 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.

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

The billing acquisition unit 302 receives billing data indicating the amount billed to the payer 31 from the billing server 10.

The payment request unit 303 transmits a request for payment of the billing data received by the billing acquisition unit 302 to the billing server 10, and causes the billing server 10 to execute a request to the immediate withdrawal server 40 to immediately withdraw 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.

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

<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.

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

In step 101 (S101), the biller terminal 20 logs in to a service that supports bill collection operations and is provided by the bill collection server 10. Specifically, the biller 21 inputs information for identifying the biller (such as a biller ID) to 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.

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.

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

In step 103 (S103), the biller terminal 20 transmits the billing data entered in S102 and information for identifying the payer 31 to the bill collection server 10.

In step 104 (S104), the billing server 10 stores in the billing information storage unit 109 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 step 105 (S105), the bill collection server 10 transmits the billing data received in S103 to the payer terminal 30 of the payer 31 identified by the information for identifying the payer 31 received in S103.

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

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 display the identified account of the payer 31 on the payer terminal 30.

The bill collection server 10 refers to the bill collection information storage unit 109 to identify information for identifying the payer 31 of the billing data for which payment has been requested in S106. Next, the bill collection server 10 refers to the payer account information storage unit 107 to identify the account of the payer 31 linked to the information for identifying the identified 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 able to specify one of the multiple accounts in S106.

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.

In step 108 (S108), the bill collection server 10 requests the immediate withdrawal server 40 to immediately withdraw the bill amount from the payer 31's account and deposit it into the biller 21's account. Specifically, the bill collection server 10 transmits the bill amount, information about the payer 31's account, and information about the biller 21's account to the immediate withdrawal server 40.

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

In step 110 (S110), the accounting system 50 immediately debits the billing amount from the account of the payer 31. The billing amount immediately debited from the account of the payer 31 is then saved for a certain period of time at the 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.

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

In step 112 (S112), the immediate withdrawal server 40 transmits the immediate withdrawal result received in S111 to the bill collection server 10.

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

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

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

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

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 performing an immediate withdrawal. Specifically, the payer terminal 30 transmits the account information of the payer 31 entered in the payer terminal 30 (e.g., bank name, branch name, account number, etc.) to the bill collection server 10.

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

In step 203 (S203), the immediate withdrawal server 40 requests the accounting system 50 (specifically, the accounting system of the 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 withdrawal account when executing the immediate withdrawal. Specifically, the immediate withdrawal server 40 transmits the account information of the payer 31 received in S202 to the accounting system 50.

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

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

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).

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

Figure 10 is an example of a screen displayed on the claimant terminal 20 in one embodiment of the present invention.

The claimant 21 can input the claim data (specifically, the claim title (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 such as that shown in FIG. 10 displayed on the claimant terminal 20. After input, the total claim amount may be calculated and displayed.

On a screen like 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 is 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 by SMS (Short Message Service) or email).

After inputting information on a screen such as that shown in FIG. 10 displayed on the claimant terminal 20, the claimant 21 can select an invoice issue button or the like to transmit the claim data from the claimant terminal 20 to the bill collection server 10.

Figure 11 shows an example of a screen transition displayed on the payer terminal 30 in one embodiment of the present invention.

In step 1001 (S1001), a message is displayed on the home screen of the payer terminal 30 indicating 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 "Notify" on the screen of S1001, the process proceeds to step 1002.

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.

In step 1003 (S1003), information on the debit account when performing the immediate debit 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 debit may be performed after authentication.

In step 1004 (S1004), the billing data for which immediate withdrawal was performed in S1003 is displayed as paid in the payment list.

<Linkage with contact network applications>
In one embodiment of the present invention, the bill collection server 10 can link and manage information of the payer 31 (specifically, the student's name, grade, class, attendance number, etc.) managed by a communication network application between the school etc. and the student's guardian etc. with information of the payer 31 managed by the bill collection server 10 (specifically, account information, contact information (telephone number, email address, etc.) etc.). 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 account information, contact information, etc. Therefore, the communication network application can provide a service that supports bill collection operations without the need to manage personal information such as the payer's 31's account information and contact information.

＜Effects＞
Thus, in one embodiment of the present invention, the payer 31, such as a student's parent or guardian, can make a payment by instantly withdrawing the amount from a desired account that has been registered in advance.

<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 withdrawal date instead of immediate withdrawal.

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

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 (e.g., multiple groups such as each grade level, PTA, savings, etc.). When a withdrawal is made from each group (i.e., 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 and managed centrally by the biller 21, making it easier to manage passbooks and seals.

Figure 12 is an example of detailed deposit and withdrawal data by group for the account of a 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 a claimant 21 (e.g. a school) at a financial institution into multiple groups (e.g. a group for 1st year class 1 and a group for 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.

[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 claimant's 21 account (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.

<Hardware Configuration>
13 is a hardware configuration diagram of the bill collection server 10 according to an 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.

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.

The control unit 1001 is a processor (e.g., a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), etc.) that executes various programs installed in the auxiliary memory unit 1003.

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. 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 they are executed by the control unit 1001.

The auxiliary memory unit 1003 is an auxiliary memory device that stores various programs and information used when the various programs are executed.

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.

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

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

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 deduction may be made on a predetermined designated deduction date rather than immediately.

In one embodiment of the present invention, the bill collection server manages and stores the details of deposits and withdrawals from the biller's account in multiple groups.

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

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 withdrawal server.

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

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

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

In one embodiment of the present invention, a bill collection system is provided that includes a bill collection server, a biller terminal, and a payer terminal, in which the bill collection server receives billing data indicating the bill amount 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 may be debited on a predetermined designated deduction date rather than immediately.

In one embodiment of the present invention, a program is provided for causing a payer terminal to execute the following processes: receiving billing data indicating the amount billed to the payer from a bill collection server; sending 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 rather than immediately.

Although the embodiment has been described above, changes in form and details are possible without departing from the spirit and scope of the claims.

1 Collection system 10 Collection server 20 Claimant terminal 21 Claimant 30 Payer terminal 31 Payer 40 Real-time withdrawal server 50 Accounting system 101 Claim data acquisition unit 102 Claim notification unit 103 Payment request acquisition unit 104 Real-time withdrawal 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 (8)

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 deduction request unit that requests an immediate deduction server to immediately debit the bill amount from the payer's account and credit the bill amount to the biller's account. A payer account information storage unit in which information on the payer's account is stored;
a claimant account information storage unit in which information on the claimant's account is stored;
The bill collection server according to claim 1 . The bill collection server according to claim 2, wherein the immediate withdrawal request unit transmits the bill amount, the payer's account information, and the biller's account information to the immediate withdrawal server. The bill collection server according to claim 3, which is provided with a payment management unit that receives information on the success or failure of the payment from the immediate withdrawal server. 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 for requesting the immediate deduction server to register the payer's account. A method executed by a collection server, comprising:
receiving billing data from a biller terminal indicating an amount billed to a payer;
transmitting the billing data to a payer terminal of the payer;
receiving a request for payment of the billing data from the payer terminal;
requesting an instant credit server to immediately debit the payer's account and credit the biller's account for the bill amount. A bill collection system including a bill collection server, a biller terminal, and a payer terminal,
The bill collection server includes:
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 deduction request unit that requests an immediate deduction server to immediately debit the bill amount from the payer's account and credit it to the biller's account. At the payer terminal,
receiving billing data from the collection server indicating an amount billed to a payer;
A program for causing the bill collection server to execute a process of transmitting a request for payment of the billing data to the bill collection server and requesting the real-time deduction server to immediately debit the billing amount from the payer's account and deposit it in the biller's account.

Images