Method, system, program, recording medium, and server for supporting cost collection

Abstract

To promote price collection on the basis of interaction between a management server and a customer terminal.SOLUTION: Acquiring billing information from a customer management database, extracting customer information for each payment due date, notifying an information terminal of a customer of prompt information including the billing information, determining whether payment is made and whether the payment is made before the payment due date, and if the payment is made before the payment due date, generating reward information and notifying the information terminal of the customer of first prompt information including the reward information; When the payment information cannot be acquired, the number of overdue days from the payment due date is calculated, and when the number of overdue days exceeds a reference waiting period, message information prompting payment is generated with reference to the history information, second presentation information including the message information is notified to the information terminal of the customer, and billing information including the payment information and / or the number of notifications of the message information prompting payment and history information including a payment history associated with the billing are stored in the customer management database.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technology for supporting payment collection, such as billing a supplier of gas such as LPG (Liquefied Petroleum Gas). [Background technology]

[0002] When purchasing fuel gas or gas appliances from a retailer, gas users are required to pay by the billing due date. The retailer manages billing and bills gas users periodically. Regarding the collection of such payments, it is known that a server device applied to a payment collection system that collects payments from users on behalf of a service provider performs processing such as sending data indicating a payment reminder by email to the user's terminal device when it receives data indicating that the payment could not be debited from a financial institution (for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2011-108221 Summary of the Invention [Problem to be solved by the invention]

[0004] By the way, retailers that sell fuel gas and gas appliances regularly bill gas users for gas usage fees, and it has traditionally been the case that they treat the purchase prices of gas appliances in the same way. When payment of such invoices is delayed, a payment reminder must be issued. Traditionally, payment reminders have been issued by issuing a reminder letter and sending it by mail. Issuing such a reminder letter poses the problem of having to cover printing costs, sealing work, and postage costs. The inventor has come to the realization that, with regard to payment collection, it is essential to encourage payment, prevent payment delays, reduce the number of collection cases, while also making collection responses more efficient. Therefore, based on the above-mentioned problems or findings, an object of the present invention is to promote payment collection based on the dialogue between the management server and the customer terminal. [Means for solving the problem]

[0005] To achieve the above object, one aspect of the payment collection support method of the present invention includes the steps of: acquiring billing information associated with a payment due date from a customer management database; extracting customer information associated with the billing information for each payment due date; notifying presented information including the billing information to an information terminal of a customer identified by the customer information; determining whether payment has been made and whether the payment is due on or before the payment due date; and, if payment is due on or before the payment due date, generating reward information and notifying first presented information including the reward information to an information terminal of a customer identified by the customer information. The method includes a step of calculating the number of days of overdue from the payment due date when the payment information of the identified customer cannot be obtained; a step of generating message information urging payment by referring to history information in the customer management database when the number of days of overdue exceeds a standard waiting period, and notifying second presentation information including the message information to the information terminal of the customer identified by the customer information; and a step of storing history information in the customer management database in association with the customer information, the billing information including the payment information and / or the number of times the message information urging payment has been notified, whether or not there has been any payment related to the billing, and the payment history of whether or not the payment was made before the payment due date,

[0006] The payment collection support method further includes a step executed by the computer of determining whether or not there has been a response from the customer's information terminal when the payment information cannot be obtained, a step of determining whether or not the customer identified by the customer information has used gas when there has been no response from the customer's information terminal, and a step of notifying the information terminal of the customer identified by the customer information of the second presentation information including visit information when gas is not being used.

[0007] The payment collection support method further includes, on the information terminal of the customer, displaying information display screen information including inquiry button information on the display screen of the first presented information or the second presented information.

[0008] The payment collection support method further includes a step executed by the computer of notifying the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information when the elapsed time since notification of the message information exceeds a predetermined period.

[0009] In order to achieve the above object, according to one aspect of the payment collection support system of the present invention, the payment collection support system uses a computer and includes a memory unit that records a customer management database that stores billing information including payment information and / or the number of notifications of message information prompting payment, whether or not a payment related to the bill has been made, and payment history information including whether or not payment was made before the payment due date, in association with customer information; a server that retrieves at least the payment information from the memory unit and executes information processing for payment collection; and an information terminal that is associated with customer information representing a customer and communicates with a communication unit of the server, wherein the server retrieves billing information associated with the payment due date from the customer management database, extracts customer information associated with the billing information for each payment due date, and notifies the information terminal of the customer identified by the customer information of presentation information including the billing information. and determines whether payment has been made and whether the payment is made before the payment due date; if the payment is made before the payment due date, generates reward information and notifies first presented information including the reward information to the information terminal of the customer specified by the customer information; if the payment information of the customer specified by the customer information cannot be obtained, calculates the number of days overdue from the payment due date; if the number of days overdue exceeds a standard waiting period, generates message information urging payment by referring to history information in the customer management database, and notifies second presented information including the message information to the information terminal of the customer specified by the customer information; and stores in the customer management database, in association with the customer information, the billing information including the payment information and / or the number of times the message information urging payment has been notified, the presence or absence of payment related to the billing, and the payment history including whether the payment was made before the payment due date, in association with the customer information. In the payment collection support system, further, if the server is unable to obtain the payment information, it determines whether or not there has been a response from the customer's information terminal, and if there has been no response from the customer's information terminal, it determines whether or not the customer identified by the customer information has used gas, and if there has been no gas usage, it notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information. In the payment collection support system, the server further includes information presentation screen information for presenting inquiry button information in the first presentation information or the second presentation information notified to the information terminal of the customer. In the payment collection support system, further, when the elapsed time since notification of the message information exceeds a predetermined period, the server notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information.

