JP2022102727A - Information processing device, information processing method, and program - Google Patents

Abstract

To provide an information processing device capable of avoiding concentration of processing load in a service in which equivalents of a part of a salary can be periodically received at a timing specified by a user before a salary payment date, an information processing method, and a program.SOLUTION: In an information processing system 1, a server device 10 is connected to each of employer terminals 20 and user terminals 30 via a communication network such as Internet. The server device receives an application including designation of payment time periodically arriving as an application of advance payment of a money amount corresponding to a salary from a worker, identifies the payment date determined according to the payment time on the basis of the application, generates and records advance data containing information of the payment date, and performs payment processing according to the application on the basis of the recorded advance data.SELECTED DRAWING: Figure 2

Description

The present invention relates to an information processing apparatus, an information processing method, and a program.

In recent years, a service has been considered that allows workers (employees who receive salary as compensation for labor) to receive an amount equivalent to a part of their salary before the predetermined salary payment date. (See, for example, Patent Document 1).

Japanese Unexamined Patent Publication No. 2007-328748

When a user (worker) uses a service as described above, it may be troublesome to apply each time he / she tries to receive payment equivalent to salary. Therefore, a regular payment service is conceivable in which a payable amount is periodically paid to a designated payee according to the work performance of the user at a timing designated in advance by the user. When realizing such a service, the payment process in which the payment amount is fixed and actually transferred is usually executed on the day of payment. However, it is not always clear when the payment date will be depending on the method of specifying the payment time at the time of application. Therefore, on the day of payment, it is necessary to determine whether the day is the payment date, and if it is the payment date, perform the process of actually making the payment. However, if all such processes are executed at once, the processing load of the system may increase.

The present invention has been made in consideration of the above circumstances, and one of the purposes thereof is to be able to periodically receive a part of the salary at a timing specified by the user before the salary payment date. The purpose of the service is to provide an information processing device, an information processing method, and a program capable of avoiding concentration of processing load.

The information processing device according to one aspect of the present invention is an application receiving unit that accepts applications for advance payment of salary equivalent from workers, and an application receiving unit that accepts applications including designation of payment timing that arrives regularly. Based on the application, the pre-data generation unit that specifies the payment date determined according to the payment time and generates and records the pre-data including the payment date information, and the pre-data generation unit that is recorded on the payment date. It is characterized by including a payment processing unit that executes payment processing according to the application based on the prior data.

In one aspect of the present invention, the advance data generation unit generates advance data including information on the payment date when the payment date determined according to the payment time is included in a given generation target period. It is characterized by doing.

Further, in one aspect of the present invention, the pre-data generation unit is characterized in that the process of generating the pre-data is executed at an execution frequency corresponding to the generation target period.

Further, in one aspect of the present invention, the advance data generation unit is characterized in that the process of generating the advance data is executed at an execution frequency according to the free space of the database for recording the advance data. ..

Further, in one aspect of the present invention, the advance data generation unit is characterized in that it executes a process of generating the advance data at a different execution frequency for each employer who pays the worker. ..

Further, in one aspect of the present invention, the advance data generation unit is characterized in that the process of generating the advance data is executed at a different execution frequency for each worker.

Further, in one aspect of the present invention, the advance data generation unit is characterized in that each time the application is accepted, the process of generating the advance data is executed based on the application.

Further, the information processing apparatus according to one aspect of the present invention obtains the upper limit amount that can be paid to the worker as a prepayment of the salary equivalent amount, which is calculated based on the work data including the actual working hours of the worker. The payment processing unit further includes an upper limit acquisition unit, and is characterized in that the payment processing unit executes payment processing according to the application when the payment amount to be paid in response to the application is equal to or less than the upper limit amount.

Further, in one aspect of the present invention, the application received by the application receiving unit is based on work data including the payment amount and the actual working hours of the worker as a method of determining the amount to be paid when the payment time comes. When the advance data generation unit generates the advance data in advance, including the designation of one of the ratio to the upper limit that can be paid to the worker as a prepayment of the salary equivalent amount calculated based on the above. It is characterized in that the advance data is generated for the application including the designation of the payment amount, and the advance data is not generated for the application including the designation of the ratio to the upper limit amount.

Further, the information processing apparatus according to one aspect of the present invention further includes a scheduled payment date providing unit that provides information on a scheduled payment date based on the worker's application in response to a provision request from the worker. The payment scheduled date providing unit is characterized in that the payment schedule information for which the advance data has been generated is provided with reference to the advance data.

Further, in one aspect of the present invention, when the ungenerated period in which the prior data has not been generated is included in the target period of the provision request, the prior data generation unit targets the ungenerated period and the prior data. Is executed, and the scheduled payment date providing unit is characterized in that it provides information on the scheduled payment date acquired by referring to the prior data generated for the ungenerated period.

