JP2024033312A - Payment calculation system - Google Patents

Abstract

An object of the present invention is to provide a payment calculation system that can selectively perform registration processing that automatically generates payment information and registration processing that does not automatically generate payment information when registering commuting routes for the same payment recipient. [Solution] A commuting transportation expense calculation server 100 receives application information from an employee terminal 200, and determines whether or not a check box 63 for "apply for route only" is checked based on the received application information. However, if it is not checked, the amount of transportation expenses to be paid will be calculated based on the commuting route information included in the application information and the payment rules set in advance, and the payment information regarding the amount of transportation expenses will be generated. If the first registration process including the approval process is executed and the check box 63 is checked, the process other than the calculation process of the transportation expense payment amount, the process of generating the payment information, and the process of approving the payment information in the first registration process A second registration process is executed. [Selection diagram] Figure 5

Description

The present invention relates to a payment calculation system for calculating the amount of transportation expenses to be paid to recipients.

BACKGROUND ART 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, automatically calculates the amount of commuting expenses to be paid based on preset commuting allowance payment standards and calculation method definitions when a new application for commuting expenses occurs. It is configured to do this.

Japanese Patent Application Publication No. 2016-192201

However, with the technology described in Patent Document 1, payment information for, for example, a six-month period is automatically generated in response to an application for a commuting route. Therefore, for example, for those eligible for payment who have a work system that includes a mix of telecommuting and commuting, payment information is generated individually with a payment amount depending on the number of days actually commuting or the number of days scheduled for commuting. It is difficult to do so.
Therefore, the present invention has been made by focusing on the unresolved problems of the conventional technology, and includes a registration process that automatically generates payment information when registering the commuting route of the same recipient. The purpose of the present invention is to provide a payment calculation system that can selectively perform registration processing without generation.

[Invention 1] In order to achieve the above object, the payment calculation system of Invention 1 is a payment calculation system that calculates the amount of transportation expenses paid to a recipient of the payment for a commuting route that the recipient can use for commuting. route information registration processing for registering commuting route information regarding the commuting route of the person to be paid; calculation processing for calculating the amount of transportation expenses paid based on the registered commuting route information; and payment regarding the calculated amount of transportation expenses paid. A first registration process that performs a generation process that generates information and a payment information registration process that registers the generated payment information, and a second registration process that performs a process that is completed with the route information registration process separately from the first registration process. a selection means for selecting one of the above for the same recipient, and when the selection means selects the first registration process, the first registration process is executed, and the selection means executes the second registration process. A registration process execution means is provided for executing the second registration process when selected.

With such a configuration, when the selection means selects either the first registration process or the second registration process for the same payment recipient, the registration process execution means selects the first registration process or the second registration process by the selection means. If the process is selected, the first registration process is executed, and if the second registration process is selected by the selection means, the second registration process is executed.
Furthermore, this system may be realized as a single device, terminal, or other device, or may be realized as a network system in which a plurality of devices, terminals, or 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.

[Invention 2] Furthermore, in the payment calculation system of Invention 1, the first registration process further includes a commuting process for approving commuting route information regarding the applied commuting route. The second registration process includes a route approval process and a payment information approval process for approving the generated payment information, and the second registration process includes a commuting route approval process for approving commuting route information regarding the commute route for which the application has been made. including.
With such a configuration, when the first registration process is selected by the selection means, the first registration process including the commuting route approval process and the payment information approval process is executed for the applied commuting route, and the selected If the second registration process is selected by the means, the second registration process including the commuting route approval process is executed for the applied commuting route.

Here, the route information registration process is a process of acquiring commuting route information regarding the commuting route and registering the acquired commuting route information, acquiring commuting route information regarding the commuting route, and registering the acquired commuting route information after it is approved. Includes processing to do.
[Invention 3] Furthermore, in the payment calculation system of Invention 1 or 2, the stipend calculation system of Invention 3 is configured to process the commuting route registered through the first or second registration process in accordance with the first or second registration process. separately, a means for calculating the amount of transportation expenses to be paid corresponding to the actual number of commuting days or scheduled number of days of commuting during the calculation period of the eligible person for the commuting route; A payment information generating means for generating payment information regarding the amount of transportation expense payment.

With such a configuration, the transportation expense payment amount calculation means determines the payment target for the commuting route that is registered through the first or second registration process, separately from the first or second registration process. When the amount of transportation expenses paid corresponding to the actual number of days of commuting or the number of scheduled days of commuting for the calculation period of the person is calculated, the amount of payment of transportation expenses calculated by the amount of transportation expenses calculation means is generated by the payment information generation means. generated.
[Invention 4] On the other hand, in order to achieve the above object, the payment calculation system of Invention 4 is based on the first fare of the means of transportation required for commuting on the commuting route and the first fare. fare information acquisition means for acquiring fare information corresponding to the commuting route of the person to be paid regarding the calculation of the transportation expenses payment amount from the fare information storage means for storing fare information regarding fares including a second fare that is also cheaper; Commuting days information obtaining means for obtaining commuting days information regarding the actual commuting days or scheduled commuting days for the calculation target period from commuting days information storage means storing commuting days information regarding the actual commuting days or scheduled commuting days of the person eligible for the payment; , for the commuting route registered through the first or second registration process, based on the fare information acquired by the fare information acquisition means and the commuting days information acquired by the commuting days information acquisition means, for the calculation target period. The first payment amount when the transportation expense payment amount corresponding to the actual number of commuting days or the scheduled number of commuting days is calculated using the first fare using the transportation expense payment amount calculation means and the actual number of commuting days or the scheduled number of commuting days during the calculation period. determination means for determining the magnitude of the second payment amount when the transportation allowance payment amount corresponding to the transportation allowance payment amount is calculated by the transportation allowance payment amount calculation means using the second fare, and the payment information generation means includes: Based on the determination result of the determining means, payment information regarding the lower of the first payment amount and the second payment amount is generated.