[0010] In order to achieve the above object, according to one aspect of the program of the present invention, there is provided a program to be executed by a computer, the program comprising: a function of acquiring billing information associated with a payment due date from a customer management database; a function of extracting customer information associated with the billing information for each payment due date; a function of notifying an information terminal of a customer specified by the customer information of presented information including the billing information; a function of determining whether or not a payment has been made and whether or not the payment is made before the payment due date; a function of generating reward information and notifying an information terminal of a customer specified by the customer information of first presented information including the reward information if the payment is made before the payment due date; The computer executes the following functions: when it is not possible to obtain the payment information of the specified customer, calculate the number of days of overdue from the payment due date; when the number of days of overdue exceeds a standard waiting period, generate message information urging payment by referring to history information in the customer management database and notify the information terminal of the customer specified by the customer information of second presentation information including the message information; and store in the customer management database, in association with the customer information, history information including the payment information and / or the number of times the message information urging payment has been notified, whether or not there has been any payment related to the billing, and payment history whether or not the payment was made before the payment due date. The program further causes the computer to execute the following functions: a function to determine whether or not a response has been received from the customer's information terminal if the payment information cannot be obtained; a function to determine whether or not the customer identified by the customer information has used gas if there has been no response from the customer's information terminal; and a function to notify the information terminal of the customer identified by the customer information of the second presentation information including visit information if there has been no gas usage. The program further causes the computer to execute a function including presenting information presentation screen information that presents inquiry button information when notifying the customer's information terminal of the first presentation information or the second presentation information. The program further causes the computer to execute a function of notifying the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information when the elapsed time since notification of the message information exceeds a predetermined period.

[0011] To achieve the above object, one aspect of a recording medium of the present invention is a recording medium storing the program.

[0012] In order to achieve the above object, according to one aspect of the server of the present invention, a storage unit that records a customer management database that stores billing information including payment information and / or the number of notifications of message information prompting payment, whether or not a payment related to the billing has been made, and payment history information including whether or not the payment was made before the payment due date, in association with customer information, and a processing unit, wherein the processing unit obtains billing information associated with a payment due date from the customer management database, extracts customer information associated with the billing information for each payment due date, notifies an information terminal of the customer identified by the customer information of presentation information including the billing information, determines whether or not a payment has been made and whether or not the payment was made before the payment due date, and if the payment was made before the payment due date, If there is, incentive information is generated and first presentation information including the incentive information is sent to the information terminal of the customer identified by the customer information; if the payment information of the customer identified by the customer information cannot be obtained, the number of days overdue from the payment due date is calculated; if the number of days overdue exceeds a standard waiting period, message information urging payment is generated by referring to history information in the customer management database; second presentation information including the message information is sent to the information terminal of the customer identified by the customer information; and history information including the payment information and / or the number of times the message information urging payment has been sent, whether or not there has been any payment related to the bill, and payment history whether or not the payment was made before the payment due date is stored in the customer management database in association with the customer information. Furthermore, in the server, if the payment information cannot be obtained, the processing unit determines whether or not there has been a response from the customer's information terminal, and if there has been no response from the customer's information terminal, determines whether or not the customer identified by the customer information has used gas, and if there has been no gas usage, notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information. In the server, the processing unit further includes information presentation screen information for presenting inquiry button information in the first presentation information or the second presentation information notified to the information terminal of the customer. Furthermore, in the server, when the elapsed time since notification of the message information exceeds a predetermined period, the processing unit notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information. [Effects of the Invention]

[0013] According to the present invention, any of the following effects can be obtained. (1) In response to a bill, if payment is made by the due date, reward information representing a reward for the user is generated, and if payment is not made within a waiting period from the due date, reminder information is generated by notifying the customer terminal, thereby communicating with the user and encouraging payment, thereby making payment collection more efficient. (2) The payment collection procedure can be automated, simplifying manual processing. (3) This eliminates the need to print, seal, and mail collection letters, thereby reducing costs such as postage. (4) For information exchange, including information distribution, in this bill collection support, SNS (Social Networking Service), such as LINE (registered trademark) communication service, can be utilized. [Brief explanation of the drawings]

