JP2023150274A - Transportation expense calculation system - Google Patents

Abstract

To provide a transportation expense calculation system that allows separate applications for outward and return routes when the routes are different.SOLUTION: A transportation expense calculation server 100 is configured to: acquire commuting route information including a commuting route that an employee can use for commuting and a route direction type indicating an outward or return route of the commuting route that the employee applies for use, in response to a new application request for the commuting route from an employee terminal 200; and calculate commuting transportation expenses when commuting for either the outward or return route of the commuting route that the employee applies for based on transportation expense information (one-way fare) of an employee-specific route information table 414 in which the transportation expense information related to the transportation expense required for commuting on the commuting route is registered and the acquired commuting route information.SELECTED DRAWING: Figure 9

Description

Application for application of Article 30, Paragraph 2 of the Patent Act has been filed Baitolhikuma Co., Ltd. has released the "Transportation Expense Calculation System" (Commuting Management Arvo) on its website.

The present invention relates to a transportation expense calculation system for calculating transportation expenses for recipients.

BACKGROUND ART Conventionally, a technique described in Patent Document 1, for example, is known as a technique for calculating a commuting allowance in response to an application from a recipient when commuting expenses are changed due to new generation, route change, discontinuation, etc.
The technology described in Patent Document 1 is a technology that calculates the amount of salary transportation expenses paid in cooperation with the payroll system when there is an application for a change in commuting transportation expenses, and it defines the payment standards and calculation method of the company's commuting allowance. When application data for commuting transportation expenses is entered, the application data is converted to commuting allowance data based on the commuting allowance definition, and when the amount of transportation expenses paid for the salary is settled, the commuting allowance data is recalculated. I do.

Japanese Patent Application Publication No. 2016-192201

However, in the technology described in Patent Document 1, when calculating commuting transportation expenses, consideration is given to, for example, cases in which only the outbound trip is used, cases in which only the return trip is used, and cases where the outbound and return trips are on different commuting routes. There is no mention of how to apply in such cases.
Therefore, the present invention has been made by focusing on the unresolved problems of the conventional technology. The purpose is to provide a calculation system.

[Invention 1] In order to achieve the above object, the transportation expense calculation system of Invention 1 calculates the travel route that the person eligible for payment can use to travel to his/her place of work and the travel route that the person eligible for payment applies for use. A travel route information acquisition means that acquires travel route information including round trip type indicating an outbound or return trip, and a transportation cost information storage means that stores transportation cost information regarding transportation costs required for traveling to the workplace on the travel route. Based on the travel route information acquired by the travel route information acquisition means and the travel route information, the outbound or return route of the travel route that the recipient applies for is determined based on the travel route information obtained by the travel route information and the travel route information acquired by the travel route information acquisition means. and a transportation expense calculation means for calculating transportation expenses.

With such a configuration, the travel route information acquisition means can collect a round trip indicating the travel route that the person eligible for payment can use to travel to his or her place of work, and the outbound or return route of the travel route that the person eligible for payment applies for use. When the travel route information including the type is acquired, the transportation cost calculation means calculates the transportation cost information and the transportation cost information of the transportation cost information storage means that stores the transportation cost information regarding the transportation cost required for traveling to the place of work on the travel route. Based on the travel route information acquired by the travel route information acquisition means, the transportation expenses for the outbound or return leg of the commuting route that the eligible person applies for use when traveling to his or her workplace along the travel route are calculated. be done.

Here, the transportation expenses include commuting expenses, transportation expenses required for traveling to a business trip destination, and the like.
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, the transportation expense calculation system of Invention 2 is the transportation expense calculation system of Invention 1, in which the transportation expense information includes first transportation expense information regarding transportation expenses related to usage over a period of multiple days and one day's transportation expense information. an application date acquisition means that includes second transportation expense information regarding transportation expenses related to usage and acquires information on an application date to which the second transportation expense information is applied; and a one-way travel route for which the second transportation expense information is applied. or a usage direction type information acquisition means for acquiring information on a usage direction type indicating which of the round trips is used by the recipient, and the transportation cost calculation means includes the second transportation cost information and the application date. The transportation fee on the applicable day is calculated based on the information on the applicable date acquired by the acquisition means and the information on the usage direction type acquired by the usage direction type information acquisition means.

With this configuration, the application date acquisition means acquires information on the application date to which the second transportation cost information is applied, and the usage direction type information acquisition means determines the one-way travel route to which the second transportation cost information is applied. Or, when the usage direction type information indicating the round trip usage direction is acquired, the transportation cost calculation means acquires the second transportation cost information, the applicable date information acquired by the application date acquisition means, and the usage direction type information acquisition means. The transportation fee for the applicable day is calculated based on the information on the usage direction type.
Here, the first transportation cost information corresponds to information regarding transportation costs using regular trains such as trains and buses, and the second transportation cost information corresponds to information regarding transportation costs using tickets and one day using a car. This includes information on transportation expenses (including parking lot fees, if applicable), and information on transportation expenses using bicycles (daily bicycle parking fee, etc.).

[Invention 3] Furthermore, in the transportation expense calculation system of Invention 2, in the transportation expense calculation system of Invention 2, the usage direction type information acquisition means may acquire the information for each of the plurality of application days to which the second transportation expense information is applied. The transportation cost calculation means obtains information on the usage direction type, and the transportation cost calculation means calculates the second transportation cost information, the application date information acquired by the application date acquisition means, and the application date information acquired by the usage direction type information acquisition means. Transportation expenses for the plurality of application days are calculated based on the information on the usage direction type.

With such a configuration, the usage direction type information acquisition means acquires the usage direction type information for each of the plurality of application days to which the second transportation cost information is applied, and the transportation cost calculation means The transportation expenses for the plurality of applicable days are calculated based on the cost information, the information on the applicable date acquired by the applicable date acquisition means, and the information on the usage direction type for each applicable date acquired by the usage direction type information acquisition means.
[Invention 4] Further, in the transportation expense calculation system of Invention 4, in the transportation expense calculation system of any one of Inventions 1 to 3, the travel route information acquisition means further comprises a system for calculating transportation expenses by which the person eligible for payment travels to his or her place of work. Travel distance information regarding the distance of available travel routes is acquired, and the transportation cost information storage means stores, as the transportation cost information, a predetermined amount of fuel for the vehicle used by the recipient to travel to his/her place of work. The transportation cost calculation means stores information on the fuel consumption indicating the travel distance and the fuel cost per the predetermined amount, and when calculating the transportation cost for traveling to the workplace using a vehicle, the transportation cost calculation means stores information on the fuel consumption and fuel of the vehicle. The transportation cost is calculated based on the transportation cost and the travel distance information acquired by the travel route information acquisition means.

With such a configuration, the travel route information acquisition means further acquires travel distance information regarding the distance of the travel route that the person eligible for payment can use to travel to his or her place of work, and the transportation expense information storage means stores the travel distance information. As cost information, information on fuel consumption indicating the travel distance per predetermined amount of fuel of the vehicle used by the recipient to travel to his or her place of work and information on the fuel cost per predetermined amount is stored, and the transportation cost calculation means calculates the cost of the vehicle. When calculating the transportation cost for traveling to the place of work using the vehicle, the transportation cost is calculated based on the fuel efficiency and fuel cost of the vehicle, and the travel distance information acquired by the travel route information acquisition means.

[Invention 5] Furthermore, the transportation expense calculation system of Invention 5 is such that, in the transportation expense calculation system of any one of Inventions 1 to 4, group identification information that is identification information of an approved group to which the payment recipient belongs, From the group identification information storage means stored in association with the target person identification information that is the identification information of the relevant payee, a group corresponding to the target person identification information of the payee who has applied for the travel route or transportation expenses. group identification information acquisition means for acquiring identification information; and approval destination information storage means for storing information on a plurality of approval destinations for the application, including approval destinations common to multiple existing departments, in association with the group identification information. an approval destination information acquisition means for acquiring information on the approval destination corresponding to the group identification information acquired by the group identification information acquisition means; and approval processing request sending means for sending an approval processing request to.