Further, the information processing method according to one aspect of the present invention is a step in which the application reception unit accepts an application for advance payment of an amount equivalent to salary from a worker, and accepts an application including designation of a payment time that arrives regularly. A step, a step in which the advance data generation unit identifies a payment date determined according to the payment time based on the application, and generates and records advance data including information on the payment date, and a payment processing unit. However, the payment date includes a step of executing a payment process according to the application based on the recorded prior data.

Further, the program according to one aspect of the present invention is a step of accepting an application for prepayment of an amount equivalent to salary from a worker, and a step of accepting an application including designation of a payment time that arrives regularly, and based on the above application. A step of specifying a payment date determined according to the payment time, generating and recording advance data including information on the payment date, and the payment date based on the recorded advance data. It is a program to make a computer execute a step to execute payment processing according to an application. This program may be provided stored in a computer-readable, non-temporary information storage medium.

It is a block diagram which shows the structure of the information processing apparatus which concerns on embodiment of this invention. It is a functional block diagram which shows the function of the information processing apparatus which concerns on embodiment of this invention. It is a figure which shows an example of an input screen. It is a figure which shows an example of the prior data. It is a figure which shows an example of the flow of the advance data generation processing. It is a figure which shows an example of the flow of payment processing using advance data. It is a figure which shows an example of the payment schedule display screen.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing an overall outline of an information processing system 1 including an information processing apparatus according to an embodiment of the present invention. As shown in the figure, the information processing system 1 includes a server device 10 functioning as an information processing device according to an embodiment of the present invention, an employer terminal 20, and a user terminal 30. ing. The server device 10 is connected to each of the employer terminal 20 and the user terminal 30 via a communication network such as the Internet.

The information processing system 1 realizes a prepayment service equivalent to salary. In this service, a worker employed by an employer (company, etc.) receives a part of the salary that he / she is entitled to pay as compensation for labor before the predetermined salary payment date. It is a service that can be done.

The server device 10 is an information processing device such as a server computer, and is managed by the provider of this service. As shown in FIG. 1, the server device 10 includes a control unit 11, a storage unit 12, and a communication unit 13.

The control unit 11 is configured to include at least one processor, and executes various information processing according to a program stored in the storage unit 12. A specific example of the processing executed by the control unit 11 will be described later.

The storage unit 12 includes at least one memory device such as a RAM, and stores a program executed by the control unit 11 and data to be processed by the program. In particular, in the present embodiment, it is assumed that the storage unit 12 stores the database D in which various data necessary for providing the service is stored. The contents of the data stored in the database D will be described later.

The communication unit 13 is an interface for connecting to a communication network wirelessly or by wire. The server device 10 is connected to the employer terminal 20 and the user terminal 30 so as to be capable of data communication by the communication unit 13.

The employer terminal 20 is an information processing device used by the employer, and may be a personal computer or the like. The employer periodically provides the worker's work data to the server device 10 using the employer terminal 20. It should be noted that the person who actually operates the employer terminal 20 to provide the work data is generally not the employer himself but a person who has received instructions from the employer (for example, a person in charge of labor of the company). In the following, these persons are collectively referred to simply as employers.

The user terminal 30 is an information processing device used by a user (worker) of a service realized by the information processing system 1, and may be a stationary device such as a desktop computer, or a smartphone or tablet. It may be a portable device such as.

A display device 31 and an operation device 32 are connected to the user terminal 30. The display device 31 is a liquid crystal display, an organic EL display, or the like, and displays various screens drawn by the user terminal 30. The operation device 32 is a keyboard, a mouse, a touch panel, or the like, and receives an operation input from the user and outputs an operation signal indicating the content to the user terminal 30. The display device 31 and the operation device 32 may be separate devices connected to the user terminal 30 by wire or wireless communication, or may be a device built in the housing of the user terminal 30. May be good. By operating the operation device 32 while viewing the screen displayed by the display device 31, the user of this service makes an advance payment application for a salary equivalent amount from the user terminal 30 to the server device 10.

Hereinafter, the functions realized by the server device 10 in the present embodiment will be described with reference to the functional block diagram of FIG. As shown in FIG. 2, the server device 10 functionally includes a work data acquisition unit 51, an upper limit acquisition unit 52, an application reception unit 53, a pre-data generation unit 54, a payment processing unit 55, and a payment schedule. It is configured to include the day provision unit 56. These functions are realized by the control unit 11 executing a program stored in the storage unit 12. This program may be provided to the server device 10 via a communication network such as the Internet, or may be stored in a computer-readable information storage medium such as an optical disk and provided to the server device 10.

The work data acquisition unit 51 acquires work data transmitted from the employer terminal 20 and stores it in the storage unit 12. The work data includes work record data showing the total working hours actually worked by the user in the past predetermined period for each user of the service employed by the employer. In addition, data on scheduled working hours (scheduled working data) indicating how long the user was scheduled to work in the past may be included. When a plurality of types of working hours having different hourly unit prices are included in the total working hours such as overtime hours, the working record data may include data indicating the working hours for each hourly unit price.