[0014] [Figure 1] 10 is a flowchart showing a payment collection support process according to the first embodiment. [Figure 2] FIG. 10 is a diagram showing timekeeping information from the billing date to the alert period. [Figure 3] 1 is a diagram showing a payment collection support system according to a first embodiment; [Figure 4] FIG. 1 is a diagram illustrating a customer database. [Figure 5] FIG. 10 is a diagram showing a billing database. [Figure 6] FIG. 10 is a diagram showing a payment collection history database. [Figure 7]FIG. 10 is a diagram showing a payment collection support system according to a second embodiment. [Figure 8] FIG. 2 is a diagram illustrating hardware of a management server and a management terminal. [Figure 9] FIG. 10 is a diagram showing a customer billing information screen. [Figure 10] FIG. 10 is a diagram showing a dunning customer extraction processing screen. [Figure 11] FIG. 10 is a diagram showing a demand letter output processing screen. [Figure 12] FIG. 10 is a diagram showing a reminder information display screen of a customer terminal. [Figure 13] FIG. 10 is a diagram showing a payment collection support sequence. DETAILED DESCRIPTION OF THE INVENTION

[0015] [First embodiment] Fig. 1 shows a payment collection support process according to the first embodiment. The configuration shown in Fig. 1 is an example, and the present invention is not limited to such a configuration. This payment collection support process includes generating customer information (S101), extracting customer information (S102), generating and notifying presented information (S103), managing payment (S104), determining payment (S105), determining the payment date (S106), generating and notifying presented information (S107), recording payment information (S108), determining the progress of unpaid payments (S109), calculating the number of days overdue (S110), determining the progress of the waiting period (S111), searching for payment collection history (S112), selecting message information (S113), generating and notifying presented information (S114), determining payment (S115), recording payment information (S116), confirming responses (S117), confirming gas usage (S118), generating and notifying alert information (S119), generating and notifying presented information (S120), and recording progress information (S121).

[0016] Creation of customer information (S101): The management server 4 creates a customer management database (DB) 10 and stores customer information in this customer management DB 10. This customer management DB 10 includes a customer DB 10-1, a billing DB 10-2, a billing collection history DB 10-3, etc. Billing information associated with the payment due date for billing is stored in the billing DB 10-2, etc. Extraction of customer information (S102): The management server 4 extracts customer information associated with billing information from the customer management DB 10 for each payment due date. Generation and notification of presentation information (S103): The management server 4 generates presentation information associated with the billing information and notifies this presentation information to the customer terminal 6 associated with the billing information. In other words, the management server 4 presents information to the customer associated with the billing information via the customer terminal 6. This presented information includes reward information that a reward will be awarded if payment is made by the payment due date.

[0017] Payment management (S104): The management server 4 determines whether the invoice amount has been paid, and performs information processing to prompt payment, such as counting the number of days overdue from the payment due date to the present time, and issuing reminders. Determining payment (S105): In this payment management, the management server 4 determines whether payment has been made based on the payment information and whether payment has been made based on the unpaid information. Determining the payment date (S106): The management server 4 acquires the payment information and determines whether the payment date is before the payment due date or has passed the payment due date. Generation and notification of presented information (S107): The management server 4 generates presented information for customers who have obtained payment information by the payment due date and notifies them of this presented information. The management server 4 generates reward information associated with the customer information of customers who have completed early payment. This reward information is included in the presented information and notified to the corresponding customer terminal 6. Recording of payment information (S108): The management server 4 records in the customer management DB 10 the presence or absence of early payment as currently acquired payment information.

[0018] Determining the progress of unpaid amounts (S109): The management server 4 determines whether the payment due date has passed. If the payment due date has not passed, the process returns to S105 and payment confirmation continues. Calculation of the number of days overdue (S110): If the payment due date has passed (YES in S109), the management server 4 calculates the number of days overdue from the payment due date to the present time. Determining whether the waiting period has elapsed (S111): The management server 4 determines whether the number of days of overdue payment has exceeded the waiting period. The waiting period is a grace period set from the day the overdue payment occurs until the day message information prompting payment is sent, and is set to, for example, about one week. Search for payment collection history (S112): The management server 4 searches the payment collection history DB 10-3 to obtain history information such as whether there is a history of past overdue payments. Selection of message information (S113): The management server 4 selects suitable message information from a plurality of pieces of message information, taking into consideration historical information such as past overdue history. Generation and notification of presentation information (S114): The management server 4 generates presentation information including overdue information and message information urging payment, and notifies the relevant customer terminal 6 of the information.

[0019] Determining whether payment has been received (S115): After notifying the presented information, the management server 4 determines whether payment has been received. This determination can be made using payment information or unpaid information. Recording of payment information (S116): If payment has been made (YES in S115), the management server 4 stores the payment information including the payment date in the customer management DB 10, and then ends this process. Confirmation of response (S117): If there is no payment even after the presented information is notified (NO in S115), it is confirmed whether there is a response from the corresponding customer terminal 6. Confirmation of gas usage (S118): If there is no response from the notified customer terminal 6 (NO in S117), the management server 4 confirms whether gas is being used.