With such a configuration, for the commuting route registered through the first or second registration process, the fare information acquisition means stores the commuting information of the person eligible for transportation expenses from the fare information storage means. When the fare information corresponding to the route is acquired and the commuting days information acquisition means acquires the commuting days information regarding the actual number of commuting days or the scheduled commuting days in the calculation target period from the commuting days information storage means, the determining means For commuting routes registered through the first or second registration process, the first payment amount and the corresponding calculation when the transportation expense payment amount corresponding to the actual number of commuting days or scheduled number of commuting days during the calculation period is calculated using the first fare. The magnitude of the second payment amount is determined when the transportation expense payment amount corresponding to the actual number of commuting days or the scheduled number of commuting days in the target period is calculated using the second fare, and the payment information generation means calculates the amount based on the determination result of the determination means. , payment information regarding the lower of the first payment amount and the second payment amount is generated.

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 on public transportation or individual transportation. Alternatively, fares that are cheaper than regular fares using coupon tickets fall under this category.
Further, the actual number of commuting days is the number of days actually commuting (actual number of days), and the scheduled number of commuting days is the number of days commuting is planned.
[Invention 5] Furthermore, in the payment calculation system of Invention 1 or 2, the payment calculation system of Invention 5 is communicably connected to the recipient terminal used by the payment recipient,
In response to the actual expense application request from the target person's terminal, actual expense application information including information on the commuting route registered through the second registration process from the target person's terminal and information on the actual number of commuting days using the said commuting route. Execute actual expense application processing including acquisition processing, calculation processing of transportation expense payment amount based on the acquired actual expense application information, generation processing of payment information regarding the transportation expense payment amount, and second payment information approval processing to approve the payment information. The system is equipped with means for executing actual cost application processing.

With such a configuration, the actual expense application processing means, in response to the actual expense application request from the target person's terminal, will transmit information on the commuting route registered through the second registration process from the target person's terminal and the commuting route. Acquisition processing of actual expense application information including information on the actual number of commuting days used, calculation processing of transportation expense payment amount based on the acquired actual expense application information, generation processing of payment information regarding the transportation expense payment amount, and process of approving the payment information. 2 Actual expense application processing including payment information approval processing is executed.

As explained above, according to the payment calculation system of invention 1, it is possible to select the first registration process or the second registration process for the same payment recipient, and by selecting the second registration process, the route information registration process is performed. Since the second registration process can be completed at It is possible to take flexible measures such as generating individual payment information according to the commuting situation of the person (hereinafter referred to as "per diem eligible person"). Furthermore, if you want to know the commuting route for people who do not receive transportation expenses, such as those who commute on foot or use free transportation, for example, due to work-related accidents, you can also select the second registration process. This allows commuting route information to be registered without any extra processing.

Furthermore, according to the payment calculation system of invention 2, for the applied commuting route, the first registration process further includes route information approval processing and payment information approval processing, or route information registration processing and route information approval processing are completed. A second registration process can be performed. Thereby, approval processing can be carried out when the approval of the superior is required.
Furthermore, according to the payment calculation system of Invention 3, for the commuting route registered through the first or second registration process, the actual number of commuting days or the scheduled number of commuting days in the calculation period is calculated separately from the first or second registration process. It is possible to calculate the corresponding transportation expense payment amount and to generate payment information regarding the transportation expense payment amount. As a result, it is possible to generate individual payment information according to the commuting situation of the person eligible for the per diem allowance, and even for those eligible for the allowance who normally receive transportation expenses paid through commuter passes, for example, they start commuting from the middle of the month. If the route has to be changed, it becomes possible to calculate it on a daily basis for the corresponding month.

Furthermore, according to the payment calculation system of Invention 4, for the commuting route registered through the first or second registration process, based on the result of determining the size of the first payment amount and the second payment amount, It is possible to select an appropriate and minimum amount of transportation expenses to be paid, and also to generate payment information for disbursing this transportation expenses to a recipient.
Furthermore, according to the payment calculation system of invention 5, for example, the recipient who pays the actual transportation expenses for the actual number of days of commuting each month can apply for the actual expenses through the recipient terminal. , it is possible to reduce the effort of human resources employees, general affairs employees, etc. who perform work related to transportation expenses.

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 (d) are diagrams showing data structures of a company master table 400, a workplace master table 402, an employee information master table 404, and a vehicle-specific payment rule master table 405. (a) to (d) are diagrams showing data structures of an employee-based route information table 406, an employee-based payment information table 408, 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. It is a diagram showing a performance information import screen 901 for importing a CSV file of employee performance information. It is a diagram showing a performance information import screen 901 after importing a CSV file of employee performance information. 8 is a diagram showing a second example of a payment information list screen 801. FIG. It is a flowchart which shows supply information generation processing concerning a 2nd embodiment. It is a diagram showing a personal calendar information import screen 902 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 flowchart which shows the actual expense payment amount application process based on 3rd Embodiment.

