WO2024014108A1

WO2024014108A1 - Payment calculation system

Info

Publication number: WO2024014108A1
Application number: PCT/JP2023/018180
Authority: WO
Inventors: 恵理土田; 千恵子横田; 崇彦高田; 匠土岐; 忍内田
Original assignee: 株式会社バイトルヒクマ
Priority date: 2022-07-15
Filing date: 2023-05-15
Publication date: 2024-01-18

Abstract

Provided is a payment calculation system suitable for minimizing the amount paid of transportation cost.　A commuting transportation cost calculation server 100 acquires, from an employee-by-employee route information table 406, fare information related to daily transportation cost calculation, the fare information corresponding to a commuting route of a payment recipient and including regular fare and one-month commuter pass fare. The commuting transportation cost calculation server 100 then acquires, from personal calendar information in a storage device 42, information regarding the number of commuting days within a period subject to the calculation. Then, on the basis of the fare information and the information regarding the number of commuting days acquired, the lower of an actual cost payment amount, which is a transportation cost payment amount corresponding to the number of commuting days or the number of scheduled commuting days within the period subject to the calculation and calculated using the regular fare, and a discounted commuter pass cost payment amount, which is determined by employing the one-month commuter pass fare as the transportation cost payment amount corresponding to the number of commuting days or the number of scheduled commuting days within the period subject to the calculation.

Description

Payment calculation system

The present invention relates to a payment calculation system that calculates the amount of transportation expenses paid to recipients.

Conventionally, as a technique for calculating the payment amount of commuting transportation expenses, for example, the technique described in Patent Document 1 is known.

The technology described in Patent Document 1, for example, when a new application for commuting transportation expenses occurs and the applied commuting route is to be used from the middle of the month, the application is based on the 6-month commuter fee and the fractional number of days in the applicable month. The system calculates a daily pro-rata amount for commuting expenses, and pays this pro-rated amount for the corresponding month.

Japanese Patent Application Publication No. 2016-192201

However, the technology described in Patent Document 1 is configured to calculate and pay the daily pro-rata amount based on a 6-month subscription, so the total actual cost for the relevant month will be higher than the pro-rata amount. . In other words, those eligible for benefits will have to pay actual expenses that exceed the amount they receive. In addition, when paying a fractional number of days based on actual expenses, depending on the number of fractional days, paying one month's commuter pass may be cheaper than the amount paid based on actual expenses. Similarly, in the case of a work system that includes a mix of telecommuting and commuting, depending on the number of commuting days in a given month, the amount paid can be kept lower by paying the monthly commuter fee rather than paying by actual expenses. There are cases where it is possible. However, the technique described in Patent Document 1 does not assume such a situation.

Therefore, the present invention has been made by focusing on the unresolved problems of the conventional technology, and aims to provide a payment calculation system suitable for reducing the amount of transportation expenses paid. .

[Invention 1] In order to achieve the above object, the payment calculation system of Invention 1 calculates the transportation expenses corresponding to the scheduled number of commuting days of the calculation target period of the payment recipient regarding the commuting route that the payment recipient can use for commuting. A payment calculation system for calculating a payment amount, wherein the fare information corresponding to the commuting route of the person to be paid is acquired from a fare information storage means that stores fare information regarding the fare required for commuting on the commuting route. The number of scheduled commuting days related to the scheduled number of commuting days for the calculation target period is obtained from the information acquisition means and the scheduled commuting days information storage means for storing the scheduled number of commuting days information regarding the number of scheduled commuting days recorded by the eligible person for each payment. Based on the scheduled commuting days information acquisition means that acquires information, the fare information acquired by the fare information acquisition means, and the scheduled commuting days information acquired by the scheduled commuting days information acquisition means, before the expiration of the calculation target period, a first payment amount calculation means for calculating a first payment amount which is a transportation expense payment amount corresponding to the scheduled number of commuting days in the calculation target period; and payment information regarding the first payment amount calculated by the first payment amount calculation means. and a payment information generating means for generating payment information for prepaying the first payment amount.

With such a configuration, the fare information acquisition means acquires the fare information from the fare information storage means, and the scheduled commuting days information acquisition means acquires the scheduled commuting days information from the scheduled commuting days information storage means. Then, the first payment amount calculation means calculates the first payment amount before the expiration of the calculation period based on the acquired fare information and scheduled commuting days information, and the payment information generation means calculates the first payment amount based on the acquired fare information and scheduled commuting days information. Payment information regarding the payment amount is generated. The first payment amount is calculated before the expiration of the calculation period, and the payment information regarding the first payment amount is generated as payment information for prepaying the first payment amount, so the number of scheduled commuting days recorded by the recipient Transportation expenses will be paid in advance based on the following.

Here, the first fare is, for example, a regular fare on public transportation or individual transportation, or an IC fare using an IC card, and the second fare is, for example, a commuter pass or a commuter pass on public transportation or individual transportation. This applies to fares that are cheaper than regular fares using tickets.

Additionally, this system may be realized as a single device, terminal, or other device, or may be realized as a network system in which multiple devices, terminals, and other devices are communicably connected. In the latter case, each component may belong to any of a plurality of devices, etc., as long as they are communicably connected. The same applies to the payment calculation systems of inventions 3, 4, and 6 below.

[Invention 2] Furthermore, in the payment calculation system of Invention 1, the actual number of commuting days information storage means for storing the actual number of commuting days information regarding the actual number of commuting days of the person to be paid, the calculation target period. Actual commuting days information acquisition means for acquiring actual commuting days information regarding the actual commuting days of A second payment amount calculation means that calculates a second payment amount which is a transportation allowance payment amount corresponding to the actual number of commuting days during the calculation period, and the second payment amount calculated by the second payment amount calculation means is the first payment amount. If the second payment amount is smaller than the first payment amount, the second payment amount calculated by the second payment amount calculation means and the second payment amount calculation means that generates shortage payment information for paying the shortage amount is smaller than the first payment amount. In this case, a collection information generation means is provided for generating collection information for collecting overpayments.

With this configuration, the actual commuting days information acquisition means acquires the actual commuting days information from the actual commuting days information storage means, and the second payment amount calculation means calculates the acquired fare information and actual commuting days information. The second payment amount is calculated based on this. If the second payment amount is larger than the first payment amount, the shortage payment information generation means generates shortage payment information for paying the shortage amount. On the other hand, if the second payment amount is smaller than the first payment amount, the collection information generation means generates collection information for collecting the overpayment.

[Invention 3] Furthermore, the payment calculation system of Invention 3 calculates the amount of transportation expense payment corresponding to the scheduled number of commuting days of the recipient of the payment in the calculation period for the commuting route that the recipient of the payment can use for commuting. The calculation system includes a fare information storage means that stores fare information regarding fares including a first fare required for commuting on the commuting route and a second fare that is cheaper than the first fare. From the fare information acquisition means for acquiring the fare information corresponding to the route, and the scheduled commuting days information storage means for storing the scheduled commuting days information regarding the scheduled commuting days recorded by the eligible person for each payment eligible person. A scheduled commuting days information acquisition means for acquiring scheduled commuting days information regarding the scheduled commuting days for the calculation target period, and based on the fare information acquired by the fare information acquiring means and the scheduled commuting days information acquired by the scheduled commuting days information acquiring means. a first payment amount calculation means for calculating the amount of transportation expenses to be paid corresponding to the scheduled number of commuting days in the calculation period before the expiration of the calculation period using the first fare or the second fare; Payment information regarding the first lower payment amount, which is the lower of the payment amount related to the first fare and the payment amount related to the second fare in the calculation, based on the calculation result of the payment amount calculation means, A payment information generating means for generating payment information for prepaying the first low payment amount, and an actual commuting days information storage means for storing actual commuting days information regarding the actual number of commuting days of the person to be paid, for the calculation target period. The calculation is performed based on the actual commuting days information acquisition means for acquiring the actual commuting days information regarding the actual commuting days, the fare information acquired by the fare information acquiring means and the actual commuting days information acquired by the actual commuting days information acquiring means. a second payment amount calculation means that calculates the transportation allowance payment amount corresponding to the actual number of commuting days in the target period using the first fare or the second fare; and the calculation based on the calculation result of the second payment amount calculation means. If the second lower payment amount, which is the lower of the payment amount for the first fare and the payment amount for the second fare, is greater than the first lower payment amount, there is a shortage to cover the shortfall. If the second lower payment amount is smaller than the first lower payment amount based on the calculation result of the insufficient payment information generation means that generates payment information and the second payment amount calculation means, the overpayment amount is collected. and collection information generation means for generating collection information for the collection.

With such a configuration, the fare information acquisition means acquires the fare information from the fare information storage means, and the scheduled commuting days information acquisition means acquires the scheduled commuting days information from the scheduled commuting days information storage means. Then, based on the acquired fare information and scheduled commuting days information, the first payment amount calculation means determines whether the transportation expense payment amount corresponding to the scheduled number of commuting days is the first fare or the second fare before the expiration of the calculation target period. is calculated, and the payment information generation means generates payment information regarding the first low payment amount.

Further, the actual commuting days information acquisition means acquires the actual commuting days information from the actual commuting days information storage means, and the second payment amount calculation means calculates the actual commuting days based on the acquired fare information and the acquired actual commuting days information. The transportation expense payment amount corresponding to the above is calculated using the first fare or the second fare. If the second low payment amount is larger than the first low payment amount, the shortfall payment information generation means generates shortfall payment information for paying the shortfall. On the other hand, if the second low payment amount is smaller than the first low payment amount, the collection information generation means generates collection information for collecting the overpayment.

[Invention 4] Furthermore, the payment calculation system of Invention 4 calculates the amount of transportation expense payment corresponding to the scheduled number of days of commuting for the calculation target period of the recipient of the payment, regarding the commuting route that the recipient of the payment can use for commuting. The calculation system includes a fare information storage means that stores fare information regarding fares including a first fare required for commuting on the commuting route and a second fare that is cheaper than the first fare. A fare information acquisition means for acquiring the fare information corresponding to the route, and a usage date information storage means for storing usage date information regarding the usage date of the commuting route of the person to be paid, for the commuting route in the calculation target period. A usage start date information acquisition means for acquiring usage start date information regarding the usage start date, and a scheduled commuting days information storage means for storing, for each of the payment recipients, scheduled commuting days information regarding the scheduled commuting days recorded by the payment recipient. a scheduled commuting days information acquisition means for acquiring scheduled commuting days information regarding the scheduled commuting days for the calculation target period; fare information acquired by the fare information acquiring means; and scheduled commuting days acquired by the scheduled commuting days information acquiring means. Based on the information and the usage start date information acquired by the usage start date information acquisition means, before the expiration of the calculation target period, the transportation expense payment amount corresponding to the scheduled number of commuting days in the calculation target period is calculated by the first fare or the usage start date information. A first payment amount calculation means that calculates using the second fare, and based on the calculation result of the first payment amount calculation means, the first payment amount related to the first fare and the second payment amount related to the second fare of the calculation. and a payment information generating means for generating payment information regarding one of the two payment amounts and for prepaying the payment amount.

With such a configuration, the fare information acquisition means acquires fare information from the fare information storage means, the usage start date information acquisition means acquires the usage start date information from the usage date information storage means, and the scheduled commuting days are calculated. The information acquisition means acquires the scheduled number of commuting days information from the scheduled commuting days information storage means. Then, the first payment amount calculation means calculates the transportation expenses payment amount corresponding to the scheduled number of commuting days, based on the acquired fare information, scheduled commuting days information, and use start date information, before the expiration of the calculation period. It is calculated based on the fare or the second fare, and the payment information generation means generates payment information regarding one of the first payment amount and the second payment amount.

[Invention 5] Furthermore, in the payment calculation system of Invention 4, the second fare is cheaper than the first fare when the number of days in which the commuting route is used is more than a predetermined number of days, The payment information generation means generates payment information regarding the second payment amount when at least one of one or more of the following conditions 1 to 5 is satisfied, and when the one or more conditions are satisfied. If the first payment amount is not satisfied, payment information regarding the first payment amount is generated.
(Condition 1) The usage start date is a date included in a predetermined period from the start of the calculation target period to the reference date.
(Condition 2) The index that increases according to the number of days from the reference date before the usage start date in the calculation target period to the usage start date is less than or equal to a predetermined value.
(Condition 3) An index that increases according to the number of days from a reference date later than the usage start date in the calculation target period to the usage start date is equal to or greater than a predetermined value.
(Condition 4) The index that decreases according to the number of days from the reference date before the usage start date in the calculation target period to the usage start date is a predetermined value or more.
(Condition 5) The index that decreases according to the number of days from the reference date after the usage start date in the calculation target period to the usage start date is less than or equal to a predetermined value.

