WO2020179569A1 - Salary prepayment system - Google Patents

Abstract

[Problem] To increase the value of a business as a place to work, by facilitating cashless payments for salaried employees and eliminating psychological pressure. [Solution] An employer company pays a deposit into a prepayment account 6, and an employee presents a provided salary prepayment card C at a store. A prepayment ID and a usage request amount are transmitted from a store terminal 9 to a usage approval server 2, and if an amount obtained by adding a total used amount of prepaid money to the usage request amount is equal to or less than a prepayment set amount in a prepayment information file 54, the usage approval server 2 transmits a usage approval to the store terminal 9, and records the usage request amount in an actual usage information file 551. An aggregating server 3 records the total used amount of the prepaid money in an aggregating period in an aggregation file 32, to be subtracted from salary to be paid on a salary payment day.

Description

Salary prepaid system

The invention of this application relates to a system for prepayment of salary.

In recent years, due to advances in IT technology, payment methods for buying and selling goods and services have become diversified. One of them is the progress of cashless payments. In addition to credit card payments, payments by smartphones and payments by prepaid cards for transportation and convenience stores are becoming popular.
Most of the general consumers who make such payments are salaried workers. In the case of a salaried employee, needless to say, the source of payment is salary. Regarding salaries, the payment method is legally stipulated from the standpoint of worker protection, which in a sense hinders the flexibility of payment. In other words, the law stipulates that the salary be handed to workers directly in cash. Bank transfers are exceptionally permitted in consideration of the fact that deposits in a bank deposit account are treated as cash and that workers can reliably withdraw.

JP, 2016-033829, A

The above situation can be said to be troublesome for salaried employees. The salaried person withdraws the paid salary from the bank account and charges the prepaid card for transportation, for example. Then, when the balance is exhausted using the prepaid card, the deposit is withdrawn from the bank account and charged. In the case of a credit card, this can be done with a monthly debit from the payroll account, so there is no such a hassle, but there is a card fee. In addition, when the balance of the bank account is insufficient at the time of withdrawal, the withdrawal damage may be incurred or the so-called blacklist may occur. Therefore, there is a problem that a burden of cost is generated and psychological pressure is applied because it does not take time and effort.

The invention of the present application has been made in consideration of the above points, and makes it possible for a salaried employee to easily perform cashless settlement without any hassle and to prevent psychological pressure. The purpose is to By providing a new and unique payroll system for this purpose to companies (employers), the purpose is to contribute to increasing corporate value as a workplace.

In order to solve the above problems, this application discloses an invention called a payroll prepaid system. This system is a payroll prepaid system that is used when an employer company pays salaries in advance to employees. It is a usage approval server that approves the use of prepaid money and an aggregation server that totals the usage amount of prepaid money. And a storage unit.
The storage unit stores a prepaid setting information file in which a prepaid setting amount set according to the working status of an employee is recorded, and a usage record information file in which a usage record of the prepaid money is recorded. The usage record information file is a file in which a prepaid ID for identifying an employee who has a right to use the prepaid money and a usage amount of the prepaid money within the aggregation period are recorded.
The use approval server is a server that accepts access from a store-side computer via the network, and when the store-side computer sends the prepaid ID and the usage request amount via the network, up to that point regarding the prepaid ID. If the sum of the total amount of prepaid money used and the requested usage amount sent is less than or equal to the prepaid setting amount, the usage approval information is sent to the store side computer, and the usage requested amount is used for the prepaid ID. It is a server that records in an information file.
The aggregation server is a server that obtains the total amount of prepaid money used within the aggregation period from the usage record information file and records it in the aggregation file in order to deduct the total amount of usage from the salary paid on the payday. is there.
Further, in order to solve the above-mentioned problem, the payroll prepaid system stores a prepaid account information file in which information of a prepaid account for depositing funds for use of the prepaid money is recorded in a storage unit, and the prepaid account information file is , The information of the individually owned deposit, which is the deposit individually owned by the employee for each prepaid ID, and the information of the store owned deposit, which is the deposit owned by each store, are recorded, and the prepaid money approved by the use approval server is recorded. The payment server may be configured to transfer the usage request amount from the individual ownership deposit related to the prepaid ID used for the usage to the store ownership deposit related to the store.
In addition, in order to solve the above problems, the payroll prepaid system has a prepaid information file that includes information on corporate deposits that are deposits deposited by an employer company for the use of prepaid money and belonging to the employer company. Information of shared deposit, which is a deposit shared by all employees who have the right to use the prepaid money, is recorded, and when the payment server transfers the usage request amount to the store-owned deposit, the usage request amount is stored. Is a server that transfers from a shared deposit to an individual ownership deposit, and then to a store-owned deposit.When the payment server transfers the usage request amount from the shared deposit to the individual ownership deposit, the usage request amount is transferred from the corporate ownership deposit to the shared deposit. It may have a configuration in which a filling server is provided to transfer to.
Further, in order to solve the above problems, the payroll prepaid system records whether or not the usage record information file is for corporate use in the employer company, and records whether it is for corporate use or not. Can be changed by the person in charge of the employer company or the employee associated with the prepaid ID operating the terminal, and the totaling server determines whether the usage request amount approved during the totaling period is not for corporate use. The server may have a configuration of calculating the total usage request amount for each prepaid ID.
Further, in order to solve the above problem, in the salary prepaid system, an employee ID, which is information for identifying an employee in an employer company, is recorded in a prepaid setting information file in a state of being associated with the prepaid ID. Can have the configuration.
Further, in order to solve the above problems, the payroll prepaid system, in the prepaid setting information file, the prepaid amount initial value is recorded, and the prepaid set amount is initially the same value as the prepaid amount initial value, There is a management server that can be accessed from a terminal operated by a person in charge of the employer company. The management server changes the set amount to change the prepaid set amount according to the request from the terminal operated by the person in charge of the company. It can have a configuration in which the program is implemented.
Further, in order to solve the above problems, the payroll prepaid system is a variable setting amount in which the prepaid setting amount fluctuates during the aggregation period, and the prepaid setting amount, which is the variable setting amount, is changed within the aggregation period according to the working status of the employee. There is provided an amount increasing server for gradually increasing the amount, and the amount increasing server may be configured to record each increased prepaid setting amount in the prepaid setting information file.
Further, in order to solve the above problems, the payroll prepaid system has a fixed set amount in which the prepaid set amount is constant during the counting period and a variable setting amount that fluctuates during the counting period, and the fixed set amount is set in the prepaid setting information file. The amount and the variable setting amount are stored for each prepaid ID, and an amount increasing server is provided for gradually increasing the prepaid setting amount, which is the variable setting amount, within the aggregation period according to the working status of the employee. The amount-increasing server is a server that records each increased variable setting amount in the prepaid setting information file, and the usage approval server compares the fixed setting amount and the variable setting amount when the approval request is sent. Then, the server may be configured to add the total usage amount related to the larger set amount and the approval request amount, and to send the use approval when the added amount is less than or equal to the larger set amount. ..
In addition, in order to solve the above problems, the salary prepaid system has a special setting in the prepaid setting information file, which is the maximum amount of prepaid money that can be used regardless of the working situation, in addition to the prepaid setting amount. The amount is recorded for each prepaid ID, and the usage approval server compares the prepaid set amount and the special set amount at the time when the approval request is sent, and the total usage amount and the approval request amount related to the larger set amount. It is possible to have a configuration in which is a server that adds and, and when the added amount is less than or equal to the larger set amount, sends a usage approval.
In addition, in order to solve the above problems, the salary prepaid system is provided with a special amount increase server that gradually increases the special set amount within the aggregation period, and the special amount increase server increases the special set amount. It may have a configuration of a server for recording in the prepaid setting information file.
Further, in order to solve the above problems, the salary prepaid system may have a configuration in which the prepaid money is a currency-denominated asset, a virtual currency, a crypto asset, points in a point card, a token, or electronic money.
Further, in order to solve the above problems, the payroll prepaid system is information presented to the store in a state where the prepaid ID is carried on the ID carrier, and the ID carrier is a card, a mobile terminal, or an authenticateable biological feature. It can have the structure of being a part.

