JP2022171378A - School payment money collection support device, school payment money collection method, program, and school payment money collection support system - Google Patents

Abstract

To provide a technique for supporting efficient connection of school payment money.SOLUTION: A school payment money collection support device includes an interaction control part for controlling interaction with a protector terminal device owned by a protector for paying school payment money, a settlement control part for controlling settlement of the school payment money, and a re-withdrawal date determination part for acquiring a re-withdrawal desired date for the school payment money from the protector terminal device to determine a re-withdrawal date. The settlement control part requests withdrawal for the school payment money from a financial institution terminal device, receives information showing whether a financial institution succeeds in withdrawal of the school payment money as a response to the request, and the interaction control part notifies the protector terminal device of a withdrawal failure by using the interaction, and receives the re-withdrawal desired date from the protector terminal device in the case that the financial institution fails in the withdrawal of the school payment money on a prescribed withdrawal date.SELECTED DRAWING: Figure 1

Description

The present invention relates to a school payment collection support device, a school payment collection method, a program, and a school payment collection support system.

A long time ago, school fees such as school lunch fees were paid by handing cash directly to the staff, and the payment rate was very high. Currently, it is mainly collected by bank withdrawal.

Patent Literature 1 discloses a technique related to a member settlement system. Paragraph [0030] states, "Based on the billing information received from the claimant device 110, the member payment system 100 identifies the member to be billed, prepares the necessary notice, and then sends the member device of the given member. 120. The billing information notification can be, for example, an e-mail, a short mail, a push notification of an application for smartphones, or the like, and can include a URL, a QR code, or the like (for example, See FIG. 6)." Paragraph [0048] states, "Membership registration can be a method of registering as necessary, such as teaching material costs in school/student expenses."

JP 2018-77769 A

Non-payment of school fees has become a social problem, and improvement of the payment rate has become an issue. The technology disclosed in Patent Literature 1 does not prevent unpaid bills from occurring.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a technique for assisting efficient collection of school fees.

The present application includes a plurality of means for solving at least part of the above problems, and examples thereof are as follows.

In order to solve the above problems, a school payment collection support device according to one aspect of the present invention includes a dialogue control unit that controls dialogue with a guardian terminal device owned by a guardian who pays school fees, and a and a re-withdrawal date determination unit that obtains the desired re-withdrawal date of the school payment from the parent terminal device and determines the re-withdrawal date, wherein the payment control unit is a financial institution terminal The device is requested to withdraw the school tuition, and as a response to the request, the financial institution receives information indicating whether or not the withdrawal of the school tuition was successful. fails to withdraw the school tuition, using the dialogue, notifies the parent's terminal device that the withdrawal is impossible, and receives the desired re-withdrawal date from the parent's terminal device.

The school payment collection support device of the present invention includes a registration information reception unit that receives registration of personal information including credit card information of parents, and the payment control unit, when the number of unsuccessful withdrawals reaches a predetermined number, The credit card information may be used to settle the school payment.

The school payment collection support device of the present invention provides either a first unsuccessful withdrawal screen, which is notified when the number of unsuccessful withdrawals is less than a predetermined number, or a second unsuccessful withdrawal screen, which is notified when the number is greater than or equal to a predetermined number. , wherein the interaction control unit uses the number of failures to provide the notification with link information for either the first withdrawal impossible screen or the second withdrawal impossible screen It may be characterized by determining whether to include

The school payment collection support device of the present invention comprises a display information generation unit that generates display information for a re-withdrawal condition change screen to be sent to the parent terminal device when the financial institution fails to withdraw the school payment, The re-withdrawal condition change screen includes a desired date input area for receiving input of the desired re-withdrawal date, a payment method change receiving area for receiving a request for changing the payment method of the school payment, and a request for consultation regarding the school payment. and a consultation reception area.

The re-withdrawal condition change screen of the present invention may be characterized by including link information to a screen displaying information about the school attendance support system.

The re-withdrawal date determination unit of the present invention determines the desired re-withdrawal date as the re-withdrawal date when the number of guardians requesting the desired re-withdrawal date received from the guardian terminal device is equal to or greater than a predetermined number. , if the number is less than a predetermined number, a date other than the desired date for re-withdrawal is determined as a re-withdrawal date, and the dialogue control unit determines the re-withdrawal date determined by the debit date determination unit using the dialogue. It may be characterized by notifying the parent's terminal device.

When the number of guardians is less than the predetermined number, the re-withdrawal date determination unit of the present invention determines, among a plurality of candidate dates at predetermined intervals, which are candidate dates at regular intervals, A date later than the desired re-withdrawal date may be determined as the re-withdrawal date.

The school payment collection support device of the present invention comprises a storage unit for storing, for the guardian, a change history of the payment method of the school payment, or withdrawal history information including the accumulated number of withdrawal failures of the guardian; The control unit determines which of the first non-withdrawal screen and the second non-withdrawal screen is to be notified to the guardian terminal device, depending on whether the withdrawal history information satisfies a predetermined condition. may be characterized.

Claim 9
Further, in order to solve the above problems, a school payment collection method according to another aspect of the present invention uses a guardian terminal device possessed by a guardian who pays a school payment and a school payment collection support device. an application form collection procedure for collecting from the parent/guardian an application form for a service provided to a student, wherein the application form contains credit card information to be used for withdrawal in the event of non-payment; and the collection of the school payment. a card information acquisition procedure for the support device to acquire the credit card information; A success/failure information reception procedure for receiving information indicating whether or not the withdrawal has succeeded, and in the above-mentioned school payment collection support device, when the withdrawal of the school payment has failed a predetermined number of times, settlement using the above-mentioned credit card information is executed. The method is characterized by comprising: a card payment execution procedure; and a notification procedure for notifying the payment result in the card payment execution procedure using a dialog function with the guardian terminal device in the school payment collection support device.

Further, in order to solve the above problems, a program according to another aspect of the present invention is a program for causing a processing unit of a computer to execute a school payment collection support method, the program comprising: a guardian terminal device owned by a guardian who pays school fees a settlement control procedure for controlling settlement of school fees; and a re-withdrawal date for determining a re-withdrawal date by acquiring a desired date for re-withdrawal of said school fees from said guardian terminal device. and, in the settlement control procedure, requesting the financial institution terminal device to withdraw the school payment, and in response to the request, information indicating whether or not the financial institution has successfully withdrawn the school payment. and in the dialogue control procedure, if the financial institution fails to withdraw the school payment on a predetermined withdrawal date, the dialogue is used to notify the guardian terminal device that the withdrawal is impossible, and the guardian terminal It is characterized by receiving the desired re-withdrawal date from the device.

Further, in order to solve the above problems, a school payment collection support system according to another aspect of the present invention includes a guardian terminal device owned by a guardian who pays a school payment, a financial institution terminal device owned by a financial institution, and the protection and a school payment collection support device communicably connected to the financial institution terminal device, wherein the school payment collection support device communicates with the parent terminal device. a settlement control unit for controlling settlement of the school payment; and a re-withdrawal date determination unit for acquiring the desired date for re-withdrawal of the school payment from the parent terminal device and determining the re-withdrawal date. wherein, in response to a request for withdrawal of the school payment from the school payment collection support device, the financial institution terminal device transmits information indicating whether or not the withdrawal of the school payment has succeeded to the school payment collection support device. the guardian terminal device has an output unit for displaying the contents of dialogue with the school payment collection support device, and the dialogue control unit of the school payment collection support device When the financial institution fails to withdraw the school fee, the communication is used to notify the parent's terminal device that the withdrawal is impossible, and the desired date for re-withdrawal is received from the parent's terminal device. do.