With such a configuration, the group identification information acquisition means associates the group identification information, which is the identification information of the approved group to which the payment recipient belongs, with the recipient identification information, which is the identification information of the payment recipient. Group identification information corresponding to the target person identification information of the recipient who applied for travel route or transportation expenses is acquired from the group identification information storage means stored in The approval destination corresponding to the group identification information acquired by the group identification information acquisition means is selected from the approval destination information storage means that stores information on a plurality of approval destinations for the application, including a common approval destination, in association with group identification information. information is acquired, and the approval processing request transmitting means transmits an approval processing request to each approval party based on the information on the approval party acquired by the approval party information obtaining means.

[Invention 6] Furthermore, the transportation expense calculation system of Invention 6 performs one of the collective processing related to fare revision or the collective processing related to salary coordination of transportation expenses in the transportation expense calculation system of any one of Inventions 1 to 5. a batch processing information acquisition means for acquiring information on batch processing; a schedule information acquisition means for acquiring batch processing execution schedule information corresponding to the information acquired by the batch processing information acquisition means; and batch processing execution means for executing batch processing corresponding to the information acquired by the batch processing information acquisition means based on execution schedule information.

With such a configuration, the batch processing information acquisition means acquires information on the batch processing to be executed among the batch processing related to fare revisions or the batch processing related to salary coordination of transportation expenses, and the schedule information obtaining means acquires information on the batch processing to be executed. When the batch processing execution schedule information corresponding to the information obtained by the processing information acquisition means is acquired, the batch processing execution means acquires the batch processing execution schedule information based on the execution schedule information acquired by the schedule information acquisition means. Batch processing corresponding to the information is executed.

[Invention 7] Furthermore, the transportation expense calculation system of Invention 7 is the transportation expense calculation system of any one of Inventions 1 to 6, which further includes a legally related transportation expense information storage means for registering information related to transportation expenses stipulated by law. A common provision for all companies that use the transportation expense calculation system.
[Invention 8] On the other hand, in order to achieve the above object, the transportation expense calculation system of Invention 8 calculates transportation expenses related to the use of a multi-day period for travel routes that can be used by recipients to travel to their workplaces. application date acquisition means for acquiring information on the application date to which the second transportation cost information is applied in the transportation cost information storage means for storing first transportation cost information regarding the transportation cost related to the use of the vehicle and second transportation cost information regarding the transportation cost related to one day's usage; and a usage direction type information acquisition means for acquiring information on a usage direction type indicating which of the one-way or round trip travel routes to which the second transportation fee information is applied is used by the person to be paid; and transportation cost calculation means for calculating the transportation cost on the applicable day based on the cost information, the information on the applicable date acquired by the applicable date acquisition means, and the information on the usage direction type acquired by the usage direction type information acquisition means. .

[Invention 9] In addition, in order to achieve the above object, the transportation expense calculation system of Invention 9 calculates transportation expenses related to the use of a multi-day period for travel routes that can be used by recipients to travel to their workplaces. application date acquisition means for acquiring information on the application date to which the second transportation cost information is applied in the transportation cost information storage means for storing first transportation cost information regarding the transportation cost related to the use of the vehicle and second transportation cost information regarding the transportation cost related to one day's usage; and obtaining usage direction type information for each of the plurality of application days to which the second transportation expense information is applied, to obtain usage direction type information indicating which of the one-way or round trip travel route is used by the person eligible for payment. and the plurality of applicable dates based on the second transportation cost information, the applicable date information acquired by the applicable date acquisition means, and the usage direction type information for each applicable date acquired by the usage direction type information acquisition means. and a transportation expense calculation means for calculating transportation expenses.

As explained above, according to the transportation expense calculation system of invention 1, it is possible to apply separately for the outbound trip and the return trip regarding the travel route related to the calculation of transportation expenses.For example, when using only the outbound trip, When only the return trip is used, transportation costs can be easily calculated if the travel routes for the outbound and return trips are different.
Furthermore, according to the transportation cost calculation system of invention 2, information on the usage direction type and application date of the travel route to which the second transportation cost information is applied is acquired, and the second transportation cost information, the acquired usage direction type and application date are Based on this information, transportation costs can be calculated on the applicable date. As a result, when transportation expenses are paid on a daily basis, it is possible to easily calculate the transportation expenses on the day on which the daily rate is applied.

Furthermore, according to the transportation cost calculation system of invention 3, it is possible to obtain the direction of use type set individually for each of the plurality of application days to which the second transportation cost information is applied. Transportation expenses can be easily calculated when there is a mixture of use (return only) and round trip use.
Furthermore, according to the transportation cost calculation system of invention 4, the transportation cost for the use of the vehicle is calculated using the fuel efficiency, fuel cost, and travel distance of the vehicle used for commuting, so the transportation cost is calculated based on the transportation cost for each vehicle. The cost can be calculated.

Furthermore, according to the transportation expense calculation system of Invention 5, even if the real organizations (actual departments) to which they belong are different, if the employees belong to the approved group with the same group identification information, they can cross real organizations. Since approval processing can be performed, it is possible to perform approval processing for registration of application information using a flexible approval route for each applicant.
Furthermore, according to the transportation expense calculation system of the sixth aspect, batch processing related to fare revisions or batch processing related to salary coordination of transportation expenses can be easily processed all at once according to a desired schedule. As a result, the processing load can be reduced by setting a schedule to perform batch processing in the middle of the night or on holidays.

Furthermore, according to the transportation expense calculation system of Invention 7, it is not necessary for each company to have a legally-related transportation expense information storage means for registering information related to transportation expenses stipulated by law. By managing the information, it is possible to reduce the burden on the person in charge at each company.
On the other hand, according to the transportation expense calculation system of Invention 8, the same operation and effect as Invention 2 can be obtained.
Further, according to the transportation expense calculation system of Invention 9, the same functions and effects as those of Invention 3 can be obtained.

FIG. 1 is a block diagram showing the configuration of a network system according to the present embodiment. 1 is a diagram showing the hardware configuration of a transportation expense calculation server 100. FIG. (a) to (f) show the data structures of the company master table 400, vehicle-specific payment rule master table 402, charge master (car) table 404, workplace master table 406, fuel unit price master table 408, and fuel efficiency master table 409. FIG. (a) to (e) are diagrams showing data structures of a private vehicle information master table 410, an employee information master table 412, an employee route information table 414, an employee allowance information table 416, and an employee daily allowance information table 418. It is. (a) to (d) are diagrams showing data structures of a department information table 420, a batch processing master table 422, a tax-exempt limit_public transportation master table 424, and a tax-exempt limit_transportation equipment master table 426. It is a flowchart which shows employee information registration processing. 5 is a diagram showing an employee information list screen 500. FIG. It is a diagram showing a new employee information registration screen 501. It is a flowchart which shows commuting route information new application processing. It is a diagram showing an application information input screen 600. (a) and (b) are diagrams for explaining a mechanism for constructing an approval route. (a) is a diagram showing an example of setting an employee group ID, department ID, and personnel authority, and (b) is a diagram showing an example of an approval route. It is a flowchart showing private vehicle transportation expense calculation processing. (a) is a diagram showing a part of the application information input screen 601, (b) is a diagram showing a display screen 700 of basic information registered in the private vehicle information master table 410, and (c) is a diagram showing a display screen 700 of basic information registered in the private vehicle information master table 410. , is a diagram showing a display screen 701 of basic information registered in a fuel consumption master table 409. 7 is a diagram showing a display screen 702 of reference information and fuel cost information registered in a fuel unit price master table 408. FIG. It is a flowchart showing payment information addition/correction processing. It is a diagram showing a route list screen 800 for selected employees. It is a diagram showing a payment information list screen 801. It is a diagram showing a daily payment information setting screen 802. It is an enlarged view of the screen portion for setting the usage direction type of the daily payment information setting screen 802. It is a figure which shows the daily prorated payment date setting screen when the usage direction type is selected for each date. It is a flowchart which shows the daily payment amount calculation process. It is a figure which shows the screen after the daily payment amount calculation when round trip is selected as a usage direction type. 12 is a flowchart illustrating schedule execution processing for batch processing. 9 is a diagram showing a batch processing setting screen 900. FIG.