As described below, according to the salary prepaid system according to the invention of this application, the employee's salary is paid in advance in the form of prepaid money. Although there is a limit, employees can pay at the store by presenting the prepaid ID, which is extremely convenient. Traditionally, you would have to withdraw your salary from your bank account and charge your prepaid card, but this system doesn't have to do that. Also, since it is not a credit card, there is no pressure to ensure that your bank account has a deposit on the day of withdrawal. Therefore, the psychological usability is also very high.
Further, in general, advance payment of salary is approved by an employee applying to the company, but according to this system, advance application is not particularly necessary. When an application is made, the department that processes the application knows the fact, which puts a psychological burden on the employee. According to this system, there is no such psychological burden, and usability is very high in this respect as well.
On the other hand, even for employer companies, the salary prepaid system raises the evaluation of employees and gives them a higher impression as a company that gives preferential treatment to employees. For this reason, it is possible to contribute to gathering a large number of excellent human resources and, as a result, to improve corporate performance. At this time, even if it is prepaid, it is inconvenient if it is a method of transferring cash to the employee's account individually, but it is extremely simple because it is only authorized to use prepaid money with a limit amount. is there.
In addition, if a prepaid account is prepared as an account for payment and the funds for payment are once transferred to the store after being held by the employee, even if the payment is made in advance, it is legally required. It makes sense that the salary is paid to the employee and then used for settlement.
Regarding the funds for the prepaid account, apart from the company-owned part, a shared part for all employees and an individual employee-owned part are provided, and the funds were transferred from the shared part to the employee-owned part to the store-owned part. In this case, if the company owns the common part and the common part is filled with funds, the loss of the prepaid salary will be reduced in the employer company.
Further, if the prepaid money can be used not only for private use but also for business use, the system can be used for settlement of company expenses (expense), which is more convenient.
Further, if the prepaid ID is linked to the employee ID, the management in the employer company becomes easier.
Also, if the prepaid setting amount in the prepaid setting information file can be changed by the terminal operated by the person in charge at the employer company, the prepaid setting amount can be changed appropriately on the employer company side, which is convenient in this respect. Get higher Further, it becomes easy to give an appropriate prepaid money according to the employee.
In addition, the prepaid setting amount is a variable setting amount, and if the variable setting amount is increased according to the working situation, the prepaid amount can be used even at the beginning of working or the introduction of salary prepaid. Therefore, convenience is improved in this respect.
In addition, if the prepaid set amount is a fixed set amount or a variable set amount, if you decide to use the larger set amount and decide to use it, the prepaid amount of the prepaid amount will be more favorable depending on the working situation. Since it can be used, it is more convenient in this respect.
In addition, if a special set amount is provided in addition to the prepaid set amount, the special set amount can be granted regardless of the working situation and can exceed the work receivable, so the prepaid amount as a so-called advance loan is available. Will be able to be used. In this respect, it is more suitable as a welfare program. At this time, if the special set amount is gradually increased, an appropriate special set amount can be given depending on the employment situation, which is more preferable.

It is the schematic of the salary prepaid system of the first embodiment. It is a schematic diagram which showed an example of the structure of an employer company information file. It is the schematic which showed the ownership relationship of the funds deposited in the prepaid account. It is the schematic which showed an example of each structure of the prepaid account information file. It is the schematic which showed an example of the structure of a card provision information file. It is a schematic diagram which showed three kinds of limits. It is the schematic which showed an example of the structure of the prepaid setting information file. It is the schematic which showed an example of the structure of a use record information file. It is the schematic which showed an example of the prepaid issuing page. It is the schematic which showed an example of the set amount change page. It is a flowchart which showed the outline of the use approval program. It is a flowchart which showed the outline of the payment program. It is a flowchart which showed the outline of the aggregation program. It is the schematic of the salary prepaid system of the second embodiment. It is the schematic which showed an example of the structure of the use record information file in 2nd embodiment. It is the schematic which showed an example of the use input page. It is an outline showing an example of the company approval page. It is a flowchart which showed the outline of the aggregation program in 2nd Embodiment. It is the schematic which showed the principal part of the salary prepaid system of 3rd embodiment. It is the schematic which showed the claim part of the salary prepaid system of 4th embodiment.

Hereinafter, modes (embodiments) for carrying out the invention of this application will be described.
FIG. 1 is a schematic diagram of a salary prepaid system according to the first embodiment. The salary prepaid system shown in FIG. 1 (hereinafter, may be simply referred to as a system) is a system used by an employer company to pay salaries to employees. This system is a system for pre-paying a part of salary in the form of prepaid money to an employee before a fixed salary payment date.

In this embodiment, the prepaid money is provided by providing a salary prepaid card C to each employee. That is, the system of FIG. 1 realizes two features that a part of the salary is given in the form of a salary prepaid card C and that the salary is paid before the salary payment date, that is, prepaid. It is supposed to do.
In the system of the embodiment, what is important is that at the store where the prepaid money is used, it is proved that the person has the right to use the prepaid money, and the prepaid ID, which is information identifying the person, is presented. Is. The payroll prepaid card C is an example of a medium carrying a prepaid ID having such a meaning (hereinafter, referred to as an ID carrier).

Describing the more specific configuration of the system, the system of the embodiment is configured to include a plurality of servers. These servers include a prepaid issuing server 1, a usage approval server 2, an aggregation server 3, a payment server, a management server 4, and the like. Each of the servers 1 to 4 may be realized by a single server computer, or a plurality of server functions may be realized by one server computer.

Further, the system of the embodiment includes a storage unit 5. The storage unit 5 may be a storage such as a hard disk included in any of the servers 1 to 4, or may be included in a dedicated server (storage server). Therefore, each of the servers 1 to 4 may be related to so-called cloud computing. Note that the system of this embodiment takes a form in which each employer company pays each employee prepayment in advance, but the actual management is entrusted to another company (hereinafter referred to as an operating company).

The prepaid issuing server 1 is a server for issuing a payroll prepaid card C to each employee, and strictly speaking, a server for issuing a prepaid ID. In the embodiment, since the payroll prepaid card C is issued for each employer company, each employee in this case is each employee in each employer company.
In the system of the embodiment, the operating company provides a plurality of employer companies with a service relating to the issuance and management of the payroll prepaid card C (hereinafter referred to as payroll prepaid service). The storage unit 5 stores an employer company information file 51 that records information on the employer company to which the service is provided. FIG. 2 is a schematic diagram showing an example of the structure of the employer company information file.

As shown in FIG. 2, the employer company information file 51 includes “company ID”, “company name”, “head office address”, “department in charge”, “person in charge”, “number of registered employees”, and “deposit amount”. , "Prepaid money initial value" and the like. The “department in charge” is a department in charge of the system in the employer company in the embodiment, and is usually a department such as the general affairs department or the human resources department. The “person in charge” is the name of a person in charge in the employer company of the system of the embodiment (hereinafter referred to as a person in charge in the company).

In the system of the embodiment, when the salary prepaid card C is issued, each employer company provides a deposit. The deposit is deposited in a bank account (hereinafter referred to as a prepaid account) 6. The prepaid account 6 is usually a bank account held by the operating company. However, the ownership relationship of the funds placed in the deposit account is negotiated by contracts with the employer company, the operator, and each employee belonging to the employer company, and changes from time to time.

FIG. 3 is a schematic diagram showing the ownership relationship of funds deposited in the prepaid account 6. There are basically four different owners of the funds deposited in the prepaid account 6. One is the employer company. The funds deposited in the prepaid account 6 are initially deposits and are still owned by the employer. The other is all employees who belong to the employer company and are entitled to use the prepaid money. If a trade union exists, it may be the owner. Yet another is each individual employee with a prepaid ID. The other is each store where prepaid money is used.

In the salary prepaid system of the embodiment, the funds put in the prepaid account 6 are initially deposits, but the ownership of the funds is shared by all employees. And, in addition, it will be owned by the individual employee for each payment. Furthermore, once payment is made, the funds will be owned by the store.

The storage unit 5 stores files 521 to 524 for managing ownership of funds deposited in the prepaid account 6 (hereinafter, prepaid account information file). The transfer of ownership is performed by changing the record of the prepaid account information files 521 to 524. Hereinafter, for convenience of description, a portion 61 of the funds of the prepaid account 6 owned by the employer company is referred to as a “corporate account”, and a shared portion 62 of all employees of the employer company is referred to as a “shared account”. , Each employee's individually owned portion 63 is called an individual account. Further, the owned portion 64 of each store is called a store account.

FIG. 4 is a schematic view showing an example of each structure of the prepaid account information files 521 to 524. As shown in FIG. 4, the prepaid account information files 521 to 524 are created for each account 61 to 64, respectively. Hereinafter, the four types of prepaid account information files 521 to 524 will be referred to as a company account information file 521, a shared account information file 522, an individual account information file 523, and a store account information file 524.
As shown in FIG. 4, the company account information file 521 is a database file including fields such as “company ID”, “date and time”, “payment amount”, “payment amount”, and “balance”. "Balance" means the balance of deposits.

The shared account information file 522 is also a database file including fields such as “company ID”, “shared ID”, “date and time”, “payment amount”, “payment amount”, and “balance”. The "shared ID" is an ID that identifies all the co-owners, and is, for example, an ID that uses a company ID and adds identification information to it. "Balance" means the balance of funds in the common area.
Each individual account information file 523 is a database file including fields such as “company ID”, “shared ID”, “prepaid ID”, “date and time”, “payment amount”, “payment amount”, and “balance”. is there. "Balance" means the balance of funds for the individually owned portion.

Each store account information file 524 is a database file including fields such as “store ID”, “date and time”, “use ID”, “payment amount”, “scheduled remittance date” and the like. As the "date and time", the date and time when the salary prepaid card C is used at the store or the date and time of payment described later is recorded. As the “payment amount”, the amount of use of the approved salary prepaid card C is recorded. As the "scheduled remittance date", the scheduled remittance date from the prepaid account 6 to the bank account owned by the store is recorded.