The Employer shall periodically, for example, daily or once a week, send the work data up to that point for each of the users of the Service that he / she employs. The work data transmitted by the employer may include only the data on the work performance since the previous transmission, or may include the data on all the work performance since the previous salary closing date.

The upper limit acquisition unit 52 acquires the maximum payable amount for each user of this service. The maximum payable amount acquired by the maximum amount acquisition unit 52 is an amount calculated based on the work data acquired by the work data acquisition unit 51, and the user of this service has applied for advance payment of the salary equivalent amount. The maximum amount that can be paid if. In the present embodiment, the upper limit acquisition unit 52 itself calculates the upper limit of payable amount of each user by using the work record data included in the work data acquired by the work data acquisition unit 51, so that the upper limit of payment is possible. The amount shall be obtained. Further, the upper limit acquisition unit 52 stores the acquired data of the maximum payable amount of each user in the storage unit 12.

Specifically, for example, the upper limit acquisition unit 52 is paid at the next salary payment according to the working hours up to that point by multiplying the past total working hours of each user by a predetermined hourly unit price. Calculate the estimated salary. Then, the maximum payable amount is calculated by multiplying the calculated planned salary by a given safety factor (for example, 70%). The information on the hourly unit price may be provided by the employer in advance and stored in the storage unit 12, or may be included in the work data together with the information on the working hours and provided. .. Here, the safety factor is a value of 100% or less, and may be a value arbitrarily determined by the service provider or the employer. In addition, the past total working hours of each user is the total value of working hours subject to salary payment after the start date of the aggregation target period. This working time may include the time actually worked by the worker, as well as the time corresponding to the paid leave for which the salary is paid. In addition, if the total working hours of the user include multiple types of hours with different labor unit prices (normal working hours, overtime hours, etc.), multiply each hour by the corresponding labor unit price before adding up. May calculate the planned salary amount.

Here, the aggregation target period is a target period of work performance used for calculating the maximum payable amount, and may be a period such as one month. This period should correspond to the reference period for employers to calculate salaries. Specifically, the aggregation target period is set so that the employee's monthly salary closing date is the last day of the aggregation target period. In this case, the upper limit acquisition unit 52 decides to switch the aggregation target period at a predetermined timing after the salary closing date (for example, the day after the salary closing date) every month, and the payment calculated based on the work data acquired so far at that timing. Reset the maximum possible amount to 0 yen. After that, based on the newly acquired work data for the next aggregation target period, the maximum payable amount to be used when the next receipt application is made is calculated.

Further, when the payment processing unit 55, which will be described later, processes the payment equivalent to the salary to the user within the current aggregation target period, the maximum amount acquisition unit 52 can pay the maximum amount that can be paid by deducting the payment amount. To update. As a result, when the payment processing unit 55 processes payments to the user multiple times within one aggregation target period, the total amount of money paid over the multiple payments is based on the total working hours within the aggregation target period. It is possible not to exceed the maximum payable amount.

The upper limit acquisition unit 52 may update the payable upper limit using the latest work record data each time the work data acquisition unit 51 acquires new work data from the employer terminal 20. Alternatively, the maximum payable amount may be updated by using the work record data acquired so far on a regular basis such as daily or weekly. Further, the maximum payable amount at that time may be acquired at the timing when the information on the maximum payable amount is required, such as the timing when the payment process is executed by the payment processing unit 55, which will be described later.

The application reception unit 53 receives an application for receiving an amount equivalent to salary from a user of this service. In particular, in this embodiment, the user can apply for regular payment. Regular payment is a service that allows you to receive payment equivalent to your salary at the time of payment that arrives on a regular basis.

Hereinafter, the information specified by the user when the application reception unit 53 accepts the application for regular payment from the user will be described. At least, when accepting a regular payment application, the application receiving unit 53 accepts the designation of the payment time from the user. The payment time is a time when the payment arrives repeatedly at a predetermined cycle, for example, the 10th day of every month, the third Friday of every month, or the last day of every month. The cycle in this case may be the same period as the aggregation target period used for calculating the above-mentioned upper limit of payable amount. The application receiving unit 53 may accept a plurality of payment timing designations that are different from each other.

Further, the application receiving unit 53 receives from the user the designation of the amount (application amount) desired to be paid when the payment time comes from the user. Here, the application reception unit 53 shall receive information from the user that directly specifies the amount to be paid in one payment.

Further, the application reception unit 53 receives information on the payment destination of the regular payment from the user. The payment method in this service may be a method selected by the user from a plurality of predetermined methods such as transfer to a bank account and charge to electronic money. The payment destination information is information that identifies the payment method desired by the user and the payment destination by the payment method (for example, an account number in the case of an account transfer).