With such a configuration, the payment information generation means generates payment information regarding the second payment amount when at least one of conditions 1 to 5 is satisfied, and the payment information regarding the second payment amount is generated. If none of the conditions are satisfied, payment information regarding the first payment amount is generated.

Here, the reference date corresponds to, for example, the first day or last day of the calculation period.
[Invention 6] Furthermore, the payment calculation system of Invention 6 calculates the amount of transportation expense payment corresponding to the scheduled number of commuting days of the recipient of the payment in the calculation period for the commuting route that the recipient of the payment can use for commuting. The calculation system includes a fare information storage means that stores fare information regarding fares including a first fare required for commuting on the commuting route and a second fare that is cheaper than the first fare. From the fare information acquisition means for acquiring the fare information corresponding to the route, and the scheduled commuting days information storage means for storing the scheduled commuting days information regarding the scheduled commuting days recorded by the eligible person for each payment eligible person. The commuting schedule of the person eligible for payment is calculated from a scheduled commuting days information acquisition means for acquiring information on the scheduled commuting days regarding the scheduled commuting days for the calculation target period, and a threshold storage means for storing a threshold value of the number of days of use of the commuting route for each commuting route. a threshold value acquisition means for acquiring the threshold value corresponding to the route; and based on the fare information acquired by the fare information acquisition means, the scheduled commuting days information acquired by the scheduled commuting days information acquisition means, and the threshold value acquired by the threshold value acquisition means. a first payment amount calculation means for calculating the amount of transportation expenses to be paid corresponding to the scheduled number of commuting days in the calculation period before the expiration of the calculation period using the first fare or the second fare; Payment information regarding one of the first payment amount related to the first fare and the second payment amount related to the second fare in the calculation, based on the calculation result of the payment amount calculation means, and payment information generation means for generating payment information for prepaying the amount.

With such a configuration, the fare information acquisition means acquires fare information from the fare information storage means, the scheduled commuting days information acquisition means acquires the scheduled commuting days information from the scheduled commuting days information storage means, and the threshold value is acquired. The means obtains the threshold value from the threshold value storage means. Then, based on the acquired fare information, scheduled commuting days information, and threshold value, the first payment amount calculation means determines whether the transportation expenses payment amount corresponding to the scheduled number of commuting days is the first fare or the first fare or the first payment amount before the expiration of the calculation target period. 2 fares, and the payment information generation means generates payment information regarding one of the first payment amount and the second payment amount.

[Invention 7] Further, in the payment calculation system of Invention 7, in the payment calculation system of Invention 6, the payment information generation means satisfies at least one of one or more of the following conditions 1 to 12. Then, payment information regarding the second payment amount is generated, and when none of the one or more conditions is satisfied, payment information regarding the first payment amount is generated.
(Condition 1) The threshold value is a first threshold value indicating the boundary number of days in which the first payment amount exceeds the second payment amount, and the scheduled number of commuting days in the calculation period is the number of days at which the first payment amount exceeds the second payment amount. It is equal to or higher than the first threshold value.
(Condition 2) The threshold value is the first threshold value, and the scheduled number of non-commuting days in the calculation target period is less than the first threshold value.
(Condition 3) The threshold value is a second threshold value that indicates the boundary number of days in which the first payment amount exceeds the second payment amount for the scheduled number of commuting days per week in the calculation period, and the number of scheduled commuting days per week. is greater than or equal to the second threshold.
(Condition 4) The threshold value is the second threshold value, and the scheduled number of non-commuting days per week is less than the second threshold value.
(Condition 5) The threshold value is a third threshold value in which the first index, which increases according to the scheduled number of commuting days in the calculation period, indicates a boundary value at which the first payment amount exceeds the second payment amount; One index is greater than or equal to the third threshold.
(Condition 6) The threshold value is the third threshold value, and the second index that increases according to the scheduled number of non-commuting days in the calculation target period is less than the third threshold value.
(Condition 7) The threshold value is a fourth threshold value in which the third index, which increases according to the scheduled number of commuting days per week during the calculation period, indicates a boundary value at which the second payment amount exceeds the first payment amount. , the third index is greater than or equal to the fourth threshold.
(Condition 8) The threshold value is the fourth threshold value, and the fourth index that increases according to the scheduled number of non-commuting days per week in the calculation target period is less than the fourth threshold value.
(Condition 9) The threshold value is a fifth threshold value in which a fifth index that decreases according to the scheduled number of commuting days in the calculation period indicates a boundary value at which the first payment amount is less than the second payment amount, and 5 indicators are less than the fifth threshold.
(Condition 10) The threshold value is the fifth threshold value, and the sixth index that decreases according to the scheduled number of non-commuting days in the calculation target period is equal to or higher than the fifth threshold value.
(Condition 11) The threshold value is a sixth threshold value in which the seventh index, which decreases according to the scheduled number of commuting days per week in the calculation period, indicates a boundary value at which the first payment amount falls below the second payment amount. , the seventh index is less than the sixth threshold.
(Condition 12) The threshold value is the sixth threshold value, and the eighth index that decreases according to the scheduled number of non-commuting days per week in the calculation target period is equal to or higher than the sixth threshold value.

With such a configuration, the payment information generation means generates payment information regarding the second payment amount when at least one of conditions 1 to 12 is satisfied, and the payment information regarding the second payment amount is generated. If none of the conditions are satisfied, payment information regarding the first payment amount is generated.

[Invention 8] Furthermore, the payment calculation system of Invention 7 is the payment calculation system of any one of Inventions 4 to 7, and further includes an actual number of commuting days information storage means for storing actual number of commuting days information regarding the actual number of commuting days of the person to be paid. an actual commuting days information acquisition means for acquiring actual commuting days information regarding the actual number of commuting days for the calculation target period; fare information acquired by the fare information acquiring means; and actual commuting days acquired by the actual commuting days information acquiring means. a second payment amount calculation means that calculates a transportation expense payment amount corresponding to the actual number of commuting days in the calculation target period using the first fare or the second fare based on the information; and a calculation by the second payment amount calculation means. Based on the result, the second lower payment amount, which is the lower of the payment amount related to the first fare and the payment amount related to the second fare in the calculation, is the lower payment amount of the first payment amount and the second payment amount. If the amount is larger than the first lower payment amount, based on the calculation results of the shortage payment information generation means for generating shortage payment information for paying the shortfall and the second payment amount calculation means, and a collection information generating means for generating collection information for collecting an overpayment when the second low payment amount is smaller than the first low payment amount.

With this configuration, the actual commuting days information acquisition means acquires the actual commuting days information from the actual commuting days information storage means, and the second payment amount calculation means calculates the acquired fare information and actual commuting days information. Based on this, the amount of transportation expenses to be paid corresponding to the actual number of commuting days is calculated using the first fare or the second fare. If the second low payment amount is larger than the first low payment amount, the shortfall payment information generation means generates shortfall payment information for paying the shortfall. On the other hand, if the second low payment amount is smaller than the first low payment amount, the collection information generation means generates collection information for collecting the overpayment.

As explained above, according to the payment calculation system of Invention 1, the amount of transportation expenses can be paid in advance based on the number of scheduled commuting days recorded by the recipient.

Furthermore, according to the payment calculation system of inventions 2, 3, or 8, when the amount of transportation allowance payment is insufficient for the commuting results, insufficient payment information is generated for paying the shortfall to the recipient. be able to. On the other hand, when the amount of transportation expenses paid is overpaid for the commuting performance, collection information for collecting the overpaid amount from the recipient can be generated.

Furthermore, according to the payment calculation system of invention 3, payment information regarding the first lower payment amount calculated by the first payment amount calculation means is generated, so it is possible to reduce the amount of transportation expense payment. can.

Furthermore, according to the payment calculation system of invention 3 or 8, the amount of transportation expense payment can be suppressed because the shortage or overpayment is adjusted depending on the size of the second lower payment amount and the first lower payment amount.

Furthermore, according to the stipend calculation system of invention 4, stipend information can be generated based on fare information, scheduled commuting days information, and use start date information, so the amount of transportation expenses paid depends on the start date of use of the commuting route. can be suppressed.

Furthermore, according to the payment calculation system of invention 5, payment information can be generated depending on whether conditions 1 to 5 are met, so it is possible to reduce the amount of transportation expenses paid according to more specific aspects.

Furthermore, according to the payment calculation system of invention 6, payment information can be generated based on fare information, scheduled commuting days information, and a threshold value, so the amount of transportation expense payment can be reduced according to the threshold value of the number of days used for the commuting route. be able to.

Furthermore, according to the payment calculation system of invention 7, payment information can be generated based on the success or failure of conditions 1 to 12, so it is possible to reduce the amount of transportation expenses paid according to more specific aspects.

FIG. 1 is a block diagram showing the configuration of a network system according to the present embodiment. It is a diagram showing the hardware configuration of a commuting transportation expense calculation server 100. (a) to (e) are diagrams showing data structures of a company master table 400, a workplace master table 402, an employee information master table 404, an employee-specific route information table 406, and an employee-specific payment information table 408. (a) to (b) are diagrams showing data structures of an employee-based daily payment information table 410 and a department information table 412. It is a flowchart which shows commuting route information new application processing. It is a diagram showing an application information input screen 600. It is a flowchart showing payment information addition/correction processing. 5 is a diagram showing an employee information list screen 500. FIG. 8 is a diagram showing a route list screen 800. FIG. 8 is a diagram showing a first example of a payment information list screen 801. FIG. It is a flowchart which shows supply information generation processing concerning a 1st embodiment. 8 is a diagram showing a second example of a payment information list screen 801. FIG. It is a diagram showing a personal calendar information import screen 900 for importing a CSV file of employee's personal calendar information. It is a flowchart which shows exception processing after daily payment. It is a diagram showing a performance information import screen 901 for importing a CSV file of employee performance information. It is a flowchart which shows supply information generation processing concerning a 2nd embodiment. It is a flowchart which shows supply information generation processing concerning a 3rd embodiment.

[First embodiment]
〔composition〕
A first embodiment of the present invention will be described below. 1 to 15 are diagrams showing a first embodiment.

First, the configuration of this embodiment will be explained.
FIG. 1 is a block diagram showing the configuration of a network system according to this embodiment.

As shown in FIG. 1, the Internet 199 includes a commuting transportation expense calculation server 100 that provides a service for calculating commuting transportation expenses (hereinafter referred to as "commuting transportation expense calculation service"), and a commuting transportation expense calculation server 100 that uses the commuting transportation expense calculation service. It is connected to an employee terminal 200 installed for each employee of the company.

[Hardware configuration of commuting transportation expense calculation server 100]
Next, the configuration of the commuting transportation expense calculation server 100 will be explained.

FIG. 2 is a diagram showing the hardware configuration of the commuting transportation expense calculation server 100.
As shown in FIG. 2, the commuting transportation expense calculation server 100 includes a CPU (Central Processing Unit) 30 that controls calculations and the entire system based on a control program, and a control program for the CPU 30 that is stored in a predetermined area in advance. A ROM (Read Only Memory) 32, a RAM (Random Access Memory) 34 for storing data read from the ROM 32, etc. and calculation results necessary in the calculation process of the CPU 30, and mediating data input/output to external devices. These are connected to each other by a bus 39, which is a signal line for transferring data, so that data can be exchanged.

The I/F 38 includes, as external devices, an input device 40 consisting of a keyboard, a mouse, etc. that can input data as a human interface, a storage device 42 that stores data, tables, etc. as files, and a screen input device 42 that stores data, tables, etc. as files. A display device 44 for displaying is connected to a signal line for connecting to the Internet 199.

[Hardware configuration of employee terminal 200]
The employee terminal 200 is composed of a stationary terminal such as the above-mentioned commuting transportation expense calculation server 100, or a portable terminal such as a smartphone or a tablet. In the former case, the hardware configuration will be the same as that of the commuting transportation expense calculation server 100 described above. On the other hand, in the latter case, the hardware configuration consists of a CPU, a ROM that stores programs such as application software and data for executing the program, and data read from the ROM and necessary for the CPU's calculation process. It is composed of a RAM for storing calculation results, and an I/F for mediating data input/output to various attached devices. These are connected to each other by signal lines for data transfer so that data can be exchanged.

The I/F is connected to various attached devices such as a touch panel display input device that can input data and display a screen based on image signals, a storage device, a wireless communication device, a video camera, etc. .