Note that the company account information file 521 may be a separate file for each employer company, or may be one file for a plurality of employer companies for which the operating company provides services. If they are separate files, they should be identifiable by using a file name that uses the company ID. The same applies to the shared account information file 522 and each individual account information file 523. The store information file 57 may also be a file for each store, or may be a single file for a plurality of or all stores.

The amount of the initial deposit deposited by the employer company into the prepaid account 6 depends on the number of employees to whom the payroll prepaid card C is issued and the prepaid amount per employee, and the operation business with each employer company. Arranged by contract with the person. For example, in a company with 500 employees (500 salary prepaid cards issued) and the issuance amount (initial value) of salary prepaid card C per person is 50,000 yen, the initial issuance amount is 25 It will be 10,000 yen. It is unlikely that all employees will use the card at the maximum limit, so a smaller amount is acceptable. For example, 20 million yen or 15 million yen. This amount is recorded in the “payment amount” field of the company account information file 521. In the “prepaid money initial value” of the employer company information file 51, the initial issuance amount of the payroll prepaid card C per person is recorded.

Although not shown, the storage unit 5 stores a login file for the person in charge in the company to log in to the system. The login file is a file in which the login ID and password are recorded. A login ID and password are issued to each employer company, and it is possible to log in to the prepaid issuing server 1 and the like. The login ID may also be a company ID, or may be issued separately from the company ID. When issued separately from the company ID, the company ID of the employer company to which the person in charge in the company to which the login ID is provided belongs is recorded in the login file.

Further, the storage unit 5 stores a card providing information file 53 which is a database file in which the prepaid ID of the salary prepaid card C provided to each employer company is recorded. FIG. 5 is a schematic diagram showing an example of the structure of a card provision information file.
In this embodiment, in order to issue the payroll prepaid card C, the operating company first provides the employer company with the required number of payroll prepaid cards C in which the prepaid ID is described, and the person in charge of the employer company provides the payroll prepaid card C. Is distributed to each employee. The card provision information file 53 is a file that allows the employer company to know which salary prepaid card C of which prepaid ID has been provided.

Specifically, as shown in FIG. 5, the card provision information file 53 is a database file in which a record including fields of “provision date”, “prepaid ID”, “expiration date”, and “issue or not” is recorded. Is.
The “issued/not issued” field is a field having a false value by default, and is a field that becomes a true value when the payroll prepaid card C is issued in association with the employee ID as described later. The card provision information file 53 has a file name using a company ID, and can be specified by the company ID.

Further, the prepaid setting information file 54 is stored in the storage unit 5.
The important information recorded in the prepaid setting information file 54 is the information on the usage limit of the prepaid money. In this embodiment, three different usage limits are set. One is information on a certain limit amount during the aggregation period. Hereinafter, this limit amount will be referred to as a fixed set amount. The other is information on the maximum amount that gradually increases during the aggregation period. Hereinafter, this limit amount will be referred to as a variable limit amount. The other is a usage limit that is specially set for employees. Hereinafter, this limit amount will be referred to as a special set amount.

　The first two limits are set according to the working conditions of employees and are based on labor claims. Therefore, the use of this amount of prepaid money has the character of prepaid salary. The special amount is based on the employment contract between the employer company and the employee, but is not necessarily based on the working situation. Therefore, it may be the maximum amount that allows the use of an amount exceeding the labor claim. In this sense, the prepaid special set amount may be a limit amount that allows use as so-called advance borrowing (debt).

The three types of limit amounts will be described in more detail with reference to FIG. FIG. 6 is a schematic diagram showing three types of limits. Of these, FIGS. 6(1-1) and 6(1-2) show the fixed set amount.
FIG. 6 (1-1) shows the simplest example. In this example, the salary deadline and the card usage deadline are the same. Therefore, the card usage aggregation period is from the 16th of each month to the 15th of the following month, which is the same as the salary aggregation period.
In the example of FIG. 6 (1-1), the card usage is totaled on the 15th day of each month and deducted from the salary on the 25th day of the same month. Then, the fixed set amount becomes zero on the 15th of every month, but recovers to the fixed set amount on the 16th of the next day. That is, the prepaid money is recharged. In FIG. 6 (1-1), the solid line indicates the fixed set amount. The amount that can actually be used decreases according to the amount used. In FIG. 6(1-1), the broken line shows an example of the change in the usable amount.

In the example of FIG. 6 (1-1), if the salary is closed on the 15th of a certain month, the salary will be paid on the 25th of the same month. In this case, the prepaid money issued on the basis of the employment is paid on the 16th day of the same month and can be used until the 15th day of the next month. Prepaid money used by the 15th of the following month will be deducted from the salary on the 25th of the following month. In other words, the prepaid money issued on the basis of employment is deducted from the salary of the following month, not the salary for the employment.
If you retire in the middle, you will stop using the card immediately, but usually the salary will be calculated on a daily basis and will be paid the following month, so it will be deducted from that. The exception is if you retire on the 15th, in which case the data up to that point will be counted and deducted from your salary on the 25th of the same month.

Although it is possible to implement the example of FIG. 6 (1-1) as well, the closing of the payroll calculation and the closing of the card use are the same day, which is complicated, so in reality, as shown in FIG. 6 (1-2) In many cases, the card usage is closed a few days before the salary is closed. In FIG. 6(1-2), the deadline for using the card is the 10th of every month. In this example, a fixed set amount of prepaid money is charged on the 16th on the basis of work closed on the 15th of a month, and the prepaid money can be used until the 10th of the next month. The card usage will be closed on the 10th of the following month, and will be deducted from the salary on the 25th of the next month. In this way, since there are 5 days from the deadline of card usage to the deadline of payroll calculation, it is possible to perform tasks such as counting card usage during that time, and reduce complexity.
In the example of FIG. 6 (1-2), after the card usage is closed on the 10th, the fixed amount is recharged on the 11th. The use of cards on the 11th to 15th will not be made in time for the payroll calculation on the 15th, so it will be counted as the amount closed on the 10th of the following month and deducted from the salary on the 25th of the next month.

On the other hand, the variable setting amount takes into consideration that employees are working every day even before the closing date of payroll calculation, and labor receivables are incurred. That is, as shown in FIG. 6 (2), the variable set amount gradually increases from the day following the first day of the salary aggregation period. The variable set amount exceeds the fixed set amount at a certain point in the aggregation period, and the increase stops when a certain amount is reached. For example, if the salary aggregation period is from the 16th to the 15th, the salary starts to increase from the 17th and gradually increases until the 10th of the following month. In the example of FIG. 6 (2), the fixed set amount is 30,000 yen and the variable set amount is a maximum of 50,000 yen.

Introducing a variable setting amount as shown in Fig. 6 (2) has an advantage in that prepaid money can be used especially immediately after getting a job and starting working. The same applies immediately after the employer company starts using the payroll prepaid service. With only the fixed amount, the fixed amount can be used after the salary is closed during the aggregation period, so the prepaid money cannot be used until the first aggregation period is reached. On the other hand, as shown in FIG. 6 (2), since the variable set amount is the maximum amount given according to daily employment, it can be used immediately after starting work.

The deadline for using the variable set price may be the same as the fixed set price. For example, the use is closed at the end of every 10th month, and the usage of the variable set amount up to that point is totaled. Then, since employment starts on the 11th of the next day, the variable set amount will be given from the 12th of the next day, and will be gradually increased. Also in FIG. 6(2), the solid line shows the fluctuation setting amount, and the broken line shows an example of the transition of the amount actually usable (the amount obtained by subtracting the used amount).

6(3) shows an example of the special set amount. Since the special set amount is an amount specially set separately from the fixed set amount and the variable set amount, there is no particular pattern. It can be set freely at the discretion of the employer company. FIG. 6 (3) shows an example of setting as a so-called advance borrowing that permits the use of an amount exceeding the labor claim. In this example, the special setting amount is also an amount that gradually increases according to the working situation. However, the amount may exceed the daily labor receivables. For example, a part-time employee whose daily salary is 10,000 yen may be given a special set amount of 15,000 yen the day after he / she works for one day, and the daily salary may increase from there.

FIG. 7 is a schematic diagram showing an example of the structure of the prepaid setting information file 54. As shown in FIG. 7, the prepaid setting information file 54 includes “prepaid ID”, “company ID”, “employee ID”, “employee name”, “fixed setting amount”, “variable setting amount”, “special setting”. It is a database file consisting of fields such as "set amount".
In the prepaid setting information file 54, the unique data is the prepaid ID. The employee ID is the same data as in the employee information file. The "fixed set amount", "variable set amount", and "special set amount" are fields in which the usage limit amount having the above meaning is recorded.

The field of "variation increase amount" is the amount when the fluctuation setting amount increases at one time. The field of "maximum variable set amount" is a field in which the maximum variable set amount is recorded. The field of "special type" is a field in which the type of the specific setting amount is recorded as gradually increasing type or fixed type. The field of "special increase amount" is a field for recording the amount of increase at one time when the special increase amount is a gradual increase type. The "special maximum amount" is a field in which the maximum value is recorded when the special set amount is a gradual increase type.