〔composition〕
Embodiments of the present invention will be described below. 1 to 25 are diagrams showing this embodiment.
First, the configuration of this embodiment will be explained.
FIG. 1 is a block diagram showing the configuration of a network system according to this embodiment.
As shown in FIG. 1, the Internet 199 includes a transportation expense calculation server 100 that provides a cloud service (hereinafter referred to as "transportation expense calculation service") that supports transportation expense calculation, and a transportation expense calculation server 100 that uses the transportation expense calculation service. It is connected to an employee terminal 200 installed for each employee of the company.

[Hardware configuration of transportation expense calculation server 100]
Next, the configuration of the transportation expense calculation server 100 will be explained.
FIG. 2 is a diagram showing the hardware configuration of the transportation expense calculation server 100.
As shown in FIG. 2, the transportation expense calculation server 100 includes a CPU (Central Processing Unit) 30 that performs calculations and controls the entire system based on a control program, and a ROM that stores a control program for the CPU 30 in a predetermined area in advance. (Read Only Memory) 32, RAM (Random Access Memory) 34 for storing data read from ROM 32 etc. and calculation results necessary in the calculation process of CPU 30, and mediating data input/output to external devices. The I/F (InterFace) 38 is 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 comprised of a stationary terminal such as the above-mentioned transportation expense calculation server 100, or a portable terminal such as a smartphone or a tablet. In the former case, the hardware configuration is the same as that of the 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 the functions of the transportation expense calculation server 100]
Next, the functions of the transportation expense calculation server 100 will be explained.
The transportation expense calculation server 100 has the following functions, which are realized by the CPU 30 executing a predetermined program stored in a predetermined area of the ROM 32.

The transportation expense calculation server 100 provides a service that allows employees with employee authority who are registered in the system to use a function to apply for commuting route information for settling commuting transportation expenses such as commuting routes. In addition, the company provides a service that allows employees with registered upper-level employee authority to apply for commuting route information and to approve the submitted commuting route information. In addition, for employees with registered personnel authority, we have a function to register the information of all employees subject to commuting management, and a function to change, correct, cancel, etc. the commuting route information of registered employees, etc. All related to commuting transportation expenses. Provide services that allow you to use the functions of

[About the functions of the employee terminal 200]
Next, the functions of the employee terminal 200 will be explained.
The employee terminal 200 has the following functions, which are realized by the CPU executing a predetermined program stored in a predetermined area of the ROM.
The employee terminal 200 logs into a cloud service (hereinafter referred to as "transportation expense calculation service") that supports the settlement management of commuting transportation expenses provided by the transportation expense calculation server 100 and uses various functions provided by this service. can do. Specifically, you can use functions according to the authority level (employee, senior employee, human resources) set for each login account.

[About various tables]
Next, various tables stored in the storage device 42 will be explained.
3(a) to (f) show data in the company master table 400, vehicle-specific payment rule master table 402, charge master (car) table 404, work place master table 406, fuel unit price master table 408, and fuel efficiency master table 409. It is a figure showing a structure.
As shown in FIGS. 3A to 3F, the storage device 42 includes a company master table 400 in which company information is registered, and a vehicle-specific payment rule master table in which information on transportation expense payment rules for each vehicle is registered. 402 is stored. Additionally, a fee master (car) table 404 for registering information on fees related to commuting transportation expenses and a workplace master table 406 for registering information on workplaces for each company are stored. Furthermore, a fuel unit price master table 408 that registers information on the fuel unit price of cars and motorcycles used for commuting, and a fuel efficiency master table 409 that registers information on fuel consumption of cars and motorcycles used for commuting 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.

In the vehicle-specific payment rule master table 402, one record is registered for each combination of company ID, payment rule ID, and vehicle ID, as shown in FIG. 3(b). 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.

As shown in FIG. 3C, in the charge master (car) table 404, one record is registered for each combination of company ID, charge type ID, charge ID, and application start date. Each record includes company ID, charge type ID, charge type name, charge master type, charge ID, charge name, amount calculation formula, number of business days classification, payment amount classification, application start date, application end date, last update date, last Main information including the updater and other information is registered.
Here, the charge type ID is information for identifying the charge type, and is composed of, for example, a unique number for each charge type (for example, only numbers, a combination of letters and numbers), etc. Further, the charge master type is information indicating the type of charge (charge name, distance, car), and in this table, it is a car. Further, the charge ID is information for identifying the charge indicated by the charge name, and is composed of, for example, a unique number for each charge name (for example, only numbers, or a combination of letters and numbers). In addition, the amount calculation formula is information on the calculation formula for calculating commuting transportation expenses for privately owned vehicles such as cars, the number of business days is information indicating the number of business days, and the payment amount classification indicates one-way or round trip. It is information.

In addition to automobiles, the fare master table includes a fare master (fare name) table for trains and buses, and a fare master (distance) table for motorbikes and bicycles (three or more wheels). Illustrations are omitted.
As shown in FIG. 3D, the workplace master table 406 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. Hereinafter, gasoline (regular) will be simply referred to as "gasoline," gasoline (high-octane) will simply be referred to as "high-octane," and diesel (light oil) will simply be referred to as "diesel."

In the fuel unit price master table 408, as shown in FIG. 3(e), one record is registered for each combination of company ID, fuel unit price type ID, fuel unit price classification, and application start date. Each record contains main information including company ID, fuel unit price type ID, fuel unit price type name, fuel unit price classification, fuel unit price, application start date, application end date, last update date, last updater, and other information. ing.
Here, the fuel unit price category is information that categorizes the fuel unit price type (regular, high-octane, diesel, EV, PHV, FCV, etc.), and the fuel unit price is information on the unit price corresponding to the fuel unit price category.

As shown in FIG. 3F, the fuel efficiency master table 409 has one record registered for each combination of company ID, fuel efficiency type ID, and application start date. In each record, main information including a company ID, fuel efficiency type ID, fuel efficiency type name, fuel efficiency, application start date, application end date, last update date, last updater, and other information is registered.
Here, the fuel efficiency type ID is information for identifying the fuel efficiency type of a car, such as common to all cars, gasoline car (1500CC), gasoline car (2000CC), etc. For example, a unique number for each fuel efficiency type (e.g. It consists of numbers only, combinations of letters and numbers), etc. Further, the fuel efficiency is information indicating the fuel efficiency (km/L (liter)) corresponding to the fuel efficiency type ID.

4(a) to (e) show the data structures of the private vehicle information master table 410, the employee information master table 412, the route information table for each employee 414, the payment information table for each employee 416, and the daily payment information table for each employee 418. FIG.
As shown in FIGS. 4(a) to 4(e), the storage device 42 includes a private vehicle information master table 410 in which information on vehicles owned by employees is registered, and an employee information master table 412 in which employee information is registered. remembered. In addition, an employee-specific route information table 414 in which commuting route information for each employee is registered, and an employee-specific payment information table 416 in which commuting transportation expense payment information for each employee is registered are stored. Furthermore, an employee-based daily pro-rata payment information table 418 is stored that registers the pro-rata transportation allowance payment information for each employee.

As shown in FIG. 4A, one record is registered in the private vehicle information master table 410 for each combination of company ID, employee ID, and application start date. Each record includes company ID, employee ID, fuel efficiency type ID, fuel unit price classification, vehicle number (number), vehicle model name, vehicle model number, vehicle body number, vehicle inspection number, vehicle inspection certificate holder, application start date, application end date, Key information including the last updated date, last updated user, and other information is registered. Here, the employee ID is information for identifying an employee, and is composed of, for example, a unique number for each employee (for example, only numbers or a combination of letters and numbers).

As shown in FIG. 4B, one record is registered in the employee information master table 412 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), phone number, email address, work ID, work name, employee group ID, Key information including department ID, department name, employee classification, payment rule ID, password, authority level, map information, application start date, application end date, last update date, last updater, and other information is registered. ing.

Here, the employee group ID is information for identifying the real organization to which the employee belongs, and is composed of, for example, a unique number for each real organization (for example, only numbers, a combination of letters and numbers), etc. In addition, the department ID is identification information dedicated to the workflow for managing approvers and proxy applicants related to the workflow (approval route). It consists of a combination of letters and numbers). Further, 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. Furthermore, the map information is information about the employee's home location and the nearest station.

As shown in FIG. 4C, one record is registered in the employee-specific route information table 414 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 amount, 3 month amount, 6 month amount, and 12 month amount are the amounts of commuting transportation expenses for 1, 3, 6, and 12 months for the set commuting method and route direction type, and the route reference date is This is the reference date when the commuting route becomes valid.