[0020] Generation and notification of alert information (S119): If there is no gas usage (NO in S118), the management server 4 generates alert information to call for a patrol visit to the customer's home, and presents this alert information to the information presentation unit 78 (FIG. 7) on the management server 4 side. The notification of this alert information triggers a manager, such as a dealer, to visit the customer's home. Generation and notification of presentation information (S120): In addition to generating and notifying the alert information, the management server 4 generates presentation information including the visit information and notifies the relevant customer terminal 6 of it. Recording of progress information (S121): After notifying the customer terminal 6 of the presented information, the management server 4 records the information acquired up to this point in the payment collection history DB10-3 and returns to S115. At this time, a reminder message and the number of reminders are recorded. Then, if there is a response from the customer terminal 6 (YES in S117) or if gas has been used (YES in S118), S119 and S120 are skipped, and after recording of progress information (S121), the process returns to S115.

[0021] <Payment deadline, reward period, waiting period, message period and alert period> The management server 4 sets the payment deadline (A in Figure 2), reward period (B in Figure 2), waiting period (C in Figure 2), message period (D in Figure 2), and alert period (E in Figure 2), and manages each period. Payment deadline: The payment deadline is usually the period from the billing date to the payment due date, as shown in A of Figure 2. The management server 4 acquires billing information including the billing date and the payment due date.

[0022] Reward period: As shown in Figure 2B, the reward period is set as the period during which rewards are received for payments. When the management server 4 acquires billing information, it sets the period from the billing date to the payment due date as the reward period for generating and notifying reward information. In other words, if payment information is acquired during the period from the billing date to the payment due date, reward information such as point redemption will be generated for the customer associated with this payment information. This reward information is an example of incentive information.

[0023] Waiting period: If payment information is not obtained, a waiting period is set. As shown in C of Figure 2, this waiting period begins on the day after the payment due date and ends on the start date of the message period during which message information is generated and notified. During the waiting period, the management server 4 waits for payment information to be obtained and does not generate message information. Message period: As shown in D of Fig. 2, the message period is the period after the waiting period during which message information prompting payment is generated and notified. If payment information is not obtained, the management server 4 sets a certain period after the waiting period as the message period, and generates and notifies message information during this period. Alert period: As shown in E of Figure 2, the alert period is the period after the message period in which alert information for payment reminders is generated and notified, and presentation information including an alert is generated and notified to the customer terminal 6. If the payment information is not obtained, the management server 4 generates presentation information including alert information and notifies the relevant customer terminal 6. This alert information includes visit information instructing a visit to the customer's home.

[0024] <Offer information, reward information, messages and alerts> Presentation information: When the management server 4 extracts the customer information related to the billing information, it notifies the customer terminal 6 related to the customer information of the presentation information including the billing information. This presentation information includes: a) Reward information that provides a reward if payment is made by the due date b) Message information to encourage payment in the event of overdue payments c) If payment is overdue even after notification of message information, alert information including visits will be included.

[0025] Reward information: The management server 4 notifies the customer terminal 6 of presentation information including reward information that corresponds to the customer who has met the conditions for obtaining the reward information. The reward content may be, for example, points that correspond to the amount of the invoice. Message and message pattern: The message is that the payment is overdue and message information urging the payment.

[0026] The message pattern will take into consideration the payment delinquency status and payment collection history, d) Amount of the invoice e)Dunning f) Supervision visits Select the pattern. Alert: If payment is not made even after receiving the message notification, the management server 4 generates and notifies alert information. This alert information includes information instructing the execution of a monitoring visit.

[0027] <Payment collection support system 2> Fig. 3 shows the payment collection support system 2. The configuration shown in Fig. 3 is an example, and the present invention is not limited to such a configuration. This payment collection support system 2 includes a management server 4 and multiple customer terminals 6 (=6-1, 6-2, ..., 6-N), and the management server 4 and each customer terminal 6 are connected to a network 8 via a wired or wireless connection. The management server 4 is provided with a customer management DB 10. This customer management DB 10 includes a customer DB 10-1, a billing DB 10-2, a payment collection history DB 10-3, and the like. The customer terminal 6 is an information terminal such as a fixed telephone, a mobile phone, a smartphone, etc. The network 8 is, for example, a public line network.

[0028] <Information processing on Management Server 4> Management Server 4 information processing a) Creation and recording of customer information, billing information, and payment collection history information b) Extraction of customer information related to payment deadlines C) Payment deadline management, payment management d) Creation and notification of various types of presentation information E) Recording of payment information and payment collection history F) Confirmation of response from customer terminal 6 G) Alert generation and notification This includes processing such as:

[0029] <Customer DB10-1> 4 shows an example of the customer DB 10-1. This customer DB 10-1 is a source of customer information and stores registration information about customers. This customer DB 10-1 is organized into multiple customer information files 12 (=12-1, 12-2, ..., 12-N). Each customer information file 12 has a customer information section 14, a consumption information section 16, an appliance information section 18, and a history information section 20. The customer information section 14 is set with a customer name section 14-1, an address section 14-2, a terminal information section 14-3, etc. The customer name section 14-1 stores identification information such as the name to identify the customer. The address section 14-2 stores information such as the customer's location, address, and whereabouts. The terminal information section 14-3 stores information on the customer terminal 6 associated with the customer information.