The system according to the embodiment includes the amount increase server 7 in order to automatically record the increase in the variable setting amount and the increase in the special setting amount in the case of the gradually increasing type in the prepaid setting information file 54. The set amount increase program 71 is implemented in the amount increase server 7.

The set amount increase program 71 is customized and implemented for each business owner company. If all employees are full-time employees, full-time contract employees, or part-time workers, the set amount increase program 71 is programmed to be automatically executed every work day of the employer company. In this case, when the set amount increase program 71 is started, it acquires a prepaid ID for each employee ID, opens the prepaid setting information file 54, and acquires the value of the “variable increase amount”. Then, the value of the variable increase amount is added to the value of the "variable setting amount". Update. If the maximum fluctuation amount is exceeded, the “variable setting amount” is updated with the maximum fluctuation amount.

If the value of the "special type" is a gradual increase type, the set amount increase program 71 acquires the value of the "special increase amount" and adds the amount to the value of the "special set amount". If the added amount is less than or equal to the "special maximum amount", the "special set amount" is updated with the added amount, and if the value exceeds the "special maximum amount", the "special maximum amount" is set. Update the "special setting amount" with the value of "amount".

If the employer company has a part-time job or part-time workday, the set amount increase program 71 is implemented in conjunction with the time card system. In this case, the set amount increase program 71 is provided with information on the amount of increase for each employee ID with respect to the hourly wage and the daily salary (hourly wage x hours). For example, it is information that 10% is given as a variable increase amount to the daily salary, or 20% is given as a special increase amount to the daily salary. Then, the set amount increase program 71 is executed according to the program execution request from the time card system, and at that time, the working hours are given as an argument. The set amount increase program 71 calculates the increase amount, adds it to the value of the "variable set amount", and updates it in the same manner as in the case of a regular employee or the like. The same applies to the specially set amount.

On the other hand, the usage record information file 551 is stored in the storage unit 5. FIG. 8 is a schematic diagram showing an example of the structure of the usage record information file 551.
As shown in FIG. 8, the usage record information file 551 includes “usage ID”, “usage date and time”, “store ID”, “store name”, “usage amount”, “usage frame ID”, and “fixed frame total”. , A database file that records records consisting of fields such as "total variable frame" and "total special frame".

The usage ID is an ID that can be identified for all usages of the payroll prepaid card C. For example, the ID is a combination of a prepaid ID, a date of use, and a serial number. The usage record information file 551 is created for each prepaid ID, and has a file name using the prepaid ID. Therefore, it can be specified by the prepaid ID.

Further, the storage unit 5 stores a total usage record information file 552 that records usage records for all prepaid IDs. Although the illustration of the all-use record information file 552 is omitted, the all-use record information file 552 includes “use ID”, “prepaid ID”, “use date/time”, “store ID”, “store name”, “store”. It is a database file that records records consisting of fields such as "location", "amount spent", and "summary".
Further, the erasure information file 56 is stored in the storage unit 5. The erasure information file 56 is a file that stores the prepaid ID of the card C that has been erased due to theft or loss. Even when the employer company retires, the prepaid ID for the employee is immediately recorded in the deletion information file 56.

Next, the prepaid issuing server 1 will be described. As shown in FIG. 1, the prepaid issuing program 11 is implemented in the prepaid issuing server 1. In the payroll prepaid system of the embodiment, the payroll prepaid card C is issued by a person in charge of the company recording the prepaid ID and the employee ID in the prepaid setting information file 54 in association with each other. Specifically, the prepaid issuing server 1 prepares a prepaid issuing page for the person in charge in the company. FIG. 9 is a schematic diagram showing an example of a prepaid issuing page.

The in-company person operates the terminal (hereinafter, in-company person in charge terminal) 81 to log in to the prepaid issuing server 1 and display the prepaid issuing page. The prepaid issuance page includes a column displaying a list of unissued prepaid IDs (hereinafter referred to as unissued prepaid ID list) 111, an employee ID input column 112 for inputting an employee ID for each prepaid ID, An employee name input field 113 for inputting an employee name is provided. The prepaid issue page is a page for transmitting the issue information of one salary prepaid card C in one line. That is, in each line, the prepaid ID is displayed on the left end, the entry field for the employee ID associated with the prepaid ID is displayed on the right side, and the employee name associated with the employee ID is displayed on the right side. Input field is displayed.

The prepaid issuing server 1 searches the card provision information file 53 of the employer company according to the login ID transmitted at the time of login, and acquires the prepaid IDs of all the records in which the "issued" field has a false value. .. Then, as shown in FIG. 9, it is incorporated into the prepaid issue page and transmitted to the terminal for the person in charge to be displayed.
The prepaid issue page is provided with a registration button 114. The registration button 114 is provided with a confirmation page, and the send button provided here is an execution button for the registration module included in the prepaid issuing program 11.

The registration module is a module that records the information displayed/input in each line in the prepaid setting information file 54 as one card issue information. That is, the registration module is programmed to add a new record to the prepaid setting information file 54 and record card issuance information such as a prepaid ID, an employee ID, and an employee name. When all the card issuance information is recorded, the registration module is finished, and the prepaid issuing program 11 is also finished.

In the above prepaid issuance, the fixed value is set to the initial value described above. That is, the registration module acquires the company ID according to the login ID and opens the company information file. Then, the default "fixed set amount" of the new record by acquiring the initial value of the prepaid money can be set as a uniform value for all employees (for example, a uniform 50,000 yen). When a new record is added to the prepaid setting information file 54, the prepaid issuing program 11 records this default value in the “fixed set amount” field. The registration module is thus programmed.

Next, the change of the prepaid set amount will be described.
The prepaid issuing server 1 prepares a page for changing the prepaid set amount (hereinafter, set amount change page). When the in-company person in charge logs in with the in-company person in charge ID and is called from the top page, the prepaid issuing server 1 displays the set amount change page on the in-company person in charge terminal 81.

FIG. 10 is a schematic view showing an example of a set amount change page.
As shown in FIG. 10, the set amount change page includes an employee ID input column 121, a prepaid set amount display column 122, and a changed amount input column 123. Further, the management server 4 is installed with a prepaid setting amount change program 41. The prepaid set amount change program 41 includes an amount display module and an amount change module.

The prepaid set amount display column 122 is a column for displaying the current prepaid set amount. The current values are displayed for each of the fixed set amount, variable maximum amount, variable increase amount, and special set amount. Regarding the special setting amount, in the case of the gradually increasing type, the special setting increasing amount is displayed. The search button 120 provided next to the employee ID input field 121 is an execution button of the forehead display module. The forehead display module acquires the company ID according to the login ID and opens the prepaid setting information file 54 of the employer company. Then, the employee ID is programmed to obtain the values of fields such as “fixed set amount” and “variable maximum amount” of the corresponding record, and display them in the prepaid set amount display field 122. Further, the amount display module acquires the "employee name" of the record and displays it in the employee name display field 124 for confirmation.
The registration button 125 provided next to the change amount input field 123 is an execution button of the amount change module. The amount change module is programmed to update the “prepaid set amount” of the corresponding record in the prepaid setting information file 54 with the value input in the changed amount input field.

Next, the configuration for using the salary prepaid card C will be described.
As will be described later, the payroll prepaid card C may be used for personal authentication, but in this embodiment, the payroll prepaid card C is used without personal authentication. That is, when using the payroll prepaid card C, it is sufficient to obtain a prepaid ID, confirm whether the prepaid card is within the expiration date and the usage limit amount, and confirm that the payroll prepaid card C is not an erasure card. It has a technical structure. Hereinafter, these points will be described.

A store terminal 9 is placed in each store where the payroll prepaid card C is used. The store terminal 9 is an example of a store-side computer in this embodiment. An approval request program 91 that accesses the card use approval server 2 via the network (Internet) is installed in each store terminal 9. The use approval program 21 is implemented in the card use approval server 2. FIG. 11 is a flowchart showing the outline of the usage approval program.

A store information file 57 is stored in the storage unit 5. Although illustration of the structure of the store information file 57 is omitted, the store information file 57 is a database file including fields such as “store ID”, “headquarters ID”, “store name”, and “location”. The "headquarters ID" is a field that is recorded as needed, and is a field that is entered when there is a separate business entity that operates the store, such as a chain store, and it is necessary to identify it. is there.

Each store terminal 9 is a terminal having a reading function such as an IC card reader. At the same time, each store terminal 9 has a storage unit such as a memory, and the storage unit 5 stores the store ID together with the approval request program 91. The approval request program 91 is installed in each store terminal 9 so as to be automatically activated when the salary prepaid card C is inserted. In addition, each store terminal 9 is provided with a numeric keypad for inputting the sales price of the product / service as the usage request amount. In some cases, the store terminal 9 is connected to the POS device so as to acquire the sales price from the POS device.