In the employee-specific payment information table 416, one record is registered for each combination of company ID, employee ID, route ID, and payment ID, as shown in FIG. 4(d). 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. 4(e), in the employee-based daily payment information table 418, 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.

5A to 5D are diagrams showing the data structures of the department information table 420, the batch processing master table 422, the tax-exempt limit_public transportation master table 424, and the tax-exempt limit_transportation equipment master table 426. .
As shown in FIGS. 5(a) to 5(d), the storage device 42 includes a department information table 420 in which information on approvers and proxy applicants for each department is registered, and information on batch processing (collective processing). A batch processing master table 422 to be registered and a tax-exempt limit_public transportation master table 424 to register information on the tax-exempt limit of commuting expenses using public transportation are stored. In addition, a tax-exempt limit_transportation equipment master table 426 is stored that registers information on the tax-exempt limit of commuting transportation expenses using transportation equipment.

As shown in FIG. 5(a), the department information table 420 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 of the department ID, and the proxy applicant ID is This is the employee ID of an employee who has the authority to apply for commuting routes on behalf of other employees who belong to the company.

As shown in FIG. 5B, one record is registered in the batch processing master table 422 for each combination of company ID, service ID, and application start date. Each record includes the service ID, company ID, process content, batch startup date classification (specific day/specific day of the week/specific year, month, and day), startup date/startup day of the week/startup date, startup time, application start date, and application end. Key information including date, last updated date, last updated user, and other information is registered.
Here, the service ID is information for identifying a batch processing service, and is composed of, for example, a unique number (for example, only numbers, or a combination of letters and numbers) for each service (processing content). Further, the process content is information indicating the content of the batch process corresponding to the service ID, and the batch startup date classification is information indicating the classification of the startup date on which the batch process is started. Batch processing services include, for example, a batch processing service that reflects revised fares on commuting transportation expenses, and a batch processing service that creates linked data for commuting transportation expenses with revised fares and salaries. and so on. In addition, examples of the batch startup date classification include a specific day, a specific day of the week, and a specific year, month, and day.

In this embodiment, service IDs corresponding to two types of batch processing are registered: batch processing related to fare revision and batch processing related to salary coordination of commuting expenses.
In the tax-exempt limit_public transportation master table 424, one record is registered for each application start date, as shown in FIG. 5(c). Each record includes main information including tax exemption limit, reason for change, application start date, application end date, and other information.
The tax-exempt limit is information that indicates the maximum amount of commuting transportation expenses that are tax-free when using public transportation, and the reason for change is information that indicates the reason for changing the tax-free limit. For example, " Due to system changes,'' etc.

As shown in FIG. 5(d), one record is registered in the tax-exempt limit_transportation equipment master table 426 for each combination of minimum distance and application start date. Each record has registered main information including a minimum distance limit, a maximum distance limit, a tax-exempt limit amount, reason for change, application start date, application end date, and other information.
Here, the tax-exempt limit for commuting transportation expenses using transportation equipment such as cars and motorcycles is set to the above amount for each combination of the minimum distance limit and the maximum distance limit. Specifically, if the minimum distance limit is 0 km and the maximum distance is 2 km, the distance required for commuting is 0 km or more and less than 2 km, and the tax-exempt limit is 0 yen. Similarly, if the minimum distance limit is 2 km and the maximum distance limit is 10 km, the tax-free limit will be 4,200 yen. In this way, the tax-free limit is determined for each range between the minimum distance limit and the maximum distance limit, and if the minimum distance limit is 55 km, that is, the distance required for commuting is 55 km or more, the tax-free limit is the maximum of 31,600 km. It becomes a yen.

The tax-exempt limit_public transportation master table 424 and the tax-exempt limit_transportation equipment master table 426 are common tables for all companies using this system, and are used to register information registered in records and Editing can only be done by the system administrator.
〔motion〕
Next, the operation of this embodiment will be explained.
[Employee information registration process]
First, the operation of the transportation expense calculation server 100 when an employee with personnel authority registers employee information will be described.

FIG. 6 is a flowchart showing the employee information registration process.
The CPU 30 is composed of an MPU (Micro-Processing Unit), etc., starts a predetermined program stored in a predetermined area of the ROM 32, and executes the employee information registration process shown in the flowchart of FIG. 6 according to the program.
When the employee information registration process is executed by the CPU 30, the process first moves to step S100, as shown in FIG.
In step S100, it is determined whether or not a new registration request for employee information has been received from the employee terminal 200. If it is determined that the new registration request for employee information has been received (YES), the process moves to step S102, and if it is determined that it has not been received (NO). ) ends the series of processing and returns to the original processing.

FIG. 7 is a diagram showing an employee information list screen 500.
Here, when you log in to the transportation 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 via the employee terminal 200 (by pressing it with a mouse or touching it with a finger, etc.), the employee information shown in FIG. 7 is displayed on the display device. A list screen 500 is displayed. Subsequently, by selecting the registration button 50 in the lower right corner of the employee information list screen 500, a new registration request for employee information is sent to the transportation expense calculation server 100.

If the process moves to step S102, employee information input processing is executed, and the process moves to step S104.
FIG. 8 is a diagram showing a new employee information registration screen 501.
Here, when the employee information input process is executed, first, employee information input screen information is transmitted to the employee terminal 200 of the human resources employee. As a result, a new employee information registration screen 501 shown in FIG. 8 is displayed on the display device of the employee terminal 200 of the human resources employee. The personnel employee enters information to be registered in the employee information master table 412 on this screen.

On the new employee information registration screen 501, the department to which the employee to be registered belongs can be selected from the drop menu 50 shown in FIG. In addition, by pressing the map button 53 at the bottom right, the station closest to the employee's home is automatically entered into the nearest station list, and by pressing the nearest station registration button 54, the nearest station can be entered. be able to. Furthermore, by pressing the registration button 55, the inputted nearest station can be confirmed.
In step S104, it is determined whether or not a registration application has been received from the employee terminal 200. If it is determined that the registration application has been received (YES), the process moves to step S106, and if it is determined that it has not been received (NO), the process proceeds to step S106. The process moves to S108.

When the input of the employee information to be registered is completed and the registration button 55 at the bottom right of the new employee information registration screen 501 shown in FIG. 8 is selected on the employee terminal 200, the registration application is sent to the transportation expense calculation server. 100.
In step S106, the contents of the input employee information are confirmed, and if it is determined that there is no omission in the required fields, the input employee information is registered in the employee information master table 412. Thereafter, the series of processing is completed and the original processing is resumed.
On the other hand, if the process moves to step S108, it is determined whether the employee information registration process has been canceled, and if it is determined that it has been canceled (YES), the series of processes is ended and the original process is returned to. If it is determined otherwise (NO), the process moves to step S104.

Here, when the back button 56 at the bottom right of the employee information new registration screen 501 shown in FIG. 8 is selected on the employee terminal 200 while inputting the employee information, a pop-up screen appears asking whether to cancel the input. (not shown) is displayed, and by selecting the OK button there, a request to cancel the registration process is sent to the transportation expense calculation server 100.
[New application process for commuting route information]
Next, the operation of the transportation expense calculation server 100 when an employee newly applies for commuting route information will be explained.

FIG. 9 is a flowchart illustrating new commuting route information application processing.
The CPU 30 starts a predetermined program stored in a predetermined area of the ROM 32, and executes a new commuting route information application process shown in the flowchart of FIG. 9 according to the program.
When the commuting route information new application process is executed by the CPU 30, as shown in FIG. 9, the process first moves to step S200.
In step S200, it is determined whether or not a new application request has been received from the employee terminal. If it is determined that the new application request has been received (YES), the process moves to step S202; if it is determined that the new application request has not been received (NO), the process proceeds to step S202. The determination process is repeated until

Here, when the employee selects the "Application" menu button from among the main menu buttons via the employee terminal 200, a drop-down list is displayed. Then, by selecting the "new application" menu from this drop-down list, a new application request is sent to the transportation expense calculation server 100.
Note that 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 a new employee moves and his/her commuting route changes.