[About various tables]
Next, various tables stored in the storage device 42 of the commuting transportation expense calculation server 100 will be explained.

FIGS. 3A to 3E are diagrams showing data structures of a company master table 400, a workplace master table 402, an employee information master table 404, an employee-specific route information table 406, and an employee-specific payment information table 408.

As shown in FIGS. 3(a) to 3(e), the storage device 42 includes a company master table 400 in which company information is registered, a work place master table 402 in which work place information for each company is registered, and employee information. An employee information master table 404 for registering commuting route information for each employee, an employee-specific route information table 406 for registering commuting route information for each employee, and an employee-specific payment information table 408 for registering commuting transportation expense payment information for each employee are stored. ing.

As shown in FIG. 3(a), one record is registered in the company master table 400 for each combination of company ID and application start date. In each record, main information including company ID, company name, application control classification, employee group classification information, application start date, application end date, last update date, last updater, and other information is registered.

Here, the company ID is information for identifying a company, and is composed of, for example, a unique number for each company (for example, only numbers, or a combination of letters and numbers). In addition, the application control classification is information that sets whether or not applications can be accepted from employees belonging to the company, and the employee group classification information determines the classification of job type, office, affiliation, etc. of the paid employee group and other employee groups. This is the information shown.

As shown in FIG. 3(b), the workplace master table 402 has one record registered for each combination of company ID, workplace ID, and application start date. Each record includes company ID, work ID, work name, work address, calendar ID, start time, end time, fuel unit price type ID, map information, application start date, application end date, last update date, and last update. Main information consisting of persons and other information is registered.

Here, the workplace ID is information for identifying the workplace, and is composed of, for example, a unique number for each workplace (for example, only numbers, a combination of letters and numbers), etc. In addition, the calendar ID is information for identifying a calendar in which business days and holidays are set for each company. and combinations of numbers). In addition, the fuel unit price type ID is information for identifying the fuel unit price type set for each company, and is composed of a unique number (for example, only numbers, a combination of letters and numbers), etc. for each unit price type. be done. The fuel unit price types include unit price types for each fuel such as gasoline (regular), gasoline (high octane), and diesel (light oil), as well as EV (electric vehicle), PHV (plug-in hybrid electric vehicle), and FCV (fuel cell). There are unit price types for each type of eco-friendly vehicle, such as automobiles. Moreover, the map information is information about the nearest station to the place of work.

As shown in FIG. 3C, one record is registered in the employee information master table 404 for each combination of company ID, employee ID, and application start date. Each record includes company ID, employee ID, employee name, employee name (kana), employee postal code (home), employee address (home), telephone number, email address, work ID, work name, department ID, Main information including department name, employee classification, payment rule ID, calendar ID, password, authority level, map information, application start date, application end date, last update date, last updater, and other information is registered. There is.

Here, the department ID is information for identifying the department to which the employee belongs, and is composed of a unique number (for example, only numbers, a combination of letters and numbers), etc. for each department. The employee classification is information for classifying full-time employees, part-time employees, etc., and the authority level is information indicating any one of personnel authority, superior authority, and employee authority. Personnel authority is the authority that allows the user to use all functions related to commuting expenses in this system, and superior authority is the authority that only allows the employee to apply for commuting routes and approve the application contents. The authority is the authority that can only apply for commuting routes. Further, the calendar ID is information for identifying an employee's personal calendar, and is composed of, for example, a unique number for each employee (for example, only numbers, or a combination of letters and numbers). Furthermore, the map information is information about the station closest to the employee's home.

In the employee-specific route information table 406, one record is registered for each combination of company ID, employee ID, and route ID, as shown in FIG. 3(d). Each record includes company ID, employee ID, vehicle ID, route direction type, employee's nearest station, route ID, route, route usage period, 1 month amount, 3 months amount, 6 months amount, 12 months amount, one way amount, and one way amount. Main information including distance, one-way time, number of transfers, route reference date, application start date, application end date, last update date, last updater, and other information is registered.

Here, the route direction type is information indicating the direction in which the means of commuting is used, and is information on an outbound trip, a return trip, or a round trip. Further, the route ID is information for identifying a commuting route, and is composed of, for example, a unique number for each commuting route (for example, only numbers or a combination of letters and numbers). The route is the route from home to work. For example, if the means of commuting is by train, "Home → Walking → Nearest station (home) → Intermediate station → Nearest station (work) → Walking → Work ”, and for example, if the means of commuting is by car, the route would be “home → car → work”. In addition, the 1-month, 3-month, 6-month, and 12-month amounts are the 1, 3, 6, and 12-month regular discount fares for the set commuting method and route direction type, and the one-way amount is the set The route reference date is the reference date on which the commuting route becomes valid. Note that when using a bus as a means of commuting, the amount of the coupon ticket may be additionally registered in addition to the amount of the commuter pass and the one-way amount.

As shown in FIG. 3(e), the employee-specific payment information table 408 has one record registered for each combination of company ID, employee ID, route ID, and payment ID. Each record includes company ID, employee ID, route ID, payment ID, start date, end date, payment date, payment method, payment period, number of payment months, payment/deduction amount, self-pay amount, type, period, Main information including notes, cancellation date, payment details, number of subscription months, number of subscriptions, payment amount, total payment amount, total co-payment amount, and other information is registered.

Here, the payment ID is information for uniquely identifying the payment information, and is composed of, for example, a unique number for each piece of payment information (for example, only numbers, or a combination of letters and numbers). In addition, the payment method is information indicating the method of paying commuting transportation expenses, such as incorporating it into the salary, transferring it to a bank account, or paying in kind (cash).The number of months to be paid and the number of regular months are 1 month, This can be 3 months, 6 months or 12 months. Further, the payment details information is information indicating whether or not the payment is subject to continuous payment, whether the payment cycle is fixed, and whether or not the payment is subject to fare revision processing.

FIGS. 4(a) and 4(b) are diagrams showing the data structures of the employee-based daily payment information table 410 and the department information table 412.

As shown in FIGS. 4(a) and 4(b), the storage device 42 includes an employee-based daily payment information table 410 that registers daily commuting transportation allowance payment information for each employee, and an approver for each department. and a department information table 412 in which information on proxy applicants is registered.

As shown in FIG. 4(a), in the employee-based daily payment information table 410, one record is registered for each combination of company ID, employee ID, route ID, payment ID, and daily payment ID. Each record includes employee ID, company ID, route ID, start date, end date, payment date, payment method, period for which daily payment is applicable, number of days for payment, usage direction type (one way/round trip), number of days, payment amount, and payment amount. Main information including the total amount and other information is registered.

Here, the daily rate ID is information for uniquely identifying the daily rate information, and is composed of, for example, a unique number for each daily rate information (for example, only numbers, or a combination of letters and numbers). In addition, the period for which commuting expenses are to be paid on a daily basis is information that indicates the period for which commuting transportation expenses are calculated on a daily basis, and the number of days for which payment is to be made is information on the number of days in which commuting expenses are paid on a daily basis within the period for which commuting expenses are to be calculated on a daily basis. The direction type (one way/round trip) is information indicating the route direction type used during the payment period. Further, the payment details information is information indicating whether or not the fare is subject to fare revision processing.

As shown in FIG. 4(b), the department information table 412 has one record registered for each department and company. In each record, main information including department ID, company ID, approver ID, proxy applicant ID, application start date, application end date, last update date, last updater, and other information is registered.

Here, the approver ID is the employee ID of an employee who has supervisor authority who has the authority to approve commuting route applications of employees who belong to the department that corresponds to the department ID, and the proxy applicant ID is the same This is the employee ID of an employee who has the authority to apply for a commuting route on behalf of another employee who belongs to the department.

In addition to the above table, the storage device 42 also stores personal calendar information for each employee, including information on the scheduled work days of each month, in association with the company ID, employee ID, and calendar ID. In addition, work performance information regarding each employee's work performance for each month is stored in association with the company ID and employee ID. Further, fare type setting information is stored in association with the company ID, in which a setting method for setting a fare type for calculating an appropriate transportation expense payment amount is determined.

Here, the personal calendar information specifically includes information such as scheduled commuting days, scheduled working days from home, total number of scheduled commuting days, total number of scheduled working days from home, etc. for each month for each employee. , which each employee records himself/herself.

In addition, the work record information includes the days and hours that each employee actually worked each month. Specifically, it includes information on the days and hours of commuting, and the days and hours of work that were carried out while working from home. It includes information on days and working hours, information on the total number of days in which commuting work was performed (hereinafter referred to as "actual number of commuting days"), and information on the total number of days in which telecommuting was performed. Note that the configuration is not limited to this, and other configurations may be used, such as a configuration that does not include information on working hours, a configuration that does not include information on the number of days worked from home, and a configuration that does not include information on the total number of days.

〔motion〕
Next, the operation of this embodiment will be explained.
[New application process for commuting route information]
Next, the operation of the commuting transportation expense calculation server 100 when an employee newly applies for commuting route information will be explained.

FIG. 5 is a flowchart illustrating new commuting route information application processing.
The CPU 30 starts a predetermined program stored in a predetermined area of the ROM 32, and executes a new commuting route information application process shown in the flowchart of FIG. 5 in accordance with the program.

When the commuting route information new application process is executed by the CPU 30, as shown in FIG. 5, the process first moves to step S100.

In step S100, it is determined whether or not a new application request has been received from the employee terminal 200. If it is determined that it has been received (YES), the process moves to step S102, and if it is determined that it has not been received (NO), the process proceeds to step S102. The determination process is repeated until it is received.

Here, a new application for commuting route information is made, for example, when a new employee registers commuting route information for the first time, or when the commuting route changes after moving.

If the process moves to step S102, application information input processing is executed and the process moves to step S104.

FIG. 6 is a diagram showing an application information input screen 600.
Here, when the application information input process is executed, first, application information input screen information is transmitted to the employee terminal 200. As a result, the application information input screen 600 shown in FIG. 6 is displayed on the display device of the employee terminal 200. The employee inputs the commuting route information to be applied for on the application information input screen 600 shown in FIG. 6 via the employee terminal 200.

Specifically, this is a process of accepting input of information to be registered in the employee-specific route information table 406, the employee-specific payment information table 408, and the employee-specific daily payment information table 410. The screen illustrated in FIG. 6 is the first screen displayed, and is switched to the next input screen by selecting the next button 61 displayed at the bottom right of the application information input screen 600. That is, the application information input process is performed over multiple screens.

Specifically, on the application information input screen 600, commuting route information such as means of commuting (vehicle ID), reason for application, home address, route direction type, etc. can be input. Specifically, it is now possible to select one of the three route direction types displayed in the drop-down list, ``outward'', ``return'', and ``round trip'', and input it in the input field 60. ing. In other words, if you only use the outbound trip, if you only use the return trip, or if the commuting routes are different for the outbound and return trips, you can set commuting route information separately for the outbound and return trips.

Additionally, as shown in the "Register only route" checkbox 63 in FIG. 6, only the commuting route can be registered. Here, if the check box 63 is not checked, when a commuting route is registered, the pay information corresponding to the registered commuting route is automatically generated immediately, and the generated pay information is displayed in the employee-specific pay information table. 416. On the other hand, if the check box 63 is checked, even if the commuting route is registered, the automatic generation of payment information is not performed immediately, and the generation work is performed separately by a person in charge of the human resources department or the general affairs department.

The option to "Register route only" is available for employees who commute using a new commuting route mid-month, or employees whose work schedule includes a mix of telecommuting and commuting. This is to respond flexibly to employees, etc. When dealing with such employees, it is difficult to simply use commuter passes and generate payment information in advance. Therefore, it is necessary to calculate the amount of commuting transportation expenses paid on a daily basis based on the actual number of commuting days or scheduled commuting days in the relevant month or each month. In particular, when transportation expenses are paid in advance or on a monthly basis, the total daily payment amount is calculated from the number of scheduled commuting days set for each employee in the corresponding month or each month (hereinafter referred to as "daily transportation expenses"). It is necessary to perform calculations.

In step S104, it is determined whether or not a registration application has been received from the employee terminal 200. If it is determined that the registration application has been received (YES), the process moves to step S106, and if it is determined that it has not been received (NO), the process proceeds to step S106. The process moves to S110.

If the process moves to step S106, information on the department to which the applicant belongs (department ID) is obtained from the employee information master table 404, and approval party information (department ID) corresponding to the obtained department ID is obtained from the department information table 412. The employee ID of the employee who has approval authority is acquired, and the process moves to step S108.