[0030] The consumption information section 16 is configured with a type section 16-1, a billing information section 16-2, a payment information section 16-3, etc. The type section 16-1 stores billing types such as gas usage fees and appliance fees. The billing information section 16-2 stores billing information such as purchase prices and purchase dates. The payment information section 16-3 stores information related to payments such as payment amounts and payment dates. The appliance information section 18 stores appliance information such as appliances used in the customer's home and their purchase dates. The history information section 20 stores history information related to customer information, such as various purchase histories and maintenance histories.

[0031] <Claim DB10-2> 5 shows an example of the billing DB 10-2. The billing DB 10-2 is an information source for billing for each customer, and stores registered information related to billing for each customer. This billing DB 10-2 is organized into a plurality of billing information files 22 (=22-1, 22-2, . . . , 22-N). Each billing information file 22 has a customer information section 24, an inspection date information section 26, a billing date information section 28, a payment due date information section 30, a billing information section 32, and a payment information section 34.

[0032] The customer information section 24 stores customer information in the same way as the customer information file 12. The inspection date information section 26 stores inspection date information for gas appliances and the like installed in the customer's home. The billing date information section 28 stores billing date information indicating the billing date for payment associated with the customer information. The payment due date information section 30 stores payment due date information indicating the payment due date for each billing date. The fee information section 32 stores fee information such as gas usage fees and appliance fees that form the basis for billing. The payment information section 34 stores information related to payments, such as the payment date for the billed fee and any outstanding payments.

[0033] <Payment collection history DB10-3> 6 shows an example of the payment collection history DB 10-3. This payment collection history DB 10-3 is, for example, a payment collection information source created for each customer information associated with unpaid payment invoice information, and stores registration information related to payment collection for each customer. This payment collection history DB 10-3 is organized into a plurality of payment collection history information files 36 (=36-1, 36-2, . . . , 36-N). Each payment collection history information file 36 has a customer information section 38, a billing date information section 40, a payment due date information section 42, a payment information section 44, an unpaid information section 46, and a history information section 48.

[0034] The customer information section 38 stores customer information similar to the customer information file 12 or the billing information file 22. The billing date information section 40 stores information relating to the billing date. The payment due date information section 42 stores information indicating the payment due date corresponding to the billing date. The payment information section 44 has a pre-deadline information section 44-1, a waiting period section 44-2, a post-message notification information section 44-3, and a post-alert notification information section 44-4. The pre-deadline information section 44-1 stores information such as whether or not a payment has been made before the payment due date and the payment date. The waiting period section 44-2 stores information such as information on when a payment has not been received and has entered the waiting period, and information on payments. The post-message notification information section 44-3 stores information such as message notifications and payments made after the notifications. The post-alert notification information section 44-4 stores information such as alert notifications and payments made after the notifications. Information indicating unpaid amounts is stored in the unpaid information section 46. History information section 48 stores history information such as payments made to bills associated with customer information.

[0035] <Advantages of the First Embodiment> According to the first embodiment, one of the following effects can be obtained. (1) By presenting information including reward information after the billing date, payment can be encouraged, and payment collection can be promoted. (2) In the event of a late payment, the system can encourage payment by communicating with the customer, such as by sending a message notification, a reminder notice, or providing information about the customer's visit. (3) The administrator can quickly process payment collections by using the management server 4 to process information, provide information, and issue alerts, and can automatically recognize the collection stage.

[0036] Second Embodiment Figure 7 shows a payment collection support system 2 according to the second embodiment. The configuration shown in Figure 7 is an example, and the present invention is not limited to such a configuration. In Figure 7, parts that are common to Figure 3 are assigned common reference numerals. This payment collection support system 2 uses a computer as a support means and supports payment collection management by managers such as gas suppliers and gas sales companies through information processing. The payment collection support system 2 of this embodiment includes a gas management system 50, a network system 52, and a plurality of customer terminals 6.

[0037] The gas management system 50 is a computer system that belongs to a manager such as a gas supplier or gas retailer, and includes a management server 4 and a management terminal 54 . A customer DB 10-1, a billing DB 10-2, and a payment collection history DB 10-3 are stored in the management server 4. The management terminal 54 is an information presentation means of the management server 4 and is also used as an information input means. The network system 52 is a system that handles public information communication via a computer equipped with a communication function, and is linked to the network 8 (FIG. 3) described above. The network system 52 includes a management server 56.

[0038] <Hardware of Management Server 4 and Management Terminal 54> 8 shows an example of hardware of the management server 4 and the management terminal 54. The management server 4 is a computer with a communication function, and includes a processor 58, a storage unit 60, an information input / output unit (I / O) 62, a communication unit 64, and a timer 66. The processor 58 is an example of a processing unit that executes an OS (Operating System) and a payment collection support program stored in the storage unit 60. The storage unit 60 is an example of a recording medium that stores various programs used for supporting payment collection. The storage unit 60 uses storage elements such as a ROM (Read-Only Memory) and a RAM (Random-Access Memory).

