JP2021174519A - Fixed date prepayment system - Google Patents

Abstract

To provide a fixed date prepayment system that automatically repeats prepayment on a fixed date.SOLUTION: A fixed date prepayment system includes a recurring payment date relationship determination unit AF configured to determine whether acquired time information has a predetermined relationship with recurring payment date defined in recurring payment date information associated with employee identification information, a recurring payment processing unit AG configured to perform payment processing, which is the processing for payment of all or part of the payable consideration by a payment method identified by payment method identification information obtained in association with the employee identification information, when the determination result is a determination result affirming the predetermined relationship with the recurring payment date, and a recurring payment processing history holding unit AH configured to hold payment processing history in association with the employee identification information.SELECTED DRAWING: Figure 1

Description

The present invention is an invention relating to a prepaid system such as salary or wage. In particular, it relates to a system suitable for repeatedly prepaying the same amount on the same day every month using an employee or worker's individual payment method.

In general, a system for prepayment of salary or wage is used by a company as an employer as a part of welfare in preparation for a shortage of living expenses due to unexpected expenses of an employee or a worker. Therefore, the system is configured to accept prepaid payments at any time within a reasonable range based on salary or labor claims.

JP-A-2019-185540

However, as mentioned above, although prepaid payments are used to meet unexpected expenses, there is no system that automates prepaid payments in response to regularly incurred living expenses such as utility bills and rent. This is because prepaid payments have been considered to play an emergency evacuation role. However, some employees or workers are constantly paid only to the limit of their lives. This is not necessarily due to low salaries or wages, but many other causes, such as the need to take care of parents and the expenses incurred for illness. In these cases, it may be difficult to pay various expenses periodically between the salary payment date and the next salary payment date, or between the wage payment date and the next wage payment date. For example, payment obligations that become difficult include utility bills, mobile phone bills, utility bills such as water and gas, and rent payments that must be paid on a regular basis.

On the other hand, PayPay (registered trademark), LINE Pay (registered trademark), iD (registered trademark), WAON (registered trademark), nanaco (registered trademark), Rakuten Edy (registered trademark), QUICPay (registered trademark), Suica (registered trademark) ), Apple pay (registered trademark) and other electronic money have become widespread, and some of the above fees can be paid. Since these electronic money are so-called charge type, they are widely used by young people who cannot open a bank account. In this case, it is not automatically paid like credit card payment or direct debit, but it is expected that it will become popular as a payment method for utility charges, etc. in the future because it is possible to easily pay utility charges.

In view of such circumstances, the present invention makes it possible to make advance payments by a predetermined payment method (including electronic money) repeatedly and periodically once set. Specifically, it is as follows.

<First solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information.

Employment relationship information holding department that holds employment relationship information that is information that associates user identification information that identifies the user and employee identification information that identifies the employee employed by the user based on the employment relationship. All or part of the payable consideration, which is the consideration payable to the subordinate before the salary payment date determined between (AA) and the employer based on the employee's salary claim information, of the employee The Salary Claim Information Acquisition Department (AB), which is acquired based on the employer identification information associated with the employee identification information, and all or part of the payable consideration paid to the employee based on the salary claim information. The Recurring Payment Date Information Holder (AC), which holds recurring payment date information associated with employee identification information, which is information that determines the recurring payment date for repetitive payments, and all or part of the payable consideration for employees. A payment method identification information acquisition unit (AD) that acquires payment method identification information in association with an employee identification information, and a time information acquisition unit (AE) that acquires time information including a date. , The Repeated Payment Date Relationship Judgment Department (AF), which determines whether the acquired time information has a predetermined relationship with the Repeated Payment Date defined in the Repeated Payment Date Information associated with the employee identification information, and Repeated. When the judgment result by the payment date relationship judgment department (AF) is the judgment result that the payment date has a predetermined relationship with the repeated payment date, it is identified by the payment method identification information obtained in association with the employee identification information. The history of payment processing by the Recurring Payment Processing Department (AG), which processes payments, which is the processing for payment of all or part of the payable consideration amount by the payment method, and the Recurring Payment Processing Department (AG). Provided is a fixed date prepayment system having a recurring payment processing history holding unit (AH) that holds in association with employee identification information.

<Second solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the first solution, and the payment method identification information is provided. Multiple payment method identification information holding units (AJ), payment method selection reception unit (AK) that accepts one or more selections of payment method identification information held in association with employee identification information, and employee identification information It also has a payment method payment consideration allocation unit (AM) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with, and a payment method identification information acquisition unit ( AD) provides a fixed date prepayment system that is configured to retrieve the payment method identification information for which the selection has been accepted in association with the employee identification information.

<Third solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the first or second solution, and employees Fixed further having a remittance unique information holding unit (AN) that holds the person identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information in association with each other. Provides a date prepayment system.

<Fourth solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the first to third solutions. A fixed-date prepayment system that also has a Recurring Payment Date Information Editing Department (AP) that edits the Recurring Payment Date Information and / and Employee Identification Information held in the Recurring Payment Date Information Retaining Department (AC). offer.

<Fifth solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information.
It is based on any one of the first to fourth solutions.
Provided is a fixed date prepayment system further having a recurring payment date information recording unit (AR) for recording recurring payment date information and / and employee identification information in a recurring payment date information holding unit (AC).
<Sixth solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the first to fifth solutions. The start processing request acquisition unit (AS) that acquires the start processing request of the prepaid salary request in association with the employee identification information, and the start processing time information acquisition unit that acquires the time information including the date when the start processing request was acquired. (CD), salary receivable information associated with employee identification information, recurring payment date information associated with employee identification information, if available, and employee identification information, if available. The Prepaid Amount Acquisition Department (AT) to obtain the Prepaid Amount, which is the amount that allows a prepayment request based on all or part of the payable consideration paid on the associated recurring payment date, and the Prepaid Amount. The prepayment request amount acquisition department (AW) that acquires the prepayment request amount in association with the employee identification information within the range not exceeding, and the prepayment processing department (AX) that performs the prepayment processing that is the processing for the prepayment of the acquired prepayment request amount. ), And a prepayment history holding unit (AY) that holds the prepayment history, which is the history of the prepayment processing in the prepayment processing unit (AX), in association with the employee identification information, and provides a fixed date prepayment system.

<7th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the first to sixth solutions. With the processing result acquisition unit (AZ) that acquires the processing result that is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the employee identification information. , The SNS identification information holding unit (BA) that holds the SNS identification information used by the employee in association with the employee identification information, and the SNS identification information associated with the employee identification information associated with the processing result. Provided is a fixed date prepayment system having a processing result notification unit (BB) for notifying a processing result via an identified SNS.

<8th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the seventh solution based on the third solution. The remittance unique information holding unit (AN) holds the employee identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. Provide a fixed date prepayment system with identification information retention means (BC).

<Ninth solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the first to eighth solutions. Then, the salary receivable information acquisition department (AB) acquires information indicating a fixed amount as all or part of the payable consideration paid to the employee acquired in association with the employee identification information (BD). ) To provide a fixed date prepayment system.

<10th solution>

Employment relationship information retention step that retains employment relationship information, which is information that identifies the user identification information that identifies the user and the employee identification information that identifies the employee employed by the user, based on the employment relationship. All or part of the payable consideration, which is the consideration that can be paid to the subordinate before the salary payment date determined between (aa) and the employer based on the employee's salary claim information, of the employee The salary receivables information acquisition step (ab) acquired based on the employer identification information associated with the employee identification information and all or part of the payable consideration paid to the employee based on the salary receivable information. Recurring payment date information retention step (ac), which retains recurring payment date information in association with employee identification information, which is information that determines the recurring payment date for recurring payments, and all or part of the payable consideration for employees. The payment method identification information acquisition step (ad) for acquiring the payment method identification information associated with the employee identification information, and the time information acquisition step (ae) for acquiring the time information including the date. , Repeat payment date relationship judgment step (af) to determine whether the acquired time information has a predetermined relationship with the repeat payment date defined in the repeat payment date information associated with the employee identification information, and repeat If the judgment result in the payment date relationship judgment step (af) is the judgment result that the payment date has a predetermined relationship with the repeated payment date, it is identified by the payment method identification information obtained in association with the employee identification information. The history of payment processing in the recurring payment processing step (ag) and the recurring payment processing step (ag), which is the processing for payment of all or part of the payable consideration amount by the payment method. Recurring payment processing history retention step (ah), which is retained in association with employee identification information,
It is composed of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides a method of operating a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information.

<11th solution>

Based on the tenth solution, it accepts a payment method identification information retention step (aj) that retains a plurality of payment method identification information and one or more selections of payment method identification information that is retained in association with the employee identification information. Payment method selection Acceptance step (ak) and payment method payment consideration allocation step (am) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the employee identification information. And, the payment method identification information acquisition step (ad) is configured to acquire the payment method identification information that has received the selection in association with the employee identification information (CPU, memory, bus). , Input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. It provides a method of operating a fixed-date prepayment system, which is a computer configured to perform calculations and realize various functions through the required data and information.

<12th solution>

Based on the tenth or eleventh solution, the employee identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information are associated and retained. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a unique information retention step (an) for remittance, and software (BioS,) for operating each of the above steps. OS, device driver, etc.), software uses hardware resources to perform various calculations and realizes various functions through the required data and information. offer.

<13th solution>

Recurring payments that edit the recurring payment date information and / and employee identification information held in the recurring payment date information retention step (ac) based on any one of the tenth to twelfth solutions. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a daily information editing step (ap) and software (BIOS, OS,) for operating each of the above steps. It is composed of device drivers, etc.), and the software provides a method of operating a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information. ..

<14th solution>

A recurring payment date information recording step that records recurring payment date information and / and employee identification information in a recurring payment date information holding unit (AC) based on any one of the tenth to thirteenth solutions. From a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has ar) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides a method of operating a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information.

<15th solution>

Based on any one of the tenth to fourteenth solutions, the start processing request acquisition step (as) for acquiring the start processing request for the prepaid salary request in association with the employee identification information and the start processing request are acquired. Start processing request to acquire time information including date Time information acquisition step (cd), salary receivable information associated with employee identification information, and recurring payments associated with employee identification information, if available. The prepayable amount, which is the amount that allows the prepayment request based on the date information and, if available, all or part of the payable consideration paid on the recurring payment date associated with the employee identification information. The prepayable amount acquisition step (at) to be acquired, the prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the employee identification information within the range not exceeding the prepayable amount, and the prepayment of the acquired prepayment request amount. Prepaid processing step (ax) that performs prepaid processing, which is a process for ), And a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides a method of operating a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information.

<16th solution>

Based on any one of the tenth to fifteenth solutions, the employee identification of the processing result which is the result of the payment processing by the recurring payment processing unit (AG) or the prepayment processing by the prepayment processing unit (AX). The processing result acquisition step (az) that is acquired in association with the information, the SNS identification information retention step (ba) that is associated with the employee identification information and holds the SNS identification information used by the employee, and the processing result are associated with the processing result. Hardware (CPU, memory, bus, input / output device,) having a processing result notification step (bb) for notifying the processing result via the SNS identified by the SNS identification information associated with the employee identification information. It consists of a computer consisting of various peripheral devices (user interfaces, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps, and the software is required to perform various calculations using hardware resources. It provides a method of operating a fixed-date prepayment system, which is a computer configured to realize various functions through data and information.

<17th solution>

Based on the twelfth solution, based on the sixteenth solution, the remittance unique information retention step (an) includes employee identification information, payment method identification information, remittance unique information, and further remittance. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having an SNS identification information holding sub-step (bc) that holds the SNS identification information in association with each other, and each of the above steps. It is composed of software (BIOS, OS, device driver, etc.) for functioning, and the software is a computer configured to realize various functions through data and information required by performing various calculations using hardware resources. Provides a method of operating a fixed date prepayment system.

<18th solution>

Based on any one of the tenth to seventeenth solutions, the salary receivables information acquisition step (ab), as all or part of the payable consideration paid to the employee acquired in association with the employee identification information. Make each of the above steps work with a computer consisting of hardware (CPU, memory, bus, input / output device, various peripherals, user interface, etc.) that has a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount. Software (BioS, OS, device driver, etc.) for the purpose of the software, which is a computer that uses hardware resources to perform various calculations and realizes various functions through the required data and information. Provides a method of operating a prepaid system.

<19th solution>

Employment relationship information retention step that retains employment relationship information, which is information that identifies the user identification information that identifies the user and the employee identification information that identifies the employee employed by the user, based on the employment relationship. All or part of the payable consideration, which is the consideration that can be paid to the subordinate before the salary payment date determined between (aa) and the employer based on the employee's salary claim information, of the employee The salary receivables information acquisition step (ab) acquired based on the employer identification information associated with the employee identification information and all or part of the payable consideration paid to the employee based on the salary receivable information. Recurring payment date information retention step (ac), which retains recurring payment date information in association with employee identification information, which is information that determines the recurring payment date for recurring payments, and all or part of the payable consideration for employees. The payment method identification information acquisition step (ad) for acquiring the payment method identification information associated with the employee identification information, and the time information acquisition step (ae) for acquiring the time information including the date. , Repeat payment date relationship judgment step (af) to determine whether the acquired time information has a predetermined relationship with the repeat payment date defined in the repeat payment date information associated with the employee identification information, and repeat If the judgment result in the payment date relationship judgment step (af) is the judgment result that the payment date has a predetermined relationship with the repeated payment date, it is identified by the payment method identification information obtained in association with the employee identification information. The history of payment processing in the recurring payment processing step (ag) and the recurring payment processing step (ag), which is the processing for payment of all or part of the payable consideration amount by the payment method. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a recurring payment processing history retention step (ah) that is retained in association with employee identification information, and the above. It consists of software (BIOS, OS, device driver, etc.) for functioning each step, and the software is configured to perform various calculations using hardware resources and realize various functions through the required data and information. It provides an operation program written readable and executable to a fixed-date prepayment system, which is a computer.

<20th solution>

Based on the nineteenth solution, it accepts a payment method identification information retention step (aj) that retains multiple payment method identification information and one or more selections of payment method identification information that is retained in association with the employee identification information. Payment method selection Acceptance step (ak) and payment method payment consideration allocation step (am) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the employee identification information. And, the payment method identification information acquisition step (ad) is configured to acquire the payment method identification information that has received the selection in association with the employee identification information (CPU, memory, bus). , Input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. It provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform calculations and realize various functions through the required data and information.

<21st solution>

Based on the 19th or 20th solution, the employee identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information are associated and retained. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a unique information retention step (an) for remittance, and software (BioS,) for operating each of the above steps. It is composed of OS, device driver, etc.), and the software can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provides the operation program described in.

<22nd solution>

Edit the recurring payment date information and / and the employee identification information held in the recurring payment date information retention step (ac) based on any one of the 19th to 21st solutions. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a daily information editing step (ap) and software (BIOS, OS,) for operating each of the above steps. It is composed of device drivers, etc.), and the software is readable and executable in a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provide the operation program.

<23rd solution>

A recurring payment date information recording step that records recurring payment date information and / and employee identification information in a recurring payment date information holding unit (AC) based on any one of the 19th to 22nd solutions. From a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has ar) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software is configured to perform various calculations using hardware resources and realize various functions through the required data and information. It is a computer that is configured to realize various functions. offer.

<24th solution>

Based on any one of the 19th to 23rd solutions, the start processing request acquisition step (as) for acquiring the start processing request for the prepaid salary request in association with the employee identification information and the start processing request are acquired. Start processing request to acquire time information including date Time information acquisition step (cd), salary receivable information associated with employee identification information, and recurring payments associated with employee identification information, if available. The prepayable amount, which is the amount that allows the prepayment request based on the date information and, if available, all or part of the payable consideration paid on the recurring payment date associated with the employee identification information. The prepayable amount acquisition step (at) to be acquired, the prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the employee identification information within the range not exceeding the prepayable amount, and the prepayment of the acquired prepayment request amount. Prepaid processing step (ax) that performs prepaid processing, which is a process for ), And a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. An operation program that is readable and executable in a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information. offer.

<25th solution>

Based on any one of the 19th to 24th solutions, the employee identification of the processing result which is the result of the payment processing by the recurring payment processing unit (AG) or the prepaid processing by the prepaid processing unit (AX). The processing result acquisition step (az) that is acquired in association with the information, the SNS identification information retention step (ba) that is associated with the employee identification information and holds the SNS identification information used by the employee, and the processing result are associated with the processing result. Hardware (CPU, memory, bus, input / output device,) having a processing result notification step (bb) for notifying the processing result via the SNS identified by the SNS identification information associated with the employee identification information. It consists of a computer consisting of various peripheral devices (user interfaces, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps, and the software is required to perform various calculations using hardware resources. It provides an operation program that can be read and executed in a fixed-date prepayment system, which is a computer configured to realize various functions through data and information.

<26th solution>

Based on the 21st Solution Based on the 25th Solution, the Remittance Unique Information Retention Step (an) includes employee identification information, payment method identification information, remittance unique information, and further remittance. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a remittance SNS identification information holding substep (bc) that holds the SNS identification information in association with the above. It is composed of software (BIOS, OS, device driver, etc.) for functioning each step, and the software is configured to perform various calculations using hardware resources and realize various functions through the required data and information. It provides an operation program written readable and executable to a fixed-date prepayment system, which is a computer.

<27th solution>

Based on any one of the 19th to 26th solutions, the salary receivables information acquisition step (ab), as all or part of the payable consideration paid to the employee acquired in association with the employee identification information. Make each of the above steps work with a computer consisting of hardware (CPU, memory, bus, input / output device, various peripherals, user interface, etc.) that has a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount. It is a computer that is composed of software (BioS, OS, device driver, etc.) for the purpose, and the software is a computer that uses hardware resources to perform various calculations and realizes various functions through the required data and information. Provides a readable and executable operating program for prepaid systems.

<28th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information.

Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. Based on the worker identification information that identifies the worker who is the person, the contractual relationship information holding department (BE) that holds the contractual relationship information that is the information related based on the contractual relationship, and the labor claim information of the worker. All or part of the payable consideration, which is the consideration payable to the worker before the wage payment date set with the employer, is added to the employer identification information associated with the worker identification information of the worker. Repetitive payment, which is information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor receivable information acquisition department (BF) acquired based on the labor receivable information. The Repeated Payment Date Information Holder (AC), which holds the day information in association with the worker identification information, and the payment method identification information, which is the information that identifies the payment method for all or part of the payable consideration for the worker. The payment method identification information acquisition unit (AD) acquired in association with the worker identification information, the time information acquisition unit (AE) that acquires the time information including the date, and the acquired time information are associated with the worker identification information. Judgment results by the Repeated Payment Date Relationship Judgment Department (AF) and the Repeated Payment Date Relationship Judgment Department (AF), which determine whether or not the relationship has been set with the repeated payment date specified in the repeated payment date information, are repeated. All or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the worker identification information when it is judged that the relationship has been determined with the return payment date. The recurring payment processing department (AG) that performs payment processing, which is the processing for payment, and the repetitive payment processing history that retains the history of payment processing in the repetitive payment processing department (AG) in association with the worker identification information. A fixed date prepayment system with a holding unit (AH) is provided.

<29th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , The software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the 28th solution, and the payment method identification information is provided. A multiple payment method identification information holding unit (AJ), a payment method selection reception unit (AK) that accepts one or more selections of payment method identification information held in association with the worker identification information, and a worker identification information. It also has a payment method payment consideration allocation unit (AM) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with, and a payment method identification information acquisition unit ( AD) provides a fixed date prepayment system that is configured to obtain the payment method identification information for which the selection has been accepted in association with the worker identification information.

<30th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the 28th or 29th solution, and labor. Fixed further having a remittance unique information holding unit (AN) that holds the person identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information in association with each other. Provides a date prepayment system.

<31st solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the 28th to 30th solutions. A fixed date prepayment system that also has a Repeated Payment Date Information Editing Department (AP) that edits the Repeated Payment Date Information and / and Worker Identification Information held in the Repeated Payment Date Information Holding Department (AC). offer.

<32nd solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information.
It is based on any one of the 28th to 31st solutions.
Provided is a fixed date prepayment system further having a recurring payment date information recording unit (AR) for recording recurring payment date information and / and worker identification information in the recurring payment date information holding unit (AC).
<33rd solution>

It consists of an electronic computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the 28th to 32nd solutions. In the start processing request acquisition unit (AS) that acquires the start processing request of the wage prepayment request in association with the worker identification information, and the start processing request time information acquisition that acquires the time information including the date when the start processing request was acquired. Department (CD), labor receivable information associated with worker identification information, recurring payment date information associated with worker identification information, if available, and worker identification information, if available. With the Prepaid Amount Acquisition Department (AT), which obtains the prepaid amount, which is the amount that allows the prepaid request, based on all or part of the payable consideration paid on the recurring payment date associated with The prepayment request amount acquisition department (AW) that acquires the prepayment request amount in association with the worker identification information within the range not exceeding the amount, and the prepayment processing department that performs the prepayment processing that is the processing for prepayment of the acquired prepayment request amount ( Provided is a fixed date prepayment system having a prepayment history holding unit (AY) that holds a prepayment history, which is a history of prepayment processing in the prepayment processing unit (AX), in association with worker identification information.

<34th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the 28th to 33rd solutions. Then, with the processing result acquisition unit (AZ) that acquires the processing result that is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the worker identification information. , The SNS identification information holding unit (BA) that holds the SNS identification information used by the worker in association with the worker identification information, and the SNS identification information associated with the worker identification information associated with the processing result. Provided is a fixed date prepayment system having a processing result notification unit (BB) for notifying a processing result via an identified SNS.

<35th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and as each part, the 31st to 34th solution means based on the 30th solution means. The Remittance Unique Information Retention Department (AN) holds the worker identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. Provided is a fixed date prepayment system having SNS identification information holding means (BC) for remittance.

<36th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the 28th to 35th solutions. Then, the Labor Claim Information Acquisition Department (BF) acquires information indicating a fixed amount as all or part of the payable consideration paid to the worker acquired in association with the worker identification information (BD). ) To provide a fixed date prepayment system.

<37th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and as each part, the first to ninth solution means or the 28th to 36th solution means. Based on any one of the above, all or part of the payable consideration associated with the worker identification information is less than the prescribed amount and the Recurring Payment Processing Department (AG) processes the full amount. Payment processing indicating that payment processing cannot be performed when the judgment result of the payment processing approval / disapproval judgment unit (BG) and the payment processing approval / disapproval judgment unit (BG) is the judgment result that payment processing cannot be performed. Provided is a fixed date prepayment system having a payment processing anomaly information notification unit (BH) that notifies workers and / and employers of anomalous information.

<38th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the 36th solution based on the 33rd solution. Assuming that the prepayment request amount acquisition department (AW) has processed the prepayment request amount acquired by the prepayment request amount acquisition department (AW), the closest repetition determined with the user. Judgment results by the fixed amount payment approval / disapproval determination means (BJ) and the fixed amount payment approval / disapproval determination means (BJ) that determine whether or not the fixed amount payment that is already set to be paid on the recurring payment date cannot be made on the payment date. The prepaid request amount acquisition means (BK), which is the prepaid request amount obtained by reducing the total amount of the payment to the worker to the amount that can be paid the fixed amount, when the result is that the payment cannot be made. Provide a fixed date prepayment system with.

<39th solution>

It consists of an electronic computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the 28th to 38th solutions. The wage payment date information holding department (BM), which holds the wage payment date information, which is the information indicating the predetermined wage payment date in association with the worker identification information and / and the employer identification information, and the worker's labor claim information. The amount paid by recurring payment and / or the prepaid request amount that has been prepaid, which occurred by the predetermined closing date on the prescribed wage payment date held with the user based on In the process of payment so that all or part of the payable consideration, which is the payable consideration excluded from the wages that would have been paid if there were no recurring payments or prepayments, is payable. Provided is a fixed date prepayment system having a balance payment processing unit (BN) that performs a balance payment processing.

<40th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , The software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the 39th solution means, and the balance payment process is performed. When the balance payment processing department (BN) requires a fee for the remittance method used as the payment method when processing the balance, the slip processing (electronic slip and electronic slip) for the user to bear the fee. Provides a fixed date prepayment system with a user-paid voucher processing unit (CE) that can include both vouchers made of actual sheets.

<41st solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , The software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the 39th or 40th solution means, and the balance payment is made. When the remittance method used as the payment method when the balance payment processing department (BN) processes the balance requires a fee, the remittance company handles the slip (electronically) to bear the fee. Provides a fixed date prepayment system with a remittance operator-paid voucher processing unit (CF) that can include both vouchers and vouchers made of actual sheets (but the same shall apply hereinafter). If it is based on, both the user and the remittance company will bear the burden).

<42nd solution>

It consists of an electronic computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , The software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the 31st solution, and the recurring payment date information. Or / and has an editing authority identification information holding unit (CC) that holds the editing authority identification information that identifies the editing authority that is the authority to edit the worker identification information, and the contract-related information holding unit (BE) holds it. It has an editing authority additional holding means (BP) that holds the worker identification information and / and the employer identification information in association with the editing authority identification information, and the recurring payment date information editorial department (AP) is held. The recurring payment date information and / and the worker identification information can be edited including registration and deletion only by the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. Provided is a fixed date prepayment system having an editing authority limiting means (BR) that sets restrictions so as to.

<43rd solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on the 39th solution, wage payment date information or / And the editing authority that identifies the editing authority, which is the authority to edit the worker identification information. The editing authority identification information holding unit (CC) that holds the identification information, and the contract-related information holding unit (BE) holds the worker. Wage payment date information that has an editing authority additional holding means (BP) that holds identification information and / and user identification information in association with the editing authority identification information, and is held by the wage payment date information holding unit (BM). of,
Fixed having a wage payment date information editorial department (BS) that allows editing, including registration and deletion, only to those (employers and / and workers) identified by the identification information associated with the editing authority identification information. Provides a date prepayment system.

<44th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and each part is based on any one of the 33rd to 43rd solutions. The time information acquisition unit (AE), which acquires time information for prepaid processing, which will be described later, and withdrawal, which is information indicating the execution date of withdrawal processing, which is the processing of withdrawal of money, etc. by prepaid from the user. It has a withdrawal processing execution reservation date information acquisition unit (BT) for acquiring processing execution reservation date information, and the prepaid processing unit (AX) has the acquired withdrawal processing execution reservation date information and a time information acquisition unit ( Withdrawal execution processing means (BW) that processes the withdrawal process so that the withdrawal process is executed on the date specified by the withdrawal process execution reservation date information based on the time information acquired by AE). To provide a fixed date prepayment system.

<45th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and as each part, the first to ninth solution means or the 28th to 44th solution means. An employee or labor that is based on any one of the above and is associated with the user identification information and the user is identified by the employee identification information or worker identification information associated with the user identification information. Executed by the Deposit Information Acquisition Department (BX) that acquires the deposit information for the recurring payment processing and / and the prepaid processing performed on the person, and the Recurring Payment Processing Department (AG) and / and the Prepaid Processing Department (AX). Payment processing that is to be executed based on the payment processing amount information acquisition unit (BY) that acquires payment processing amount information, which is information indicating the amount of payment processing to be attempted, the acquired payment processing amount information, and deposit information. The payment processing execution judgment rule holding unit (BZ) that holds the payment processing execution judgment rule, which is a rule for judging whether to execute, the held payment processing execution judgment rule, the held deposit information, and Provided is a fixed date prepayment system further comprising a payment processing execution determination unit (CA) that determines whether payment processing should be executed based on the acquired payment processing amount information.

<46th solution>

It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BioS, OS, device driver, various programs, etc.) for operating the following parts. , Software is configured to perform various calculations using hardware resources and realize various functions through the required data and information, and as each part, the first to ninth solution means or the 28th to 44th solution means. An employee or labor that is based on any one of the above and is associated with the user identification information and the user is identified by the employee identification information or the worker identification information associated with the user identification information. It has a deposit information acquisition department (BX) that acquires deposit information for repetitive payment processing and / and prepayment processing performed on a person, and a salary receivable information acquisition department (AB) or labor receivable information acquisition department (BE). , Or / and the Prepaid Amount Acquisition Department (AT) shall be an employee before the salary payment date or wage payment date determined between the employer based on the acquired deposit information and the salary claim information and / and the labor claim information. Provided is a fixed date prepayment system having a deposit information dependent prepayable amount acquisition means (CB) for acquiring all or part of the payable consideration, which is the payable consideration to the person or / and the worker.

<47th solution>

Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. Based on the contract relationship information retention step (be) that holds the contract relationship information, which is the information related to the worker identification information that identifies the worker who is the person, and the labor claim information of the worker. All or part of the payable consideration, which is the consideration payable to the worker before the wage payment date set with the employer, is added to the employer identification information associated with the worker identification information of the worker. Repetitive payment, which is information that determines the labor receivable information acquisition step (bf) to be acquired based on the labor receivable information and the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor receivable information. Repeated payment date information retention step (ac), which retains day information in association with worker identification information, and payment method identification information, which is information that identifies the payment method for all or part of the payable consideration for workers. The payment method identification information acquisition step (ad) acquired in association with the worker identification information, the time information acquisition step (ae) in which the time information including the date is acquired, and the acquired time information are associated with the worker identification information. The judgment results in the repeat payment date relation judgment step (af) and the repeat payment date relation judgment step (af) for judging whether or not the relationship has become a predetermined relationship with the repeat payment date specified in the repeat payment date information are repeated. All or part of the payable consideration by the payment method identified by the acquired payment method identification information associated with the employee identification information when it is determined that the return payment date has a predetermined relationship. Repetitive payment processing history (ag) that performs payment processing, which is processing for payment, and repetitive payment processing history that retains the history of payment processing in the repetitive payment processing step (ag) in association with worker identification information. Retention step (ah) and
It is composed of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides a method of operating a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information.

<48th solution>

Based on the 47th solution, it accepts a payment method identification information retention step (aj) that retains multiple payment method identification information and one or more selections of payment method identification information that is retained in association with the worker identification information. Payment method selection Acceptance step (ak) and payment method payment consideration allocation step (am) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information. And, the payment method identification information acquisition step (ad) is configured to acquire the payment method identification information that has received the selection in association with the worker identification information (CPU, memory, bus). , Input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. It provides a method of operating a fixed-date prepayment system, which is a computer configured to perform calculations and realize various functions through the required data and information.

<49th solution>

Based on the 47th or 48th solution, the worker identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information are retained in association with each other. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a unique information retention step (an) for remittance, and software (BioS,) for operating each of the above steps. OS, device driver, etc.), software uses hardware resources to perform various calculations and realizes various functions through the required data and information. offer.

<Fifth solution>

Recurring payment to edit the recurring payment date information and / and the worker identification information held in the recurring payment date information retention step (ac) based on any one of the 47th to 49th solutions. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a daily information editing step (ap) and software (BIOS, OS,) for operating each of the above steps. It is composed of device drivers, etc.), and the software provides a method of operating a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information. ..

<51st solution>

A recurring payment date information recording step that records recurring payment date information and / and worker identification information in a recurring payment date information holding unit (AC) based on any one of the 47th to 50th solutions. From a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has ar) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides a method of operating a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information.

<52nd solution>

Based on any one of the 47th to 51st solutions, the start processing request acquisition step (as) for acquiring the start processing request for the prepaid wage request in association with the worker identification information and the start processing request are acquired. Start processing request to acquire time information including date Time information acquisition step (cd), labor receivable information associated with worker identification information, and recurring payment associated with worker identification information, if available. The prepayable amount, which is the amount that allows the prepayment request based on the daily information and, if available, all or part of the payable consideration paid on the recurring payment date associated with the worker identification information. The prepayable amount acquisition step (at) to be acquired, the prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the worker identification information within the range not exceeding the prepayable amount, and the prepayment of the acquired prepayment request amount. Prepaid processing step (ax) that performs prepaid processing, which is a process for ), And a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides a method of operating a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information.

<53rd solution>

Based on any one of the 47th to 52nd solutions, the worker identification of the processing result which is the result of the payment processing by the recurring payment processing unit (AG) or the prepaid processing by the prepaid processing unit (AX). The processing result acquisition step (az), which is acquired in association with the information, and the SNS identification information retention step (ba), which retains the SNS identification information used by the worker in association with the worker identification information, are associated with the processing result. Hardware (CPU, memory, bus, input / output device,) having a processing result notification step (bb) for notifying the processing result via the SNS identified by the SNS identification information associated with the worker identification information. It consists of a computer consisting of various peripheral devices (user interfaces, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps, and the software is required to perform various calculations using hardware resources. It provides a method of operating a fixed-date prepayment system, which is a computer configured to realize various functions through data and information.

<54th solution>

Based on the 50th to 53rd solutions based on the 49th solution, the remittance unique information retention step (an) includes worker identification information, payment method identification information, remittance unique information, and Further, an electronic device consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a remittance SNS identification information holding substep (bc) that is held in association with the remittance SNS identification information. It consists of a computer and software (BioS, OS, device driver, etc.) for functioning each of the above steps, and the software uses hardware resources to perform various calculations and realize various functions through the required data and information. Provided is a method of operating a fixed date prepayment system, which is a computer to be configured.

<55th solution>

On the basis of any one of the 47th to 54th solutions, the labor claim information acquisition step (bf) is performed as all or part of the payable consideration paid to the worker acquired in association with the worker identification information. Make each of the above steps work with a computer consisting of hardware (CPU, memory, bus, input / output device, various peripherals, user interface, etc.) that has a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount. Software (BioS, OS, device driver, etc.) for the purpose of the software, which is a computer that uses hardware resources to perform various calculations and realizes various functions through the required data and information. Provides a method of operating a prepaid system.

<56th solution>

Based on any one of the 10th to 18th solutions or the 47th to 55th solutions, all or part of the payable consideration associated with the worker identification information is less than the prescribed amount. , Judgment that payment processing is not possible based on the judgment results in the payment processing approval / disapproval judgment step (bg) and the payment processing approval / disapproval judgment step (bg) that determine whether the full payment can be processed by the recurring payment processing department (AG). Hardware (CPU, memory, bus, It consists of a computer consisting of input / output devices, various peripheral devices, user interfaces, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps, and the software uses hardware resources for various calculations. It provides a method of operating a fixed-date prepayment system, which is a computer configured to realize various functions through the required data and information.

<57th solution>

Based on the 55th solution based on the 52nd solution, the prepayment request amount acquisition step (aw) pays the prepayment request amount acquired in the prepayment request amount acquisition step (aw). Assuming that, on the closest recurring payment date set with the user, it is determined whether or not the fixed amount that has already been set to be paid on the recurring payment date cannot be paid. If the judgment result in (bj) and the fixed amount payment approval / disapproval substep (bj) is the judgment result that the payment cannot be made, the total amount of payment to the worker is changed to the amount that can pay the fixed amount. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a prepaid request amount acquisition substep (bk), which is a reduced prepaid request amount, and each of the above steps. It is composed of software (Bios, OS, device driver, etc.) for functioning, and software is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provides a method of operating a fixed date prepayment system.

<58th solution>

Based on any one of the 47th to 57th solutions, it retains wage payment date information, which is information indicating a predetermined wage payment date in association with worker identification information and / and employer identification information. Wage payment date information retention step (bm) and recurring payments that occur by the predetermined closing date on the retained predetermined wage payment date determined between the employer and the employer based on the worker's labor claim information. Of the payable consideration, which is the payable consideration excluding the amount paid and / and the prepaid prepayment request amount from the wages that would have been paid in the absence of these recurring payments and prepayments. Hardware (CPU, memory, bus, input / output device, various peripheral devices) having a balance payment processing step (bn) for performing a balance payment process, which is a process for payment so that all or part of the payment can be made. , User interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software uses hardware resources to perform various calculations and requires data and information. It provides a method of operating a fixed date prepayment system, which is a computer configured to realize various functions through.

<59th solution>

Based on the 58th solution, it is used when the balance payment processing step (bn) for processing the balance requires a fee for the remittance method used as the payment method for processing the balance. A hardware having a user-paid check processing step (ce) for the person to perform the slip processing (which may include both an electronic slip and a slip made of an actual sheet; the same shall apply hereinafter) for the person to bear the fee. It consists of a computer consisting of wear (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps, and the software is hardware. It provides a method of operating a fixed-date prepayment system, which is a computer configured to perform various calculations using ware resources and realize various functions through the required data and information.

<60th solution>

Based on the 58th or 59th solution, when the balance payment processing step (bn) for processing the balance requires a fee for the remittance means used as the payment method for processing the balance. In addition, the remittance operator-paid voucher processing step (cf) for the remittance operator to process the voucher for paying the fee (both an electronic voucher and a voucher made of an actual sheet may be included. The same shall apply hereinafter). (If the solution 59 is the basis, both the user and the remittance operator bear the burden), and the electronic component consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) It consists of a computer and software (Bios, OS, device driver, etc.) for functioning each of the above steps, and the software uses hardware resources to perform various calculations and realize various functions through the required data and information. Provided is a method of operating a fixed date prepayment system, which is a configured computer.

<61st solution>

Based on the 50th solution, the edit authority identification information retention step (cc) that retains the edit authority identification information that identifies the edit authority that is the authority to edit the recurring payment date information and / and the worker identification information. ), And the contract-related information holding step (be) has an editing authority additional holding substep (bp) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information. Then, in the recurring payment date information editing step (ap), the retained recurring payment date information and / and the worker identification information is identified by the identification information associated with the editing authority identification information (the person (). Hardware (CPU, memory, bus, input / output device, various peripheral devices) that has an editing authority restriction substep (br) that restricts editing including registration and deletion only to the user or / and worker). , User interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software uses hardware resources to perform various calculations and requires data and information. It provides a method of operating a fixed date prepayment system, which is a computer configured to realize various functions through.

<62nd solution>

Based on the 58th solution, the editing authority identification information retention step (cc) for retaining the editing authority identification information that identifies the editing authority, which is the authority to edit the wage payment date information and / and the worker identification information. The contract-related information holding step (be) has an editing authority additional holding substep (bp) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information. , The wage payment date information held in the wage payment date information retention step (bm) is registered only in the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a wage payment date information editing step (bs) that allows editing including erasing and each of the above steps. It is composed of software (BIOS, OS, device driver, etc.) for functioning, and the software is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provides a method of operating a fixed date prepayment system.

<63rd solution>

Based on any one of the 52nd to 62nd solutions, the time information acquisition step (ae) for acquiring time information for the prepayment processing described later, and the withdrawal of money, etc. by prepayment from the user. Withdrawal processing execution reservation date information acquisition step (bt), which is information indicating the execution date of withdrawal processing, which is the processing of the withdrawal processing execution reservation date information acquisition step (bt), and the prepaid processing step (ax) , Withdrawal processing is performed on the date specified by the withdrawal processing execution reservation date information based on the acquired withdrawal processing execution reservation date information and the time information acquired by the time information acquisition step (ae). A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a withdrawal execution processing sub-step (bw) that processes so that It is composed of software (BIOS, OS, device driver, etc.) for functioning, and the software is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provides a method of operating a fixed date prepayment system.

<64th solution>

Based on any one of the tenth to eighteenth solutions or the 47th to 63rd solutions, the user is associated with the user identification information in association with the user identification information. Deposit information acquisition step (bx) to acquire deposit information for recurring payment processing and / and prepaid processing performed on the employee or worker identified by the employee identification information or worker identification information, and repetitive The payment processing amount information acquisition step (by) for acquiring the payment processing amount information which is the information indicating the amount of the payment processing to be executed by the payment processing step (ag) and / and the prepaid processing step (ax), and the acquired payment. The payment processing execution judgment rule holding step (bz) that holds the payment processing execution judgment rule, which is a rule for determining whether to execute the payment processing to be executed based on the processing amount information and the deposit information, is retained. Hardware having a payment processing execution judgment rule (ca) for determining whether payment processing should be executed based on the payment processing execution judgment rule, the retained deposit information, and the acquired payment processing amount information. It consists of a computer consisting of (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps, and the software is hardware. It provides a method of operating a fixed-date prepayment system, which is a computer configured to perform various calculations using resources and realize various functions through the required data and information.

<65th solution>

Based on any one of the tenth to eighteenth solutions or the 47th to 63rd solutions, the user is associated with the user identification information in association with the user identification information. It has a deposit information acquisition step (bx) to acquire deposit information for repetitive payment processing and / and prepaid processing performed on the employee or worker identified by the employee identification information or worker identification information. The salary receivable information acquisition step (ab) or labor receivable information acquisition step (be), and / and the prepaid amount acquisition step (at) are based on the acquired deposit information and the salary receivable information and / and labor receivable information. Acquire all or part of the payable consideration that is the payable consideration to the subordinates and / and workers before the salary payment date or wage payment date specified with the employer. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a sub-step (cb) and software (BIOS, OS, device driver) for functioning each of the above steps. Etc.), and the software provides a method of operating a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information.

<66th solution>

Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. Based on the contract relationship information retention step (be) that holds the contract relationship information, which is the information related to the worker identification information that identifies the worker who is the person, and the labor claim information of the worker. All or part of the payable consideration, which is the consideration payable to the worker before the wage payment date set with the employer, is added to the employer identification information associated with the worker identification information of the worker. Repetitive payment, which is information that determines the labor receivable information acquisition step (bf) to be acquired based on the labor receivable information and the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor receivable information. Repeated payment date information retention step (ac), which retains day information in association with worker identification information, and payment method identification information, which is information that identifies the payment method for all or part of the payable consideration for workers. The payment method identification information acquisition step (ad) acquired in association with the worker identification information, the time information acquisition step (ae) in which the time information including the date is acquired, and the acquired time information are associated with the worker identification information. The judgment results in the repeat payment date relation judgment step (af) and the repeat payment date relation judgment step (af) for judging whether or not the relationship has become a predetermined relationship with the repeat payment date specified in the repeat payment date information are repeated. All or part of the payable consideration by the payment method identified by the acquired payment method identification information associated with the employee identification information when it is determined that the return payment date has a predetermined relationship. Repetitive payment processing history (ag) that performs payment processing, which is processing for payment, and repetitive payment processing history that retains the history of payment processing in the repetitive payment processing step (ag) in association with worker identification information. A computer consisting of holding steps (ah) and hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device) for functioning each of the above steps. The software is readable and executable in a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provide an operation program.

<67th solution>

Based on the 66th solution, it accepts a payment method identification information retention step (aj) that retains multiple payment method identification information and one or more selections of payment method identification information that is retained in association with the worker identification information. Payment method selection Acceptance step (ak) and payment method payment consideration allocation step (am) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information. And, the payment method identification information acquisition step (ad) is configured to acquire the payment method identification information that has received the selection in association with the worker identification information (CPU, memory, bus). , Input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. It provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform calculations and realize various functions through the required data and information.

<68th solution>

Based on the 66th or 67th solution, the worker identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information are retained in association with each other. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a unique information retention step (an) for remittance, and software (BioS,) for operating each of the above steps. It is composed of OS, device driver, etc.), and the software can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provides the operation program described in.

<69th solution>

Recurring payment to edit the recurring payment date information and / and the worker identification information held in the recurring payment date information retention step (ac) based on any one of the 66th to 68th solutions. A computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has a daily information editing step (ap) and software (BIOS, OS,) for operating each of the above steps. It is composed of device drivers, etc.), and the software is readable and executable in a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provide the operation program.

<70th solution>

A recurring payment date information recording step that records recurring payment date information and / and worker identification information in a recurring payment date information holding unit (AC) based on any one of the 66th to 69th solutions. From a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that further has ar) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software is configured to perform various calculations using hardware resources and realize various functions through the required data and information. It is a computer that is configured to realize various functions. offer.

<71st solution>

Based on any one of the 66th to 70th solutions, the start processing request acquisition step (as) for acquiring the start processing request for the prepaid wage request in association with the worker identification information and the start processing request are acquired. Start processing request to acquire time information including date The time information acquisition step (cd), the labor receivable information associated with the worker identification information, and the recurring payment associated with the worker identification information, if available. The prepayable amount, which is the amount that allows the prepayment request based on the day information and, if available, all or part of the payable consideration paid on the recurring payment date associated with the worker identification information. The prepayable amount acquisition step (at) to be acquired, the prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the worker identification information within the range not exceeding the prepayable amount, and the prepayment of the acquired prepayment request amount. Prepaid processing step (ax) that performs prepaid processing, which is a process for ), And a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. An operation program that is readable and executable in a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information. offer.

<72nd solution>

Based on any one of the 66th to 71st solutions, the worker identification of the processing result which is the result of the payment processing by the recurring payment processing unit (AG) or the prepaid processing by the prepaid processing unit (AX). The processing result acquisition step (az), which is acquired in association with the information, and the SNS identification information retention step (ba), which retains the SNS identification information used by the worker in association with the worker identification information, are associated with the processing result. Hardware (CPU, memory, bus, input / output device,) having a processing result notification step (bb) for notifying the processing result via the SNS identified by the SNS identification information associated with the worker identification information. It consists of a computer consisting of various peripheral devices (user interfaces, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps, and the software is required to perform various calculations using hardware resources. It provides an operation program that can be read and executed in a fixed-date prepayment system, which is a computer configured to realize various functions through data and information.

<73rd solution>

Based on the 68th Solution Based on the 69th to 72nd Solutions, the Remittance Unique Information Retention Step (an) includes worker identification information, payment method identification information, and remittance unique information. Further, an electronic device consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) having a remittance SNS identification information holding substep (bc) that is held in association with the remittance SNS identification information. It consists of a computer and software (BioS, OS, device driver, etc.) for functioning each of the above steps, and the software uses hardware resources to perform various calculations and realize various functions through the required data and information. It provides an operation program written readable and executable to a fixed-date prepayment system, which is a computer to be configured.

<74th solution>

On the basis of any one of the 66th to 73rd solutions, the labor claim information acquisition step (bf) is performed as all or part of the payable consideration paid to the worker acquired in association with the worker identification information. Make each of the above steps work with a computer consisting of hardware (CPU, memory, bus, input / output device, various peripherals, user interface, etc.) that has a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount. It is a computer that is composed of software (BioS, OS, device driver, etc.) for the purpose, and the software is a computer that uses hardware resources to perform various calculations and realizes various functions through the required data and information. Provides a readable and executable operating program for prepaid systems.

<75th solution>

Based on any one of the 19th to 27th solutions or the 66th to 74th solutions, all or part of the payable consideration associated with the worker identification information is less than the prescribed amount. , Judgment that payment processing is not possible based on the judgment results in the payment processing approval / disapproval judgment step (bg) and the payment processing approval / disapproval judgment step (bg) that determine whether the full payment can be processed by the recurring payment processing department (AG). Hardware (CPU, memory, bus, It consists of a computer consisting of input / output devices, various peripheral devices, user interfaces, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software uses hardware resources for various calculations. It provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to realize various functions through the required data and information.

<76th solution>

Based on the 71st Solution Based on the 74th Solution, it is assumed that the prepayment request amount acquisition step (aw) has paid the prepayment request amount acquired in the prepayment request amount acquisition step (aw). In this case, the fixed amount payment approval / disapproval substep (bj) is used to determine whether or not the fixed amount that has already been set to be paid on the recurring payment date cannot be paid on the closest recurring payment date specified with the user. If the judgment result in the fixed amount payment approval / disapproval substep (bj) is the judgment result that the payment cannot be made, the total amount paid to the worker is reduced to the amount that can be paid in the fixed amount. Prepaid request amount acquisition substep (bk) to be the request amount,
It consists of a computer consisting of its own hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. Provides an operating program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various operations using hardware resources and realize various functions through the required data and information.

<77th solution>

Based on any one of the 66th to 76th solutions, the wage payment date holding the wage payment date information which is the information indicating the predetermined wage payment date in association with the worker identification information and / and the employer identification information. The information retention step (bm) and the retention of the prescribed wage payment date determined between the employer and the employer based on the worker's labor claim information, were paid by recurring payments that occurred by the prescribed closing date. All or one of the payable consideration, which is the payable consideration excluding the amount and / and the prepaid prepayment request amount from the wages that would have been paid in the absence of these recurring payments and prepayments. The balance payment process step (bn), which processes the balance payment, which is the process for payment so that the department is payable,
It is composed of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various operations using hardware resources and realize various functions through the required data and information.

<78th solution>

Based on the 77th solution, when the balance payment processing step (bn) for processing the balance requires a fee for the remittance means used as the payment method for processing the balance, the user said. It has a user-paid voucher processing step (ce) for processing vouchers for paying fees (which may include both electronic vouchers and vouchers made of actual sheets; the same shall apply hereinafter).
It consists of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. It provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various operations using hardware resources and realize various functions through the required data and information.

<79th solution>

Remittance when the balance payment processing step (bn) for processing the balance requires a fee for the remittance method used as the payment method for processing the balance based on the 77th or 78th solution. It has a remittance operator-paid voucher processing step (cf) for the operator to process the voucher (which may include both an electronic voucher and a voucher made of an actual sheet; the same shall apply hereinafter) for the operator to bear the fee. (If the 78th solution is the basis, both the user and the remittance company bear the burden), and a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) And software (Bios, OS, device driver, etc.) for functioning each of the above steps, and the software is configured to perform various calculations using hardware resources and realize various functions through the required data and information. It provides a read-and-executable operating program to a fixed-date prepayment system that is a computer.

<80th solution>

Based on the 69th solution, there is an edit authority identification information retention step (cc) for retaining the edit authority identification information that identifies the edit authority, which is the authority to edit the recurring payment date information and / and the worker identification information. However, the contract-related information retention step (be) has an editing authority additional retention substep (bp) that retains the retained worker identification information and / and the employer identification information in association with the editing authority described later, and is repeated. The payment date information editing step (ap) identifies the retained recurring payment date information and / and the worker identification information by the identification information associated with the editing authority (employer and / and labor). Editing authority restriction sub-step (br) that sets restrictions so that only those who can edit, including registration and deletion, can perform editing.
It is composed of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various operations using hardware resources and realize various functions through the required data and information.

<81st solution>

Based on the 77th solution, it has an edit authority identification information holding step (cc) for retaining an edit authority identification information that identifies an edit authority that is an authority to edit wage payment date information and / and worker identification information. , The contract-related information retention step (be) has an editing authority additional retention substep (bp) that retains the retained worker identification information and / and the employer identification information in association with the editing authority identification information, and pays wages. Register and delete the wage payment date information held in the day information retention step (bm) only to the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. Allow editing including wage payment date information editing step (bs),
It is composed of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various operations using hardware resources and realize various functions through the required data and information.

<82nd solution>

Based on any one of the 71st to 81st solutions, in the time information acquisition step (ae) of acquiring time information for the prepayment processing described later, and the processing of withdrawal of money etc. by prepayment from the user. It has a withdrawal processing execution reservation date information acquisition step (bt) for acquiring withdrawal processing execution reservation date information, which is information indicating an execution date of a certain withdrawal process, and the prepaid processing step (ax) has been acquired. The withdrawal process is executed on the date specified by the withdrawal process execution reservation date information based on the withdrawal process execution reservation date information and the time information acquired by the time information acquisition step (ae). To make each of the above steps work with a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) that has a withdrawal execution processing sub-step (bw). Fixed date prepayment, which is a computer composed of software (BioS, OS, device driver, etc.) that is configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provide an operating program written to the system so that it can be read and executed.

<83rd solution>

Employee identification in which the user is associated with the user identification information in association with the user identification information on the basis of any one of the 19th to 27th solutions or the 66th to 82nd solutions. Deposit information acquisition step (bx) to acquire deposit information for recurring payment processing and / and prepaid processing performed on the employee or worker identified by the information or worker identification information, and recurring payment processing step. (ag) or / and the payment processing amount information acquisition step (by) to acquire the payment processing amount information which is the information indicating the amount of the payment processing to be executed by the prepaid processing step (ax), and the acquired payment processing amount information. And the payment processing execution judgment rule holding step (bz) that holds the payment processing execution judgment rule, which is a rule for judging whether to execute the payment processing that is going to be executed based on the deposit information, and the held payment. Payment processing execution judgment step (ca) that determines whether payment processing should be executed based on the processing execution judgment rule, the retained deposit information, and the acquired payment processing amount information.
It is composed of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides an operation program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various operations using hardware resources and realize various functions through the required data and information.
<84th solution>

Employee identification in which the user is associated with the user identification information in association with the user identification information on the basis of any one of the 19th to 27th solutions or the 66th to 82nd solutions. It has a deposit information acquisition step (bx) to acquire deposit information for repetitive payment processing and / and prepayment processing performed on an employee or worker identified by information or worker identification information, and payroll claim information. The acquisition step (ab) or labor claim information acquisition step (be), or / and the prepaid amount acquisition step (at) is based on the acquired deposit information and salary claim information and / and labor claim information with the employer. Acquire all or part of the payable consideration that is the payable consideration to the subordinates and / and workers before the salary payment date or wage payment date specified between the deposit information-dependent prepaid amount acquisition substeps ( cb),
It consists of a computer consisting of its own hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. Provides an operating program that can be read and executed by a fixed-date prepayment system, which is a computer configured to perform various operations using hardware resources and realize various functions through the required data and information.

According to the invention relating to the fixed date prepayment system according to claims 1 to 84 of the present invention, it is possible to obtain an excellent effect that the prepayment is repeatedly made on a stipulated date by a stipulated payment method.

Functional block diagram of the first embodiment Process flow diagram of the first embodiment The hardware diagram of the first embodiment Functional block diagram of the second embodiment The processing flow diagram of the second embodiment The hardware diagram of the second embodiment Functional block diagram of the third embodiment Process flow diagram of the third embodiment Hardware diagram of embodiment 3 Functional block diagram of the fourth embodiment The processing flow diagram of the fourth embodiment Hardware diagram of embodiment 4 Functional block diagram of the fifth embodiment The processing flow diagram of the fifth embodiment Hardware diagram of embodiment 5 Functional block diagram of the sixth embodiment The processing flow diagram of the sixth embodiment Hardware diagram of embodiment 6 Functional block diagram of the seventh embodiment The processing flow diagram of the seventh embodiment Hardware diagram of embodiment 7 Functional block diagram of the eighth embodiment 8th embodiment processing flow diagram 8th hardware diagram Functional block diagram of the ninth embodiment The processing flow diagram of the ninth embodiment Hardware diagram of embodiment 9 Functional block diagram of the tenth embodiment The processing flow diagram of the tenth embodiment Hardware diagram of embodiment 10 Functional block diagram of the eleventh embodiment 11th embodiment processing flow diagram Hardware diagram of embodiment 11 Functional block diagram of the twelfth embodiment The processing flow diagram of the twelfth embodiment Hardware diagram of embodiment 12 Functional block diagram of the thirteenth embodiment The processing flow diagram of the thirteenth embodiment The hardware diagram of the thirteenth embodiment Functional block diagram of embodiment 14 The processing flow diagram of the 14th embodiment Hardware diagram of embodiment 14 Functional block diagram of embodiment 15 The processing flow diagram of the 15th embodiment Hardware diagram of embodiment 15 Functional block diagram of embodiment 16 The processing flow diagram of the 16th embodiment Hardware diagram of embodiment 16 Functional block diagram of embodiment 17 17th embodiment processing flow diagram Hardware diagram of embodiment 17 Functional block diagram of embodiment 18 The processing flow diagram of the 18th embodiment Hardware diagram of embodiment 18 Functional block diagram of embodiment 19 The processing flow diagram of the 19th embodiment Hardware diagram of embodiment 19 Functional block diagram of embodiment 20 20th embodiment processing flow diagram Hardware diagram of embodiment 20 Functional block diagram of embodiment 21 21st embodiment processing flow diagram Hardware diagram of embodiment 21 Functional block diagram of embodiment 22 The processing flow diagram of the 22nd embodiment Hardware diagram of embodiment 22 Functional block diagram of embodiment 23 The processing flow diagram of the 23rd embodiment Hardware diagram of embodiment 23 Functional block diagram of embodiment 24 The processing flow diagram of the 24th embodiment Hardware diagram of embodiment 24 Functional block diagram of embodiment 25 The processing flow diagram of the 25th embodiment Hardware diagram of embodiment 25 Functional block diagram of embodiment 26 The processing flow diagram of the 26th embodiment Hardware diagram of embodiment 26 Functional block diagram of embodiment 27 The processing flow diagram of the 27th embodiment Hardware diagram of embodiment 27 Functional block diagram of embodiment 28 The processing flow diagram of the 28th embodiment Hardware diagram of embodiment 28 Schematic diagram of the overall configuration of the present invention Example of repeat setting specification screen in the present invention Example of repeat designated amount input screen in the present invention Example of repeat setting confirmation screen in the present invention Example of date reservation setting specification screen in the present invention Example of date reservation designated amount input screen in the present invention Example of date reservation setting confirmation screen in the present invention Explanatory drawing of the prepayment method based on the labor consideration already worked in the present invention Explanatory drawing of the prepayment method based on the labor consideration already worked in the present invention Explanatory drawing of payment processing abnormality information in this invention

<Premise of explanation of all embodiments>

<About the hardware that can constitute the present invention>

The present invention is an invention using a computer in principle, but it is realized by software, by hardware, and also by collaboration between software and hardware. In this case, the software uses hardware resources to perform various operations and realizes various functions through the required data and information. It can be said that information processing by software is concretely realized by using hardware resources.

The hardware that realizes all or part of each configuration requirement of the present invention is composed of the CPU, memory, bus, input / output device, various peripheral devices, user interface, etc., which are the basic configurations of the computer. Various peripheral devices include storage devices, interfaces such as the Internet, devices such as the Internet, LAN devices, Wifi devices, displays, keyboards, mice, speakers, cameras, videos, TVs, CD devices, DVD devices, Blu-ray devices, USB memory, USB. It may include memory interfaces, removable hard disks, general hard disks, projector devices, SSDs, telephones, fax machines, copiers, printing devices, movie editing devices, various sensor devices, and the like.

Further, this system does not necessarily have to be configured by one chassis, and may be configured by combining a plurality of chassis by communication. Further, the communication may be LAN, WAN, Wifi, Bluetooth (registered trademark), infrared communication, ultrasonic communication, and a part of the communication may be installed across national borders.

Further, each of the plurality of housings may be operated by a different entity, or may be operated by one entity. The operating entity of the system of the present invention may be singular or plural. In addition to this system, the invention can also be configured as a system including a terminal used by a third party and a terminal used by another third party. In addition, these terminals may be installed across national borders. Furthermore, in addition to this system and the terminal, even if related information of a third party, a device used for registering a related person, a device used for a database for recording the registered contents, etc. are prepared. good. These may be provided in this system, or may be provided outside this system and this system may be configured so that such information can be used.

<Satisfaction of the usability of the law of nature of the present invention in all embodiments>

The present invention functions in collaboration with a computer, communication equipment, and software. Not only is it possible to use ICT to process the processing that was previously performed by employees or workers and employers in interviews regarding prepayment, but also many complicated information exchanges, procedures, authentication, and settlement related to prepayment. Includes processing unique to ICT, such as determining the effects of ICT by ICT, and supporting the accumulation, retention, and exchange of effective information that meets all the necessary items that cannot be created without skill. Therefore, it is established as a so-called business model patent. In addition, various identification information, recurring payment date information, salary receivable information or labor receivable information are retained or processed in each part, and from this viewpoint as well, the present invention uses resources such as a computer as claims and specifications. Judging from the matters described in the above and the common general technical knowledge related to those matters, the invention of the present application utilizes the laws of nature.

<Applicant's understanding of the significance of using the laws of nature required by patent law>

The use of the laws of nature required by the Patent Law is to be useful industrially from the viewpoint that the invention must have industrial applicability and contribute to the development of the industry based on the legal purpose. It is required to ensure that the invention can be made. In other words, it is required to be industrially useful, that is, the effect of the invention declared at the time of filing can be reproduced with a certain degree of certainty by implementing the invention. From this point of view, the usability of the law of nature means that the functions of each of the invention-specific matters (invention constituent requirements), which are the constitutions of the invention for exerting the effect of the invention, are exerted by utilizing the law of nature. It is interpreted as good. Furthermore, the effect of the invention is only if there is a possibility of providing a predetermined usefulness to the user who uses the invention, and how the user feels or thinks about the usefulness. It should not be seen from the perspective of. Therefore, even if the effect that the user (employee, etc., user, etc.) obtains from this fixed date prepaid system is a psychological effect (convenient, reassuring, etc.), the effect itself is a required natural law. This is a non-target event for determining the availability of.

<Hardware configuration>

FIG. 3 is a diagram showing an example of the hardware configuration in the present embodiment. The hardware configuration of the fixed hardware system in this embodiment will be described with reference to FIG.

As shown in FIG. 3, the computer includes a chipset, a CPU, a non-volatile memory, a main memory, various buses, a BIOS, various interfaces, a real-time clock, and the like, which are configured on the motherboard. They work in tandem with operating systems, device drivers, and various programs. The various programs and various data constituting the present invention are configured to efficiently utilize these hardware resources to execute various processes.

≪Chipset≫

A "chipset" is a set of large-scale integrated circuits (LSIs) mounted on the motherboard of a computer and integrated with a communication function between an external bus of a CPU and a standard bus for connecting a memory and peripheral devices, that is, a bridge function. .. There are cases where a two-chipset configuration is adopted and cases where a one-chipset configuration is adopted. A north bridge is provided on the side close to the CPU and main memory, and a south bridge is provided on the side of the interface with a relatively low-speed external I / O on the far side.

(Northbridge)
The north bridge includes a CPU interface, a memory controller, and a graphic interface. The CPU may be responsible for most of the functions of the conventional north bridge. The north bridge is connected to the memory slot of the main memory via a memory bus, and is connected to the graphic card slot of the graphic card by a high-speed graphic bus (AGP, PCI Express).

(Southbridge)
The south bridge is connected to a PCI interface (PCI slot) via a PCI bus, and is responsible for I / O functions and sound functions with an ATA (SATA) interface, a USB interface, an Ethernet interface, and the like. Incorporating circuits that support PS / 2 ports, floppy disk drives, serial ports, parallel ports, and ISA buses that do not require or do not require high-speed operation is a hindrance to speeding up the chipset itself. Therefore, it may be separated from the chip of the south bridge and assigned to another LSI called a super I / O chip. Buses are used to connect the CPU (MPU) with peripheral devices and various control units. The buses are connected by a chipset. The memory bus used for connection with the main memory may adopt a channel structure instead of this in order to increase the speed. A serial bus or a parallel bus can be used as the bus. In the parallel bus, while the serial bus transfers data bit by bit, the original data itself or a plurality of bits cut out from the original data are grouped together and transmitted at the same time through a plurality of communication paths. A dedicated clock signal line is provided parallel to the data line to synchronize data demodulation on the receiving side. It is also used as a bus that connects a CPU (chipset) and an external device, and includes GPIB, IDE / (parallel) ATA, SCSI, and PCI. Since there is a limit to the speedup, the data line may be a serial bus in the improved version of PCI Express or the improved version of serial ATA of parallel ATA.

≪CPU≫

The CPU sequentially reads, interprets, and executes an instruction sequence called a program in the main memory, and outputs information consisting of signals to the main memory as well. The CPU functions as a center for performing calculations in the computer. The CPU is composed of a CPU core part that is the center of calculation and a peripheral part thereof, and a register and a cache memory inside the CPU, an internal bus that connects the cache memory and the CPU core, a DMA controller, a timer, and a north bridge. The interface with the connection bus with is included. A plurality of CPU cores may be provided in one CPU (chip). Further, in addition to the CPU, processing may be performed by a graphic controller (GPU) or a floating-point arithmetic unit (FPU). The description in the embodiment is of the two-core type, but is not limited to this. It is also possible to incorporate a program in the CPU.

≪Non-volatile memory≫

(HDD)

The basic structure of a hard disk drive consists of a magnetic disk, a magnetic head, and an arm on which the magnetic head is mounted. As the external interface, SATA (ATA in the past) can be adopted. A sophisticated controller, such as SCSI, is used to support communication between hard disk drives. For example, when copying a file to another hard disk drive, the controller can read the sector and transfer it to another hard disk drive for writing. At this time, the memory of the host CPU is not accessed. Therefore, it is not necessary to increase the load on the CPU.

≪Main memory≫

The CPU directly accesses and executes various programs on the main memory. The main memory is a volatile memory and DRAM is used. The program on the main memory is expanded from the non-volatile memory onto the main memory in response to the program start command. After that, the CPU executes the program according to various execution instructions and execution procedures in the program.

≪Operating system (OS)≫

The operating system is used to manage the resources on the computer for the application to use, to manage various device drivers, and to manage the computer itself, which is the hardware. Small computers may use firmware as the operating system.

≪BIOS≫

The BIOS is the one that causes the CPU to execute the procedure for starting up the hardware of the computer and operating the operating system, and most typically, the hardware that the CPU first reads when receiving the start command of the computer. .. The address of the operating system stored in the disk (nonvolatile memory) is described here, and the operating system is sequentially expanded to the main memory by the BIOS expanded in the CPU and put into an operating state. The BIOS also has a check function for checking the presence or absence of various devices connected to the bus. The result of the check is saved in the main memory and made available by the operating system as appropriate. The BIOS may be configured to check external devices and the like. The above is the same for all embodiments.

As shown in FIG. 3, the present invention can basically be configured by a general-purpose computer program and various devices. The operation of the computer basically takes the form of loading the program recorded in the non-volatile memory into the main memory and executing the processing in the main memory, the CPU, and various devices. Communication with the device is done via an interface connected to the bus line. The interface may include a display interface, a keyboard, a communication buffer, and the like.

<Terminals used by employees or workers Smartphones, mobile phones>

Unlike the above, the chipset is omitted in smartphones, mobile phones, tablet terminals, etc., which are terminals used by employees or workers who appear subordinately in the present invention. As a typical hardware, a hardware called SoC that realizes a computer function with one chip is used. The communication function block communicates directly with the CPU by bus, and the memory, graphics function block, and voice processing function block also directly communicate with each other. A USB interface is connected to the bus outside the chip. The display interface outside the chip is connected to the graphics function block, and the voice interface is also connected to the voice processing function block. The cooperative relationship between basic software and hardware resources is similar to that of hardware that processes via the chipset described above.

<Specific examples of terminals used by employees or workers>

The memory of the terminal used by the employee or the worker is via the communication of the fixed date prepayment system, which is software for communicating with the fixed date prepayment system, which is a computer composed of the hardware described later, via the Internet. An application for use, in some cases, a browser for accessing the web service of the fixed date prepayment system and browsing the web, an application for using electronic money, and for operating bank account information via the Internet. It is preferable that one or more of a bank application, various SNS applications, and in some cases, an application for paying utility charges, rent, and the like are included. In addition, it is unique for remittance including employee identification information or worker identification information, information on recurring payment dates, payment method identification information, icon information for payment method selection, bank account number, identification information for using electronic money. Any one or more of the information and various data may be included, and these information and various data are configured to be held and processed by the above-mentioned various applications and the like.
Hereinafter, embodiments of the present invention will be described with reference to the illustrated examples.

<Embodiment 1 Mainly relating to the invention according to claim 1> Basic

<Outline of Embodiment 1>

The first embodiment is a fixed date prepayment system for repeatedly making a so-called prepayment of salary to an employee on a predetermined date by a designated payment method.

<Embodiment 1 Configuration>

As shown in FIG. 1, the fixed date prepayment system (0100) of the first embodiment includes an employment relationship information holding unit (AA) (0101), a payroll receivable information acquisition unit (AB) (0102), and a recurring payment date. Information holding unit (AC) (0103), payment method identification information acquisition unit (AD) (0104), time information acquisition unit (AE) (0105), and recurring payment date relationship judgment unit (AF) (0106). It also has a recurring payment processing unit (AG) (0107) and a recurring payment processing history holding unit (AH) (0108).

<Explanation of Embodiment 1 Configuration>

<Embodiment 1 Employment-related Information Holding Department (AA) (0101)>

The "Employment Relations Information Retention Department (AA)" (0101) associates user identification information that identifies an employer with employee identification information that identifies an employee employed by an employer based on an employment relationship. Retains employment-related information, which is information that has been collected. This employment-related information is registered by the administrator of the fixed date prepaid system (0100), or is registered from an external terminal via the Internet with the authority of the user who is the user.

An "employer" is a person who employs an employee, regardless of whether it is a natural person, a corporation, a union, or the like. "User identification information for identifying a user" is information for uniquely identifying a user in this system, and the format of the information does not matter. Further, it is preferable that various information is retained or receivable in association with the user identification information. For example, company name, store name, location, telephone number, fax number, bank account information, email address, homepage address, representative name, representative telephone number, representative or company, store SNS identification information, user or representative Electronic money identification information, etc.

An "employee" is a person employed by an employer and is, in principle, a natural person. However, it is not limited to one person, and may be a group or the like. That is, in this case, one subordinate identification information is attached to the group.

There are various forms of "employment relations". In addition to the so-called relationship between companies and employers and regular employees, the relationship between dispatched workers and dispatch sources or destinations, the relationship between contract employees and employers with a fixed period, and the relationship between part-time workers and employers. Relationships, relationships between short-time regular employees and employers, relationships between workers who work under a business consignment (contract) contract and employers who are business consignors, relationships between domestic workers and business consignors, self-employed teleworkers And the relationship with the user who is the consignor. Therefore, in a broad sense, an employment relationship is defined as a relationship in which the consideration for some kind of labor or the deliverables produced by the labor is received from the employer or the like.

In the fixed date prepaid system (0100), in principle, we do not investigate whether the registered employment relationship is a legally appropriate employment relationship and is false information. If there is a registration by a genuine user or a person to whom authority has been delegated by the user, it will be operated as having an employment relationship. However, a document or the like that can prove the employment relationship may be configured to be retained in the fixed date prepaid system (0100) in association with the user identification information and the employee identification information. Examples of this document include a salary payment statement and an employee ID card. In addition, if there is an employment-related information server outside and information certifying the employment relationship between the employer and the employee can be obtained, the employment-related information server is searched to see if the registration is genuine and the result is obtained. It can also be configured to secure registration accordingly.

<Embodiment 1 Salary Receivable Information Acquisition Department (AB) (0102)>

The “Salary Claim Information Acquisition Department (AB)” (0102) is the payable consideration that is the consideration that can be paid to the subordinate before the salary payment date determined with the employer based on the employee's salary claim information. All or part of is acquired based on the user identification information associated with the employee identification information of the employee.

"Salary claim" is also called "salary claim" and has the same meaning. Salary as compensation for labor and deliverables is also called salary or wage. This salary takes a certain period of time to be paid to employees. For example, the salary for the previous month is paid on the 25th of the following month, for example. However, employees have the right to receive salary as compensation for labor that has already been done or deliverables that have been submitted and passed the acceptance inspection even if the salary payment date has not been reached, and this is called a salary claim. ..

"Salary receivable information" is information on salary receivables, but is mainly information indicating the amount of the salary receivables. In addition, information on the scheduled payment date and payment method of the salary may be included. In addition, it may contain information about the labor and deliverables that caused the salary. Labor may include information on working hours, such as when and how many hours worked, and how many hours worked in total, and information indicating where the work was done.
It may also include information such as type, quantity, quality and yield of deliverables.

<Embodiment 1 Repeated payment date information holding unit (AC) (0103)>

The "Repeat Payment Date Information Retention Department (AC)" (0103) is information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to an employee based on salary receivable information. Keep recurring payment date information associated with employee identification information.

"Payable consideration paid to employees based on salary receivable information" means, for example, if there is N yen in salary receivables (N is a natural number), the total amount is N yen or a fixed amount less than N yen. The amount of money is M yen (N> M: M is a natural number). However, if the prepaid amount is increased too much, the future life of the employee (after this month, etc.) may become unstable, so the payable consideration as prepaid is N yen x safety factor S. preferable. It is considered appropriate that the safety factor S is about 10% to 30%. That is, N × 0.1 to N × 0.3 is preferable as a payable consideration or a part of the payable consideration.

The "payable consideration" may theoretically be the same as the amount of salary receivables, or may be less than the amount of salary receivables. "Part of the payable consideration" is the amount less than the amount of salary receivables.

"Pay repeatedly" means, most typically, paying at the same intervals as the salary payment interval. For example, if the employee has a monthly salary system, he / she can pay on the same day of every month, on the specified day of the week from the beginning of the month, or on what day of the week (for example, the third Monday) from the beginning of the month. good. Alternatively, if the employee's payment date is predetermined, such as utility bills and utility charges, the payment date and payment interval may be set for each. For example, if utility charges such as water charges are on the 10th day of each month and utility charges are on the 12th day of each month, the 10th and 12th days of each month can be used as repeated payment dates. However, it may be other than that. For example, the interval may be half or double the salary payment interval. Since the payment date can be specified on the fixed date prepayment system (0100) side, it is preferable to configure the repetitive payment so that the payment is made even if there is no request from the employee.

“Repeated payment date information” is therefore information for specifying the date for repeated payment, and in principle, the information indicating the date is used. The date is information indicating the date. However, this may include information indicating the time. For example, it is information such as 10 am, 1 pm, and 1:30 pm. This recurring payment date date information is associated with the employee identification information to acquire the recurring payment date calculation rule holding unit that holds the recurring payment date calculation rule, and the recurring payment date using the rule. There is a recurring payment date acquisition unit, and the recurring payment date information holding unit (AC) (0103) can also be configured to hold the recurring payment date acquired by the recurring payment date acquisition unit. As mentioned above, the recurring payment date calculation rule is the same day of every month, the specified day of the week from the beginning of the month, the day of the week from the beginning of the month (for example, the third Monday), and the 10th day of every month. It is preferable that a plurality of calculation formulas are prepared according to the method of repeating the recurring payment date such as 12th and 12th.

The recurring payment date information may be associated with or may be included in the recurring payment date information. If an employee has multiple recurring prepayments, it is used to identify them.

<Implementation 1 Payment method identification information acquisition unit (AD) (0104)>

The "Payment Method Identification Information Acquisition Department (AD)" (0104) acquires payment method identification information, which is information for identifying payment methods for all or part of the payable consideration for employees, in association with employee identification information. do.

"Payment method identification information" is information that identifies a payment method from an employer to an employee. As mentioned above, payment methods include PayPay (registered trademark), LINE Pay (registered trademark), iD (registered trademark), WAON (registered trademark), nanaco (registered trademark), Rakuten Edy (registered trademark), and QUICPay (registered trademark). Electronic money used by employees such as trademark), Suica (registered trademark), apple pay (registered trademark), and white card (registered trademark) may be paid using the point charge or remittance function, or to a bank account. You may make a transfer, transfer to a securities account, or, in some cases, charge a credit card with a charge function or a cash card with a charge function. When charging points to electronic money, the management company or management company of the fixed date prepayment system (0100) concludes a contract with each electronic money company and identifies the electronic money of the employee who uses the electronic money in a predetermined bank account. It is preferable to construct a system to automatically charge by transferring a predetermined amount of money together with information.

"Association with employee identification information" may associate one payment method identification information with one employee, and by design, a plurality of payment method identification information with one employee identification information. May be associated. When multiple payment method identification information is associated with one employee identification information, the fixed date prepayment system (0100) makes multiple payment methods optional every time the payment date and the date of a predetermined relationship are reached. It is also possible to select a payment method identified by the payment method identification information and configure it to be used for payment, and the employee each time the date of the recurring payment date and a predetermined relationship or a date close to it is reached. One payment method may be configured to be used by the fixed date prepayment system (0100) by allowing an employee who can be identified by the identification information to select a specific payment method identification information among a plurality of payment method identification information. .. Further, even if a plurality of payment method identification information is associated with one employee identification information, if there are multiple recurring payment dates, different payment method identification information is used for each recurring payment date. In association with each other, the payment method identification information can be configured to be associated with the payment date on a one-to-one basis.

"Acquisition" of payment method identification information is repeated when a judgment result is obtained by the Repeated Payment Date Relationship Judgment Unit (AF) (0106), which will be described later, that the judgment result has a predetermined relationship. Obtain the payment method identification information that is further associated with the employee identification information that is associated with the payment date information. This payment method identification information is therefore preferably held in the fixed date prepayment system (0100) in advance in association with the employee identification information. Of course, it is held externally and can be configured to be acquired from the outside.

For example, an employee who receives a remittance to electronic commerce reads the bar code on the transfer form with an application for approval of a smartphone that can use electronic commerce, and registers with the charged electronic money or each payment. You can pay by the method you have set (bank account or credit card).

An application for using the fixed date prepaid system (0100) is installed in the employee's smartphone, and it is linked to this or integrated with the smartphone payment (utility, gas / water charges, rent, utility charges, etc.) It is convenient to enable the function (for approval).

For example, when prepayment is made to electronic money, the application that can be used for the fixed date prepayment system (0100) pushes to the user who is an employee that the prepayment has been made and that it is the payment date of utilities etc. It is conceivable to notify and indicate the amount so that payment can be completed with one push.

With the payment method identification information and the employee identification information, the employee's bank account information in the payment method identified by the payment method identification information and the employee's unique information for charging, remittance, and transfer of electronic money are acquired. It needs to be configured to allow it. For example, it is a unique information acquisition unit. The recurring payment processing unit (AG) (0107), which will be described later, will actually perform payment processing using the bank account information and unique information.

The payment method identification information may be associated with the repetitive payment date identification information described above. This is because the payment method is individually set for each of a plurality of recurring payment dates. In this case, the recurring payment processing unit (AG) (0107), which will be described later, is responsible for the payment associated with the recurring payment date information or the recurring payment date identification information included therein. Perform payment processing according to the payment method identified by the method identification information.

<Embodiment 1 Time Information Acquisition Unit (AE) (0105)>

The "time information acquisition unit (AE)" (0105) acquires time information including a date. The "time information" is like information that can be read from a calendar, and in principle, refers to information on the date, but may include information indicating the time. The time may be information indicating hours, minutes, and seconds, information indicating hours and minutes, or information indicating only hours. In principle, time information refers to the current time information. This is because the payment must be made as promised to the employee who expects to be paid in advance on the recurring payment date. The acquisition source may be from an information source of time information on the Internet, or from a clock unit having a clock function provided in a fixed date prepaid system (0100).

<Embodiment 1 Repeated Payment Date Relationship Judgment Department (AF) (0106)>

The “Repeat payment date relationship judgment unit (AF)” (0106) has determined whether the acquired time information has a predetermined relationship with the repetitive payment date defined by the repetitive payment date information associated with the employee identification information. to decide. A predetermined relationship is a relationship in which the date specified in the recurring payment date information and the date indicated in the time information match, or the date indicated in the recurring payment information and the date indicated in the time information. The date is approaching a predetermined date, the date and time determined by the recurring payment information and the date and time indicated by the time information are approaching to a predetermined time, and so on. It is natural that the date, etc., which has a predetermined relationship with the recurring payment date information and the date, etc., which is determined by the time information, have a predetermined relationship, but it is agreed.

<Embodiment 1 Repeated Payment Processing Unit (AG) (0107)>

When the "repeated payment processing unit (AG)" (0107) determines that the judgment result of the repetitive payment date relation judgment unit (AF) (0106) has a predetermined relationship with the repetitive payment date. The payment process, which is the process for payment of all or part of the payable consideration by the payment method identified by the payment method identification information acquired in association with the employee identification information, is performed. The "processing for payment" may be the payment processing itself, or may not be the payment processing itself, but may be a processing performed for the payment processing. "Payment" means transfer processing to the bank account of the electronic money operating company, transfer processing to the employee's bank account, transfer processing to the bank account of the electronic money operating company, transfer processing to the employee's bank account, employee It includes various things such as charge processing for the electronic money of the person and transfer (transfer point) processing of the electronic money of the employee.

<Embodiment 1 Repeated payment processing history holding unit (AH) (0108)>

The “Repeat payment processing history holding unit (AH)” (0108) holds the history of payment processing in the recurring payment processing unit (AG) (0107) in association with the employee identification information. This includes, in addition to the information indicating that the payment processing has been completed, information on the processing result such as the result of the payment after the payment processing, and information indicating that the payment processing could not be executed. May include.

<Embodiment 1 Hardware Configuration>

As shown in FIG. 3, the present invention and the present embodiment can basically be composed of a general-purpose computer program and various devices. The operation of the computer basically takes the form of loading the program recorded in the non-volatile memory into the main memory and executing the processing in the main memory, the CPU, and various devices. Communication with the device is done via an interface connected to the bus line. The interface may include a display interface, a keyboard, a communication buffer, and the like.

As shown in FIG. 3, the employment relationship information retention program, the salary receivable information acquisition program, the repeat payment date information retention program, the payment method identification information acquisition program, the time information acquisition program, and the repeat payment date relationship. The judgment program, the repetitive payment processing program, and the repetitive payment processing history holding program are held in the non-volatile memory, and these programs are read into the main memory based on the execution instructions of the series of programs to be main. It is expanded in memory and these programs are executed based on the operation start instruction.

Here, the employment relationship information retention program is information that associates the user identification information that identifies the user with the employee identification information that identifies the employee employed by the user based on the employment relationship. Hold information. It can also be configured to run an employment-related information acquisition program as a prerequisite for retention.

Next, the salary receivable information acquisition program sets the employee's payable consideration, which is the consideration that can be paid to the subordinate before the salary payment date determined with the employer based on the employee's salary receivable information. Obtained based on the user identification information associated with the person identification information. The acquisition may be obtained from a peripheral device, particularly a storage, a recording medium, an attached information of an e-mail, or a computer used by a user via the Internet. If an attendance management system that manages and records the work status of employees is provided separately from this system, it is also possible to obtain payable consideration via the Internet as described above.

The recurring payment date information retention program provides recurring payment date information, which is information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to the employee based on the payroll receivable information. Retain in association with identification information. There may be a recurring payment date information acquisition program as a prerequisite for retention. This repeat payment date information acquisition program typically acquires the repeat payment date information desired by the employee from a terminal or the like used by the employee via the Internet.

The payment method identification information acquisition program acquires payment method identification information, which is information that identifies the payment method for all or part of the payable consideration for employees, in association with the employee identification information. This payment method identification information acquisition program typically acquires payment method identification information that identifies the payment method desired by the employee via the Internet from a terminal or the like used by the employee.

The time information acquisition program acquires time information including a date. The acquisition source of the time information may be a clock consisting of a real-time clock built in a fixed date prepayment system which is a computer, or may be configured to acquire the time information from an external time server via the Internet.

The recurring payment date relationship determination program determines whether the acquired time information has a predetermined relationship with the recurring payment date defined in the recurring payment date information associated with the employee identification information. Judgment is made according to the relationship judgment rules described in this program. As an example of the relationship judgment rule, for example, the recurring payment date and the date indicated by the time information are within a predetermined time. As the predetermined time, for example, 24 hours, 12 hours, and the like can be considered. If there is no time information on the recurring payment date and only information on the date, it can be configured to make a judgment in relation to midnight on that date.

The recurring payment processing program acquires the employee identification information in association with the recurring payment date when the judgment result in the recurring payment date relationship judgment step (af) is the judgment result that the repetitive payment date has a predetermined relationship. Perform payment processing, which is processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information. The payment process is as described above.

The recurring payment processing history retention program retains the history of payment processing in the recurring payment processing step (ag) in association with the employee identification information. It is preferable that the history of recurring payment processing held here can be viewed by the user or the employee from the terminal used by the user via the Internet. That is, the recurring payment processing history viewing program is configured to be provided in the fixed date prepayment system which is a computer.

These programs acquire, retain, and perform other processing such as user identification information, employee identification information, employment relationship information, recurring payment date information, payment method identification information, and time information according to their functions. .. This information is also held in the non-volatile memory, and is read and expanded in the main memory as needed. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 1 Processing flow>

As shown in FIG. 2, in the present invention and the present embodiment, the following processing is performed as an operation method of the fixed date prepaid system which is a computer described in the description of the hardware of the first embodiment. This process can also be described as an operation program of a fixed date prepaid system which is a computer.

As shown in FIG. 2, this process is information in which the user identification information that identifies the user and the employee identification information that identifies the employee employed by the user are associated with each other based on the employment relationship. The consideration that can be paid to the subordinate before the salary payment date determined between the employment relationship information retention step (aa) (S0201) that retains the employment relationship information and the employer based on the employee's salary claim information. The salary receivables information acquisition step (ab) (S0202), which acquires the payable consideration based on the employer identification information associated with the employee identification information of the employee, and the employee based on the salary receivable information. Recurring payment date information retention step (ac) (S0203) for retaining recurring payment date information, which is information that determines the recurring payment date, for repeatedly paying all or part of the payable consideration value paid in ), The time information acquisition step (ae) (S0204) to acquire the time information including the date, and the recurring payment date defined by the recurring payment date information in which the acquired time information is associated with the employee identification information. The judgment result in the repeat payment date relationship judgment step (af) (S0205) and the repeat payment date relationship judgment step (af) (S0205) for determining whether or not the relationship has been established has a predetermined relationship with the repeat payment date. Acquisition of payment method identification information that is acquired by associating payment method identification information, which is information that identifies the payment method for all or part of the payable consideration for employees, with the employee identification information when it is determined that the payment has been made. Step (ad) (S0206) and payment processing, which is the processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the employee identification information. The recurring payment processing history step (ah) that retains the payment processing history in the recurring payment processing step (ag) (S0207) and the recurring payment processing step (ag) (S0207) in association with the employee identification information. ) (S0208) and the fixed date prepayment system, which is a computer.

<Example of using fixed date prepaid system>
FIG. 85 shows an overall schematic configuration example of the fixed date prepaid system of the present invention. The terminal (8501) of the user A and the terminal (8502) of the user B are connected to the Internet line (8500). Attendance management information of each employee employed is stored in the terminal (8501) of the user A and the terminal (8502) of the user B, and serves as a basis for calculating the employee's loan receivable information. In addition, a fixed-date prepayment system operated by a wage prepayment agency or a server (8503) that stores and operates an operation program of the system, a server of bank A (8504), a server of bank B (8505), and an employee A A smartphone (8506), a smartphone of employee B (8507), a server of an electronic money operating company (8508), an SNS operating company (8509), etc. are also connected to the Internet. Although it is described as worker A and worker B in FIG. 85, in the description in the first embodiment, it will be read as an employee. As described above, the fixed date prepayment system operated by the wage prepayment agency different from the employer receives the recurring payment information registration from the employee and holds the recurring payment date information. If Employee A is employed by User A, the payable consideration will be determined based on the attendance management information and recurring payment information in User A's terminal, whether it is User A's terminal or a fixed date prepayment system. Calculate with or both. When the recurring payment date arrives, the fixed date payment system processes the payment by the payment method (financial institution, electronic money, SNS remittance means, etc.) specified by the employee A.

An example of an employee's work of registering actual recurring payment date information using his / her own smartphone will be described with reference to FIG. 86. FIG. 86a is an example of a screen for setting a repeat payment date, FIG. 86b is an example of an input screen for the prepaid application amount to be paid on each repeat payment date, and FIG. 86c is an example of a setting confirmation screen after the completion of input of the repeat payment date. FIG. 86abc is an example of a screen and is not limited to this layout and usage.
First, on the screen of FIG. 86a, the date at the time when the setting input is started is acquired from the time information in the smartphone and displayed as the current date, and the calendar of the corresponding month is also displayed at the start of operation. In FIG. 86a, the time of operation is September 2, 2020. Select the year and month to be input (8601). Return from the initially displayed September 2020, or press the left and right triangle buttons to proceed. If you return from the current time, you can refer to the history when you applied for payment in the past. The corresponding calendar (8602) is displayed immediately below. September 11, which is the date (8603) circled by a dotted line, represents a date that has already been registered. It is September 24th, which is the date (8604) that is displayed in black and white inversion, that we are going to additionally register this time.
It is more preferable to configure it so that it can be added only when the total amount of recurring payments including the newly added amount is small compared to the amount obtained by multiplying the labor consideration by the safety factor.
For the addition operation, you can click (press) the part of the date to be added directly on the calendar, or in the start date selection field (8605) under the calendar, for each year, month, day, the triangle button next to each field. You may press to enter individual selection. Below the start date is the repeat setting. It can be set weekly (ie, every day of the week) (8606) or monthly (in the case of FIG. 86a, specified on either the 24th or the 4th Thursday of each month) (8607). Although not shown, it may be possible to set multiple months (bimonthly, quarterly, etc.), yearly, and the like. As for the setting of the end date of the recurring payment (8608), either the end date is not specified (that is, the recurring payment is executed unless the registration is deleted) or the recurring payment is specified (repeated payment until the designated end date). After entering the date, enter the amount next. If only the date is entered and the amount has not been entered yet, it is preferable that only the amount input button (8609) and the cancel button (8611) are displayed in an operable state, or the other buttons are not displayed. Press the amount input button (8609) to proceed to the prepaid application amount input screen shown in FIG. 86b.

On the prepaid application amount input screen shown in FIG. 86b, the transfer destination (8613) is selected as the payment method. In the figure, the Yurakucho branch of Chiyoda Bank is selected. Below the payee's bank account, the amount that can be paid in advance at the time of application is displayed as 127,000 yen. You can choose to pay the full balance or specify the amount (8614). To specify the amount, touch the amount input field (8615) and then enter it with the numeric keypad. If you start operating the numeric keypad directly after selecting the transfer, you may consider that you have selected the specified amount. Further, when the amount input field is pressed, options in units of 1000 yen are displayed in the pull-down menu and the selection may be made. After entering the amount, press the enter button (8616) at the bottom of the screen. To cancel the input work, press the cancel button (8618), and to cancel the input and return to the date selection screen, press the back button (8617). When the enter button (8616) is pressed, the screen returns to the setting screen shown in FIG. 86a. To add a repeat payment date, press the add button (8610), then enter the date and set the amount in the same way. When the repeat payment date setting is completed, the input completion button (8612) is pressed to move to the setting confirmation screen shown in FIG. 86c.
In FIG. 86c, the left and right triangular buttons of the year / month display (8619) can be used to check the setting status of the previous / next year / month. Date circled by dotted line (8620) September 11 is the date already registered, the date added this time is the date circled by solid line (8621), and September 24 is displayed by circled by solid line. Has been done. Below the calendar, the currently set recurring payment dates, amounts, and financial institutions are listed. It is possible to easily set the recurring payment date by such an operation on the smartphone. Note that this setting method is a specific example of operation, and can be appropriately designed without being limited to this screen.

<Effect of Embodiment 1>

In the present embodiment, since the advance payment of a predetermined amount is made in principle by the selected payment method on a fixed date set in advance, it is constant between the salary payment date and the next salary payment date. It is possible to surely make up for the lack of funds for employees who are short of funds.

<Embodiment 2 Mainly Related to the Invention of Claim 2> Multiple Payment Methods

<Outline of Embodiment 2>

In the second embodiment, based on the first embodiment, an employee or the like can select a payment method, and all or a part of the payable consideration can be assigned to each selected payment method.

<Embodiment 2 Configuration>

As shown in FIG. 4, the fixed date prepayment system (0400) of the second embodiment has the employment relationship information holding unit (AA) (0401) and the salary receivable information acquisition unit (AB) (0402) which are the configurations of the first embodiment. ), The recurring payment date information holding unit (AC) (0403), the payment method identification information acquisition unit (AD) (0404), the time information acquisition unit (AE) (0405), and the recurring payment date relationship determination. It has a unit (AF) (0406), a recurring payment processing unit (AG) (0407), and a recurring payment processing history holding unit (AH) (0408). It has an information holding unit (AJ) (0409), a payment method selection reception unit (AK) (0410), and a payment method payment consideration allocation unit (AM) (0411). In the following description, the description of the configuration described in the first embodiment will be omitted, and only the configuration peculiar to the present embodiment will be described.

<Explanation of Embodiment 2 Configuration>

<Implementation 2 Payment method identification information holding unit (AJ) (0409)>
The "payment method identification information holding unit (AJ)" (0409) holds a plurality of payment method identification information. "Payment method identification information" is information for identifying a payment method for making a fixed date prepayment. It may be information indicating the type of processing such as bank account transfer, electronic money use, cash card charge, credit card charge, etc., Mitsubishi UFJ bank account use, Mitsui Sumitomo bank account use, Resona bank account use, Mizuho Bank Account use, Saitama Sona bank account use, PayPay (registered trademark) use, LINE Pay (registered trademark) use, iD (registered trademark) use, WAON (registered trademark) use, nanaco (registered trademark) use, Rakuten Edy (registered trademark) use ) Use, QUICPay (registered trademark) use, Suica (registered trademark) use, apple pay (registered trademark) use, white card (registered trademark) use, etc. to identify the bank where the employee has an account, used by the employee What specifies the type of electronic money to be used, VISA (registered trademark) use, MasterCard (registered trademark) use, JCB (registered trademark) use, AMEX (registered trademark) use, Diners (registered trademark) use, UnionPay (UnionPay) ) (Registered trademark) may be used to specify a credit card.

Furthermore, if the system allows, information that identifies T point (registered trademark) card, Rakuten point (registered trademark) card, Ponta (registered trademark) point card, d point (registered trademark) card, JRE POINT (registered trademark) card, etc. It may be. In this case, the fixed date prepaid system (0400) is configured to allow remittance (sending points) of points. The payment method identification information held in this section is not yet associated with the subcontractor identification information. It is preferable that the fixed date prepayment system (0400) has a payment method identification information editing unit for deleting the payment method identification information held here or adding the payment method identification information here.

<Embodiment 2 Payment method selection reception unit (AK) (0410)>

The "Payment Method Selection Reception Unit (AK)" (0410) accepts one or more selections of payment method identification information held in association with the employee identification information. The selected payment method identification information and the employee identification information associated therewith are acquired by the payment method identification information acquisition unit (AD) (0404). This is to ensure that the payment method identified by the selected payment method identification information makes a prepayment to the employee identified by the employee identification information.

This payment method is typically selected via the Internet by identifying employee identification information from a terminal used by the employee, such as a smartphone, mobile phone, tablet terminal, or personal computer used by the employee. The payment method selection reception unit (AK) (0410) may have a function of displaying a selectable payment method on a terminal used by the employee via an Internet web with an icon or the like. When the employee selects an icon displayed on the terminal used by the employee, the fixed date prepayment system (0400) can be configured to receive the signal and accept the selection of the payment method.

In addition, a dedicated application is installed in the terminal used by the employee, the payment method identification information is held in advance in the application, and the icon etc. to be displayed in association with this is also held, and the payment method is performed by the function of the application. Allows the employee to make a choice and sends the selected payment method identification information to the fixed date prepayment system (0400) so that the fixed date prepayment system (0400) receives the transmission and accepts the payment method selection. It can also be configured.

It should be noted that the acceptance of payment method selection may be configured so that the employee associates it with the subcontractor identification information at the time of registration for use of the fixed date prepaid system (0400), or before the repeated prepaid date. It may be configured so that it can be selected each time in association with the subcontractor identification information. Alternatively, the employee registers at the time of registration for the fixed date prepaid system (0400), and the selection is used thereafter, but the selection is configured to be changed in association with the employee identification information after the fact. May be. Changes can be made using a dedicated application set on the terminal used by the employee for the fixed date prepayment system (0400), or via a web page on the Internet provided by the fixed date prepayment system (0400). It may be configured.

The selected payment method identification information is associated with the employee identification information and is held in the fixed date prepayment system (0400), or is held in a device that can obtain the fixed date prepayment system (0400). Will be done. The retained payment method identification information is configured to be acquired by the payment method identification information acquisition unit (AD) (0404) already described in the first embodiment.

<Implementation 2 Payment Method Payment Consideration Allocation Department (AM) (0411)>

The "Payment Method Payment Consideration Allocation Unit (AM)" (0411) allocates all or part of the payable consideration to one or more payment method identification information selected in association with the employee identification information. This is to make an advance payment of all or part of the payable consideration allocated by the payment method identified by the payment method identification information to the employee. When a plurality of payment method identification information is selected, a part of the payable consideration is assigned to each payment method identification information. Multiple prepayments will be made by one or more payment methods between the payday and the next payday. The payment methods may be the same or different. In the case of different payment methods, for example, between the salary payment date and the next salary payment date, the first transfer to a bank account and the second charge to electronic money can be performed. This is because it is convenient when the payment methods that can be used for utilities, gas / water charges, rent, etc. are different.

<Embodiment 2 Hardware Configuration>

As shown in FIG. 6, the present invention and the present embodiment can basically be composed of a general-purpose computer program and various devices. The operation of the computer basically takes the form of loading the program recorded in the non-volatile memory into the main memory and executing the processing in the main memory, the CPU, and various devices. Communication with the device is done via an interface connected to the bus line. The interface may include a display interface, a keyboard, a communication buffer, and the like.

As shown in this figure, in addition to the program described in the first embodiment, the payment method identification information holding program, the payment method selection reception program, and the payment method payment consideration allocation program are characteristic programs in the present embodiment. Will be described.

The "payment method identification information holding program" holds a plurality of payment method identification information. The reason for holding more than one is to let the employee choose. This is for the convenience of employees. As a premise, a payment method identification information recording program for recording payment method identification information is required in this holding program. The payment method identification information recording program acquires and records the payment method identification information from a storage, a recording medium, an external device, or the like.

The "Payment Method Selection Acceptance Program" accepts one or more selections of payment method identification information that is held in association with the employee identification information. This selection is accepted mainly from the terminal used by the employee via the Internet. The payment method selection reception program communicates with the terminal of the employee who is trying to select, searches for the type and presence of the application for electronic money and the application for bank account operation in the employee's terminal, and uses it. It is convenient to configure the application for electronic commerce that is possible, the application for manipulating bank accounts that is available, and other applications related to remittance to be displayed on the terminal of a selectable subcontractor.

This is to prevent the selection from making prepaid processing impossible due to an employee's operation error. Alternatively, if the payment method identified by the selected payment method identification information is not installed on the employee's terminal, it is identified by the selected payment method identification information on the employee's terminal in conjunction with the selection. It can also be configured to download the application used for the payment method. After downloading, the employee sets and inputs the necessary items according to the guidance of the application, and when the setting is completed, the employee's payment method identification information is used only by using the information of the setting completion of the application. It can also be configured to activate the selection.

The "Payment Method Payment Consideration Allocation Program" allocates all or part of the payable consideration in association with the employee identification information to one or more selected payment method identification information. Once assigned, the payment method identification information is associated with all or part of the payable consideration and is retained in association with the employee identification information as an allocation result. The allocation is made by input from the terminal used by the employee via the Internet. At the same time, it is equipped with an allocation information acquisition program that acquires allocation information from the terminal used by the employee. The payment method identification information acquisition program operates to acquire the payment method identification information for which the selection has been accepted.

Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 2 Processing flow>

As shown in FIG. 5, the processing flow of the operation method of the fixed date prepayment system, which is the computer described in the description of the hardware of the second embodiment, is the user identification information for identifying the user and the employer for the user. Retaining employment relationship information retention steps (aa) (S0501), which retains employment relationship information, which is information related to the employee identification information that identifies the employee to be paid, and multiple payment method identification information. Payment method identification information retention step (aj) (S0502) and payment method selection acceptance step (ak) (S0503) that accepts one or more selections of payment method identification information held in association with employee identification information. A payment method payment consideration allocation step (am) (S0504) that allocates all or part of the payable consideration to one or more payment method identifications selected in association with the employee identification information, and the employee's salary receivables. Based on the employee identification information associated with the employee identification information of the employee, the payable consideration, which is the consideration payable to the subordinate before the salary payment date determined with the employer based on the information. Information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to the employee based on the salary receivable information acquisition step (ab) (S0505). Repeated payment date information retention step (ac) (S0506) that retains return payment date information in association with employee identification information, time information acquisition step (ae) (S0507) that acquires time information including date, and acquisition The repeat payment date relationship determination step (af) (S0508) to determine whether the time information has a predetermined relationship with the repeat payment date defined in the repeat payment date information associated with the employee identification information, and the repeat payment date. Payment to all or part of the payable consideration when the judgment result in the return payment date relationship judgment step (af) (S0508) is the judgment result that the relationship with the repeat payment date has become a predetermined relationship. With the payment method identification information acquisition step (ad) (S0509), which acquires the payment method identification information associated with the employee identification information, which is the information that identifies the method, and the payment method identification information acquired in association with the employee identification information. A recurring payment processing step (ag) (S0510) and a recurring payment processing step (ag) (S0510) that process payments for payment of all or part of the payable consideration by the identified payment method. ) Recurring payment processing history retention step that retains the payment processing history in association with the employee identification information The payment method identification information acquisition step (ad) (S0509), which further has a payment method identification information (ah) (S0511), is configured to acquire the payment method identification information for which the selection has been accepted in association with the employee identification information. ing.

<Effect of Embodiment 2>

According to the second embodiment, the employee can select a payment method that supports payment for utilities and receive advance payment. Therefore, even an employee who has a problem of constant lack of funds during salary payment days can smoothly pay utility bills and the like, which have tended to be delayed in the past.

<Embodiment 3 Mainly Related to the Invention of Claim 3> Unique Information for Remittance

<Outline of Embodiment 3>

In this embodiment, based on the first or second embodiment, a fixed date prepayment system is used to transfer the employee's remittance-specific information necessary for prepayment to a bank account, electronic money, etc. By holding it, it is possible to omit the operation of inputting the same information from the employee each time.

<Structure 3 of Embodiment>

As shown in FIG. 7, the fixed date prepayment system (0700) of the third embodiment has the employment-related information holding unit (AA) (0701) and the salary receivable information acquisition unit (AB) (0702), which are the configurations of the first embodiment. ), The recurring payment date information holding unit (AC) (0703), the payment method identification information acquisition unit (AD) (0704), the time information acquisition unit (AE) (0705), and the recurring payment date relationship determination. When it has a unit (AF) (0706), a recurring payment processing unit (AG) (0707), a recurring payment processing history holding unit (AH) (0708), and is based on the second embodiment. Further has a payment method identification information holding unit (AJ), a payment method selection reception unit (AK), and a payment method consideration allocation unit (AM) of the second embodiment, and further, a characteristic of the third embodiment. As a configuration, it has a unique information holding unit (AN) (0712) for remittance. In the following description, the description of the configuration described in the first embodiment or the second embodiment will be omitted, and only the configuration peculiar to the present embodiment will be described. Although FIG. 7 shows the first embodiment as a basis, the same effect can be obtained even when the second embodiment is used as a basis.

<Embodiment 3 Remittance Unique Information Holding Unit (AN) (0712)>

The "remittance unique information holding unit (AN)" (0712) provides the employee identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information. Associate and keep. As a premise of retention, it is preferable that there is a remittance-specific information acquisition unit that acquires remittance-specific information in association with employee identification information from a terminal or the like used by the employee. In principle, this remittance-specific information is transmitted from the terminal used by the employee.

"Remittance unique information" is a bank account number, an employee's electronic money account identification information, a remittance destination identification information when remittance to an employee's electronic money, or an employee's SNS. It is the identification information of the employee, and other information unique to the employee, which is indispensable for account transfer, remittance by electronic money, and charging of electronic money.

Note that the remittance-specific information is changed by abolishing the bank account, acquiring a new bank account, changing the type of electronic money, acquiring a new ID of electronic money, etc. It is preferable to configure the terminal so that the unique information for remittance can be updated from the terminal used by the subcontractor in the event of a problem. That is, it is preferable to provide a remittance-specific information update unit. It is preferable that this update is configured so that the update content is transmitted from the terminal used by the employee in association with the information indicating that the communication is the update of the remittance-specific information.

<Embodiment 3 Hardware>

As for the hardware of the third embodiment, as shown in FIG. 9 (an example based on the first embodiment), the hardware configuration of the third embodiment is based on the hardware described in the premise of the description of the embodiment. In addition to the program described in 1 or the second embodiment, the non-volatile memory has a unique information holding program for remittance, which is expanded and executed in the main memory, and the unique information for remittance is also in the non-volatile memory, which is the main. It is expanded in memory and processed by the unique information retention program. The unique information for remittance is as already mentioned. The same effect can be obtained when the second embodiment is used as a basis.

Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 3 Processing flow>

The processing flow of the third embodiment is based on the processing flow of the first embodiment or the second embodiment, and is characterized by having a remittance-specific information holding step (an). As an example, as shown in FIG. 8, the remittance unique information holding step (an) (S0802) is added to the processing step of the first embodiment.

<Effect of Embodiment 3>

According to the present embodiment, since the fixed date prepayment system is configured to retain the remittance unique information, the fixed date prepayment system alone does not accept the input of the remittance unique information from the employee each time on the recurring payment date. Push-type prepayment is possible for employees.

<Example 4 Mainly relating to the invention according to claim 4> Repeated payment date information editing

<Outline of Embodiment 4>

In the present embodiment, when it is desired to change the recurring payment date due to the convenience of the employee, it can be changed via the Internet or the like.

<Structure of Embodiment 4>

As shown in FIG. 10, the fixed date prepaid system (1000) of the fourth embodiment is based on the embodiment described in any one of the first to third embodiments, and further, the recurring payment date information editing unit (AP). ) Is a fixed date prepayment system. Based on the first embodiment, as shown in FIG. 10, the employment-related information holding unit (AA) (1001), the salary receivable information acquisition department (AB) (1002), and the recurring payment date information holding Department (AC) (1003), payment method identification information acquisition unit (AD) (1004), time information acquisition unit (AE) (1005), recurring payment date relationship judgment unit (AF) (1006), It has a recurring payment processing unit (AG) (1007) and a recurring payment processing history holding unit (AH) (1008), and as a configuration peculiar to the present embodiment, a recurring payment date information editing unit (AP). ) (1013). Hereinafter, the repeat payment date information editing unit (AP) (1013), which is a configuration peculiar to the present embodiment, will be described. The same effect can be obtained based on either of the second and third embodiments.

<Explanation of Embodiment 4 Configuration>

<Embodiment 4 Repeated Payment Date Information Editing Department (AP) (1013)>

The "Repeat Payment Date Information Editing Department (AP)" (1013) edits the Recurring Payment Date Information and / and the Employee Identification Information held in the Recurring Payment Date Information Holding Department (AC) (1003). .. Editing information is input from a terminal used by an employee via the Internet. When editing, it will be possible after authenticating with employee identification information, password, employee's face photo, employee's face image, employee's voice, employee's fingerprint, etc. It is preferable to configure it. The fixed date prepaid system (1000) preferably has such an employee authentication unit and a user authentication unit described later. This "edit" is to perform one or more operations of addition, change, and deletion on the repeated payment date information and / and the employee identification information. The user authenticates with the user authentication department using his / her own user identification information, password, user's face photo, user's face image, user's voice, user's fingerprint, etc. It is preferable to configure it so that it can be edited with.

However, as a general rule, the employee identification information cannot be added or changed from the terminal used by the employee. From the terminal used by the user, the employee identification information may be added, changed, or deleted after the authentication process. Deletion of employee identification information effectively suspends prepayment processing on that prepayment date because there are no more prepayment recipients for that prepayment date. A change in the recurring payment date is a change in the date on which the recurring prepayment is made.

<Embodiment 4 Addition of other repetitive payment dates (second and subsequent repetitive payment dates)>

The addition of a recurring payment date prepares for another new recurring prepayment. Based on the employee's salary receivable information and some of the payable consideration paid on other recurring payment dates, the prepaid amount required by the employee on the new recurring payment date can be repaid. It is judged whether there is. When this new prepayment amount is input from a terminal or the like used by an employee, the salary receivable information acquisition department (AB) (1002) acquires the salary receivable information based on the user identification information that employs the employee. It is determined whether or not the payable consideration acquired based on the above is within the range of the remaining amount excluding a part of the payable consideration paid on the other recurring payment date.

<Embodiment 4 Others Judgment unit within the remaining amount range>

It is desirable that the fixed date prepaid system (1000) has such a determination unit within the residual amount range. If the result of this determination is determined to be within the range, a new recurring payment date will be activated. That is, when the repeat payment date relationship judgment unit (AF) (1006) determines that the relationship between the repeat payment date and the time information has become a predetermined relationship, the payment process is performed. It will be executed. A plurality of recurring payment date information is effectively held in the recurring payment date information holding unit (AC) (1003) in association with one employee identification information. If it is determined that it is not within the above range, the recurring payment date associated with the employee identification information of the Recurring Payment Date Information Holder (AC) (1003) is not updated.

<Embodiment 4 Other editing by the user New employee>

When the user makes this edit, the employee identification information is added to the recurring payment date information holding unit (AC) (1003) as a preliminary preparation for allowing a new employee to pay in advance. Is. If the employee has the employee identification information assigned to him / her in the Repeated Payment Date Information Holding Department (AC) (1003), the employee can use the Repeated Payment Date Information Editing Department (AP) (1013). It is possible to make prepayment of repayment by associating the repayment date information indicating a new repayment date with the employee identification information of oneself.

If the employer records new employee identification information in the Repeated Payment Date Information Retention Department (AC) (1003), the employee will edit it later. It is configured so that it cannot be edited without authority, and the above-mentioned password, employee's face photo, employee's face image, employee's voice, employee's fingerprint, etc. are fixed date prepayment system (1000) as authority information. ). It is desirable that these authority information is held in the authority information holding unit in association with the employee identification information. When the user is authenticated by the fixed date prepaid system (1000) with his / her own authority information, the user can register the employee's authority information in association with the employee identification information in the authority information registration unit. When the authority information of a new employee is registered and retained in the authority information holding unit, it is advisable to provide an authority information notification unit that notifies the relevant new employee or the user at the same time that the information has been retained. Not only new registration but also when editing the already registered and held authority information, the employee associated with the edited employee identification information or the user can be notified. It is also preferable to provide an authority information recording unit that records the history of new registration and editing of authority information.

<Implementation 4 Acquisition of other salary receivable information>

In addition, the newly registered employee identification information is retained and managed in association with the subcontractor identification information in the fixed date prepaid system or in the server managed by the user. It is also used to obtain. That is, the employee identification information associated with the salary receivable information and the employee identification information held in the recurring payment date information holding unit (AC) (1003) are the same information. The meaning of the same information indicates that the meaning of the information contained in the description is the same even if the description is formally different. Alternatively, the employee identification information held in the recurring payment date information holding section (AC) (1003) in the employee identification information related section is held in association with the payroll claim information in the payroll claim information holding section. It may have in association with the employee identification information.

In this case as well, the meaning of the employee identification information is the same. The information of the salary receivable information holding unit may be updated manually by the user, or may be linked to the employee's attendance management system used by the user or the like. When linked to the time and attendance system, it is configured to be automatically updated based on the number of working days and / or the employee's working hours and information such as the employee's monthly salary, annual salary, and hourly wage. You may set up a salary receivable information holding department update department. The attendance management system can also be configured to automatically update salary receivable information according to the employee ID of the employee or the location information from the smartphone.

<Embodiment 4 Hardware>

As shown in FIG. 12 (an example based on the first embodiment), the hardware configuration of the fourth embodiment is based on the hardware described in the premise of the description of the embodiment, and is any of the first to third embodiments. In addition to the program described in 1 above, a recurring payment date information editing program is provided in the non-volatile memory, and this is expanded and executed in the main memory. Similar effects can be obtained based on the second to third embodiments. If there is a residual amount range determination program that has the above-mentioned residual amount range determination function, efficient processing becomes possible. Therefore, as information, new prepaid desired amount information desired by the employee is stored in the main memory as a processing target and used for determination within the remaining amount range.

In addition, the judgment result information indicating the judgment result is also acquired in the main memory by the judgment program within the residual amount range, and the payroll receivable information acquisition program determines the recurring prepayment amount which is a part of the new payable consideration according to the judgment result. get. Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 4 Processing flow>

As shown in FIG. 11, the processing flow of the present embodiment is based on any one of the first to third embodiments. And the peculiar part is that there is a repeat payment date information editing step (ap) (S1110). The processing flow shown in FIG. 11 is based on the processing flow of the first embodiment. The recurring payment date information editing step (ap) (S1110) is a feature of the present embodiment. Similar effects can be obtained based on the second to third embodiments.

<Effect of Embodiment 4>

In the fixed date prepayment system of the present embodiment, since it is possible to edit the recurring payment date, etc. of the recurring payment date information holding unit (AC), the payment date of utility charges, etc. of employees, etc. is changed. It is also possible to flexibly change the recurring payment date.

<Embodiment 5 Mainly relating to the invention according to claim 5> Repeated payment date information New record

<Outline of Embodiment 5>

The fixed date prepayment system of the present embodiment is configured to newly record recurring payment date information and / and employee identification information.

<Structure 5 of Embodiment>

As shown in FIG. 13, the fixed date prepaid system (1300) of the fifth embodiment is based on any one of the first to fourth embodiments. FIG. 13 is a functional block diagram of the present embodiment based on the first embodiment. As shown in this figure, the employment relationship information holding unit (AA) (1301), the salary receivable information acquisition department (AB) (1302), the recurring payment date information holding department (AC) (1303), and the payment method. Identification information acquisition unit (AD) (1304), time information acquisition unit (AE) (1305), recurring payment date relationship judgment unit (AF) (1306), recurring payment processing unit (AG) (1307). And a recurring payment processing history holding unit (AH) (1308), and further having a recurring payment date information recording unit (AR) (1314). The description of the already explained part will be omitted, and the recurring payment date information recording part (AR) (1314) peculiar to the present embodiment will be described. The same effect can be obtained based on any one of the second to fourth embodiments.

<Explanation of Embodiment 5 Configuration>

<Embodiment 5 Repeated Payment Date Information Recording Unit (AR) (1314)>

The "Repeat payment date information recording unit (AR)" (1314) has a function of newly recording the recurring payment date information and / and the employee identification information in the repetitive payment date information holding unit (AC) (1303). Have. This new record can be newly recorded by the administrator of the fixed date prepaid system (1300) or by an authorized user, and is repeated by the employee identified by the authorized employee identification information. A new record of payment date is made. As mentioned above, the employee identification information and the recurring payment date information are associated and finally retained in the recurring payment date information holding unit (AC) (1303), but initially, as described above, the employee Only person identification information is recorded. This is done from the terminal used by the authorized user in principle.

The authority of the user is given by the user authentication department, and the authority of the employee is given by the employee authentication department. The authority information is held by the authority information holding unit as described above. The initial user's authority information is registered in the authority information registration department by a person who has the administrator authority of the fixed date prepaid system (1300), and the registered record is recorded in the authority information holding department, and thereafter. The administrator of the fixed date prepaid system (1300) notifies the user of the authority information, and the user records the first employee identification information by using the authority information learned in the notification. Will be able to.

As described above, at the same time as recording the employee identification information, the user can record the employee's authority information in association with the employee identification information of the authority information holding department, and this employee's authority information is recorded by the employee. By notifying the employer, the employee uses his / her authority information to be authenticated by the employee authentication department, and the recurring payment date information indicating a new recurring payment date in association with his / her employee identification information. Can be recorded.

<Implementation 5 Retention of all or part of payable consideration>

After the recurring payment date information can be recorded in association with the employee identification information, the employee then inputs the desired amount of prepayment to the fixed date prepayment system (1300) from the terminal or the like used by the employee. The entered recurring prepayment amount is then tested.
In the test, the fixed date prepayment system (1300) uses the employee identification information to access the salary receivable information holding unit owned by the employee or the salary receivable information server used by the user, and the prepayment amount is the salary receivable information. Judge whether it is within the repeatable payment range based on. The recurring payable range determination unit in the fixed date prepaid system (1300) may perform such a function. Alternatively, a fixed date prepayment desired amount input section for inputting the prepayment desired amount and a fixed date prepayment desired amount testing section for testing whether the prepayment desired amount is within the repeatable payable range based on salary receivable information are provided. May be good.

If the judgment result of the repeatable payment range judgment unit is the repeatable payment range, the amount is paid in association with the employee identification information and the repeat payment date information. Recorded and retained as all or part of the possible consideration. This is the function of the payable consideration holding department. This payable consideration holding unit may be provided in the fixed date prepaid system (1300) or may be provided externally. Then, on the recurring payment date determined by the recurring payment date information, all or part of the held payable consideration is acquired by the salary receivable information acquisition unit (AB) (1302).

<Relationship with the recurring payment information editorial department of the fifth embodiment>

The "repeated payment date information editing unit" of the fourth embodiment also has a function similar to that of the "repeated payment date information recording unit" of the present embodiment, but the "repeated payment date information editing unit (AP)" of the fourth embodiment has a function similar to that of the "repeated payment date information recording unit". And the “repeated payment date information recording unit (AR)” of the present embodiment may be provided by one fixed date prepayment system (1300).

<Embodiment 5 Hardware>

As shown in FIG. 15 (an example based on the first embodiment), the hardware configuration of the fifth embodiment is. Based on the hardware described in the premise of the description of the embodiment, the non-volatile memory has a recurring payment date information recording program in addition to the program described in any one of the first to fourth embodiments. It is expanded in memory and executed.

It should be noted that if there is a judgment program within the remaining amount range, which is carried by the above-mentioned judgment function within the remaining amount range, efficient processing becomes possible. Therefore, as information, new prepaid desired amount information desired by the employee is stored in the main memory as a processing target and used for determination within the remaining amount range. In addition, the judgment result information indicating the judgment result is also acquired in the main memory by the judgment program within the residual amount range, and the payroll receivable information acquisition program determines the recurring prepayment amount which is a part of the new payable consideration according to the judgment result. get.

In addition to the programs already explained in this embodiment on the hardware described in the premise of the above-mentioned functions, the user authentication program and the employee authentication program are used to realize each of the above-mentioned functions. , Authority information retention program, authority information notification program, authority information recording program, prepaid desired amount input program, prepaid desired amount test program, repetitive payable range judgment program, payable consideration holding program. ..

Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 5 Processing flow>

The present embodiment has a recurring payment date information recording step (ar) (S1402) based on the processing flow according to any one of the first to fourth embodiments. FIG. 14 shows an example having the recurring payment date information recording step (ar) (S1402) based on the processing flow of the first embodiment. Note that the recurring payment date information recording step (ar) (S1402) is described here in the second step of the process, but it should be placed in the first step, the last step, or other intermediate position of the process. Is also possible.

<Effect of Embodiment 5>

In the present embodiment, when the user first uses the fixed date prepaid system, or when a new employee is registered, it can be efficiently performed.

<Embodiment 6 Mainly relating to the invention according to claim 6> Advance payment on an arbitrary date

<Outline of Embodiment 6>

The present embodiment is a system that can make a prepayment request to a subcontractor on an arbitrary date by using a fixed date prepayment system.

<Structure 6 of the embodiment>

The fixed date prepayment system (1600) of the sixth embodiment is based on the fixed date prepayment system (1600) of any one of the first to fifth embodiments, and makes a prepayment request from a subcontractor on any non-fixed date. Is made possible. As shown in FIG. 16, in the functional block based on the first embodiment, the employment relationship information holding unit (AA) (1601), the salary receivable information acquisition department (AB) (1602), and the recurring payment date information holding Department (AC) (1603), payment method identification information acquisition unit (AD) (1604), time information acquisition unit (AE) (1605), recurring payment date relationship judgment unit (AF) (1606), It has a repetitive payment processing unit (AG) (1607) and a repetitive payment processing history holding unit (AH) (1608), and further, as a characteristic configuration of the present embodiment, a start processing request acquisition unit (AS). ) (1615), start processing request time information acquisition unit (CD) (1644), prepaid amount acquisition unit (AT) (1616), prepaid request amount acquisition unit (AW) (1617), and prepaid processing unit. A fixed date prepayment system (1600) comprising (AX) (1618) and a prepayment history holding unit (AY) (1619). Similar effects can be obtained based on the second to fifth embodiments.

In addition, in order to realize the functions described in the fourth and fifth embodiments, the employee authentication unit, the user authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (users are If the fixed date prepayment system (1600) is authenticated with its own authority information, the authority information holding department can register the employee's authority information in association with the employee identification information.), The authority information holding department, Employee identification information related department, salary receivable information holding department, salary receivable information holding department renewal department, authority information notification department, authority information recording department, fixed date prepayment desired amount input department, fixed date prepayment desired amount testing department, repeat It may be configured to have a payable range determination unit and a payable consideration holding unit.

The configurations described in the first to fifth embodiments will be omitted, and only the configurations specific to the present embodiment will be described below.

<Explanation of Embodiment 6 Configuration>

<Embodiment 6 Start Processing Request Acquisition Unit (AS) (1615)>

The “start processing request acquisition unit (AS)” (1615) acquires the start processing request of the salary prepayment request in association with the employee identification information. This prepayment is different from the fixed date prepayment described so far, and is requested by the employee from the employer at an arbitrary timing. However, this does not mean that the employee is required to be registered so that the fixed date prepayment can be made by the fixed date prepayment system (1600). The employee who can make this start processing request may be an employee who does not use the fixed date prepayment. That is, it does not matter whether the repeat payment date information holding unit (AC) (1603) holds the employee identification information in association with the repeat payment date information.

The start processing request is typically transmitted from a terminal used by the employee. That is, the terminal used by the employee has a start processing request transmission unit. The start processing request transmission unit may be a fixed date prepayment system (1600) provided on a web page that can be viewed on the employee's terminal, or can be used on the employee's terminal. It may be one provided on the application.

<Embodiment 6 Start processing request time information acquisition unit (CD) (1644)>

The "start processing request time information acquisition unit (CD)" (1644) acquires time information including the date when the start processing request is acquired. Specifically, the timing of receiving the start processing request is acquired. The date is a typical example, but time information may be attached to this. Hours, minutes, seconds.

The time information may be obtained from the same source used by the fixed date prepayment system (1600) or may be different. The start processing request time information acquisition unit (CD) (1644) may be the same as the time information acquisition unit (AE) (1605) of the fixed date prepayment system (1600). However, it is characterized in that the time information is acquired in conjunction with the acquisition of the start processing request.

<Embodiment 6 Prepaid Amount Acquisition Department (AT) (1616)>

The Prepaid Amount Acquisition Department (AT) (1616) uses salary receivable information associated with employee identification information and, if available, recurring payment date information associated with employee identification information. When possible, obtain the prepayable amount, which is the amount that allows the prepayment request, based on all or part of the payable consideration paid on the recurring payment date associated with the employee identification information. However, if the employee does not use fixed date prepayment, that is, he / she has not received all or part of the payable consideration on the recurring payment date, the salary associated with the employee identification information. We do not use information on the recurring payment date based on the claim information and all or part of the payable consideration paid on the recurring payment date. This information is flagged as "unavailable".

As mentioned above, if all of the payable consideration is paid in advance, the life of the employee may become unstable because there is no salary paid on the payday. This is based on the premise that the compensation for the labor of last month will be paid as salary in the following month at the end of the month. Therefore, the amount of payable consideration paid on the recurring payment date is that the number of working days in the last month was D1 and the planned number of working days in this month was D2. It is assumed that the number of working days is the D4 day from the beginning of the month (assuming D1> D4> D3). Assuming that the employee's daily labor consideration is a yen, the payable consideration to this employee the next day is D1 x a yen, assuming that no fixed date prepayment has been made this month. This is based on the premise that only the balance of labor consideration last month will be paid in advance.

Assuming that this month's fixed date prepayment is calculated based only on last month's salary receivables, if the fixed date prepayment safety factor is S, the prepayment amount is D1 x a x S yen and will be paid this month. The salary will be the remaining amount of D1 x a x (1-S) yen. If the fixed date prepayment has not been made yet and the fixed date prepayment has not been made, the salary receivable of last month will be D1 × a. If it is D1 × a × (1-S) yen and the current date is after the salary payment date (assuming D1> D3> D4), the salary receivable of last month will be 0 yen. In other words, the policy of processing prepaid payments only based on last month's salary receivables will result in different sources of prepaid payments depending on when the prepaid bill is made on any date. Furthermore, the source of funds also depends on the size of S.

That is, the influence rate of the prepaid amount on any date changes with the amount that can be paid to the employee on the salary payment date according to the magnitude of the safety factor S paid by the fixed date prepaid. Therefore, how the timing indicated by the date and time information of the start processing request is related to the recurring payment date indicated by the recurring payment date information, and the payable consideration paid on the recurring payment date ( (All) Depending on how large a part of the amount is, it will be necessary to set the prepaid amount on any date.

For example, if it is possible to make advance payments on any date until T% of the salary receivable amount D1 × a yen last month, it is considered appropriate that the combined safety factor T is about 20% to 40%. That is, as a result of the fixed date prepayment and the arbitrary date prepayment, the amount R of the salary that should be finally paid to the employee on the salary payment date is D1 × a × 0.8> R> D1 × a × 0.6. The degree is considered appropriate.

The compound safety factor T may be configured to be adjusted according to the employee's past prepaid history. It is conceivable to take a large T value for employees who frequently use prepayment and a small T value for employees who do not. It is also desirable to adjust the allowance for prepaid on any date in relation to the salary payment date and the timing of the start processing request. If there are still many days left before the salary payment date, it is preferable to adjust the prepayment allowance per payment to a smaller value because prepayment of multiple arbitrary dates may occur. The allowance can be adjusted to a large extent.

<Embodiment 6 Prepaid Request Amount Acquisition Department (AW) (1617)>

The “prepaid request amount acquisition unit (AW)” (1617) acquires the prepaid request amount in association with the employee identification information within the range not exceeding the prepaid possible amount. As described above, the prepaid request amount is transmitted from the terminal used by the employee. The employee identification information is configured to be entered by the employee each time and associated with the prepaid request amount, or to be held in the terminal used by the employee and automatically associated with the transmission of the prepaid request amount. You can also do it. This is the same for web communication with the fixed date prepayment system (1600) and for communication via the application for the fixed date prepayment system (1600). It may be sent on the web via the Internet or sent by an application available on the terminal.

There are two styles before the prepaid amount is determined.

One is to let a subcontractor arbitrarily enter the prepaid request amount, determine whether it is within the range of the prepaid amount on the fixed date prepaid system (1600) side, and if it is within the range, move on to processing the requested amount and prepaid. If the amount exceeds the range of the possible amount, the employee is asked to send the requested amount again, and this is repeated in some cases, and when the amount finally falls within the range of the prepaid amount, the requested amount is reached. It is to move on to processing. In this case, since the prepaid request amount transmitted by the employee is an arbitrary amount, the comparison between the requested amount and the prepaid possible amount is performed by the fixed date prepaid system (1600).

The other is to have the employee determine the prepayment request amount within the range based on the prepayable amount acquired in advance in the fixed date prepayment system (1600). In this case, the prepaid amount is transmitted in advance to the terminal used by the employee, and the prepaid amount is displayed on the display of the terminal.

Further, the prepayable amount means the upper limit of the prepayable amount, but it is also conceivable to have the employee show and select the prepayment request amount within the range below the prepayable amount. In this case, the options are transmitted from the fixed date prepayment system (1600) to the employee's terminal and displayed on the display of the employee's terminal. Further, it is preferable to configure the option as an icon so that the value is transmitted to the fixed date prepaid system (1600) as a prepaid request amount by simply touching the icon. This may also be done via the internet via a web page provided by the fixed date prepayment system (1600) or by using an application available on the terminal for the fixed date prepayment system (1600). ..

<Embodiment 6 Prepaid Processing Unit (AX) (1618)>

The “prepaid processing unit (AX)” (1618) performs prepaid processing, which is processing for prepaid the acquired prepaid request amount. Since the "prepayment process" is a process for "for" the prepaid payment, it does not have to be the process of the actual remittance, transfer, or charge itself. It may be a pre-processing for remittance, transfer, or charging. The prepayment process is the same as the payment process already described in the first embodiment, and is the transfer process to the bank account of the electronic money operating company, the transfer process to the employee's bank account, and the transfer process to the bank account of the electronic money operating company. , Employee's bank account transfer processing, employee's electronic money charge processing, employee's electronic money transfer (transfer point) processing, etc.

<Embodiment 6 Prepaid Processing Unit (AX) (1618) Other Payment Method Identification Information>

When the prepaid request amount is acquired from the employee's terminal, it is possible to configure the payment method identification information to be directly or indirectly associated with the employee identification information. In this case, the payment method identification information is acquired by the payment method identification information acquisition unit (AD) (1604) already described in the fixed date prepayment system (1600) in association with the employee identification information, and the acquired payment method. The identification information can also be configured to be associated with the prepaid request amount via the employee identification information.

Alternatively, a payment method identification information acquisition unit (AD) (1604) for the fixed date prepayment system (1600) may be provided separately from the payment method identification information acquisition unit (AD) (1604). This is because the payment method may be different each time because it is a prepaid request on an arbitrary date. The meaning of the payment method identification information itself is as described in the first embodiment.

It is also possible to divide the total amount of the prepaid request amount into a plurality of payment methods and make a partial payment. In that case, the prepaid request amount is divided into multiple amounts, and the employee is made to select the same number of payment method identification information as the divided amount, and the process of allocating to each amount is performed on the employee's terminal. The result needs to be sent to the fixed date prepaid system (1600). Then, the prepaid processing unit (AX) (1618) needs to execute a plurality of prepaid processing based on the transmission from the employee. As an interface for this processing on the employee terminal, a payment method icon is displayed in the vicinity of a plurality of divided payment request amounts, and an icon is selected for each payment request amount to display the payment request amount and payment method identification information. It's about associating.

<Embodiment 6 Prepaid History Holding Unit (AY) (1619)>

The "prepaid history holding unit (AY)" (1619) holds the prepaid history, which is the history of the prepaid processing in the prepaid processing unit (AX) (1618), in association with the employee identification information. In addition to the history of the completion of the prepaid processing, the history of the processing after the prepaid processing may be included. In other words, it is the history of actual execution of processes such as transfer, remittance, and charge. It is conceivable that these records the history based on the processing report from the server such as the company that performs the processing after the prepaid processing.

<Embodiment 6 Hardware>

The hardware of the fixed date prepayment system of the sixth embodiment is based on the hardware described in the premise of the description of the embodiment, and the program described in the description of the hardware of the first to fifth embodiments is added to these. The start processing request acquisition program, the start processing request time information acquisition program, the prepayable amount acquisition program, the prepayment request amount acquisition program, the prepayment processing program, and the prepayment history holding program for realizing the above functions are non-volatile. While holding it in the sex memory, expand each to the main memory based on the start command, and execute the program according to the necessary procedure. Data and information used / / and generated / acquired are also expanded from the non-volatile memory to the main memory. The data is data showing the amount of money, such as all or part of the payable consideration amount, the prepaid amount, the prepaid request amount, or the prepaid amount, the divided amount of the prepaid amount, etc. Person identification information, payment method identification information, prepaid history, start processing request time information, and the like. In addition, in order to realize the functions described in the fourth and fifth embodiments, the employee authentication program, the user authentication program, the remaining amount range judgment program, the authority information holding program, and the user use their own authority information. Employee authority information registration program, employee identification information related program, salary that can register employee authority information in association with employee identification information in the authority information holding department after being certified by the fixed date prepayment system Receivable information retention program, salary receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repetitive payable range judgment program, payable pair A value retention program, may be similarly configured, deployed, and run on hardware. As for the terminals used by employees, hardware resources such as smartphones are used by the corresponding programs in cooperation with these programs. This point is the same from the first embodiment to the present embodiment.

<Example 6 Processing flow>

In addition to, or partially or entirely, in addition to the flow of processing according to any one of the processes of Embodiment 1 to Embodiment 5, the following processing is performed. As shown in FIG. 17, the processing flow of the first embodiment is on the left side, and the processing flow peculiar to the present embodiment is on the right side. Explaining the processing flow on the right side, the start processing request acquisition step (as) (S1709) for acquiring the start processing request for the prepaid salary request in association with the employee identification information, and the time including the date when the start processing request is acquired. Start processing request time to acquire information Information acquisition step (cd) (S1710), salary receivable information associated with employee identification information, and recurring payments associated with employee identification information, if available. Prepaid amount that allows a prepaid request based on daily information and, if available, all or part of the payable consideration paid on the recurring payment date associated with the employee identification information. The prepaid amount acquisition step (at) (S1711) to acquire the prepaid amount, and the prepaid request amount acquisition step (aw) (S1712) to acquire the prepaid request amount in association with the employee identification information within the range not exceeding the prepaid amount. Employees have a prepaid processing step (ax) (S1713) that performs prepaid processing, which is a process for prepaid the acquired prepaid request amount, and a prepaid history that is a history of prepaid processing in the prepaid processing step (ax) (S1713). It is an operation method of a fixed date prepaid system which is a computer having a prepaid history holding step (ay) (S1714) which is held in association with identification information.

These processing steps are separate processes from the fixed date prepayment processing of Embodiments 1 to 5, and when the relationship between the time information and the recurring payment date is other than the predetermined relationship in the fixed date prepayment processing. A branch for determining whether or not to make a prepaid date on an arbitrary date can be inserted in, and a process specific to the present embodiment can be executed when it is determined that a prepaid process on an arbitrary date should be performed. It should be noted that whether or not to execute the prepayment on an arbitrary date is triggered by the acquisition of the start processing request by the first subcontractor.

An example of the registration work when an employee applies for prepaid payment on an actual arbitrary date using his / her own smartphone will be described with reference to FIG. 87. FIG. 87a is an example of a prepaid payment date setting screen of an arbitrary date, FIG. 87b is an example of a prepaid application amount input screen to be paid on the prepaid payment date, and FIG. 87c is an example of a setting confirmation screen after the setting input is completed. FIG. 87abc is an example, and the layout and usage are not limited.
First, on the screen of FIG. 87a, the date at the time when the setting input is started is acquired from the time information in the smartphone and displayed as the current one, and the calendar of the corresponding month is displayed at the start of the operation. In FIG. 87a, the time of operation is September 2, 2020. Select the year and month to be input (8701). Return from the initially displayed September 2020, or press the left and right triangle buttons to proceed. If you return from the current time, you can refer to the history when you applied for payment in the past. The corresponding calendar (8702) is displayed immediately below. The date to be registered this time is September 16th, which is the date (8703) that is highlighted in black and white.
The prepaid application on an arbitrary date may be a prepaid application requesting payment on the day of application. If the payment is requested from the fixed date prepayment system to the financial institution involved in the payment and the payment cannot be made on the same day due to the time required for payment, the prepayment agency may temporarily reimburse the funds from its own funds and execute the prepayment processing. good.

If the amount applied for this time is less than the balance obtained by multiplying the labor consideration by the safety factor and subtracting the total amount already paid by recurring payment or prepayment on any date, additional registration is possible. As in the example of the embodiment described later, if the balance of the prepaid amount that can be prepaid by the prepaid payment date that has already been set is estimated and calculated from the present time to the future, and the prepaid request amount is paid on the prepaid date of any date, If the recurring payment set earlier becomes impossible, it is preferable to reduce the prepaid amount, which is the basis for determining the acceptance of the prepaid request amount, and display it to the employee. In the case of a worker who closes at the end of each month and pays on the 24th, in the example of FIG. 87, there is a closing of attendance for August on August 31, and compensation for the work for August is paid on September 24. If only the amount obtained by multiplying the labor consideration for August by the safety factor is used as the source of prepayment, the prepayment application amount will be adjusted so that the prepayment application for any date in September will not be hindered by the already set recurring payment. It is easy to induce them to do so. If you apply for prepayment on an arbitrary date after the wage payment date, for example, on October 5, the accumulation of labor consideration for the wages scheduled to be paid in October is insufficient as of September 2, and the set repetition in October Due to the balance with payment, it may not be possible to set prepayment for any date.
If the prepaid agency is registered as a money lending business, it is an estimated labor that estimates the labor performance in September based on the attendance record of the specified number of days for at least one month in the past. The amount obtained by multiplying the consideration by the safety factor is the estimated prepayable amount, and the prepayment request amount is compared with the amount obtained by subtracting the total amount of recurring payments in October from the estimated prepayable amount and the prepayment application on the above arbitrary date. May be configured to determine if it is payable and to notify the employee of the adjustment of the application amount. In this case, the prepaid agent should be registered as a money lending business as described above in order to make a decision to accept the prepaid application before the labor consideration is incurred.
If the work record in September is low, it is better to notify that the payment amount will be insufficient before the entered arbitrary date prepayment date in October or the set recurring payment date.

In the reservation addition operation on the screen shown in FIG. 87a, the part of the date to be directly added may be clicked (pressed) on the calendar, or the year, month, and year, month, may be displayed in the prepaid reservation date selection field (8704) under the calendar. You may individually select and input by pressing the triangle button next to each column for each day. The amount that can be paid in advance is displayed below the reservation date. Below that, there is an amount setting column (8705) and a transfer destination financial institution selection column (8706). When the amount setting field (8705) is pressed, the screen changes to the amount input screen shown in FIG. 87b. Either the amount input or the transfer destination selection order may come first.
To specify the amount, touch the amount input field (8710) and then enter it with the numeric keypad. If you start operating the numeric keypad directly, you may consider that you have selected the specified amount. If you enter an amount that exceeds the amount that can be paid in advance, the amount you have entered once disappears, and you can configure it so that an error message such as "input error" or "excess amount" appears (example in case of excess amount). Is not shown). The amount of money can be selected by pressing the amount input field and displaying the options in units of 1000 yen from the pull-down menu, or by touching the icon with the amount of money such as 10000 yen or 1000 yen. It may be in the form of If you touch the icon of 20000 yen and then touch the icon of 2000 yen, you may enter 22000 yen, or you may touch the icon written as 22000 yen. When you enter the amount, the fee required to apply for the amount in advance should be displayed below the entered amount. Further, when the prepaid amount is 127,000 yen, the pull-down menu or the icon may be configured so that options are presented in units of 1,000 yen with a maximum value of 127,000 yen. Since the number of choices is large, it is preferable to have a pull-down menu scrolling function and a screen scrolling function in which icons are displayed.
In FIG. 87b, the display is included in the prepaid amount, and since the fee is 1200 out of the prepaid amount of 20000 yen, the subordinate actually receives 18800 yen. The fee may be excluded from the input amount, and when receiving a prepayment of 20,000 yen, the fee of 1,200 yen may be deducted each time or in a lump sum in addition to the 20,000 yen. This prepayment fee may be paid by the employee or by the employer as part of the welfare program. At least part of the fee may be borne by the financial institution used for payment. The prepayment up to once a month may be borne by the user, and the second and subsequent payments may be borne by the employee.
After entering the amount, press the enter button (8711) at the bottom of the screen. Pressing the enter button (8711) returns to the screen shown in FIG. 87a. After selecting the financial institution to transfer to (LINE Pay (registered trademark) in FIG. 87a), press the enter button (8707). The prepaid reservation date (8715) added this time, which changes to the confirmation screen of FIG. 87c, is displayed as a solid circle in the calendar. In Figure 87c, September 16th. The reservation date, amount, and payment financial institution are listed under the calendar, and if there is no problem, press the execute button to complete the setting. It is possible to easily set the recurring payment date by such an operation on the smartphone. Note that this setting method is a specific example of operation, and can be appropriately designed without being limited to this screen.

<Embodiment 7 Mainly relating to claim 7> Processing notification on SNS

<Outline of Embodiment 7>

In the present embodiment, the result of the above payment processing is notified to the employee via the SNS used by the smartphone or the like used by the employee.

<Structure 7 of Embodiment>

This embodiment is based on any one of the first to sixth embodiments, and further includes a processing result acquisition unit (AZ) (1920), an SNS identification information holding unit (BA) (1921), and a processing result notification unit (1921). BB) (1922). For example, as shown in FIG. 19, when the first embodiment is used, the employment-related information holding department (AA) (1901), the salary receivable information acquisition department (AB) (1902), and the recurring payment date. Information holding unit (AC) (1903), payment method identification information acquisition unit (AD) (1904), time information acquisition unit (AE) (1905), and recurring payment date relationship judgment unit (AF) (1906). It has a recurring payment processing unit (AG) (1907), a recurring payment processing history holding unit (AH) (1908), and further, a processing result acquisition unit (AZ) (1920) and SNS identification information. It has a holding unit (BA) (1921) and a processing result notification unit (BB) (1922). The same effect can be obtained based on the second to sixth embodiments.

As described in the previous embodiment, the employee authentication unit, the user authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the user has a fixed date with his / her own authority information). After being certified by the prepaid system (1900), the authority information holding department can register the employee's authority information in association with the employee identification information), the authority information holding department, and the employee identification information related department. , Salary claim information holding section, Salary claim information holding section updating section, Authority information notification section, Authority information recording section, Fixed date prepayment desired amount input section, Fixed date prepayment desired amount testing section, Repeatable payment range judgment section, Payment It may be configured to have a possible consideration holding unit.
Hereinafter, the processing result acquisition unit (AZ) (1920), the SNS identification information holding unit (BA) (1921), and the processing result notification unit (BB) (1922), which are characteristic configurations of the present embodiment, will be described. ..

<Embodiment 7 Processing Result Acquisition Unit (AZ) (1920)>

The "processing result acquisition unit (AZ)" (1920) outputs a processing result that is the result of payment processing by the recurring payment processing unit (AG) (1907) or prepaid processing by the prepaid processing unit (AX). Obtained in association with identification information. Since it is a processing result, it includes at least information that the processing has been completed normally or information that the processing has not been completed normally.

In addition, the amount of prepaid processing, the amount collected as a fee, the date and time of this prepaid processing, information that identifies the person who made the prepaid (user, intermediary, etc.), in the case of fixed date prepaid The next repaid payment date, the amount that can be prepaid by the next salary payment date (the remaining period may be divided into multiple categories and the amount may be presented for each category), the next salary payment date Estimated amount of money that can be prepaid by (the remaining period may be divided into multiple categories and the amount may be presented for each category), past prepaid results, processing identification information of prepaid processing, processing is normal It may include any one or more of the causes when it does not end in. The processing result acquisition unit (AZ) (1920) acquires the processing result immediately after the payment processing (repeated payment processing, prepaid processing). That is, it is preferable that the acquisition of the processing result is performed continuously with the payment processing.

<Embodiment 7 SNS Identification Information Holding Unit (BA) (1921)>

The "SNS identification information holding unit (BA)" (1921) holds the SNS identification information used by the employee in association with the employee identification information. The "SNS identification information" is information that identifies the type of SNS. Examples of SNS types include Facebook (registered trademark), LINE (registered trademark), instagram (registered trademark), WeChat (registered trademark), Twitter (registered trademark), Mixi (registered trademark), YouTube (registered trademark), Nico Nico Video (registered trademark), KakaoTalk (registered trademark), etc. can be mentioned. Basically, it has one or more of member profile introduction function, message sending / receiving function between members, timeline (wall) function by members, member mutual link function, member search function, blog function, questionnaire function, community function, etc. It is a system.

<Embodiment 7 SNS Identification Information Holding Unit (BA) (1921) Other SNS Employee ID>

It is preferable that the "SNS identification information holding unit (BA)" (1921) also holds the SNS employee ID. The "SNS employee ID" refers to information that uniquely identifies an employee on the SNS used by the employee. This information can be used to communicate with the employee and send information on the SNS. Therefore, the fixed date prepaid system (1900) can transmit and notify the employee by using the SNS identification information and the SNS employee ID.

<Embodiment 7 Processing Result Notification Unit (BB) (1922)>

The "processing result notification unit (BB)" (1922) notifies the employee of the processing result via the SNS identified by the employee identification information associated with the processing result and the SNS identification information associated with the processing result. It is configured to do. In particular, when the SNS as a notification means and the electronic money type as a processing means are linked, the viewing of the processing result of the employee and the consumption of the prepaid electronic money by the employee are integrated. It is convenient because it is possible. The processing result notification referred to here is different from the notification from the electronic money system. Therefore, in addition to the notifications such as charge completion, remittance possible, and remittance completion by the electronic money system, the notification by the fixed date prepayment system (1900) is given.

In addition, as a response to the processing result notification, it is more desirable to configure the fixed date prepaid system (1900) so that the employee can perform an acknowledge reply such as read or accepted by a simple operation such as one push. .. It is desirable to perform this with the link button provided in the processing result notification screen. In addition, it is desirable to configure the prepaid processing result to be automatically forwarded or automatically notified to the user of the employee based on the knowledge reply. It should be noted that this processing result notification may include not only the processing of the fixed date prepayment system (1900) but also the notification of all external processing related to the prepayment. And this notification may be multiple notifications regarding one payment process. It is preferable that the notification of the processing result is continuously executed when the processing result acquisition unit (AZ) (1920) acquires the processing result. This is because it is an employee's concern.

<Embodiment 7 Hardware>

In the hardware configuration of the fixed date prepaid system of the seventh embodiment, the program described in any one of the first to sixth embodiments is executed using the hardware described in the premise part of the description of the embodiment as a resource. Furthermore, in addition to that, a processing result acquisition program that acquires the processing result that is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the employee identification information. , The SNS identification information holding program that holds the SNS identification information used by the employee in association with the employee identification information, and the SNS identification information associated with the employee identification information associated with the processing result. It has a processing result notification program for notifying a processing result via SNS. Based on the first embodiment, the above hardware configuration is as shown in FIG. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions. This execution is preferably carried out continuously and without intervals.

As described in the previous embodiment, the employee authentication program, the user authentication program, the authority information holding program, the remaining amount range judgment program, and the authority information registration program (the user has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the employee's authority information in association with the employee identification information.), Authority information retention program, employee identification information related program, salary claim Information retention program, salary receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 7 Processing flow>

In addition to the processing flow of any one of the first to sixth embodiments, the following processing is performed. Based on the first embodiment, as shown in FIG. 20, the processing result which is the result of the payment processing in the recurring payment processing step (ag) (S2008) or the prepayment processing in the prepayment processing step (ax). The processing result acquisition step (az) (S2010) for acquiring the information in association with the employee identification information, and the SNS identification information retention step (ba) (ba) for holding the SNS identification information used by the employee in association with the employee identification information. It has S2002) and a processing result notification step (bb) (S2011) for notifying the processing result via the SNS identified by the employee identification information associated with the processing result and the SNS identification information associated with the processing result. This is the operation method of the fixed date prepayment system, which is a computer. This processing result notification step (bb) (S2011) may include notifications for all external processing related to prepayment, as well as processing for fixed date prepayment systems. And this notification may be multiple notifications regarding one payment process. This is shown in FIG.

In addition to these, the employee authentication step, the user authentication step, the authority information retention step, the remaining amount range judgment step, and the authority information registration step (the user is authenticated by the fixed date prepayment system with his / her own authority information). And, the authority information holding department can register the employee's authority information in association with the employee identification information.), Authority information holding step, employee identification information related step, salary claim information holding step, salary claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 7>

As an employee, whether or not the prepaid process is completed successfully is a very important concern that is directly linked to daily life. Therefore, I want to know the result as soon as possible. The payment process of this fixed date prepayment system is not necessarily the remittance process itself such as fund transfer, remittance to the account, remittance of electronic money, charge to electronic money, but as an employee, it is a pre-stage process. However, since we want to know as soon as possible that the processing has been completed successfully, this embodiment is effective in satisfying the demand.

<Embodiment 8 Mainly relating to claim 8> Remittance by SNS

<Outline of Embodiment 8>

The eighth embodiment is an embodiment based on the seventh embodiment based on the third embodiment. This is because it is premised that the remittance unique information holding unit (AN) is provided and the SNS identification information holding unit (BA) is provided. In the present embodiment, the remittance SNS identification information is held in association with the employee identification information.

This is because the employee who has the SNS identification information for remittance is inevitably the employee who is identified by the employee identification information associated with the SNS identification information regardless of whether it is for remittance or not.

<Structure 8 of Embodiment>

The configuration of the eighth embodiment is based on the seventh embodiment based on the third embodiment as described above. Therefore, as shown in FIG. 22, the configuration of the present embodiment 8 is shown by an example in which the third embodiment is not based on the second embodiment. ) (2202), the recurring payment date information holding unit (AC) (2203), the payment method identification information acquisition unit (AD) (2204), the time information acquisition unit (AE) (2205), and repetitive payment. Japan-related judgment unit (AF) (2206), recurring payment processing unit (AG) (2207), recurring payment processing history holding unit (AH) (2208), and remittance unique information holding unit (AN) ( 2212), a processing result acquisition unit (AZ) (2220), an SNS identification information holding unit (BA) (2221), and a processing result notification unit (BB) (2222). (AN) (2212) is configured to have SNS identification information holding means (BC) (2223) for remittance. When the third embodiment is based on the second embodiment, a payment method identification information holding unit (AJ), a payment method selection reception unit (AK), and a payment method payment consideration allocation unit (AM) are further provided. Further, the payment method identification information acquisition unit (AD) (2204) is configured to acquire the payment method identification information for which the selection has been accepted in association with the employee identification information.

As described in the previous embodiment, the employee authentication unit, the user authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the user has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the employee's authority information in association with the employee identification information), the authority information holding department, the employee identification information related department, and salary claims. Information retention department, salary receivable information retention department update department, authority information notification department, authority information recording department, fixed date prepayment desired amount input department, fixed date prepayment desired amount testing department, repeatable payment range judgment department, payable consideration It may be configured to have a holding portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 8 Remittance Unique Information Holding Unit (AN) / Remittance SNS Identification Information Holding Means (BC) (2223)>

The "remittance SNS identification information holding means (BC)" (2223) is a means provided in the remittance unique information holding unit (AN) (2212), and is configured to hold the remittance SNS identification information. .. This remittance SNS identification information is held in association with the employee identification information, the payment method identification information, and the remittance unique information. The remittance-specific information may be the same as the remittance SNS identification information. "SNS identification information for remittance" is information used when sending money to an employee by a remittance means linked with SNS or charging an electronic money account used by the employee. Information used to identify an employee or electronic money account.

The SNS identification information for remittance can be used to find profile introductions of members on SNS, send and receive messages between members, find timelines (walls) by members, and become identification information for the member mutual link function. It is used when finding a blog or becoming a community member, and may or may not be the same as the SNS ID. Further, the remittance SNS ID may be different from the electronic money consumption ID.

<Embodiment 8 Hardware Configuration>

In the hardware configuration of the fixed date prepaid system of the eighth embodiment shown in FIG. 24, the program described in the seventh embodiment based on the third embodiment executes the hardware described in the premise part of the description of the embodiment as a resource. Will be done. In addition to that, the remittance unique information holding program is an SNS identification information holding subprogram that holds employee identification information, payment method identification information, remittance unique information, and further remittance SNS identification information in association with each other. Has. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions. This execution is preferably carried out continuously and without intervals. As described in the previous embodiment, the employee authentication program, the user authentication program, the authority information holding program, the remaining amount range judgment program, and the authority information registration program (the user has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the employee's authority information in association with the employee identification information.), Authority information retention program, employee identification information related program, salary claim Information retention program, salary receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 8 Processing flow>
In addition to the processing flow according to the seventh embodiment based on the third embodiment, the following processing is performed as shown in FIG. 23. The remittance unique information holding step (an) (S2302) holds the employee identification information, the payment method identification information, the remittance unique information, and further, the SNS identification information is held in association with the SNS identification information. It has an information retention substep (bc) (S2303).

In addition to these, the employee authentication step, the user authentication step, the authority information retention step, the remaining amount range judgment step, and the authority information registration step (the user is authenticated by the fixed date prepayment system with his / her own authority information). And, the authority information holding department can register the employee's authority information in association with the employee identification information.), Authority information holding step, employee identification information related step, salary claim information holding step, salary claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 8>

Since payment processing and processing result notification to employees can be executed with the same SNS and SNS linkage function, batch processing can be performed with the SNS used by employees, the labor of employee operations can be reduced, and information sharing is unified. This makes it possible to use an efficient fixed date prepayment system.

<Embodiment 9 Mainly relating to claim 9> Fixed amount repetitive payment

<Outline of Embodiment 9>

In this embodiment, all or part of the payable consideration paid to the employee on a fixed date prepayment is treated so that it is always a fixed amount on the recurring payment date. The present embodiment is based on any one of the first to eighth embodiments.

<Structure 9 of Embodiment>

The ninth embodiment is based on any one of the first to eighth embodiments. For example, in the case of the first embodiment, as shown in FIG. 25, the configuration is repeated by the employment relationship information holding unit (AA) (2501) and the salary receivable information acquisition unit (AB) (2502). Return payment date information holding unit (AC) (2503), payment method identification information acquisition unit (AD) (2504), time information acquisition unit (AE) (2505), and recurring payment date relationship judgment unit (AF) It has (2506), a recurring payment processing unit (AG) (2507), a recurring payment processing history holding unit (AH) (2508), and a salary receivable information acquisition unit (AB) (2502). , Has a fixed amount acquisition means (BD) (2524). The same effect can be obtained based on any one of the second to eighth embodiments.

As described in the previous embodiment, the employee authentication unit, the user authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the user has a fixed date with his / her own authority information). Once the prepaid system is authenticated, the authority information holding department can register the employee's authority information in association with the employee identification information.) Authority information holding department, employee identification information related department, salary claim information Holding department, salary receivable information holding department updating department, authority information notification department, authority information recording department, fixed date prepayment desired amount input department, fixed date prepayment desired amount testing department, repeatable payment range judgment department, payable consideration holding It may be configured to have a portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 9 Fixed amount acquisition means (BD) (2524)>

The "fixed amount acquisition means (BD)" (2524) is a means provided in the salary receivable information acquisition department (AB) (2502), and is the payable consideration paid to the employee acquired in association with the employee identification information. Obtain information indicating a fixed amount in whole or in part. Since it is a "fixed amount", in principle, a fixed amount is paid to the employee each time on the recurring payment date. Fixed amounts that are repeatedly paid include rent, parking fees, and various subscription services.

This acquisition source is a fixed amount holding unit that holds a fixed amount in association with the employee identification information. The fixed amount holding unit may be provided inside the fixed date prepaid system (2500) or may be provided outside. Then, the fixed amount holding unit is configured so that the fixed amount can be set and input from the terminal used by the employee. When there are a plurality of types of recurring payments, it is preferable that a fixed amount can be set individually for each recurring payment date.
This can be realized by setting, inputting, and holding a fixed amount in association with each of the plurality of recurring payment date identification information described above.

<Embodiment 9 Hardware>

In the hardware configuration of the fixed date prepaid system of the ninth embodiment, the program described in any one of the first to eighth embodiments is executed using the hardware described in the premise part of the description of the embodiment as a resource. In addition to that, the payroll receivables information acquisition program has a fixed amount acquisition subprogram. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions. FIG. 27 shows a hardware configuration based on the first embodiment.

As described in the previous embodiment, the employee authentication program, the user authentication program, the authority information holding program, the remaining amount range judgment program, and the authority information registration program (the user has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the employee's authority information in association with the employee identification information.), Authority information retention program, employee identification information related program, salary claim Information retention program, salary receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 9 Processing flow>

In addition to the processing flow according to any one of the first to eighth embodiments, the salary receivable information acquisition step (ab) includes a fixed amount acquisition substep (bd).
FIG. 26 shows a flow of processing of the present embodiment based on the first embodiment. The payroll receivable information acquisition step (ab) (S2602) has a fixed amount acquisition substep (bd) (S2603).

In addition to these, the employee authentication step, the user authentication step, the authority information retention step, the remaining amount range judgment step, and the authority information registration step (the user is authenticated by the fixed date prepayment system with his / her own authority information). And, the authority information holding department can register the employee's authority information in association with the employee identification information.), Authority information holding step, employee identification information related step, salary claim information holding step, salary claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 9>

The amount paid on the recurring payment date is fixed, which is convenient for employees who regularly spend a fixed amount repeatedly. Also, although it is not a fixed amount, if you can cover the recurring expenses with a certain amount of prepaid, you can register so that the fixed amount will be paid repeatedly with a little margin so that you do not have to enter the desired prepaid amount every time. It's convenient to get rid of it.

<Embodiment 10 Mainly relating to the invention according to claim 28>: Worker, wage; Basic

<Outline of Embodiment 10>

The tenth embodiment is a fixed date prepayment system for making so-called prepayment of wages to workers repeatedly on a predetermined date by a designated payment method.

<Structure 10 of Embodiment>

As shown in FIG. 28, the fixed date prepayment system (2800) of the tenth embodiment includes a contract-related information holding unit (BE) (2825), a labor claim information acquisition unit (BF) (2826), and a recurring payment date. Information holding unit (AC) (2803), payment method identification information acquisition unit (AD) (2804), time information acquisition unit (AE) (2805), and recurring payment date relationship judgment unit (AF) (2806). It also has a recurring payment processing unit (AG) (2807) and a recurring payment processing history holding unit (AH) (2808).

<Explanation of Embodiment 10 Configuration>

<Embodiment 10 Contract-related information holding unit (BE) (2825)>

The "Contractual Information Retention Department (BE)" (2825) identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information. It retains contractual relationship information, which is information related to information and worker identification information that identifies a worker who receives payable consideration based on labor claim information, based on a contractual relationship. This contract-related information is registered by the administrator of the fixed date prepaid system (2800), or is registered from an external terminal via the Internet with the authority of the user who is the user.

An "employer" is a person who has a contract with a worker regarding the exchange of labor and compensation, regardless of whether it is a natural person, a corporation, a union or the like. "User identification information for identifying a user" is information for uniquely identifying a user in this system, and the format of the information does not matter. Further, it is preferable that various information is retained or receivable in association with the user identification information. For example, company name, store name, location, telephone number, fax number, bank account information, email address, homepage address, representative name, representative telephone number, representative or company, store SNS identification information, user or representative Electronic money identification information, etc.

A "worker" is a person who has a contract with an employer regarding the provision of labor and the exchange of labor compensation, and is, in principle, a natural person. However, it is not limited to one person, and may be a group or the like. That is, in this case, one worker identification information is attached to the group.

There are various forms of "contractual relationships". In addition to the so-called relationship between companies and employers and regular employees, the relationship between dispatched workers and dispatch sources or destinations, the relationship between contract employees and employers with a fixed period, and the relationship between part-time workers and employers. Relationships, relationships between short-time regular employees and employers, relationships between workers who work under a business consignment (contract) contract and employers who are business consignors, relationships between domestic workers and business consignors, self-employed teleworkers And the relationship with the user who is the consignor. Therefore, in a broad sense, a contractual relationship is defined as a relationship in which the consideration for some kind of labor or the deliverables produced by the labor is received from the employer or the like.
In the present specification, the "wage" is the labor consideration paid by the "employer" to the "worker" based on the above-mentioned "contractual relationship", and is mainly paid in currency (including electronic money).

In the fixed date prepaid system (2800), in principle, it is not investigated whether the registered contractual relationship is a legally appropriate contractual relationship and is false information. If there is a registration by a genuine user or a person to whom authority has been delegated from the user, it will be operated as having a contractual relationship. However, a document or the like that can prove the contractual relationship may be configured to be retained in the fixed date prepaid system (2800) in association with the employer identification information and the worker identification information. Examples of this document include a wage payment statement and an employee ID card. In addition, if there is an external contract-related information server and information certifying the contractual relationship between the employer and the worker can be obtained, the contract-related information server is searched to see if the registration is genuine and the result is obtained. It can also be configured to secure registration accordingly.

<Implementation 10 Labor Claim Information Acquisition Department (BF) (2826)>

The “Labor Claim Information Acquisition Department (BF)” (2826) is a payable consideration that is a consideration that can be paid to a worker before the wage payment date determined with the employer based on the worker's labor claim information. All or part of is acquired based on the employer identification information associated with the worker identification information of the worker.

"Labor receivables" are also called "salary receivables" and are synonymous. Wages as compensation for labor and deliverables are also called salaries and wages. This wage takes a certain period of time to be paid to workers. For example, the wages for the previous month are paid on the 25th of the following month, for example. However, workers have the right to receive wages as compensation for labor that has already been done or deliverables that have been submitted and passed the acceptance inspection even if the wage payment date has not been reached, and this is called a labor claim. .. Therefore, if you intend to receive prepayment in the form of recurring payment before the wage payment date, the payable consideration will be calculated based on the labor claim information up to the date of receiving the prepayment.

"Labor claim information" is information on labor claims, but mainly information indicating the amount of the labor claims. In addition, information on the scheduled payment date and payment method of the wage may be included. In addition, it may contain information about the labor and deliverables that caused the wage. Labor may include information on working hours, such as when and how many hours worked, and how many hours worked in total, and information indicating where the work was done.
It may also include information such as type, quantity, quality and yield of deliverables.

<Embodiment 10 Repeated Payment Date Information Holding Unit (AC) (2803)>

The "Repeat Payment Date Information Retention Department (AC)" (2803) is information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to a worker based on labor claim information. Keep recurring payment date information associated with worker identification information.

"Payable consideration paid to workers based on labor claim information" means, for example, if there is N yen for labor claims (N is a natural number), the total amount is N yen or a fixed amount below N yen. The amount of money is M yen (N> M: M is a natural number). However, if the prepaid amount is increased too much, the future life of the worker (after this month, etc.) may become unstable, so the payable consideration as prepaid is N yen x safety factor S. preferable. It is considered appropriate that the safety factor S is about 10% to 30%. That is, N × 0.1 to N × 0.3 is preferable as a payable consideration or a part of the payable consideration.

The “payable consideration” may theoretically be the same as the amount of labor receivables, or may be less than the amount of labor receivables. "Part of the payable consideration" is the amount less than the amount of labor receivables.

“Pay repeatedly” most typically means paying at the same intervals as wage payments. For example, if the worker has a monthly salary system, he / she pays on the same day of every month, on the specified day of the week from the beginning of the month, or on what day of the week (for example, the third Monday) from the beginning of the month. You may. Alternatively, if the worker's payment date is predetermined, for example, utility bills and utility charges, the payment date and payment interval may be set for each. For example, if utility charges such as water charges are on the 10th day of each month and utility charges are on the 12th day of each month, the 10th and 12th days of each month can be used as repeated payment dates. However, it may be other than that. For example, the interval may be half or double the wage payment interval. Since the payment date can be specified on the fixed date prepayment system (2800) side, it is preferable to configure the repetitive payment so that the payment is made even if there is no request from the worker.

For example, attendance is closed at the end of the month, and from the beginning of the month to the end of the month, the labor consideration for the last month multiplied by the safety factor is used as a source of prepayment by repeated payment of this month, and there is a wage payment date on the 24th of this month. In this case, when setting the recurring payment date from the 24th of this month to the closing date of the end of the month, it can be configured to use the labor consideration of this month multiplied by the safety factor as the source of funds.
In addition, the payment amount on the recurring payment date set between the wage payment date of this month and the end of this month may be set aside from this month's wage in advance so that this month's wage is paid.

“Repeated payment date information” is therefore information for specifying the date for repeated payment, and in principle, the information indicating the date is used. The date is information indicating the date. However, this may include information indicating the time. For example, it is information such as 10 am, 1 pm, and 1:30 pm. This information on the date of the recurring payment date is associated with the worker identification information and holds the recurring payment date calculation rule. There is a recurring payment date acquisition unit, and the recurring payment date information holding unit (AC) can also be configured to hold the recurring payment date acquired by the recurring payment date acquisition unit. As mentioned above, the recurring payment date calculation rule is the same day of every month, or a predetermined day of the week specified from the beginning of the month, the day of the week from the beginning of the month (for example, the third Monday), and every month. It is preferable that a plurality of calculation formulas are prepared according to the method of repeating payment dates such as 10th and 12th.

The recurring payment date information may be associated with or may be included in the recurring payment date information. If a worker has multiple recurring prepayments, it is used to identify them.

<Implementation 10 Payment method identification information acquisition unit (AD) (2804)>

The "Payment Method Identification Information Acquisition Department (AD)" (2804) acquires payment method identification information, which is information for identifying the payment method for all or part of the payable consideration for workers, in association with the worker identification information. do.

"Payment method identification information" is information that identifies a payment method from an employer to a worker. As mentioned above, payment methods include PayPay (registered trademark), LINE Pay (registered trademark), iD (registered trademark), WAON (registered trademark), nanaco (registered trademark), Rakuten Edy (registered trademark), and QUICPay (registered trademark). Electronic money used by workers such as trademark), Suica (registered trademark), apple pay (registered trademark), and white card (registered trademark) may be paid using the point charge or remittance function, or to a bank account. You may make a transfer, transfer to a securities account, or, in some cases, charge a credit card with a charge function or a cash card with a charge function. When charging points to electronic money, the management company or management company of the fixed date prepayment system (2800) concludes a contract with each electronic money company and identifies the electronic money of the worker who uses the electronic money in a predetermined bank account. It is preferable to construct a system to automatically charge by transferring a predetermined amount of money together with information.

"Association with worker identification information" may associate one payment method identification information with one worker, and by design, a plurality of payment method identification information with respect to one worker identification information. May be associated. When multiple payment method identification information is associated with one worker identification information, the fixed date prepayment system (2800) makes multiple payment methods optional every time the payment date and the date of a predetermined relationship are reached. It is also possible to select a payment method identified by the payment method identification information and configure it to be used for payment, and the worker each time the date of the recurring payment date and a predetermined relationship or a date close to it is reached. A worker who can be identified by the identification information may be configured to use one payment method in the fixed date prepayment system (2800) by having a worker select a specific payment method identification information among a plurality of payment method identification information. .. Further, even if a plurality of payment method identification information is associated with one worker identification information, if there are a plurality of recurring payment dates, different payment method identification information is used for each recurring payment date. In association with each other, the payment method identification information can be configured to be associated with the payment date on a one-to-one basis.

"Acquisition" of payment method identification information is the repeated payment date information when the judgment result by the Repeated Payment Date Relationship Judgment Department (AF), which will be described later, is determined to have a predetermined relationship. Obtain the worker identification information associated with and the payment method identification information further associated with. This payment method identification information is therefore preferably stored in a fixed day prepayment system in advance in association with the worker identification information. Of course, it is held externally and can be configured to be acquired from the outside.

For example, a worker who receives a remittance to electronic commerce reads the bar code on the transfer form with an application for approval of a smartphone that can use electronic commerce, and registers the charged electronic money or each payment. You can pay by the method you have set (bank account or credit card).

An application for using the fixed date prepaid system (2800) is installed in the worker's smartphone, and it is linked to this or integrated with the smartphone payment (utility, gas / water charges, rent, utility charges, etc.) It is convenient to enable the function (for approval).

For example, when prepayment is made to e-commerce, the application available for the fixed date prepayment system (2800) pushes to the worker user that the prepayment has been made and that it is the payment date for utilities etc. It is conceivable to notify and indicate the amount so that payment can be completed with one push.

With the payment method identification information and the worker identification information, the bank account information of the worker in the payment method identified by the payment method identification information and the worker's unique information for charging, transferring, and transferring electronic money are acquired. It needs to be configured to allow it. For example, it is a unique information acquisition unit. The Repeated Payment Processing Department (AG) (2807), which will be described later, will actually perform payment processing using the bank account information and unique information.

The payment method identification information may be associated with the repetitive payment date identification information described above. This is because the payment method is individually set for each of a plurality of recurring payment dates. In this case, the recurring payment processing unit (AG), which will be described later, has the payment method identification information associated with the recurring payment date information or the recurring payment date identification information included therein. Perform payment processing according to the payment method identified in.

<Embodiment 10-hour information acquisition unit (AE) (2805)>

The "time information acquisition unit (AE)" (2805) acquires time information including a date. The "time information" is like information that can be read from a calendar, and in principle, refers to information on the date, but may include information indicating the time. The time may be information indicating hours, minutes, and seconds, information indicating hours and minutes, or information indicating only hours. In principle, time information refers to the current time information. This is because workers who expect to be paid in advance on the recurring payment date must be paid as promised. The acquisition source may be from an information source of time information on the Internet, or from a clock unit having a clock function provided in a fixed date prepaid system (2800).

<Embodiment 10 Repeated Payment Date Relationship Judgment Department (AF) (2806)>

The "Repeat Payment Date Relationship Judgment Department (AF)" (2806) has determined whether the acquired time information has a predetermined relationship with the repeat payment date specified in the repeat payment date information associated with the worker identification information. to decide. A predetermined relationship is a relationship in which the date specified in the recurring payment date information and the date indicated in the time information match, or the date indicated in the recurring payment information and the date indicated in the time information. The date is approaching a predetermined date, the date and time determined by the recurring payment information and the date and time indicated by the time information are approaching to a predetermined time, and so on. It is natural that the date, etc., which has a predetermined relationship with the recurring payment date information and the date, etc., which is determined by the time information, have a predetermined relationship, but it is agreed.

<Embodiment 10 Repeated Payment Processing Department (AG) (2807)>

When the "repeated payment processing unit (AG)" (2807) determines that the judgment result of the repetitive payment date relation judgment unit (AF) (2806) has a predetermined relationship with the repetitive payment date. The payment process, which is the process for payment of all or part of the payable consideration by the payment method identified by the payment method identification information acquired in association with the employee identification information, is performed. The "processing for payment" may be the payment processing itself, or may not be the payment processing itself, but may be a processing performed for the payment processing. "Payment" means transfer processing to the bank account of the electronic money operating company, transfer processing to the bank account of the worker, transfer processing to the bank account of the electronic money operating company, transfer processing to the bank account of the worker, labor. It includes various things such as charge processing for a person's electronic money and processing for a worker's electronic money transfer (transfer point).

<Embodiment 10 Repeated Payment Processing History Holding Unit (AH) (2808)>

The “Repeat payment processing history holding unit (AH)” (2808) holds the history of payment processing in the recurring payment processing unit (AG) (2807) in association with the worker identification information. This includes, in addition to the information indicating that the payment processing has been completed, information on the processing result such as the result of the payment after the payment processing, and information indicating that the payment processing could not be executed. May include.

<Embodiment 10 Hardware Configuration>

As shown in FIG. 30, the present invention and the present embodiment can basically be composed of a general-purpose computer program and various devices. The operation of the computer basically takes the form of loading the program recorded in the non-volatile memory into the main memory and executing the processing in the main memory, the CPU, and various devices. Communication with the device is done via an interface connected to the bus line. The interface may include a display interface, a keyboard, a communication buffer, and the like.

As shown in FIG. 30, the contract-related information retention program, the labor claim information acquisition program, the repeat payment date information retention program, the payment method identification information acquisition program, the time information acquisition program, and the repeat payment date relationship. The judgment program, the repetitive payment processing program, and the repetitive payment processing history holding program are held in the non-volatile memory, and these programs are read into the main memory based on the execution instructions of the series of programs to be main. It is expanded in memory and these programs are executed based on the operation start instruction.

Here, the contract relationship information retention program is information that associates the user identification information that identifies the employer and the worker identification information that identifies the worker contracted with the employer based on the contract relationship. Hold information. It can also be configured to execute the contract contract information acquisition program as a prerequisite for retention.

Next, the labor claim information acquisition program sets the payable consideration, which is the consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information, for the worker's labor. Obtained based on the user identification information associated with the person identification information. The acquisition may be obtained from a peripheral device, particularly a storage, a recording medium, an attached information of an e-mail, or a computer used by a user via the Internet.

The Repeated Payment Date Information Retention Program provides workers with repeated payment date information, which is information that determines the repeated payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor claim information. Retain in association with identification information. There may be a recurring payment date information acquisition program as a prerequisite for retention. This repeat payment date information acquisition program typically acquires the repeat payment date information desired by the worker from a terminal or the like used by the worker via the Internet.

The payment method identification information acquisition program acquires payment method identification information, which is information that identifies the payment method for all or part of the payable consideration for workers, in association with the worker identification information. This payment method identification information acquisition program typically acquires payment method identification information that identifies the payment method desired by the worker from a terminal or the like used by the worker via the Internet.

The time information acquisition program acquires time information including a date. The acquisition source of the time information may be a clock built in the fixed date prepaid system, or may be configured to acquire the time information from an external time server via the Internet.

The repeat payment date relationship determination program determines whether the acquired time information has a predetermined relationship with the repeat payment date defined in the repeat payment date information associated with the worker identification information. Judgment is made according to the relationship judgment rules described in this program. As an example of the relationship judgment rule, for example, the recurring payment date and the date indicated by the time information are within a predetermined time. As the predetermined time, for example, 24 hours, 12 hours, and the like can be considered. If there is no time information on the recurring payment date and only information on the date, it can be configured to make a judgment in relation to midnight on that date.

The recurring payment processing program acquires the employee identification information in association with the recurring payment date when the judgment result in the recurring payment date relationship judgment step (af) is the judgment result that the repetitive payment date has a predetermined relationship. Perform payment processing, which is processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information. The payment process is as described above.

The recurring payment processing history retention program retains the history of payment processing in the recurring payment processing step (ag) in association with the worker identification information. It is preferable that the history of recurring payment processing held here can be viewed via the Internet from the terminal used by the employer or the worker. That is, the recurring payment processing history viewing program is configured to be provided in the fixed date prepayment system which is a computer.

These programs acquire, retain, and perform other processing such as employer identification information, worker identification information, contractual information, recurring payment date information, payment method identification information, and time information according to their functions. .. This information is also held in the non-volatile memory, and is read and expanded in the main memory as needed. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 10 Processing flow>

As shown in FIG. 29, in the present invention and the present embodiment, the following processing is performed as an operation method of the fixed date prepaid system which is a computer described in the description of the hardware of the tenth embodiment. This process can also be described as an operation program of a fixed date prepaid system which is a computer.

As shown in FIG. 29, this process
The contractual information retention step (be) (S2901) is an employer identification information that identifies an employer who pays a payable consideration to a worker identified by the worker identification information based on the labor claim information. , Performs processing to retain the worker identification information that identifies the worker who receives the payable consideration based on the labor claim information and the contractual relationship information that is the information related based on the contractual relationship.
The labor claim information acquisition step (bf) (S2902) is the total payable consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information. Or, perform a process to acquire a part based on the employer identification information associated with the worker identification information of the worker.
The recurring payment date information retention step (ac) (S2903) is information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor claim information. Performs processing to retain payment date information in association with worker identification information,
The time information acquisition step (ae) (S2904) performs the process of acquiring the time information including the date.
The recurring payment date relationship determination step (af) (S2905) determines whether the acquired time information has a predetermined relationship with the recurring payment date defined in the recurring payment date information associated with the worker identification information. Process and
If the judgment result in the repeat payment date relationship judgment step (af) (S2905) is a judgment result that does not have a predetermined relationship with the repeat payment date, before the time information acquisition step (ae) (S2904). Perform the process to return to
When the judgment result in the repeat payment date relationship judgment step (af) (S2905) is the judgment result that the relationship with the repeat payment date has become predetermined.
The payment method identification information acquisition step (ad) (S2906) is a process of acquiring payment method identification information, which is information for identifying a payment method for all or part of the payable consideration for a worker, in association with the worker identification information. And
The recurring payment processing step (ag) (S2907) is the processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the worker identification information. Perform the processing to process the payment,
The recurring payment processing history holding step (ah) (S2908) performs a process of holding the payment processing history in the recurring payment processing step (ag) (S2907) in association with the worker identification information.
This is how the fixed date prepaid system, which is a computer, operates.

<Example of using fixed date prepaid system>
FIG. 85 shows an overall schematic configuration example of the fixed date prepaid system of the present invention. The terminal (8501) of the user A and the terminal (8502) of the user B are connected to the Internet line (8500). Attendance management information of the workers employed by each is stored in the terminal (8501) of the employer A and the terminal (8502) of the employer B, which serves as a basis for calculating the information on the claims provided by the workers. In addition, a fixed-date prepayment system operated by a wage prepayment agency or a server (8503) that stores and operates an operation program of the system, a server of bank A (8504), a server of bank B (8505), and a worker A Smartphones (8506), worker B's smartphones (8507), electronic money operating company servers (8508), SNS operating companies (8509), etc. are also connected to the Internet. As described above, a fixed date prepayment system operated by a wage prepayment agency different from the employer holds the repayment date information upon registration of the repayment information from the worker. When worker A is employed by employer A, the payable consideration is determined based on the attendance management information and recurring payment information in the terminal of employer A, either the terminal of employer A or the fixed date prepayment system. Calculate with or both. When the recurring payment date arrives, the fixed date payment system processes the payment by the payment method (financial institution, electronic money, SNS remittance means, etc.) specified by the worker A.

An example of a worker using his / her own smartphone to register the actual recurring payment date information will be described with reference to FIG. 86. FIG. 86a is an example of a screen for setting a repeat payment date, FIG. 86b is an example of an input screen for the prepaid application amount to be paid on each repeat payment date, and FIG. 86c is an example of a setting confirmation screen after the completion of input of the repeat payment date. FIG. 86abc is an example of a screen and is not limited to this layout and usage.
First, on the screen of FIG. 86a, the date at the time when the setting input is started is acquired from the time information in the smartphone and displayed as the current date, and the calendar of the corresponding month is also displayed at the start of operation. .. In FIG. 86, the operation time point is September 2, 2020. Select the year and month to be input (8601). Return from the initially displayed September 2020, or press the left and right triangle buttons to proceed. If you return from the current time, you can refer to the history when you applied for payment in the past. The corresponding calendar (8602) is displayed immediately below. September 11, which is the date (8603) circled by a dotted line, represents a date that has already been registered. It is September 24th, which is the date (8604) that is displayed in black and white inversion, that we are going to additionally register this time.
It is more preferable to configure it so that it can be added as long as the total amount of recurring payments including the newly added amount is small, rather than the amount obtained by multiplying the labor consideration by the safety factor.
For the addition operation, you can click (press) the part of the date to be added directly on the calendar, or in the start date selection field (8605) under the calendar, for each year, month, day, the triangle button next to each field. You may press to enter individual selection. Below the start date is the repeat setting. It can be set weekly (ie, every day of the week) (8606) or monthly (in the case of FIG. 86a, specified on either the 24th or the 4th Thursday of each month) (8607). Although not shown, it may be possible to set multiple months (bimonthly, quarterly, etc.), yearly, and the like. As for the setting of the end date of the recurring payment (8608), either the end date is not specified (that is, the recurring payment is executed unless the registration is deleted) or the recurring payment is specified (repeated payment until the designated end date). After entering the date, enter the amount next. If only the date is entered and the amount has not been entered yet, it is preferable that only the amount input button (8609) and the cancel button (8611) are displayed in an operable state, or the other buttons are not displayed. Press the amount input button (8609) to proceed to the prepaid application amount input screen shown in FIG. 86b.

On the prepaid application amount input screen shown in FIG. 86b, the transfer destination (8613) is selected as the payment method. In the figure, the Yurakucho branch of Chiyoda Bank is selected. Below the payee's bank account, the amount that can be paid in advance at the time of application is displayed as 127,000 yen. You can choose to pay the full balance or specify the amount (8614). To specify the amount, touch the amount input field (8615) and then enter it with the numeric keypad. If you start operating the numeric keypad directly after selecting the transfer, you may consider that you have selected the specified amount. Further, when the amount input field is pressed, options in units of 1000 yen are displayed in the pull-down menu and the selection may be made. After entering the amount, press the enter button (8616) at the bottom of the screen. To cancel the input work, press the cancel button (8618), and to cancel the input and return to the date selection screen, press the back button (8617). When the enter button (8616) is pressed, the screen returns to the setting screen shown in FIG. 86a. To add a repeat payment date, press the add button (8610), then enter the date and set the amount in the same way. When the repeat payment date setting is completed, the input completion button (8612) is pressed to move to the setting confirmation screen shown in FIG. 86c.
In FIG. 86c, the left and right triangular buttons of the year / month display (8619) can be used to check the setting status of the previous / next year / month. Date circled by dotted line (8620) September 11 is the date already registered, the date added this time is the date circled by solid line (8621), and September 24 is displayed by circled by solid line. Has been done. Below the calendar, the currently set recurring payment dates, amounts, and financial institutions are listed. It is possible to easily set the recurring payment date by such an operation on the smartphone. Note that this setting method is a specific example of operation, and can be appropriately designed without being limited to this screen.

<Effect of Embodiment 10>

In the present embodiment, the prepayment of a predetermined amount is repeatedly made on a preset fixed date by the selected payment method in principle, so that it is constant between the wage payment date and the next wage payment date. It is possible to surely make up for the shortage of funds for workers who are short of funds.

<Embodiment 11 Mainly Related to the Invention of Claim 29> Multiple Payment Methods

<Outline of Embodiment 11>

In the eleventh embodiment, based on the tenth embodiment, a worker or the like can select a payment method, and all or a part of the payable consideration can be assigned to each selected payment method.

<Structure of Embodiment 11>

As shown in FIG. 31, the fixed date prepayment system (3100) of the eleventh embodiment includes the contract-related information holding unit (BE) (3125) and the labor claim information acquisition unit (BF) (3126), which are the configurations of the tenth embodiment. ), The recurring payment date information holding unit (AC) (3103), the payment method identification information acquisition unit (AD) (3104), the time information acquisition unit (AE) (3105), and the recurring payment date relationship determination. It has a unit (AF) (3106), a recurring payment processing unit (AG) (3107), and a recurring payment processing history holding unit (AH) (3108). It has an information holding unit (AJ) (3109), a payment method selection reception unit (AK) (3110), and a payment method payment consideration allocation unit (AM) (3111). In the following description, the description of the configuration described in the tenth embodiment will be omitted, and only the configuration peculiar to the present embodiment will be described.

<Explanation of Embodiment 11 Configuration>

<Embodiment 11 Payment method identification information holding unit (AJ) (3109)>
The "payment method identification information holding unit (AJ)" (3109) holds a plurality of payment method identification information. "Payment method identification information" is information for identifying a payment method for making a fixed date prepayment. It may be information indicating the type of processing such as bank account transfer, electronic money use, cash card charge, credit card charge, etc., Mitsubishi UFJ bank account use, Mitsui Sumitomo bank account use, Resona bank account use, Mizuho Bank Account use, Saitama Sona bank account use, PayPay (registered trademark) use, LINE Pay (registered trademark) use, iD (registered trademark) use, WAON (registered trademark) use, nanaco (registered trademark) use, Rakuten Edy (registered trademark) use ) Use, QUICPay (registered trademark) use, Suica (registered trademark) use, apple pay (registered trademark) use, white card (registered trademark) use, etc. to identify the bank where the worker has an account, used by the worker What specifies the type of electronic money to be used, VISA (registered trademark) use, MasterCard (registered trademark) use, JCB (registered trademark) use, AMEX (registered trademark) use, Diners (registered trademark) use, UnionPay (UnionPay) ) (Registered trademark) may be used to specify a credit card.

Furthermore, if the system allows, information that identifies T point (registered trademark) card, Rakuten point (registered trademark) card, Ponta (registered trademark) point card, d point (registered trademark) card, JRE POINT (registered trademark) card, etc. It may be. In this case, the fixed date prepaid system is configured to allow remittance (sending points) of points. The payment method identification information held in this section is not yet associated with the worker identification information. It is preferable that the fixed date prepayment system (3100) has a payment method identification information editing unit for deleting the payment method identification information held here or adding the payment method identification information here.

<Embodiment 11 Payment method selection reception unit (AK) (3110)>

The "Payment Method Selection Reception Unit (AK)" (3110) accepts one or more selections of payment method identification information held in association with the worker identification information. The selected payment method identification information and the worker identification information associated therewith are acquired by the payment method identification information acquisition unit (AD) (3104). This is to ensure that the payment method identified by the selected payment method identification information makes a prepayment to the worker identified by the worker identification information.

This selection of payment method typically specifies worker identification information from terminals used by workers such as smartphones, mobile phones, tablet terminals, and personal computers used by workers, and accepts them via the Internet. The payment method selection reception unit (AK) (3110) may have a function of displaying the selectable payment method on the terminal used by the worker via the Internet web with an icon or the like. When the worker selects an icon displayed on the terminal used by the worker, the fixed date prepayment system (3100) can be configured to receive the signal and accept the selection of the payment method.

In addition, a dedicated application is installed in the terminal used by the worker, the payment method identification information is held in advance in the application, and the icon etc. to be displayed in association with the information is also held, and the payment method is performed by the function of the application. Allows workers to make a choice and sends the selected payment method identification information to a fixed date prepayment system (3100) so that the fixed date prepayment system (3100) receives the transmission and accepts the payment method choice. It can also be configured.

The acceptance of payment method selection may be configured so that the worker associates it with the worker identification information at the time of registration for use of the fixed date prepayment system (3100), or before the repeated prepayment date. It may be configured so that it can be selected each time in association with the worker identification information. Alternatively, the worker registers at the time of registration for use of the fixed date prepaid system (3100), and the selection is used thereafter, but the selection is configured to be changed in association with the worker identification information after the fact. You may be. Changes can be made using a dedicated application set on the terminal used by the worker for the fixed date prepayment system, or via the web page on the Internet provided by the fixed date prepayment system (3100). You may.

The selected payment method identification information is associated with the worker identification information and is held in the fixed date prepayment system (3100), or is held in a device that can be acquired by the fixed date prepayment system (3100). Will be done. The retained payment method identification information is configured to be acquired by the payment method identification information acquisition unit (AD) (3104) already described in the first embodiment.

<Embodiment 11 Payment Method Payment Consideration Allocation Unit (AM) (3111)>

The "Payment Method Payment Consideration Allocation Unit (AM)" (3111) allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information. This is to make a prepayment of all or part of the payable consideration allocated by the payment method identified by the payment method identification information to the worker. When a plurality of payment method identification information is selected, a part of the payable consideration is assigned to each payment method identification information. Multiple prepayments will be made by one or more payment methods between the wage payment date and the next wage payment date. The payment methods may be the same or different. When the payment methods are different, for example, between the wage payment date and the next wage payment date, the first transfer to a bank account and the second charge to electronic money can be made. This is because it is convenient when the payment methods that can be used for utilities, gas / water charges, rent, etc. are different.

<Embodiment 11 Hardware Configuration>

As shown in FIG. 33, the present invention and the present embodiment can basically be composed of a general-purpose computer program and various devices. The operation of the computer basically takes the form of loading the program recorded in the non-volatile memory into the main memory and executing the processing in the main memory, the CPU, and various devices. Communication with the device is done via an interface connected to the bus line. The interface may include a display interface, a keyboard, a communication buffer, and the like.

As shown in this figure, in addition to the program described in the tenth embodiment, the payment method identification information holding program, the payment method selection reception program, and the payment method payment consideration allocation program are characteristic programs in the present embodiment. Will be described.

The "payment method identification information holding program" holds a plurality of payment method identification information. The reason for holding more than one is to let the worker choose. This is for the convenience of workers. As a premise, a payment method identification information recording program for recording payment method identification information is required in this holding program. The payment method identification information recording program acquires and records the payment method identification information from a storage, a recording medium, an external device, or the like.

The "Payment Method Selection Acceptance Program" accepts one or more selections of payment method identification information held in association with the worker identification information. This selection is accepted mainly from terminals used by workers via the Internet. The payment method selection reception program communicates with the terminal of the worker who is trying to select, searches for the type and presence of the application for electronic money and the application for bank account operation in the worker's terminal, and uses it. It is convenient to configure the worker's terminal to select only possible applications for electronic money, available bank account manipulation applications, and other applications related to remittance.

This is to prevent the selection from being unable to process prepaid due to a worker's operation error. Alternatively, if the payment method identified by the selected payment method identification information is not installed on the worker's terminal, it is identified by the selected payment method identification information on the worker's terminal in conjunction with the selection. It can also be configured to download the application used for the payment method. After downloading, the worker sets and inputs the necessary items according to the guidance of the application, and when the setting is completed, the worker's payment method identification information is used only by using the information of the setting completion of the application. It can also be configured to activate the selection.

The "Payment Method Payment Consideration Allocation Program" allocates all or part of the payable consideration in association with the worker identification information to one or more selected payment method identification information. Once assigned, the payment method identification information is associated with all or part of the payable consideration and is retained in association with the worker identification information as an allocation result. The allocation is made by input from the terminal used by the worker via the Internet. At the same time, it is equipped with an allocation information acquisition program that acquires allocation information from terminals used by workers. The payment method identification information acquisition program operates to acquire the payment method identification information for which the selection has been accepted.

Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 11 Processing flow>

As shown in FIG. 32, the processing flow of the operation method of the fixed date prepaid system, which is the computer described in the description of the hardware of the eleventh embodiment, is as follows.
The contractual information retention step (be) (S3201) is an employer identification information that identifies an employer who pays a payable consideration to a worker identified by the worker identification information based on the labor claim information. , Performs processing to retain the worker identification information that identifies the worker who receives the payable consideration based on the labor claim information and the contractual relationship information that is the information related based on the contractual relationship.
The labor claim information acquisition step (bf) (S3202) is the total payable consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information. Or, perform a process to acquire a part based on the employer identification information associated with the worker identification information of the worker.
The recurring payment date information retention step (ac) (S3203) is information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor claim information. Performs processing to retain payment date information in association with worker identification information,
The payment method identification information holding step (aj) (S3204) performs a process of holding a plurality of payment method identification information.
The payment method selection acceptance step (ak) (S3205) accepts one or more selections of payment method identification information held in association with the worker identification information.
The payment method payment method identification step (am) (S3206) allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information.
The time information acquisition step (ae) (S3207) performs the process of acquiring the time information including the date.
The recurring payment date relationship determination step (af) (S3208) determines whether the acquired time information has a predetermined relationship with the recurring payment date defined in the recurring payment date information associated with the worker identification information. Process and
If the judgment result in the repeat payment date relationship judgment step (af) (S3208) is a judgment result that does not have a predetermined relationship with the repeat payment date, before the time information acquisition step (ae) (S3207). Perform the process to return to
When the judgment result in the repeat payment date relationship judgment step (af) (S3208) is the judgment result that the relationship with the repeat payment date has become predetermined.
The payment method identification information acquisition step (ad) (S3209) is a process of acquiring payment method identification information, which is information for identifying a payment method for all or part of the payable consideration for a worker, in association with the worker identification information. And
The recurring payment processing step (ag) (S3210) is the processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the employee identification information. Perform the processing to process the payment,
The recurring payment processing history holding step (ah) (S3211) performs a process of holding the payment processing history in the recurring payment processing step (ag) (S3210) in association with the worker identification information.
This is how the fixed date prepaid system, which is a computer, operates.

<Effect of Embodiment 11>

According to the eleventh embodiment, the worker can select a payment method for which payment is compatible with utility charges and the like and receive advance payment. Therefore, even a worker who has a problem of constant lack of funds during wage payment days can smoothly pay utility bills and the like, which have tended to be delayed in the past.

<Embodiment 12 Mainly Related to the Invention of Claim 30> Unique Information for Remittance

<Outline of Embodiment 12>

In this embodiment, based on the tenth or eleventh embodiment, a fixed date prepayment system is used to transfer the worker's remittance-specific information necessary for prepayment to a bank account, electronic money, or the like. By holding it, it is possible to omit the operation of inputting the same information from the worker each time.

<Structure 12 of Embodiment>

As shown in FIG. 34, the fixed date prepayment system (3400) of the twelfth embodiment has a contract-related information holding unit (BE) (3425) and a labor claim information acquisition unit (BF) (3426), which are the configurations of the tenth embodiment. ), The recurring payment date information holding unit (AC) (3403), the payment method identification information acquisition unit (AD) (3404), the time information acquisition unit (AE) (3405), and the recurring payment date relationship determination. When it has a unit (AF) (3406), a recurring payment processing unit (AG) (3407), a recurring payment processing history holding unit (AH) (3408), and is based on the eleventh embodiment. Further has a payment method identification information holding unit (AJ), a payment method selection reception unit (AK), and a payment method consideration allocation unit (AM) according to the eleventh embodiment. As a configuration, it has a unique information holding unit (AN) for remittance. In the following description, the description of the configuration described in the tenth embodiment or the eleventh embodiment will be omitted, and only the configuration peculiar to the present embodiment will be described. Although FIG. 34 shows the embodiment 10 as a basis, the same effect can be obtained even when the embodiment 11 is used as a basis.

<Embodiment 12 Remittance Unique Information Holding Unit (AN) (3412)>

The "Remittance Unique Information Holder (AN)" (3412) provides worker identification information, payment method identification information, and remittance unique information used for the payment method identified by the payment method identification information. Associate and keep. As a premise of retention, it is preferable that there is a remittance-specific information acquisition unit that acquires remittance-specific information in association with worker identification information from a terminal or the like used by a worker. In principle, this remittance-specific information is transmitted from the terminal used by the worker.

"Unique information for remittance" is a bank account number, identification information of a worker's electronic money account, remittance destination identification information when transferring money to a worker's electronic money, or a worker's SNS. It is the identification information of the worker, and also the unique information of the worker, which is indispensable for account transfer, transfer by electronic money, charge of electronic money, and the like.

Note that the remittance-specific information is changed by abolishing the bank account, acquiring a new bank account, changing the type of electronic money, acquiring a new ID of electronic money, etc. It is preferable to configure the terminal so that the unique information for remittance can be updated from the terminal used by the worker in the event of a problem. That is, it is preferable to provide a remittance-specific information update unit. It is preferable that this update is configured so that the update content is transmitted from the terminal used by the worker in association with the information indicating that the communication is the update of the remittance-specific information.

<Embodiment 12 Hardware>

The hardware of the twelfth embodiment is shown in FIG. 36 (an example based on the tenth embodiment). The hardware configuration of the twelfth embodiment is based on the hardware described in the premise of the description of the embodiment, and in addition to the program described in the tenth embodiment or the eleventh embodiment, the non-volatile memory has a unique information holding program for remittance. However, this is expanded in the main memory and executed, and the unique information for remittance is also in the non-volatile memory, which is expanded in the main memory and processed by the unique information holding program. The unique information for remittance is as already mentioned.

Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 12 Processing flow>

The processing flow of the twelfth embodiment is based on the processing flow of the tenth embodiment or the eleventh embodiment, and is characterized by having a remittance-specific information holding step (an). As an example, as shown in FIG. 35, the remittance unique information holding step (an) (S3505) is added to the processing step of the first embodiment.

<Effect of Embodiment 12>

According to the present embodiment, since the fixed date prepayment system is configured to retain the remittance unique information, the fixed date prepayment system alone does not accept the input of the remittance unique information from the worker each time on the recurring payment date. Push-type prepayment is possible for workers.

<Embodiment 13 Mainly relating to the invention according to claim 31> Repeated payment date information editing

<Outline of Embodiment 13>

In the present embodiment, when it is desired to change the recurring payment date due to the convenience of the worker, it can be changed via the Internet or the like.

<Structure 13 of Embodiment>

As shown in FIG. 37, the fixed date prepaid system (3700) of the thirteenth embodiment is based on the embodiment described in any one of the tenth to the twelfth embodiments, and further, the recurring payment date information editing unit (AP). ) (3713) is a fixed date prepayment system (3700). Based on the tenth embodiment, as shown in FIG. 37, the contract-related information holding unit (BE) (3725), the labor claim information acquisition department (BF) (3726), and the recurring payment date information holding Department (AC) (3703), payment method identification information acquisition unit (AD) (3704), time information acquisition unit (AE) (3705), recurring payment date relationship judgment unit (AF) (3706), It has a recurring payment processing unit (AG) (3707) and a recurring payment processing history holding unit (AH) (3708), and as a configuration peculiar to the present embodiment, a recurring payment date information editing unit (AP). ) (3713). Hereinafter, the repeat payment date information editing unit (AP) (3713), which is a configuration peculiar to the present embodiment, will be described.

<Explanation of Embodiment 13 Configuration>

<Embodiment 13 Repeated Payment Date Information Editing Department (AP) (3713)>

The "Repeat Payment Date Information Editing Department (AP)" (3713) edits the Recurring Payment Date Information and / and the Worker Identification Information held in the Recurring Payment Date Information Holding Department (AC) (3703). .. Editing information is input via the Internet from a terminal used by workers. When editing, it will be possible after authenticating with worker identification information, other passwords, worker's face photo, worker's face image, worker's voice, worker's fingerprint, etc. It is preferable to configure in. The fixed date prepayment system (3700) preferably has such a worker certification unit and an employer certification unit described later. This "editing" is to perform one or more operations of addition, change, and deletion on the repeated payment date information and / and the worker identification information. The user authenticates with the user authentication department using his / her own user identification information, password, user's face photo, user's face image, user's voice, user's fingerprint, etc. It is preferable to configure it so that it can be edited with.

However, as a general rule, the worker identification information cannot be added or changed from the terminal used by the worker. From the terminal used by the employer, it may be possible to add, change, or delete the worker identification information after the authentication process. The deletion of the worker identification information effectively suspends the prepayment process on the prepayment date because there are no more prepayment targets for the prepayment date. A change in the recurring payment date is a change in the date on which the recurring prepayment is made.

<Embodiment 13 Other Addition of Repeated Payment Dates (Second and subsequent Repeated Payment Dates)>

The addition of a recurring payment date prepares for another new recurring prepayment. Based on the worker's labor receivable information and some of the payable consideration paid on other recurring payment dates, the prepaid amount required by the worker on the new recurring payment date can be repaid. It is judged whether there is. This new prepayment amount is based on the labor claim information acquired by the Labor Claim Information Acquisition Department (BF) based on the employer identification information contracting the worker when input from the terminal used by the worker. It will be determined by judging whether the acquired payable consideration is within the range of the remaining amount excluding a part of the payable consideration paid on the other recurring payment dates.

<Embodiment 13 Others Judgment unit within the remaining amount range>

It is desirable that the fixed date prepaid system (3700) has such a determination unit within the remaining amount range. If the result of this determination is determined to be within the range, a new recurring payment date will be activated. That is, when the repeat payment date relationship judgment unit (AF) (3706) determines that the relationship between the repeat payment date and the time information has become a predetermined relationship, the payment process is performed. It will be executed. A plurality of recurring payment date information is effectively held in the recurring payment date information holding unit (AC) (3703) in association with one worker identification information. If it is determined that it is not within the above range, the recurring payment date associated with the worker identification information of the Recurring Payment Date Information Holder (AC) (3703) is not updated.

<Embodiment 13 Other editing by employer New worker>

If the employer makes this edit, the worker identification information is added to the Repeated Payment Date Information Retention Department (AC) (3703) as a preliminary preparation for allowing new workers to pay in advance. Is. If the worker identification information assigned to the worker is available in the Repeated Payment Date Information Holding Department (AC) (3703), the worker can use the Repeated Payment Date Information Editing Department (AP) (3713). It is possible to make prepayment of repayment by associating the repayment date information indicating a new repayment date with the worker identification information of oneself.

If the employer records new worker identification information in the Repeated Payment Date Information Retention Department (AC) (3703), the worker will edit it later. It is configured so that it cannot be edited without authority, and as authority information, the above-mentioned password, worker's face photo, worker's face image, worker's voice, worker's fingerprint, etc. are fixed date prepayment system (3700). ). It is desirable that these authority information is held in the authority information holding unit in association with the worker identification information. When the employer is authenticated by the fixed date prepayment system (3700) with his / her own authority information, the employer can register the worker's authority information in association with the worker identification information at the authority information registration department. When the authority information of a new worker is registered and retained in the authority information holding section, it is advisable to establish an authority information notification section that notifies the relevant new worker or the employer of the retention at the same time. Not only new registration but also when the already registered and held authority information is edited, the worker associated with the edited worker identification information or the employer can be notified. It is also preferable to provide an authority information recording unit that records the history of new registration and editing of authority information.

<Implementation 13 Other acquisition of labor claim information>

In addition, the newly registered worker identification information is retained and managed by the employer in the fixed date prepayment system (3700) or in the server managed by the employer in association with the worker identification information. It is also used to obtain labor claim information. That is, the worker identification information associated with the labor claim information and the worker identification information held in the Repeated Payment Date Information Holding Department (AC) (3703) are the same information. The meaning of the same information indicates that the meaning of the information contained in the description is the same even if the description is formally different. Alternatively, the worker identification information held in the Repeated Payment Date Information Holding Department (AC) (3703) in the Worker Identification Information Related Department is held in the Labor Claim Information Holding Department in association with the labor claim information. It may be associated with the worker identification information provided.

In this case as well, the meaning of the worker identification information is the same. The information of the labor claim information holding unit may be updated manually by the employer, or may be linked to the worker's attendance management system used by the employer or the like. When linked to the attendance management system, it is configured to be automatically updated based on the number of working days and / and the working hours of the worker and the information such as the worker's monthly salary, annual salary, and hourly wage. You may set up a salary claim information holding department update department. The time and attendance management system can also be configured to automatically update the labor claim information according to the employee ID of the worker or the location information from the smartphone.

<Embodiment 13 Hardware>

As shown in FIG. 39 (an example based on the tenth embodiment), the hardware configuration of the thirteenth embodiment is based on the hardware described in the premise of the description of the embodiment, and any of the tenth embodiment to the twelfth embodiment. In addition to the program described in 1 above, a recurring payment date information editing program is provided in the non-volatile memory, and this is expanded and executed in the main memory. If there is a residual amount range determination program that has the above-mentioned residual amount range determination function, efficient processing becomes possible. Therefore, as information, new prepaid desired amount information desired by the worker is stored in the main memory as a processing target and used for judgment within the remaining amount range.

In addition, the judgment result information indicating the judgment result is also acquired in the main memory by the judgment program within the residual amount range, and the labor claim information acquisition program determines the recurring prepayment amount which is a part of the new payable consideration according to the judgment result. get. Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 13 Processing flow>

As shown in FIG. 38, the processing flow of the present embodiment is based on any one of the tenth to the twelfth embodiments. And the peculiar part is that there is a repeat payment date information editing step (ap). The processing flow shown in FIG. 38 is based on the processing flow of the tenth embodiment. The recurring payment date information editing step (ap) (S3810) is a feature of the present embodiment.

<Effect of Embodiment 13>

In the fixed date prepayment system of the present embodiment, since it is possible to edit the repeated payment date, etc. of the payment date information holding unit repeatedly, it is flexible even if the payment date of utility charges, etc. of workers is changed. It is possible to change the recurring payment date.

<Example 14 Mainly relating to the invention according to claim 32> Repeated payment date information record

<Outline of Embodiment 14>

The fixed date prepayment system of the present embodiment is configured to newly record recurring payment date information and / and worker identification information.

<Structure of Embodiment 14>

As shown in FIG. 40, the fixed date prepaid system (4000) of embodiment 14 is based on any one of embodiments 10 to 13. FIG. 40 is a functional block diagram of the present embodiment based on the tenth embodiment. As shown in this figure, the contract-related information holding section (BE) (4025), the labor claim information acquisition section (BF) (4026), the recurring payment date information holding section (AC) (4003), and the payment method. Identification information acquisition unit (AD) (4004), time information acquisition unit (AE) (4005), recurring payment date relationship judgment unit (AF) (4006), recurring payment processing unit (AG) (4007) And a recurring payment processing history holding unit (AH) (4008), and further having a recurring payment date information recording unit (AR) (4014). The description of the already explained part will be omitted, and the recurring payment date information recording part (AR) (4014) peculiar to the present embodiment will be described.

<Explanation of Embodiment 14 Configuration>

<Embodiment 14 Repeated Payment Date Information Recording Unit (AR) (4014)>

The "Repeat payment date information recording unit (AR)" (4014) has a function of newly recording the recurring payment date information and / and the worker identification information in the repetitive payment date information holding unit (AC) (4003). Have. This new record can be newly recorded by the administrator of the fixed date prepayment system (4000) or an authorized employer, and is repeated by the worker identified by the authorized worker identification information. A new record of payment date is made. As mentioned above, the worker identification information and the repaid payment date information are associated with each other and finally held in the repaid payment date information holding unit (AC) (4003). Only person identification information is recorded. This is done from the terminal used by the authorized user in principle.

The authority of the employer is given by the Employer Certification Department, and the authority of the worker is given by the Worker Certification Department. The authority information is held by the authority information holding unit as described above. The initial user's authority information is registered in the authority information registration department by a person who has the administrator authority of the fixed date prepaid system (4000), and the registered record is recorded in the authority information holding department, and thereafter. The administrator of the fixed date prepaid system (4000) notifies the employer of the authority information, and the employer records the first worker identification information by using the authority information learned in the notification. Will be able to.

As described above, at the same time as recording the worker identification information, the employer can record the worker's authority information in association with the worker identification information in the authority information holding department, and this worker's authority information is recorded in the worker. By notifying the employer, the worker uses his / her authority information to be authenticated by the worker certification department, and the repaid payment date information indicating a new repaid payment date in association with his / her worker identification information. Can be recorded.

<Implementation 14 Retention of all or part of payable consideration>

After the repeat payment date information can be recorded in association with the worker identification information, the worker then inputs the desired amount of prepayment to the fixed date prepayment system (4000) from the terminal or the like used by the worker. The entered recurring prepayment amount is then tested. In the test, the fixed date prepayment system (4000) uses the worker identification information to access the labor claim information holding section owned by the worker or the labor claim information server used by the employer, and the prepayment amount is the labor claim information. Judge whether it is within the repeatable payment range based on. The repetitive payable range determination unit in the fixed date prepaid system (4000) may perform such a function. Alternatively, a fixed date prepayment desired amount input section for inputting the prepayment desired amount and a fixed date prepayment desired amount testing section for testing whether the prepayment desired amount is within the repeatable payable range based on the labor claim information are provided. May be good.

If the judgment result of the repeatable payment range judgment unit is the repeatable payment range, the amount is paid in association with the worker identification information and the repeat payment date information. Recorded and retained as all or part of the possible consideration. This is the function of the payable consideration holding department. This payable consideration holding unit may be provided in the fixed date prepaid system (4000) or may be provided externally. Then, on the recurring payment date specified in the recurring payment date information, all or part of the held payable consideration is acquired by the Labor Claim Information Acquisition Department (BF) (4026).

<Relationship with the recurring payment information editorial department of the 14th embodiment>

The "repeated payment date information editing unit" of the thirteenth embodiment has a function similar to that of the "repeated payment date information recording unit" of the present embodiment, but the "repeated payment date information editing unit (AP)" of the fourth embodiment also has a function similar to that of the "repeated payment date information recording unit". And the “repeated payment date information recording unit (AR)” of the present embodiment may be provided in one fixed date prepayment system.

<Embodiment 14 Hardware>

As shown in FIG. 42 (an example based on the tenth embodiment), the hardware configuration of the fourteenth embodiment is as shown. Based on the hardware described in the premise of the description of the embodiment, the non-volatile memory has a recurring payment date information recording program in addition to the program described in any one of the tenth to the thirteenth embodiments. It is expanded in memory and executed.

It should be noted that if there is a judgment program within the remaining amount range, which is carried by the above-mentioned judgment function within the remaining amount range, efficient processing becomes possible. Therefore, as information, new prepaid desired amount information desired by the worker is stored in the main memory as a processing target and used for judgment within the remaining amount range. In addition, the judgment result information indicating the judgment result is also acquired in the main memory by the judgment program within the residual amount range, and the labor claim information acquisition program determines the recurring prepayment amount which is a part of the new payable consideration according to the judgment result. get.

In addition to the programs already explained in this embodiment on the hardware described in the premise of the above-mentioned functions, the user certification program and the worker certification program are used to realize each of the above-mentioned functions. , Authority information retention program, authority information notification program, authority information recording program, prepaid desired amount input program, prepaid desired amount test program, repetitive payable range judgment program, payable consideration holding program. ..

Based on the execution instructions of a series of programs, these programs are read into the main memory, and these programs are executed based on the operation start instruction. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 14 Processing flow>

The present embodiment has a recurring payment date information recording step (ar) based on the processing flow according to any one of the tenth to thirteenth embodiments. FIG. 41 shows an example having the recurring payment date information recording step (ar) (S4104) based on the processing flow of the tenth embodiment. Although the recurring payment date information recording step (ar) (S4104) is described here at an intermediate position, it may be placed at the first step of processing, the last step of processing, or another intermediate position. It is possible.

<Effect of Embodiment 14>

In the present embodiment, when the employer first uses the fixed date prepaid system, or when a new worker is registered, it can be efficiently performed.

<Embodiment 15 Mainly Related to the Invention of Claim 33> Arbitrary Date Prepaid Processing

<Outline of Embodiment 15>

The present embodiment is a system that can make a prepayment request to a worker on an arbitrary date by using a fixed date prepayment system.

<Structure 15 of Embodiment>

The fixed date prepayment system of the fifteenth embodiment is based on the fixed date prepayment system of any one of the tenth to the fourteenth embodiments so that the worker can make a prepayment request on any non-fixed date. Is. As shown in FIG. 43, in the functional block based on the tenth embodiment, the contract-related information holding unit (BE) (4325), the labor claim information acquisition unit (BF) (4326), and the recurring payment date information holding Department (AC) (4303), payment method identification information acquisition unit (AD) (4304), time information acquisition unit (AE) (4305), recurring payment date relationship judgment unit (AF) (4306), It has a recurring payment processing unit (AG) (4307) and a recurring payment processing history holding unit (AH) (4308), and further, as a characteristic configuration of the present embodiment, is a start processing request acquisition unit (AS). ) (4315), start processing request time information acquisition unit (CD) (4344), prepaid amount acquisition unit (AT) (4316), prepaid request amount acquisition unit (AW) (4317), and prepaid processing unit. A fixed date prepayment system (4300) comprising (AX) (4318) and a prepayment history holding unit (AY) (4319).

In addition, in order to realize the functions described in the 13th and 14th embodiments, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer is If the fixed date prepayment system is certified with its own authority information, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, and the worker identification. Information-related department, labor claim information holding department, labor claim information holding department updating department, authority information notification department, authority information recording department, fixed date prepayment desired amount input department, fixed date prepayment desired amount testing department, repeatable payment range It may be configured to have a judgment unit and a payable consideration holding unit.

The configurations described in the tenth to the fourteenth embodiments will be omitted, and only the configurations specific to the present embodiment will be described below.

<Explanation of Embodiment 15 Configuration>

<Embodiment 15 Start processing request acquisition unit (AS) (4315)>

The “start processing request acquisition unit (AS)” (4315) acquires a start processing request for a wage prepayment request in association with the worker identification information. This prepayment is different from the fixed date prepayment described so far and is required by the worker from the employer at any time. However, this does not mean that workers are required to be registered to allow fixed date prepayment through the fixed date prepayment system (4300). The worker who can make this start processing request may be a worker who does not use the fixed date prepayment. That is, it does not matter whether or not the worker identification information is retained in association with the recurring payment date information in the recurring payment date information holding unit (AC).

The start processing request is typically transmitted from a terminal used by the worker. That is, the terminal used by the worker has a start processing request transmission unit. The start processing request transmission unit may be a fixed date prepayment system (4300) provided on a web page that can be viewed on the worker's terminal, or can be used on the worker's terminal. It may be one provided on the application.

<Embodiment 15 Start processing request time information acquisition unit (CD) (4344)>

The “start processing request time information acquisition unit (CD)” (4344) acquires time information including the date when the start processing request is acquired. Specifically, the timing of receiving the start processing request is acquired. The date is a typical example, but time information may be attached to this. Hours, minutes, seconds.

The time information may be obtained from the same source used by the fixed date prepaid system (4300) or may be different. The start processing request time information acquisition unit (CD) (4344) may be the same as the time information acquisition unit (AE) (4305) of the fixed date prepaid system (4300). However, it is characterized in that the time information is acquired in conjunction with the acquisition of the start processing request.

<Embodiment 15 Prepaid Amount Acquisition Department (AT) (4316)>

The Prepaid Amount Acquisition Department (AT) (4316) uses labor claim information associated with worker identification information and, where available, recurring payment date information associated with worker identification information. When possible, obtain the prepayable amount, which is the amount that allows the prepayment request, based on all or part of the payable consideration paid on the recurring payment date associated with the worker identification information. However, if the worker does not use fixed date prepayment, that is, who has not received all or part of the payable consideration on the recurring payment date, the work associated with the worker identification information. Information on the recurring payment date information based on the receivable information and all or part of the payable consideration paid on the recurring payment date is not used. This information is flagged as "unavailable".

As mentioned above, if all of the payable consideration is paid in advance, the life of the worker may become unstable because there is no wage to be paid on the wage payment date. This is based on the premise that the compensation for the labor of last month will be paid as wages in the following month at the end of the month. Therefore, the amount of payable consideration paid on the recurring payment date is that the number of working days in the last month was D1 and the planned number of working days in this month was D2. It is assumed that the number of working days is the D4 day from the beginning of the month (assuming D1> D4> D3). Assuming that the worker's daily labor consideration is a yen, the payable consideration to this worker the next day is D1 x a yen, assuming that no fixed date prepayment has been made this month. This is based on the premise that only the balance of labor consideration last month will be paid in advance.

Assuming that this month's fixed date prepayment is calculated based only on last month's labor receivables, if the fixed date prepayment safety factor is S, the prepayment amount is D1 x a x S yen, which will be paid this month. The wage is the balance of D1 x a x (1-S) yen. If the fixed date prepayment has not been made yet and the fixed date prepayment has not been made, the labor receivable of last month will be D1 × a. If it is D1 × a × (1-S) yen and the wage payment date or later is the current date (assuming D1> D3> D4), the labor receivables of last month will be 0 yen. In other words, the policy of processing prepaid payments only based on last month's labor receivables will result in different sources of prepaid payments depending on when the prepaid bill is made on any date. Furthermore, the source of funds also depends on the size of S.

That is, the influence rate of the prepaid amount on any date changes with the amount that can be paid to the employee on the wage payment date according to the magnitude of the safety factor S paid by the fixed date prepaid. Therefore, how the timing indicated by the date and time information of the start processing request is related to the recurring payment date indicated by the recurring payment date information, and the payable consideration paid on the recurring payment date ( (All) Depending on how large a part of the amount is, it will be necessary to set the prepaid amount on any date.

For example, if it is possible to make advance payments on any date until the amount of labor receivables D1 x a yen reaches T% last month, the combined safety factor T is considered to be about 20% to 40%. That is, as a result of the fixed date prepayment and the voluntary date prepayment, the amount R of the wage that should be finally paid to the worker on the wage payment date is D1 × a × 0.8> R> D1 × a × 0.6. The degree is considered appropriate.

The compound safety factor T may be configured to be adjusted according to the worker's past prepaid history. It is conceivable to take a large T value for workers who frequently use prepaid payments and a small T value for workers who do not. It is also desirable to adjust the allowance for prepaid on any date in relation to the wage payment date and the timing of the start processing request. If there are still many days left before the wage payment date, it is preferable to adjust the permissible amount of prepayment to a smaller amount because prepayment of multiple arbitrary dates may occur. The allowance can be adjusted to a large extent.

<Embodiment 15 Prepaid Request Amount Acquisition Department (AW) (4317)>

The “prepaid request amount acquisition unit (AW)” (4317) acquires the prepaid request amount in association with the worker identification information within the range not exceeding the prepaid possible amount. The prepaid request amount is transmitted from the terminal used by the worker as described above. The worker identification information is configured to be entered by the worker each time and associated with the prepayment request amount, or to be held in the terminal used by the worker and automatically associated with the transmission of the prepayment request amount. You can also do it. This is the same for web communication with the fixed date prepayment system (4300) and for communication via the application for the fixed date prepayment system (4300). It may be sent on the web via the Internet or sent by an application available on the terminal.

There are two styles before the prepaid amount is determined.

One is to let the worker arbitrarily enter the prepaid request amount, determine whether it is within the range of the prepaid amount on the fixed date prepaid system (4300) side, and if it is within the range, move on to processing the requested amount and prepaid. If the amount exceeds the possible amount, the worker is asked to send the requested amount again, and this is repeated in some cases, and when the required amount is finally within the range of the prepaid amount, the requested amount is reached. It is about moving to processing. In this case, since the prepaid request amount transmitted by the worker is an arbitrary amount, the fixed date prepaid system (4300) is used to compare the requested amount with the prepaid possible amount.

The other is to have the worker determine the prepaid amount within the range based on the prepaid amount previously acquired in the fixed date prepaid system (4300). In this case, the prepaid amount is transmitted in advance to the terminal used by the worker, and the prepaid amount is displayed on the display of the terminal.

Further, the prepayable amount means the upper limit of the prepayable amount, but it is also conceivable to have the worker select the prepayment request amount within the range below the prepayable amount. In this case, the option is transmitted from the fixed date prepayment system (4300) to the worker's terminal and displayed on the display of the worker's terminal. Further, it is preferable to configure the option as an icon so that the value is transmitted to the fixed date prepaid system (4300) as a prepaid request amount by simply touching the icon. This may also be done via the Internet via a web page provided by the fixed date prepayment system (4300) or by using an application available on the terminal for the fixed date prepayment system (4300). ..

<Embodiment 15 Prepaid processing unit (AX) (4318)>

The “prepaid processing unit (AX)” (4318) performs prepaid processing, which is processing for prepaid the acquired prepaid request amount. Since the "prepayment process" is a process for "for" the prepaid payment, it does not have to be the process of the actual remittance, transfer, or charge itself. It may be a pre-processing for remittance, transfer, or charging. The prepayment process is the same as the payment process already described in the first embodiment, and is the transfer process to the bank account of the electronic money operating company, the transfer process to the worker's bank account, and the transfer process to the bank account of the electronic money operating company. , Worker's bank account transfer processing, worker's electronic money charge processing, worker's electronic money transfer (transfer point) processing, etc.

<Implementation 15 Prepaid processing unit (AX) Other payment method identification information>

When the prepayment request amount is acquired from the worker's terminal, it is possible to configure the payment method identification information to be directly or indirectly associated with the worker identification information. The prepaid amount acquisition unit (AW) (4317) may be configured to acquire the payment method identification information at the same time as acquiring the prepaid request amount. In addition, the payment method identification information is acquired by the payment method identification information acquisition unit (AD) (4304) already described in the fixed date prepayment system (4300) in association with the worker identification information, and the acquired payment method identification information is obtained. It can also be configured to be associated with the prepayment request amount via worker identification information.

Alternatively, a payment method identification information acquisition unit (AD) (4304) for the fixed date prepayment system (4300) may be provided separately from the payment method identification information acquisition unit (AD) (4304). This is because the payment method may be different each time because it is a prepaid request on an arbitrary date. The meaning of the payment method identification information itself is as described in the first embodiment.

It is also possible to divide the total amount of the prepaid request amount into a plurality of payment methods and make a partial payment. In that case, the prepaid request amount is divided into multiple amounts, and the worker is made to select the same number of payment method identification information as the divided amount, and the process of allocating to each amount is performed on the worker's terminal. The result needs to be sent to the fixed date prepayment system (4300). Then, the prepaid processing unit (AX) (4318) needs to execute a plurality of prepaid processing based on the transmission from the worker. As an interface for this processing in the worker terminal, a payment method icon is displayed in the vicinity of a plurality of divided payment request amounts, and an icon is selected for each payment request amount to display the payment request amount and payment method identification information. It's about associating.

<Embodiment 15 Prepaid history holding unit (AY) (4319)>

The “prepaid history holding unit (AY)” (4319) holds the prepaid history, which is the history of the prepaid processing in the prepaid processing unit (AX), in association with the worker identification information. In addition to the history of the completion of the prepaid processing, the history of the processing after the prepaid processing may be included. In other words, it is the history of actual execution of processes such as transfer, remittance, and charge. It is conceivable that these records the history based on the processing report from the server such as the company that performs the processing after the prepaid processing.

<Embodiment 15 Hardware>

The hardware of the fixed date prepayment system of the fifteenth embodiment is based on the hardware described in the premise of the description of the embodiment, and further includes the program described in the description of the hardware of the tenth embodiment to the fourteenth embodiment, and further. The start processing request acquisition program, the start processing request time information acquisition program, the prepayable amount acquisition program, the prepayment request amount acquisition program, the prepayment processing program, and the prepayment history holding program for realizing the above functions are non-volatile. While holding it in the sex memory, expand each to the main memory based on the start command, and execute the program according to the necessary procedure. Data and information used / / and generated / acquired are also expanded from the non-volatile memory to the main memory. The data is data showing the amount of money, such as all or part of the payable consideration amount, the prepaid amount, the prepaid request amount, or the prepaid amount, the divided amount of the prepaid amount, etc. Person identification information, payment method identification information, prepaid history, start processing request time information, and the like. In addition, in order to realize the functions described in the 13th and 14th embodiments, the worker authentication program, the employer authentication program, the remaining amount range judgment program, the authority information holding program, and the employer use their own authority information. Once certified by the fixed date prepayment system, the authority information holding department can register worker authority information in association with worker identification information. Worker authority information registration program, worker identification information related program, labor Receivable information retention program, labor receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repetitive payable range judgment program, payable pair A value retention program, may be similarly configured, deployed, and run on hardware. As for the terminals used by workers, hardware resources such as smartphones are used by the corresponding programs in cooperation with these programs. This point is the same from the first embodiment to the present embodiment.

<Example 15 Processing flow>

In addition to, or partially or entirely, in addition to the flow of processing according to any one of the processes of Embodiment 10 to Embodiment 14, the following processing is performed. As shown in FIG. 44, the processing flow of the tenth embodiment is on the left side, and the processing flow peculiar to the present embodiment is on the right side. To explain the processing flow on the right side,
In the start processing request acquisition step (as) (S4409), the process of acquiring the start processing request of the wage prepaid request is performed in association with the worker identification information, and if it is not acquired, the labor claim information acquisition of the processing flow on the left side is acquired. If you go back to step (bf) (S4402) and get it,
In the start processing request time information acquisition step (cd) (S4410), the process of acquiring the time information including the date when the start processing request is acquired is performed.
In the prepayable amount acquisition step (at) (S4411), the labor receivable information associated with the worker identification information and, if available, the recurring payment date information associated with the worker identification information are not available. If possible, process to obtain the prepayable amount, which is the amount that allows the prepayment request, based on all or part of the payable consideration paid on the recurring payment date associated with the worker identification information. ,
In the prepayment request amount acquisition step (aw) (S4412), the prepayment request amount is acquired by associating it with the worker identification information within the range not exceeding the prepayment possible amount.
In the prepaid processing step (ax) (S4413), a process for performing prepaid processing, which is a process for prepaid the acquired prepaid request amount, is performed.
In the prepayment history holding step (ay) (S4414), the prepayment history, which is the history of the prepayment processing in the prepayment processing step (ax) (S4413), is held in association with the worker identification information.
This is how the fixed date prepaid system, which is a computer, operates.

These processing steps are separate processes from the fixed date prepayment processing of Embodiments 10 to 14, and when the relationship between the time information and the recurring payment date is other than the predetermined relationship in the fixed date prepayment processing. A branch for determining whether or not to make a prepaid date on an arbitrary date can be inserted in, and a process specific to the present embodiment can be executed when it is determined that a prepaid process on an arbitrary date should be performed. In addition, whether or not to execute the prepayment on an arbitrary date is first triggered by the acquisition of the start processing request by the worker.

An example of the registration work when a worker applies for prepaid payment on an actual arbitrary date using his / her smartphone will be described with reference to FIG. 87. FIG. 87a is an example of a prepaid payment date setting screen of an arbitrary date, FIG. 87b is an example of a prepaid application amount input screen to be paid on the prepaid payment date, and FIG. 87c is an example of a setting confirmation screen after the setting input is completed. FIG. 87abc is an example, and the layout and usage are not limited.
First, on the screen of FIG. 87a, the date at the time when the setting input is started is acquired from the time information in the smartphone and displayed as the current date, and the calendar of the corresponding month is also displayed at the start of operation. .. In FIG. 87a, the time of operation is September 2, 2020. Select the year and month to be input (8701). Return from the initially displayed September 2020, or press the left and right triangle buttons to proceed. If you return from the current time, you can refer to the history when you applied for payment in the past. The corresponding calendar (8702) is displayed immediately below. The date to be registered this time is September 16th, which is the date (8703) that is highlighted in black and white.
The prepaid application on an arbitrary date may be a prepaid application requesting payment on the day of application. If the payment is requested from the fixed date prepayment system to the financial institution involved in the payment and the payment cannot be made on the same day due to the time required for payment, the prepayment agency may temporarily reimburse the funds from its own funds and execute the prepayment processing. good.

If the amount applied for this time is less than the balance obtained by multiplying the labor consideration by the safety factor and subtracting the total amount already paid by recurring payment or prepayment on any date, additional registration is possible. As in the example of the embodiment described later, if the balance of the prepaid amount that can be prepaid by the prepaid payment date that has already been set is estimated and calculated from the present time to the future, and the prepaid request amount is paid on the prepaid date of any date, If the recurring payment set earlier becomes impossible, it is preferable to reduce the prepaid amount, which is the basis for determining acceptance of the prepaid request amount, and display it to the worker. In the case of a worker who closes at the end of each month and pays on the 24th, in the example of FIG. 87, there is a closing of attendance for August on August 31, and compensation for the work for August is paid on September 24. If only the amount obtained by multiplying the labor consideration for August by the safety factor is used as the source of prepayment, the prepayment application amount will be adjusted so that the prepayment application for any date in September will not be hindered by the already set recurring payment. It is easy to induce them to do so. If you apply for prepayment on an arbitrary date after the wage payment date, for example, on October 5, the accumulation of labor consideration for the wages scheduled to be paid in October is insufficient as of September 2, and the set repetition in October Due to the balance with payment, it may not be possible to set prepayment for any date.
If the prepaid agency is registered as a money lending business, it is an estimated labor that estimates the labor performance in September based on the attendance record of the specified number of days for at least one month in the past. The amount obtained by multiplying the consideration by the safety rate is the estimated prepaid amount, and the amount obtained by subtracting the total amount of recurring payments in October from the estimated prepaid amount is compared with the prepaid application on the above arbitrary date. May be configured to determine if it is payable and to notify the worker of the adjustment of the application amount. In this case, the prepaid agent should be registered as a money lending business as described above in order to make a decision to accept the prepaid application before the labor consideration is incurred.
If the work record in September is low, it is better to notify that the payment amount will be insufficient before the entered arbitrary date prepayment date in October or the set recurring payment date.

In the reservation addition operation on the screen shown in FIG. 87a, the part of the date to be directly added may be clicked (pressed) on the calendar, or the year, month, and year, month, may be displayed in the prepaid reservation date selection field (8704) under the calendar. You may individually select and input by pressing the triangle button next to each column for each day. The amount that can be paid in advance is displayed below the reservation date. Below that, there is an amount setting column (8705) and a transfer destination financial institution selection column (8706). When the amount setting field (8705) is pressed, the screen changes to the amount input screen shown in FIG. 87b. Either the amount input or the transfer destination selection order may come first.
To specify the amount, touch the amount input field (8710) and then enter it with the numeric keypad. If you start operating the numeric keypad directly, you may consider that you have selected the specified amount. If you enter an amount that exceeds the amount that can be paid in advance, the amount you have entered once disappears, and you can configure it so that an error message such as "input error" or "excess amount" appears (example in case of excess amount). Is not shown). The amount of money can be selected by pressing the amount input field and displaying the options in units of 1000 yen from the pull-down menu, or by touching the icon with the amount of money such as 10000 yen or 1000 yen. It may be in the form of If you touch the icon of 20000 yen and then touch the icon of 2000 yen, you may enter 22000 yen, or you may touch the icon written as 22000 yen. When you enter the amount, the fee required to apply for the amount in advance should be displayed below the entered amount. Further, when the prepaid amount is 127,000 yen, the pull-down menu or the icon may be configured so that options are presented in units of 1,000 yen with a maximum value of 127,000 yen. Since the number of choices is large, it is preferable to have a pull-down menu scrolling function and a screen scrolling function in which icons are displayed.
In FIG. 87b, the display is included in the prepaid amount, and since the fee is 1200 out of the prepaid amount of 20000 yen, the subordinate actually receives 18800 yen. The fee may be excluded from the input amount, and when receiving a prepayment of 20,000 yen, the fee of 1,200 yen may be deducted each time or in a lump sum in addition to the 20,000 yen. This prepayment fee may be paid by the employee or by the employer as part of the welfare program. At least part of the fee may be borne by the financial institution used for payment. The prepayment up to once a month may be borne by the user, and the second and subsequent payments may be borne by the employee.
After entering the amount, press the enter button (8711) at the bottom of the screen. Pressing the enter button (8711) returns to the screen shown in FIG. 87a. After selecting the financial institution to transfer to (LINE Pay (registered trademark) in FIG. 87a), press the enter button (8707). The prepaid reservation date (8715) added this time, which changes to the confirmation screen of FIG. 87c, is displayed as a solid circle in the calendar. In Figure 87c, September 16th. The reservation date, amount, and payment financial institution are listed under the calendar, and if there is no problem, press the execute button to complete the setting. It is possible to easily set the recurring payment date by such an operation on the smartphone. Note that this setting method is a specific example of operation, and can be appropriately designed without being limited to this screen.

<Embodiment 16 Mainly Regarding Claim 34> Processing Notification on SNS

<Outline of Embodiment 16>

In the present embodiment, the result of the above payment processing is notified to the worker via the SNS used by the smartphone or the like used by the worker.

<Structure 16 of Embodiment>

This embodiment is based on any one of the tenth to the fifteenth embodiments, and further includes a processing result acquisition unit (AZ), an SNS identification information holding unit (BA), and a processing result notification unit (BB). For example, as shown in FIG. 46, in the case of the tenth embodiment, the contract-related information holding unit (BE) (4625), the labor claim information acquisition department (BF) (4626), and the recurring payment date. Information holding unit (AC) (4603), payment method identification information acquisition unit (AD) (4604), time information acquisition unit (AE) (4605), and recurring payment date relationship judgment unit (AF) (4606). In addition to having a recurring payment processing unit (AG) (4607), a processing result acquisition unit (AZ) (4620), an SNS identification information holding unit (BA) (4621), and a processing result notification unit ( BB) (4622).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.) Authority information holding department, worker identification information related department, labor claim information Holding Department, Labor Claim Information Holding Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration Retention Department It may be configured to have a portion. Hereinafter, the processing result acquisition unit (AZ) (4620), the SNS identification information holding unit (BA) (4621), and the processing result notification unit (BB) (4622), which are characteristic configurations of the present embodiment, will be described. ..

<Embodiment 16 Processing Result Acquisition Unit (AZ) (4620)>

The "processing result acquisition unit (AZ)" (4620) processes the payment by the recurring payment processing unit (AG) (4607) or the processing result which is the result of the prepaid processing by the prepaid processing unit (AX). Obtained in association with identification information. Since it is a processing result, it includes at least information that the processing has been completed normally or information that the processing has not been completed normally.

In addition, the amount of prepaid processing, the amount collected as a fee, the date and time of this prepaid processing, information that identifies the person who made the prepaid (user, intermediary, etc.), in the case of fixed date prepaid The next repaid payment date, the amount that can be prepaid by the next wage payment date (the remaining period may be divided into multiple categories and the amount may be presented for each category), the next wage payment date Estimated amount of money that can be prepaid by (the remaining period may be divided into multiple categories and the amount may be presented for each category), past prepaid results, processing identification information of prepaid processing, processing is normal It may include any one or more of the causes when it does not end in. The processing result acquisition unit (AZ) (4620) acquires the processing result immediately after the payment processing (repeated payment processing, prepaid processing). That is, it is preferable that the acquisition of the processing result is performed continuously with the payment processing.

<Embodiment 16 SNS Identification Information Holding Unit (BA) (4621)>

The “SNS identification information holding unit (BA)” (4621) holds the SNS identification information used by the worker in association with the worker identification information. The "SNS identification information" is information that identifies the type of SNS. Examples of SNS types include Facebook (registered trademark), LINE (registered trademark), instagram (registered trademark), WeChat (registered trademark), Twitter (registered trademark), Mixi (registered trademark), YouTube (registered trademark), Nico Nico Video (registered trademark), KakaoTalk (registered trademark), etc. can be mentioned. Basically, it has one or more of member profile introduction function, message sending / receiving function between members, timeline (wall) function by members, member mutual link function, member search function, blog function, questionnaire function, community function, etc. It is a system.

<Embodiment 16 SNS Identification Information Holding Unit (BA) (4621) Other SNS Worker ID>

It is preferable that the "SNS identification information holding unit (BA)" (4621) also holds the SNS worker ID. The "SNS worker ID" refers to information that uniquely identifies a worker on the SNS used by the worker. This information can be used to communicate with the worker and send information on the SNS. Therefore, the fixed date prepayment system (4600) can transmit and notify the worker by using the SNS identification information and the SNS worker ID.

<Embodiment 16 Processing Result Notification Unit (BB) (4622)>

The "processing result notification unit (BB)" (4622) notifies the worker of the processing result via the SNS identified by the worker identification information associated with the processing result and the SNS identification information associated with the processing result. It is configured to do. In particular, when the SNS as a notification means and the electronic money type as a processing means are linked, the viewing of the processing result of the worker and the consumption of the prepaid electronic money by the worker are integrated. It is convenient because it is possible. The processing result notification referred to here is different from the notification from the electronic money system. Therefore, in addition to the notifications such as charge completion, remittance possible, and remittance completion by the electronic money system, the notification by the fixed date prepayment system (4600) is given.

In addition, as a response to the processing result notification, it is more desirable to configure the worker to perform an acknowledge reply such as read or consent to the fixed date prepaid system (4600) by a simple operation such as one push. .. It is desirable to perform this with the link button provided in the processing result notification screen. In addition, it is desirable to configure the prepaid processing result to be automatically forwarded or automatically notified to the employer of the worker based on the knowledge reply. The processing result notification may include not only the processing of the fixed date prepayment system (4600) but also the notification of all external processing related to the prepayment. And this notification may be multiple notifications regarding one payment process. It is preferable that the notification of the processing result is continuously executed when the processing result acquisition unit (AZ) (4620) acquires the processing result. This is because it is a worker's concern.

<Embodiment 16 Hardware>

In the hardware configuration of the fixed date prepaid system of the 16th embodiment, the program according to any one of the 10th to 15th embodiments is executed using the hardware described in the premise part of the description of the embodiment as a resource. Furthermore, in addition to that, with a processing result acquisition program that acquires the processing result that is the result of payment processing by the recurring payment processing department (AG) or prepaid processing by the prepaid processing department (AX) in association with the worker identification information. , The SNS identification information holding program that holds the SNS identification information used by the worker in association with the worker identification information, and the SNS identification information associated with the worker identification information associated with the processing result. It has a processing result notification program for notifying a processing result via SNS. Based on the tenth embodiment, the above hardware configuration is shown in FIG. 48. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions. This execution is preferably carried out continuously and without intervals.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 16 Processing flow>

In addition to the processing flow of any one of the tenth to the fifteenth embodiments, the following processing is performed. Based on the tenth embodiment, as shown in FIG. 47, the processing that is the result of the payment processing in the recurring payment processing step (ag) (S4708) or the prepayment processing in the prepayment processing step (ax). The processing result acquisition step (az) (S4710) for acquiring the result in association with the worker identification information and the SNS identification information retention step (BA) for retaining the SNS identification information used by the worker in association with the worker identification information. (S4704) and the processing result notification step (bb) (S4711) for notifying the processing result via the SNS identified by the worker identification information associated with the processing result and the SNS identification information associated with the processing result. It is an operation method of a fixed date prepayment system which is a computer to have. This processing result notification step (bb) (S4711) may include notifications for all external processing related to prepayment, as well as processing for the fixed date prepayment system. And this notification may be multiple notifications regarding one payment process.

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 16>

As a worker, whether or not the prepaid process is completed successfully is a very important concern that is directly linked to life. Therefore, I want to know the result as soon as possible. The payment process of this fixed date prepayment system is not necessarily the remittance process itself such as fund transfer, remittance to the account, remittance of electronic money, charge to electronic money, but as a worker, it is a pre-stage process. However, since we want to know as soon as possible that the processing has been completed successfully, this embodiment is effective in satisfying the demand.

<Embodiment 17 Mainly relating to claim 35> Remittance by SNS

<Outline of Embodiment 17>

The 17th embodiment is an embodiment based on the 13th to 16th embodiments based on the 12th embodiment. This is because it is premised that the remittance unique information holding unit (AN) is provided and the SNS identification information holding unit (BA) is provided. In the present embodiment, the SNS identification information for remittance is retained in association with the worker identification information.

This is because a worker who has SNS identification information for remittance is inevitably a worker who is identified by the worker identification information associated with the SNS identification information regardless of whether it is for remittance or not.

<Structure 17 of the embodiment>

The configuration of the 17th embodiment is based on the 13th to 16th embodiments based on the 12th embodiment as described above. Therefore, when the configuration is shown by an example in which the embodiment 12 is not based on the embodiment 11, the contract-related information holding unit (BE) (4925), the labor claim information acquisition unit (BF) (4926), and the recurring payment date information are shown. The holding unit (AC) (4903), the payment method identification information acquisition unit (AD) (4904), the time information acquisition unit (AE) (4905), and the recurring payment date relationship determination unit (AF) (4906). , Repeated payment processing unit (AG) (4907), Repeated payment processing history holding unit (AH) (4908), Remittance unique information holding unit (AN) (4912), Processing result acquisition unit (AZ) ( 4920), SNS identification information holding unit (BA) (4921), processing result notification unit (BB) (4922), and the remittance unique information holding unit (AN) (4912) is a remittance SNS. It is configured to have identification information holding means (BC) (4923). When the embodiment 12 is based on the embodiment 11, it further has a payment method identification information holding unit, a payment method selection reception unit (AK), and a payment method payment consideration allocation unit (AM). , The payment method identification information acquisition unit (AD) is configured to acquire the payment method identification information for which the selection has been accepted in association with the worker identification information.

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.) Authority information holding department, worker identification information related department, labor claim information Holding Department, Labor Claim Information Holding Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration Retention Department It may be configured to have a portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 17 Remittance Specific Information Holding Unit / Remittance SNS Identification Information Holding Means (BC) (4912)>

The "remittance SNS identification information holding means (BC)" (4912) is a means provided in the remittance unique information holding unit (AN) (4912), and is configured to hold the remittance SNS identification information. .. This remittance SNS identification information is retained in association with the worker identification information, the payment method identification information, and the remittance unique information. The remittance-specific information may be the same as the remittance SNS identification information. "Remittance SNS identification information" is information used when sending money to a worker or charging an electronic money account used by a worker by a remittance means linked with the SNS. Information used to identify a worker or electronic money account.

The SNS identification information for remittance can be used to find profile introductions of members on SNS, send and receive messages between members, find timelines (walls) by members, and become identification information for the member mutual link function. It is used when finding a blog or becoming a community member, and may or may not be the same as the SNS ID. Further, the remittance SNS ID may be different from the electronic money consumption ID.

<Embodiment 17 Hardware Configuration>

The hardware configuration of the fixed date prepaid system of the 17th embodiment is based on the 12th embodiment of the 13th to 16th embodiments, as shown in FIG. 51, using the hardware described in the premise part of the description of the embodiment as a resource. The described program is executed. Furthermore, in addition to that, the remittance unique information holding program is an SNS identification information holding subprogram that holds the worker identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. Has. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions. This execution is preferably carried out continuously and without intervals. As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 17 Processing flow>
In addition to the processing flow according to the 13th to 16th embodiments based on the 12th embodiment, the following processing is performed. The remittance unique information holding step (an) (S5004) holds the worker identification information, the payment method identification information, the remittance unique information, and further, the SNS identification information is held in association with the SNS identification information. It has an information retention substep (bc) (S5005).

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 17>

Since payment processing and processing result notification to workers can be executed with the same SNS and SNS cooperation function, batch processing is possible with the SNS used by workers, labor for workers' operations can be reduced, and information sharing is unified. This makes it possible to use an efficient fixed-date prepayment system.

<Embodiment 18 Mainly relating to claim 36> Fixed amount repetitive payment

<Outline of Embodiment 18>

In this embodiment, all or part of the payable consideration paid in advance to the worker on a fixed date is treated to be a fixed amount at all times on the recurring payment date. The present embodiment is based on any one of the tenth to the seventeenth embodiments.

<Structure 18 of the embodiment>

The 18th embodiment is based on any one of the 10th to 17th embodiments. For example, when the embodiment 10 is used as a basis, as shown in FIG. 52, the configuration includes a contract-related information holding unit (BE) (5225), a labor claim information acquisition unit (BF) (5226), and the like. Repeated payment date information holding unit (AC) (5203), payment method identification information acquisition unit (AD) (5204), time information acquisition unit (AE) (5205), and repeated payment date relationship judgment unit (AF). ) (5206), a recurring payment processing unit (AG) (5207), a recurring payment processing history holding unit (AH) (5208), and a labor claim information acquisition unit (BF) (5226). Has a fixed amount acquisition means (BD) (5224).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, the worker identification information related department, and the labor claim. Information Retention Department, Labor Claim Information Retention Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration It may be configured to have a holding portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 18 Fixed amount acquisition means (BD) (5224)>

The "fixed amount acquisition means (BD)" (5224) is a means provided in the Labor Claim Information Acquisition Department (BF) (5226), and is the payable consideration paid to the worker acquired in association with the worker identification information. Obtain information indicating a fixed amount in whole or in part. Since it is a "fixed amount", in principle, a fixed amount is paid to the worker each time on the recurring payment date. Fixed amounts that are repeatedly paid include rent, parking fees, and various subscription services.

This acquisition source is a fixed amount holding unit that holds a fixed amount in association with the worker identification information. The fixed amount holding unit may be provided inside the fixed date prepayment system (5200) or may be provided outside. Then, this fixed amount holding unit is configured so that a fixed amount can be set and input from a terminal used by a worker. When there are a plurality of types of recurring payments, it is preferable that a fixed amount can be set individually for each recurring payment date.
This can be realized by setting, inputting, and holding a fixed amount in association with each of the plurality of recurring payment date identification information described above.

<Embodiment 18 Hardware>

The hardware configuration of the fixed date prepaid system of the 18th embodiment is described in any one of the 10th to 17th embodiments as shown in FIG. 54, using the hardware described in the premise part of the description of the embodiment as a resource. Program is executed. In addition to that, the labor receivables information acquisition program has a fixed amount acquisition subprogram. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 18 Processing flow>

In addition to the processing flow according to any one of the tenth to the seventh embodiments, the labor claim information acquisition step (bf) includes a fixed amount acquisition substep (bd).
FIG. 53 shows a flow of processing of the present embodiment based on the first embodiment. The labor claim information acquisition step (bf) (S5302) has a fixed amount acquisition substep (bd) (S5303).

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 18>

The amount paid on the recurring payment date is fixed, which is convenient for workers who regularly spend a fixed amount repeatedly. Also, although it is not a fixed amount, if you can cover the recurring expenses with a certain amount of prepaid, you can register so that the fixed amount will be paid repeatedly with a little margin so that you do not have to enter the desired prepaid amount every time. It's convenient to get rid of it.

<Embodiment 19 Mainly relating to claim 37> Notification when the balance is insufficient

<Outline of Embodiment 19>

In the present embodiment, when the balance of labor receivables is less than the predetermined amount on the recurring payment date and the full amount cannot be paid, the worker or / and the employer are notified. The present embodiment is based on any one of the first to eighteenth embodiments.

<Structure 19 of the embodiment>

The 19th embodiment is based on any one of the 1st to 18th embodiments. For example, when the embodiment 10 is used as a basis, as shown in FIG. 55, the configuration includes a contract-related information holding unit (BE) (5525), a labor claim information acquisition unit (BF) (5526), and the like. Repeated payment date information holding unit (AC) (5503), payment method identification information acquisition unit (AD) (5504), time information acquisition unit (AE) (5505), and repeated payment date relationship judgment unit (AF) ) (5506), a recurring payment processing unit (AG) (5507), a recurring payment processing history holding unit (AH) (5508), and a payment processing approval / disapproval determination unit (BG) (5527). And a payment processing abnormality information notification unit (BH) (5528).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, the worker identification information related department, and the labor claim. Information Retention Department, Labor Claim Information Retention Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration It may be configured to have a holding portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Implementation 19 Payment Processing Acceptability Judgment Department (BG) (5527)>

The "Payment Processing Appropriateness Judgment Department (BG)" (5527) states that all or part of the payable consideration associated with the worker identification information is less than the prescribed amount, and the Repeated Payment Processing Department (AG) (AG) It is configured to determine if the full payment can be processed according to 5507).

<Implementation 19 Payment Processing Abnormal Information Notification Unit (BH) (5528)>

The "payment processing abnormality information notification unit (BH)" (5528) indicates that payment processing cannot be performed when the judgment result of the payment processing availability judgment unit (BG) (5527) is the judgment result that payment processing cannot be performed. It is configured to notify the worker and / and the employer of the payment processing abnormality information indicating.

There are two possible timings for notifying payment processing error information. The first is when the timing of processing for payment on the recurring payment date is reached, and the decision on whether or not to process payment is made in an attempt to actually process payment. The second is when it is determined that the payable consideration is expected to run short on the recurring payment date (prior to the date on which the recurring payment date is processed for payment).
This will be described with reference to FIG. 88. There are two possible methods of recurring payment and voluntary date payment, in which the labor consideration multiplied by the safety factor is used as a source of advance payment, as shown in Fig. 88a and Fig. 88b. When using the labor consideration for one month last month multiplied by the safety factor as a source of prepayment for this month (Fig. 88a), the application date for this month when the prepayment is to be received from the closing date of the attendance of the month before last. There are two types of cases where the labor consideration up to the day multiplied by the safety factor is used as the source of funds (Fig. 88b).

The former will be described with reference to FIG. 88a. In FIG. 88abc, attendance is closed at the end of the month, the wage payment date is set to 24 days, and the set repetitive payment date is set to 20 days. The labor consideration for the month from August 1st, the day after July 31st, the closing date of the previous month, to August 31st, the closing date of last month, multiplied by the safety factor will be used as a source of prepaid funds for September. .. It is assumed that the amount that can be paid in advance is 30 units from the labor consideration in August. It is set to receive 25 prepayments on the 20th of every month. If you try to receive prepayment on any date on September 16th, the prepayable amount of September 30-25 = 5 will be the maximum amount you can receive prepayment on any date on September 16th. If a recurring payment date is set between the wage payment date such as the 25th and the closing date at the end of the month, either deduct it from the prepaid amount in August and secure it before paying the wage on the 24th, or in September. It can be configured to make recurring payments using the labor consideration multiplied by the safety factor as a source of funds.

The latter case will be described with reference to FIG. 88b. The deadline for attendance and the set date for prepayment are the same as in FIG. 88a. If you intend to receive prepayment on any date on September 16th, use the labor consideration obtained by multiplying the labor consideration from the beginning of September to September 15 by the safety rate in addition to the labor consideration in August. , The amount that can be paid in advance is 30 + 15 = 45. It is set to receive 25 prepayments on the 20th of every month. If you try to receive prepayment on any date on September 16th, the prepayable amount 45-25 = 20 will be the maximum amount you can receive prepayment on any date on September 16th.

The timing of notifying the payment processing abnormality information when the prepaid resources are used as shown in FIG. 88a will be described. As shown in Fig. 88c, if a worker is absent due to poor physical condition for 10 days from August 14th to 24th, the total prepaid amount calculated based on the labor consideration in August multiplied by the safety factor is all. Compared to working days, it decreases to 30-10 = 20. There are two possible timings for notifying the payment processing abnormality information, which are indicated by the crosses in FIG. 88c. × 2 detects and notifies the shortage at the timing of processing for payment for recurring payment. It is a notification just before the day before payment, and it tends to be difficult for workers to make money for rent and utility bill payments. It may be possible to contact the relevant parties for consultation if payment is hindered. The timing of × 1 is to notify when it is expected that the recurring payment in September will be insufficient as it is in the middle of absenteeism. When obtaining labor claim information from an attendance management server, etc., in this case, if the same work is done for the remaining days in August from the attendance information before absenteeism, the amount that can be paid in advance is insufficient for recurring payments. We will notify you when we know that we will do it (around August 19th). It is more preferable to present a countermeasure plan at the same time as issuing a notification. The notification timing of × 1 is not limited to the above example. If you are notified that absenteeism will result in a shortage of recurring payments scheduled for September in the days following when you are absent from work, in the above case, it was found that you will be short of work due to absenteeism. If you notify after a predetermined period and before the August closing date, or if you notify when it is found that you cannot recover the shortage even if you work overtime or take a leave before the August closing date, the August closing date or immediately before There may be various cases, such as when the deadline for August has passed and the labor consideration for August has been finalized, and after a predetermined period of time has passed. It is preferable for workers to be notified at an early stage so that they can recover from overtime work or leave before the closing date in August.

The contents of the presentation include the estimated shortage amount (or / and the estimated amount that can be paid on the recurring payment date) at the time of notification, overtime work until the closing date in August, and work on holidays (including how many hours and days are required). Proposals and so on. If the shortfall is known and how much can be obtained if even a part of the payment is possible, the worker will have time to negotiate with the person who will pay the amount obtained by repeated payment and take measures. Is. If you receive a proposal for overtime work or work on holidays, you can think of recovery by working until the deadline. However, regarding overtime work and holiday commuting, it may be necessary for the employer to consider the safety and health of workers (upper limit of overtime hours, continuous work). Therefore, it is necessary to notify the user of the payment processing abnormality information notification. After the deadline, it is preferable to issue a notification regardless of whether there is a shortage or not, based on the information that was confirmed again when the labor claim information was confirmed. This is because if it is determined that there will be a shortage, the exact amount of the shortfall will be known, and if it is found that there is not enough shortage, it will be a relief.
In addition to the closing date, the function to monitor the transition of the labor claim information of workers at any time even in the middle of the month and estimate the accumulation of labor claim information until the next closing date based on the transition, and the set repetition A separate labor claim information monitoring department may be provided, which has a function of determining whether or not the already accumulated labor claim information or the estimated labor claim information for the current month is insufficient for payment. Alternatively, the labor receivable information acquisition department and the payment processing approval / disapproval judgment department may be provided with distributed functions.

As shown in FIG. 88b, the timing of notifying the payment processing abnormality information when the labor receivables of the current month are used as the calculation source of the prepaid amount in addition to the labor receivables for one month last month is the same.
However, unlike the above example, it is necessary to make a forecast not only one month ahead but also two months ahead so that there will be no shortage of recurring payments in October of the following month. In addition to the September 24 recurring payment in Figure 88b, the October 24 recurring payment must also be considered.

<Embodiment 19 Hardware>

The hardware configuration of the fixed date prepaid system of the nineteenth embodiment is described in any one of the first to eighteenth embodiments as shown in FIG. 57, using the hardware described in the premise part of the description of the embodiment as a resource. Program is executed. Furthermore, in addition to that, it has a payment processing admissibility determination program and a payment processing abnormality information notification program. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 19 Processing flow>

In addition to the processing flow according to any one of the first to eighteenth embodiments, the payment processing admissibility determination step (bg) and the payment processing abnormality information notification step (bh) are included.
FIG. 56 shows a flow of processing of the present embodiment based on the first embodiment. It has a payment processing admissibility determination step (bg) (S5607) and a payment processing abnormality information notification step (bh) (S5608). As mentioned above, if it is found that the payment amount is insufficient on the recurring payment date, it can be configured not to execute the processing for payment unless the set amount is full, but even if it is insufficient. After receiving input from the worker whether or not to partially process the payment in the payment processing approval / disapproval step (bg) (S5607), the amount can be paid in the repetitive payment processing step (ag) (S5609). It can also be configured to be reduced and processed for payment.

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 19>

Amount to be paid on the recurring payment date When the balance of labor receivables is less than the planned amount and the full amount cannot be processed, the worker or / and the employer will be notified that the payment will be made. For the expected worker, it is convenient to be able to quickly know that the payment will not be processed. In addition, the employer can quickly know that the payment to the worker was not made due to the insufficient balance of the labor claim, so that the worker's financial situation can be quickly known. Since it can cause a decrease in work efficiency, a deterioration in the health condition of workers, and a decrease in work morals, it is also useful for quickly grasping and providing medical treatment such as interviews as necessary.

<Embodiment 20 Mainly relating to claim 38> Securing an amount for a fixed amount payment date

<Outline of Embodiment 20>

In the present embodiment, when a worker applies for input of a prepayment request amount to a fixed day prepayment system at an arbitrary amount, the prepayment request amount is reduced in order to secure the amount for the fixed amount payment date. The present embodiment is based on the 18th embodiment based on the 15th embodiment.

<Structure 20 of Embodiment>

The 20th embodiment is based on the 18th embodiment based on the 15th embodiment. For example, when the embodiment 18 is used as a basis, as shown in FIG. 58, the configuration includes a contract-related information holding unit (BE) (5825), a labor claim information acquisition unit (BF) (5826), and the like. Repeated payment date information holding unit (AC) (5803), payment method identification information acquisition unit (AD) (5804), time information acquisition unit (AE) (5805), and repeated payment date relationship judgment unit (AF). ) (5806), the recurring payment processing unit (AG) (5807), the recurring payment processing history holding unit (AH) (5808), the start processing request acquisition unit (AS) (5815), and the prepaid amount. It has an acquisition unit (AT) (5816), a prepayment request amount acquisition unit (AW) (5817), a prepayment processing unit (AX) (5818), and a prepayment history holding unit (AY) (5819). Further, the prepayment request amount acquisition unit (AW) (5817) has a fixed amount payment possibility determination means (BJ) (5829) and a prepayment request amount acquisition means (BK) (5830).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.) Authority information holding department, worker identification information related department, labor claim information Holding Department, Labor Claim Information Holding Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration Retention Department It may be configured to have a portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 20 Fixed amount payment availability determination means (BJ) (5829)>

The "fixed amount payment approval / disapproval determination means (BJ)" (5829) communicates with the user on the assumption that the prepaid request amount acquired by the prepaid request amount acquisition unit (AW) (5817) has been paid. It is configured within the Prepaid Request Amount Acquisition Department (AW) (5817) to determine if the fixed amount already set to be paid on the repeat payment date cannot be paid on the nearest repeat payment date. ..

<Embodiment 20 Prepaid Request Amount Acquisition Means (BK) (5830)>

The "prepaid request amount acquisition means (BK)" (5830) determines the total amount of payment to the worker when the judgment result of the fixed amount payment approval / disapproval judgment department (BJ) is the judgment result that the payment cannot be made. , The prepaid request amount acquisition unit (AW) (5817) is configured so that the prepaid request amount is reduced to the amount that can be paid the fixed amount.

<Embodiment 20 Hardware>

The hardware configuration of the fixed date prepaid system of the 20th embodiment is described in the 18th embodiment based on the 15th embodiment as shown in FIG. 60 using the hardware described in the premise part of the description of the embodiment as a resource. The program is executed. Furthermore, in addition to that, the prepaid request amount acquisition program has a fixed amount payability judgment subprogram and a prepaid request amount acquisition subprogram. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 20 Processing flow>

The processing flow of the 20th embodiment further includes a fixed amount payment admissibility determination substep (bj) and a prepaid request amount acquisition substep (bk). In addition to, or partially or entirely, in addition to the flow of processing according to embodiment 18 based on embodiment 15, the following processing is performed. As shown in FIG. 59, the processing flow of the embodiment 18 based on the embodiment 15 is on the left side, and the processing flow peculiar to the present embodiment is on the right side. To explain the processing flow on the right side,
In the start processing request acquisition step (as) (S5910), the process of acquiring the start processing request of the wage prepaid request is performed in association with the worker identification information, and if it is not acquired, the labor claim information acquisition of the processing flow on the left side is acquired. If you go back to step (bf) (S5902) and get it,
In the time information acquisition step (ae) (S5911), the process of acquiring the time information including the date when the start processing request is acquired is performed.
In the prepayable amount acquisition step (at) (S5912), the labor receivable information associated with the worker identification information, the recurring payment date information associated with the worker identification information, and the repeat payment associated with the worker identification information. Process to obtain the prepayable amount, which is the amount that allows the prepayment request based on all or part of the payable consideration paid on the return payment date.
In the prepayment request amount acquisition step (aw) (S5913), the prepayment request amount is acquired by associating it with the worker identification information within the range not exceeding the prepayment possible amount.
In the fixed amount payment availability substep (bj) (S5914) in the prepayment request amount acquisition step (aw), it is assumed that the prepayment request amount acquired in the prepayment request amount acquisition step (aw) (S5913) is processed. In the case of the case where it is judged that the fixed amount that has already been set to be paid on the repeat payment date cannot be paid on the closest repeat payment date set with the user, and the payment cannot be made. teeth,
In the prepaid request amount acquisition substep (bk) (S5915), the total amount paid to the worker is reduced to the amount that can be paid the fixed amount to obtain the prepaid request amount.
In the prepaid processing step (ax) (S5916), a process for performing prepaid processing, which is a process for prepaid the acquired prepaid request amount, is performed.
In the prepayment history holding step (ay) (S5917), the prepayment history, which is the history of the prepayment processing in the prepayment processing step (ax) (S5916), is held in association with the worker identification information.
If it is determined that payment can be made in the fixed amount payment approval / disapproval substep (bj) (S5914), the prepaid request amount acquisition substep (bk) (S5915) is skipped and the processing is performed in the prepaid processing step (ax) ( Performs the process to proceed to S5916).
It is an operation method of a fixed date prepaid system which is a computer as described above.

These processing steps are separate processes from the fixed date prepayment processing of Embodiments 10 to 14, and when the relationship between the time information and the recurring payment date is other than the predetermined relationship in the fixed date prepayment processing. A branch for determining whether or not to make a prepaid date on an arbitrary date can be inserted in, and a process specific to the present embodiment can be executed when it is determined that a prepaid process on an arbitrary date should be performed. In addition, whether or not to execute the prepayment on an arbitrary date is first triggered by the acquisition of the start processing request by the worker.

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 20>

In the configuration of the 20th embodiment, by paying an arbitrary amount in advance on an arbitrary date, it is possible to prevent the worker from being unable to pay the fixed amount on the repeated date previously agreed with the employer. For example, since the application was made in advance to cover the cost of eating and drinking with a friend in the middle of the month, it is possible to prevent the shortage of money for rent and utility bill payment at the end of the month.

<Embodiment 21 Mainly relating to claim 39> Wage payment agency

<Outline of Embodiment 21>

In this embodiment, the prescribed wage is all or part of the payable consideration excluding the amount of repaid or / and prepaid from the wage that would have been paid if there was no repaid or prepaid. It is configured to process for payment so that it can be paid on the payment date. This embodiment is based on any one of embodiments 10 to 20.

<Structure 21 of the embodiment>

The 21st embodiment is based on any one of the 10th to 20th embodiments. For example, when the embodiment 10 is used as a basis, as shown in FIG. 61, the configuration includes a contract-related information holding unit (BE) (6125), a labor claim information acquisition unit (BF) (6126), and the like. Repeated payment date information holding unit (AC) (6103), payment method identification information acquisition unit (AD) (6104), time information acquisition unit (AE) (6105), and repeated payment date relationship judgment unit (AF). ) (6106), a recurring payment processing unit (AG) (6107), a recurring payment processing history holding unit (AH) (6108), and a wage payment date information holding unit (BM) (6131). ) And the balance payment processing unit (BN) (6132).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, the worker identification information related department, and the labor claim. Information Retention Department, Labor Claim Information Retention Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration It may be configured to have a holding portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 21 Wage Payment Date Information Holding Department (BM) (6131)>

The "Wage Payment Date Information Retention Department (BM)" (6131) is configured to retain wage payment date information, which is information indicating a predetermined wage payment date in association with worker identification information and / and employer identification information. Will be done.

<Embodiment 21 Balance Payment Processing Department (BN) (6132)>

The "Balance Payment Processing Department (BN)" (6132) has set aside the prescribed wage payment date held with the employer based on the worker's labor claim information, and has occurred by the prescribed closing date. Payable consideration excluding the amount paid in return payment and / and the prepaid request amount processed in advance from the wages that would have been paid in the absence of these recurring payments and prepayments. It is configured to perform a balance payment process, which is a process for payment, so that all or part of the consideration is payable. It proceeds with the processing for payment so that all or part of the payable consideration can be paid on the wage payment date.

The 21st embodiment is a configuration in which the user who uses the fixed date prepayment system outsources the calculation and payment of wages to a contractor who outsources the prepayment processing. Especially in small companies, it is useful because it can reduce the burden of maintaining personnel and labor management involved in payment calculation and payment processing to wages and related contractors. For the workers who use it, it is possible to edit the wage payment date information described later in the same way as the system of repeat payment and prepayment on any date, and in the form of prepayment and wages with one system. It is convenient because you can receive payment for the labor claims of.

<Embodiment 21 Hardware>

In the hardware configuration of the fixed date prepaid system of the 21st embodiment, the program according to any one of the 10th to 20th embodiments is executed using the hardware described in the premise part of the description of the embodiment as a resource. FIG. 63 shows a case based on the tenth embodiment. In addition to the program described in the tenth embodiment, the program includes a wage payment date information holding program and a balance payment processing program. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 21 Processing flow>

In addition to the processing flow according to any one of embodiments 10 to 20, the wage payment date information holding step (bm) and the balance payment processing step (bn) are included.
FIG. 62 shows a flow of processing of the present embodiment based on the tenth embodiment. It has a wage payment date information retention step (bm) (S6204) and a balance payment processing step (bn) (S6206).

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 21>

It is efficient because the wage calculation and payment operations can be unified by performing normal wage payment in the same processing as the processing form in which recurring payment or prepayment is performed. In particular, when recurring payments and prepayments are outsourced to a payment agent other than the employer, the employer can save labor because he / she can collectively handle all administrative duties for payments to workers, including wages. Can be achieved.

<Implementation 22 Mainly relating to claim 40> Wage payment agency, payment fee paid by the user

<Outline of Embodiment 22>

In the present embodiment, when the balance payment processing unit (BN) that performs the balance payment processing requires a fee for the remittance means used as the payment method when the balance payment process is performed, the user bears the fee. It is configured to have a user-paid check processing unit that performs slip processing for the purpose (both electronic slips and slips made of actual sheets may be included. The same shall apply hereinafter). This embodiment is based on the 21st embodiment.

<Structure of Embodiment 22>

The configuration of the 22nd embodiment is based on the 21st embodiment. As shown in FIG. 64, the configurations are a contract-related information holding unit (BE) (6425), a labor claim information acquisition unit (BF) (6426), and a recurring payment date information holding unit (AC) (6403). The payment method identification information acquisition unit (AD) (6404), the time information acquisition unit (AE) (6405), the recurring payment date relationship judgment unit (AF) (6406), and the recurring payment processing unit (AG). ) (6407), a recurring payment processing history holding unit (AH) (6408), a wage payment date information holding unit (BM) (6431), and a balance payment processing unit (BN) (6432). Further, it has a user-paid slip processing unit (CE) (6445).

As described in the description of the twenty-first embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer is fixed by his / her own authority information). Once the date prepayment system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding department, worker identification information related department, labor Receivable information holding department, labor receivable information holding department renewal department, authority information notification department, authority information recording department, fixed date prepayment desired amount input department, fixed date prepayment desired amount testing department, repeatable payment range judgment department, payable pair It may be configured to have a value holding unit. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 22 User-paid slip processing unit (CE) (6445)>

The "user-paid slip processing unit (CE)" (6445) required a fee for the remittance method used as the payment method when the balance payment processing unit (BN) that performs the balance payment processing performs the balance payment processing. In this case, the user is configured to perform voucher processing (which may include both an electronic voucher and a voucher made of an actual sheet; the same shall apply hereinafter) for the user to bear the fee.

<Embodiment 22 Hardware>

As for the hardware configuration of the fixed date prepaid system of the 22nd embodiment, the program described in the 21st embodiment is executed as shown in FIG. 66 using the hardware described in the premise part of the description of the embodiment as a resource. Further, in addition to that, it has a user-paid slip processing program. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the description of the twenty-first embodiment, the worker authentication program, the employer authentication program, the authority information holding program, the remaining amount range judgment program, and the authority information registration program (the employer is fixed by his / her own authority information). Once the date prepayment system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor Receivable information retention program, labor receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repetitive payable range judgment program, payable pair It may be configured to have a value retention program.

<Example 22 Processing flow>

The processing flow of the 22nd embodiment will be described with reference to FIG. 65. In addition to the processing flow described in the 21st embodiment, after the balance payment processing step (bn) (S6506), it is determined whether a remittance fee is required for the balance payment processing, and if a fee is required, a user-paid slip. In the processing step (ce) (S6507), the user performs a processing for processing the slip (which may include both an electronic slip and a slip made of an actual sheet) for the user to bear the fee, and the fee is charged. If is not required, the process of skipping is performed before the repeat payment date relationship judgment step (af) (S6508).

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 22>

When paying the remaining amount of labor receivables after repaying or prepaid as wages, the employer bears the fee required for the remittance means, so that the worker can obtain the wage that should be received without paying the fee. ..

<Embodiment 23 Mainly relating to claim 41> Wage payment agency, payment fee paid by financial institution

<Outline of Embodiment 23>

In the present embodiment, when the balance payment processing unit (BN) that performs the balance payment processing requires a fee for the remittance means used as the payment method when processing the balance, the remittance company bears the fee. It is configured to have a remittance operator-paid check processing unit (CF) for processing slips (which may include both electronic slips and slips made of actual sheets; the same shall apply hereinafter). This embodiment is based on embodiment 21 or 22. However, in the case of the 22nd embodiment, the remittance fee is borne by both the user and the remittance business operator.

<Structure of Embodiment 23>

The configuration of the 23rd embodiment is based on the 21st embodiment. As shown in FIG. 67, the configurations are a contract-related information holding unit (BE) (6725), a labor claim information acquisition unit (BF) (6726), and a recurring payment date information holding unit (AC) (6703). The payment method identification information acquisition unit (AD) (6704), the time information acquisition unit (AE) (6705), the recurring payment date relationship judgment unit (AF) (6706), and the recurring payment processing unit (AG). ) (6707), a recurring payment processing history holding unit (AH) (6708), a wage payment date information holding unit (BM) (6731), and a balance payment processing unit (BN) (6732). In addition, it has a remittance operator-paid slip processing unit (CF) (6746).

As described in the description of the 21st or 22nd embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has his / her own authority information). Once the fixed date prepayment system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), The authority information holding department, and the worker identification information related department. , Labor Claim Information Holding Department, Labor Claim Information Holding Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payment Range Judgment Department, Payment It may be configured to have a possible consideration holding unit. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 23 Remittance Business Operator Burden Slip Processing Department (CF) (6746)>

The "remittance operator-paid slip processing unit (CF)" (6746) requires a fee for the remittance method used as the payment method when the balance payment processing unit (BN) that processes the balance payment processes the balance. In such a case, the remittance company is configured to process the voucher for paying the fee (both an electronic voucher and a voucher made of an actual sheet may be included. The same shall apply hereinafter).
When an employer and a worker conclude an employment contract and first decide on a financial institution to use for paying wages, for example, when the employer first presents a candidate for a financial institution and the candidate is inconvenient for the worker. , The financial institution desired by the worker is selected. Workers are more likely to make a choice if they are candidates for a financial institution when first presented by the employer. In addition to paying wages, it is more likely that the financial institution used to pay wages will be used, and it is expected that the overall transaction volume will increase for financial institutions. If an employer who has a contractual relationship with a large number of workers chooses it, sales are expected to exceed the wage payment fee, which is also beneficial for financial institutions. The user and the remittance business operator may share the fee at a predetermined ratio. In that case, in addition to the remittance operator-paid slip processing unit (CF) (6746), the user-paid slip processing unit (CE) described in the 22nd embodiment is also provided. The predetermined ratio is a fixed ratio, a fixed amount, or a remittance amount that has been agreed in advance between the user and the remittance business operator or through a wage prepayment agency that operates a fixed date prepayment system. It refers to the fee sharing ratio according to the ratio. It may be arranged that both parties share the remittance amount above or below the predetermined remittance amount, or only within the range of a specific amount, and one side shares the other amount.

<Embodiment 23 Hardware>

As for the hardware configuration of the fixed date prepaid system of the 23rd embodiment, the program described in the 21st embodiment is executed as shown in FIG. 69 using the hardware described in the premise part of the description of the embodiment as a resource. In addition to that, it also has a remittance operator-paid slip processing program. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.
When the user and the remittance business operator share the remittance fee at a predetermined ratio, they also have a user-paid slip processing program.

As described in the description of the twenty-first embodiment, the worker authentication program, the employer authentication program, the authority information holding program, the remaining amount range judgment program, and the authority information registration program (the employer is fixed by his / her own authority information). Once the date prepayment system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor Receivable information retention program, labor receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repetitive payable range judgment program, payable pair It may be configured to have a value retention program.

<Process 23 Flow of processing>

The processing flow of the 23rd embodiment will be described with reference to FIG. 68. In addition to the processing flow described in the 21st embodiment, after the balance payment processing step (bn) (S6806), it is determined whether a remittance fee is required for the balance payment processing, and if a fee is required, the remittance company bears the fee. In the slip processing step (ce) (S6807), the user performs slip processing (both an electronic slip and a slip made of an actual sheet. The same shall apply hereinafter) for the user to bear the fee. If no fee is required, the process is skipped before the repeat payment date relationship judgment step (af) (S6808).
As described above, when the user and the remittance company share the remittance fee at a predetermined ratio, after determining whether the fee was required for balance processing, the remittance company's check processing step (ce) (S6807) In addition, the processing is also configured to be divided into the user-paid slip processing step (ce). A side-by-side distribution step may be provided.

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 23>

When paying the remaining amount of labor receivables after repaying or prepaid as wages, the relevant financial institution bears the fee required for the means of remittance, so that the worker can obtain the wage that he or she should receive without paying the fee. In addition to being able to do this, the user does not have to pay a fee. Although the burden of fees will increase for financial institutions, it is expected that there will be more opportunities to use financial institutions because employers and workers have accounts for paying wages at the financial institutions, and the number of cases handled will increase. It can be expected that the profit from the commission will increase.

<Embodiment 24 Mainly relating to claim 42> Repeated payment date editing authority

<Outline of Embodiment 24>

In this embodiment, processing is performed so as to limit the persons who can perform editing including registration and deletion of recurring payment date information and / and worker identification information. This embodiment is based on the thirteenth embodiment.

<Structure of Embodiment 24>

The 24th embodiment is based on the 13th embodiment. For example, when the embodiment 13 is used as a basis, as shown in FIG. 70, the configuration includes a contract-related information holding unit (BE) (7025), a labor claim information acquisition unit (BF) (7026), and the like. Repeated payment date information holding unit (AC) (7003), payment method identification information acquisition unit (AD) (7004), time information acquisition unit (AE) (7005), and repeated payment date relationship judgment unit (AF) ) (7006), a recurring payment processing unit (AG) (7007), a recurring payment processing history holding unit (AH) (7008), and a recurring payment date information editing unit (AP) (7013). In addition, the editing authority identification information holding unit (CC) (7043), the contract-related information holding unit (BE) (7025), the editing authority addition holding means (BP) (7033), and the recurring payment date information editing department (AP) (7013) has editing authority limiting means (BR) (7034).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, the worker identification information related department, and the labor claim. Information Retention Department, Labor Claim Information Retention Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration It may be configured to have a holding portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 24 Editing Authority Identification Information Holding Unit (CC) (7043)>

The "Editing Authority Identification Information Holding Unit (CC)" (7043) is configured to retain editing authority identification information that identifies the editing authority, which is the authority to edit the recurring payment date information and / and the worker identification information. NS.
Editing authority is information that targets editing such as changing, adding, or deleting part or all of the target information, registering new information, or deleting registered information. The right to do to. The information for identifying those editing authority is the editing authority identification information.

<Embodiment 24 Editing authority additional holding means (BP) (7033)>

The "editing authority additional holding means (BP)" (7033) holds the contract-related information holding unit (BE) so as to hold the worker identification information and / and the employer identification information to be held in association with the editing authority identification information. It is configured in (7025).

<Embodiment 24 Editing authority limiting means (BR) (7034)>

"Editing authority limiting means (BR)" (7034) is a person (7034) who identifies the retained recurring payment date information and / and the worker identification information by the identification information associated with the editing authority identification information ( It is configured within the Repeated Payment Date Information Editing Department (AP) (7013) to limit editing, including registration and deletion, only to employers and / and workers).
It is a function to limit the editing authority so that the recurring payment date information and / and the worker identification information, which are important information for the worker, are not edited without the permission of the worker himself / herself. Other than the person himself / herself, on behalf of the employer or employer, related to the worker (personnel-related department such as the worker's address or department to which the company belongs, department related to wage calculation, welfare, etc. Editing authority can be restricted to members of departments, etc.). Even within the department, it is preferable to limit the editing authority to as few people as possible from the viewpoint of personal information protection and security.
By giving the worker the authority to edit the recurring payment date, even the worker for the same employer can flexibly set the recurring payment date, and at the same time, the complicated accounting process can be made smarter. The benefits to workers will increase.

<Embodiment 24 Hardware>

As for the hardware configuration of the fixed date prepaid system of the 24th embodiment, the program described in the 13th embodiment is executed as shown in FIG. 72 using the hardware described in the premise part of the description of the embodiment as a resource. Furthermore, in addition to that, it has an editing authority identification information holding program that performs a process of retaining the editing authority identification information that identifies the editing authority that is the authority to edit the recurring payment date information and / and the worker identification information, and has a contractual relationship. The information retention program has an editing authority additional retention subprogram that retains the retained worker identification information and / and the employer identification information in association with the editing authority described later, and the recurring payment date information editing program is retained. The recurring payment date information and / and the worker identification information can be edited including registration and deletion only by the person (employer or / and worker) identified by the identification information associated with the editing authority. It has an editing authority restriction subprogram that sets restrictions on. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 24 Processing flow>

In addition to the processing flow described in the thirteenth embodiment, the editing authority identification information holding step (cc) and the contract-related information holding step (be) have an editing authority addition holding substep (bp), and the return payment date information. The editing step has an editing authority restriction substep (br).
FIG. 71 shows a flow of processing of the present embodiment based on the thirteenth embodiment. It has an editing authority identification information holding step (cc) (S7101), an editing authority addition holding substep (bp) (S7103), and an editing authority restriction substep (br) (S7115).

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 24>

Repeated payment date information and worker identification information are important personal information for workers who have labor claims and receive payments, so they should not be edited, including registration or deletion, by other workers. Can be restricted. Other than the person himself / herself, it is possible to limit the number of personnel in departments related to work management and wage payment, and to the employer.

<Embodiment 25 Mainly relating to claim 43> Wage payment date information editing authority

<Outline of Embodiment 25>

In the present embodiment, the wage payment date information is such that only the person identified by the identification information held in association with the editing authority, which is the authority to edit including the registration and deletion of the wage payment date information, is allowed to edit. Processed by the editorial department (BS). This embodiment is based on the 21st embodiment.

<Structure 25 of Embodiment>

The 25th embodiment is based on the 21st embodiment. For example, when the embodiment 21 is used as a basis, as shown in FIG. 73, the configuration includes a contract-related information holding unit (BE) (7325), a labor claim information acquisition unit (BF) (7326), and the like. Repeated payment date information holding unit (AC) (7303), payment method identification information acquisition unit (AD) (7304), time information acquisition unit (AE) (7305), and repeated payment date relationship judgment unit (AF). ) (7306), the recurring payment processing unit (AG) (7307), the recurring payment processing history holding unit (AH) (7308), the wage payment date information holding unit (BM) (7331), and the balance payment. It has a processing unit (BN) (7332), and further has an editing authority identification information holding unit (CC) (7343), and an editing authority addition holding means (BP) is added to the contract-related information holding unit (BE) (7325). It has (7333) and has a wage payment date information editorial department (BS) (7335).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, the worker identification information related department, and the labor claim. Information Retention Department, Labor Claim Information Retention Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration It may be configured to have a holding portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 25 Editing Authority Identification Information Holding Unit (CC) (7343)>

The "Editing Authority Identification Information Retention Department (CC)" (7343) is configured to retain editing authority identification information that identifies editing authority, which is the authority to edit wage payment date information and / and worker identification information. ..
In the 25th embodiment, the editing authority identification information for identifying the editing authority, which is the authority to edit the wage payment date information, is also retained with respect to the editing authority identification information holding unit (CC) of the 24th embodiment.
Editing authority is information that targets editing such as changing, adding, or deleting part or all of the target information, registering new information, or deleting registered information. The right to do to. The information for identifying those editing authority is the editing authority identification information.

<Embodiment 25 Editing authority additional holding means (BP) (7333)>

The "editing authority additional holding means (BP)" (7333) holds the contract-related information holding unit (BE) so as to hold the worker identification information and / and the employer identification information to be held in association with the editing authority identification information. It is configured in (7325).

<Embodiment 25 Wage Payment Date Information Editing Department (BS) (7335)>

The "wage payment date information editorial department (BS)" (7335) identifies the wage payment date information held by the wage payment date information holding unit (BM) (7331) in association with the editing authority identification information. It is configured to allow editing, including registration and deletion, only to those identified by the information (employers and / and workers).
By giving workers the authority to edit wage payment dates, even workers for the same employer can flexibly set wage payment dates, while making complicated accounting processing smarter, so from employer to worker. The thickness of welfare benefits will increase. Even if the same user is transferred to a different business and the wage payment date is different for each business, the wage payment date of the new workplace can be easily edited by the user, so complicated labor management can be avoided. If the standard wage payment date is transferred to a different business, the wage payment date of the business before the transfer can be used as described above. If various payments such as rent were adjusted according to the wage payment date before the transfer, the wage payment date can be adjusted so that it does not change before and after the transfer, which is useful for workers because it saves the trouble of various adjustments. be.
In addition, if the branch number of the worker identification information is different for each business establishment, it is possible to easily determine which business the worker belongs to by editing the worker identification information, and the management burden on the employer. Is reduced. The authority can be divided by the branch number of the corresponding business establishment, such as the personnel and labor department in charge.

<Embodiment 25 Hardware>

As for the hardware configuration of the fixed date prepaid system of the 25th embodiment, the program described in the 21st embodiment is executed as shown in FIG. 75 using the hardware described in the premise part of the description of the embodiment as a resource. In addition to that, the contract-related information holding program has an editing authority identification information holding program that holds the editing authority identification information that identifies the editing authority that is the authority to edit the wage payment date information and / and the worker identification information. It has an editing authority additional retention subprogram that retains the worker identification information and / and the employer identification information to be retained in association with the editing authority identification information.
Wage payment date information retention The wage payment date information held in the program includes registration and deletion only for the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. Has a wage payment date information editing program that allows editing. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 25 Processing flow>

In addition to the processing flow described in the 21st embodiment, it has a wage payment date information editing step (bs).
FIG. 74 shows a flow of processing of the present embodiment based on the 21st embodiment. It also has a wage payment date information editing step (bs) (S7408).

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

<Effect of Embodiment 25>

It is an embodiment related to the editing authority for changing the wage payment date agreed between the employer and the worker. For example, the worker pays twice at the middle of the month and the end of the month instead of the general one payment at the end of the month. With the consent of the worker, the payment on the 25th of every month can be changed to the payment at the end of the month for the convenience of the employer.

<Embodiment 26 Mainly relating to claim 44> Date reservation and securing amount

<Outline of Embodiment 26>

In this embodiment, a fixed date prepayment system is used to secure a required amount so that a worker can make a reservation so that the prepayment process can be performed on an arbitrary date and the prepayment process can be performed on the reserved date. It is a system that can be done.

<Structure 26 of the embodiment>

The fixed date prepayment system of the 26th embodiment is based on the fixed date prepayment system of any one of the 15th to 25th embodiments, and the prepayment process is performed on an arbitrary date by using the fixed date prepayment system. The requested amount can be secured so that the worker can make a reservation and perform the prepaid processing on the reservation date. As shown in FIG. 76, in the functional block based on the 15th embodiment based on the 10th embodiment, the contract-related information holding unit (BE) (7625) and the labor claim information acquisition unit (BF) (7626) , Repeated payment date information holding unit (AC) (7603), payment method identification information acquisition unit (AD) (7604), time information acquisition unit (AE) (7605), and repeated payment date relation judgment unit ( AF) (7606), recurring payment processing unit (AG) (7607), repetitive payment processing history holding unit (AH) (7608), start processing request acquisition unit (AS) (7615), prepaid Amount acquisition unit (AT) (7616), prepayment request amount acquisition unit (AW) (7617), prepayment processing unit (AX) (7618), prepayment history holding unit (AY) (7619), and start processing request. In addition to having a time information acquisition unit (CD) (7464), as a characteristic configuration of this embodiment, information indicating the execution date of withdrawal processing, which is processing of withdrawal of money or the like by advance payment from the user. The withdrawal processing execution reservation date information acquisition unit (BT) (7636) and the prepaid processing unit (AX) (7618) that acquire the withdrawal processing execution reservation date information are the acquired withdrawal processing execution reservation date information. , The withdrawal process is executed on the date specified by the withdrawal process execution reservation date information based on the time information acquired by the time information acquisition unit (AE) (7605). A fixed date prepayment system (7600) having withdrawal execution processing means (BW) (7637) for processing.

In addition, in order to realize the functions described in the 13th and 14th embodiments, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer is If the fixed date prepayment system is certified with its own authority information, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, and the worker identification. Information-related department, labor claim information holding department, labor claim information holding department updating department, authority information notification department, authority information recording department, fixed date prepayment desired amount input department, fixed date prepayment desired amount testing department, repeatable payment range It may be configured to have a judgment unit and a payable consideration holding unit.

The configurations described in the 15th to 25th embodiments will be omitted, and only the configurations specific to the present embodiment will be described below.

<Explanation of Embodiment 26 Configuration>

<Embodiment 26 Withdrawal processing execution reservation date information acquisition unit (BT (7636)>

The "withdrawal processing execution reservation date information acquisition department (BT)" (7636) is information indicating the execution date of the withdrawal processing, which is the processing of withdrawal of money, etc. by advance payment from the worker who is the user. It is configured to acquire execution reservation date information. In the 26th embodiment, a future date prior to the date on which the prepayment request is applied is input as the execution date of the withdrawal process.

The amount obtained by multiplying the total amount of the labor receivables balance at the time of acquisition of the withdrawal processing execution reservation date information and the amount of labor receivables added by the withdrawal processing execution reservation date by the safety factor is less than the same amount as the prepaid request amount. In such a case, a means for presenting the prepaid amount that can be reserved is given to the worker, or the amount calculated by multiplying the safety factor is presented to the worker as the reservable prepaid amount. It is preferable to have more.

<Embodiment 26 Withdrawal Execution Processing Means (BW) (7637)>

The "withdrawal execution processing means (BW)" (7637) performs the withdrawal processing based on the acquired withdrawal processing execution reservation date information and the time information acquired by the time information acquisition unit (AE) (7605). It is configured in the prepaid processing unit (AX) (7618) so that the withdrawal processing is executed on the date specified by the withdrawal processing execution reservation date information.
If a worker makes a reservation for a prepayment request and it is determined at the time of application for the request that the amount considering the safety factor can be paid on the wage payment date even if the withdrawal reservation is executed, the withdrawal processing scheduled date It is very likely that a prepayment request on an arbitrary date, which is the withdrawal date before, or a withdrawal processing reservation application will be made, so that the amount of the withdrawal processing reservation reserved earlier will be secured. For example, on the 2nd of a month, a reservation application is accepted so that the withdrawal process will be performed on the 15th, and on the 10th, an application for withdrawal processing will be performed on the 10th as a prepayment application on an arbitrary date. If you do, if the 10th sunrise payment process interferes with the 15th sunrise payment reservation and wage payment, you can either reduce the prepaid amount in response to the 10-day prepaid request or present it, or if the labor claim balance is insufficient, prepaid. Processing is performed to prevent reception.

<Embodiment 26 Hardware>

The hardware of the fixed date prepayment system of the 26th embodiment is based on the hardware described in the premise of the description of the embodiment, and further includes the program described in the description of the hardware of the 15th to 25th embodiments, and further. It is necessary to hold the withdrawal processing execution reservation date information acquisition program and the withdrawal execution processing subprogram to realize the above functions in the non-volatile memory, and expand each to the main memory based on the start instruction. Execute the program according to the above procedure. FIG. 78 shows the hardware of the 26th embodiment based on the 15th embodiment based on the 10th embodiment. Data and information used / / and generated / acquired are also expanded from the non-volatile memory to the main memory. The data is data showing the amount of money, such as all or part of the payable consideration amount, the prepaid amount, the prepaid request amount, or the prepaid amount, the divided amount of the prepaid amount, etc. Person identification information, payment method identification information, prepayment history, time information, etc. In addition, in order to realize the functions described in the 13th and 14th embodiments, the worker authentication program, the employer authentication program, the remaining amount range judgment program, the authority information holding program, and the employer use their own authority information. Once certified by the fixed date prepayment system, the authority information holding department can register worker authority information in association with worker identification information. Worker authority information registration program, worker identification information related program, labor Receivable information retention program, labor receivable information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repetitive payable range judgment program, payable pair A value retention program, may be similarly configured, deployed, and run on hardware. As for the terminals used by workers, hardware resources such as smartphones are used by the corresponding programs in cooperation with these programs. This point is the same from the first embodiment to the present embodiment.

<Example 26 Processing flow>

In addition to, or partially or entirely, in addition to the process flow according to any one of the processes of Embodiments 15 to 25, the following processes are performed. As shown in FIG. 77, the processing flow of the tenth embodiment is on the left side, and the processing flow peculiar to the present embodiment is on the right side. To explain the processing flow on the right side,
In the start processing request acquisition step (as) (S7709), the process of acquiring the start processing request of the wage prepaid request in association with the worker identification information is performed, and if it has not been acquired, the labor claim information acquisition in the processing flow on the left side is acquired. If you go back to step (bf) (S7702) and get it,
In the withdrawal processing execution reservation date information acquisition step (at) (S7710), the withdrawal processing execution reservation date information which is the information indicating the execution date of the withdrawal processing which is the processing of withdrawal of money etc. by advance payment from the user is obtained. Perform the process to acquire
In the start processing request time information acquisition step (cd) (S7711), the process of acquiring the time information including the date when the start processing request is acquired is performed.
In the prepayable amount acquisition step (at) (S7712), the labor receivable information associated with the worker identification information, the recurring payment date information associated with the worker identification information, and the repeat payment associated with the worker identification information. Process to obtain the prepayable amount, which is the amount that allows the prepayment request based on all or part of the payable consideration paid on the return payment date.
In the prepayment request amount acquisition step (aw) (S7713), the prepayment request amount is acquired by associating it with the worker identification information within the range not exceeding the prepayment possible amount.
In the prepaid processing step (ax) (S7714), a process for performing prepaid processing, which is a process for prepaid the acquired prepaid request amount, is performed.
In the withdrawal execution processing sub-step (bw) (S7715), the withdrawal processing is performed based on the acquired withdrawal processing execution reservation date information and the time information acquired by the time information acquisition unit (AE) (S7711). Withdrawal processing execution Processing is performed so that the withdrawal processing is executed on the date specified by the reserved date information.
In the prepayment history holding step (ay) (S7716), the prepayment history, which is the history of the prepayment processing in the prepayment processing step (ax) (S7714), is held in association with the worker identification information.
This is how the fixed date prepaid system, which is a computer, operates.

These processing steps are separate processes from the fixed date prepayment processing of Embodiments 10 to 14, and when the relationship between the time information and the recurring payment date is other than the predetermined relationship in the fixed date prepayment processing. A branch for determining whether or not to make a prepaid date on an arbitrary date can be inserted in, and a process specific to the present embodiment can be executed when it is determined that a prepaid process on an arbitrary date should be performed. In addition, whether or not to execute the prepayment on an arbitrary date is first triggered by the acquisition of the start processing request by the worker.

Allow prepaid processing to be booked on a future date. After making a reservation on a future date, as a result of separately requesting and executing payment on a date earlier than the above date, the balance of labor receivables will be insufficient and payment processing will not be possible on the previously reserved reservation date. Can be prevented.

<Embodiment 27 Mainly relating to the invention according to claim 45> Deposit

<Outline of Embodiment 27>

The 27th embodiment is a so-called deposit, in which the employer performs a recurring payment process and / or a deposit for a prepaid process performed on an employee or a worker. It is a fixed date prepayment system that determines whether to execute the payment request requested by the employee or worker based on the deposit information.

<Structure of Embodiment 27>

As shown in FIG. 79, in the fixed date prepayment system of the 27th embodiment, the employer performs the repetitive payment processing and / and the deposit for the prepayment processing performed on the worker based on the 10th embodiment. Based on the deposit information, it is configured to determine whether to execute the payment request requested by the worker. As shown in FIG. 73, a contract-related information holding unit (BE) (7925), a labor claim information acquisition department (BF) (7926), a recurring payment date information holding unit (AC) (7903), and a payment method. Identification information acquisition unit (AD) (7904), time information acquisition unit (AE) (7905), recurring payment date relationship judgment unit (AF) (7906), recurring payment processing unit (AG) (7907) It has a recurring payment processing history holding unit (AH) (7908), a deposit information acquisition unit (BX) (7938), a payment processing amount information acquisition unit (BY) (7939), and payment processing execution. It has a determination rule holding unit (BZ) (7940) and a payment processing execution determination unit (CA) (7941).

<Explanation of Embodiment 27 Configuration>

<Embodiment 27 Deposit Information Acquisition Department (BX) (7938)>

The "Deposited Information Acquisition Department (BX)" (7938) associates with the user identification information and identifies the employee with the employee identification information or the worker identification information associated with the user identification information. It is configured to obtain deposit information for recurring payment processing and / and prepaid processing performed on a person or worker.
"Deposit information" refers to information for the user to substantially control the liquidity of money or the like over the operator or administrator of the fixed date prepayment system. For example, it is information such as whether a sufficient amount of remittance has been made from the user to the operator or the like, or whether a sufficient amount of money has been transferred to an account of a bank or the like controlled by the operator or the like. In the case of, not only the amount but also the date and time information may be included in the deposit information. In addition, information such as remittance reservations may be included as well as past movements such as actual money. Alternatively, it may include information on the loan made in the name of the user (loan record, loan reservation, loan limit setting).

<Implementation 27 Payment Processing Amount Information Acquisition Department (BY) (7939)>

The "payment processing amount information acquisition unit (BY)" (7939) is information indicating the amount of payment processing to be executed by the recurring payment processing unit (AG) (7907) and / and the prepaid processing unit (AX). It is configured to acquire payment processing amount information.

<Embodiment 27 Payment Processing Execution Judgment Rule Holding Unit (BZ) (7940)>

The "payment processing execution judgment rule holding unit (BZ)" (7940) is a rule for determining whether to execute the payment processing to be executed based on the acquired payment processing amount information and the deposit information. It is configured to hold the execution decision rule.

<Embodiment 27 Payment Processing Execution Judgment Unit (CA) (7941)>

The "Payment Processing Execution Judgment Unit (CA)" (7941) should execute payment processing based on the retained payment processing execution judgment rule, the retained deposit information, and the acquired payment processing amount information. It is configured to judge the information.

<Embodiment 27 Hardware Configuration>

As shown in FIG. 81, the hardware configuration of the present embodiment based on the tenth embodiment, the present invention and the present embodiment can basically be configured by a general-purpose computer program and various devices. The operation of the computer basically takes the form of loading the program recorded in the non-volatile memory into the main memory and executing the processing in the main memory, the CPU, and various devices. Communication with the device is done via an interface connected to the bus line. The interface may include a display interface, a keyboard, a communication buffer, and the like.

As shown in this figure, the contract-related information retention program, the labor claim information acquisition program, the repeat payment date information retention program, the payment method identification information acquisition program, the time information acquisition program, and the repeat payment date relationship judgment. A program, a recurring payment processing program, a recurring payment processing history holding program, a deposit information acquisition program, a payment processing amount information acquisition program, a payment processing execution judgment rule holding program, and a payment processing execution judgment program. It is held in the non-volatile memory, and these programs are read into the main memory and expanded to the main memory based on the execution instructions of a series of programs, and these programs are executed based on the operation start instruction.

These programs acquire, retain, and perform other processing such as employer identification information, worker identification information, contractual information, recurring payment date information, payment method identification information, and time information according to their functions. .. This information is also held in the non-volatile memory, and is read and expanded in the main memory as needed. In this computer, the non-volatile memory, main memory, CPU, and interface (for example, display, keyboard, communication, etc.) are connected to the bus line via the chipset and communicate with each other as described in the premise of the embodiment. It is configured to be possible.

<Example 27 Processing flow>

The processing flow of the present embodiment 27 based on the tenth embodiment is shown in FIG. 80. In the present invention, the 27th embodiment, the following processing is performed as an operation method of the fixed date prepaid system, which is a computer described in the description of the hardware. This process can also be described as an operation program of a fixed date prepaid system which is a computer.

As shown in FIG. 80, this process
In the contractual information retention step (be) (S8001), the employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information and , Performs processing to retain the worker identification information that identifies the worker who receives the payable consideration based on the labor claim information and the contractual relationship information that is the information related based on the contractual relationship.
In the deposit information acquisition step (bx) (S8002), it is repeated in association with the employer identification information and performed on the worker identified by the worker identification information associated with the employer identification information. Perform payment processing and / and processing to acquire deposit information for prepaid processing,
In the payment processing execution judgment rule holding step (bz) (S8003), payment processing execution judgment is a rule for determining whether to execute the payment processing to be executed based on the acquired payment processing amount information and the deposit information. Performs the process of holding the rule
In the labor claim information acquisition step (bf) (S8004), all of the payable consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information. Or, perform a process to acquire a part based on the employer identification information associated with the worker identification information of the worker.
In the recurring payment date information retention step (ac) (S8005), information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor claim information. Performs processing to retain payment date information in association with worker identification information,
In the payment processing amount information acquisition step (by) (S8006), it is information indicating the amount of payment processing to be executed by the recurring payment processing step (ag) (S8011) and / and the prepaid processing (step) (ax). Performs processing to acquire payment processing amount information,
In the time information acquisition step (ae) (S8007), the process of acquiring the time information including the date is performed.
In the repeat payment date relationship determination step (af) (S8008), it is determined whether the acquired time information has a predetermined relationship with the repeat payment date defined in the repeat payment date information associated with the worker identification information. Process is performed, and if it does not have a predetermined relationship, it is returned to before the time information acquisition step (ae) (S8007), and if it has a predetermined relationship, it is returned.
In the payment method identification information acquisition step (ad) (S8009), the process of acquiring the payment method identification information, which is the information for identifying the payment method for all or part of the payable consideration for the worker, in association with the worker identification information. And
In the payment processing execution judgment step (ca) (S8010), it is determined whether or not the payment processing should be executed based on the retained payment processing execution judgment rule, the retained deposit information, and the acquired payment processing amount information. If it is determined that the payment process should not be executed, the process to return to the payment processing amount information acquisition step (by) (S8006) should be performed, and if it is determined that the payment process should be executed.
In the recurring payment processing step (ag) (S8011), in the processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the worker identification information. Perform a certain payment processing process and
In the recurring payment processing history holding step (ah) (S8012), a process of holding the payment processing history in the recurring payment processing step (ag) (S8011) in association with the worker identification information is performed.
This is how the fixed date prepaid system, which is a computer, operates.

Although the configuration, hardware, and processing flow have been described based on the tenth embodiment, the same effect can be obtained based on the other embodiments.

<Effect of Embodiment 27>

In the present embodiment, by responding to the repetitive payment processing and / and the prepaid processing request from the worker within the range deposited by the employer, the deposit and credit of the employer deposited at the financial institution should occur. It is possible to prevent the range from being exceeded. If the above situation occurs, it may damage the credit of the employer and lead to a disadvantageous situation in subsequent transactions with financial institutions. Such concerns can be prevented.

<Embodiment 28 Mainly relating to claim 46> Prepaid amount is determined in consideration of the deposit.

<Outline of Embodiment 28>

In this embodiment, it is a so-called deposit, and the employer performs the recurring payment processing and / and the deposit for the prepaid processing performed on the worker. It is a fixed date prepayment system that determines whether to execute the payment request requested by the worker based on the deposit information.

<Structure 28 of the embodiment>

The 28th embodiment is based on any one of the first to the 26th embodiments. For example, when the embodiment 10 is used as a basis, as shown in FIG. 82, the configuration includes a contract-related information holding unit (BE) (8225), a labor claim information acquisition unit (BF) (8226), and the like. Repeated payment date information holding unit (AC) (8203), payment method identification information acquisition unit (AD) (8204), time information acquisition unit (AE) (8205), and repeated payment date relationship judgment unit (AF). ) (8206), a recurring payment processing unit (AG) (8207), a recurring payment processing history holding unit (AH) (8208), and further, a deposit information acquisition unit (BX) (8238). The Labor Claim Information Acquisition Department (BE) has a means for acquiring depositable information-dependent prepaid amount (CB) (8242).

As described in the previous embodiment, the worker authentication unit, the employer authentication unit, the authority information holding unit, the remaining amount range judgment unit, and the authority information registration unit (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information), the authority information holding department, the worker identification information related department, and the labor claim. Information Retention Department, Labor Claim Information Retention Department Update Department, Authority Information Notification Department, Authority Information Recording Department, Fixed Date Prepaid Desired Amount Input Department, Fixed Date Prepaid Desired Amount Testing Department, Repeatable Payable Range Judgment Department, Payable Consideration It may be configured to have a holding portion. Hereinafter, a configuration unique only to this embodiment will be described.

<Embodiment 28 Deposit Information Acquisition Department (BX) (8238)>

The "Deposited Information Acquisition Department (BX)" (8238) associates with the user identification information and identifies the employee with the employee identification information or the worker identification information associated with the user identification information. It is configured to obtain deposit information for recurring payment processing and / and prepaid processing performed on a person or worker.
<Embodiment 28 Deferred Information Dependent Prepaid Amount Acquisition Means (CB) (8242)>

"Deposit information dependent prepaid amount acquisition means (CB)" (8242) is the salary receivable information acquisition department (AB) or labor receivable information acquisition department (BE) (8225), or / and the prepaid amount acquisition department (AT). Is the consideration that can be paid to the subordinate or / and the worker before the salary payment date or the wage payment date determined between the employer based on the acquired deposit information and the salary receivable information and / and the labor receivable information. It is configured to acquire all or part of the payable consideration that is. Since the amount that can be paid to the worker is obtained in consideration of the deposit information deposited by the employer, for example, if the deposit is insufficient for the worker's request, the amount that is commensurate with the reservation is set as the payable amount. Can be presented. Further, since the determination processing step is one less than that of the 27th embodiment, the system can be simplified in configuration.

<Embodiment 28 Hardware>

The hardware configuration of the fixed date prepaid system of the 28th embodiment will be described with reference to FIG. 84 based on the 10th embodiment. As shown in FIG. 84, the program described in the tenth embodiment is executed using the hardware described in the premise part of the description of the embodiment as a resource. In addition to that, recurring payment processing and / and prepayment processing performed by the employer on the worker identified by the worker identification information associated with the employer identification information in association with the employer identification information. It has a deposit information acquisition program to acquire deposit information for, and further, the salary receivable information acquisition program and / and the labor receivable information acquisition program, or / and the prepaid amount acquisition program are the acquired deposit information and salary receivables. All or one of the payable consideration that is the consideration that can be paid to the worker or / and the worker before the salary payment date or wage payment date determined with the employer based on the information and / and the labor claim information. It has a deposit information-dependent prepaid amount acquisition subprogram to acquire a department. These programs are held in non-volatile memory, expanded to main memory when started, and executed sequentially by the CPU in the order in which they should perform their functions.

As described in the previous embodiment, the worker authentication program, the employer authentication program, the authority information retention program, the remaining amount range judgment program, and the authority information registration program (the employer has a fixed date with his / her own authority information). Once the prepaid system is certified, the authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information retention program, worker identification information related program, labor receivables. Information retention program, labor claim information retention department update program, authority information notification program, authority information recording program, fixed date prepayment desired amount input program, fixed date prepayment desired amount test program, repeatable range judgment program, payable consideration It may be configured to have a retention program.

<Example 28 Processing flow>

In addition to the processing flow described in the tenth embodiment, the deposit information acquisition step (bx), the salary receivable information acquisition step (ab) and / and the labor receivable information acquisition step (be), or / and the prepaid amount acquisition step ( It has a deposit information-dependent prepaid amount acquisition substep (cb) included in at).
FIG. 83 shows a flow of processing of the present embodiment based on the tenth embodiment. It further has a deposit information acquisition step (bx) (S8303) and a deposit information dependent prepaid amount acquisition substep (cb) (S8302).

In addition to these, a worker authentication step, an employer authentication step, an authority information retention step, a judgment step within the remaining amount range, and an authority information registration step (employers are certified by a fixed date prepayment system with their own authority information). The authority information holding department can register the worker's authority information in association with the worker identification information.), Authority information holding step, worker identification information related step, labor claim information holding step, labor claim Information retention unit update step, authority information notification step, authority information recording step, fixed date prepayment desired amount input step, fixed date prepayment desired amount test step, repetitive payable range determination step, payable consideration holding step It may be configured.

Although the configuration, hardware, and processing flow have been described in the description of the 28th embodiment based on the 10th embodiment, the same effect can be obtained in the other 1st to 26th embodiments (excluding the 10th embodiment).

<Effect of Embodiment 28>

Since the payable amount is acquired in consideration of the deposit information deposited by the user, it is possible to have a simple configuration with less one-step processing as compared with the 27th embodiment.

The fixed date prepayment system of the present invention pays out of the consideration that the employer is obliged to pay to the employee (or worker) based on the salary claim (or labor claim) before the payment date of the salary (or wage). It relates to a system in which all or part of the possible consideration is paid every time on the recurring payment date.

Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. Based on the contract relationship information retention step (be) that holds the contract relationship information, which is the information related to the worker identification information that identifies the worker who is the person, and the labor claim information of the worker. All or part of the payable consideration, which is the consideration payable to the worker before the wage payment date set with the employer, is added to the employer identification information associated with the worker identification information of the worker. Repetitive payment, which is information that determines the labor receivable information acquisition step (bf) to be acquired based on the labor receivable information and the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor receivable information. Repeated payment date information retention step (ac), which retains day information in association with worker identification information, and payment method identification information, which is information that identifies the payment method for all or part of the payable consideration for workers. The payment method identification information acquisition step (ad) acquired in association with the worker identification information, the time information acquisition step (ae) in which the time information including the date is acquired, and the acquired time information are associated with the worker identification information. The judgment results in the repeat payment date relation judgment step (af) and the repeat payment date relation judgment step (af) for judging whether or not the relationship has become a predetermined relationship with the repeat payment date specified in the repeat payment date information are repeated. All or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the worker identification information when it is judged that the relationship has been determined with the return payment date. Repetitive payment processing history (ag) that performs payment processing, which is processing for payment, and repetitive payment processing history that retains the history of payment processing in the repetitive payment processing step (ag) in association with worker identification information. Retention step (ah) and
It is composed of a computer consisting of hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device driver, etc.) for functioning each of the above steps. The software provides a method of operating a fixed-date prepayment system, which is a computer configured to perform various calculations using hardware resources and realize various functions through the required data and information.

Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. Based on the contract relationship information retention step (be) that holds the contract relationship information, which is the information related to the worker identification information that identifies the worker who is the person, and the labor claim information of the worker. All or part of the payable consideration, which is the consideration payable to the worker before the wage payment date set with the employer, is added to the employer identification information associated with the worker identification information of the worker. Repetitive payment, which is information that determines the labor receivable information acquisition step (bf) to be acquired based on the labor receivable information and the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor receivable information. Repeated payment date information retention step (ac), which retains day information in association with worker identification information, and payment method identification information, which is information that identifies the payment method for all or part of the payable consideration for workers. The payment method identification information acquisition step (ad) acquired in association with the worker identification information, the time information acquisition step (ae) in which the time information including the date is acquired, and the acquired time information are associated with the worker identification information. The judgment results in the repeat payment date relation judgment step (af) and the repeat payment date relation judgment step (af) for judging whether or not the relationship has become a predetermined relationship with the repeat payment date specified in the repeat payment date information are repeated. All or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the worker identification information when it is judged that the relationship has been determined with the return payment date. Repetitive payment processing history (ag) that performs payment processing, which is processing for payment, and repetitive payment processing history that retains the history of payment processing in the repetitive payment processing step (ag) in association with worker identification information. A computer consisting of holding steps (ah) and hardware (CPU, memory, bus, input / output device, various peripheral devices, user interface, etc.) and software (BIOS, OS, device) for functioning each of the above steps. The software is readable and executable in a fixed-date prepayment system, which is a computer that is configured to perform various calculations using hardware resources and realize various functions through the required data and information. Provide an operation program.

When the "repeated payment processing unit (AG)" (2807) determines that the judgment result of the repetitive payment date relation judgment unit (AF) (2806) has a predetermined relationship with the repetitive payment date. The payment process, which is the process for payment of all or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the worker identification information, is performed. The "processing for payment" may be the payment processing itself, or may not be the payment processing itself, but may be a processing performed for the payment processing. "Payment" means transfer processing to the bank account of the electronic money operating company, transfer processing to the bank account of the worker, transfer processing to the bank account of the electronic money operating company, transfer processing to the bank account of the worker, labor. It includes various things such as charge processing for a person's electronic money and processing for a worker's electronic money transfer (transfer point).

The recurring payment processing program acquires the worker identification information in association with the repetitive payment date when the judgment result in the repetitive payment date relationship judgment step (af) is the judgment result that the repetitive payment date has a predetermined relationship. Perform payment processing, which is processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information. The payment process is as described above.

As shown in FIG. 32, the processing flow of the operation method of the fixed date prepaid system, which is the computer described in the description of the hardware of the eleventh embodiment, is as follows.
The contractual information retention step (be) (S3201) is an employer identification information that identifies an employer who pays a payable consideration to a worker identified by the worker identification information based on the labor claim information. , Performs processing to retain the worker identification information that identifies the worker who receives the payable consideration based on the labor claim information and the contractual relationship information that is the information related based on the contractual relationship.
The labor claim information acquisition step (bf) (S3202) is the total payable consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information. Or, perform a process to acquire a part based on the employer identification information associated with the worker identification information of the worker.
The recurring payment date information retention step (ac) (S3203) is information that determines the recurring payment date for repeatedly paying all or part of the payable consideration paid to the worker based on the labor claim information. Performs processing to retain payment date information in association with worker identification information,
The payment method identification information holding step (aj) (S3204) performs a process of holding a plurality of payment method identification information.
The payment method selection acceptance step (ak) (S3205) accepts one or more selections of payment method identification information held in association with the worker identification information.
The payment method payment method identification step (am) (S3206) allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information.
The time information acquisition step (ae) (S3207) performs the process of acquiring the time information including the date.
The recurring payment date relationship determination step (af) (S3208) determines whether the acquired time information has a predetermined relationship with the recurring payment date defined in the recurring payment date information associated with the worker identification information. Process and
If the judgment result in the repeat payment date relationship judgment step (af) (S3208) is a judgment result that does not have a predetermined relationship with the repeat payment date, before the time information acquisition step (ae) (S3207). Perform the process to return to
When the judgment result in the repeat payment date relationship judgment step (af) (S3208) is the judgment result that the relationship with the repeat payment date has become predetermined.
The payment method identification information acquisition step (ad) (S3209) is a process of acquiring payment method identification information, which is information for identifying a payment method for all or part of the payable consideration for a worker, in association with the worker identification information. And
The recurring payment processing step (ag) (S3210) is the processing for payment of all or part of the payable consideration by the payment method identified by the payment method identification information obtained in association with the worker identification information. Perform the processing to process the payment,
The recurring payment processing history holding step (ah) (S3211) performs a process of holding the payment processing history in the recurring payment processing step (ag) (S3210) in association with the worker identification information.
This is how the fixed date prepaid system, which is a computer, operates.

Claims (84)

Employment relationship information holding department that holds employment relationship information that is information that associates user identification information that identifies the user and employee identification information that identifies the employee employed by the user based on the employment relationship. (AA) and
All or part of the payable consideration, which is the consideration that can be paid to the subordinate before the salary payment date determined with the employer based on the employee's salary claim information, is used as the employee identification information of the employee. Payroll Receivables Information Acquisition Department (AB), which is acquired based on the associated user identification information,
Repeated payment of all or part of the payable consideration paid to an employee based on salary receivable information Repeated payment date information, which is information that determines the recurring payment date, is retained in association with the employee identification information. Payment date information holding department (AC) and
The Payment Method Identification Information Acquisition Department (AD), which acquires payment method identification information in association with employee identification information, which is information that identifies payment methods for all or part of the payable consideration for employees.
The time information acquisition unit (AE) that acquires time information including the date,
The Repeated Payment Date Relationship Judgment Department (AF), which determines whether the acquired time information has a predetermined relationship with the repeated payment date defined in the repeated payment date information associated with the employee identification information,
If the judgment result by the Repeated Payment Date Relationship Judgment Department (AF) is the judgment result that the relationship has a predetermined relationship with the repeated payment date, the payment method identification information acquired in association with the employee identification information is used. With the Recurring Payments Processing Department (AG), which processes payments, which is the processing for the payment of all or part of the payable consideration by the identified payment method.
The Recurring Payment Processing History Retention Department (AH), which retains the payment processing history in the Recurring Payment Processing Department (AG) in association with the employee identification information,
Fixed date prepayment system with. Payment method identification information holding unit (AJ) that holds multiple payment method identification information,
A payment method selection receptionist (AK) that accepts one or more selections of payment method identification information that is held in association with the employee identification information.
A payment method payment consideration allocation unit (AM) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the employee identification information.
Have more
The fixed date prepayment system according to claim 1, wherein the payment method identification information acquisition unit (AD) is configured to acquire the payment method identification information for which the selection has been accepted in association with the employee identification information. It further has a remittance unique information holding unit (AN) that holds the employee identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information in association with each other. The fixed date prepayment system according to claim 1 or 2. Claims 1 to 3 further having a Repeated Payment Date Information Editing Department (AP) that edits the Repeated Payment Date Information and / and Employee Identification Information held in the Repeated Payment Date Information Holding Department (AC). Fixed date prepayment system described in any one of. Any one of claims 1 to 4 further having a recurring payment date information recording unit (AR) for recording recurring payment date information and / and employee identification information in the recurring payment date information holding unit (AC). Fixed date prepayment system as described in. The Start Processing Request Acquisition Department (AS), which acquires the start processing request for salary prepayment requests in association with employee identification information,
The start processing request time information acquisition unit (CD) that acquires time information including the date when the start processing request was acquired, and
Payroll information associated with employee identification information, recurring payment date information associated with employee identification information, if available, and recurring payment date information associated with employee identification information, if available. The Prepaid Amount Acquisition Department (AT), which acquires the prepaid amount, which is the amount that allows the prepaid request based on all or part of the payable consideration paid on the payment date, and
The Prepaid Request Amount Acquisition Department (AW), which acquires the prepaid request amount in association with the employee identification information within the range that does not exceed the prepaid amount,
The prepaid processing department (AX), which performs prepaid processing, which is the processing for prepaid the acquired prepaid request amount,
The prepaid history holding unit (AY), which holds the prepaid history, which is the history of prepaid processing in the prepaid processing unit (AX), in association with the employee identification information,
The fixed date prepayment system according to any one of claims 1 to 5. The processing result acquisition unit (AZ) that acquires the processing result that is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the employee identification information.
The SNS identification information holding unit (BA) that holds the SNS identification information used by the employee in association with the employee identification information,
The processing result notification unit (BB) that notifies the processing result via the SNS identified by the SNS identification information associated with the employee identification information associated with the processing result, and
The fixed date prepayment system according to any one of claims 1 to 6. The remittance unique information holding unit (AN) holds the remittance SNS identification information holding means (AN) that holds the employee identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. The fixed date prepayment system according to claim 7, which is subordinate to claim 3 having BC). The salary receivable information acquisition department (AB) provides a fixed amount acquisition means (BD) for acquiring information indicating a fixed amount as all or part of the payable consideration paid to the employee acquired in association with the employee identification information. The fixed date prepayment system according to any one of claims 1 to 8. Employment relationship information retention step that retains employment relationship information, which is information that associates user identification information that identifies an employer and employee identification information that identifies an employee employed by an employer based on an employment relationship. (aa) and
All or part of the payable consideration, which is the consideration that can be paid to the subordinate before the salary payment date determined with the employer based on the employee's salary claim information, is used as the employee identification information of the employee. Payroll receivable information acquisition step (ab) to be acquired based on the associated user identification information,
Repeated payment of all or part of the payable consideration paid to an employee based on salary receivable information Repeated payment date information, which is information that determines the recurring payment date, is retained in association with the employee identification information. Payment date information retention step (ac),
The payment method identification information acquisition step (ad) for acquiring the payment method identification information, which is the information for identifying the payment method for all or part of the payable consideration, in association with the employee identification information, and the payment method identification information acquisition step (ad).
Time information acquisition step (ae) to acquire time information including date,
The recurring payment date relationship determination step (af), which determines whether the acquired time information has a predetermined relationship with the recurring payment date defined in the recurring payment date information associated with the employee identification information, and
If the judgment result in the recurring payment date relationship judgment step (af) is the judgment result that the repetitive payment date has a predetermined relationship, the payment method identification information acquired in association with the employee identification information is used. A recurring payment processing step (ag) that performs payment processing, which is the processing for payment of all or part of the payable consideration by the identified payment method.
The recurring payment processing history retention step (ah), which retains the payment processing history in the recurring payment processing step (ag) in association with the employee identification information,
How to operate a fixed date prepaid system that is a calculator with. The payment method identification information retention step (aj), which retains multiple payment method identification information, and
A payment method selection acceptance step (ak) that accepts one or more selections of payment method identification information that is held in association with the employee identification information.
A payment method payment consideration assignment step (am) that allocates all or part of the payable consideration to one or more payment method identifications selected in association with the employee identification information.
Have more
The operation of the fixed date prepayment system, which is the calculator according to claim 10, wherein the payment method identification information acquisition step (ad) is configured to acquire the payment method identification information for which the selection has been accepted in association with the employee identification information. Method. It further has a remittance-specific information holding step (an) that holds the employee identification information, the payment method identification information, and the remittance-specific information used for the payment method identified by the payment method identification information in association with each other. A method of operating a fixed date prepayment system, which is the computer according to claim 10 or 11. Claims 10 to 10 further include a recurring payment date information editing step (ap) for editing the recurring payment date information and / and employee identification information held in the recurring payment date information retention step (ac). A method of operating a fixed date prepayment system, which is the computer according to any one of 12. Any one of claims 10 to 13 further comprising a recurring payment date information recording step (ar) for recording recurring payment date information and / and employee identification information in the recurring payment date information holding unit (AC). How to operate a fixed date prepayment system, which is the calculator described in. The start processing request acquisition step (as), which acquires the start processing request for the salary prepayment request in association with the employee identification information,
Start processing request time information acquisition step (cd) to acquire time information including the date when the start processing request was acquired, and
Payroll information associated with employee identification information, recurring payment date information associated with employee identification information, if available, and recurring payment date information associated with employee identification information, if available. The prepayable amount acquisition step (at) to obtain the prepayable amount, which is the amount that allows the prepayment request based on all or part of the payable consideration paid on the payment date.
The prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the employee identification information within the range that does not exceed the prepayment possible amount, and
The prepaid processing step (ax) for prepaid processing, which is the processing for prepaid the acquired prepaid request amount,
The prepaid history holding step (ay), which holds the prepaid history, which is the history of the prepaid processing in the prepaid processing step (ax), in association with the employee identification information,
A method of operating a fixed date prepaid system, which is the computer according to any one of claims 10 to 14. The processing result acquisition step (az) of acquiring the processing result which is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the employee identification information,
An SNS identification information holding step (ba) that holds the SNS identification information used by the employee in association with the employee identification information, and
The processing result notification step (bb) for notifying the processing result via the SNS identified by the SNS identification information associated with the employee identification information associated with the processing result, and
The method of operating a fixed date prepaid system, which is the computer according to any one of claims 10 to 15. The remittance unique information holding step (an) is a remittance SNS identification information holding sub-step that holds the employee identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. The method of operating a fixed date prepayment system, which is the computer according to claim 16, which is subordinate to claim 12 having (bc). The payroll receivable information acquisition step (ab) is a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount as all or part of the payable consideration paid to the employee acquired in association with the employee identification information. A method of operating a fixed date prepayment system, which is the computer according to any one of claims 10 to 17. Employment relationship information retention step that retains employment relationship information, which is information that associates user identification information that identifies an employer and employee identification information that identifies an employee employed by an employer based on an employment relationship. (aa) and
All or part of the payable consideration, which is the consideration that can be paid to the subordinate before the salary payment date determined with the employer based on the employee's salary claim information, is used as the employee identification information of the employee. Payroll receivable information acquisition step (ab) to be acquired based on the associated user identification information,
Repeated payment of all or part of the payable consideration paid to an employee based on salary receivable information Repeated payment date information, which is information that determines the recurring payment date, is retained in association with the employee identification information. Payment date information retention step (ac),
The payment method identification information acquisition step (ad) for acquiring the payment method identification information, which is the information for identifying the payment method for all or part of the payable consideration, in association with the employee identification information, and the payment method identification information acquisition step (ad).
Time information acquisition step (ae) to acquire time information including date,
The recurring payment date relationship determination step (af), which determines whether the acquired time information has a predetermined relationship with the recurring payment date defined in the recurring payment date information associated with the employee identification information, and
If the judgment result in the recurring payment date relationship judgment step (af) is the judgment result that the repetitive payment date has a predetermined relationship, the payment method identification information acquired in association with the employee identification information is used. A recurring payment processing step (ag) that performs payment processing, which is the processing for payment of all or part of the payable consideration by the identified payment method.
The recurring payment processing history retention step (ah), which retains the payment processing history in the recurring payment processing step (ag) in association with the employee identification information,
An operating program written readable and executable in a fixed date prepaid system that is a computer with. The payment method identification information retention step (aj), which retains multiple payment method identification information, and
A payment method selection acceptance step (ak) that accepts one or more selections of payment method identification information that is held in association with the employee identification information.
A payment method payment consideration assignment step (am) that allocates all or part of the payable consideration to one or more payment method identifications selected in association with the employee identification information.
Have more
The payment method identification information acquisition step (ad) is read into a fixed date prepayment system, which is the calculator according to claim 19, which is configured to acquire the payment method identification information for which the selection has been accepted in association with the employee identification information. An action program written executable. It further has a remittance-specific information holding step (an) that holds the employee identification information, the payment method identification information, and the remittance-specific information used for the payment method identified by the payment method identification information in association with each other. An operating program readable and executable in a fixed date prepayment system, which is the computer according to claim 19 or claim 20. Claims 19 to 19 further include a recurring payment date information editing step (ap) for editing the recurring payment date information and / and employee identification information held in the recurring payment date information retention step (ac). An operation program readable and executable in a fixed date prepayment system, which is the computer according to any one of 21. Any one of claims 19 to 22 further having a recurring payment date information recording step (ar) for recording recurring payment date information and / and employee identification information in the recurring payment date information holding unit (AC). An operating program written readable and executable in a fixed-date prepayment system, which is the computer described in. The start processing request acquisition step (as), which acquires the start processing request for the salary prepayment request in association with the employee identification information,
Start processing request time information acquisition step (cd) to acquire time information including the date when the start processing request was acquired, and
Payroll information associated with employee identification information, recurring payment date information associated with employee identification information, if available, and recurring payment date information associated with employee identification information, if available. The prepayable amount acquisition step (at) to obtain the prepayable amount, which is the amount that allows the prepayment request based on all or part of the payable consideration paid on the payment date.
The prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the employee identification information within the range that does not exceed the prepayment possible amount, and
The prepaid processing step (ax) for prepaid processing, which is the processing for prepaid the acquired prepaid request amount,
The prepaid history holding step (ay), which holds the prepaid history, which is the history of the prepaid processing in the prepaid processing step (ax), in association with the employee identification information,
An operation program readable and executable in a fixed date prepaid system, which is the computer according to any one of claims 19 to 23. The processing result acquisition step (az) of acquiring the processing result which is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the employee identification information,
An SNS identification information holding step (ba) that holds the SNS identification information used by the employee in association with the employee identification information, and
The processing result notification step (bb) for notifying the processing result via the SNS identified by the SNS identification information associated with the employee identification information associated with the processing result, and
An operation program readable and executable in a fixed date prepaid system, which is the computer according to any one of claims 19 to 24. The remittance unique information holding step (an) is a remittance SNS identification information holding sub-step that holds the employee identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. An operating program readable and executable in a fixed date prepayment system, the computer according to claim 25, which is subordinate to claim 21 having (bc). The payroll receivable information acquisition step (ab) is a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount as all or part of the payable consideration paid to the employee acquired in association with the employee identification information. An operating program readable and executable in a fixed date prepayment system, which is the computer according to any one of claims 19 to 26. Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. The Contractual Relationship Information Holding Department (BE), which holds the contractual relationship information that is the information that identifies the worker who is the person and the information that is associated based on the contractual relationship,
All or part of the payable consideration, which is the consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information, is used as the worker identification information of the worker. The Labor Credit Information Acquisition Department (BF), which is acquired based on the associated employer identification information,
Repeated payment of all or part of the payable consideration paid to the worker based on the labor claim information Repeated payment date information that determines the repeated payment date is retained in association with the worker identification information. Payment date information holding department (AC) and
The Payment Method Identification Information Acquisition Department (AD), which acquires payment method identification information in association with worker identification information, which is information that identifies payment methods for all or part of the payable consideration for workers.
The time information acquisition unit (AE) that acquires time information including the date,
The Repeated Payment Date Relationship Judgment Department (AF), which determines whether the acquired time information has a predetermined relationship with the repeated payment date defined in the repeated payment date information associated with the worker identification information,
When the judgment result by the Repeated Payment Date Relationship Judgment Department (AF) is the judgment result that the relationship has a predetermined relationship with the repeated payment date, the payment method identification information acquired in association with the worker identification information is used. With the Recurring Payments Processing Department (AG), which processes payments, which is the processing for the payment of all or part of the payable consideration by the identified payment method.
The Recurring Payment Processing History Retention Department (AH), which retains the payment processing history in the Recurring Payment Processing Department (AG) in association with the worker identification information,
Fixed date prepayment system with. Payment method identification information holding unit (AJ) that holds multiple payment method identification information,
The Payment Method Selection Reception Department (AK), which accepts one or more selections of payment method identification information held in association with the worker identification information, and
A payment method payment consideration allocation unit (AM) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information.
Have more
The fixed date prepayment system according to claim 28, wherein the payment method identification information acquisition unit (AD) is configured to acquire the payment method identification information for which the selection has been accepted in association with the worker identification information. It further has a remittance unique information holding unit (AN) that holds the worker identification information, the payment method identification information, and the remittance unique information used for the payment method identified by the payment method identification information in association with each other. The fixed date prepayment system according to claim 28 or 29. Claims 28 to 30 further include a Repeated Payment Date Information Editing Department (AP) that edits the Repeated Payment Date Information and / and Worker Identification Information held in the Repeated Payment Date Information Holding Department (AC). Fixed date prepayment system described in any one of. Any one of claims 28 to 31 further having a recurring payment date information recording unit (AR) that records recurring payment date information and / and worker identification information in the recurring payment date information holding unit (AC). Fixed date prepayment system as described in. The Start Processing Request Acquisition Department (AS), which acquires the start processing request for wage prepayment requests in association with worker identification information,
The start processing request time information acquisition unit (CD) that acquires time information including the date when the start processing request was acquired, and
Labor receivable information associated with worker identification information, recurring payment date information associated with worker identification information, if available, and recurring payment date information associated with worker identification information, if available. The Prepaid Amount Acquisition Department (AT), which acquires the prepaid amount, which is the amount that allows the prepaid request based on all or part of the payable consideration paid on the payment date, and
The Prepaid Request Amount Acquisition Department (AW), which acquires the prepaid request amount in association with the worker identification information within the range that does not exceed the prepaid amount,
The prepaid processing department (AX), which performs prepaid processing, which is the processing for prepaid the acquired prepaid request amount,
The prepaid history holding unit (AY), which holds the prepaid history, which is the history of prepaid processing in the prepaid processing unit (AX), in association with the worker identification information,
The fixed date prepayment system according to any one of claims 28 to 32. The processing result acquisition unit (AZ) that acquires the processing result that is the result of the payment processing by the recurring payment processing unit (AG) or the prepaid processing by the prepaid processing unit (AX) in association with the worker identification information.
The SNS identification information holding unit (BA) that holds the SNS identification information used by the worker in association with the worker identification information,
The processing result notification unit (BB) that notifies the processing result via the SNS identified by the SNS identification information associated with the worker identification information associated with the processing result, and
The fixed date prepayment system according to any one of claims 28 to 33. The remittance unique information holding unit (AN) holds the remittance SNS identification information holding means (AN) that holds the worker identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. The fixed date prepayment system according to claims 31 to 34, which is subordinate to claim 30 having BC). The Labor Claim Information Acquisition Department (BF) provides fixed amount acquisition means (BD) to acquire information indicating a fixed amount as all or part of the payable consideration paid to workers acquired in association with worker identification information. The fixed date prepayment system according to any one of claims 28 to 35 having. Payment processing admissibility judgment department that determines whether all or part of the payable consideration associated with the worker identification information is less than the prescribed amount and the recurring payment processing department (AG) cannot process the full amount. BG) and
Payment that notifies the worker or / and the employer of payment processing abnormality information indicating that payment processing cannot be performed when the judgment result of the payment processing approval / disapproval judgment department (BG) is the judgment result that payment processing cannot be performed. The fixed date prepayment system according to any one of claims 1 to 9 or 28 to 36, which has a processing abnormality information notification unit (BH). The Prepaid Request Amount Acquisition Department (AW)
Assuming that the prepayment request amount acquired by the prepayment request amount acquisition department (AW) has been processed, it is stipulated that the payment will already be made on the prepayment payment date closest to the user. Fixed amount payment availability judgment means (BJ) to determine whether the fixed amount cannot be paid, and
When the judgment result by the fixed amount payment approval / disapproval judgment means (BJ) is the judgment result that the payment cannot be made.
A prepaid request amount acquisition means (BK), which is a prepaid request amount obtained by reducing the total amount of payments to workers to an amount that can pay the fixed amount.
The fixed-day prepayment system according to claim 36, which is subordinate to claim 33 having. The Wage Payment Date Information Holding Department (BM), which holds wage payment date information that indicates a predetermined wage payment date in association with worker identification information and / and employer identification information,
The amount paid by recurring payment and / or prepaid processing that occurred by the predetermined closing date on the prescribed wage payment date held with the employer based on the worker's labor claim information. Make all or part of the payable consideration, which is the payable consideration excluding the prepayment request amount from the wages that would have been paid in the absence of these recurring payments or prepayments, so that it is payable. The balance payment processing department (BN), which processes the balance payment, which is the processing for payment,
The fixed date prepayment system according to any one of claims 28 to 38. When the balance payment processing unit (BN) that performs the balance payment processing requires a fee for the remittance means used as the payment method when processing the balance, the slip processing for the user to bear the fee ( 39. The fixed date prepayment system according to claim 39, which has a user-paid check processing unit (CE) that includes both electronic slips and slips made of actual sheets. The same shall apply hereinafter. When the balance payment processing department (BN) that processes the balance requires a fee for the remittance method used as the payment method when processing the balance, the remittance company handles the slip to bear the fee. (In claim 40), claim 39 or 40 (in claim 40) having a remittance operator-paid check processing unit (CF) that performs (including both an electronic slip and a slip made of an actual sheet. The same shall apply hereinafter). Fixed date prepayment system described in (Both the user and the remittance operator bear the burden if subordinate). Has an editing authority identification information holding unit (CC) that holds editing authority identification information that identifies editing authority that is the authority to edit recurring payment date information and / and worker identification information.
The contract-related information holding unit (BE) has an editing authority additional holding means (BP) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information.
The Repeated Payment Date Information Editorial Department (AP)
Register and delete the retained recurring payment date information and / and worker identification information only to the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. Editing authority limiting means (BR) that sets restrictions so that editing including can be performed,
The fixed day prepaid system according to claim 31 having. It has an editing authority identification information holding unit (CC) that holds editing authority identification information that identifies editing authority that is the authority to edit wage payment date information and / and worker identification information.
The contract-related information holding unit (BE) has an editing authority additional holding means (BP) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information.
Wage payment date information held by the Wage Payment Date Information Holding Department (BM),
Claims having a wage payment date information editorial department (BS) that allows editing, including registration and deletion, only to those (employers and / and workers) identified by the identification information associated with the editing authority identification information. Item 39. Fixed date prepayment system. The time information acquisition unit (AE) that acquires time information for prepaid processing, which will be described later,
Withdrawal processing execution reservation date information acquisition unit (BT) that acquires withdrawal processing execution reservation date information, which is information indicating the execution date of withdrawal processing, which is the processing of withdrawal of money etc. by advance payment from the user,
Have,
The prepayment processing unit (AX) identifies the withdrawal process with the withdrawal processing execution reservation date information based on the acquired withdrawal processing execution reservation date information and the time information acquired by the time information acquisition unit (AE). The fixed date prepayment system according to any one of claims 33 to 43, which has a withdrawal execution processing means (BW) for processing so that the withdrawal processing is executed on the date to be withdrawn. Recurring payment processing or / or recurring payment processing performed by the employer in association with the employer identification information to the employee or worker identified by the employee identification information or worker identification information associated with the employer identification information. And the Deposit Information Acquisition Department (BX), which acquires deposit information for prepaid processing,
A payment processing amount information acquisition unit (BY) that acquires payment processing amount information, which is information indicating the amount of payment processing that the recurring payment processing unit (AG) and / and the prepaid processing unit (AX) intends to execute.
With the payment processing execution judgment rule holding unit (BZ) that holds the payment processing execution judgment rule, which is a rule for determining whether to execute the payment processing to be executed based on the acquired payment processing amount information and the deposit information. ,
Further, a payment processing execution judgment unit (CA) that determines whether payment processing should be executed based on the retained payment processing execution judgment rule, the retained deposit information, and the acquired payment processing amount information. The fixed date prepayment system according to any one of claims 1 to 9 or 28 to 44. Recurring payment processing or / or recurring payment processing performed by the employer in association with the employer identification information to the employee or worker identified by the employee identification information or worker identification information associated with the employer identification information. And has a deposit information acquisition department (BX) that acquires deposit information for prepaid processing,
The Payroll Information Acquisition Department (AB) or Labor Claim Information Acquisition Department (BE), and / and the Prepaid Amount Acquisition Department (AT) are based on the acquired deposit information and the payroll claim information and / and the labor claim information. Acquire all or part of the payable consideration that is the payable consideration to the subordinates and / and workers before the salary payment date or wage payment date specified with the employer. The fixed date prepayment system according to any one of claims 1 to 9 or 28 to 44 having means (CB). Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. A contract-relationship information retention step (be) that retains contract-relationship information, which is information that identifies a worker who is a person and is information that is associated with each other based on a contractual relationship.
All or part of the payable consideration, which is the consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information, is used as the worker identification information of the worker. The labor claim information acquisition step (bf) acquired based on the associated employer identification information, and
Repeated payment of all or part of the payable consideration paid to the worker based on the labor claim information Repeated payment date information that determines the repeated payment date is retained in association with the worker identification information. Payment date information retention step (ac),
The payment method identification information acquisition step (ad) for acquiring the payment method identification information, which is the information for identifying the payment method for all or part of the payable consideration, in association with the worker identification information,
Time information acquisition step (ae) to acquire time information including date,
The repeat payment date relationship judgment step (af) for determining whether the acquired time information has a predetermined relationship with the repeat payment date defined in the repeat payment date information associated with the worker identification information, and
If the judgment result in the recurring payment date relationship judgment step (af) is the judgment result that the repetitive payment date has a predetermined relationship, the payment method identification information acquired in association with the employee identification information is used. A recurring payment processing step (ag) that performs payment processing, which is the processing for payment of all or part of the payable consideration by the identified payment method.
The recurring payment processing history retention step (ah), which retains the payment processing history in the recurring payment processing step (ag) in association with the worker identification information,
How to operate a fixed date prepaid system that is a calculator with. The payment method identification information retention step (aj), which retains multiple payment method identification information, and
A payment method selection acceptance step (ak) that accepts one or more selections of payment method identification information that is held in association with the worker identification information, and
A payment method payment consideration allocation step (am) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information.
Have more
The operation of the fixed date prepayment system, which is the calculator according to claim 47, configured to obtain the payment method identification information acquisition step (ad) in association with the worker identification information for which the selection has been accepted. Method. It further has a remittance-specific information holding step (an) that holds the worker identification information, the payment method identification information, and the remittance-specific information used for the payment method identified by the payment method identification information in association with each other. A method of operating a fixed date prepayment system, which is the computer according to claim 47 or 48. Claims 47 to 47 further include a recurring payment date information editing step (ap) for editing the recurring payment date information and / and the worker identification information held in the recurring payment date information retention step (ac). A method of operating a fixed date prepayment system, which is the computer according to any one of 49. Any one of claims 47 to 50 further comprising a recurring payment date information recording step (ar) for recording recurring payment date information and / and worker identification information in the recurring payment date information holding unit (AC). How to operate a fixed date prepayment system, which is the computer described in. The start processing request acquisition step (as), which acquires the start processing request for the wage prepayment request in association with the worker identification information,
Start processing request time information acquisition step (cd) to acquire time information including the date when the start processing request was acquired, and
Labor receivable information associated with worker identification information, recurring payment date information associated with worker identification information, if available, and recurring payment date information associated with worker identification information, if available. The prepayable amount acquisition step (at) to obtain the prepayable amount, which is the amount that allows the prepayment request based on all or part of the payable consideration paid on the payment date.
The prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the worker identification information within the range that does not exceed the prepayment possible amount, and
The prepaid processing step (ax) for prepaid processing, which is the processing for prepaid the acquired prepaid request amount,
The prepaid history holding step (ay), which holds the prepaid history, which is the history of the prepaid processing in the prepaid processing step (ax), in association with the worker identification information,
A method of operating a fixed date prepaid system, which is the computer according to any one of claims 47 to 51. The processing result acquisition step (az) of acquiring the processing result which is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the worker identification information,
The SNS identification information holding step (ba), which holds the SNS identification information used by the worker in association with the worker identification information,
A processing result notification step (bb) that notifies the processing result via the SNS identified by the SNS identification information associated with the worker identification information associated with the processing result, and
A method of operating a fixed date prepaid system, which is the computer according to any one of claims 47 to 52. The remittance unique information holding step (an) is a remittance SNS identification information holding sub-step that holds the worker identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. A method of operating a fixed date prepayment system, which is the computer according to claims 50 to 53, which is subordinate to claim 49 having (bc). The labor claim information acquisition step (bf) is a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount as all or part of the payable consideration paid to the worker acquired in association with the worker identification information. A method of operating a fixed date prepayment system, which is the computer according to any one of claims 47 to 54. Payment processing approval / disapproval step () to determine whether all or part of the payable consideration associated with the worker identification information is less than the prescribed amount and the Recurring Payment Processing Department (AG) can process the full amount. bg) and
Payment that notifies the worker or / and the employer of payment processing abnormality information indicating that payment processing cannot be performed when the judgment result in the payment processing approval / disapproval judgment step (bg) is the judgment result that payment processing cannot be performed. The method of operating a fixed date prepayment system, which is the computer according to any one of claims 10 to 18 or 47 to 55, which has a processing abnormality information notification step (bh). The prepaid request amount acquisition step (aw) is
Assuming that the prepayment request amount acquired in the prepayment request amount acquisition step (aw) has been processed, it is stipulated that the payment is already made on the prepayment payment date closest to the user. When the judgment result in the fixed amount payment approval / disapproval judgment substep (bj) and the fixed amount payment approval / disapproval judgment substep (bj) to judge whether or not the fixed amount cannot be paid is the judgment result that the payment cannot be made.
The prepaid request amount acquisition substep (bk), which is the prepaid request amount obtained by reducing the total amount paid to the worker to the amount that can be paid the fixed amount,
The method of operating a fixed-day prepaid system, which is the computer according to claim 55, which is subordinate to claim 52. A wage payment date information retention step (bm) that retains wage payment date information, which is information indicating a predetermined wage payment date in association with worker identification information and / and employer identification information, and
The amount paid by recurring payment and / or prepaid processing that occurred by the predetermined closing date on the prescribed wage payment date held with the employer based on the worker's labor claim information. Make all or part of the payable consideration, which is the payable consideration excluding the prepayment request amount from the wages that would have been paid in the absence of these recurring payments or prepayments, so that it is payable. The balance payment processing step (bn) for processing the balance payment, which is the processing for payment, and
A method of operating a fixed date prepaid system, which is the computer according to any one of claims 47 to 57. When the balance payment processing step (bn) for processing the balance requires a fee for the remittance means used as the payment method for processing the balance, the user is required to pay the fee (slip processing). The fixed date prepayment system according to claim 58, which has a user-paid voucher processing step (ce) that includes both an electronic voucher and a voucher made of an actual sheet. The same shall apply hereinafter. How it works. When the balance payment processing step (bn) for processing the balance requires a fee for the remittance means used as the payment method for processing the balance, the remittance operator pays the fee. It has a remittance operator-paid check processing step (cf) that does (may include both electronic slips and slips made of actual sheets; the same shall apply hereinafter).
The method of operating a fixed date prepaid system, which is the computer according to claim 58 or 59 (in the case of being subordinate to claim 59, both the user and the remittance business operator bear the burden). Has an edit authority identification information retention step (cc) that retains the edit authority identification information that identifies the edit authority that is the authority to edit the recurring payment date information and / and the worker identification information.
The contract-related information holding step (be) has an editing authority additional holding substep (bp) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information.
The recurring payment date information edit step (ap) is
Register and delete the retained recurring payment date information and / and worker identification information only to the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. Edit permission restriction substep (br) that sets restrictions so that editing including can be performed,
A method of operating a fixed date prepaid system, which is the computer according to claim 50. Has an edit authority identification information retention step (cc) that retains the edit authority identification information that identifies the edit authority that is the authority to edit the wage payment date information and / and the worker identification information.
The contract-related information holding step (be) has an editing authority additional holding substep (bp) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information.
Wage payment date information retention The wage payment date information held in step (bm),
A claim having a wage payment date information editing step (bs) that allows editing, including registration and deletion, only to the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. Item 58. The method of operating a fixed date prepayment system, which is the computer according to item 58. The time information acquisition step (ae) for acquiring time information for prepaid processing, which will be described later,
Withdrawal processing execution reservation date information acquisition step (bt) to acquire withdrawal processing execution reservation date information, which is information indicating the execution date of withdrawal processing, which is the processing of withdrawal of money etc. by advance payment from the user,
Have,
The prepayment processing step (ax) specifies the withdrawal process with the withdrawal processing execution reservation date information based on the acquired withdrawal processing execution reservation date information and the time information acquired by the time information acquisition step (ae). Operation of a fixed date prepayment system, which is the computer according to any one of claims 52 to 62, having a withdrawal execution processing substep (bw) that processes the withdrawal processing to be executed on the date to be executed. Method. Recurring payment processing or / or recurring payment processing performed by the employer in association with the employer identification information to the employee or worker identified by the employee identification information or worker identification information associated with the employer identification information. And the deposit information acquisition step (bx) to acquire the deposit information for prepaid processing,
A payment processing amount information acquisition step (by) for acquiring payment processing amount information, which is information indicating the amount of payment processing to be executed by the repetitive payment processing step (ag) and / and the prepaid processing step (ax).
Payment processing execution judgment rule holding step (bz) that holds the payment processing execution judgment rule, which is a rule for judging whether to execute the payment processing to be executed based on the acquired payment processing amount information and the deposit information. ,
Further, a payment processing execution judgment step (ca) for determining whether payment processing should be executed based on the retained payment processing execution judgment rule, the retained deposit information, and the acquired payment processing amount information. A method of operating a fixed date prepayment system, which is the computer according to any one of claims 10 to 18 or 47 to 63. Recurring payment processing or / or recurring payment processing performed by the employer in association with the employer identification information to the employee or worker identified by the employee identification information or worker identification information associated with the employer identification information. And has a deposit information acquisition step (bx) to acquire deposit information for prepaid processing
The salary receivable information acquisition step (ab) or labor receivable information acquisition step (be), or / and the prepaid amount acquisition step (at) are based on the acquired deposit information and salary receivable information or / and labor receivable information. Acquire all or part of the payable consideration that is the payable consideration to the subordinates and / and workers before the salary payment date or wage payment date specified with the employer. The method of operating a fixed date prepayment system, which is the computer according to any one of claims 10 to 18 or 47 to 63, having a sub-step (cb). Receives employer identification information that identifies the employer who pays the payable consideration based on the labor claim information to the worker identified by the worker identification information, and payable consideration based on the labor claim information. A contract-relationship information retention step (be) that retains contract-relationship information, which is information that identifies a worker who is a person and is information that is associated with each other based on a contractual relationship.
All or part of the payable consideration, which is the consideration that can be paid to the worker before the wage payment date determined with the employer based on the worker's labor claim information, is used as the worker identification information of the worker. The labor claim information acquisition step (bf) acquired based on the associated employer identification information, and
Repeated payment of all or part of the payable consideration paid to the worker based on the labor claim information Repeated payment date information that determines the repeated payment date is retained in association with the worker identification information. Payment date information retention step (ac),
The payment method identification information acquisition step (ad) for acquiring the payment method identification information, which is the information for identifying the payment method for all or part of the payable consideration, in association with the worker identification information,
Time information acquisition step (ae) to acquire time information including date,
The repeat payment date relationship judgment step (af) for determining whether the acquired time information has a predetermined relationship with the repeat payment date defined in the repeat payment date information associated with the worker identification information, and
If the judgment result in the recurring payment date relationship judgment step (af) is the judgment result that the repetitive payment date has a predetermined relationship, the payment method identification information acquired in association with the employee identification information is used. A recurring payment processing step (ag) that performs payment processing, which is the processing for payment of all or part of the payable consideration by the identified payment method.
The recurring payment processing history retention step (ah), which retains the payment processing history in the recurring payment processing step (ag) in association with the worker identification information,
An operation program written readable and executable in a fixed date prepaid system that is a computer that has. The payment method identification information retention step (aj), which retains multiple payment method identification information, and
A payment method selection acceptance step (ak) that accepts one or more selections of payment method identification information that is held in association with the worker identification information, and
A payment method payment consideration allocation step (am) that allocates all or part of the payable consideration to one or more payment method identification information selected in association with the worker identification information.
Have more
The payment method identification information acquisition step (ad) is read into a fixed date prepayment system, which is the computer according to claim 66, which is configured to acquire the payment method identification information for which the selection has been accepted in association with the worker identification information. An action program written executable. It further has a remittance-specific information holding step (an) that holds the worker identification information, the payment method identification information, and the remittance-specific information used for the payment method identified by the payment method identification information in association with each other. An operating program readable and executable in a fixed date prepayment system, which is the computer according to claim 66 or 67. Claims 66 to 66 further include a recurring payment date information editing step (ap) for editing the recurring payment date information and / and the worker identification information held in the recurring payment date information retention step (ac). An operating program readable and executable in a fixed date prepayment system, which is the computer according to any one of 68. Any one of claims 66 to 69 further comprising a recurring payment date information recording step (ar) for recording recurring payment date information and / and worker identification information in the recurring payment date information holding unit (AC). An operating program written readable and executable in a fixed-date prepayment system, which is the computer described in. The start processing request acquisition step (as), which acquires the start processing request for the wage prepayment request in association with the worker identification information,
Start processing request time information acquisition step (cd) to acquire time information including the date when the start processing request was acquired, and
Labor receivable information associated with worker identification information, recurring payment date information associated with worker identification information, if available, and recurring payment date information associated with worker identification information, if available. The prepayable amount acquisition step (at) to obtain the prepayable amount, which is the amount that allows the prepayment request based on all or part of the payable consideration paid on the payment date.
The prepayment request amount acquisition step (aw) to acquire the prepayment request amount in association with the worker identification information within the range that does not exceed the prepayment possible amount, and
The prepaid processing step (ax) for prepaid processing, which is the processing for prepaid the acquired prepaid request amount,
The prepaid history holding step (ay), which holds the prepaid history, which is the history of the prepaid processing in the prepaid processing step (ax), in association with the worker identification information,
An operating program readable and executable in a fixed date prepaid system, which is the computer according to any one of claims 66 to 70. The processing result acquisition step (az) of acquiring the processing result which is the result of the payment processing in the recurring payment processing unit (AG) or the prepaid processing in the prepaid processing unit (AX) in association with the worker identification information,
The SNS identification information holding step (ba), which holds the SNS identification information used by the worker in association with the worker identification information,
A processing result notification step (bb) that notifies the processing result via the SNS identified by the SNS identification information associated with the worker identification information associated with the processing result, and
An operating program readable and executable in a fixed date prepaid system, which is the computer according to any one of claims 66 to 71. The remittance unique information holding step (an) is a remittance SNS identification information holding sub-step that holds the worker identification information, the payment method identification information, the remittance unique information, and the remittance SNS identification information in association with each other. A program readable by a fixed date prepayment system, which is a computer according to claim 69 to 72, which is subordinate to claim 68 having (bc). The labor claim information acquisition step (bf) is a fixed amount acquisition substep (bd) that acquires information indicating a fixed amount as all or part of the payable consideration paid to the worker acquired in association with the worker identification information. 66 to 73, the operation program readable and executable in the fixed date prepayment system, which is the computer according to any one of claims 73. Payment processing approval / disapproval step () to determine whether all or part of the payable consideration associated with the worker identification information is less than the prescribed amount and the Recurring Payment Processing Department (AG) can process the full amount. bg) and
Notify the worker or / and the employer of payment processing abnormality information indicating that payment processing cannot be performed when the judgment result in the payment processing approval / disapproval judgment step (bg) (is the judgment result that payment processing cannot be performed. The payment processing anomaly information notification step (bh) is readable and executable in a fixed date prepayment system, which is the computer according to any one of claims 19 to 27 or 66 to 74 having a payment processing anomaly information notification step (bh). Operation program. The prepaid request amount acquisition step (aw) is
Assuming that the prepayment request amount acquired in the prepayment request amount acquisition step (aw) has been processed, it is stipulated that the payment is already made on the prepayment payment date closest to the user. When the judgment result in the fixed amount payment approval / disapproval judgment substep (bj) and the fixed amount payment approval / disapproval judgment substep (bj) to judge whether or not the fixed amount cannot be paid is the judgment result that the payment cannot be made.
The prepaid request amount acquisition substep (bk), which is the prepaid request amount obtained by reducing the total amount paid to the worker to the amount that can be paid the fixed amount,
An operating program readable and executable in a fixed date prepaid system, which is the computer according to claim 74 that is subordinate to claim 71. A wage payment date information retention step (bm) that retains wage payment date information, which is information indicating a predetermined wage payment date in association with worker identification information and / and employer identification information, and
The amount paid by recurring payment and / or prepaid processing that occurred by the predetermined closing date on the prescribed wage payment date held with the employer based on the worker's labor claim information. Make all or part of the payable consideration, which is the payable consideration excluding the prepayment request amount from the wages that would have been paid in the absence of these recurring payments or prepayments, so that it is payable. The balance payment processing step (bn) for processing the balance payment, which is the processing for payment, and
An operating program readable and executable in a fixed date prepaid system, which is the computer according to any one of claims 66 to 76. When the balance payment processing step (bn) for processing the balance requires a fee for the remittance means used as the payment method for processing the balance, the user is required to pay the fee (slip processing). The fixed date prepayment system, which is the computer according to claim 77, having a user-paid check processing step (ce) that includes both an electronic check and a check made of an actual sheet. An operation program written so that it can be read and executed. When the balance payment processing step (bn) for processing the balance requires a fee for the remittance means used as the payment method for processing the balance, the remittance operator pays the fee. (In claim 78 or claim 78) having a remittance operator-paid voucher processing step (cf) (which may include both an electronic voucher and a voucher made of an actual sheet; the same shall apply hereinafter). An operation program that can be read and executed by the fixed-date prepayment system, which is the computer described in (Both the user and the remittance operator bear the burden if subordinate). Has an edit authority identification information retention step (cc) that retains the edit authority identification information that identifies the edit authority that is the authority to edit the recurring payment date information and / and the worker identification information.
The contract-related information holding step (be) has an editing authority additional holding substep (bp) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information.
The recurring payment date information edit step (ap) is
Register and delete the retained recurring payment date information and / and worker identification information only to the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. Edit permission restriction substep (br) that sets restrictions so that editing including can be performed,
An operating program readable and executable in a fixed date prepaid system, which is the computer according to claim 69. Has an edit authority identification information retention step (cc) that retains the edit authority identification information that identifies the edit authority that is the authority to edit the wage payment date information and / and the worker identification information.
The contract-related information holding step (be) has an editing authority additional holding substep (bp) that holds the worker identification information and / and the employer identification information to be held in association with the editing authority identification information.
Wage payment date information retention The wage payment date information held in step (bm),
A claim having a wage payment date information editing step (bs) that allows editing, including registration and deletion, only to the person (employer or / and worker) identified by the identification information associated with the editing authority identification information. An operating program readable and executable in a fixed date prepayment system, which is the computer according to item 77. The time information acquisition step (ae) for acquiring time information for prepaid processing, which will be described later,
Withdrawal processing execution reservation date information acquisition step (bt) to acquire withdrawal processing execution reservation date information, which is information indicating the execution date of withdrawal processing, which is the processing of withdrawal of money etc. by advance payment from the user,
Have,
The prepayment processing step (ax) identifies the withdrawal process with the withdrawal processing execution reservation date information based on the acquired withdrawal processing execution reservation date information and the time information acquired by the time information acquisition step (ae). Read to a fixed date prepayment system, which is the computer according to any one of claims 71 to 81, having a withdrawal execution processing substep (bw) that processes the withdrawal processing to be executed on the date to be executed. An action program written executable. Recurring payment processing or / or recurring payment processing performed by the employer in association with the employer identification information to the employee or worker identified by the employee identification information or worker identification information associated with the employer identification information. And the deposit information acquisition step (bx) to acquire the deposit information for prepaid processing,
A payment processing amount information acquisition step (by) for acquiring payment processing amount information, which is information indicating the amount of payment processing to be executed by the repetitive payment processing step (ag) and / and the prepaid processing step (ax).
Payment processing execution judgment rule holding step (bz) that holds the payment processing execution judgment rule, which is a rule for judging whether to execute the payment processing to be executed based on the acquired payment processing amount information and the deposit information. ,
Further, a payment processing execution judgment step (ca) for determining whether payment processing should be executed based on the retained payment processing execution judgment rule, the retained deposit information, and the acquired payment processing amount information. An operation program readable and executable in a fixed date prepayment system, which is the computer according to any one of claims 19 to 27 or 66 to 82. Recurring payment processing and / and prepayment processing performed by the employer in association with the employer identification information to the worker identified by the employee identification information or worker identification information associated with the employer identification information. Has a deposit information acquisition step (bx) to acquire deposit information for
The salary receivable information acquisition step (ab) or labor receivable information acquisition step (be), or / and the prepaid amount acquisition step (at) are based on the acquired deposit information and salary receivable information or / and labor receivable information. Acquire all or part of the payable consideration that is the payable consideration to the subordinates and / and workers before the salary payment date or wage payment date specified with the employer. An operating program readable and executable in a fixed date prepayment system, which is the computer according to any one of claims 19 to 27 or 66 to 82 having a substep (cb).

Images