The approval request program 91 is automatically activated when the salary prepaid card C is inserted, and is in a state of waiting for input of the usage request amount. The usage request amount is usually entered by a person in charge at the store using the numeric keypad or from a POS device. When the usage request amount is input, the approval request program 91 sends the prepaid ID read from the salary prepaid card C, the input usage request amount, and the store ID to the card use approval server 2 and the usage approval program 21 Is programmed to launch.
As shown in FIG. 11, the use approval program 21 first searches the erasure information file 56 with the prepaid ID and determines whether or not it is a deleted salary prepaid card. If the salary prepaid card has been deleted, a reply to that effect is sent to the approval request program 91 (store terminal 9), and the program is terminated. Further, although not shown, the use approval program 21 searches the prepaid setting information file according to the prepaid ID and acquires the expiration date of the corresponding record. If the expiration date has passed, the approval is returned and the program ends.

If the prepaid ID is not recorded in the deletion information file 56 and the expiration date has not passed, the usage approval program 21 opens the usage record information file 551 of the corresponding user (employee) according to the prepaid ID, and the last record. Acquire the values of "fixed set amount", "variable set amount", and "special set amount" of (the latest usage record). Then, for the highest set amount among those values, the value of the total usage amount for the corresponding set amount is acquired. For example, if the "fixed set amount" is the highest, the "fixed frame total" is acquired. If the “variable set amount” is the highest, the “variable frame total” is acquired. If the "special setting amount" is the highest, "special frame total" is acquired. Then, if the sum of the acquired total usage amount and the transmitted usage request amount is less than or equal to the set amount, the use approval return value is returned to the approval request program 91. For example, if the fixed set amount is the highest, and the sum of the fixed frame use total amount and the approval request amount is less than or equal to the fixed set amount, the return value of the use approval is returned.

When the return value of the usage approval is returned, the usage approval program 21 adds a new record to the usage record information file 551. Then, the “usage frame ID” is recorded according to the type of the usage limit amount, and the total usage amount of the corresponding type is updated by adding the usage request amount. In addition, a usage ID is automatically generated and recorded in the "use ID" field. Further, the store information file 57 is searched by the store ID to acquire the store name, and the information is recorded in the record added in the usage record information file 551. Also, a new record is added to the total usage record information file 552 to record the shop ID, usage request amount, and the like. On the other hand, when the usage request amount transmitted from the store terminal 9 does not satisfy the above condition, the approval request program 91 transmits a non-approvable return value to the approval request program 91 and ends.

Next, a configuration for settlement with a store in which the payroll prepaid card C is used will be described.
The settlement by the settlement server here does not mean remittance to a bank account held by the store, but means a change in ownership (movement of funds) within the prepaid account 6. Technically, it is equivalent to changing the record of each prepaid account information file 521 to 524.

The use approval server 2 described above also functions as a payment server. That is, the payment program 22 is implemented on the use approval server 2. In addition, the system of the embodiment includes a filling server that fills funds from the company account 61 to the shared account 62, and the use approval server 2 also functions as a filling server. That is, the payment program 22 also includes a code for filling funds.
In this embodiment, the settlement program 22 is designed to be executed in real time when the payroll prepaid card C is used, and the settlement program 22 is called from the use approval program 21 and executed. That is, the use approval program 21 approves the use, records the use record information in the use record information file 551, and then executes and ends the settlement program 22.

FIG. 12 is a flowchart showing an outline of the payment program 22. The payment program 22 is executed by passing a prepaid ID, a usage ID, an approval request amount, and a store ID as arguments. As shown in FIG. 12, the payment program 22 opens the shared account information file 522 and adds a new record. Then, the date and time of execution of the program is recorded in the “date and time” of the added record, the usage ID is recorded in the “usage ID”, the approval request amount is recorded in the “withdrawal amount”, and the prepaid ID is recorded in the “prepaid ID”. Then, the store ID is stored in the "store ID". In the "Balance" field, the amount after withdrawal is automatically calculated and recorded.

Next, open the individual account information file 523 related to the prepaid ID and add a new record. Then, the program execution date and time is recorded in “date and time”, the use ID is recorded in “use ID”, the approval request amount is recorded in “payment amount”, and the store ID is recorded in “store ID”. In the "Balance" field, the amount after deposit is automatically calculated and updated.

Next, the payment program 22 adds a new record in the same individual account information file 523. Then, the program execution date and time is recorded in the "date and time", the use ID is recorded in the "use ID", the approval request amount is recorded in the "withdrawal amount", and the store ID is recorded in the "store ID". The "Balance" field is updated with the amount after withdrawal automatically calculated. Normally, the balance is zero.

Next, the payment program 22 opens the store information file 57 of the corresponding store according to the store ID, and adds a new record. Then, the program execution date and time, the prepaid ID, the prepaid ID, the use ID, and the approval request amount are recorded in the "date and time", "prepaid ID", and "approval amount", respectively. In the "Balance" field, the amount after deposit is automatically calculated and updated.

After that, the payment program 22 fills the funds from the corporate account 61. That is, the company account information file 521 is opened and a new record is added. Then, the program execution date and time is recorded in “date and time”, and the approval request amount is recorded in “withdrawal amount”. The "Balance" field is updated with the amount after withdrawal automatically calculated. Then, the shared account information file 522 is opened, and the program execution date and time is recorded in the "date and time" and the approval request amount is recorded in the "deposit amount".

In this way, the payment program 22 transfers funds in the order of shared account 62, individual account 63, and store account 64. After that, the shared account 62 is moved and filled with the reduced amount of money from the company account 61. The settlement program 22 is programmed so that information is recorded in each of the files 521 to 524 in this manner.

As can be seen from the above description, the settlement program 22 puts the settlement funds into the individual account 63 of the employee who used the settlement and then into the store account 64. Therefore, legally (contractually), the funds for settlement are once owned by the employee and then owned by the store.
Note that the actual remittance is performed from the prepaid account 6 to the bank account owned by the store. This is performed, for example, once every two months, and the amount of settlement during that period is summed up to transfer (transfer) money between bank accounts.

Next, the aggregation of the usage amount of the salary prepaid card C will be described.
As described above, the use of the salary prepaid card C for payment to the store is deducted from the salary. Therefore, it is preferable that the card usage amount is totaled on or before the closing day of the payroll calculation. For example, if the deadline for payroll calculation is the 15th day of every month and the payroll is the 25th day of the month, the aggregation is performed on the 10th day of each month.

As shown in FIG. 1, the system of the embodiment includes a totaling server 3 on which a totaling program 31 is implemented. The aggregation server 3 is a server that aggregates the usage amount of the salary prepaid card C for each employer company and each employee. The total usage amount will be settled using the deposits previously contributed by the employer company.

FIG. 13 is a flowchart showing an outline of the aggregation program 31.
As shown in FIG. 13, the aggregation program 31 opens the employee information file and acquires the prepaid ID of the first record. Then, the usage record information file 551 for the prepaid ID is opened, and the "fixed frame total", "variable frame total", and "special frame total" are acquired respectively. Next, they are added up, and the amount (total amount of prepaid use) is recorded by adding a new record to the totaling file 32 together with the prepaid ID. The aggregation file 32 is a file created for each employer company at the aggregation time, and is a database file that records the prepaid ID, the total amount of prepaid usage, and the like.

Next, the aggregation program 31 opens the prepaid setting information file 54 and updates the record of the corresponding prepaid ID with the value of the "variable set amount" set to zero. When the "special type" is the gradually increasing type, the value of the "special setting amount" is also set to zero and updated.
In this way, the tallying program 31 successively reads the employee IDs, calculates the total amount of prepaid use, and records the amount in a new record of the tallying file 32. Although omitted in FIG. 13, the operating company actually provides services to a large number of employer companies, and the aggregation program 31 is executed for each employee ID in each employer company. The aggregation file 32 is created for each employer company. The counting file 32 has a file name using a company ID, and can be identified by the company ID.

The operation of the salary prepaid system of such an embodiment will be collectively described below.
The operator solicits each business owner company for the introduction of salary prepaid and signs a contract with the company that has responded. The contract includes the number of payroll prepaid cards issued (the number of prepaid IDs issued) and the initial prepaid set amount per person (one prepaid ID) (prepaid initial value). The contracted business owner company transfers the deposit to the prepaid account 6.
The operator provides the employer company with the number of salary prepaid cards C stated in the contract. At this time, the card provision information file 53 is created, and the prepaid ID of each salary prepaid card C provided is recorded in the file.

In the employer company that has received the prepaid card C for salary, the person in charge of the company operates the terminal 81 of the person in charge of the company to log in to the prepaid issuing server 1. Then, the prepaid issuance page is displayed on the in-company person-in-charge terminal 81, and the employee ID and the employee name are input for each prepaid ID. Click the OK button to confirm on the confirmation screen, and then click the send button. As a result, the registration module is executed, new records are added to the prepaid setting information file 54, and the employee ID and the employee name are recorded. Then, the person in charge in the company passes the payroll prepaid card C associated with the employee ID to the employee, and completes issuing the payroll prepaid card.