If the process moves to step S202, application information input processing is executed, and the process moves to step S204.
FIG. 10 is a diagram showing an application information input screen 600.
Here, when the application information input process is executed, first, application information input screen information is transmitted to the employee terminal 200. As a result, the application information input screen 600 shown in FIG. 10 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. 10 or the like via the employee terminal 200. Specifically, this is a process of accepting input of information to be registered in the employee route information table 414, the employee pay information table 416, and the employee daily pro rata pay information table 418. Note that the screen illustrated in FIG. 10 is the first screen displayed, and is switched to the next input screen by selecting the next button 61 displayed at the lower right of the application information input screen 600. That is, the application information input process is performed over multiple screens.

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. As for the route direction type, specifically, as shown in the route direction type drop-down list 60 in FIG. It has become. 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.

For example, if the means of commuting is by car, and a road that can be used on the outbound trip is not possible on the return trip due to the time of day or one-way traffic, especially if the mileage varies greatly, the commuting route information can be set separately for the outbound and return trips. can do. For example, if your means of commuting is by train, you work at office A in the morning, and in the afternoon you work at another office B, which is within walking distance from office A. Commuting route information can be set separately for outbound and return trips, such as when the nearest stations are different. Moreover, when setting an outbound trip and a return trip separately, for example, a new application is made for each.

In step S204, it is determined whether or not the registration application has been received from the employee terminal 200. If it is determined that the registration application has been received (YES), the process moves to step S206; if it is determined that it has not been received (NO), the process proceeds to step S206. The process moves to S210.
If the process moves to step S206, information on the department to which the applicant belongs (department ID) is obtained from the employee information master table 412, and approval party information (department ID) corresponding to the obtained department ID is obtained from the department information table 420. The employee ID of the employee who has approval authority is acquired, and the process moves to step S208.

11(a) and (b) are diagrams for explaining the mechanism for constructing an approval route (workflow), and FIG. 12(a) shows an example of setting employee group ID, department ID, and employee authority. FIG. 12B is a diagram showing an example of an approval route.
Here, the department ID is identification information dedicated to the workflow, and can be set so that employees in different real organizations have the same department ID. For example, in the example shown in Figure 11(a), employees A to D who belong to the general affairs department, which is a real organization, and employees F to I who belong to the sales department, which is a real organization, are assigned the same department ID. A certain "B1" is set. Note that the actual organization is registered using the employee group ID in the employee information master table 412.

Further, as shown in FIGS. 11 and 12, employees A and F are employees who have superior authority, and are given approval authority in the workflow. Furthermore, employee E is a general employee and is given the authority to apply on behalf of others. Here, the approval authority is the authority to approve the application contents of an employee who belongs to the same department (for example, B1) in the workflow, and the proxy application authority is the authority that allows an employee other than the human resources department to apply on behalf of another employee. This is the authority to do so. That is, employees A and F who have approval authority can approve the applications of employees B to E and G to I of the same department B1. Further, the employee E who has proxy application authority can process applications for employees A to D and F to I of the same department B1 on their behalf.

As a result, even if the real organizations are different, if they are managed by the same department ID defined in the department information table 420, approval processing and proxy application processing can be performed across real organizations. In other words, it is now possible to construct an amoeba-like approval route.
Returning to FIG. 9, in step S208, an approval route is constructed based on the obtained approval destination information, and an application information approval request is sent to each approver of the route destination based on the constructed approval route. Finish the series of processing and return to the original processing.

For example, when a general employee who belongs to department B1 applies for a commuting route, the recipients of approval will be both employees A and F, and after approval, the person who will be inspected will be HR employee J who is in charge of department B1. ~There will be three people, L. Furthermore, the human resources employee has the authority to inspect (final check) any department.
In other words, as shown in FIG. 12(b), the approval route first becomes "employees A and F", then after employee A approves, it becomes "employee A → HR employee J~L", and after employee F approves, , "Employee F → Human Resources Employee J~L". In other words, approval can be given by either employee A or employee F, and approval by both employees is not required. Further, the inspection after approval is performed by three human resources employees J to L who are in charge of the department B1, and any one of the human resources employees J to L may perform the inspection.

In this way, when the application is approved and inspected, the application information is registered in the employee-based route information table 414, the employee-based payment information table 416, and the employee-based daily payment information table 418.
On the other hand, if the process proceeds to step S210 without receiving a registration application in step S204, it is determined whether or not a cancellation request has been received from the employee terminal 200. If it is determined that a cancellation request has been received (YES), a series of If it is determined otherwise (NO), the process proceeds to step S204.

Here, when the return button 62 at the bottom right of the application information input screen 600 shown in FIG. 10 is selected on the employee terminal 200 while inputting the application information, a pop-up screen ( (not shown) is displayed, and by selecting the OK button there, a request to cancel the input process is sent to the transportation expense calculation server 100.
[Private vehicle commuting transportation expense calculation process]
Next, the calculation process for commuting transportation expenses for privately owned vehicles will be explained.
When a car or motorcycle is selected as a means of transportation when applying for a new commuting route information, a process is executed to calculate the commuting transportation cost of a private vehicle using the commuting distance, the fuel consumption and fuel unit price of the private vehicle. This process is performed when a new application is made in the above-mentioned new commuting route information application process.

FIG. 13 is a flowchart showing a private vehicle commuting transportation cost calculation process.
The CPU 30 starts a predetermined program stored in a predetermined area of the ROM 32, and executes a private vehicle commuting transportation expense calculation process shown in the flowchart of FIG. 13 according to the program.
When the private vehicle commuting transportation expense calculation process is executed by the CPU 30, as shown in FIG. 13, the process first moves to step S300.
In step S300, a payment rule ID is obtained from the employee information master table 412 based on the applicant's company ID and employee ID, and a vehicle ID associated with the commuting method selected in the commuting method selection column 66 in FIG. 10 is obtained. do. Then, based on the acquired payment rule ID and vehicle ID, a charge type ID is acquired from the vehicle-specific payment rule master table 402, and the process moves to step S302.

In step S302, an amount calculation formula is obtained from the charge master (car) table 404 based on the charge type ID obtained in step S300, and the process proceeds to step S304.
Here, the amount calculation formula is, for example, "(commuting distance/fuel consumption) x fuel unit price." Note that each company can set an arbitrary formula for calculating the amount. For example, a calculation formula for multiplying the above calculation formula by an arbitrary coefficient (eg, 1.7, etc.) may be set.

In step S304, the one-way distance is obtained based on the address of the workplace selected in the workplace selection column 67 in FIG. 10, and the process proceeds to step S306.
FIG. 14(a) is a diagram showing a part of the application information input screen 601, and FIG. 14(b) is a diagram showing a display screen 700 of basic information registered in the private vehicle information master table 410. FIG. 14(c) is a diagram showing a display screen 701 of basic information registered in the fuel consumption master table 409.
As illustrated in a part of the application information input screen 601 in FIG. 14(a), the applicant's address registered in advance in the employee information master table 412 is displayed in the home address display field 63, and the applicant's address registered in advance in the employee information master table 412 is displayed. The display field 64 displays the address of the workplace selected in the workplace selection field 67 in Figure 10, and the commuting distance (one-way distance) is automatically calculated from these addresses. It has become. The automatically calculated commuting distance is displayed in the commuting distance display field 65 and is registered in the employee-specific route information table 414 after approval.

Returning to FIG. 13, in step S306, the fuel efficiency type ID is acquired from the private vehicle information master table 410 based on the target employee's company ID and employee ID, and the process moves to step S308.
That is, in the private vehicle information master table 410, as illustrated in the standard information display screen 700 of FIG. The fuel type ID "NGP1004" displayed in the fuel type ID display column 70 is registered.

Returning to FIG. 13, in step S308, the fuel efficiency of the applicant's private vehicle is obtained from the fuel efficiency master table 409 based on the applicant's company ID and the fuel efficiency type ID of the private vehicle, and the process proceeds to step S310.
That is, in the fuel efficiency master table 409, as illustrated in the standard information display screen 701 of FIG. The fuel efficiency "9.5 km/L" displayed in 72 is registered.

Returning to FIG. 13, in step S310, the fuel unit price category is acquired from the private vehicle information master table 410 based on the applicant's company ID and employee ID, and the process moves to step S312.
That is, in the private vehicle information master table 410, as illustrated in the standard information display screen 700 of FIG. The fuel unit price category “2: Gasoline” displayed in the fuel unit price category display column 71 is registered.

Returning to FIG. 13, in step S312, the fuel unit price type ID is determined from the workplace master table 406 based on the applicant's company ID and the workplace ID of the workplace selected in the workplace selection field 67 of FIG. is acquired, and the process moves to step S314.
In step S314, the fuel unit price is obtained from the fuel unit price master table 408 based on the applicant's company ID, the fuel unit price type ID of the applicant's workplace, and the fuel unit price classification of the applicant's private vehicle, and step S316 to move to.

FIG. 15 is a diagram showing a display screen 702 of reference information and fuel cost information registered in the fuel unit price master table 408.
That is, as illustrated in the display screen 702 of FIG. 15, the applicant's company ID "KN10000", the fuel unit price type ID of the applicant's workplace "GAS1001", and the fuel unit price category of the applicant's private vehicle "2: Gasoline". ”, the fuel unit price “122 yen” displayed in the fuel unit price display column 73 is registered.
Returning to FIG. 13, in step S316, the payment amount category (one-way/round trip) and the number of business days are acquired from the rate master (car) table 406 based on the rate type ID acquired in step S300, and the process proceeds to step S318. Transition.

In step S318, one of the applicant's private vehicles is Calculate monthly commuting expenses (one way/round trip). Thereafter, the series of processing is completed and the original processing is resumed.
In other words, the commuting transportation cost (monthly) for a privately owned vehicle is calculated as follows: "Commuting transportation cost (monthly) = (commuting distance (one way) / fuel consumption) x fuel unit price x payment amount category x number of business days."

For example, if the commuting distance is 17 km, the fuel consumption is 9.5 km/L, the fuel unit price is 122 yen, the payment amount is 2 round trips, and the number of business days in a month is 20 days. , commuting transportation expenses (monthly) are as follows.
Commuting transportation expenses (monthly) = (17/9.5) x 122 x 2 x 20 = 8,732 yen [Payment information addition/correction process]
Next, a description will be given of the operation when a human resources employee adds or corrects the payment information registered in the employee-specific payment information table 416 and the employee-specific daily prorated payment information table 418.

FIG. 16 is a flowchart showing the payment information addition/correction process. Further, FIG. 17 is a diagram showing a selected employee's route list screen 800, FIG. 18 is a diagram showing a payment information list screen 801, and FIG. 19 is a diagram showing a daily payment information setting screen 802. . Further, FIG. 20 is an enlarged view of the screen portion for setting the usage direction type of the daily payment information setting screen 802. Further, FIG. 21 is a diagram showing a daily pro rata payment date setting screen when individual is selected as the usage direction type.

Payment information addition/correction processing is performed on the route list screen 800 (see FIG. 17) that is displayed after selecting the employee to be added or modified on the employee information list screen 500 (see FIG. 7) and selecting the route list button 51. This is the process executed in (Reference).
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. 16 according to the program.
When the payment information addition/correction process is executed by the CPU 30, as shown in FIG. 16, the process first moves to step S400.

In step S400, based on the information from the employee terminal 200, the route modification button 80 (see FIG. 17) is selected for the commuting route selected from the selected employee's commuting route list displayed on the route list screen 800. Determine whether or not. If it is determined that the payment information list screen 801 (see FIG. 18) has been selected, the screen information of the payment information list screen 801 (see FIG. 18) is sent to the employee terminal 200, and the process moves to step S402; ) repeats the determination process until it is selected.

That is, when the route modification button 80 is selected on the route list screen 800 shown in FIG. 17, the payment information list screen 801 shown in FIG. 18 is displayed on the display device of the employee terminal 200.
Returning to FIG. 16, if the process moves to step S402, 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), the screen information of the payment information setting screen is sent to the employee terminal 200 and the process moves to step S404; if it is determined that it has not been selected (NO), the process moves to step S406. do.