Further, the application receiving unit 53 may accept from the user the designation of the payment start time and the payment end time of the regular payment. The payment start time and payment end time may be specified by the year, month, or date, respectively, and this information specifies the period for executing the periodic payment to the user. The user may not specify one or both of the payment start time and the payment end time. If the user does not specify the payment start time, the regular payment will be started immediately when the service can start the regular payment to the user, for example, the next day or later. If the payment end time is not specified, the regular payment may be continued until the user instructs the end of the regular payment again. Alternatively, a predetermined default payment end time (for example, one year after the application date) may be specified in this service.

FIG. 3 is a diagram showing an example of an application content input screen. In this figure, the prepaid applicable amount indicates the maximum payable amount acquired by the maximum amount acquisition unit 52 at the time of application, the scheduled monthly receipt date indicates the payment time, and the receiving method indicates the payee. As for the expected receipt date, multiple dates can be selected within the range of one month. It is also possible to specify the application amount, payment start time, and payment end time.

This input screen is displayed on the display device 31 in response to a request operation performed by the user on the operation device 32 connected to the user terminal 30. In the state where such an input screen is displayed, the user performs an operation input for designating information such as one or a plurality of payment timings, application amounts, and payment methods. Then, by performing the periodic payment application operation, the application data including the designated information is transmitted from the user terminal 30 to the server device 10.

The presentation of such an input screen may be realized by a web service or the like. In this case, the application receiving unit 53 transmits HTML data and Javascript data necessary for drawing a web page of the input screen as input screen drawing data in response to the HTTP request transmitted from the user terminal 30. The browser program of the user terminal 30 draws an input screen by rendering a web page using the input screen drawing data received from the server device 10, and causes the display device 31 to display the input screen.

The application reception unit 53 does not accept the application for regular payment received from the user as it is, but once notifies the employer terminal 20 of the contents of the receipt application, and the employer operates the employer terminal 20. The content of the application may be accepted only when the intention to accept the content of the application is indicated.

Each time the application reception unit 53 receives a new periodic payment application from the user, the application reception unit 53 stores data indicating the application content (hereinafter referred to as application data) in the application data table in the database D. As a specific example, the application data table stores an application for regular payment by one user as application data of one record. The application data for one record is for the identification information (user ID, etc.) of the user who made the application, the identification information (company ID, etc.) of the employer who employs the user, the payment time, the application amount, and the payment. It is the data associated with the information of the destination, the payment start time, and the payment end time. The payment timing information included in this application data indicates the rules for determining the payment date (1st of each month, 3rd Friday of each month, last day of each month, etc.) as described above, and the payment date. It is not data that directly indicates the actual date.

If a user once applies for a regular payment and then changes the payment timing and other details to apply for a new regular payment, the application reception unit 53 will display the application data table in relation to the user. Update the stored application data with the newly applied contents.

The advance data generation unit 54 generates advance data based on the content of the periodic payment application received by the application reception unit 53 and stores it in the advance data table in the database D. This prior data is information in which the user's identification information, payment date, payment destination, and payment amount are related to each other. Preliminary data may also include payment completion status information indicating whether or not the payment was actually made. Each record in the pre-data table corresponds to a single payment process. That is, a plurality of independent records are generated for a plurality of payment processes performed on the same user.

In the present embodiment, the advance data generation unit 54 periodically executes the advance data generation process for the payment to be executed in the predetermined generation target period. For example, the pre-data generation unit 54 executes the pre-data generation process once a month with one month from the day following the day when the process is executed to the execution date of the next pre-data generation process as the generation target period. FIG. 4 shows an example of prior data stored in the prior data table. In the example of this figure, it is assumed that the user A specifies the first Friday and the third Friday as the payment time twice a month, and the advance data generation unit 54 sets one month in December 2020 as the generation target period. Shows an example of the prior data generated in. In this case, the payment dates for which regular payments should be made to User A within the generation target period are December 4th on the first Friday and December 18th on the third Friday, so these two payment processes are supported. Two records are generated.

Hereinafter, an example of the flow of the prior data generation process will be described with reference to the flow chart of FIG. First, the advance data generation unit 54 refers to the application data table and extracts application data whose payment date arrives within the generation target period (S1). Specifically, if the generation target period is included in the period between the payment start time and the payment end time included in the application data, and there is a date that matches the payment time during the generation target period, that Extract application data as a processing target. In particular, when the payment time is specified by the day of the week, such as the third Friday of every month or every Tuesday, the advance data generation unit 54 calculates how many days match the specified day of the week within the generation target period. There is a need to.

Subsequently, the advance data generation unit 54 generates advance data based on each of the application data extracted in S1 (S2). Specifically, the advance data generation unit 54 sets the payment date as the date matching the payment time included in the application data, the application amount included in the application data as the payment amount, and the payment destination included in the application data as the payment destination. Generate advance data. Then, the generated pre-data is stored in the pre-data table (S3). As described above, when there are a plurality of dates matching the payment time within the generation target period, the advance data generation unit 54 generates a plurality of records of advance data with each of them as the payment date.