[First embodiment]
〔composition〕
A first embodiment of the present invention will be described below. 1 to 14 are diagrams showing a first embodiment.
First, the configuration of the first embodiment will be explained.
FIG. 1 is a block diagram showing the configuration of a network system according to a first 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 3D are diagrams showing data structures of a company master table 400, a workplace master table 402, an employee information master table 404, and a vehicle-specific pay rule master table 405.

As shown in FIGS. 3A to 3D, 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 transportation expenses, and a vehicle-specific payment rule master table 405 for registering information on transportation expense payment rules for each vehicle are stored.
As shown in FIG. 3A, 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, or a combination of letters and numbers). 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, for example, 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 vehicle-specific payment rule master table 405, one record is registered for each combination of company ID, payment rule ID, and vehicle ID, as shown in FIG. 3(d). Each record includes company ID, payment rule ID, payment rule name, vehicle ID, payment cycle, payment standard amount in months, tax calculation type, fee type number, application start date, application end date, last update date, and last updater. , and other information is registered.
Here, the supply rule ID is information for identifying the supply rule, and is composed of, for example, a unique number for each supply rule (for example, only numbers, or a combination of letters and numbers). Furthermore, the payment rules are rules regarding the payment of commuting transportation expenses. Vehicle ID is information for identifying vehicles used for commuting such as trains, buses, cars, walking, motorbikes, bicycles, etc. For example, a vehicle ID is a unique number for each type of vehicle (for example, numbers only, letters or It consists of a combination of numbers). In addition, the payment cycle is information indicating the cycle in which commuting transportation expenses are paid, such as 1 month, 3 months, 6 months, 12 months, etc., and the payment standard amount in months is 1 month, 3 months, 6 months, 12 months, etc. This is information that determines the standard amount of payment, such as per month. In addition, the tax calculation type is information that determines whether or not it is subject to tax, and includes types such as public transportation (tax calculation in accordance with laws and regulations), transportation equipment (tax calculation in accordance with laws and regulations), and full taxation. This is the information shown. Further, the charge type number is a number set for each type of vehicle or type of parking facility.

FIGS. 4A to 4D are diagrams showing data structures of the employee route information table 406, the employee pay information table 408, the employee daily pro rata pay information table 410, and the department information table 412.
As shown in FIGS. 4(a) to 4(d), the storage device 42 stores an employee-specific route information table 406 in which commuting route information for each employee is registered, and commuting transportation expense payment information for each employee. An employee-specific payment information table 408, an employee-specific daily payment information table 410 that registers payment information for daily commuting transportation expenses for each employee, and a department information table that registers information on approvers and proxy applicants for each department. 412 is stored.

As shown in FIG. 4A, one record is registered in the employee-specific route information table 406 for each combination of company ID, employee ID, and route ID. 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 commuting means 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.

In the employee-specific payment information table 408, as shown in FIG. 4(b), one record is 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 example, only numbers, a combination of letters and numbers), etc. for each piece of payment information. 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.

As shown in FIG. 4C, 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 rate 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 specifying 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. 4D, 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 scheduled work days for 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. Furthermore, fare type setting information is stored that defines a setting method for setting a fare type for calculating the minimum required amount of transportation expenses in association with the company ID.

Here, the personal calendar information specifically includes, for each employee, scheduled commuting days, scheduled working days from home, total number of scheduled commuting days (hereinafter referred to as "scheduled number of commuting days"), scheduled working days from home. This information includes information such as the total number of days.
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. The advantage of including information on working days is that if a fare revision occurs for a transportation facility, it is possible to determine whether it is before or after the revision depending on the working day, and to pay an amount that matches the actual situation. It is. 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 the first 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 showing a new commuting route information application process, and FIG. 6 is a diagram showing an application information input screen 600.
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 according to 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, input screen information for application information is transmitted to the employee terminal 200 that is the source of the application request, and the process moves to step S104.
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, the application information input process is a process of accepting input of information to be registered in the employee route information table 406, the employee pay information table 408, and the employee daily pro rata pay information table 410. That is, 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. Furthermore, as shown in the "Apply only route" check box 63 in FIG. 6, it is possible to apply only for a commuting route.

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.
In step S104, it is determined whether or not the application information has been received from the employee terminal 200. If it is determined that the application information 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 S122.

Here, when the application button is pressed on the final screen of the application information input screen, the input application information is transmitted to the commuting transportation expense calculation server 100.
When proceeding to step S106, it is determined based on the received application information whether or not the "Apply for route only" checkbox 63 is checked, and if it is determined that it is checked (Yes), The process moves to step S108, and if it is determined otherwise (No), the process moves to step S110. That is, the application information includes information (for example, flag information) indicating whether or not the check box 63 is checked.