That is, when the correction button 83 is selected with daily pro-rata payment information selected on the payment information list screen 801 shown in FIG. 18, the pro-rata payment information shown in FIG. 19 is displayed on the display screen of the employee terminal 200. A settings screen 802 is displayed. Note that if the modify button 83 is selected with periodic payment information selected, a screen that allows additional settings for periodic payment information that is different from the daily payment information setting screen 802 will be displayed, and if nothing is selected, If the add button 82 is selected in a state where no payment information is available, a screen will be displayed that allows additional settings for both regular and daily payment information, but will not be described here.

Returning to FIG. 16, if the process moves to step S404, the payment information addition process is executed, the series of processes ends, and the process returns to the original process.
Here, as payment information addition processing, a process will be described in which payment information is added based on information input by the human resources employee on the daily prorated payment information setting screen 802 shown in FIG. 19.
The human resources employee inputs necessary information on the daily payment information setting screen 802 via the employee terminal 200. Specifically, input the pro-rata payment period, the number of payment days, and the direction of use (one-way/round trip). Pro-rated payment information is set, for example, if you start work halfway through the month and start work in the middle of the month, commuting transportation expenses will be paid on a daily basis only on the working days of that month. It is information. Alternatively, this information is set when, for example, it is necessary to work from home due to the spread of an infectious disease and the employee only goes to work two days a week, and commuting transportation expenses are paid on a daily basis only on the working days. Therefore, the period eligible for daily pro rata payment is set as the period eligible for pro rata payment.

In addition, as illustrated in FIG. 19, the drop-down list 87 shown in FIG. Select it and enter it in the input field 84. Here, as the usage direction type, if the outbound and return trips are the same commuting route, select round trip, and if the outbound and return trips are different commuting routes or if only one way is used, select one way. As a result, a round trip or one-way trip is commonly set for each date in the payment period. Also, if there are days when you use the same commuting route only one way and days when you use it round trip, you can set it individually for each date after selecting either one way or round trip.

In addition, as illustrated in FIG. 19, by inputting the period for which the daily pro-rata payment is applicable, the pro-rata payment period "January 18, 2022 to January 31, 2022" is entered in the daily pro-rata payment details input field 85. A list of fees for each date and direction of use "round trip" is displayed. A checkbox is displayed to the left of each date, and by checking the checkbox and selecting the day of work from among the displayed dates, the employee can input (set) the payable date.
In addition, after inputting the daily pro-rata payment information, if the OK button 86 at the bottom right of the daily pro-rata payment information setting screen 802 shown in FIG. The screen returns to the payment information list screen 801 shown in FIG. Then, the newly input pro-rata pay information is added to the list on the pay information list screen 801, and by selecting the confirmation button at the bottom right, the new pro-rata pay information is added to the list of per-employee per-daily pay information. It is added to the information table 418.

Also, if you want to set the usage direction type individually for each date, press the drop button to the right of the fare displayed for each date in the daily payment details input field 85, as shown in Figure 21. By selecting one-way or round trip in the drop box 89 displayed, the direction of use type can be set for each date. In the example shown in Figure 21, except for one one-way option, all round-trip options are selected, and selecting one-way will display the one-way fare, and selecting round-trip will display the round-trip fare. Ru.

On the other hand, if the process moves to step S406 without selecting the add button 81 in step S402, 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 is sent to the employee terminal 200 and the process moves to step S408; if it is determined that it has not been selected (NO), the process moves to step S410. do.

That is, if the correction button 83 is selected on the payment information list screen 801 shown in FIG. 18 with already registered daily payment information selected, the screen shown in FIG. The daily payment information setting screen 802 shown in FIG. 8 is displayed with information already entered.
If the process moves to step S408, the payment information correction process is executed, the series of processes ends, and the process returns to the original process.
Here, the payment information modification process is a process for modifying the information that has already been input on the daily payment information setting screen 802, and compared to the payment information addition process, it is different from the process of adding new information or changing the information that has already been input. The process is the same, the only difference being whether it is changed (corrected), so the explanation will be omitted.

Further, in step S406, if the correction button 83 is not selected and the process moves to step S410, it is determined whether or not any 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 S412; if it is determined that this has not been selected (NO). ) moves to step S402.
If the process moves to step S412, 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.
[Prorated daily payment amount calculation process]
Next, a description will be given of the operation of the calculation process of the daily pro-rata payment amount when the human resources employee adds or corrects the pro-rata payment amount. This process is the process performed in steps S404 and S408 above.