According to the present invention, efficient collection of school fees can be supported.

Problems, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

1 is an example of a functional block diagram of a bookkeeping device; FIG. It is a figure which shows an example of the data structure of personal registration information. It is a figure which shows an example of the data structure of regular withdrawal information. It is a figure which shows the hardware structural example of a school payment collection|recovery support apparatus. It is a flow chart which shows an example of withdrawal processing. FIG. 11 is a flowchart showing an example of re-withdrawal information change processing; FIG. It is a figure which shows an example of the data structure of re-withdrawal information. It is a figure which shows an example of an application form. It is a figure which shows an example of a withdrawal completion screen. It is a figure which shows an example of the 1st withdrawal impossible screen. It is a figure which shows an example of the 2nd withdrawal impossible screen. It is a figure which shows an example of a re-withdrawal condition change screen. It is a figure which shows an example of a school attendance support information screen. It is a flow chart which shows an example of credit payment processing. It is a figure which shows an example of a card settlement success notification screen. It is a figure which shows an example of a card payment failure notification screen. It is a figure which shows an example of the withdrawal process in a 1st modification. FIG. 11 is a flow chart showing an example of withdrawal date determination processing in a second modified example; FIG. It is a figure which shows an example of a re-withdrawal date notification screen. FIG. 10 is an image diagram showing an outline of re-withdrawal date determination processing using fixed-interval candidate dates.

The outline of the present invention will be described below based on the drawings. FIG. 1 is an example of a functional block diagram of a school payment collection support system 1. As shown in FIG. The school payment collection support system 1 includes a school payment collection support device 10, a guardian terminal device 20 owned by a guardian who pays the school payment, and a bank terminal device 30 owned by a bank. , the guardian terminal device 20 and the bank terminal device 30 are connected via a network X so as to be able to communicate with each other. For example, the school payment collection support system 1 has one school payment collection support device 10 , a plurality of guardian terminal devices 20 , and one or a plurality of bank terminal devices 30 .

The school payment collection support device 10 is an information processing device such as a server device or a PC (Personal Computer), and is owned by, for example, a company that provides a school payment collection support service. The school payment collection support device 10 supports the collection of the school payment from the guardian who has not paid the school payment. The guardian terminal device 20 is an information processing device such as a PC (Personal Computer), a smart phone, or a tablet. The bank terminal device 30 is an information processing device such as a server device or a PC (Personal Computer), and is a device owned by a financial institution for withdrawing school fees. The bank terminal device 30 may function as a financial institution terminal device and may be a device owned by a financial institution other than a bank.

The school payment collection support device 10 in this embodiment manages the payment of the school payment by the guardian, and supports the collection of the unpaid amount. As an example, parents pay school dues by debiting funds in a bank account. However, due to circumstances such as the guardian forgetting the debit date and there is no bank account balance for the school payment, or the payment cannot be made on the debit date for some reason.

In the event of arrears, it may be possible to make payment on a date that is convenient for the guardian. In addition, receiving public assistance may enable the payment of school fees. The school payment collection support device 10 in this embodiment supports the collection of school payment by responding to the needs of parents.

The school payment terminal device includes a processing section 110 , a storage section 120 , an input section 130 , an output section 140 and a communication section 150 . The processing unit 110 comprehensively controls the school payment collection support device 10 as a whole. The storage unit 120 stores information necessary for processing by the processing unit 110 . The input unit 130 receives input of information to the school payment collection support device 10 from an input device connected via the input IF 14, which will be described later. The output unit 140 outputs information stored in the school payment collection support device 10 from an output device connected via the output IF 15, which will be described later. The communication unit 150 mediates transmission and reception of information with other communicably connected devices.

The processing unit 110 includes a registration information reception unit 111, a dialogue control unit 112, a settlement control unit 113, a withdrawal information generation unit 114, a display information generation unit 115, a re-withdrawal date determination unit 116, and a consultation reception unit 117. And prepare.

The registration information reception unit 111 receives registration of personal information of parents or students (including children or students). The registration information reception unit 111 receives, for example, the input of credit card information of the guardian described in the application form, and registers it in the personal registration information 121 described later.

The dialogue control unit 112 controls dialogue with the guardian terminal device 20 . The dialogue control unit 112 executes dialogue using, for example, a direct message function of SNS (Social Networking Service). Note that the dialog control unit 112 may execute a dialog using a so-called SMS (Short Message Service) function that transmits and receives information using a telephone number. An example in which the school payment collection support device 10 and the guardian terminal device 20 interact via an SNS will be described below.

The dialogue control unit 112 uses dialogue to notify the guardian terminal device 20 of whether or not the bank has successfully withdrawn the school payment on the predetermined withdrawal date. As an example, the dialog control unit 112 notifies that withdrawal is impossible when the bank fails to withdraw the school fee. In addition, the dialog control unit 112 receives the desired re-withdrawal date input from the guardian terminal device 20 . The dialog control unit 112 uses dialog to notify the guardian terminal device 20 of the re-withdrawal date determined using the desired re-withdrawal date.

The settlement control unit 113 controls settlement of school fees. For example, the settlement control unit 113 requests the bank terminal device 30 to withdraw the school payment, and receives, as a response to the request, information indicating whether or not the bank has successfully withdrawn the school payment. In addition, the payment control unit 113 settles the school payment using the credit card information registered in the personal registration information 121 when the number of withdrawal failures reaches a predetermined number. That is, in that case, school fees are paid using a credit card.

The withdrawal information generation unit 114 generates withdrawal information and re-withdrawal information 124 for requesting the bank to withdraw the school fee.

The display information generation unit 115 generates display information for a screen displayed on the guardian terminal device 20 . For example, the display information generation unit 115 generates display information for a first withdrawal impossible screen 263A and a second withdrawal impossible screen 263B, which will be displayed on the guardian terminal device 20 when there is a non-payment. In addition, the display information generation unit 115 generates display information for a re-withdrawal condition change screen 264, which will be described later, to be transmitted to the guardian terminal device 20 when the bank fails to withdraw the school payment.

The re-withdrawal date determination unit 116 acquires the desired re-withdrawal date of the school payment from the guardian terminal device 20 and determines the re-withdrawal date. For example, the re-withdrawal date determining unit 116 determines the desired re-withdrawal date as the re-withdrawal date.

The consultation accepting unit 117 accepts a consultation request regarding payment of school fees from the guardian terminal device 20 . Upon receiving the consultation request, consultation reception unit 117 specifies the contact information of the guardian and notifies the contact information of the guardian to a predetermined notification destination. For example, the consultation receiving unit 117 notifies the parent's contact information to the school to which the student belongs and the board of education that targets the school.

The storage unit 120 stores personal registration information 121 , regular withdrawal information 122 , withdrawal result information 123 , re-withdrawal information 124 , notification information 125 , and withdrawal history information 126 .

The personal registration information 121 includes information about students and parents. For example, the personal registration information 121 includes the parent's credit card information as stated in the application form for the service. The periodic withdrawal information 122 is information about school payments that are periodically withdrawn from the parent's bank account. The withdrawal result information 123 is information obtained by the payment control unit 113 from the bank terminal device 30 and indicating whether or not the withdrawal of the school payment was successful.