[0039] The I / O 62 outputs and acquires various information under the control of the processor 58 . The communication unit 64 establishes wireless or wired communication with the management terminal 54, and also transmits and receives various information to and from various information devices and the network system 52 via wired or wireless connections under the control of the processor 58. The timer 66 measures the time from the billing date to the billing deadline, the waiting period, etc. under the control of the processor 58. This timer 66 may be configured as hardware, or may be configured to manage time using software.

[0040] The management terminal 54 is a computer with communication functions similar to the management server 4, and includes a processor 68, a memory unit 70, an I / O 72, a communication unit 74, an information input unit 76, and an information presentation unit 78. The processor 68, the memory unit 70, the I / O 72, and the communication unit 74 have the same functions as the management server 4, and therefore their explanation will be omitted. The information input unit 76 is used to input information to the management server 4. The information presentation unit 78 is used to present information from the management server 4 and to notify alert information.

[0041] <Customer billing information screen 80> 9 shows a screen for customer billing information. This customer billing information screen 80 is presented on the information presentation unit 78 of the management terminal 54 and is used when registering customer billing information. This customer billing information screen 80 includes a title section 82 , an identification information section 84 , and a customer billing information section 86 . The title section 82 presents title information representing customer billing information. The identification information section 84 stores and presents identification information such as a code or name for identifying the customer. The customer billing information section 86 stores and presents information relating to payment bills, such as the customer closing date and the scheduled collection date.

[0042] <Dunning customer extraction processing screen 90> 10 shows an extraction processing screen 90 for dunning customers. This extraction processing screen 90 is displayed on the information presentation unit 78 of the management terminal 54. In addition to a title section 92, the extraction processing screen 90 includes an extraction condition section 94 for presenting extraction conditions and target customers to be extracted, a target customer section 96, a print designation section 98, and the like. The title section 92 presents title information indicating the extraction process of the dunning customer. The extraction condition section 94 includes a dunning condition information section 100. The dunning condition information section 100 stores and presents extraction condition information such as the processing month and closing date.

[0043] <Dunning Notice Output Processing Screen 102> 11 shows an output processing screen 102 for a reminder. This output processing screen 102 is output information presented from the management server 4 to the management terminal 54. This output processing screen 102 includes a title section 104, a processing information section 106, and the like.

[0044] <Information presentation to customer terminal 6> 12 shows information presented to the customer terminal 6. This information presentation screen 108 is presented information presented to the customer terminal 6 from the management server 4.

[0045] This information presentation screen 108 includes a distribution date information section 110, a presentation information section 112, and the like. The distribution date information section 110 stores and presents distribution date information, and "today" representing the distribution date information indicates that the information was distributed on the notification day. The presented information unit 112 stores, as an example of presented information, H) Billing date K) Unpaid J) Unpaid amount K) Non-payment risk etc. are presented. In order to facilitate quick communication with customers, an inquiry button 114 is provided at the bottom of the information presentation screen 108, and guide information is displayed on the customer terminal 6 encouraging the customer to contact a manager such as a gas supplier or gas sales company by phone.

[0046] <Payment collection support sequence> 13 shows a payment collection support sequence, in which information is exchanged between the management server 4, the management terminal 54, and the customer terminal 6. The management server 4 generates customer information (S201), extracts the customer information (S202), generates presentation information, and notifies the relevant customer terminal 6 through the management terminal 54 (S203). The customer terminal 6 presents the provided information (S204).

[0047] The management server 4 manages payments (S205), determines payments (S206), and determines the payment date (S207), and generates presentation information including reward information for customers who have obtained payment information by the payment due date, and notifies the management terminal 54 and the relevant customer terminal 6 (S208). The customer terminal 6 presents the information provided by the management server 4 (S209). The management server 4 records payment information (S210), determines the progress of unpaid payments (S211), calculates the number of days overdue (S212), determines the progress of the waiting period (S213), searches for payment collection history (S214), and selects message information (S215). The management server 4 then generates presentation information and notifies the management terminal 54 and the corresponding customer terminal 6 (S216). The customer terminal 6 presents the provided information (S217). The presentation information generated by the management server 4 may be notified to the customer terminal 6 via the management terminal 54.

[0048] The management server 4 determines whether or not payment has been made (S218) and records the payment information (S219). At this point, it is expected that a response notification will arrive from the customer terminal 6 (S220). The management server 4 confirms the response from the relevant customer terminal 6 (S221), and confirms the gas usage of the relevant customer (S222). The management server 4 generates alert information including information about visits to customer homes where there is no response (NO in S221) and no gas usage (NO in S222), and notifies the management terminal 54 of the alert information (S223). After notifying the alert information, the management server 4 generates presentation information and notifies the management terminal 54 and the customer terminal 6 of this presentation information (S224). Upon receiving this notification, the customer terminal 6 presents presentation information including reminder information such as visit information (S225). This presentation information may also be notified to the customer terminal 6 from the management terminal 54. Then, the management server 4 records the progress information (S226).