The user (employee) for whom the salary prepaid card C is issued uses the salary prepaid card C at any store. That is, the salary prepaid card C is presented to the store at the time of payment. The presented salary prepaid card C is read by the store terminal 9, and the approval request program 91 is executed. If it is not an erasure card, is within the expiration date, and the sum of the total usage amount and the approval request amount in the largest frame (set amount) is less than the set amount, the use approval is returned. When the use approval is returned, the payroll prepaid card C is returned to the user because the payment has been made. At this time, the store terminal 9 is often provided with a simple type printer, and in this case, a record of card usage is printed and handed to the user.

The usage approval program 21 opens the usage record information file 551 of the prepaid ID and adds a new record. Then, the usage request amount is added to the total usage amount for the set amount frame used, and updated. Further, the store information file 57 is searched by the store ID to obtain the store name and the like, and the information is recorded in the record added to the usage record information file 551, and the process ends. Also, a new record is added to the total usage record information file 552, and the store ID, usage request amount, etc. are recorded.

The use approval program 21 executes the payment program 22 as a subroutine. The payment program 22 performs an operation (recording information) of transferring funds from the shared account 62 to the individual account 63 in the prepaid account 6, and then transfers the funds from the individual account 63 to the store account 64 associated with the store ID. After that, the usage request amount is charged from the company account 61 to the shared account 62.

In this way, each use of each salary prepaid card C is approved, and information on each use record is recorded in the use record information file 551 and the total use record information file 552. In addition, each use is immediately settled. When the card closing date arrives, the counting program 31 is executed, the card usage amount is counted for each prepaid ID, and the counting file 32 is created and recorded for each employer company. The aggregated credit card usage is deducted from the salary for each employee.

Since the balance of the corporate account 61 decreases with the use of the card, the employer company adds the deposit to the prepaid account 6. The operator regularly aggregates the total amount of card usage for each employer company and requests additional deposits based on the total amount. The employer company adds a deposit based on this.

Employer companies can change the prepaid amount at any time. Generally, it is done when it becomes necessary to change the prepaid set amount after the salary closing date. In the case of a full-time employee, the prepaid set amount often does not change frequently, but in the case of a part-time job or a part-timer, it may change frequently. For example, if the salary of a part-time job is lower than expected when the salary is closed, the prepaid setting amount will be changed. The person in charge of the company logs in to the management server 4 and displays the prepaid setting amount change page. Then, the employee ID of the employee to be changed is input, and the changed prepaid setting amount is input to update the prepaid setting information file 54. When raising the prepaid set amount once lowered, the person in charge in the company operates the terminal 81 in charge in the company in the same manner. Even in the case of full-time employees, if the pay is increased by a regular increase or the like, the prepaid set amount is appropriately changed.

The contract concluded between the operator and each employer company includes the usage fee for the salary prepaid service. The usage fee is, for example, a monthly fee for one prepaid ID (zero for a prepaid ID that is not used at all), and is totaled and billed monthly.

According to the salary prepaid system of such an embodiment, the employee's salary is paid in advance in the form of a salary prepaid card C. Although there is a limit, employees can pay at the store simply by showing the payroll prepaid card C, which is extremely convenient. Conventionally, it is necessary to withdraw cash from a bank account and charge a prepaid card by oneself, but this embodiment does not have such trouble. Also, since it is not a credit card, there is no pressure to ensure that your bank account has a deposit on the day of withdrawal. Therefore, the psychological usability is also very high.

Employees are usually allowed to apply for advance payment of salary, but according to the system of this embodiment, advance application is not required. When an application is made, the fact is known to the department that processes the application (general affairs department, etc.), so there is a psychological burden on the employee. According to the system of the embodiment, there is no such psychological burden, and usability is very high in this respect as well.

On the other hand, even for employer companies, the prepaid salary system will increase the evaluation by employees, and the impression as a company that gives preferential treatment to employees will increase. For this reason, it can contribute to attracting a large number of excellent human resources, and as a result, can improve corporate performance. At this time, even though prepaid, it is inconvenient if it is a method of individually transferring cash to the employee's account, but it is extremely simple because it is only provided with a prepaid card C with a usage limit. ..

In addition, as described above, a prepaid account 6 is prepared as an account for settlement, and the funds for settlement are once held by the employee and then transferred to the store. This is legally significant in that it makes it clearer that salaries are given to employees, even if they are prepaid, and then used for settlement.

Note that the prepaid account 6 is provided with a shared account 62 and an individual account 63 in addition to the corporate account 61, which has the significance of reducing losses when canceling the use of the salary prepaid service. In implementing the invention of the present application, a configuration may be considered in which the prepaid account 6 is settled without dividing the count. However, the current system does not allow refunds for prepaid cards. If you make a payment without dividing the ownership relationship of the funds put in the prepaid account 6, the entire amount will be prepaid funds, so when you stop using the service, the funds in that account cannot be collected .. Therefore, it can be a big loss in the employer company.

If the ownership relationship is divided in the prepaid account 6 and only the shared account 62 and the individual account 63 are used as the funds for settlement (prepaid funds), the funds of the corporate account 61 can be recovered even when the use of the service is stopped. it can. Therefore, the loss is extremely small. That is, it is sufficient for the shared account 62 to have only the maximum amount of money required for one payment. Since this corresponds to the prepaid set amount for one prepaid ID, the amount is not large. Therefore, if only the maximum amount required for one payment is set as the fund on the shared account 62, and each time it is transferred to the individual account 63 and settled, the fund on the shared account 62 becomes the minimum necessary amount and the loss Even if it becomes, it does not become a problematic amount in the employer company.
In the same sense as a so-called prepaid card (in a narrow sense), it means that the fund is owned by the user himself, so the shared account 62 and the individual account 63 of the prepaid account 6 are the prepaid account. It turns out that. This point is indicated by a broken line in FIG.

In the above explanation, each set amount is changed so that the person in charge in the company accesses the management server 4 and inputs it individually, but it is automatically performed by interlocking with the payroll system or the like. In some cases, it is more convenient, which is preferable. For example, a salary system is often equipped with a function capable of recording an employee ID and the amount of salary paid in a database file of a general-purpose format such as CSV when the salary is closed (hereinafter, this file will be described). Is called salary information file). The setting change program on the management server 4 can be programmed to read the salary information file and automatically change the prepaid setting amount. In this case, for example, 20% of the paid salary can be programmed to be uniformly changed and set as the prepaid set amount. The person in charge in the company sends the salary information file to the management server 4, and the management server 4 executes the prepaid change program with this as an argument.

Further, in the above embodiment, it is possible to use a prepaid money with a special set amount. Therefore, it is possible to use the fixed amount or the amount exceeding the variable amount in the form of advance borrowing, which further enhances the convenience for employees. Also, for employer companies, taking preferential measures for employees, such as setting up front debt, will further improve the corporate image. If the special set amount is to be borrowed in advance, the interest rate may or may not be collected. When collecting an interest rate, the aggregation program 31 is implemented so as to aggregate and distinguish the usage separately from the fixed setting amount and the variable setting amount.

Next, the salary prepaid system of the second embodiment will be described. FIG. 14 is a schematic diagram of a salary prepaid system according to the second embodiment.
In the second embodiment, the payroll prepaid card C can be used not only for the private use of the employee but also for the purpose of payment required for the business of the employer company (hereinafter referred to as the corporate use). ing. This point is different from the above embodiment.

In some cases, all employees are permitted to use the company, but usually, it is limited because it is often a sales employee or executive. Therefore, the prepaid setting information file 54 is provided with a field for recording information on whether or not the employee who uses the salary prepaid card C has a company permit.
In addition, for use for corporate use, the fixed set amount for the prepaid ID is higher than usual. The in-company person in charge of the employer company makes a setting on the set amount change page so that the fixed set amount is set higher than usual for the employees who are permitted to use the company.

There is no particular difference between the use and approval of the salary prepaid card C as in the first embodiment. The changes are that the usage type can be input for the use of the payroll prepaid card C, and the company approval program 42 that approves the use for the company is installed in the management server 4. Is. Incidentally, also in the first embodiment, a structure in which the use type input and the company authentication program are installed and the use can be changed from private to company at any time may be adopted.
FIG. 15 is a schematic diagram showing an example of the structure of the usage record information file 551 in the second embodiment. As shown in FIG. 15, in this embodiment, each record of the usage record information file 551 has a “use type” field and a “company approval” field.

The management server 4 provides a usage input page to each employee (hereinafter referred to as a licensed employee) who is permitted to use the company. FIG. 16 is a schematic view showing an example of a usage input page.
As shown in FIG. 16, the usage input page is configured to display a list of the usage record information of the user closed on the card closing date of the current month. Each authorized employee is provided with a login ID and password to access the usage entry page. The login ID is the same as the prepaid ID, or is a combination of the company ID and the employee ID. When the authorized employee sends a login ID and password to log in using his / her own terminal (PC, smartphone, etc.) 82, the usage input page shown in FIG. 16 is displayed. The module for displaying the purpose input page is programmed to open the usage record information file 551 according to the prepaid ID corresponding to the login ID and display a list of information for the current month as shown in FIG.