The re-withdrawal information 124 is information about the school payment to be billed again to the guardian when the bank fails to withdraw the school payment. The re-withdrawal information 124 includes the number of unsuccessful withdrawals, which is the number of failures to withdraw school fees. The reminder information 125 is information about the school payment to be settled using the credit card information when the number of withdrawal failures reaches a predetermined number.

Withdrawal history information 126 is information about school fees that have already been withdrawn. The withdrawal history information 126 includes, in addition to the amounts of school fees that have been successfully withdrawn, for example, the total number of times the parents have failed to withdraw the fees, the change history of the payment method of the school fees, and the like.

The parent terminal device 20 includes a processing section 210 , an input section 230 , an output section 240 and a communication section 250 . The processing unit 210 centrally controls the whole guardian terminal device 20 . The input unit 230 receives input of information to the guardian terminal device 20 using an input device. The output unit 240 outputs information stored in the guardian terminal device 20 using an output device. The output unit 240 displays the content of the dialogue with the school payment collection support device 10 under the control of the dialogue control unit 211, which will be described later. The communication unit 250 mediates transmission and reception of information with other communicably connected devices.

The processing unit 210 includes a dialog control unit 211 and a re-withdrawal information change request unit 212 . The dialogue control unit 211 controls dialogue with the school payment collection support device 10 using SMS or SNS, for example, like the dialogue control unit 112 of the school payment collection support device 10 . The dialog control unit 211 displays, via the output unit 240, a message received from the school payment collection support device 10 or a message input by the guardian in the dialog.

The re-withdrawal information change request unit 212 requests the school payment collection support device 10 to change the re-withdrawal information 124 . For example, the re-withdrawal information change request unit 212 accepts an input operation from the parent regarding the change in each item displayed on the second withdrawal impossible screen 263B displayed when the withdrawal fails, and collects the school payment. A request to change the re-withdrawal information 124 including the input information is sent to the support device 10 .

The bank terminal device 30 includes a processing section 310 , an input section 330 , an output section 340 and a communication section 350 . The processing unit 310 centrally controls the bank terminal device 30 as a whole. The input unit 330 receives input of information to the bank terminal device 30 using an input device. The output unit 340 outputs information stored in the bank terminal device 30 using an output device. The communication unit 350 mediates transmission and reception of information with other communicably connected devices. In addition, the communication unit 350 transmits information indicating whether or not the school payment has been successfully withdrawn to the school payment collection support device 10 in response to the school payment withdrawal request from the school payment collection support device 10 .

The processing unit 310 includes a withdrawal request reception unit 311 and a withdrawal unit 312 . The withdrawal request reception unit 311 receives a withdrawal request for the school payment from the school payment collection support device 10 . The withdrawal unit 312 executes the withdrawal of the school payment from the guardian's financial institution account in response to the withdrawal request. The withdrawal unit 312 generates information indicating whether or not the withdrawal of the school fee was successful.

FIG. 2 is a diagram showing an example of the data structure of the personal registration information 121. As shown in FIG. Personal registration information 121 includes name 121a, department 121b, contact application 121c, account information 121d, and credit card information 121e. The name 121a is the name of the student. The affiliation 121b is information specifying the affiliation of the student. Note that the name 121a and the affiliation 121b may be identification information that can identify the student, and are not limited to the name and affiliation of the student.

The contact application 121c is information specifying software that the interaction control unit 112 uses for interaction with the guardian terminal device 20 . The account information 121d is information relating to the account of the guardian terminal device 20 in the software specified by the contact application 121c. The interaction control unit 112 can interact with the guardian terminal device 20 using the contact application 121c and the account information 121d.

Note that if the guardian terminal device 20 does not desire dialogue using software, the account information 121d may be a telephone number. The dialog control unit 112 can perform a dialog with the guardian terminal device 20 by SMS using a phone number.

The credit card information 121e is information relating to the credit card owned by the guardian from which school fees are withdrawn. The payment control unit 113 can settle the school payment using the credit card information 121e when the school payment cannot be withdrawn from the financial institution account.

FIG. 8 is a diagram showing an example of the application form 261. As shown in FIG. The application form 261 is a form for accepting applications for services such as school lunch fees, which are services provided by the school to the students and for which fees are charged to parents. The application form 261 has a card information entry field 261a for entering credit card information to be used for debiting school fees in the event of non-payment.

In the application form 261, a written oath indicating that payment will be made using the credit card information entered in the card information entry field 261a in the event of non-payment of a certain number of times or more is entered, and signed by a guardian. It is desirable to It is more desirable if this pledge is written in the application form 261 for a service, such as school lunch fees, which periodically charges the guardian. For example, for receivables that occur periodically, it is possible to determine whether or not it is necessary to withdraw from a credit card using the cumulative number of times that withdrawal is impossible.

FIG. 3 is a diagram showing an example of the data structure of the regular debit information 122. As shown in FIG. The regular debit information 122 includes a name 122a, an expense item 122b, an amount 122c, and a debit date 122d. The name 122a is information that identifies the student or guardian from whom school fees are collected. The expense item 122b is information indicating the expense item of the school payment. The amount 122c is information indicating the amount of the school payment. The withdrawal date 122d is information indicating the withdrawal date of the school payment.

FIG. 4 is a diagram showing a hardware configuration example of the school payment collection support device 10. As shown in FIG. The school payment collection support device 10 includes an arithmetic device 11, a memory 12, an external storage device 13, an input IF (Interface) 14, an output IF 15, a communication IF 16, and a storage medium drive device 17. The elements are connected by buses.

The arithmetic device 11 is an arithmetic device such as a CPU (Central Processing Unit), and executes processing according to a program recorded in the memory 12 or the external storage device 13 . In the school payment collection support device 10 , processing is performed by the computing device 11 that operates according to the program read out on the memory 12 or the external storage device 13 . Each processing unit that configures the processing unit 110 realizes each function when the arithmetic device 11 executes a program.

The memory 12 is a storage device such as RAM (Random Access Memory) or flash memory, and functions as a storage area from which programs and data are temporarily read. The external storage device 13 is a writable and readable storage medium such as a HDD (Hard Disk Drive), a CD-R (Compact Disc-Recordable), a DVD-RAM (Digital Versatile Disk-Random Access Memory), and a storage medium drive. equipment and the like. The function of the storage unit 120 is realized by the memory 12 or the external storage device 13 . Note that the function of the storage unit 120 may be realized by a storage device connected via the communication IF 16 .

The input IF 14 is an interface for receiving input operations from the operator, and is connected to input devices such as a touch panel, keyboard, mouse, and microphone. The output IF 15 is an interface for outputting information to a display device such as an LCD (Liquid Crystal Display) built in the school payment collection support device 10 .

The communication IF 16 is an interface for connecting the school payment collection support device 10 to the network X and bus, and is connected to a communication device such as a LAN (Local Area Network) card. The function of the communication unit 150 is realized by the communication IF 16 . A storage medium drive device 17 is a device for inputting/outputting information from a portable medium 18 such as a CD (Compact Disk) or a DVD (Digital Versatile Disk).

The processing of each component of the school payment collection assistance device 10 may be executed by one piece of hardware, or may be executed by a plurality of pieces of hardware. Further, the processing of each component of the school payment collection support device 10 may be realized by one program or may be realized by a plurality of programs.

Since the hardware configurations of the guardian terminal device 20 and the bank terminal device 30 are the same as those of the school payment collection support device 10, description thereof will be omitted.