[0049] <Advantages of the second embodiment> (1) The same effects as those of the first embodiment can be obtained, such as improved efficiency in payment collection through a series of information processing. (2) In supporting payment collection, communication services such as LINE (registered trademark) on social networking sites can be utilized for information exchange, including information distribution.

[0050] As explained above, the most preferred embodiment of the present invention has been described. However, the present invention is not limited to the above description. Various modifications and changes are possible for those skilled in the art based on the gist of the invention as set forth in the claims or disclosed in the detailed description. It goes without saying that such modifications and changes are included within the scope of the present invention. [Industrial Applicability]

[0051] According to the present invention, in relation to the collection of payments associated with customer information, a step-by-step collection process can be mechanically executed, including notifying message information, reminder information, and visit information, in addition to rewards for payments made before the due date, thereby speeding up the process, reducing the burden of collection of payments, and realizing more efficient collection of payments. [Explanation of symbols]

[0052] 2. Payment collection support system 4 Management Server 6, 6-1, 6-2, , 6-N Customer terminal 8 Network 10 Customer management DB 10-1 Customer DB 10-2 Billing DB 10-3 Payment collection history DB 12, 12-1, 12-2, 12-N Customer Information File 14 Customer Information Department 14-1 Customer Name Department 14-2 Address section 14-3 Terminal Information Section 16 Consumer Information Department 16-1 Category 16-2 Billing Information Section 16-3 Payment Information Section 18 Instrument Information Department 20 History Information Department 22, 22-1, 22-2, 22-N Billing information file 24 Customer Information Department 26 Inspection Date Information Department 28 Claim Date Information Department 30 Payment Due Date Information Section 32 Payment Information Department 34 Payment Information Section 36, 36-1, 36-2, 36-N Payment collection history information file 38 Customer Information Department 40 Claim Date Information Department 42 Payment Due Date Information Section 44 Payment Information Section 44-1 Deadline Information Section 44-2 Waiting Period 44-3 Post-Message Notification Information Section 44-4 Post-alert information section 46 Unpaid Information Department 48 History Information Department 50 Gas Management System 52 Network Systems 54 Management terminal 56 Management Server 58 processors 60 Storage section 62 Information input / output section (I / O) 64 Communications Department 66 Timer 68 processors 70 Storage section 72 I / O 74 Communications Department 76 Information input section 78 Information presentation section 80 Customer billing information screen 82 Title section 84 Identification information section 86 Customer Billing Information Department 90 Extraction processing screen 92 Title section 94 Extraction condition part 96 Target Customer Department 98 Print specification section 100 Dunning Conditions Information Department 102 Output Processing Screen 104 Title section 106 Processing Information Department 108 Information presentation screen 110 Distribution Date Information Department 112 Presentation Information Department 114 Contact Us Button

Claims

1. The computer executes retrieving billing information associated with a payment due date from a customer management database; extracting customer information associated with the billing information for each payment due date; a step of notifying the information terminal of the customer identified by the customer information of the presentation information including the billing information; determining whether payment has been made and whether payment is on or before the payment due date; If the payment is made on or before the due date, generating reward information and notifying the information terminal of the customer identified by the customer information of first presentation information including the reward information; a step of calculating the number of days of overdue payment from the payment due date when payment information of the customer identified by the customer information cannot be obtained; a step of generating message information prompting payment by referring to history information in the customer management database when the number of overdue days exceeds a standard waiting period, and notifying second presentation information including the message information to an information terminal of the customer identified by the customer information; a step of storing the billing information including the payment information and / or the number of times message information prompting payment has been sent, history information including whether or not a payment has been made related to the billing, and a payment history indicating whether or not the payment was made before the payment due date in the customer management database in association with the customer information; A payment collection assistance method, including:

2. Furthermore, the computer executes a step of determining whether or not there is a response from the customer's information terminal when the payment information cannot be acquired; If there is no response from the customer's information terminal, determining whether or not the customer specified by the customer information is using gas; If there is no gas usage, notifying the information terminal of the customer identified by the customer information of the second presentation information including visit information; The payment collection support method according to claim 1, comprising:

3. Furthermore, the computer executes 2. The payment collection support method according to claim 1, wherein the display screen of the first presented information or the second presented information on the customer's information terminal includes information display screen information including inquiry button information.

4. Furthermore, the computer executes A payment collection support method as described in claim 1, which includes a step of notifying the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information when the elapsed time since the notification of the message information exceeds a predetermined period.