In the above description, the advance data generation unit 54 will execute the advance data generation process for all users at a predetermined frequency, for example, once a month. However, the advance data generation unit 54 may execute the advance data generation process every time the application reception unit 53 accepts a new periodic payment application. In this example, when a new periodic payment application is received, the advance data generation unit 54 makes the application for the entire period from the payment start time to the payment end time specified in the application as the generation target period. Performs pre-data generation processing for the user who performed. If the advance data generation process is executed each time the application for regular payment is received in this way, it is not necessary to execute the advance data generation process for all users on a regular basis.

In addition, even if the advance data generation process is executed for all users on a regular basis, the initial payment to be made to that user depends on the timing when a new periodic payment application is received from the user. In some cases, the periodic pre-data generation process may not be in time. Therefore, when the application receiving unit 53 accepts a new periodic payment application, the advance data generation unit 54 is based on the periodic payment application newly received during the generation target period for which the advance data has already been generated by the past advance data generation process. You may decide if you need to pay. Then, if payment is required, the advance data may be generated and added to the advance data table.

By executing the pre-data generation process as described above with a period in the future from the process execution date as the generation target period, the server device 10 corresponds to the pre-data corresponding to each payment process at a timing earlier than the payment date arrives. Can be prepared and recorded. As a result, the server device 10 can reduce the amount of processing required to make an actual payment on the day of payment.

However, in order to prepare and record the preliminary data, the capacity of the database D is required accordingly. In particular, when the execution frequency of the advance data generation process is low, the generation target period becomes long and the number of advance data increases accordingly, so that the required capacity of the database D becomes larger. Therefore, the execution frequency of the advance data generation process needs to be determined according to the size of the capacity of the database D that can be secured, the number of payment processes, and the like. In the above example, the pre-data generation unit 54 decides to execute the pre-data generation process once a month on a monthly basis, but the frequency is different, such as weekly (once a week) or daily (once a day). You may execute the pre-data generation process with. Even when the pre-data generation process is executed on a daily basis, the pre-data for the next day is generated at a time when the processing load is relatively light, such as at night, at a timing before the payment date arrives. By executing the pre-data generation process, it is possible to reduce the concentration of the processing load.

In order to secure the capacity required for storing the advance data, the advance data generation unit 54 automatically executes a process of increasing the free capacity when the free capacity of the database D becomes less than a predetermined capacity. You may.

Further, the advance data generation unit 54 may dynamically change the execution frequency of the advance data generation process according to the free space of the database D. For example, when the pre-data generation process is executed monthly and the free space of the database D becomes less than or equal to the predetermined capacity, the pre-data generation unit 54 newly executes the pre-data generation process at the timing when the pre-data generation process should be executed next. The generation target period of the advance data generation process is changed to a period shorter than one month (for example, one week). As a result, the number of records of the pre-data generated in one pre-data generation process can be reduced. Instead, the next pre-data generation process needs to be executed before the generation target period in the previous pre-data generation process expires, such as one week later instead of one month later. That is, the advance data generation unit 54 shortens the execution cycle of the advance data generation process and increases the execution frequency. By dynamically changing the execution frequency of the pre-data generation process in this way, it is possible to adjust the number of records of the pre-data so as to avoid a state in which the capacity of the database D is insufficient.

The advance data generation unit 54 may change the execution frequency of the advance data generation process for each employer and / or for each user. As an example, the advance data generation unit 54 may determine the execution frequency of the advance data generation process according to the application rate of regular payment for each employee and the number of applicants. Employees who have contracts for this service usually employ multiple employees, and these employees will be registered as users of this service. However, not all employees use the regular payment service, and the actual number of employees who actually use this service varies from employee to employee. Then, as the number of users who actually apply for regular payment increases, the number of advance data also increases, and there is a high possibility that the capacity of the database D will be squeezed. Therefore, the advance data generation unit 54 calculates, for example, the application rate for each employer, and if the calculated application rate is equal to or higher than a predetermined ratio, the advance data generation process is executed for the user employed by the employer. Shorten the cycle. Here, the application rate is the percentage of users who are applying for regular payment to all users employed by the employer. Further, when the application rate is less than the predetermined ratio, the advance data may be generated with the entire period as the generation target period at the timing when the application reception unit 53 accepts the application for regular payment. Further, the execution frequency of the advance data generation process for each employer may be determined based on the absolute value of the number of applicants instead of the application rate.