FIG. 22 is a flowchart showing the pro-rata payment amount calculation process.
When the daily payment amount calculation process is executed in step S404 or S408, the process first moves to step S500, as shown in FIG. 22.
In step S500, it is determined whether the re-search button 88 has been selected based on the information from the employee terminal 200, and if it is determined that it has been selected (YES), the process moves to step S502, and if it is determined that it has not been selected. In the case (NO), the determination process is repeated until the selection is made.

If the process moves to step S502, the number of dates with checked checkboxes for each one-way trip and each round trip is counted, and the process moves to step S504.
FIG. 23 is a diagram showing a screen after calculating the daily payment amount when round trip is selected as the usage direction type. In the example shown in FIG. 23, since 10 checkboxes are checked, the number of days of payment is 10 days.
In step S504, the round-trip fare (one-way fare x 2) is multiplied by the number of round-trip paid days counted in step S502, the one-way fare is multiplied by the one-way paid days counted in step S502, and these multiplication results are added. This will calculate the daily payment amount. After that, the process moves to step S506.

In the example shown in Figure 21, the round trip fare is set to "1,036 yen" and the one-way fare is set to "518 yen", so the daily rate is "1,036 x 10 + 518 x 0 = 10,360 yen". It is calculated as the payment amount.
On the other hand, in the example of FIG. 21, the checkbox for the date corresponding to the round trip and the checkbox corresponding to the one-way trip are checked, so the daily payment amount is 1,036 x 1 + 518 x 1 = 1, It will be 554 yen.
In step S506, the daily pro-rata payment amount calculated in step S504 is displayed in the payment amount display field 850 of the daily pro-rata payment details input field 85, and the series of processes is ended and the process returns to the original process.

In the example shown in FIG. 21, "10,360 yen" is displayed in the display field 850 as the daily payment amount, and in the example shown in FIG. 21, "1,554 yen" is displayed in the display field 850 as the daily payment amount. be done.
[Batch processing schedule execution process]
Next, the operation of the batch process execution process based on the batch process schedule set by the human resources employee will be explained.
FIG. 24 is a flowchart showing schedule execution processing for batch processing.
The batch process schedule execution process is a process for executing the batch process scheduled by the human resources employee. Here, batch processing includes, for example, batch processing in which fare revisions are reflected in each corresponding table at once, and batch processing in which creation of salary linkage data that links commuting transportation expenses with salary is carried out in a batch. .

The CPU 30 starts a predetermined program stored in a predetermined area of the ROM 32, and executes the batch processing schedule execution process shown in the flowchart of FIG. 24 according to the program.
When the batch processing schedule execution process is executed by the CPU 30, as shown in FIG. 24, the process first moves to step S600.
In step S600, it is determined whether or not a schedule for batch processing has been set. If it is determined that it has been set (YES), the process moves to step S602; if it is determined that it is not (NO), the schedule is set. The determination process is repeated until the value is set.

FIG. 25 is a diagram showing a batch processing setting screen 900.
As shown in FIG. 25, the batch processing setting screen 900 includes a service ID input field 90 in which a service ID for batch processing is input, and schedule information for batch processing corresponding to the service ID input in the service ID input field 90. It includes a schedule input field 91, a registration button 92, and a list information display field 93 that displays list information of registered batch processes.
The human resources employee inputs the company ID on the batch process setting screen 900 displayed on the display device of the employee terminal 200, and also inputs the service ID of the batch process to be executed in the service ID input field 90. Thereafter, the batch processing schedule corresponding to this service ID is input into the schedule input field 91. Specifically, information on the batch startup date classification (specific day/specific day of the week/specific year/month/day), startup date/starting day of the week/starting date, and startup time is input.