As shown in FIG. 16, on the usage input page, each row of the list is provided with a type input field (here, pull-down list) 421 of “company”, “private”, and “other”. A send button 422 is provided on the purpose input page. The send button 422 is an execution button of the type registration module. Each row of the list has a usage ID embedded therein for use of the row. The type registration module is programmed to open the usage record information file 551 of the employee according to the prepaid ID and record the value input in the type input field in the “use type” field of the record of the corresponding use ID. There is. The default value of the "use type" is for company use.

In addition, in this embodiment, the in-company person in charge of the employer company individually approves the use for company use from the in-company person in charge terminal 81. The company approval program 42 is a program for causing this transmission.
Specifically, the company approval program 42 includes a module for displaying the company approval page on the in-house person in charge terminal 81. FIG. 17 is a schematic showing an example of a company approval page.

FIG. 17 shows a state in which a certain prepaid ID is selected. A company approval button is provided on the top page displayed by logging in on the in-house person in charge terminal 81, and when this is clicked, a list of authorized employees is displayed. The module is programmed to open the prepaid setting information file 54 of the company ID according to the login ID, acquire the names of employees whose company permission fields are true values, and list them. When a specific employee is selected from the employees displayed in the list, the company approval page shown in FIG. 17 is displayed.

As shown in FIG. 17, on the company approval page, the usage record information of each salary prepaid card C closed on the card closing day of the current month is displayed in a list. The module for displaying the company approval page is programmed to open the usage record information file 551 according to the prepaid ID and display a list of information for the current month as shown in FIG.
As shown in FIG. 17, each line of the list is provided with a usage type display field 423 and a check box for approval (hereinafter, approval input field) 424. In the usage type display field 423, the value of “usage type” of the usage record information file 551 is displayed. The default value is "company", so unless the authorized employee has changed it, it will be displayed as "company". This point is based on the assumption that it will be used frequently for corporate use, and is considered to significantly reduce the time and effort for inputting changes.
Regarding the use of the line for which “for company” is displayed, the person in charge of the company judges whether or not the company name can be approved from the store name and the description of the store where the payroll prepaid card C is used, and if it is good Check the approval input field (check box) 424.

The company approval page is provided with a send button 425. The send button 425 is an execution button of the company registration module. Each row of the list has a usage ID embedded therein for use of the row. The company registration module opens the usage record information file 551 of the employee according to the prepaid ID. Each record of the usage record information file 551 has a field of “approval for company”. The company registration module acquires the usage ID of the row in which the approval input field 424 is checked, and records the true value in the “company approval” field of the corresponding record of the usage record information file 551. The registration module performs this process for all checked uses. The company representative will do the same for other employees who are approved for use.

On the other hand, in this embodiment, the aggregation program 31 is different from the above embodiment. FIG. 18 is a flow chart showing the outline of the counting program 31 in the second embodiment.
As shown in FIG. 18, also in this embodiment, the counting program 31 reads the first employee ID, opens the prepaid setting information file 54 for the employee ID, and acquires the prepaid set amount. Next, the usage record information file 551 for that employee ID is opened, and the prepaid balance at that time (the value of the field of the prepaid balance of the last record) is acquired. Then, the difference between the two is calculated and temporarily stored in a variable.

Next, the aggregation program 31 calculates the total value of the "usage amount" field of all the records (all records within the aggregation period) for which the "company" field is the true value. Then, the total amount of corporate use is subtracted from the prepaid usage amount. This is the total amount of the employee's private use of the card. The totaling program 31 similarly records the total card usage in the record of the employee ID in the totaling file 32. The aggregation program 31 performs such processing for all employee IDs.

According to this embodiment, the salary prepaid card C can also be used for company use. Therefore, by simply carrying one salary prepaid card C, it is possible to settle the product/service for prepaid prepaid company or personal use, which is extremely convenient. Although the description is omitted, the tallying server 3 also has a program for tallying the company portion, and the tallying server 3 automatically performs settlement of the company portion. Therefore, there is no complication for the user (employee).

Further, as another embodiment, a personal salary prepaid card and a corporate salary prepaid card may be provided to one employee. This means providing one employee with a private prepaid ID and a company prepaid ID. In this way, the employee can use it properly according to the purpose, and it is not necessary to input the change of use, which is more preferable.

Next, the salary prepaid system of the third embodiment will be described. FIG. 19 is a schematic diagram showing a main part of the salary prepaid system according to the third embodiment.
In the third embodiment, the prepaid account 6 is configured as in each of the above embodiments. As shown in FIG. 19, in the third embodiment, the prepaid account (prepaid account in a broad sense) 6 does not include a corporate account. Then, a corporate account account 60 is provided as a bank account different from the prepaid account 6.

The corporate account account 60 is also for filling the shared account 62 in the prepaid account 6. Then, in this embodiment, a debit method is adopted in order to perform real-time fund filling. Specifically, also in this embodiment, the use approval server 2 is also used as the payment server. Then, the use approval server 2 is authorized to debit the corporate account account 60 by the debit method. That is, a debit debit contract is concluded between the employer company and the operator.

The payment program 22 implemented in the use approval server 2 transfers funds from the shared account 62 to the individual account 63 and the store account 64 for payment, and then immediately transfers funds from the corporate account account 60 to the prepaid account by the David method. It is programmed to move to a shared account 62 in 6. Other configurations are the same as those in the first or second embodiment.

In this embodiment, the employer company does not need to deposit the deposit in the prepaid account 6, so the configuration of this part is simplified. That is, the operator does not have to request the deposit, and the employer company does not have to deposit the deposit. Therefore, it is preferable. Also in this embodiment, since the amount of money to be filled at one time is the maximum amount of one use of one salary prepaid card C, a larger amount than that can be made by one debit withdrawal. Absent.

Next, the salary prepaid system of the fourth embodiment will be described. FIG. 20 is a schematic diagram showing an asserting unit of the salary prepaid system according to the fourth embodiment.
The salary prepaid system of the fourth embodiment uses a prepaid service provided by another business operator, and this point is different from each of the above embodiments. For example, there may be a case where a banking company provides a service for issuing a prepaid card based on funds (deposits) in a bank account, and such a company corresponds to another company. Hereinafter, the prepaid card service of another company is referred to as another company service.

A user (business operator) has a prepaid card (hereinafter referred to as another business card) C'issued based on the deposit in his/her bank account (hereinafter referred to as other service account) 600. The other company manages the user account 601 and the store account 602 by the server operated by itself (hereinafter referred to as the other company server), and at the time of settlement, the name of the deposit in the bank account 600 is used. It is transferred to the store account 602 according to the use of the other business card C′.

On the other hand, a shared account 62 also exists in the prepaid account 6 managed by the operating company. Then, in this embodiment, a fund transfer server (not shown) for transferring funds from the prepaid account 6 to another service account 600 by a debit method is provided. The transfer of funds by the fund transfer server is performed by a request from the server of another business. Specifically, a configuration may be adopted in which the funds are automatically moved and charged when the balance in the other business card falls below a certain level. For example, if the user initially deposits a deposit of 50,000 yen and the prepaid setting amount of the salary prepaid service is 50,000 yen, when the balance of the user account 601 falls below 100,000 yen, The fund transfer server fills the bank account 600 by the debit method with the difference from 100,000 yen being limited to 50,000 yen. This is a configuration in which the salary prepaid portion is preferentially used, but a configuration in which the salary prepaid portion is filled up to 50,000 yen when it falls below 50,000 yen may be used. In any case, the filling of the funds is the use of the prepaid money in the above embodiment.

According to this embodiment, the issuance of the prepaid card, the approval of the use, and the settlement are performed by another company, so that the burden on the business of the operator of the salary prepaid service is reduced. In this embodiment, it is quite possible that users (employees) belonging to one employer company use different service providers, so the operator of the salary prepaid service is different from other service providers. It will partner to provide a payroll prepaid service.

In each of the above-mentioned embodiments, the source of the prepaid money is a deposit deposited by the employer company in the prepaid account (bank account) 6, and therefore the prepaid money is a cash deposit in accounting. However, in carrying out the present invention, the prepaid money may be another type of asset/fund. For example, the prepaid account may be an account related to currency-denominated assets. In this case, the employer deposits the deposit in the prepaid account in the form of currency denominated assets. Further, the prepaid money may be virtual currency, crypto assets, tokens or other electronic money. A token is an asset issued using an existing blockchain. Furthermore, the prepaid money may be points in a so-called point card. For example, the salary may be prepaid in the form of charging the point card used in the cashback service (in the form of points), which may be used. In this case, the user (employee) can also use the points in the cashback service and the points paid in advance in total.
The prepaid money can also be a fund in a so-called smart payment (smartphone payment) service as an example of other electronic money. Among smart payments, a service that adopts a prepaid type payment method is familiar with the system of the embodiment. For example, in the service using the QR code (registered trademark), it is necessary to charge the funds in advance, and the funds may be the prepaid money in the embodiment. Further, even in the case of the service by the non-contact IC, the ex post facto settlement may be the prepaid money in the embodiment instead of the payment by the credit (credit). Further, even in the case of a carrier pay that is settled together with the payment to the communication company, the payment may be appropriated by the prepaid money in the embodiment.