Further, the advance data generation unit 54 may change the execution frequency of the advance data generation process for each user based on the content of the application for the periodic payment for each user. For example, when a new periodic payment application is accepted, if the period determined by the payment start time and payment end time specified in the application is shorter than the predetermined period, the capacity of the database D is not required so much. Therefore, the advance data generation unit 54 may increase the execution frequency of the advance data generation process. Specifically, for example, when the period of the periodic payment specified by the user is shorter than the predetermined period, the advance data generation unit 54 generates advance data using the entire period specified at the time when the application is accepted as the generation target period. The process may be executed. Further, when the number of payments within one aggregation target period specified by the payment time becomes a predetermined number or more, the advance data generation unit 54 may reduce the execution frequency of the advance data generation process. According to such control, while keeping the state in which the capacity shortage of the database D is unlikely to occur, the advance data is generated in advance for a long period of time for the employer or the user who has a relatively small number of advance data to be generated. Can be left.

The payment processing unit 55 processes payment of an amount equivalent to salary according to the application contents received by the application reception unit 53. In particular, in the present embodiment, when the advance data is generated in advance, the payment processing unit 55 generates data for payment processing (hereinafter referred to as payment processing data) using the advance data. Then, individual payment processing is executed according to the generated payment processing data.

In the present embodiment, the payment processing unit 55 executes payment processing to be paid on that day on a daily basis. That is, the payment processing unit 55 executes the payment processing once a day with the day of the execution as the processing target day. Hereinafter, an example of the flow of payment processing executed by the payment processing unit 55 will be described with reference to the flow chart of FIG.

First, the payment processing unit 55 extracts the advance data whose payment date is the processing target date (current day) from the advance data table (S11). As mentioned above, the pre-data is stored in the pre-data table as one record for each day when payment should be made. Therefore, by simply performing the record extraction process using the processing target date as the key, the payment processing unit 55 can easily extract the record to be processed on that day from the advance data table.

However, the advance data is data generated before the payment date, and at the time of generation, it is not determined whether or not payment can actually be made according to the work record. Therefore, the payment processing unit 55 determines whether or not payment can actually be made with respect to the extracted pre-data record. Specifically, the payment processing unit 55 determines whether the payment amount included in the prior data is equal to or less than the payable upper limit amount acquired by the upper limit amount acquisition unit 52 (S12). As a result of the determination, if the payment amount is equal to or less than the payable upper limit, the payment processing is continued, but if the payment amount exceeds the payable upper limit, the payment processing of the record is stopped (S13). Here, if the payment amount exceeds the payable upper limit, the payment process itself is canceled, but the payment process may be continued with the payable upper limit as the actual payment amount.

Subsequently, the payment processing unit 55 acquires information on the payment source for the advance data determined to be payable in S12 (S14). It is assumed that the information of the payment source is the information of the account in which the employer prepares the source of payment, and is stored in the storage unit 12 in advance in association with the identification information of the employer. After that, the payment processing unit 55 generates transfer data using the advance data extracted in S11 and the payment source information acquired in S14 (S15). Then, a transfer instruction is given based on the generated transfer data (S16). This is a process of requesting the financial institution of the payment source to execute the transfer process of transferring the payment amount to the payment destination specified by the user. When the transfer process based on this transfer instruction is completed normally, the payment processing unit 55 updates the payment completion status to the "completed" state for the corresponding advance data record extracted in S11 (S17).

When the processing from S12 to S17 is completed for all the advance data records extracted in S11, the payment processing unit 55 ends the payment processing for that day. The payment process was not completed normally, such as a record in which the maximum payable amount was determined to be insufficient in S12 and the payment process was canceled in S13, or a record in which the transfer process in response to the instruction in S16 failed. If the advance data exists, the payment processing unit 55 may execute error processing such as notifying the user of the payment failure. Further, the advance data whose payment completion status is not updated to "completed" by the payment processing may be extracted again at a predetermined timing, and the payment processing may be retried.

When the scheduled payment date providing unit 56 receives a request for providing the scheduled payment date from the user, the scheduled payment date providing unit 56 provides the information on the scheduled payment date to the requesting user. The provided scheduled payment date information is displayed on the screen of the display device 31 connected to the user terminal 30. The request for payment on the scheduled payment date shall include information that specifies the period covered by the payment. Scheduled payment date The provision unit 56 identifies a scheduled payment date that arrives within the designated provision target period, and transmits the information to the requesting user terminal 30.

FIG. 7 shows an example of a payment scheduled date display screen that displays information on the scheduled payment date. In this example, the scheduled payment date display screen can display the scheduled payment date for each month in a calendar format, and the payment date determined by the user's application content is highlighted so that it can be distinguished from other days. There is. Each time the user performs an operation of switching the display month, the user terminal 30 transmits a new provision request with the provision target period of one month after the switching to the server device 10. Specifically, in the example of FIG. 7, the calendar for December 2020 is displayed on the screen as the provision target period, and December 4th and December 18th are shaded as payment dates.

Scheduled payment date When the provision target period specified by the provision request includes the generation target period (hereinafter referred to as the generation period) of the pre-data generation process that has been executed in the past, the provision unit 56 is within the generation period. The estimated payment date will be specified by referring to the prior data. If the advance data has been generated, the payment date has already been specified for the generation target period. Therefore, by referring to the advance data table, the scheduled payment date providing unit 56 does not need to perform a calculation for specifying the scheduled payment date again using the application data, and it can be easily generated within a relatively short time. Information on the scheduled payment date can be acquired and provided to the user terminal 30.