In step S108, an approval route is constructed based on the obtained approval destination information. Thereafter, based on the constructed approval route, an approval request for application information is sent to each approver at the route destination, the series of processes is completed, and the original process is resumed.

As a result, the application is approved and the application is allowed, and if "Register only route" is not selected, the application information and payment information will be updated to the employee-specific route information table 406 and the employee-specific payment information table 408. and is registered in the employee-based daily payment information table 410. On the other hand, if "Register only route" is selected, the application information is only registered in the employee route information table 406 and no payment information is generated.

On the other hand, in step S104, if the process moves to step S110 without receiving a registration application, it is determined whether or not a cancellation request has been received from the employee terminal 200. If it is determined that a cancellation request has been received (YES), a series of If it is determined otherwise (NO), the process moves to step S104.

[Payment information addition/correction process]
Next, a description will be given of the operation when the human resources employee adds payment information to the employee-specific payment information table 408 and the employee-specific daily pro rata payment information table 410 and modifies the registered payment information.

FIG. 7 is a flowchart showing the payment information addition/correction process, FIG. 8 is a diagram showing the employee information list screen 500, FIG. 9 is a diagram showing the route list screen 800, and FIG. 8 is a diagram showing a first example of an information list screen 801. FIG.

Here, when you log in to the commuting expense calculation service provision page with an account that has human resources authority, the top page of the service will be displayed on the display device of the employee terminal 200 of the employee who has human resources authority (hereinafter referred to as "human resources employee"). is displayed. Although not shown, main menu buttons such as "application," "employee information," and "work master" are displayed on this top page. Although not shown, these main menu buttons are always displayed at the top of the screen, and can be selected from pages other than the top page. Then, when the employee who has personnel authority selects the "employee information" menu button (by pressing with a mouse or touching with a finger, etc.) via the employee terminal 200, the employee information shown in FIG. 8 is displayed on the display device. A list screen 500 is displayed. Here, the human resources employee has the authority to perform work related to calculation of commuting transportation expenses.

The payment information addition/correction process is a process executed on the route list screen 800 that is displayed after selecting the employee to be added or modified on the employee information list screen 500 and selecting the route list button 51.

The CPU 30 starts a predetermined program stored in a predetermined area of the ROM 32, and executes the payment information addition/correction process shown in the flowchart of FIG. 7 according to the program.

When the payment information addition/correction process is executed by the CPU 30, as shown in FIG. 7, the process first moves to step S200.

In step S200, based on information from the employee terminal 200, it is determined whether the route modification button 80 has been selected for the commuting route selected from the list of commuting routes of the selected employee displayed on the route list screen 800. . If it is determined that it has been selected (YES), the screen information of the payment information list screen 801 is sent to the employee terminal 200 and the process moves to step S202; if it is determined that it has not been selected (NO), it is selected. The determination process is repeated until.

That is, when the route correction button 80 is selected on the route list screen 800 shown in FIG. 9, the payment information list screen 801 shown in FIG. 10 is displayed on the display device of the employee terminal 200.

Note that in the example shown in FIG. 10, the payment information is not registered because "Register only route" was selected at the time of application.

Returning to FIG. 7, when proceeding to step S202, it is determined whether the add button 82 has been selected on the payment information list screen 801 based on information from the employee terminal 200. If it is determined that it has been selected (YES), screen information of a payment information setting screen (not shown) for setting payment information is transmitted to the employee terminal 200, and the process moves to step S204. If so (NO), the process moves to step S206. As a result, although not shown, a payment information setting screen is displayed on the display screen of the employee terminal 200.

If the process moves to step S204, the payment information addition process is executed, the series of processes ends, and the process returns to the original process.

For example, when a new commuting route is used in the middle of a month, the process of adding prorated payment information corresponds to the process of adding pro rata payment information for the number of days the new commuting route is used in that month. Furthermore, in the case of a work style that includes both telecommuting and commuting, the process of adding pro rata payment information according to the actual number of commuting days or the scheduled number of commuting days in each month is applicable.

Specifically, the human resources employee inputs necessary information such as the pro rata payment period, the number of payment days, and the usage direction type (one-way/round trip) on the payment information setting screen via the employee terminal 200. Pro-rate payment information can be used, for example, if your first day of employment is halfway through the month and you start work in the middle of the month using the commute route you applied for, commuting expenses will be paid on a pro-rata basis only on the working days of that month. This information is set when In addition, for example, if it is necessary to work from home due to the spread of an infectious disease, and if working from home and commuting work are mixed, this is set up in cases where commuting transportation expenses are paid on a daily basis for the days of work. It is information. Therefore, the period eligible for daily pro rata payment is set as the period eligible for pro rata payment.

In addition, if you use the commuter route you applied for in the middle of the month, the period covered by commuting in that month will be the period covered by daily pro-rata payment. For example, if you start commuting using a new commuting route from June 15th, the period from June 15th to June 30th will be set as the period for which you will be eligible for prorated payments. On the other hand, for a work system in which telecommuting and commuting work are mixed (mixed work system), for example, each applicable monthly period is the period eligible for pro rata payment. For example, if a mixed work system is implemented from June 1st, the period from June 1st to June 30th will be set as the period for which the per diem payment will be made. If the mixed work system continues from the next month onwards, each month will be set as a period eligible for pro rata payments.

In addition, by selecting the OK button (not shown) displayed on the payment information setting screen after entering the necessary information, instructions to generate payment information related to daily transportation expenses including the input information will be sent to the commuting transportation expense calculation server. 100. As a result, the commuting transportation expense calculation server 100 generates payment information regarding daily transportation expenses.

On the other hand, if the process moves to step S206 without selecting the add button 81 in step S202, the modify button 83 is selected for the selected payment information on the payment information list screen 801 based on the information from the employee terminal 200. Determine whether or not. If it is determined that it has been selected (YES), the screen information of the payment information setting screen (not shown) is sent to the employee terminal 200 and the process moves to step S208; if it is determined that it is not selected (NO), The process moves to step S210.

In other words, although not shown, if the modify button 83 is selected on the payment information list screen 801 with already registered daily payment information selected, the information is already displayed on the display screen of the employee terminal 200. A payment information setting screen (not shown) in an input state is displayed.

If the process moves to step S208, the payment information correction process is executed, the series of processes ends, and the process returns to the original process.

Here, the payment information modification process is a process for modifying information that has already been input on the payment information setting screen.

Further, in step S206, if the modify button 83 is not selected and the process moves to step S210, it is determined whether or not any other button other than the add button 82 and the modify button 83 has been selected. If it is determined that another button has been selected (YES), the screen information of the screen corresponding to the other button is transmitted to the employee terminal 200 and the process moves to step S212; if it is determined that this is not the case (NO). ) moves to step S202.

If the process moves to step S212, the process corresponding to the other selected button is executed, the series of processes ends, and the process returns to the original process.

As shown in FIG. 10, other buttons include a cancel button, a delete button, a confirm button, and a cancel button. If the Cancel button is selected, periodic cancellation processing is executed, if the Delete button is selected, the selected payment information deletion process is executed, and if the Cancel button is selected, route correction is canceled. Processing to return to route list screen 800 is executed.

[Payment information generation process]
Next, the operation of the commuting transportation expense calculation server 100 when executing the generation process of payment information regarding daily transportation expenses will be explained. Hereinafter, the calculation period for daily prorated transportation expenses will be explained as the calculation target month.

FIG. 11 is a flowchart showing the payment information generation process according to the present embodiment, and FIG. 12 is a diagram showing a second example of the payment information list screen 801. Further, FIG. 13 is a diagram showing a personal calendar information importing screen 900 for importing a CSV file of employee's personal calendar information. Further, FIG. 15 is a diagram showing a performance information importing screen 901 for importing a CSV file of employee performance information.

When the supply information generation process is executed in the CPU 30, as shown in FIG. 11, the process first moves to step S250.

In step S250, it is determined whether there is an instruction to generate payment information. If it is determined that there is a generation instruction (YES), the process moves to step S252, and if it is determined otherwise (NO), the determination process is repeated until there is a generation instruction.

Here, the instruction to generate payment information corresponds to an instruction issued in the payment information addition process in step S204 in the payment information addition/correction process. In addition, this also applies to instructions issued when the batch processing function implemented in the commuting transportation expense calculation server 100 batch-processes the addition of payment information.

In step S252, the work record information or personal calendar information corresponding to the calculation target month of the employee is acquired, and the process moves to step S254.

Specifically, if the calculation target period is the calculation target month, and if you want to pay daily transportation expenses in the month following the target month based on the work performance of the target month, work performance information will be obtained, and for example, the following month's prorated transportation expenses will be paid. If the payment is made in the previous month or the current month, personal calendar information will be obtained.

Here, the commuting transportation expense calculation server 100 acquires the company ID, employee ID, and work record information or personal calendar information of the employee stored in the storage device 42 and corresponding to the month to be calculated. Work performance information and personal calendar information are stored in the storage device 42 as files in a predetermined file format such as a CSV file, and as shown in the example of FIG. 13 or 15, the CSV file of the relevant employee is selected. You can obtain it by importing it. This import can be performed for all employees to be processed when the batch processing function is applied, and if the files of all employees to be processed are imported, the subsequent processing will be performed for all employees. This can now be done in bulk. On the other hand, in the payment information addition/correction process, the file of the selected employee is acquired, and the subsequent process is executed only for the selected employee.

Note that the determination of whether to pay the daily prorated transportation expenses in advance, in the current month, or in the following month is made using, for example, the time information (year, month, day, hour, minute, second) of the RTC (Real Time Clock) built into the commuting transportation expense calculation server 100. The configuration may be such that the determination is made automatically, or the configuration may be configured such that the HR employee selects the selection using a check box or the like.

In step S254, the total number of days of commuting work is obtained from the work performance information for the processing month obtained in step S252, or the total number of scheduled commuting days is obtained from the personal calendar information for the processing month obtained in step S252. After obtaining the information, the process moves to step S256.

In step S256, fare information corresponding to the corresponding employee's commuting route is acquired, and the process moves to step S258. Here, the commuting transportation expense calculation server 100 obtains information about the one-way ticket fare (normal fare) and the monthly commuter pass price (monthly fare) as fare information from the record of the employee in the employee-specific route information table 406. get.

In step S258, the actual amount to be paid is calculated based on the total number of days obtained in step S254 and the one-way fare (normal fare) obtained in step S256. After that, the process moves to step S260.

Specifically, if the same commuting route is used for a round trip, the actual amount paid will be calculated as "actual amount paid = total number of days x one-way amount x 2". On the other hand, if the commuting route is used one-way (only the "outbound" or "return"), the calculation is calculated as "actual expenses paid = total number of days x one-way amount". In other words, if each commuting route is different, the amount of actual expenses paid will be calculated for each commuting route.

In step S260, it is determined whether the actual payment amount calculated in step S258 and the monthly amount obtained in step S254 (hereinafter referred to as "regular discount payment amount") are larger or smaller. Then, based on this determination result, it is determined whether the actual payment amount is lower than the regular discount payment amount, and if it is determined that the amount is lower (YES), the process moves to step S262, and if it is determined otherwise. If so (NO), the process moves to step S264.

If the process moves to step S262, payment information for paying the actual payment amount calculated in step S258 is generated. After that, the process moves to step S266.

On the other hand, if the process moves to step S264, payment information for paying a regular discount payment amount consisting of one month's amount of a commuter pass is generated. After that, the process moves to step S266.

In step S266, the payment information generated in step S262 or S264 is registered in the record of the corresponding employee in the employee-specific payment information table 408 or the employee-specific daily prorated payment information table 410. Thereafter, the series of processing is completed and the original processing is resumed.

Specifically, the commuting transportation expense calculation server 100 stores the generated payment information in the corresponding record of the per-employee daily payment information table 410 for employees whose monthly transportation expenses are paid on a daily basis. For registered employees whose monthly transportation expenses are normally paid in the amount of the commuter pass, they are registered in the corresponding record in the employee-specific payment information table 408.

As a result, as shown in FIG. 12, the payment information regarding the registered daily transportation expenses is displayed on the payment information list screen 801.

[Exception processing after daily payment]
Next, exception handling after the daily transportation allowance is paid will be explained. Here, the post-daily payment exception process is a process that is executed when the daily pro-rata commuting transportation expenses are paid in advance or in the current month.

Specifically, the post-daily payment exception processing is a process that corresponds to the shortage or overpayment of daily pro-rated transportation expenses that may occur when pro-rated transportation expenses are paid in advance or in the current month. Hereinafter, the period to be calculated will be explained as the month to be calculated.