5. A computer-based payment collection support system, a storage unit for recording a customer management database that stores billing information including payment information and / or the number of times message information prompting payment is notified, history information including whether or not a payment has been made in relation to the billing, and a payment history indicating whether or not the payment was made before the payment due date, in association with customer information; a server that acquires at least the payment information from the storage unit and executes information processing for payment collection; an information terminal associated with customer information representing a customer and communicating with a communication unit of the server; wherein the server obtains billing information associated with the payment due date from the customer management database, extracts customer information associated with the billing information for each payment due date, notifies presented information including the billing information to an information terminal of the customer specified by the customer information, determines whether payment has been made and whether the payment was made before the payment due date, and if payment was made before the payment due date, generates reward information and notifies first presented information including the reward information to the information terminal of the customer specified by the customer information, and if the payment information of the customer specified by the customer information cannot be obtained, A payment collection support system that calculates the number of days of overdue payment from the payment due date, and if the number of days of overdue payment exceeds a standard waiting period, generates message information urging payment by referring to historical information in the customer management database, notifies the information terminal of the customer identified by the customer information of second presentation information including the message information, and associates historical information including the billing information including the payment information and / or the number of times the message information urging payment has been notified, whether or not there has been a payment related to the billing, and the payment history indicating whether or not the payment was made before the payment due date, with the customer information and stores it in the customer management database.

6. Furthermore, the server, when unable to obtain the payment information, determines whether or not there has been a response from the customer's information terminal, and if there has been no response from the customer's information terminal, determines whether or not the customer identified by the customer information has used gas, and if there has been no gas usage, notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information.

7. The payment collection support system according to claim 5, further comprising: information presentation screen information for presenting inquiry button information in the first presentation information or the second presentation information notified to the customer's information terminal by the server.

8. Furthermore, the server notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information when the elapsed time since notification of the message information exceeds a predetermined period.

9. A program to be executed by a computer, A function for retrieving billing information associated with a payment due date from a customer management database; a function of extracting customer information associated with the billing information for each payment due date; a function of notifying the information terminal of the customer identified by the customer information of the presentation information including the billing information; a function for determining whether a payment has been made and whether the payment is made on or before the due date; a function of generating reward information and notifying a first presentation information including the reward information to an information terminal of a customer identified by the customer information if the payment is made before the payment due date; a function of calculating the number of days overdue from the payment due date when payment information of a customer identified by the customer information cannot be obtained; a function of generating message information urging payment by referring to history information in the customer management database when the number of overdue days exceeds a standard waiting period, and notifying second presentation information including the message information to an information terminal of the customer identified by the customer information; a function of storing in the customer management database, in association with the customer information, the billing information including the number of notifications of the payment information and / or message information prompting payment, history information including whether or not a payment related to the billing has been made, and a payment history indicating whether or not the payment was made before the payment due date; A program for causing the computer to execute the above.

10. Furthermore, if the payment information cannot be acquired, a function of determining whether or not there is a response from the information terminal of the customer; a function of determining whether or not a customer specified by the customer information is using gas when there is no response from the customer's information terminal; a function of notifying an information terminal of a customer identified by the customer information of the second presentation information including visit information when no gas is used; The program according to claim 9, for causing the computer to execute the steps of:

11. The program according to claim 9 further causes the computer to execute a function including presenting information presentation screen information that presents inquiry button information when notifying the customer of the first presentation information or the second presentation information.

12. The program of claim 9 further causes the computer to execute a function of notifying the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information when the elapsed time since the notification of the message information exceeds a predetermined period.

13. A recording medium storing the program according to any one of claims 9 to 12.

14. a storage unit for recording a customer management database that stores billing information including payment information and / or the number of times message information prompting payment is notified, history information including whether or not a payment has been made in relation to the billing, and a payment history indicating whether or not the payment was made before the payment due date, in association with customer information; a processing unit; the processing unit acquires billing information associated with the payment due date from the customer management database, extracts customer information associated with the billing information for each payment due date, notifies the information terminal of the customer identified by the customer information of presentation information including the billing information, determines whether payment has been made and whether the payment was made before the payment due date, generates reward information if the payment was made before the payment due date, and notifies the information terminal of the customer identified by the customer information of first presentation information including the reward information, if the payment information of the customer identified by the customer information cannot be obtained, calculates the number of days of overdue from the payment due date, and if the number of days of overdue exceeds a standard waiting period, generates message information urging payment by referring to history information in the customer management database, notifies the information terminal of the customer identified by the customer information of second presentation information including the message information, and stores the billing information including the payment information and / or the number of times the message information urging payment has been notified, history information including whether or not a payment has been made associated with the billing and a payment history indicating whether or not the payment was made before the payment due date, in association with the customer information, in the customer management database.

15. Furthermore, the processing unit, when the payment information cannot be obtained, determines whether or not there has been a response from the customer's information terminal, and when there has been no response from the customer's information terminal, determines whether or not the customer identified by the customer information has used gas, and when there has been no gas usage, notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information.

16. The server according to claim 14 , further comprising: the processing unit causing the first presentation information or the second presentation information notified to the information terminal of the customer to include information presentation screen information for presenting inquiry button information.

17. Further, the processing unit notifies the information terminal of the customer identified by the customer information of the second presentation information including visit information representing a visit to the customer identified by the customer information when the elapsed time since notification of the message information exceeds a predetermined period.

Images