On the contrary, when the period for which the advance data has not been generated (hereinafter referred to as the ungenerated period) is specified as the provision target period, the scheduled payment date provision unit 56 refers to the application data stored in the application data table. It is necessary to identify the expected payment date that will arrive within the ungenerated period. In order to specify the scheduled payment date, the advance data generation unit 54 specifies the payment time based on the payment timing information included in the application data in the same manner as when the advance data is generated. Therefore, when the provision request of the scheduled payment date including the ungenerated period as the provision target period is received, the advance data generation unit 54 may execute the advance data generation process with the ungenerated period as the generation target period. Then, the scheduled payment date providing unit 56 provides the user terminal 30 with information on the scheduled payment date newly specified by the pre-data generation process of the ungenerated period. With such control, it is possible to avoid duplicating the process of specifying the payment date for the same period.

When such control is performed, the generated period or the ungenerated period is generated for each user depending on whether or not each user has requested the provision of the scheduled payment date, and for which provision target period the provision request has been made. The period will be different. Therefore, the advance data generation unit 54 shall record in the database D information that specifies the generated period for each user. Scheduled payment date The provision unit 56 determines whether or not the provision target period includes an ungenerated period by referring to the information of the generated period, and if so, generates advance data about the ungenerated period. Is requested from the advance data generation unit 54. On the contrary, if the provision target period includes the generated period, the estimated payment date within the generated period is immediately obtained by referring to the advance data table.

As explained above, if the advance data generation process for the ungenerated period is executed when the request for provision of the scheduled payment date is received, payment is made not only for the scheduled payment date but also for each scheduled payment date. The amount can also be specified by referring to the prior data. Therefore, the scheduled payment date providing unit 56 may provide information on the payment amount together with the scheduled payment date. The user terminal 30 displays information on the payment amount in association with each of the scheduled payment dates provided by the server device 10, so that the user can easily confirm when and how much amount is planned to be received. can do.

If the user frequently confirms the scheduled payment date, if the advance data is generated in advance with a relatively long period as the generation target period, it is not yet available when the user requests the provision of the scheduled payment date. There is a high possibility that it will not be necessary to generate advance data for the generation period. Therefore, the advance data generation unit 54 may change the execution frequency of the advance data generation process according to the display frequency of the scheduled payment date display screen for each user. Specifically, for example, for a user who frequently displays the scheduled payment date display screen, advance data may be generated in advance for the entire period covered in the application for regular payment. Further, for users who frequently use the scheduled payment date display screen, a change may be made to shorten the generation target period of the advance data generation process.

According to the server device 10 according to the present embodiment described above, once the user applies for regular payment, the salary according to his / her work performance is periodically set apart from the day when the employee pays the salary. You will be able to receive a considerable amount. Then, the server device 10 can generate advance data at a predetermined timing in advance so that the processing load is not concentrated on the day of payment.

In the above explanation, the user directly specifies the amount of money he / she wants to receive for each payment at the time of application, but the payment amount may be determined by another method. For example, the user may specify a ratio (payment amount ratio) to the maximum available amount. In this case, at the time of payment, the payment amount is the amount obtained by multiplying the maximum payable amount calculated based on the work record up to that point by the payment amount rate specified in advance by the user. Therefore, it may not be possible to determine the payment amount before the payment date when the latest work performance data has not been provided by the employer. Therefore, for the user who has made such an application, the advance data generation unit 54 may not generate the advance data. In this case, the advance data generation unit 54 generates advance data for an application for which the payment amount is directly specified when executing the advance data generation process, and for an application for which the payment amount rate is specified instead of the payment amount. Will not generate prior data. In this case, the advance data generation unit 54 refers to the application data table on the payment day, extracts the application data whose payment date is that day and the payment amount rate is specified, and the advance data based on the contents. Is generated and registered. This may be the same process as the prior data generation process that is periodically executed, except that the generation target period is for one day on the current day. In this case, the payment processing unit 55 immediately uses the advance data generated by the advance data generation unit 54 to execute the payment process as it is.

Alternatively, the advance data generation unit 54 may execute the advance data generation process at the timing when new work record data is provided by the employer. By doing this, the payment amount can be calculated using the payable upper limit calculated based on the newly acquired work record data, so even if the payment amount is calculated according to the payment amount rate, that Preliminary data can be generated that reflect the amount payable at the time.

Further, when an application for regular payment for specifying the payment amount rate is accepted, the advance data generation unit 54 may generate advance data including information on the payment amount rate instead of the payment amount in the above description. good. In this case, the payment processing unit 55 can calculate the actual payment amount using the payment amount rate included in the prior data and the maximum payable amount at the time of executing the payment processing. Further, if the advance data including the payment amount rate is retained in this way, the payment amount rate used by the scheduled payment date providing unit 56 to calculate the payment amount to be paid on the payment date together with the payment date. Information can be provided to the user terminal 30.