Here, we have made it possible to select ``Apply for route only'', for example, employees who commute using a new commuting route from the middle of the month, and employees who have a work system that mixes telecommuting and commuting. This is to provide flexibility for employees who are paid commuting expenses according to their work performance for each month or month. 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 total amount of commuting transportation expenses paid on a daily basis (hereinafter referred to as "daily transportation expenses") based on the actual number of commuting days in the relevant month or each month.

If the process moves to step S108, application information including commuting route information is provisionally registered in the employee-specific route information table 406, and the process moves to step S114. In other words, if the check box 63 is checked, even if the application information is temporarily registered, the payment information will not be automatically generated immediately, and the payment will be made separately from the application processing by the person in charge of the Human Resources Department or the General Affairs Department. Information generation work is performed.
On the other hand, in step S106, if the "apply for route only" checkbox 63 is not checked and the process moves to step S110, payment information is generated based on the commuting route information included in the received application information. After that, the process moves to step S112.

Specifically, the transportation expense payment amount is calculated based on the commuting route information included in the commuting route information and the payment rules registered in the vehicle-specific payment rule master table 405 for each company. Here, the payment rules are defined as information on the payment cycle such as payment every 1 month, 3 months, 6 months, 12 months, etc., and information on the standard payment amount for 1 month, 3 months, 6 months, 12 months, etc. has been done. In other words, commuting transportation expenses are calculated according to the payment rules. Thereafter, payment information regarding the calculated transportation expense payment amount is generated. Although not shown, the storage device 42 also stores a charge master table. In the fare master table, fare information corresponding to the fare type number registered in the vehicle-specific payment rule master table 405 for each company is registered, and the amount of transportation expenses to be paid is calculated based on this fare information. Here, the payment information generated in step S110 is information registered in the employee-specific payment information table 408.

That is, if the "Apply for route only" checkbox 63 is not checked, payment information is automatically generated immediately based on commuting route information, payment rules, and fare information.
In step S112, the application information received in step S104 is temporarily registered in the employee-specific route information table 406, and the payment information generated in step S110 is provisionally registered in the employee-specific payment information table 408. After that, the process moves to step S114.
In step S114, information on the department to which the applicant belongs (department ID) is acquired from the employee information master table 404, and from the department information table 412, approval party information (with approval authority) corresponding to the acquired department ID is obtained. The employee's employee ID) is acquired, and the process moves to step S116.

In step S116, 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 or application information and supply information is sent to each approver at the route destination, and the process moves to step S118.
In step S118, it is determined whether or not the application information or the application information and payment information has been approved based on the information from the approval party as to whether or not to approve. If it is determined that the application information and the payment information have been approved (Yes), step S120 If not (No), the series of processes ends and returns to the original process.

If the process moves to step S120, the temporarily registered and approved information is permanently registered, the series of processes ends, and the process returns to the original process.
As a result, if "Apply for route only" is selected, the application information temporarily registered in the employee-specific route information table 406 is permanently registered. On the other hand, if "Apply for route only" is not selected, the application information and payment information temporarily registered in the employee-specific route information table 406 and the employee-specific payment information table 408 are permanently registered. Here, the official registration is performed by, for example, changing the status flag of the temporarily registered information.

In addition, if it is determined in step S104 that no application information has been received and the process moves to step S122, it is determined whether or not an application cancellation request has been received, and if it is determined that an application cancellation request has been received (Yes), a series of If it is determined that the process is finished and the original process is not executed (No), the process moves to step S104.
Hereinafter, "No" in step S106 and the processing in S110 to S120 will be referred to as "first registration processing", and "Yes" in step S106 and processing in S114 to S120 will be referred to as "second registration processing". called.