Specifically, in the post-daily payment exception processing, if the daily prorated transportation fee is overpaid, collection information is generated to collect the difference amount, and if the daily prorated transportation fee is insufficient, Generate pro rata payment information for paying the shortfall.

FIG. 14 is a flowchart showing post-daily payment exception processing.
The post-daily payment exception process is a process that is executed when preset execution conditions are met.

The CPU 30 starts a predetermined program stored in a predetermined area of the ROM 32, and executes the post-daily payment exception processing shown in the flowchart of FIG. 14 according to the program.

When the post-daily payment exception processing is executed in the CPU 30, as shown in FIG. 14, the process first moves to step S300.

In step S300, it is determined whether or not the execution condition is satisfied. If it is determined that the execution condition is satisfied (YES), the process moves to step S302; if it is determined that the execution condition is not satisfied (NO), the determination process is continued until the condition is satisfied. repeat.

Here, the execution conditions are set so that they are met, for example, when there is a request from an employee who is eligible for payment, when there is a request from a human resources employee, or when a preset execution timing has arrived. ing. For example, if you purchase a one-month commuter pass because your scheduled commuting days have increased significantly after the daily transportation allowance has been paid, the purchase cost may exceed the actual amount. In this case, there will be a shortage of daily transportation expenses. Furthermore, for example, after the daily pro-rata transportation allowance has been paid using the periodic discount payment amount, the scheduled commuting days have significantly decreased, so if you buy a ticket and go to work, the cost required for commuting may be less than the periodic discount payment amount. In this case, an overpayment of daily transportation expenses will occur.

In this way, when a shortage or overpayment of daily transportation expenses occurs, the execution conditions can be set so that they are met by a request from the employee via the employee terminal 200.

However, if the pro-rated transportation allowance paid in advance exceeds the actual cost of commuting, there is a high possibility that the employee will not proactively request that the overpayment be returned. Therefore, in consideration of such a case, for example, set the execution condition to be met periodically for all employees who are paid daily transportation expenses on a regular basis (for example, on a fixed date every month). You can also do that.

Furthermore, by inputting an instruction to satisfy the execution condition by the human resources employee, it is also possible for the human resources employee to establish the execution condition at any timing.

If the process moves to step S302, the work record information corresponding to the calculation target month of the employee is acquired, and the process moves to step S304. Here, the commuting transportation expense calculation server 100 obtains information on the total number of days of commuting work from the company ID, employee ID, and work performance information corresponding to the target month of the employee stored in the storage device 42. For example, the work performance information can be obtained by storing the work record information in the storage device 42 as a CSV file, and selecting and importing the CSV file of the employee as shown in the example of FIG. This import can be performed for multiple employees, and if multiple employees' CSV files are imported, the subsequent processing can be performed for multiple employees at once.

In step S304, fare information corresponding to the corresponding employee's commuting route is acquired, and the process moves to step S306. Here, the commuting transportation expense calculation server 100 acquires information on the one-way fare (normal fare) and the one-month commuter pass price (one-month fare) from the record of the employee in the employee-specific route information table 406.

In step S306, the payment information corresponding to the month to be calculated for the relevant employee (in this case, payment information indicating that the daily prorated transportation expenses have been paid) is acquired, and the process moves to step S308. Here, the commuting transportation expense calculation server 100 acquires payment information corresponding to the calculation target month from the record of the relevant employee in the employee-based daily payment information table 410.

In step S308, the actual payment amount is calculated based on the total number of days obtained in step S302 and the one-way fare (normal fare) obtained in step S304, and the calculated actual payment amount and the monthly amount obtained in step S304 are combined. Compare and set the lower amount as the actual payment amount. After that, the process moves to step S310.

In step S310, the amount of the payment information for the calculation target month of the employee obtained in step S306 is compared with the actual payment amount set in step S308, and it is determined whether the amount of the payment information is less than or equal to the actual payment amount. . If it is determined that it is less than the actual payment amount (YES), the process moves to step S312, and if it is determined that it is not (NO), the process moves to step S316.

If the process moves to step S312, shortfall payment information for paying the shortfall money is generated, and the process moves to step S314. That is, since the actual payment amount is higher, payment information for paying the difference between the actual payment amount and the payment amount is generated.

In step S314, the insufficient pay information generated in step S312 is registered in the record of the corresponding employee in the employee-based daily pro rata pay information table 410. Thereafter, the series of processing is completed and the original processing is resumed.

On the other hand, if it is determined in step S310 that the amount of the payment information is greater than or equal to the actual payment amount and the process moves to step S316, collection information for collecting overpayments is generated and the process moves to step S318. In other words, since the actual payment amount is lower, the difference between the actual payment amount and the payment amount is collected.

Note that if the amount in the payment information matches the actual payment amount, there is no shortage or overpayment, so the series of processes is ended and the original process is returned to without executing the subsequent process.

In step S318, the collection information generated in step S316 is stored in the storage device 42 in association with the company ID, employee ID, and target month information of the relevant employee. Thereafter, the series of processing is completed and the original processing is resumed. Here, the collection information can be viewed by the human resources employee, and based on this collection information, the human resources employee performs processing such as, for example, subtracting the overpayment amount corresponding to the collection information from the salary payment amount.

〔effect〕
Next, the effects of this embodiment will be explained.
In this embodiment, commuting transportation expense calculation server 100 calculates the daily transportation expense for the commuting route applied for by the employee who is eligible for payment, from the employee-specific route information table 406. Obtain information about the monthly amount (regular discount payment amount) that is the regular fee. In addition, information on the actual number of commuting days or scheduled number of commuting days for the relevant employee during the calculation target period is obtained from the storage device 42, and the amount of actual expenses to be paid is calculated based on the obtained normal fare and the actual number of commuting days or scheduled number of commuting days. . Then, the magnitude of the calculated actual expense payment amount and the obtained regular discount payment amount, which is the monthly amount, is determined, and based on the determination result, it is determined which one is the lower amount. Furthermore, payment information regarding the lower payment amount is generated. Then, the generated payment information is registered in the record of the corresponding employee in the employee-specific payment information table 408 or the employee-specific daily pro rata payment information table 410.

With such a configuration, it is possible to select an amount of daily prorated transportation expenses appropriate for the employee to be paid, and to generate payment information regarding the selected daily prorated transportation expenses.

Furthermore, in this embodiment, when daily transportation expenses are paid in advance or in the current month, depending on the fulfillment of the execution conditions, the corresponding employee's commuting work performance (total number of commuting days) in the target month and the corresponding employee's The actual payment amount is calculated based on the normal fare corresponding to the commuting route, and the lower of the actual payment amount and the monthly amount (regular discount payment amount) is set as the actual payment amount. In addition, we compare the size of the pro-rata transportation expenses (calculated based on the scheduled commuting date) and the actual payment amount corresponding to the per diem payment information for the applicable month for the relevant employee, and if the actual payment amount is lower, the overpayment will be made. Collection information is generated to collect the amount, and when the actual amount paid is higher, pro-rated payment information is generated to pay the shortfall.

With this structure, for example, there may be an exceptional situation where, after the pro-rata transportation allowance has been paid based on the actual amount paid, circumstances change and you purchase a one-month commuter pass, but the purchase cost exceeds the actual amount paid. In the event that a shortage occurs, the amount of shortfall can be paid to the relevant employee. Also, for example, if an exceptional situation arises, such as after you have been paid pro-rated transportation expenses using the regular discount payment amount, circumstances change and you purchase a ticket and commute to work, but the cost of commuting is less than the regular discount payment amount. The overpayment amount can be collected from the relevant employee.

However, since both are judged based on work performance, for example, after the daily transportation allowance is paid based on the actual amount paid, the number of days scheduled for commuting increases significantly, and you purchase a one-month commuter pass, but due to illness or injury, the number of days scheduled for commuting increases significantly. If you are unable to commute to work for the latter half of the day, the judgment will be based on the number of days you actually commuted, so depending on the actual number of commuting days, the actual amount paid may be less than the amount paid in advance and overpayments may be collected. may occur.

[Correspondence]
In the present embodiment, steps S252 to S254 and S302 correspond to the scheduled commuting days information acquisition means of the first or third invention, or the actual commuting days information acquisition means of the second or third invention, and step S256 corresponds to the scheduled commuting days information acquisition means of the inventions 1 to 3. Step S258 corresponds to the first payment amount calculation means of the invention 1 or 3.

Further, in this embodiment, steps S262 to S264 correspond to the payment information generation means of invention 1 or 3, step S308 corresponds to the second payment amount calculation means of invention 2 or 3, and step S312 corresponds to the payment information generation means of invention 1 or 3. Corresponding to the short supply information generation means of the second or third invention, step S316 corresponds to the collection information generation means of the second or third invention.

Furthermore, in the present embodiment, the storage device 42 corresponds to the fare information storage means of the first or third invention, the scheduled commuting days information storage means of the first or third invention, or the actual commuting days information storage means of the second or third invention. , the normal fare corresponds to the first fare of the third invention, and the one-month, three-month, six-month, and 12-month fares of the commuter pass correspond to the second fare of the third invention.

[Second embodiment]
〔composition〕
Next, a second embodiment of the present invention will be described. FIG. 16 is a diagram showing the second embodiment. Hereinafter, only the different parts from the first embodiment will be explained, and the explanation of the overlapping parts will be omitted.

In this embodiment, for a newly applied commuting route, if the usage start date is a date in the middle of the usage start month, the usage start date is determined using a determination method different from the determination method of the first embodiment described above. This embodiment differs from the first embodiment in that the fare type for calculating the daily transportation cost is determined. The other configurations are the same as those of the first embodiment.

In this embodiment, if the start date of the first month of use for a newly applied commuting route is a date included in the first period (for example, from the 1st to the 15th) of that month, the regular discount fare will be applied. Set as the fare type used to calculate the amount of transportation expenses paid for the month of start of use. On the other hand, if the start date of use falls within the second period (for example, 16th to 30th or 31st) of the month of start of use, the normal fare will be used to calculate the amount of transportation expenses paid for the month of start of use. Set as fare type. Hereinafter, this setting method will be referred to as the "first setting method." In other words, the first setting method is an appropriate setting method for calculating the amount of transportation expenses paid for a newly applied commuting route when the start date of use of this route falls in the middle of the month of start of use. It has become.

Note that the first period and second period are set for each applied commuting route. Specifically, the optimal period is set for each commuting route, the month in which usage begins, and the number of business days (number of commuting work days) in that month. Specifically, the period is set so that the amount of transportation expenses paid is appropriate for the target employee.

For example, the railway company corresponding to the commuting route is Railway Company A, and the fares are set so that if the commuter route you applied for is used for 18 days or more, the one-month commuter pass becomes cheaper than the regular fare. shall be. In this case, if weekdays are business days and the usage start month is June, for example, the first period is set from June 1st to June 7th, and the second period is set from June 8th to June 30th. The period is set as follows. Also, for example, if the railway company corresponding to the commuting route is Railway Company B, and the commuter route you applied for is used for 12 days or more, the fares are set so that the one-month commuter pass becomes cheaper than the regular fare. Suppose that In this case, if weekdays are business days and the usage start month is June, for example, the first period is set from June 1st to 15th, and the second period is set from June 1st to June 30th. The period is set as follows. In other words, for railway company A, if the start date of June is within the period from 1st to 7th, the monthly pass will be cheaper than the actual amount paid based on the normal fare, and 8. If the date falls within the period of 30 days to 30 days, the actual amount paid will be cheaper than the monthly subscription fee. Similarly, for railway company B, if the start date of June is between the 1st and 15th, the monthly pass will be cheaper than the actual amount paid, and the period between the 16th and 30th will be lower. If the date is within the period, the actual amount paid will be cheaper than the monthly subscription fee.

As explained above, the first period and the second period are set as the optimal periods for each applied commuting route, and this information is, for example, a commuting route, The information is stored in the storage device 42 in association with the means of transportation (for example, railway company, bus company, etc.), the type of route used, the month in which use begins, and the number of business days (number of commuting days) in the month in which use begins. Below, specify the first and second periods, such as the commuting route, the mode of transportation corresponding to the commuting route, the type of route to be used, the start date of use (year, month, and day), the number of business days in the month of start of use (number of commuting work days), etc. The various information for commuting is referred to as "commuting-related information."

〔motion〕
Next, the operation of this embodiment will be explained.
[Payment information generation process]
Next, the operation of the commuting transportation expense calculation server 100 when executing the generation process of payment information regarding daily transportation expenses when a new application for a commuting route is made will be described.