After the input of the schedule is completed, by selecting the registration button 92, the information of this batch processing is displayed in the list information display field 93 and is transmitted to the transportation cost calculation server 100. When the transportation expense calculation server 100 acquires (receives) information on batch processing from the employee terminal 200, it determines that a schedule for batch processing has been set.
If the process moves to step S602, information on the execution time (startup date/startup day of the week/startup date and start time) is acquired from the acquired batch processing information, and the current time ( (Year, Month, Sunday and Time) information is acquired, and the process moves to step S604.

In step S604, the execution time obtained in step S602 and the current time are compared to determine whether the execution time has arrived. If it is determined that the execution time has arrived (YES), the process moves to step S606, If it is determined otherwise (NO), the process moves to step S602.
If the process moves to step S606, batch processing is executed and the process moves to step S608.
In step S608, it is determined whether or not the batch processing has been completed. If it is determined that the batch processing has been completed (YES), the series of processing is finished and the original processing is resumed; if it is determined that the batch processing is not completed (NO) repeats the determination process until the batch process is completed.

[Effects of embodiment]
Next, the effects of this embodiment will be explained.
In this embodiment, when inputting application information related to commuting route information including a commuting route, by selecting either the outbound route or the inbound route in the route direction type drop-down list 60 on the application information input screen 600. , it is now possible to apply for outbound and return commuting routes separately.
With this kind of configuration, for example, if you only use one of the outbound and return trips, or if the commuting routes are different for the outbound and return trips, you can easily apply for separate applications, and you can also apply for the outbound and return trips separately. Commuting transportation expenses can be calculated easily and individually.

Furthermore, in this embodiment, when inputting the daily pro-rata payment information when commuting transportation expenses are paid on a daily basis, after setting the usage direction type and the period for which the pro-rata payment is to be made, the pro-rata payment details input field 85 For each date corresponding to the pro-rata payment period displayed in , you can enter the payment date by checking the checkbox displayed to the left of each date.
With such a configuration, it is possible to easily set the payment target date, and it is also possible to easily calculate commuting transportation expenses on the payment target day.

Furthermore, in this embodiment, when inputting daily pro-rata payment information when commuting transportation expenses are paid on a daily basis, in the daily pro-rata payment details input field 85, "one-way/round trip" is selected for each date for which payment is to be made. It is now possible to input (set) the direction type individually.
With this configuration, if there is a mix of one-way use and round-trip use on each payment day, it is easy to set appropriate information (direction type, fare, etc.) for each payment day. You can easily calculate commuting expenses.

Furthermore, in this embodiment, the commuting cost for using a private car is calculated using fuel efficiency and fuel unit price set for each type of employee's private car.
With such a configuration, it is possible to calculate appropriate commuting expenses for each private vehicle.
Furthermore, in this embodiment, the approval destination corresponding to the department to which the employee corresponding to the application information belongs is obtained from the department information table 420 in which the approval destination (supervisor with approval authority) is registered for each department dedicated to workflow. Then, an approval request for registration of application information is sent to each approver using the approval route established by the obtained approval party.

With this kind of configuration, even if the real organizations (employee group IDs) to which they belong are different, if the employees belong to departments with the same department ID, approval processing can be performed across real organizations. Therefore, it is possible to perform approval processing for registration of application information using a flexible approval route for each applicant.
Furthermore, in this embodiment, it is possible to register an employee who has proxy applicant authority for each department dedicated to workflow, and to apply on behalf of other employees who belong to the same department for commuting routes. I made it.

With this configuration, even if the real organizations (employee group IDs) to which they belong are different, if the employees belong to the same department with the same department ID, proxy application processing can be performed across real organizations. I can do it.
Furthermore, in this embodiment, the content of batch processing to be executed from among the service IDs corresponding to batch processing related to fare revision or batch processing related to salary coordination of commuting transportation expenses registered in batch processing master table 422 is supported. It is now possible to select a service ID and set an execution schedule for the batch process corresponding to the selected service ID.

With such a configuration, batch processing related to fare revision or batch processing related to salary coordination of commuting expenses can be easily executed according to a desired schedule. As a result, batch processing can be executed during times when the processing load is light, such as on holidays or in the middle of the night.
Furthermore, in this embodiment, the tax-exempt limit_public transportation master table 424 in which the tax-exempt limit of commuting expenses using public transportation is registered, and the tax-exempt amount of commuting expenses using transportation equipment such as a car Regarding the tax-exempt limit amount_transportation equipment master table 426 in which the limit amount is registered, one table is provided in common for all companies using this system. Only the administrator of this system can register and edit information on these tables. With such a configuration, for example, it is possible to reduce the processing load on employees in the human resources department of each company, and to prevent erroneous registration of wrong information.

[Correspondence]
In this embodiment, the commuting route corresponds to the travel routes of Inventions 1, 2, 4, 5, 8, and 9, the route direction type corresponds to the round trip type of Invention 1, and the usage direction type corresponds to Invention 2. , 3, 8, and 9, the storage device 42 stores transportation expense information storage means for inventions 1, 4, 7, and 8, approval destination information storage means for invention 5, and legal-related transportation expenses for invention 7. Compatible with information storage means.
Further, in this embodiment, step S202 corresponds to the travel route information acquisition means of inventions 1 and 4, and steps S318 and S504 correspond to the transportation cost calculation means of inventions 1 to 4, 8, and 9. .

Further, step S206 corresponds to the approval destination information acquisition means of invention 5, step S208 corresponds to the approval processing request transmission means of invention 5, step S600 corresponds to the batch processing information acquisition means of invention 6, Step S602 corresponds to the schedule information acquisition means of the sixth invention, and steps S604 to S606 correspond to the batch processing execution means of the sixth invention.
[Modified example]
In addition, in the above embodiment, when the commuting route is different for the outbound route and the return route, the application is made separately for the outbound route and the return route, but the application is not limited to this configuration. A configuration may also be adopted in which a route and a return commuting route can be requested.

Further, in the above embodiment and its modifications, the present system is applied to the application for a commuting route and the calculation of commuting transportation expenses, but the present invention is not limited to this configuration. For example, the present system may be applied to apply for transportation expenses (actual expenses) required for traveling to a business trip destination and calculate comprehensive transportation expenses including this transportation expense.
Furthermore, in the above embodiment and its modifications, a common department ID (B1) dedicated to workflow is set for employees who belong to two different actual organizations (general affairs department, sales department). However, the configuration is not limited to this. For example, a configuration may be adopted in which a common department ID is set for employees who belong to three or more real organizations.

Furthermore, in the above embodiment and its variations, the configuration is such that approval authority is granted to two employees with superior authority who belong to two different actual organizations (general affairs department and sales department). The present invention is not limited to this configuration, and the configuration may be such that approval authority is granted to three or more employees who have superior authority.
Further, in the above embodiment and its modifications, various table data are stored in the storage device 42 of the transportation expense calculation server 100, but the structure is not limited to this, and a separate database server may be communicably connected. , a configuration may be adopted in which various table data are stored in the storage device of the database server.

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 modifications thereof, when executing the processes shown in the flowcharts of FIGS. 6, 9, 13, 16, 22, and 24, programs stored in the ROM 32 Although the case where these steps are executed has been described, the present invention is not limited to this, and a program showing these procedures may be read into the RAM 34 from a storage medium in which the program is stored and executed.

100...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…Vehicle-specific payment rule master table, 404…Charge master (car) table, 406…Work place master table, 408…Fuel unit price master table, 409…Fuel efficiency master table, 410…Private ownership Vehicle information master table, 412... Employee information master table, 414... Route information table by employee, 416... Payment information table by employee, 418... Daily payment information table by employee, 420... Department information table, 422... Batch processing master table , 424...Tax exemption limit_Public transportation master table, 426...Tax exemption limit_Transportation equipment master table

Claims (9)

a travel route information acquisition means for acquiring travel route information including a travel route that a person eligible for payment can use to travel to his or her place of work and a round trip type indicating an outbound or return route of the travel route that the person eligible for payment applies for use; ,
Based on the transportation cost information of the transportation cost information storage means that stores transportation cost information regarding the transportation cost required for traveling to the place of work on the travel route and the travel route information acquired by the travel route information acquisition means, the travel route is determined. A transportation expense calculation system, comprising: a transportation expense calculation means for calculating the transportation expense when traveling to the place of work on the travel route for the outbound or return trip for which the recipient applies. In claim 1,
The transportation cost information includes first transportation cost information regarding transportation costs for use over a period of multiple days and second transportation cost information regarding transportation costs for one day of use,
Applicable date acquisition means for acquiring information on an applicable date to which the second transportation expense information is applied;
a usage direction type information acquisition means for acquiring usage direction type information indicating which of the one-way or round trip travel route to which the second transportation expense information is applied is used by the payment recipient;
The transportation cost calculation means calculates the traffic on the applicable day based on the second transportation cost information, the information on the applicable date acquired by the applicable date acquisition means, and the information on the usage direction type acquired by the usage direction type information acquisition means. A transportation expense calculation system characterized by calculating expenses. In claim 2,
The usage direction type information acquisition means acquires information on the usage direction type for each of a plurality of application days to which the second transportation fee information is applied;
The transportation cost calculation means calculates the applicable amount based on the second transportation cost information, the information on the applicable date acquired by the applicable date acquisition means, and the information on the usage direction type for each applicable date acquired by the usage direction type information acquisition means. A transportation expense calculation system characterized by calculating transportation expenses for multiple application days. In any one of claims 1 to 3,
The travel route information acquisition means further acquires travel distance information regarding the distance of a travel route that the benefit recipient can use to travel to his or her place of work;
The transportation cost information storage means stores, as the transportation cost information, information on fuel consumption and fuel costs per predetermined amount of fuel for a vehicle used by the recipient to travel to his/her place of work. remember,
When calculating the transportation cost for traveling to the place of work using a vehicle, the transportation cost calculation means calculates the transportation cost based on the fuel consumption and fuel cost of the vehicle and the travel distance information acquired by the travel route information acquisition means. A transportation expense calculation system characterized by calculating transportation expenses. In any one of claims 1 to 4,
The travel route or a group identification information acquisition means for acquiring group identification information corresponding to the target person identification information of the recipient who has applied for transportation expenses;
The group acquired by the group identification information acquisition means from an approval destination information storage means that stores information on a plurality of approval destinations for the application, including an approval destination common to a plurality of existing departments, in association with the group identification information. Approval party information acquisition means for acquiring approval party information corresponding to the identification information;
A transportation expense calculation system comprising: an approval processing request transmitting means for transmitting an approval processing request to each approval destination based on the information on the approval destination acquired by the approval destination information acquisition means. In any one of claims 1 to 5,
Batch processing information acquisition means for acquiring information on the batch processing to be executed among the batch processing related to fare revisions or the batch processing related to salary coordination of transportation expenses;
schedule information acquisition means for acquiring batch processing execution schedule information corresponding to the information acquired by the batch processing information acquisition means;
A transportation expense calculation system comprising: collective processing execution means for executing collective processing corresponding to the information acquired by the collective processing information acquisition means, based on the execution schedule information acquired by the schedule information acquisition means. In any one of claims 1 to 6,
A transportation expense calculation system characterized in that all companies using the transportation expense calculation system have a legal transportation expense information storage means for registering information related to transportation expenses stipulated by law. Stores first transportation expense information related to transportation expenses related to use over a period of multiple days required for travel routes that can be used by recipients to travel to their workplaces, and second transportation expense information related to transportation expenses related to one day use. application date acquisition means for acquiring information on the application date to which the second transportation expense information of the transportation expense information storage means is applied;
Usage direction type information acquisition means for acquiring usage direction type information indicating the one-way or round trip of the travel route to which the second transportation expense information is applied, which is used by the person to be paid;
Transportation expense calculation that calculates the transportation expense for the applicable day based on the second transportation expense information, the information on the applicable date acquired by the applicable date acquisition means, and the information on the usage direction type acquired by the usage direction type information acquisition means. A transportation expense calculation system characterized by comprising a means. Stores first transportation expense information related to transportation expenses related to use over a period of multiple days required for travel routes that can be used by recipients to travel to their workplaces, and second transportation expense information related to transportation expenses related to one day use. application date acquisition means for acquiring information on the application date to which the second transportation expense information of the transportation expense information storage means is applied;
Usage direction type information acquisition means for acquiring usage direction type information indicating which of the one-way or round trip travel route the recipient will use for each of the plurality of application dates to which the second transportation expense information is applied; ,
Transportation costs for the plurality of applicable days based on the second transportation cost information, the information on the applicable date acquired by the applicable date acquisition means, and the information on the usage direction type for each applicable date acquired by the usage direction type information acquisition means. A transportation expense calculation system comprising: transportation expense calculation means for calculating.

Images