In each of the above embodiments, the payroll prepaid card C is an example of an ID carrier. In carrying out the present invention, since the prepaid ID may be presented to the store, it may be an ID carrier of another type. For example, the ID carrier may be a mobile terminal such as a smartphone or tablet PC. There may be a configuration in which the prepaid ID is displayed on the mobile terminal and presented to the store, or near field communication (NFC) is performed between the mobile terminal and the store terminal 9 to acquire information.
In the case of smart payment in which authentication is performed using a QR code (registered trademark), a smartphone that displays the QR code (registered trademark) is an ID-carrying item. In the case of performing payment authentication with a smartphone to which some authentication information (password, fingerprint, etc.) has been input, the smartphone to which such authentication information has been input is an ID-bearing object.

Furthermore, the ID carrier may be the user (employee) himself. For example, various technologies have been developed for authenticating with biometric feature points such as fingerprints, veins, retinas, and voiceprints, and such biometric feature portions can be used as an ID carrier. In this case, the store terminal 9 has a function of reading such a biometric characteristic portion, and the information of the read biometric characteristic portion is sent to the use approval server 2 together with the usage request amount. The storage unit 5 stores a file in which the prepaid ID and the information of the biometric characteristic portion are associated and recorded, and the use approval server 2 accesses the file to obtain the prepaid ID and approve the use. I do.
The ID carrier may also be a so-called deposit card. A deposit card is generally a credit card that requires a deposit (security deposit) for issuance. In the present invention, for example, for a salary prepaid card C, a deposit may be deposited in addition to the deposit. If the deposit becomes zero and it becomes impossible to fill the usage, the deposit may be withdrawn and settled. Such a salary prepaid card C can be called a deposit card because a deposit is provided at the time of issuance.

In each of the above embodiments, personal authentication (password) is not required when using the salary prepaid card C, but password authentication may be performed if necessary. In some cases, the user simply verbally conveys the prepaid ID to the store, in which case password authentication is usually performed. Also, in the case of using a card, password authentication may be performed in consideration of security. Mobile terminals such as smartphones are usually unnecessary because password authentication is often performed as a function of the device when the device is started up. In any case, when password authentication is performed, an authentication file in which the password is recorded is stored in the storage unit 5, and the use approval server 2 approves the use by accessing this file.
If identity verification is required for use, the payroll prepaid card C will be provided after identity verification. That is, it is provided after confirming the identity by a method such as registered mail limited to the person.

Further, in each of the above embodiments, the store computer is the store terminal 9, but there may be other cases. For example, when prepaid money is used in Internet shopping, a server that provides a shopping site may send an approval request, and in this case, that server is a store-side computer. In addition, a user (employee) may operate a terminal to request approval and send the result of approval for use to a server of a shopping site. In this case, the terminal operated by the user is the store-side computer. Further, the payment agent may make payment, the server operated by the payment agent may be the computer on the store side, and the terminal operated by the person in charge in the payment agent may be the computer on the store side.

1 Prepaid Issuing Server 11 Card Issuing Program 2 Usage Approval Server 21 Usage Approval Program 22 Payment Program 3 Aggregation Server 31 Aggregation Program 4 Management Server 5 Storage 54 Prepaid Settings Information File 6 Prepaid Account 61 Corporate Account 62 Shared Account 63 Individual Account 64 Stores Account 7 Amount increase server 71 Amount increase program 81 In-house person in charge Terminal 9 Store terminal C Salary prepaid card (ID carrier)

Claims (12)

1. A payroll prepaid system used when an employer company pays employees in advance,
   It includes a use approval server that approves the use of prepaid money, a totaling server that totals the amount of prepaid money used, and a storage unit.
   The storage unit stores a prepaid setting information file recording the prepaid setting amount set according to the working status of the employee, and a usage record information file recording the usage record of the prepaid money,
   The usage record information file is a file in which a prepaid ID for identifying an employee who has a right to use the prepaid money and a usage amount of the prepaid money within the aggregation period are recorded.
   The use approval server is a server that accepts access from a store-side computer via the network, and when the store-side computer sends the prepaid ID and the usage request amount via the network, up to that point regarding the prepaid ID. If the sum of the total amount of prepaid money used and the requested usage amount sent is less than or equal to the prepaid setting amount, the usage approval information is sent to the store side computer, and the usage requested amount is used for the prepaid ID. It is a server that records in information files.
   The aggregation server is a server that obtains the total amount of prepaid money used within the aggregation period from the usage record information file and records it in the aggregation file in order to deduct the total amount of usage from the salary paid on the payday. A payroll prepaid system that is characterized by being.
2. In the storage unit,
   A prepaid account information file that records information on the prepaid account that has deposited funds for the use of the prepaid money is stored.
   In the prepaid account information file, the information of the individually owned deposit, which is the deposit individually owned by the employee for each prepaid ID, and the information of the store owned deposit, which is the deposit owned by each store, are recorded.
   Regarding the use of the prepaid money approved by the use approval server, there is provided a settlement server for transferring the usage request amount from the individual ownership deposit related to the prepaid ID used for the usage to the store ownership deposit related to the store. The salary prepaid system according to claim 1.
3. The prepaid information file includes information on company-owned deposits, which are deposits deposited by the employer company for the use of the prepaid money, and all the rights to belong to the employer company and use the prepaid money. Information on shared deposits, which are deposits jointly owned by employees, is recorded,
   The settlement server is a server that, when transferring the usage request amount to the store-owned deposit, transfers the usage request amount from the shared deposit to the individual-owned deposit, and then to the store-owned deposit,
   The filling server is provided for transferring the usage request amount from the corporate-owned deposit to the shared deposit when the payment server transfers the usage requested amount from the shared deposit to the individual ownership deposit. Salary prepaid system.
4. The usage record information file records whether or not the use of the prepaid money is for the employer company, and the record of whether or not the use is for the employer is made by the person in charge of the employer company or Employees related to prepaid ID can change it by operating the terminal,
   The said totaling server is a server which calculates the total of the said usage request amount for each non-company use among the usage request amounts approved during the counting period for each prepaid ID. Payroll prepaid system.
5. 5. The prepaid setting information file stores an employee ID, which is information for identifying an employee in the employer company, in a state of being associated with the prepaid ID. The salary prepaid system described in the information.
6. In the prepaid setting information file, prepaid money initial values are recorded,
   The prepaid setting amount is initially the same value as the prepaid amount initial value,
   There is a management server that can be accessed from a terminal operated by a person in charge at the employer company.
   The salary prepaid according to any one of claims 1 to 5, wherein the management server is implemented with a setting amount changing program for changing the prepaid setting amount according to a request from a terminal operated by a person in charge in the company. system.
7. The prepaid set amount is a variable set amount that fluctuates during the aggregation period.
   There is an amount increase server that gradually increases the prepaid set amount, which is a variable set amount, according to the employment status of employees within the aggregation period.
   7. The salary prepaid system according to claim 1, wherein the amount-increasing server is a server which records each increased prepaid setting amount in the prepaid setting information file.
8. The prepaid set amount is a fixed set amount that is constant during the aggregation period and a variable set amount that fluctuates during the aggregation period.
   In the prepaid setting information file, a fixed set amount and a variable set amount are stored for each prepaid ID.
   There is an amount increase server that gradually increases the prepaid set amount, which is a variable set amount, according to the employment status of employees within the aggregation period.
   The amount increase server is a server that records each increased variable setting amount in the prepaid setting information file.
   The use approval server compares the fixed setting amount and the variable setting amount at the time when the approval request is transmitted, adds the total amount of use relating to the larger setting amount and the approval request amount, and adds the sum. 7. The salary prepaid system according to claim 1, wherein the server is a server that transmits the use approval when the amount is less than or equal to the larger set amount.
9. In the prepaid setting information file, in addition to the prepaid setting amount, a special setting amount that is a limit amount of use of the prepaid amount that does not depend on working conditions and can exceed the labor claim is recorded for each prepaid ID,
   The use approval server compares the prepaid setting amount and the special setting amount at the time when the approval request is transmitted, and adds the total amount of use relating to the larger setting amount and the approval request amount, and adds them. 9. The salary prepaid system according to claim 1, wherein the salary prepaid system is a server that transmits the use approval when the amount is less than or equal to the larger set amount.
10. A special setting amount increasing server is provided which gradually increases the special setting amount within the aggregation period. The special setting amount increasing server is a server which records the increased special setting amount in the prepaid setting information file. The payroll prepaid system according to claim 9, wherein the payroll prepaid system is provided.
11. The salary prepaid system according to any one of claims 1 to 10, wherein the prepaid money is a currency-denominated asset, a virtual currency, a cryptographic asset, points in a point card, a token, or electronic money.
12. The prepaid ID is information presented to the store while being carried on an ID carrier,
    The payroll prepaid system according to claim 1 to 11, wherein the ID carrier is a card, a mobile terminal, or an authenticateable biological feature portion.

Images