FIG. 16 is a flowchart showing the payment information generation process according to this embodiment.
When the supply information generation process is executed by the CPU 30, as shown in FIG. 16, the process first moves to step S400.

In step S400, it is determined whether or not there has been a new application for a commuting route. If it is determined that there has been (YES), the process moves to step S402; if it is determined otherwise (NO), judgment is made until there is a new application. Repeat the process.

In step S402, the work history information or personal calendar information for the month in which usage starts corresponding to the newly applied commuting route of the employee is acquired, and the process moves to step S404.

Here, the work record information and personal calendar information include information on the start date of use of the commuting route. Work record information and personal calendar information are stored in the storage device 42 as files in a predetermined file format such as a CSV file, for example, as in the first embodiment. As shown in , it can be obtained by selecting and importing the CSV file of the relevant employee. This import can be performed for all employees to be processed when the batch processing function is applied, and if the files of all employees to be processed are imported, the subsequent processing will be performed for all employees. This can now be done in bulk.

In step S404, the usage start date is acquired from the work record information or personal calendar information for the usage start month acquired in step S402, and the process moves to step S405.

In step S405, it is determined whether the usage start date is a date in the middle of the usage start month. If it is determined that it is a date in the middle (YES), the process moves to step S406, and if it is determined that it is not (NO). ) ends the series of processing and returns to the original processing.

Here, the process for determining whether or not the date is in the middle of the usage start month is basically determined to be a midway date when the usage start date is a date other than the first business day of the usage start month, and This process determines that the date is not in the middle of a business day. Note that, for example, if the first working day in the month of starting use is a holiday, this date may be determined as the business start date. Additionally, if the usage start date is the business start date, the amount paid will be calculated separately based on the three-month amount of the commuter pass.

In step S406, the first period corresponding to the commuting related information of the employee is acquired from the storage device 42, and it is determined whether the usage start date acquired in step S404 is within the acquired first period. Then, if it is determined that the date is within the first period (YES), the process moves to step S408, and if it is determined that it is not (NO), the process moves to step S410.

If the process moves to step S408, the regular discount fare (one month amount) is set as the fare type for calculating the daily prorated transportation fee for the month of starting use, and the process moves to step S410.

In step S410, the monthly amount of the commuter pass corresponding to the commuting route of the employee is obtained from the employee-specific route information table 406, and payment information for disbursing the regular discount payment amount consisting of the obtained monthly amount is generated. After that, the process moves to step S416.

On the other hand, if it is determined in step S406 that the usage start date is not within the first period (that is, it is a date within the second period) and the process moves to step S412, the prorated transportation fee for the usage start month is calculated. One-way fare (normal fare) is set as the fare type, and the process moves to step S414.

In step S414, the total number of days of commuting is obtained from the work record information of the month of starting use obtained in step S402, or the total number of days of scheduled commuting is obtained from the personal calendar information of the month of starting of use obtained in step S402. get. In addition, the one-way amount corresponding to the commuting route of the employee is obtained from the employee-specific route information table 406, and the daily pro-rata payment amount is calculated based on the one-way amount and the total number of days. Furthermore, payment information for paying the calculated daily payment amount is generated, and the process moves to step S416.

In step S416, the payment information generated in step S410 or S414 is registered in the record of the corresponding employee in the employee-specific payment information table 408 or the employee-specific daily prorated payment information table 410. Thereafter, the series of processing is completed and the original processing is resumed.

〔effect〕
Next, the effects of this embodiment will be explained.
In this embodiment, the commuting transportation expense calculation server 100 calculates the pro-rata transportation expenses for the commuting route newly applied for by the employee who is eligible for the allowance, based on a date in which the usage start date is a date in the middle of the usage start month. In this case, the first period, which is the determination period corresponding to commuting-related information such as commuting route information of the employee, is obtained from the storage device 42, and whether or not the usage start date is within the first period is obtained. Determine. In addition, based on this judgment result, if the date is within the first period, the fare type of the fare used to calculate the daily transportation fee is set to regular discount fare (monthly amount), and If it is not a date, set the fare type of the fare used to calculate the daily transportation cost to normal fare (one-way amount). Furthermore, payment information regarding daily transportation expenses calculated using the fare of the set fare type is generated. Then, the generated payment information is registered in the record of the corresponding employee in the employee-specific payment information table 408 or the employee-specific daily pro rata payment information table 410.

With this configuration, if the start date of the commuter route for which the commuter has applied falls in the middle of that month, a simple judgment process will be used to calculate the appropriate amount of daily transportation expenses for the recipient. It is possible to select a fare type that can be used as a fare type, and to generate payment information regarding the daily prorated transportation fee calculated using the fare of the selected fare type.

[Correspondence]
In this embodiment, steps S402 to S404 correspond to the scheduled commuting days information acquisition means of invention 4, the actual commuting days information acquisition means of invention 8, or the usage start date information acquisition means of invention 4, and steps S406 to S414 corresponds to the supply information generation means of invention 4, 5, or 8.

Furthermore, in the present embodiment, the storage device 42 is the fare information storage means of the fourth invention, the usage date information storage means of the fourth invention, the scheduled commuting days information storage means of the fourth invention, or the actual commuting days information storage means of the eighth invention. , and the normal fare corresponds to the first fare of inventions 4, 5, or 8.

Furthermore, in this embodiment, the regular discount fare (one month amount) corresponds to the second fare of invention 4, 5, or 8.

[Third embodiment]
Next, a third embodiment of the present invention will be described. FIG. 17 is a diagram showing the third embodiment. Hereinafter, only the different parts from the first embodiment will be explained, and the explanation of the overlapping parts will be omitted.

In this embodiment, the daily transportation expenses for the calculation period are calculated based on the actual number of commuting days or scheduled commuting days during the calculation period according to the applied commuting route and the judgment standard days corresponding to the applied commuting route. This embodiment differs from the first embodiment in that either the periodic discount payment amount or the periodic discount payment amount is determined. The other configurations are the same as those of the first embodiment.

In this embodiment, when the actual number of commuting days or the scheduled number of commuting days in the calculation target period is less than the preset judgment reference number of days, which is the boundary number of days where the actual expense payment amount becomes higher than the regular discount payment amount, Set the normal fare as the fare type used to calculate the amount of transportation expenses paid for the calculation period. On the other hand, if the actual number of commuting days or the scheduled number of commuting days during the calculation target period is equal to or greater than the determination reference number of days, the regular discount fare is set as the fare type used to calculate the transportation expense payment amount for the calculation target period. Hereinafter, this setting method will be referred to as a "second setting method."

Note that the criteria for determining the number of days is set to the optimal number of days for each applied commuting route. Specifically, the number of days is set so that the amount of transportation expenses paid is appropriate for the target employee.

A specific example will be described below assuming that the period to be calculated is the month to be calculated.
For example, the railway company corresponding to the commuting route is Railway Company C, and fares are set so that if you use the commuter route you applied for for 14 days or more round trip, the one-month commuter pass becomes cheaper than the regular fare. Suppose that In this case, the criterion number of days is set to 14 days. Also, for example, if the railway company corresponding to the commuting route is Railway Company D, and the commuter route you applied for is used for more than 16 days round trip, the fare will be changed so that the one-month commuter pass is cheaper than the regular fare. Assume that it is set. In this case, the criterion number of days is set to 16th. In other words, for railway company C, if the actual number of commuting days or scheduled commuting days in the calculation target month is less than 14 days, which is the criterion number of days, the actual amount paid will be cheaper than the monthly commuter fare, and 14 days In the above cases, the one-month commuter pass will be cheaper than the actual amount paid based on the normal fare. Similarly, for railway company D, if the actual number of commuting days or scheduled number of commuting days in the calculation target month is less than 16 days, which is the criterion number of days, the actual amount paid will be cheaper than the monthly commuter fare, and 16 If the period is more than 1 day, the monthly subscription will be cheaper than the actual amount paid.

As explained above, the criteria for determining the number of days is set to the optimum number of days for each applied commuting route. etc.) and are stored in the storage device 42 in association with the route type to be used.

〔motion〕
Next, the operation of this embodiment will be explained.
[Payment information generation process]
Next, the operation of the commuting transportation expense calculation server 100 when executing the generation process of payment information regarding daily transportation expenses will be explained. Hereinafter, the period to be calculated will be explained as the month to be calculated.

FIG. 17 is a flowchart showing the payment information generation process according to this embodiment.
When the payment information generation process is executed in the CPU 30, as shown in FIG. 17, the process first moves to step S500.

In step S500, it is determined whether or not there is an instruction to generate payment information. If it is determined that there is (YES), the process moves to step S502; if it is determined that there is not (NO), the process continues until the generation instruction is received. Repeat the process.

In step S502, work performance information or personal calendar information corresponding to the calculation target month of the employee is acquired, and the process moves to step S504.

Here, the work record information and the personal calendar information are stored in the storage device 42 as files in a predetermined file format, such as a CSV file, as in the first embodiment. As shown in example 15, it can be obtained by selecting and importing the CSV file of the relevant employee. This import can be performed for all employees to be processed when the batch processing function is applied, and if the files of all employees to be processed are imported, the subsequent processing will be performed for all employees. This can now be done in bulk.

In step S504, the total number of days of commuting work (total commuting days) is obtained from the work performance information for the calculation target month obtained in step S502, or the commuting schedule is obtained from the personal calendar information for the calculation target month obtained in step S502. Get the total number of days (total scheduled commuting days). After that, the process moves to step S506.

In step S506, the determination standard number of days corresponding to the commuting route of the employee is acquired from the storage device 42, and it is determined whether the total number of days acquired in step S504 is less than the acquired determination standard number of days. If it is determined that the number of days is less than the criterion number of days (YES), the process moves to step S508, and if it is determined otherwise (NO), the process moves to step S512.

If the process moves to step S508, one-way fare (regular fare) is set as the fare type for calculating the daily prorated transportation fee, and the process moves to step S510.

In step S510, the one-way amount corresponding to the commuting route of the employee is obtained from the employee-specific route information table 406, and the daily pro-rated amount is calculated based on the obtained one-way amount and the total number of days obtained in step S504. In addition, payment information for paying the calculated daily payment amount is generated, and the process moves to step S516.

On the other hand, if it is determined in step S506 that the total number of days is not less than the criterion number of days and the process moves to step S512, a regular discount fare (one month amount) is set as the fare type for calculating the daily prorated transportation cost for the month to be calculated. Then, the process moves to step S514.

In step S514, the monthly amount of the commuter pass corresponding to the commuting route of the employee is obtained from the employee-specific route information table 406, and payment information for paying the regular discount payment amount, which is the obtained monthly amount, is generated. After that, the process moves to step S516.

In step S516, the payment information generated in step S510 or S514 is registered in the record of the corresponding employee in the employee-specific payment information table 408 or the employee-specific daily prorated payment information table 410. Thereafter, the series of processing is completed and the original processing is resumed.

〔effect〕
Next, the effects of this embodiment will be explained.
In the present embodiment, the commuting transportation expense calculation server 100 uses data from the storage device 42 for the per diem transportation expenses corresponding to the actual number of commuting days or the scheduled number of commuting days for the commuting route applied for by the employee to be paid. The determination reference number of days corresponding to the commuting route, etc. is acquired, and it is determined whether the actual number of commuting days or the scheduled number of commuting days is less than the determination reference number of days. In addition, based on this judgment result, if the number of days is less than the judgment standard, the fare type of the fare used to calculate the daily prorated transportation fee is set to normal fare (one-way amount), and the fare type is calculated using this fare type. Generate payment information regarding daily transportation expenses. On the other hand, if the judgment result is not less than the judgment standard number of days, the fare type of the fare used to calculate the daily prorated transportation cost is set to regular discount fare (monthly amount), and the daily prorated transportation calculated using the fare of this fare type is set. Generate payment information regarding expenses. Then, the generated payment information is registered in the record of the corresponding employee in the employee-specific payment information table 408 or the employee-specific daily pro rata payment information table 410.

With such a configuration, it is possible to select a fare type that allows calculation of a daily pro-rata transportation expense amount appropriate for the employee to be paid through a simple determination process, and to calculate a pro-rata transportation fee based on the fare of the selected fare type. Payment information regarding transportation expenses can be generated.

[Correspondence]
In this embodiment, steps S502 to S504 correspond to the scheduled commuting days information acquisition means of invention 6 or the actual commuting days information acquisition means of invention 8, and step S506 corresponds to the threshold value acquisition means of invention 6, Steps S506 to S514 correspond to the provision information generation means of inventions 6 to 8.