FIG. 5 is a flowchart showing an example of withdrawal processing. This processing is executed for, for example, a single request included in the regular debit information 122, a request for which repayment is completed with a single payment, or a request for re-withdrawal that is performed after a debit cannot be debited. That is, the school payment collection support device 10 executes the processing of this flowchart for each information that can identify the bill, for example, the combination of the guardian and the expense item, or the combination of the guardian and the school payment amount.

More specifically, for example, the settlement control unit 113 transmits the regular debit information 122 to the bank terminal device 30, and out of the periodical school payment requests for debit, the debit is executed for one request. . Alternatively, the debit information generating unit 114 may generate debit information including the amount of the school payment for each debit date using the regular debit information 122, and the settlement control unit 113 may request the bank terminal device 30 to make the debit. can. In that case, the processing of this flowchart is executed for the billing related to the withdrawal information.

In addition, the withdrawal information generation unit 114 can also generate withdrawal information including the amount of the school payment that can be paid in one payment. Even in that case, the processing of this flowchart is executed for the billing related to the withdrawal information. In addition, the processing of this flowchart is executed for a request related to the re-withdrawal information 124 generated after the withdrawal is impossible. Generation of the re-withdrawal information 124 will be described later.

In addition, before starting this process, for example, the school collects the application form 261 containing the credit card information from the parent. Also, the school or the provider of the school payment collection support service inputs the credit card information described in the application form 261 into a terminal device (not shown). The school payment collection support device 10 acquires the inputted credit card information.

First, the settlement control unit 113 acquires the withdrawal result information 123 (step S11). Specifically, when the settlement control unit 113 of the school payment collection support device 10 requests withdrawal, the withdrawal request receiving unit 311 of the bank terminal device 30 receives the withdrawal request, and the withdrawal unit 312 executes the withdrawal. The withdrawal request receiving unit 311 generates information indicating whether the withdrawal is possible or not, and transmits the information to the school payment collection support device 10 . The settlement control unit 113 of the school payment collection support device 10 acquires the withdrawal result information 123, which is information indicating whether or not the withdrawal is possible, as a response to the request for withdrawal of the school payment.

Next, the settlement control unit 113 determines whether or not the withdrawal has been completed (step S12). When the payment control unit 113 acquires the withdrawal result information 123 indicating that the withdrawal was possible in step S11, the payment control unit 113 treats the withdrawal as having been completed.

When the settlement control unit 113 determines that the withdrawal has been completed ("YES" in step S12), the interaction control unit 112 notifies via the SNS that the payment has been completed normally (step S13).

FIG. 9 is a diagram showing an example of the withdrawal completion screen 262. As shown in FIG. The withdrawal completion screen 262 is a screen displayed on the guardian terminal device 20 and includes a message indicating that the withdrawal has been completed. As shown in FIG. 9, the withdrawal completion screen 262 may display the date and time when the withdrawal was completed and the amount of the school payment.

This screen may be displayed, for example, in the message column of the SNS, or may be displayed on the guardian terminal device 20 by accessing the link information displayed in the message column.

Returning to FIG. Next, if there is withdrawal information or re-withdrawal information 124 corresponding to the withdrawal result information 123, the withdrawal information generation unit 114 deletes the corresponding withdrawal information or re-withdrawal information 124 (step S14). Specifically, if there is a record of withdrawal information or re-withdrawal information 124 for a bill for which withdrawal has been completed in step S12, the withdrawal information generator 114 deletes the record of the withdrawal information or re-withdrawal information 124 . By deleting the information related to the completed billing, it is possible to prevent erroneous operations such as re-billing by mistake. After that, the processing unit 110 terminates the processing of this flowchart.

When the settlement control unit 113 determines that the withdrawal has not been completed (“NO” in step S12), the interaction control unit 112 determines whether the number of withdrawal failures is less than the first threshold. (Step S15). Specifically, the dialog control unit 112 identifies whether or not there is the re-withdrawal information 124 for the bill for which it is determined that the withdrawal has not been completed in step S12. When the re-withdrawal information 124 is present, the dialog control unit 112 determines whether or not the number of withdrawal failures included in the re-withdrawal information 124 is less than a first threshold, which is a predetermined number of times. Note that, when the re-withdrawal information 124 does not exist, the dialog control unit 112 determines that the number of times the withdrawal is impossible is less than the first threshold.

When the interaction control unit 112 determines that the withdrawal failure count is less than the first threshold (“YES” in step S15), the withdrawal information generation unit 114 increments the withdrawal failure count of the re-withdrawal information 124. (Step S16). Specifically, if the withdrawal information generation unit 114 determines in step S15 that there is no re-withdrawal information 124, it generates the re-withdrawal information 124 for the billing related to the withdrawal result information 123 received in step S11. Let the number of times be "1". Alternatively, if the withdrawal information generating unit 114 determines that the re-withdrawal information 124 exists in step S15, the withdrawal-withdrawal information generation unit 114 increments the withdrawal failure count of the re-withdrawal information 124 .

FIG. 7 is a diagram showing an example of the data structure of the re-withdrawal information 124. As shown in FIG. The re-withdrawal information 124 includes a name 124a, an amount 124b, a number of times 124c, a re-withdrawal date 124d, a payment method 124e, and a consultation contact information 124f.

The name 124a is information indicating the guardian or student of the billing destination that could not be withdrawn. The amount 124b is the amount of the school payment related to the claim that could not be withdrawn. The number of times 124c is the number of times that withdrawal is judged to be impossible. If the first withdrawal is impossible, the number of times 124c is "1". The re-withdrawal date 124d is information indicating the schedule for the next withdrawal of the bill that could not be withdrawn. In the present embodiment, the withdrawal date is predetermined, and the withdrawal information generation unit 114 uses the date of the billing that is determined to be unwithdrawable to identify the schedule set as the next withdrawal date. , is included in the redemption date 124d.

The payment method 124e is information specifying the payment method for the school payment for the next bill. In this embodiment, the first withdrawal is billed using a bank transfer, and re-billing for failure to withdraw less than a predetermined number of times is billed using a bank transfer in the same manner as the first withdrawal. That is, when the number of times 124c is "1", the payment method 124e is "bank transfer".

The consultation contact information 124f is information specifying the contact information of the parent or student who consulted when a request for consultation was received on the second withdrawal impossible screen 263B described later.

Returning to FIG. Next, the interaction control unit 112 transmits the first withdrawal failure screen 263A via the SNS (step S17). Specifically, display information generation unit 115 generates display information for first withdrawal impossible screen 263A. For example, the dialogue control unit 112 transmits the link information to the first withdrawal impossible screen 263A to the guardian terminal device 20 by including it in the SNS message. After that, the processing unit 110 terminates the processing of this flowchart. Note that the interaction control unit 112 may include the information included in the first withdrawal failure screen 263A in an SNS message and transmit it.

FIG. 10 is a diagram showing an example of the first withdrawal impossible screen 263A. The first withdrawal failure screen 263A includes a withdrawal failure message display area 263c and a re-withdrawal date display area 263d. The withdrawal impossible message display area 263c is an area for displaying a message indicating that the withdrawal was impossible. The non-withdrawable message display area 263c may include information indicating the item of expense and the billing period by which the non-withdrawable bill can be identified, information indicating the bank that made the billing, and the like. The re-withdrawal date display area 263d is an area for displaying the re-withdrawal date.