Further, the advance data generation unit 54 does not generate advance data before the payment date even when the free space of the database is insufficient, and executes the advance data generation process on the payment date. May be good. As a result, it is possible to avoid a state in which the prior data squeezes the capacity of the database D.

Further, in the above description, the upper limit acquisition unit 52 calculates the payable upper limit based on the work data acquired by the work data acquisition unit 51 of the server device 10, but the upper limit acquisition unit 52 has different information. Information on the maximum payable amount calculated by the processing device may be acquired by receiving the information from the information processing device.

10 Server device, 11 Control unit, 12 Storage unit, 13 Communication unit, 20 Employer terminal, 30 User terminal, 31 Display device, 32 Operation device, 51 Work data acquisition unit, 52 Upper limit acquisition unit, 53 Application reception unit , 54 Advance data generation department, 55 Payment processing department, 56 Expected payment date providing department.

Claims (13)

An application reception department that accepts applications for prepayment of salary equivalent from workers, and an application reception department that accepts applications including designation of payment time that arrives regularly.
Based on the application, the pre-data generation unit that specifies the payment date determined according to the payment time and generates and records the pre-data including the payment date information.
A payment processing unit that executes payment processing according to the application based on the recorded prior data on the payment date.
An information processing device characterized by including. In the information processing apparatus according to claim 1,
Information characterized in that the advance data generation unit generates advance data including information on the payment date when the payment date determined according to the payment time is included in a given generation target period. Processing device. In the information processing apparatus according to claim 2,
The advance data generation unit is an information processing apparatus characterized in that it executes a process of generating the advance data at an execution frequency corresponding to the generation target period. In the information processing apparatus according to any one of claims 1 to 3.
The advance data generation unit is an information processing apparatus characterized in that it executes a process of generating the advance data at an execution frequency according to the free space of a database for recording the advance data. In the information processing apparatus according to any one of claims 1 to 4.
The advance data generation unit is an information processing apparatus characterized in that it executes a process of generating the advance data at a different execution frequency for each employer who pays the worker. In the information processing apparatus according to any one of claims 1 to 5,
The advance data generation unit is an information processing apparatus characterized in that it executes a process of generating the advance data at a different execution frequency for each worker. In the information processing apparatus according to claim 1,
The advance data generation unit is an information processing device that executes a process of generating the advance data based on the application each time the application is accepted. In the information processing apparatus according to any one of claims 1 to 7.
It also includes an upper limit acquisition unit that obtains the upper limit that can be paid to the worker as a prepayment of the salary equivalent, which is calculated based on the work data including the actual working hours of the worker.
The payment processing unit is an information processing device that executes payment processing according to the application when the payment amount to be paid according to the application is equal to or less than the upper limit amount. The information processing apparatus according to any one of claims 1 to 8.
The application accepted by the application reception department is calculated based on the payment amount and the work data including the actual working hours of the worker as a method of determining the amount to be paid when the payment time comes. Includes either designation as a percentage of the maximum amount that can be paid to a person as a prepayment of salary equivalent.
When the advance data generation unit generates the advance data in advance, the advance data is generated for the application including the designation of the payment amount, and the application including the designation of the ratio to the upper limit amount. Is an information processing device characterized in that it does not generate the prior data. In the information processing apparatus according to any one of claims 1 to 9.
It also includes an Expected Payment Date Providing Department that provides information on the Expected Payment Date based on the worker's application in response to the provision request from the worker.
The information processing apparatus characterized in that the scheduled payment date providing unit provides information on the scheduled payment date acquired by referring to the prior data for the scheduled payment date for which the advance data has been generated. In the information processing apparatus according to claim 10,
When the ungenerated period in which the pre-data has not been generated is included in the target period of the provision request, the pre-data generation unit executes a process of generating the pre-data for the non-generated period.
The scheduled payment date providing unit is an information processing apparatus characterized in that it provides information on a scheduled payment date acquired by referring to the prior data generated for the ungenerated period. The application reception department accepts applications for prepayment of salary equivalent from workers, including the step of accepting applications including the designation of payment time that arrives on a regular basis.
A step in which the advance data generation unit identifies a payment date determined according to the payment time based on the application, and generates and records advance data including information on the payment date.
A step in which the payment processing unit executes payment processing according to the application based on the recorded prior data on the payment date.
An information processing method characterized by including. A step of accepting an application for prepayment of salary equivalent from a worker, and a step of accepting an application including designation of a payment time that arrives regularly.
Based on the application, the step of specifying the payment date determined according to the payment time, and generating and recording the preliminary data including the information of the payment date, and
A step of executing payment processing according to the application based on the recorded prior data on the payment date, and
A program that lets your computer run.

Images