Furthermore, in the present embodiment, the storage device 42 corresponds to the fare information storage means of the sixth invention, the scheduled commuting days information storage means of the sixth invention, or the threshold storage means of the sixth invention, and the determination reference number of days corresponds to the seventh invention. Corresponding to the first threshold value, the normal fare corresponds to the first fare of invention 6 or 8.

Furthermore, in this embodiment, the regular discount fare (one month amount) corresponds to the second fare of invention 6 or 8.

[Modified example]
In addition, in the above-mentioned embodiment, by comparing the amount of actual expenses paid in the month to be calculated and the monthly amount of the commuter pass, the lower of the two is set as the daily transportation expense, but this configuration is not limited. do not have. For example, if daily transportation expenses are paid for multiple consecutive months, the actual payment amount for multiple months and the corresponding multiple monthly amount for the commuter pass (for example, 3 months, 6 months, or 12 months amount) A configuration may also be adopted in which the daily prorated transportation expenses are determined by comparison with the following.

In addition, in the above embodiment and its variations, it is determined whether the periodic discount payment amount is lower (cheaper) than the actual payment amount, and if it is determined that it is lower (cheaper), the periodic payment amount is paid. However, the present invention is not limited to this configuration. For example, it may be determined whether the regular discount payment amount is higher than the actual cost payment amount, and if it is determined that the regular discount payment amount is higher, the actual cost payment amount may be paid. Alternatively, depending on payment conditions, etc., it may be determined whether the periodic discount payment amount is higher than the actual payment amount, and if it is determined to be higher, the periodic payment amount may be paid, or the actual payment amount It may be determined whether the regular discount payment amount is lower (cheaper) than the regular discount payment amount, and if it is determined to be lower (cheaper), the actual cost payment amount may be provided.

In addition, in the above embodiment and its variations, if the usage start date is within the first period, the fare type used for calculating the daily prorated transportation fee is set to a regular discount fare, and the regular discount is applied. Although the configuration is such that payment information regarding the payment amount (for example, monthly amount) is generated, the configuration is not limited to this. For example, it is determined whether the usage start date is within the second period, and if it is within the second period, the fare type used to calculate the daily transportation fee is set to normal fare. , the actual payment amount may be calculated and payment information regarding the actual payment amount may be generated. In addition, the judgment is not limited to the first period or the second period, but for example, (a) if the index that increases according to the number of days from the reference date before the usage start date in the calculation period to the usage start date is less than a predetermined value. If so, (b) if the index that increases according to the number of days from the reference date after the start date of use in the calculation period to the start date of use is equal to or greater than a predetermined value, (c) from the start date of use in the calculation period (d) If the index decreases according to the number of days from the previous reference date to the start date of use, (d) the index decreases according to the number of days from the reference date after the start date of use in the calculation period to the start date of use. A configuration that generates payment information for disbursing a regular discount payment amount (for example, a monthly amount) by setting the fare type used for calculating daily transportation expenses to a regular discount fare when a decreasing index is below a predetermined value. You can also use it as The indicator (a) above is, for example, the ratio of the number of days (e.g., 8 days) from the beginning of the month to the start date of use (e.g., 8/30 or 31) is applicable, and the indicator in (b) above is, for example, the ratio of the number of days (for example, 15 days) from the end of the month to the usage start date to the calculation period (for example, 15/30 or 31), and the above (b) is applicable. The indicator in c) is, for example, the ratio of the calculation period (e.g. 30 or 31/8) to the number of days from the beginning of the month to the start date of use (e.g. 8 days), and the indicator in (d) above is, for example, the ratio of the calculation period to the number of days from the beginning of the month to the start date of use (e.g. 8 days). This corresponds to the ratio of the calculation period (for example, 30 or 31/15) to the number of days (for example, 15 days) from the date to the usage start date. Note that the period to be calculated is not limited to the total number of days in the period, but may be the number of business days.

Furthermore, in the above embodiment and its modifications, the configuration is such that information on the scheduled commuting date is acquired from the personal calendar information stored in the storage device 42, but the configuration is not limited to this. For example, other configurations may be used, such as a configuration that reads from another storage medium, a configuration that imports manually entered information, or a configuration that receives and imports information sent from a terminal used by an employee. . The same holds true when acquiring information on the usage start date.

In addition, in the above-described embodiment and its variations, the first setting method is used to select the fare type used for calculating the daily prorated transportation cost when the commuting route usage start date begins in the middle of the month. However, the configuration is not limited to this. For example, the first setting method may be applied to other similar cases, such as a case where there is a leave period such as a long-term hospitalization and the return to work is in the middle of the month.

In addition, in the above embodiment and its variations, when the actual number of commuting days or the scheduled number of commuting days is compared with the determination reference number of days, and the actual number of commuting days or the scheduled number of commuting days is equal to or greater than the number of determination reference days, the daily transportation cost is calculated. Although the configuration has been described in which the fare type used in the calculation is set to regular discount fare and payment information regarding the regular discount payment amount (for example, monthly amount) is generated, the configuration is not limited to this. For example, if information on the actual number of non-commuting days or the scheduled number of non-commuting days is obtained or calculated based on work record information or personal calendar information, and the actual number of non-commuting days or the scheduled number of non-commuting days is less than the judgment standard number of days, the The fare type used for calculating transportation expenses may be set to regular discount fare. If the calculation period is the month, the actual number of non-commuting days or scheduled number of non-commuting days is "number of days in the month - actual number of commuting days or scheduled number of commuting days" or "number of business days in the month - actual number of commuting days or scheduled number of commuting days". ”.