Returning to FIG. When the dialog control unit 112 determines that the number of withdrawal failures is not less than the first threshold ("NO" in step S15), the settlement control unit 113 determines whether the number of withdrawal failures is equal to or greater than the second threshold. (Step S18). Specifically, the settlement control unit 113 refers to the number of times 124c of the re-withdrawal information 124 used for determination in step S15, and determines whether the number of times the withdrawal is impossible is equal to or greater than a second threshold, which is a predetermined number of times. judge. Note that the second threshold is a numerical value larger than the first threshold.

When the settlement control unit 113 determines that the withdrawal failure count is not equal to or greater than the second threshold (“NO” in step S18), the withdrawal information generation unit 114 increments the withdrawal failure count of the re-withdrawal information 124 ( step S19). The withdrawal information generator 114 adds 1 to the number 124c of the re-withdrawal information 124 referred to in step S18.

Next, the dialogue control unit 112 transmits the second withdrawal impossible screen 263B via the SNS (step S20). For example, the dialogue control unit 112 transmits the SNS message to the guardian terminal device 20 by including the link information to the second withdrawal impossible screen 263B. Note that the interaction control unit 112 may include the information included in the second withdrawal failure screen 263B in an SNS message and transmit it. After that, the processing unit 110 terminates the processing of this flowchart.

FIG. 11 is a diagram showing an example of the second withdrawal failure screen 263B. The second withdrawal-impossible screen 263B includes link information 263e in addition to the withdrawal-impossible message display area 263c and re-withdrawal date display area 263d included in the first withdrawal-impossible screen 263A. The link information 263 is a hyperlink to a re-withdrawal condition change screen 264 for accepting changes in conditions for re-withdrawal, an address of a storage destination, and the like.

When the link information 263 e of the second withdrawal impossible screen 263 B displayed on the guardian terminal device 20 is selected, the display screen changes to the re-withdrawal condition change screen 264 . The re-withdrawal information change processing performed in accordance with the input operation to the re-withdrawal condition change screen 264 will be described later.

Returning to FIG. When the settlement control unit 113 determines that the number of withdrawal failures is greater than or equal to the second threshold ("YES" in step S18), the withdrawal information generation unit 114 generates notification information 125 (step S21). The notification information 125 includes information specifying the guardian of the billing destination and the billed amount that could not be withdrawn. After that, the processing unit 110 terminates the processing of this flowchart.

FIG. 6 is a flow chart showing an example of re-withdrawal information change processing. The re-withdrawal information change process is executed in accordance with an input operation to the re-withdrawal condition change screen 264 .

FIG. 12 is a diagram showing an example of the re-withdrawal condition change screen 264. As shown in FIG. The re-withdrawal condition change screen 264 includes a desired date input area 264a, a payment method change reception area 264b, a consultation reception area 264c, and school attendance support link information 264d. The desired date input area 264a is an area for receiving the specification of the schedule for which the guardian wishes to withdraw again. The payment method change acceptance area 264b is an area for accepting a request to change the payment method for school fees. In the payment method change acceptance area 264b, as payment methods that can be used for payment of school fees, for example, "convenience store payment" for paying at a convenience store, and "payment notice" for paying at a financial institution using a payment notice payment” etc. are displayed in a selectable manner.

The consultation reception area 264c is an area for receiving a request for consultation regarding school fees. Consultation reception area 264c receives input of contact information by parents. The school attendance support link information 264d is a hyperlink to a screen showing information related to school attendance support, a storage destination address, etc. When the school attendance support link information 264d is selected, the display screen transitions to the school attendance support information screen 265 described later. do.

By displaying the re-withdrawal condition change screen 264 on the guardian terminal device 20, the viewing guardian can simultaneously recognize that the payment schedule and payment method of the school fee can be changed. In addition, since parents can recognize that consultations regarding school fees are accepted, they can contribute to improving the payment rate by consulting about school fees that are difficult to pay. In addition, having access to information about school assistance helps parents decide whether they can get assistance with their school fees, increasing the likelihood of collecting arrears.

In FIG. 6, first, the interaction control unit 112 accepts an input operation on the re-withdrawal condition change screen 264 (step S31).

Next, the re-withdrawal date determining unit 116 determines whether or not the input operation received in step S31 is to change the withdrawal date (step S32). Specifically, when the desired date is entered in the desired date input area 264a of the re-withdrawal condition change screen 264, the re-withdrawal date determining unit 116 determines that the withdrawal date has been changed.

If the re-withdrawal date determination unit 116 determines that the withdrawal date has been changed (“YES” in step S32), the withdrawal information generation unit 114 changes the re-withdrawal date of the re-withdrawal information 124 (step S33). ). Specifically, the re-withdrawal date determining unit 116 determines the desired date input in the desired date input area 264a as the re-withdrawal date. The withdrawal information generation unit 114 records the determined re-withdrawal date as the re-withdrawal date 124d of the record of the record of the re-withdrawal information 124 in which the number of withdrawal failures is incremented in step S19 shown in FIG. After that, the processing unit 110 terminates the processing of this flowchart.

When the re-withdrawal date determination unit 116 determines that the withdrawal date has not been changed (“NO” in step S32), the settlement control unit 113 determines whether the payment method has been changed (step S34). . Specifically, when the payment method selection is received in the payment method change reception area 264b of the re-withdrawal condition change screen 264, the settlement control unit 113 determines that the payment method has been changed.

When the payment control unit 113 determines that the payment method is changed ("YES" in step S34), the payment control unit 113 determines whether or not payment is made at a convenience store (step S35). Specifically, the settlement control unit 113 determines whether or not “convenience store payment” is selected in the payment method change acceptance area 264 b of the re-withdrawal condition change screen 264 .

When the settlement control unit 113 determines that the payment is made at the convenience store ("YES" in step S35), the dialogue control unit 112 notifies the payment number via the SNS (step S36). Specifically, the payment control unit 113 issues a payment number that is used for payment at a convenience store. The dialogue control unit 112 notifies the guardian terminal device 20 of the payment number issued by the settlement control unit 113 via the SNS.

Next, the withdrawal information generator 114 changes the payment method of the re-withdrawal information 124 (step S33). Specifically, the withdrawal information generation unit 114 indicates that the payment method 124e of the record of the re-withdrawal information 124 in which the number of withdrawal failures has been incremented in step S19 shown in FIG. Record information. After that, the processing unit 110 terminates the processing of this flowchart.

When the settlement control unit 113 determines that the payment is not made at the convenience store ("NO" in step S35), the settlement control unit 113 outputs a payment slip (step S38). Specifically, the payment control unit 113 prints a payment slip used for payment. After that, the printed payment slip will be mailed to the guardian. Note that the dialogue control unit 112 may transmit screen information showing the payment slip to the guardian terminal device 20 via the SNS.

Next, the withdrawal information generator 114 changes the payment method of the re-withdrawal information 124 (step S39). Specifically, the withdrawal information generation unit 114 sets the payment method 124e of the record of the re-withdrawal information 124 for which the number of withdrawal failures has been incremented in step S19 shown in FIG. Record the information shown. After that, the processing unit 110 terminates the processing of this flowchart.

When the settlement control unit 113 determines that the payment method has not been changed (“NO” in step S34), the consultation reception unit 117 determines whether or not a request for consultation has been received (step S40). Specifically, consultation accepting unit 117 determines whether or not an input operation to consultation accepting area 264c of re-withdrawal condition change screen 264 has been accepted.

If the settlement control unit 113 determines that the request for consultation has been received (“YES” in step S40), the consultation reception unit 117 notifies the input contact information to the notification destination registered in advance (step S41). Specifically, consultation reception unit 117 notifies the parent's contact information entered in consultation reception area 264c to a predetermined notification destination such as a school or board of education.

Next, the withdrawal information generator 114 changes the consultation contact information in the re-withdrawal information 124 (step S42). Specifically, the withdrawal information generating unit 114 selects the consultation contact address 124f of the record for which the withdrawal failure count has been incremented in step S19 shown in FIG. Record parental contact information. After that, the processing unit 110 terminates the processing of this flowchart.

When the settlement control unit 113 determines that the consultation request has not been received (“NO” in step S40), the dialogue control unit 112 transmits school attendance support information (step S43). When an input operation to the re-withdrawal condition change screen 264 is accepted, if it is not an input operation to the desired date input area 264a, the payment method change acceptance area 264b, or the consultation acceptance area 264c, an input operation to the school attendance support link information 264d is performed. It is The dialogue control unit 112 transmits the display information of the school attendance support information screen 265 to the guardian terminal device 20 via the SNS. After that, the processing unit 110 terminates the processing of this flowchart.

FIG. 13 is a diagram showing an example of the school attendance support information screen 265. As shown in FIG. The school attendance support information screen 265 is a screen that displays information about the school attendance support system implemented by the national government and local governments. If the enrollment support system can be used, the burden of school fees will be reduced. Informing parents about the enrollment support system when school fees are in arrears provides an opportunity to consider the possibility of receiving benefits from the enrollment support system, thereby improving the possibility of collecting unpaid fees.

As described above, in the present embodiment, the dialog control unit 112 protects either the first withdrawal failure screen 263A or the second withdrawal failure screen 263B using the number of withdrawal failures (that is, the number of failures) and the first threshold. It determines whether or not to transmit to the user terminal device 20 . As a result, for example, for the first withdrawal failure that is likely to be a mere careless mistake, only the re-withdrawal date is notified by the first withdrawal failure screen 263A. , changes in the withdrawal date and payment method can be accepted on the second withdrawal impossible screen 263B. That is, by setting the first threshold according to the parents' tendencies, it is possible to promote more efficient payment of school fees.

In addition, in the past, it was difficult to ask parents about the payment date of school fees, so the school had to make payments according to a schedule unilaterally determined by the school. rice field. According to this embodiment, the payment date can be specified according to the parent's convenience, which contributes to the reduction of unpaid balance.

FIG. 14 is a flowchart showing an example of credit settlement processing. The processing of this flow chart is periodically executed in the school payment collection support device 10, for example.

First, the settlement control unit 113 identifies the target notification information 125 (step S51). Specifically, the settlement control unit 113 identifies one record of the reminder information 125 to be processed by credit card among the reminder information 125 generated in step S21 of FIG. Note that the notice information 125 includes the guardian or student to be billed and the amount billed.

Next, the settlement control unit 113 acquires credit card information (step S52). Specifically, the settlement control unit 113 refers to the personal registration information 121 using the notification information 125 specified in step S31, and acquires the credit card information 121e of the guardian or the like to be charged.

Next, the settlement control unit 113 executes credit settlement (step S53). The payment control unit 113 uses the credit card information acquired in step S32 to execute payment using a credit card for the target guardian. As a result, the payment control unit 113 acquires information indicating whether the payment using the credit card was successful. The information is, for example, payment information issued by a card company.

Next, the settlement control unit 113 determines whether or not the settlement has succeeded (step S54). Specifically, the payment control unit 113 determines whether or not the payment is successful using the information acquired as a result of the payment in step S33.

When the settlement control unit 113 determines that the settlement has succeeded ("YES" in step S54), the dialog control unit 112 notifies the success of the credit settlement via the SNS (step S55).

FIG. 15 is a diagram showing an example of a card settlement success notification screen 266. As shown in FIG. For example, as shown in FIG. 15, the card settlement success notification screen 266 displays the schedule and amount of credit card settlement. Note that the interaction control unit 112 of the school payment collection support device 10 may include the information shown on the card payment success notification screen 266 in an SNS message and transmit it to the guardian terminal device 20 . , a message including the link information of the card settlement success notification screen 266 may be sent.

Returning the description to FIG. Next, the settlement control unit 113 deletes the target notification information 125 (step S56). Specifically, the settlement control unit 113 deletes the notification information 125 specified as the processing target in step S31.

Next, the settlement control unit 113 deletes the withdrawal information and the re-withdrawal information 124 corresponding to the notification information 125 (step S57). Specifically, the settlement control unit 113 identifies and deletes the re-withdrawal information 124 corresponding to the record of the notice information 125 identified as the object in step S31. Also, if there is withdrawal information corresponding to the notification information 125, the payment control unit 113 deletes the withdrawal information. After that, the processing unit 110 terminates the processing of this flowchart.

When the settlement control unit 113 determines that the settlement has failed ("NO" in step S54), the dialog control unit 112 notifies the failure of credit settlement via the SNS (step S58).

FIG. 16 is a diagram showing an example of the card payment failure notification screen 267. As shown in FIG. The card settlement failure notification screen 267 includes a message indicating that the card settlement was unsuccessful. As shown in FIG. 16, the card payment failure screen may include link information for updating credit card information, for example.

Next, the settlement control unit 113 generates blacklist information when settlement is impossible for a predetermined number of times or more (step S59). Specifically, the payment control unit 113 uses the notification information 125 when it is determined in step S54 that the payment related to the record of the notification information 125 specified in step S51 has failed more than a predetermined number of times in step S54. to generate blacklist information. After that, the processing unit 110 terminates the processing of this flowchart.

According to the present embodiment, payment using a credit card can be efficiently performed when school fees cannot be withdrawn from a bank. Credit card payments have become more common due to the activation of commercial transactions using the Internet, and there is a possibility that social credibility will be lost if unpaid credit card payments occur. Therefore, collection of school fees using a credit card can contribute to the reduction of unpaid fees.

<First modification>
A first modification of the present embodiment will be described below. In the above-described embodiment, the dialog control unit 112 compares the number of withdrawal failures with the first threshold value to determine which of the first withdrawal failure screen 263A and the second withdrawal failure screen 263B is displayed on the guardian terminal device. Decided to display on 20. In the first modified example, it is determined whether to display the first screen 263A or the second screen 263B, which cannot be withdrawn, according to the parent's payment history. Differences from the above-described embodiment will be described below.

FIG. 17 is a diagram showing an example of withdrawal processing in the first modified example. In step S12 of this modification, if the settlement control unit 113 determines that the withdrawal has not been completed ("NO" in step S12), the dialogue control unit 112 determines that the withdrawal history information 126 satisfies the predetermined condition. It is determined whether or not the condition is satisfied (step S151).

Specifically, the dialog control unit 112 displays the first impossible-withdrawal screen 263A or the second-impossible-withdrawal screen on the guardian terminal device 20 depending on whether or not the information included in the withdrawal history information 126 satisfies a predetermined condition. 263B to be displayed. For example, if at least one of the change history of the school payment method included in the withdrawal history information 126 and the cumulative number of failures satisfies a predetermined condition ("YES" in step S151), the dialog control unit 112 determines whether the payment method has changed. case), a second withdrawal failure screen 263B is sent as a permit to change the re-withdrawal information 124 such as the desired date.

For example, if the number of changes included in the payment method change history is equal to or greater than a predetermined number, the dialog control unit 112 assumes that promoting payment by a method other than bank transfer is expected to result in early collection of the outstanding balance. It is treated as satisfying the conditions, and a second withdrawal failure screen 263B is sent. Further, for example, when the total number of failures of the guardian is equal to or greater than a predetermined number, the interaction control unit 112 may contribute to collection of outstanding balance by transmitting the second change screen including link information to the desired date change screen. Assuming that it does, it is treated as one that satisfies the conditions, and a second withdrawal failure screen 263B is sent.

Note that the predetermined condition using the withdrawal history information 126 is not limited to this example. For example, when both the change history of the payment method and the total number of failures satisfy the conditions, the second withdrawal failure screen 263B may be displayed. Also, consultation history may be included in the withdrawal history information 126, and whether or not to display the second withdrawal failure screen 263B may be determined according to the consultation history.

As described above, according to this modified example, different display screens are transmitted according to the situation of each guardian. By displaying a screen suitable for each guardian, it is possible to efficiently promote the collection of the outstanding balance.

<Second modification>
A second modification of the present embodiment will be described below. In the above-described embodiment, the guardian's desired re-withdrawal date is determined as the re-withdrawal date. In the second modification, the re-withdrawal date is determined according to the number of guardians who desire the same desired re-withdrawal date. Specifically, the school payment collection support device 10 in the second modified example determines the desired re-withdrawal date as the re-withdrawal date when the number of guardians requesting the same desired re-withdrawal date is equal to or greater than a predetermined number. If the number is less than the predetermined number, a day other than the desired re-withdrawal date is determined as the re-withdrawal date. '' Hereinafter, points different from the above-described embodiment will be described.

FIG. 18 is a flow chart showing an example of the withdrawal date determination process in the second modified example.

First, the re-withdrawal date determining unit 116 receives an input of the desired re-withdrawal date (step S61). Specifically, the re-withdrawal date determination unit 116 accepts an operation to input the desired re-withdrawal date in the desired date input area 264 a of the re-withdrawal condition change screen 264 . Note that the re-withdrawal date determination unit 116 stores the input desired re-withdrawal date in an area (not shown) of the storage unit 120 .

Next, the re-withdrawal date determining unit 116 determines whether or not the number of guardians who have entered the same desired re-withdrawal date is equal to or greater than a predetermined number (step S62). Specifically, re-withdrawal date determination unit 116 refers to storage unit 120 to determine whether the number of guardians who have specified the same schedule as the desired re-withdrawal date input in step S41 is equal to or greater than a predetermined number. determine whether or not

If the re-withdrawal date determination unit 116 determines that the number of guardians who have entered the same desired date for re-withdrawal is equal to or greater than the predetermined number ("YES" in step S62), the re-withdrawal date determination unit 116 selects the desired re-withdrawal date. The date is determined as the re-withdrawal date (step S63).

Since the processing performed in step S64 is the same as the processing in step S33 of FIG. 6, the description thereof is omitted.

Next, the dialog control unit 112 notifies the re-withdrawal date (step S65). Specifically, the dialogue control unit 112 transmits to the guardian terminal device 20 a notification indicating the re-withdrawal date determined in step S43. After that, the processing unit 110 terminates the processing of this flowchart.

FIG. 19 is a diagram showing an example of the re-withdrawal date notification screen 268. As shown in FIG. The re-withdrawal date notification screen 268 includes the determined re-withdrawal date. As shown in FIG. 19, the re-withdrawal date notification screen 268 may include the desired re-withdrawal date input in step S61 of FIG. The re-withdrawal date notification screen 268 may be displayed, for example, in the message column of the SNS, or may be displayed on the guardian terminal device 20 by accessing the link information displayed in the message column.

Return the description to FIG. When the re-withdrawal date determination unit 116 determines that the number of guardians who have entered the same desired re-withdrawal date is less than the predetermined number ("NO" in step S62), the re-withdrawal date determination unit 116 selects candidates for fixed intervals. Among the days, the date later than the desired re-withdrawal date is determined as the re-withdrawal date (step S66). Specifically, before the start of this process, fixed-interval candidate dates, which are candidates for re-withdrawal dates and are a plurality of candidate dates set at regular intervals, are preliminarily set in the school payment collection support device 10. It is defined. The re-withdrawal date determination unit 116 determines a re-withdrawal date as a date belonging to the fixed-interval candidate dates and later than the desired date for re-withdrawal input in step S61.

FIG. 20 is an image diagram showing an overview of the re-withdrawal date determination process using the fixed-interval candidate date. The circles with symbols "1", "2", and "3" indicate requests for the date the guardian wishes to withdraw again, and the circles without symbols indicate requests for the fixed-interval candidate dates. Also, the dotted line indicates a threshold value for determining the desired re-withdrawal date as the re-withdrawal date. The threshold in FIG. 20 is "4", and when there are four or more guardians who desire the same desired re-withdrawal date, the desired re-withdrawal date can be determined as the re-withdrawal date.

Since there is only one guardian who requested a re-withdrawal date related to the request of "1", the desired re-withdrawal date is not decided on the re-withdrawal date. A fixed interval candidate date later than the date is determined as the redemption date. Similarly, since there are two guardians who requested the desired re-withdrawal date of "2" and "3", the desired date of re-withdrawal is not decided, and the guardian has "2" ” and “3” are determined as re-withdrawal dates.

Return the description to FIG. Since the processes performed in steps S67 and S68 are the same as the processes performed in steps S64 and S65, description thereof is omitted. After that, the processing unit 110 terminates the processing of this flowchart.

As described above, according to this modification, if there are few guardians who request the same desired date for re-withdrawal, the re-withdrawal date is decided so that the withdrawal will be made collectively on the candidate date at regular intervals instead of deciding on the re-withdrawal date. do. As a result, it is possible to reduce the burden of management work and withdrawal work related to re-withdrawal, and improve efficiency.

After the withdrawal date determination process shown in FIG. 18 is completed, there is a possibility that the number of guardians who will withdraw money on the fixed interval candidate date does not reach the threshold value for making the determination in step S62. In that case, by repeating the process of FIG. 18, it is possible to adjust the number of guardians equal to or greater than the threshold so that the withdrawal will be made on the same re-withdrawal date. Specifically, in step S62, it is determined whether or not the number of guardians assigned to the same fixed-interval candidate day is equal to or greater than a predetermined number (that is, a threshold value). ), another fixed-interval candidate date after the fixed-interval candidate date is determined as the re-withdrawal date. This is repeated until there are no redemption dates for which guardians below the threshold have been determined.

Although the embodiments and modifications according to the present invention have been described above, the present invention is not limited to the examples of the above-described embodiments, and includes various modifications. For example, the above-described exemplary embodiments are described in detail to facilitate understanding of the present invention, and the present invention is not limited to those having all the configurations described herein. Also, part of the configuration of one example of an embodiment can be replaced with the configuration of another example. Also, it is possible to add another example configuration to one example configuration of a certain embodiment. In addition, addition, deletion, and replacement of other configurations can also be performed for a part of the configuration of one example of each embodiment. Further, each of the above configurations, functions, processing units, processing means, and the like may be realized by hardware, for example, by designing a part or all of them using an integrated circuit. In addition, the control lines and information lines in the drawing indicate what is considered necessary for explanation, and do not necessarily indicate all of them. It may be considered that almost all configurations are interconnected.

In order to facilitate understanding, the functional configurations of the school payment collection support device 10, the guardian terminal device 20, and the bank terminal device 30 are classified according to main processing contents. The present invention is not limited by the method of classifying the constituent elements or their names. As described above, the configurations of the school payment collection support device 10, the guardian terminal device 20, and the bank terminal device 30 can be classified into more components according to the processing contents. Also, one component can be grouped to perform more processing.

1: school payment collection support system, 10: school payment collection support device, 11: arithmetic device, 12: memory, 13: external storage device, 14: input IF, 15: output IF, 16: communication IF, 17: storage medium Driving device 18: Media 20: Guardian terminal device 30: Bank terminal device 110/210/310: Processing unit 111: Registration information reception unit 112/211: Dialogue control unit 113: Payment control unit 114: Withdrawal information generation unit 115: Display information generation unit 116: Re-withdrawal date determination unit 117: Consultation reception unit 120: Storage unit 121: Personal registration information 122: Regular withdrawal information 123: Withdrawal result information , 124: Re-withdrawal information, 125: Notification information, 126: Withdrawal history information, 130/230/330: Input unit, 140/240/340: Output unit, 150/250/350: Communication unit, 212: Re-withdrawal information Change request part, 261: Application form, 262: Withdrawal completion screen, 263A: First withdrawal impossible screen, 263B: Second withdrawal impossible screen, 264: Re-withdrawal condition change screen, 265: School attendance support information screen, 266: Card payment success notification screen 267: Card payment failure notification screen 268: Re-withdrawal date notification screen 311: Withdrawal request reception unit 312: Withdrawal unit X: Network

Claims (11)

a dialogue control unit that controls dialogue with a guardian terminal device owned by a guardian who pays school fees;
a payment control unit for controlling payment of the school payment;
a re-withdrawal date determination unit that acquires the desired re-withdrawal date of the school payment from the parent terminal device and determines the re-withdrawal date;
The payment control unit requests the financial institution terminal device to withdraw the school payment, and receives information indicating whether or not the financial institution has successfully withdrawn the school payment as a response to the request,
When the financial institution fails to withdraw the school fee on a predetermined debit date, the dialogue control unit notifies the guardian terminal device of the impossibility of withdrawal by using the dialogue, and A school payment collection support device characterized by receiving a desired date for re-withdrawal. The school payment collection support device according to claim 1,
Equipped with a registration information reception unit that receives registration of personal information including credit card information of parents,
A school payment collection support device, wherein the payment control unit settles the school payment using the credit card information when the number of withdrawal failures reaches a predetermined number. The school payment collection support device according to claim 1 or 2,
Display information generation for generating display information of a first withdrawal failure screen notified when the number of withdrawal failures is less than a predetermined number or a second withdrawal failure screen notified when the number is equal to or greater than a predetermined number having a department,
The dialogue control unit uses the number of failures to determine which link information of the first screen that cannot be withdrawn or the second screen that cannot be withdrawn should be included in the notification. Recovery support device. The school payment collection support device according to claim 1 or 2,
a display information generation unit that generates display information for a re-withdrawal condition change screen to be transmitted to the parent terminal device when the financial institution fails to withdraw the school fee;
The re-withdrawal condition change screen includes a desired date input area for receiving input of the desired re-withdrawal date, a payment method change receiving area for receiving a request for changing the payment method of the school payment, and a request for consultation regarding the school payment. A school payment collection support device characterized by having a consultation reception area. The school payment collection support device according to claim 4,
The school payment collection support device, wherein the re-withdrawal condition change screen includes link information to a screen displaying information related to the school attendance support system. The school payment collection support device according to claim 3,
A storage unit for storing withdrawal history information including a change history of the payment method of the school fee or the cumulative number of withdrawal failures of the guardian for the guardian,
The dialogue control unit determines which of the first screen for disabling withdrawal and the second screen for disabling withdrawal is to be notified to the guardian terminal device based on whether or not the withdrawal history information satisfies a predetermined condition. A school payment collection support device characterized by: The school payment collection support device according to any one of claims 1 to 6,
The re-withdrawal date determination unit determines the desired re-withdrawal date as the re-withdrawal date when the number of guardians requesting the desired re-withdrawal date received from the guardian terminal device is equal to or greater than a predetermined number, If it is less than the above, determine a day other than the desired re-withdrawal date as the re-withdrawal date,
The school payment collection support device, wherein the dialogue control unit uses the dialogue to notify the guardian terminal device of the re-withdrawal date determined by the re-withdrawal date determination unit. The school payment collection support device according to claim 7,
When the number of guardians is less than the predetermined number, the re-withdrawal date determination unit selects the re-withdrawal date among a plurality of candidate dates at fixed intervals set in advance at regular intervals. A school payment collection support device, characterized in that a date later than a desired date is determined as the re-withdrawal date. A school payment collection method using a guardian terminal device owned by a guardian who pays school payment and a school payment collection support device,
an application form collection procedure for collecting from the parent an application form for a service provided to the student, the application form containing credit card information to be used for withdrawal in the event of non-payment;
a card information acquisition procedure for the school payment collection support device to acquire the credit card information;
Success/failure information reception procedure of requesting the financial institution terminal device to withdraw the school payment in the school payment collection support device, and receiving information indicating whether or not the financial institution has successfully withdrawn the school payment as a response to the request. When,
a card payment execution procedure for executing payment using the credit card information when the withdrawal of the school payment fails a predetermined number of times in the school payment collection support device;
a notification procedure for notifying a payment result in the card payment execution procedure using a dialogue function with the parent terminal device in the school payment collection support device;
A school payment collection method, comprising: A program for causing a processing unit of a computer to execute a school payment collection support method,
A dialogue control procedure for controlling dialogue with a guardian terminal device possessed by a guardian who pays school fees;
a payment control procedure for controlling the payment of school fees;
a re-withdrawal date determination procedure for obtaining the desired re-withdrawal date of the school payment from the guardian terminal device and determining the re-withdrawal date;
In the settlement control procedure, requesting the financial institution terminal device to withdraw the school fee, receiving information indicating whether or not the financial institution has successfully withdrawn the school fee as a response to the request,
In the dialog control procedure, if the financial institution fails to withdraw the school fee on a predetermined withdrawal date, the parent terminal device is notified of the impossibility of withdrawal using the dialog, and the parent terminal device A program characterized by receiving a desired date for re-withdrawal. A guardian terminal device possessed by a guardian who pays school fees, a financial institution terminal device possessed by a financial institution, and a school payment collection support device communicably connected to the guardian terminal device and the financial institution terminal device. A school payment collection support system comprising
The school payment collection support device is
an interaction control unit that controls interaction with the parent terminal device;
a payment control unit that controls the payment of school fees;
a re-withdrawal date determination unit that acquires the desired re-withdrawal date of the school payment from the parent terminal device and determines the re-withdrawal date;
The financial institution terminal device
a communication unit that transmits information indicating whether or not the school payment has been successfully withdrawn to the school payment collection support device in response to a request for withdrawal of the school payment from the school payment collection support device;
The parent terminal device
An output unit that displays the content of dialogue with the school payment collection support device,
When the financial institution fails to withdraw the school payment on a predetermined withdrawal date, the dialogue control unit of the school payment collection support device uses the dialogue to notify the parent terminal device of the inability to withdraw the school payment. A school payment collection system, characterized in that the desired re-withdrawal date is received from a parent's terminal device.

Images