[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,""employeeinformation,""batchprocessing," and "business 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 modification 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.

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, if the process moves to step S202, it is determined based on information from the employee terminal 200 whether the add button 82 has been selected on the payment information list screen 801. 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, processing to add payment information includes adding pro rata payment information according to the actual number of working days in each month when "Apply for route only" is selected, or when the work style is a mix of telecommuting and commuting. This corresponds to the process of adding daily payment information according to the actual number of working days. In addition, for example, when a new commuting route is used from the middle of the month, processing for adding pro rata payment information according to the number of days the new commuting route is used in that 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.
The daily pro rata payment information is information that is set when commuting transportation expenses incurred during the pro rata period are to be paid on a daily pro rata basis. 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 have applied for in the middle of the month, the commuting period for that month will be the period for which the per diem payment is applicable. 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 employees whose monthly transportation expenses are paid on a daily basis, or for work systems in which telecommuting and commuting work are mixed (mixed work system), for example, each month in question is a pro-rated payment period. Become. For example, June 1st to June 30th is set as the period to be paid on a daily basis. If pro-rated pay or a mixed work system continues from the following month onwards, each month will be set as a period eligible for pro-rated pay.

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 of modifying information that has already been input on the payment information setting screen.

Further, in step S206, if the correction 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 correction 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.

Other buttons include a cancel button, a delete button, a confirm button, and a cancel button, as shown in FIG. 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 payment information generation processing according to the first embodiment, and FIG. 12 is a diagram showing a performance information importing screen 901 for importing a CSV file of employee performance information. Further, FIG. 13 is a diagram showing a performance information importing screen 901 after importing a CSV file of employee performance information, and FIG. 14 is a diagram showing a second example of the payment information list screen 801.
When the supply information generation process is executed by the CPU 30, as shown in FIG. 11, the process first moves to step S300.

In step S300, it is determined whether there has been an instruction to generate payment information regarding a commuting route that has been officially registered through the first or second registration process. When it is determined that there is a generation instruction (Yes), the process moves to step S302, and when it is determined that there is no generation instruction (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 S302, work performance information corresponding to the calculation target month of the employee is acquired, and the process moves to step S304. Here, if the calculation target period is the calculation target month, daily transportation expenses are paid in the month following the target month based on the work performance of the target month.
Here, the commuting transportation expense calculation server 100 acquires the company ID, employee ID, and work performance information of the employee stored in the storage device 42 and corresponding to the calculation target month. The work performance information can be stored in the storage device 42 as a file in a predetermined file format, such as a CSV file, and can be obtained by selecting and importing the CSV file of the relevant employee, as shown in the example of FIG. Can be done. 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, all employees who have imported subsequent processes will be imported. It is now possible to do this 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. The example in FIG. 13 shows a case where the batch processing function is used and there are 5 subjects, but by pressing the execution button 91 on this screen, the subsequent processing will be performed for all 5 subjects. executed.

In step S304, the actual number of commuting days is obtained from the work performance information for the processing month obtained in step S302, and the process proceeds to step S306.
In step S306, fare information corresponding to the commuting route of the employee is acquired, and the process moves to step S308. Here, the commuting transportation expense calculation server 100 acquires information on the one-way ticket fare (normal fare) as fare information from the record of the employee in the employee-specific route information table 406.
In step S308, the amount of actual transportation expenses paid (hereinafter referred to as "actual expenses paid amount") is calculated based on the actual number of commuting days acquired in step S304 and the one-way fare (normal fare) acquired in step S306. . After that, the process moves to step S310.

Specifically, if the same commuting route is used for a round trip, the actual amount paid is 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 S310, payment information for providing the actual payment amount calculated in step S308 is generated. After that, the process moves to step S312.

In step S312, the payment information generated in step S310 is registered in the record of the corresponding employee in the employee-based daily payment information table 410. Thereafter, the series of processing is completed and the original processing is resumed.
As a result, as shown in FIG. 14, the payment information regarding the registered daily transportation expenses is displayed on the payment information list screen 801.
[Effects of the first embodiment]
Next, the effects of the first embodiment will be explained.
In the first embodiment, the commuting transportation expense calculation server 100 acquires application information including commuting route information, temporarily registers the acquired application information, calculates the amount of transportation expenses paid based on the acquired application information, Generates payment information related to calculated transportation expense payment amount, approves commuting route information related to acquired application information, approves generated payment information, and registers approved commuting route information and payment information. First registration processing (“No” in step S106 and processing in S110 to S120 above), processing for obtaining application information including commuting route information, provisional registration processing for the obtained application information, and commuting route information related to the obtained application information. The second registration process (“Yes” in step S106, the processes in S108, S114 to S120) that performs the approval process and the main registration process of the approved commuting route information ``Yes'' check box 63. In addition, the registration process for the selected one is executed.

As a result, by selecting the second registration process, commuting route information can be registered without unnecessary processing such as automatic generation of payment information, so for example, when working from home and commuting, It is possible to take flexible measures such as generating individual payment information according to the commuting situation of employees who are paid commuting expenses on a daily basis, such as employees who work on a daily basis. In addition, if you want to know the commuting route for employees who do not receive transportation expenses, such as employees who commute by foot or use free transportation, for example, due to work-related accidents, etc., you can also perform the second registration process. By selecting this option, you can register commuting route information without unnecessary processing such as automatically generating payment information.

Furthermore, in the first embodiment, for commuting routes that have been officially registered through the first or second registration process, transportation expenses corresponding to the actual number of commuting days in the calculation target period are provided separately from the first or second registration process. It is possible to calculate the amount, generate payment information regarding the transportation expense payment amount, and register the generated payment information. Thereby, payment information can be generated individually according to the commuting situation of the person eligible for the daily rate.
[Correspondence]
In the first embodiment, the employees to whom the transportation allowance amount is paid correspond to the recipients of inventions 1 and 2, step S106 corresponds to the selection means of invention 1, and steps S108 to S120 are Step S308 corresponds to the registration processing execution means of the first invention, step S308 corresponds to the transportation expense payment amount calculation means of the third invention, and step S310 corresponds to the payment information generation means of the third invention.

Further, in the first embodiment, step S108, step S112, and step S120 correspond to the route information registration process and payment information registration process of invention 1, and step S110 corresponds to the calculation process and generation process of invention 1. However, steps S114 and S116 correspond to the commuting route approval process and payment information approval process of the second invention.
[Second embodiment]
〔composition〕
Next, a second embodiment of the present invention will be described. 15 to 17 are diagrams 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.

The second embodiment calculates the daily transportation expenses corresponding to the actual number of commuting days or the scheduled number of commuting days in the calculation target period, separately from the registration processing, for the registered commuting route, and also calculates the amount of actual expenses paid or periodic discount paid. This embodiment differs from the first embodiment in that payment information for paying the minimum necessary payment amount is generated.
In the second embodiment, the payment information addition process includes, for example, a process of adding pro rata payment information according to the actual number of working days or scheduled working days in each month when "apply for route only" is selected; In the case of a work style that includes both telecommuting and commuting, processing is performed to add daily payment information according to the actual number of working days or the scheduled number of working days. In addition, for example, when a new commuting route is used in the middle of a month, the process to add pro rata payment information according to the number of days the new commuting route is used in that month is executed. This is different from the first embodiment. The other configurations are the same as those of the first embodiment.

〔motion〕
Next, the operation of the second 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 calculation period for daily prorated transportation expenses will be explained as the calculation target month.
FIG. 15 is a flowchart showing payment information generation processing according to the second embodiment, and FIG. 16 is a diagram showing a personal calendar information import screen 902 for importing a CSV file of employee's personal calendar information. .

When the supply information generation process is executed in the CPU 30, as shown in FIG. 15, the process first moves to step S400.
In step S400, it is determined whether there has been an instruction to generate payment information regarding a commuting route that has been officially registered through the first or second registration process. When it is determined that there is a generation instruction (Yes), the process moves to step S402, and when it is determined that there is no generation instruction (No), the determination process is repeated until there is a generation instruction.
In step S402, work performance information or personal calendar information corresponding to the calculation target month of the employee is acquired, and the process moves to step S404.

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. 12 or 16, 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.

Note that the determination of whether to pay the daily prorated transportation expenses in advance, in the current month, or in the next month is made using, for example, 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 S404, the actual number of commuting days is acquired from the work record information for the month to be processed acquired in step S402, or the expected number of days for commuting is acquired from the personal calendar information for the month to be processed acquired in step S402, and the process proceeds to step S406. Transition.

In step S406, fare information corresponding to the commuting route of the employee is acquired, and the process moves to step S408. 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 S408, the actual amount to be paid is calculated based on the total number of days obtained in step S404 and the one-way fare (normal fare) obtained in step S406. After that, the process moves to step S410.

In step S410, it is determined whether the actual payment amount calculated in step S408 and the monthly amount obtained in step S404 (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 it is lower (Yes), the process moves to step S412, and if it is determined otherwise. If so (No), the process moves to step S414.
If the process moves to step S412, payment information for paying the actual payment amount calculated in step S408 is generated. After that, the process moves to step S416.

On the other hand, if the process moves to step S414, 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 S416.
In step S416, the payment information generated in step S412 or S414 is registered in the record of the corresponding employee in the employee-based daily 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 registers the generated payment information in the corresponding record of the employee-based daily payment information table 410.

[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 process is a process that corresponds to a shortage or overpayment of daily pro-rated transportation expenses that may occur if the 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. 17 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. 17 according to the program.
When the post-daily payment exception processing 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 the execution condition is satisfied. If it is determined that the execution condition is satisfied (Yes), the process moves to step S502. If it is determined that the execution condition is not satisfied (No), the determination process is continued until the execution 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 regular 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 regular discount payment amount. In this case, an overpayment of daily transportation expenses will occur.

In this way, if there is a shortage or overpayment of daily transportation expenses, it is possible to set the execution conditions to be satisfied based on a request from the employee via the employee terminal 200.
However, if the pro-rated transportation expenses paid in advance exceed the actual cost of commuting, there is a high possibility that the employee will not proactively request that the overpaid amount 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.

Further, by inputting an instruction to satisfy the execution condition by the human resources employee, it is possible for the human resources employee to establish the execution condition at any timing.
If the process moves to step S502, work record information corresponding to the calculation target month of the employee is acquired, and the process moves to step S504. 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 is stored in the storage device 42 as a CSV file, and as shown in the example of FIG. 12 of the first embodiment, it is obtained by selecting and importing the CSV file of the relevant employee. be able to. 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 S504, fare information corresponding to the commuting route of the employee is acquired, and the process moves to step S506. 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 S506, the payment information corresponding to the calculation target month of the 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 S508, the actual payment amount is calculated based on the total number of days obtained in step S502 and the one-way fare (normal fare) obtained in step S504, and the calculated actual payment amount and the monthly amount obtained in step S504 are combined. Compare and set the lower amount as the actual payment amount. After that, the process moves to step S510.
In step S510, the amount of the payment information for the calculation target month of the employee obtained in step S506 is compared with the actual payment amount set in step S508, 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 S512, and if it is determined that it is not (No), the process moves to step S516.

If the process moves to step S512, shortfall payment information for paying the shortfall is generated, and the process moves to step S514. 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 S514, the insufficient pay information generated in step S512 is registered in the record of the corresponding employee in the employee-based daily prorated 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 S510 that the amount of the payment information is equal to or greater than the actual payment amount and the process moves to step S516, collection information for collecting overpayments is generated, and the process moves to step S518. 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 and the actual payment amount match, there is no shortage or overpayment, so the series of processes is ended and the original process is returned to without executing subsequent processes.
In step S518, the collection information generated in step S516 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.

[Effects of the second embodiment]
Next, the effects of the second embodiment will be explained.
In the second embodiment, in calculating the daily pro-rata transportation expenses for the commuting route of the employee who is officially registered through the first or second registration process, the average cost of this commuting route is calculated from the employee-specific route information table 406. Information on the fare and the monthly commuter fee (regular discount payment amount) is obtained. 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 regular discount payment amount, which is the obtained 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 prorated payment information table 410.

With such a configuration, it is possible to select a daily prorated transportation expense that is appropriate and the minimum amount necessary for the employee to be paid, and to generate payment information regarding the selected daily prorated transportation expense.
Furthermore, in the second embodiment, when daily transportation expenses are paid in advance or in the current month, depending on the fulfillment of the execution conditions, the commuting work performance (total number of commuting days) of the relevant employee in the target month, The actual payment amount is calculated based on the normal fare corresponding to the commuting route of the employee, and the lower of this actual payment amount and the monthly amount (regular discount payment amount) is set as the actual payment amount. do. 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 second embodiment, the employees to whom the transportation allowance amount is paid correspond to the recipients of inventions 1, 3, and 4, and steps S402 to S404 correspond to the commuting days information acquisition means of invention 4. , step S406 corresponds to the fare information acquisition means of the fourth invention, steps S408 to S410 correspond to the determination means of the fourth invention, and steps S412 to S414 correspond to the payment information generation means of the fourth invention.

Furthermore, in the second embodiment, the normal fare corresponds to the first fare of Invention 4, and the 1-month, 3-month, 6-month, and 12-month amounts of the commuter pass correspond to the second fare of Invention 4. Corresponding to this, the daily prorated transportation expenses correspond to the transportation expense payment amount of Inventions 1 to 3, the actual expense payment amount corresponds to the first payment amount of Invention 4, and the periodic discount payment amount corresponds to the second payment amount of Invention 4. It corresponds to the amount paid.
Furthermore, in the second embodiment, the storage device 42 corresponds to the fare information storage means and the commuting days information storage means of the fourth invention.

[Third embodiment]
〔composition〕
Next, a third embodiment of the present invention will be described. FIG. 18 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 the third embodiment, the check box 63 for "Apply for route only" is checked, and the employee applies for the actual payment amount via the employee terminal 200 for the commuting route that has been officially registered through the second registration process. This embodiment differs from the first embodiment in that it can perform the following steps. The other configurations are the same as those of the first embodiment.

〔motion〕
Next, the operation of the third embodiment will be explained.
[Payment information generation process]
FIG. 18 is a flowchart showing the actual payment amount application process according to the third embodiment.
When the actual expense payment amount application process is executed by the CPU 30, as shown in FIG. 18, the process first moves to step S600.
In step S600, it is determined whether or not an actual expense 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 S602; if it is determined that it has not been received (NO), the process proceeds to step S602. The determination process is repeated until it is received.

Here, the actual expense application request can be made by pressing the ``Application'' button on the main menu on the employee terminal 200 and selecting, for example, ``Actual Expense Application'' from among the multiple submenus displayed. 100.
If the process moves to step S602, input screen information for actual expense application information is transmitted to the employee terminal 200 that is the source of the actual expense application request, and the process moves to step S604.
As a result, an actual expense application information input screen (not shown) is displayed on the display device of the employee terminal 200. The employee inputs information related to the actual expense application on the actual expense application information input screen via the employee terminal 200. Specifically, by selecting one of the registered commuting routes, the user inputs the information on the commuting route for which the actual expense is to be applied for, and then inputs the information on the actual number of working days during the period for which the actual expense is to be applied for.

In step S604, it is determined whether or not actual expense application information has been received from the employee terminal 200. If it is determined that it has been received (Yes), the process moves to step S606; if it is determined that it has not been received (No), the process proceeds to step S606. The process moves to step S614.
Here, when the application button is pressed on the actual expense application information input screen, the input actual expense application information is transmitted to the commuting transportation expense calculation server 100.
If the process moves to step S606, actual expense payment information is generated based on information on the commuting route specified in the received actual expense application information. After that, the process moves to step S608.

In step S608, the actual expense payment information generated in step S606 is temporarily registered in the employee-based daily payment information table 410. After that, the process moves to step S610.
In step S610, information on the department to which the applicant belongs (department ID) is acquired from the employee information master table 604, and from the department information table 412, approval party information (with approval authority) corresponding to the acquired department ID is obtained. The employee's employee ID) is acquired, and the process moves to step S612.

In step S612, 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 commuting route information that has been approved and applied for is permitted, and the actual expense payment information that has been temporarily registered in the employee-based daily payment information table 410 is permanently registered.
In addition, if it is determined in step S604 that no application information has been received and the process moves to step S614, it is determined whether or not an application cancellation request has been received, and if it is determined that it has been received (Yes), a series of If it is determined that the process is finished and the original process is not executed (No), the process moves to step S604.

[Effects of the third embodiment]
Next, the effects of the third embodiment will be explained.
In the third embodiment, the employee himself or herself is able to apply for actual expenses via the employee terminal 200 for the commuting route that has been officially registered through the second registration process. With such a configuration, it is possible to reduce the time and effort required by human resources employees, general affairs employees, etc. who perform work related to transportation expenses to apply for actual expenses.
[Correspondence]
In the third embodiment, the employees to whom the transportation allowance amount is paid correspond to the recipients of inventions 1 to 4, and steps S604 to S612 correspond to the third actual expense application processing execution means of invention 5. ing.

[Modified example]
In the above embodiment, the second registration process is used to register a commuting route for employees who commute using a new commuting route from the middle of the month, but the present invention is not limited to this configuration. For example, a commuting route is officially registered in the first registration process, and it is determined whether or not the usage starts in the middle of the month based on the information on the usage start month or usage start date included in the registration information. If it is determined that the use begins in the middle of the month, the amount of transportation expenses paid for that month will be calculated on a daily basis, and the amount of transportation expenses paid for the following month and thereafter will be calculated using a commuter pass. It may also be a configuration. Alternatively, the configuration is such that only the amount of transportation expenses paid for the month following the month in question is calculated, and for the corresponding month, the amount of transportation expenses paid is calculated on a daily basis through payment information addition/correction processing, etc., and the transportation expenses are calculated on a daily basis. A configuration may also be adopted in which daily payment information regarding the payment amount is registered.

Further, in the above-described embodiment and its modified example, the configuration is such that approval processing is performed for the applied commuting route information and its payment information in the first registration process and the second registration process, but the configuration is not limited to this. For example, in a company with a small number of employees, when a person in charge of human resources or accounting is responsible for approving and registering commuting route information for all employees by themselves, the process of approving commuting routes and payment information may be omitted or omitted. It may be configured such that settings can be made.
In addition, in the above-described embodiment and its variations, the actual expense amount for the month to be calculated is compared with the monthly amount of the commuter pass, and the lower one is set as the daily transportation expense. It is not limited to this configuration. 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.

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 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 modified examples, the present invention is realized as a network system, but the present invention is not limited to this, and may 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, 15, 17, and 18, programs stored in the ROM in advance 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, 405...Vehicle-specific payment rule master table, 406...Employee-specific route information table, 408...Employee-specific payment information table, 410 ...Employee-based 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, 901...Actual information import screen, 902...Personal calendar information import screen

Claims (5)

A payment calculation system that calculates the amount of transportation expenses paid to a person eligible for payment for commuting routes that the person eligible for payment can use for commuting,
A route information registration process for registering commuting route information regarding the commuting route of the person eligible for payment, a calculation process for calculating the amount of transportation expenses paid based on the registered commuting route information, and payment information regarding the calculated amount of transportation expenses paid. Either of a first registration process that performs a generation process to generate and a payment information registration process to register the generated payment information, and a second registration process that performs a process that is completed with the route information registration process separately from the first registration process. a selection means for selecting whether for the same person eligible for payment;
Executing a registration process in which when the first registration process is selected by the selection means, the first registration process is executed, and when the second registration process is selected by the selection unit, the second registration process is executed. A payment calculation system characterized by comprising a means. In claim 1,
The first registration process further includes, for the applied commuting route, commuting route approval processing for approving commuting route information regarding the commuting route and payment information approval processing for approving the generated payment information,
The payment calculation system is characterized in that the second registration process further includes a commuting route approval process for approving commuting route information regarding the applied commuting route. In claim 1 or 2,
For commuting routes registered through the first or second registration process, separately from the first or second registration process, corresponds to the actual number of commuting days or scheduled commuting days during the calculation period for the person eligible for payment related to the commuting route. a means for calculating the amount of transportation expenses to be paid;
A payment calculation system comprising: payment information generation means for generating payment information regarding the transportation allowance payment amount calculated by the transportation allowance payment amount calculation means. In claim 3,
From the fare information storage means that stores fare information regarding fares including the first fare of the transportation facility required for commuting on the commuting route and the second fare that is cheaper than the first fare, information regarding the calculation of the amount to be paid for transportation expenses is obtained a fare information acquisition means for acquiring fare information corresponding to the commuting route of the person eligible for payment;
Commuting days information obtaining means for obtaining commuting days information regarding the actual commuting days or scheduled commuting days for the calculation target period from commuting days information storage means storing commuting days information regarding the actual commuting days or scheduled commuting days of the person eligible for the payment; ,
Regarding the commuting route registered through the first or second registration process, commuting during the calculation target period is calculated based on the fare information acquired by the fare information acquisition means and the commuting days information acquired by the commuting days information acquisition means. The first payment amount when the amount of transportation expenses corresponding to the actual number of days or scheduled number of commuting days is calculated using the first fare using the transportation expenses amount calculation means and the actual number of commuting days or scheduled number of commuting days during the calculation period. a determining means for determining the magnitude of the second payment amount when the corresponding transportation allowance payment amount is calculated by the transportation allowance payment amount calculation means using the second fare;
The payment calculation system is characterized in that the payment information generation means generates payment information regarding the lower of the first payment amount and the second payment amount based on the determination result of the determination unit. . In claim 1 or 2,
Connected for communication with the target terminal used by the recipient,
In response to the actual expense application request from the target person's terminal, actual expense application information including information on the commuting route registered through the second registration process from the target person's terminal and information on the actual number of commuting days using the said commuting route. Execute actual expense application processing including acquisition processing, calculation processing of transportation expense payment amount based on the acquired actual expense application information, generation processing of payment information regarding the transportation expense payment amount, and second payment information approval processing to approve the payment information. A payment calculation system characterized by comprising an actual cost application processing execution means.

Images