Also, for example, information on the actual number of commuting days or scheduled number of commuting days per week may be obtained from work record information or personal calendar information, and the actual number of commuting days or scheduled number of commuting days per week may be determined by the second judgment standard days ( The actual number of commuting days or scheduled commuting days per week, which corresponds to the second threshold and is compared with the monthly judgment standard number of days (the number of days set to ensure an appropriate payment amount in the same way as the first threshold) If the number of days is equal to or greater than the second determination standard number of days (for example, four days), the fare type used for calculating the daily transportation cost may be set to a regular discount fare. Here, the actual number of commuting days or scheduled number of commuting days per week is, for example, the average number of days per week in the calculation target month (=actual number of commuting days or scheduled number of commuting days/4). In addition, information on the actual number of non-commuting days or scheduled number of non-commuting days per week is obtained or calculated based on work record information or personal calendar information, and the actual number of non-commuting days or scheduled number of non-commuting days per week is the second criterion. If the number of days is less than the number of days, the fare type used for calculating the daily prorated transportation fee may be set to a regular discount fare.

In addition, from the same perspective as the judgment standard number of days (first threshold), instead of a threshold of days, a threshold of the first index (for example, a percentage threshold (third threshold)) that increases according to the actual number of commuting days or the planned number of commuting days is set. For example, obtain or calculate the ratio of the actual number of commuting days or scheduled number of commuting days to the calculation target period (for example, actual number of commuting days or scheduled number of commuting days/30 or 31 days or number of business days) from work performance information or personal calendar information. However, if this ratio (first indicator) is equal to or higher than the third threshold (for example, the ratio at which regular trains are cheaper, "15 days/30 days or 31 days, or the number of business days"), the fare used to calculate the daily transportation cost. A configuration may be adopted in which the type is set to regular discount fare. In addition, for example, as a second index that increases according to the actual number of non-commuting days or the scheduled number of non-commuting days, the ratio of the actual number of non-commuting days or the scheduled number of non-commuting days to the calculation target period (for example, Acquire or calculate the actual number of non-commuting days or scheduled number of non-commuting days/30 or 31 days or business days), and if this ratio (second indicator) is less than the third threshold, the fare used to calculate the daily pro-rata transportation cost. A configuration may be adopted in which the type is set to regular discount fare.

In addition, from the same perspective as the second judgment standard number of days (second threshold), instead of using the number of days threshold, the third index threshold (for example, the percentage threshold (fourth For example, the ratio of the actual number of commuting days or scheduled number of commuting days per week to the number of days in a week (7 days or number of business days per week) (third index) is set based on work performance information or personal calendar information. If this ratio is equal to or higher than the fourth threshold (for example, 4 days/7 days, which is the borderline where the monthly commuter fare is cheaper), the fare type used to calculate the daily prorated transportation fee is set as the commuter discount fare. It is also possible to have a configuration in which it is set to . In addition, for example, as a fourth index that increases according to the actual number of non-commuting days per week or the scheduled number of non-commuting days, the number of days per week (7 days or number of business days per week) can be calculated based on work performance information or personal calendar information. Obtain or calculate the ratio of the actual number of non-commuting days or scheduled number of non-commuting days per day (fourth index), and if this ratio is less than the fourth threshold, change the fare type used for calculating daily transportation expenses to regular discount fare. It is also possible to configure the settings.

In addition, from the same perspective as the third threshold, a threshold for the fifth index (for example, a ratio threshold (fifth threshold)) that decreases depending on the actual number of commuting days or the scheduled number of commuting days is set, and for example, work performance information or personal Obtain or calculate the ratio of the calculation target period to the actual number of commuting days or scheduled commuting days (for example, 30 days or 31 days or number of business days/actual number of commuting days or scheduled number of commuting days) from the calendar information, and obtain or calculate this ratio (fifth index). is less than the fifth threshold (for example, the rate at which the commuter pass is cheaper "30 days or 31 days or the number of business days/15 days"), the fare type used for calculating the daily transportation cost is set to the commuter pass discount fare. You can also use it as For example, as a sixth index that decreases according to the actual number of non-commuting days or the scheduled number of non-commuting days, the ratio of the calculation target period to the actual number of non-commuting days or the scheduled number of non-commuting days (for example, 30 days or 31 days or the number of business days/actual number of non-commuting days or scheduled number of non-commuting days), and if this ratio (sixth indicator) is greater than or equal to the fifth threshold, the fare used to calculate the pro-rata transportation cost. A configuration may be adopted in which the type is set to regular discount fare.

In addition, from the same perspective as the fourth threshold, a threshold for the seventh index (for example, a percentage threshold (sixth threshold)) that decreases depending on the actual number of commuting days or the scheduled number of commuting days per week is set, and for example, the work performance The ratio (seventh index) of the number of days in a week (7 days or number of business days per week) to the actual number of commuting days per week or the scheduled number of commuting days is obtained or calculated from the information or personal calendar information, and this ratio is the sixth threshold. (For example, if the fare is less than 7 days/4 days, at which point a one-month commuter fare is cheaper), the fare type used for calculating the daily prorated transportation fee may be set to a regular discount fare. In addition, for example, as an eighth index that decreases according to the actual number of non-commuting days or the scheduled number of non-commuting days per week, the number of weekly non-commuting days or scheduled non-commuting days can be calculated from work performance information or personal calendar information. Obtain or calculate the ratio (eighth index) of the number of days (7 days or business days per week), and if this ratio is greater than or equal to the sixth threshold, change the fare type used for calculating daily transportation expenses to regular discount fare. It is also possible to configure the settings.

In addition, in the above embodiment and its variations, it is determined whether or not the amount of this payment information is less than the actual payment amount corresponding to the work performance for payment information in which the daily pro-rata transportation expenses have been paid, and this determination is made. Although the configuration is such that the underpayment is paid or the overpayment is collected based on the results, the configuration is not limited to this. For example, when paying daily transportation expenses the next month, before paying the daily transportation expenses corresponding to the generated payment information, it is determined whether the amount is less than the actual payment amount corresponding to the work performance, and The provision information may be modified based on the determination result before payment of the daily transportation fee.

Further, in the above embodiment and its modification examples, the present invention is realized as a network system, but the present invention is not limited to this, and can also be realized as a single device or application.

Further, in the above embodiments and their modifications, the case where the application is applied to a network system consisting of the Internet 199 has been described, but the invention is not limited to this, and the application may be applied to, for example, a so-called intranet that communicates using the same method as the Internet 199. Good too. Of course, the present invention is not limited to a network that communicates using the same method as the Internet 199, but can be applied to a network using any communication method.

Furthermore, in the above embodiments and their modifications, when executing the processes shown in the flowcharts of FIGS. 5, 7, 11, 14, 16, and 17, programs stored in the ROM Although the case where these procedures are executed has been described, the present invention is not limited to this, and a program showing these procedures may be read from a storage medium in which the program is stored into the RAM and executed.

100... Commuting transportation expense calculation server, 200... Employee terminal, 30... CPU, 32... ROM, 34... RAM, 38... I/F, 39... Bus, 40... Input device, 42... Storage device, 44... Display device, 199...Internet, 400...Company master table, 402...Workplace master table, 404...Employee information master table, 406...Employee-specific route information table, 408...Employee-specific payment information table, 410...Employee-specific daily payment information table, 412...Department information table, 500...Employee information list screen, 600...Application information input screen, 800...Route list screen, 801...Payment information list screen, 900...Personal calendar information import screen, 901...Accomplishment information import screen

Claims

A payment calculation system that calculates the amount of transportation expenses to be paid corresponding to the scheduled number of commuting days for the calculation target period of the payment recipient regarding the commuting route that the payment recipient can use for commuting,
Fare information acquisition means for acquiring the fare information corresponding to the commuting route of the recipient from a fare information storage means for storing fare information regarding the fare required for commuting on the commuting route;
Commuting for each person eligible for payment, obtaining information on the number of scheduled commuting days related to the number of scheduled commuting days in the calculation target period from a scheduled commuting days information storage means that stores information on the number of scheduled commuting days related to the number of scheduled commuting days recorded by the person eligible for payment. A means for acquiring information on the number of scheduled days;
Based on the fare information acquired by the fare information acquisition means and the scheduled commuting days information acquired by the scheduled commuting days information acquisition means, before the expiration of the calculation target period, the traffic corresponding to the scheduled number of commuting days in the calculation target period is calculated. a first payment amount calculation means for calculating a first payment amount that is an expense payment amount;
A payment calculation comprising: payment information generation means for generating payment information regarding the first payment amount calculated by the first payment amount calculation means, for prepaying the first payment amount. system.
In claim 1,
Actual number of commuting days information obtaining means for obtaining actual number of commuting days information regarding the actual number of commuting days in the calculation target period from an actual number of commuting days information storage means for storing actual number of commuting days information regarding the actual number of commuting days of the person to be paid;
A second payment amount, which is a transportation expense payment amount corresponding to the actual number of commuting days in the calculation period, based on the fare information acquired by the fare information acquisition means and the actual number of commuting days information acquired by the actual commuting days information acquisition means. a second payment amount calculation means for calculating the
If the second payment amount calculated by the second payment amount calculation means is larger than the first payment amount, insufficient payment information generation means for generating insufficient payment information for paying the shortfall;
If the second payment amount calculated by the second payment amount calculation means is smaller than the first payment amount, collection information generation means generates collection information for collecting the overpayment amount. Payment calculation system.
A payment calculation system that calculates the amount of transportation expenses to be paid corresponding to the scheduled number of commuting days for the calculation target period of the payment recipient regarding the commuting route that the payment recipient can use for commuting,
The fare information corresponding to the commuting route of the person eligible for payment is retrieved from a fare information storage means that stores fare information regarding fares including a first fare required for commuting on the commuting route and a second fare that is cheaper than the first fare. a fare information acquisition means for acquiring information;
Commuting for each person eligible for payment, obtaining information on the number of scheduled commuting days related to the number of scheduled commuting days in the calculation target period from a scheduled commuting days information storage means that stores information on the number of scheduled commuting days related to the number of scheduled commuting days recorded by the person eligible for payment. A means for acquiring information on the number of scheduled days;
Based on the fare information acquired by the fare information acquisition means and the scheduled commuting days information acquired by the scheduled commuting days information acquisition means, before the expiration of the calculation target period, the traffic corresponding to the scheduled number of commuting days in the calculation target period is calculated. a first payment amount calculation means for calculating the payment amount using the first fare or the second fare;
Payment information regarding the first lower payment amount, which is the lower of the payment amount related to the first fare and the payment amount related to the second fare, based on the calculation result of the first payment amount calculation means. a payment information generating means for generating payment information for prepaying the first low payment amount;
Actual number of commuting days information obtaining means for obtaining actual number of commuting days information regarding the actual number of commuting days in the calculation target period from an actual number of commuting days information storage means for storing actual number of commuting days information regarding the actual number of commuting days of the person to be paid;
Based on the fare information acquired by the fare information acquisition means and the actual commuting days information acquired by the actual commuting days information acquisition means, the amount of transportation expenses to be paid corresponding to the actual number of commuting days in the calculation period is determined by the first fare or a second payment amount calculation means that calculates using the second fare;
Based on the calculation result of the second payment amount calculation means, the second lower payment amount, which is the lower of the payment amount related to the first fare and the payment amount related to the second fare, is the first lower payment amount. Insufficient payment information generating means for generating insufficient payment information for paying the shortfall amount if the amount is larger than the payment amount;
collection information generation means for generating collection information for collecting overpayment if the second low payment amount is smaller than the first low payment amount based on the calculation result of the second payment amount calculation means; A payment calculation system characterized by comprising:
A payment calculation system that calculates the amount of transportation expenses to be paid corresponding to the scheduled number of commuting days for the calculation target period of the payment recipient regarding the commuting route that the payment recipient can use for commuting,
The fare information corresponding to the commuting route of the person eligible for payment is retrieved from a fare information storage means that stores fare information regarding fares including a first fare required for commuting on the commuting route and a second fare that is cheaper than the first fare. a fare information acquisition means for acquiring information;
Acquisition of usage start date information for acquiring usage start date information regarding the usage start date of the commuting route in the calculation target period from usage date information storage means that stores usage date information regarding the usage date of the commuting route of the payee. means and
Commuting for each person eligible for payment, obtaining information on the number of scheduled commuting days related to the number of scheduled commuting days in the calculation target period from a scheduled commuting days information storage means that stores information on the number of scheduled commuting days related to the number of scheduled commuting days recorded by the person eligible for payment. A means for acquiring information on the number of scheduled days;
The expiration of the calculation target period based on the fare information acquired by the fare information acquisition means, the scheduled commuting days information acquired by the scheduled commuting days information acquisition means, and the usage start date information acquired by the usage start date information acquisition means. a first payment amount calculation means for calculating a transportation expense payment amount corresponding to the scheduled number of commuting days in the calculation target period using the first fare or the second fare;
Payment information regarding one of the first payment amount related to the first fare and the second payment amount related to the second fare in the calculation, based on the calculation result of the first payment amount calculation means, A payment calculation system comprising: a payment information generating means for generating payment information for prepaying the payment amount.
In claim 4,
The second fare becomes cheaper than the first fare when the number of days the commuting route is used is more than a predetermined number of days,
The payment information generation means generates payment information regarding the second payment amount when at least one of one or more of the following conditions 1 to 5 is satisfied, and when the one or more conditions are satisfied. A payment calculation system that generates payment information regarding the first payment amount when the first payment amount is not satisfied.
(Condition 1) The usage start date is a date included in a predetermined period from the start of the calculation target period to the reference date.
(Condition 2) The index that increases according to the number of days from the reference date before the usage start date in the calculation target period to the usage start date is less than or equal to a predetermined value.
(Condition 3) An index that increases according to the number of days from a reference date later than the usage start date in the calculation target period to the usage start date is equal to or greater than a predetermined value.
(Condition 4) The index that decreases according to the number of days from the reference date before the usage start date in the calculation target period to the usage start date is a predetermined value or more.
(Condition 5) The index that decreases according to the number of days from the reference date after the usage start date in the calculation target period to the usage start date is less than or equal to a predetermined value.
A payment calculation system that calculates the amount of transportation expenses to be paid corresponding to the scheduled number of commuting days for the calculation target period of the payment recipient regarding the commuting route that the payment recipient can use for commuting,
The fare information corresponding to the commuting route of the person eligible for payment is retrieved from a fare information storage means that stores fare information regarding fares including a first fare required for commuting on the commuting route and a second fare that is cheaper than the first fare. a fare information acquisition means for acquiring information;
Commuting for each person eligible for payment, obtaining information on the number of scheduled commuting days related to the number of scheduled commuting days in the calculation target period from a scheduled commuting days information storage means that stores information on the number of scheduled commuting days related to the number of scheduled commuting days recorded by the person eligible for payment. A means for acquiring information on the number of scheduled days;
Threshold value acquisition means for acquiring the threshold value corresponding to the commuting route of the payment recipient from a threshold value storage means for storing a threshold value for the number of days of use of the commuting route for each of the commuting route;
The calculation target is calculated before the expiration of the calculation target period based on the fare information acquired by the fare information acquisition means, the scheduled commuting days information acquired by the scheduled commuting days information acquisition means, and the threshold value acquired by the threshold value acquisition means. a first payment amount calculation means for calculating a transportation expense payment amount corresponding to the scheduled number of commuting days in the period using the first fare or the second fare;
Payment information regarding one of the first payment amount related to the first fare and the second payment amount related to the second fare in the calculation, based on the calculation result of the first payment amount calculation means, A payment calculation system comprising: a payment information generating means for generating payment information for prepaying the payment amount.
In claim 6,
The payment information generation means generates payment information regarding the second payment amount when at least one of the following conditions 1 to 12 is satisfied, and determines whether the one or more conditions are satisfied. A payment calculation system that generates payment information regarding the first payment amount when the first payment amount is not satisfied.
(Condition 1) The threshold value is a first threshold value indicating the boundary number of days in which the first payment amount exceeds the second payment amount, and the scheduled number of commuting days in the calculation period is the number of days at which the first payment amount exceeds the second payment amount. It is equal to or higher than the first threshold value.
(Condition 2) The threshold value is the first threshold value, and the scheduled number of non-commuting days in the calculation target period is less than the first threshold value.
(Condition 3) The threshold value is a second threshold value that indicates the boundary number of days in which the first payment amount exceeds the second payment amount for the scheduled number of commuting days per week in the calculation period, and the number of scheduled commuting days per week. is greater than or equal to the second threshold.
(Condition 4) The threshold value is the second threshold value, and the scheduled number of non-commuting days per week is less than the second threshold value.
(Condition 5) The threshold value is a third threshold value in which the first index, which increases according to the scheduled number of commuting days in the calculation period, indicates a boundary value at which the first payment amount exceeds the second payment amount; One index is greater than or equal to the third threshold.
(Condition 6) The threshold value is the third threshold value, and the second index that increases according to the scheduled number of non-commuting days in the calculation target period is less than the third threshold value.
(Condition 7) The threshold value is a fourth threshold value in which the third index, which increases according to the scheduled number of commuting days per week during the calculation period, indicates a boundary value at which the second payment amount exceeds the first payment amount. , the third index is greater than or equal to the fourth threshold.
(Condition 8) The threshold value is the fourth threshold value, and the fourth index that increases according to the scheduled number of non-commuting days per week in the calculation target period is less than the fourth threshold value.
(Condition 9) The threshold value is a fifth threshold value in which a fifth index that decreases according to the scheduled number of commuting days in the calculation period indicates a boundary value at which the first payment amount is less than the second payment amount, and 5 indicators are less than the fifth threshold.
(Condition 10) The threshold value is the fifth threshold value, and the sixth index that decreases according to the scheduled number of non-commuting days in the calculation target period is equal to or higher than the fifth threshold value.
(Condition 11) The threshold value is a sixth threshold value in which the seventh index, which decreases according to the scheduled number of commuting days per week in the calculation period, indicates a boundary value at which the first payment amount falls below the second payment amount. , the seventh index is less than the sixth threshold.
(Condition 12) The threshold value is the sixth threshold value, and the eighth index that decreases according to the scheduled number of non-commuting days per week in the calculation target period is equal to or higher than the sixth threshold value.
In any one of claims 4 to 7,
Actual number of commuting days information obtaining means for obtaining actual number of commuting days information regarding the actual number of commuting days in the calculation target period from an actual number of commuting days information storage means for storing actual number of commuting days information regarding the actual number of commuting days of the person to be paid;
Based on the fare information acquired by the fare information acquisition means and the actual commuting days information acquired by the actual commuting days information acquisition means, the amount of transportation expenses to be paid corresponding to the actual number of commuting days in the calculation period is determined by the first fare or a second payment amount calculation means that calculates using the second fare;
Based on the calculation result of the second payment amount calculation means, the second lower payment amount, which is the lower of the payment amount related to the first fare and the payment amount related to the second fare, is calculated based on the calculation result of the second payment amount calculation means. If the lower of the payment amount and the second payment amount is larger than the first lower payment amount, a shortage payment information generating means for generating shortage payment information for paying the shortfall;
collection information generation means for generating collection information for collecting overpayment if the second low payment amount is smaller than the first low payment amount based on the calculation result of the second payment amount calculation means; A payment calculation system characterized by comprising: