JP7580099B1 - Payment calculation system - Google Patents

Abstract

[Problem] To provide a payment calculation system suitable for reducing the effort required to register nearest station information. [Solution] In a payment calculation system consisting of the Internet 199, a commuter travel expense calculation server 100 acquires the home addresses of employees from an employee information master table, acquires nearest station information from a station information search server based on the acquired home addresses of employees, and performs batch processing for multiple employees at once to set the acquired nearest station information for the employee information targeted by the employee information master table. It also acquires route information related to the commute route used by employees to travel between the nearest station to their home and their workplace. A batch server 150 calculates the payment amount when an employee uses a commuter route based on the route information acquired by the commuter travel expense calculation server 100 and the fare information in the fare information table. [Selected Figure] Figure 1

Description

The present invention relates to a system that assists in the calculation of payment amounts for payment recipients, and in particular to a payment calculation system that is suitable for reducing the effort required to register nearest station information.

Conventionally, the technology described in Patent Document 1, for example, is known as a technology for calculating commuting allowances and linking them to wages when changes occur due to new commuting expenses, route changes, terminations, etc.

The technology described in Patent Document 1 works in conjunction with a payroll system to calculate the amount of commuting allowances in salary when a request for commuting allowances is made, a route is changed, or the allowance is terminated. It creates definitions regarding the company's commuting allowance payment standards and calculation methods, and when application data for commuting allowances is input, it converts the application data into commuting allowance data based on the commuting allowance definition, and performs an update process to recalculate the commuting allowance data when the amount of commuting allowances in salary is to be settled.

The technology described in Patent Document 2 transmits location information obtained from the mobile phone's GPS (Global Positioning System) to a route search server, which then searches a route database for the nearest station based on the received location information (Patent Document [0018]).

JP 2016-192201 A JP 2001-318932 A

In the technology described in Patent Document 1, when an employee registers a route to be used when traveling between the nearest station to his/her home and the nearest station to his/her workplace, it is possible to apply the technology described in Patent Document 2, for example, and register the nearest station to his/her home by obtaining it from a route search server.

However, when this type of configuration is adopted, although the amount of work required for each employee is reduced compared to manual input, there is a problem in that the overall amount of work increases when there are a large number of employees.

Therefore, the present invention was made with a focus on the unresolved issues of such conventional technology, and aims to provide a payment calculation system that is suitable for reducing the effort required to register nearest station information.

[Invention 1] In order to achieve the above object, the payment calculation system of invention 1 includes a station information setting means for setting nearest station information of the home of the payment recipient for the target information based on the target information in a target information storage means that stores target information including the home address information of the payment recipient, and a payment amount calculation means for calculating the payment amount of transportation expenses when the payment recipient uses the route based on route information in a route information storage means that stores route information related to the route used by the payment recipient to travel between the nearest station to the home and the workplace, and fare information in a fare information storage means that stores fare information related to the fare for the route, and the station information setting means acquires the home address information of the payment recipient from the target information storage means, acquires nearest station information from the acquired address information, and performs the process of setting the acquired nearest station information for the target information in the target information storage means collectively for multiple payment recipients.

In such a configuration, the station information setting means performs batch processing for multiple grant recipients. In this batch processing, home address information of the grant recipients is obtained from the grant recipient information storage means, nearest station information is obtained from the obtained address information, and the obtained nearest station information is set for that grant recipient information in the grant recipient information storage means. In addition, the payment amount calculation means calculates the payment amount of transportation expenses when the grant recipient uses the route, based on the route information in the route information storage means and the fare information in the fare information storage means.

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

[Invention 2] Furthermore, the payment calculation system of invention 2 is the payment calculation system of invention 1, and further comprises a subject information acquisition means for acquiring subject information from a file in which subject information including home address information of the payment recipient is registered, and a subject information registration means for registering the subject information acquired by the subject information acquisition means in the subject information storage means, and the station information setting means acquires nearest station information from the address information included in the subject information acquired by the subject information acquisition means, and performs processing for setting the acquired nearest station information to the subject information in the subject information storage means after registration by the subject information registration means is completed.

In this configuration, the station information setting means performs processing after the registration by the subject information registration means is completed. In this processing, the nearest station information is obtained from the address information included in the subject information obtained by the subject information obtaining means, and the obtained nearest station information is set for that subject information in the subject information storage means.

The address information included in the subject information acquired by the subject information acquisition means includes, for example, the subject information acquired by the subject information acquisition means, or the subject information acquired by the subject information acquisition means and registered in the subject information storage means. That is, the station information setting means may use the subject information acquired by the subject information acquisition means to acquire the nearest station information, or may use the subject information in the subject information storage means to acquire the nearest station information. The same applies below in the payment calculation system of invention 3.

[Invention 3] Furthermore, the payment calculation system of invention 3 includes a subject information acquisition means for acquiring subject information from a file in which subject information including home address information of the payment recipient is registered, a subject information registration means for registering the subject information acquired by the subject information acquisition means in a subject information storage means, a station information setting means for setting the nearest station information of the home of the payment recipient for the subject information based on the subject information of the subject information storage means, and a payment amount calculation means for calculating the payment amount of transportation expenses when the payment recipient uses the route based on route information in a route information storage means that stores route information related to the route used by the payment recipient to travel between the nearest station to the home and the workplace, and fare information in a fare information storage means that stores fare information related to the fare for the route, and the station information setting means acquires nearest station information from the address information included in the subject information acquired by the subject information acquisition means, and performs a process of setting the acquired nearest station information for the subject information in the subject information storage means after the registration by the subject information registration means is completed.

In this configuration, the station information setting means performs processing after registration by the target person information registration means is completed. In this processing, the nearest station information is obtained from the address information included in the target person information obtained by the target person information obtaining means, and the obtained nearest station information is set for that target person information in the target person information storage means. In addition, the payment amount calculation means calculates the payment amount of transportation expenses when the target person uses the route, based on the route information in the route information storage means and the fare information in the fare information storage means.

[Invention 4] Furthermore, the payment calculation system of invention 4 includes a station information setting means for setting the nearest station information of the payee's workplace for the workplace information based on workplace information in a workplace information storage means that stores workplace information including address information of the payee's workplace, and a payment amount calculation means for calculating the payment amount of transportation expenses when the payee uses the route based on route information in a route information storage means that stores route information related to the route used by the payee to travel between the home and the nearest station of the workplace and fare information in a fare information storage means that stores fare information related to the fare for the route, and the station information setting means acquires address information of the payee's workplace from the workplace information storage means, acquires nearest station information from the acquired address information, and performs the process of setting the acquired nearest station information for the workplace information in the workplace information storage means, for a plurality of the workplaces, all at once.

In this configuration, the station information setting means processes multiple grant recipients collectively. In this batch processing, address information of the grant recipient's workplace is obtained from the workplace information storage means, nearest station information is obtained from the obtained address information, and the obtained nearest station information is set for that workplace information in the workplace information storage means. In addition, the payment amount calculation means calculates the payment amount of transportation expenses when the grant recipient uses the route, based on the route information in the route information storage means and the fare information in the fare information storage means.

[Invention 5] The payment calculation system of invention 5 further comprises, in the payment calculation system of invention 4, an employment information acquisition means for acquiring the employment information from a file in which employment information including address information of the employment of the payment recipient is registered, and an employment information registration means for registering the employment information acquired by the employment information acquisition means in the employment information storage means, and the station information setting means acquires nearest station information from the address information included in the employment information acquired by the employment information acquisition means, and performs a process of setting the acquired nearest station information to the employment information in the employment information storage means after the registration by the employment information registration means is completed.

In this configuration, the station information setting means performs processing after the work place information registration means has completed registration. In this processing, the nearest station information is obtained from the address information included in the work place information obtained by the work place information obtaining means, and the obtained nearest station information is set for that work place information in the work place information storage means.

The address information included in the workplace information acquired by the workplace information acquisition means includes, for example, the workplace information acquired by the workplace information acquisition means, or the workplace information acquired by the workplace information acquisition means and registered in the workplace information storage means. In other words, the station information setting means may use the workplace information acquired by the workplace information acquisition means to acquire the nearest station information, or may use the workplace information in the workplace information storage means to acquire the nearest station information. The same applies below in the payment calculation system of invention 6.

[Invention 6] The payment calculation system of invention 6 further comprises: a workplace information acquisition means for acquiring workplace information including address information of the workplace of the payee from a file in which the workplace information acquired by the workplace information acquisition means is registered; a workplace information registration means for registering the workplace information acquired by the workplace information acquisition means in a workplace information storage means; a station information setting means for setting the nearest station information of the workplace of the payee for the workplace information based on the workplace information in the workplace information storage means; and a payment amount calculation means for calculating the payment amount of the transportation expenses when the payee uses the route based on route information in a route information storage means for storing route information related to the route used by the payee to travel between the home and the nearest station of the workplace and fare information in a fare information storage means for storing fare information related to the route, and the station information setting means acquires nearest station information from the address information included in the workplace information acquired by the workplace information acquisition means, and performs a process of setting the acquired nearest station information for the workplace information in the workplace information storage means after the registration by the workplace information registration means is completed.

In this configuration, the station information setting means performs processing after the workplace information registration means has completed registration. In this processing, the nearest station information is obtained from the address information included in the workplace information obtained by the workplace information obtaining means, and the obtained nearest station information is set for that workplace information in the workplace information storage means. In addition, the payment amount calculation means calculates the payment amount of transportation expenses when the payment recipient uses the route, based on the route information in the route information storage means and the fare information in the fare information storage means.

As described above, according to the payment calculation system of Invention 1, the process of setting the nearest station for multiple payment recipients is performed in one go, which reduces the effort required to register the nearest station information for the recipients' homes compared to the conventional method.

Furthermore, according to the payment calculation system of inventions 2 or 3, the target person information in the file is registered in the target person information registration means, while the nearest station information is obtained and set by processing after the registration is completed, so that the target person information can be used quickly.

Furthermore, according to the payment calculation system of Invention 4, the process of setting the nearest station for multiple payment recipients is performed in one go, which reduces the effort required to register the nearest station information for the payment recipients' workplaces compared to the conventional method.

Furthermore, according to the payment calculation system of inventions 5 and 6, the workplace information in the file is registered in the workplace information registration means, while the nearest station information is obtained and set by processing after the registration is completed, thereby realizing early use of the workplace information.

1 is a block diagram showing a configuration of a network system according to an embodiment of the present invention; FIG. 2 is a diagram illustrating a hardware configuration of the commute expense calculation server 100. 4A and 4B are diagrams showing the data structures of a company master table 400, a workplace master table 402, an employee information master table 404, an employee-specific route information table 406, and an employee-specific payment information table 408. 4A and 4B are diagrams showing the data structures of an employee daily rate pay information table 410, a department information table 412, a system environment information table 414, a batch job definition information table 416, and a task scheduler information table 418. 4 is a diagram showing the data structure of a fare information table 420. FIG. 13 is a flowchart showing an employee information registration process. FIG. 5 shows an employee information list screen 500. FIG. 5 shows an employee information new registration screen 501. FIG. 5 shows an import screen 502. 13 is a flowchart showing a nearest station information acquisition process. 1 is a flowchart showing batch processing. 13 is a flowchart showing a new commute route information application process. FIG. 5 shows a commute route application screen 510. FIG. 5 shows a commute route application screen 520. 13 is a flowchart showing a payment information addition/modification process. FIG. 8 shows a route list screen 800. FIG. 8 shows a payment information list screen 801. 13 is a flowchart showing a salary linkage basic data creation task registration process. FIG. 13 is a diagram illustrating an example in which the amount of commuting expenses paid fluctuates. 13 is a flowchart showing the execution process of the payroll linkage batch processing program. 13 is a diagram showing a flow of execution processing of a batch processing main program by a task scheduler in the batch server 150. FIG. This is a time chart showing the calculation of payment information related to fare revisions and daily payment information.

The following describes an embodiment of the present invention. Figures 1 to 22 show this embodiment.

In this embodiment, the term "employee" refers to a full-time employee, a part-time employee, or any other employee.
〔composition〕
First, the configuration of this embodiment will be described.

FIG. 1 is a block diagram showing a configuration of a network system according to the present embodiment.
As shown in FIG. 1, the Internet 199 is connected to a commuter travel expense calculation server 100 that provides a service that assists in the calculation of commuter travel expenses and the calculation of the amount of commuter travel expense payment (hereinafter referred to as the "transportation expense/salary linkage support service"), a batch server 150 that executes update processing of various basic data for calculating the amount of commuter travel expenses payment, a database server 170 that manages various table information used by the commuter travel expense calculation server 100 and the batch server 150, and employee terminals 200 installed for each employee of the company that uses the transportation expense/salary linkage support service.

Although not shown in the figure, a map search server that provides location information and a station information search server that provides station information are connected to the Internet 199. When the map search server receives a request including an address string, it searches a database for location information of the address from the received address string and provides this information to the requester. When the station information search server receives a request including location information, it searches a database for nearest station information from the received location information and provides this information to the requester.

[Hardware Configuration of Commuting Expense Calculation Server 100]
Next, the configuration of the commute expense calculation server 100 will be described.

FIG. 2 is a diagram showing a hardware configuration of the commute expense calculation server 100. As shown in FIG.
As shown in FIG. 2, the commuter travel expense calculation server 100 is composed of a CPU (Central Processing Unit) 30 that controls calculations and the entire system based on a control program, a ROM (Read Only Memory) 32 in which the control program etc. of the CPU 30 is stored in advance in a specified area, a RAM (Random Access Memory) 34 for storing data read from the ROM 32 etc. and calculation results required in the calculation process of the CPU 30, and an I/F (InterFace) 38 that mediates the input and output of data to and from external devices, and these are connected to each other so that data can be sent and received by a bus 39, which is a signal line for transferring data.

Connected to the I/F 38 are external devices such as an input device 40 consisting of a keyboard, mouse, etc. that can input data as a human interface, a storage device 42 that stores data, tables, etc. as files, a display device 44 that displays a screen based on an image signal, and a signal line for connecting to the Internet 199.

[Hardware configuration of the batch server 150 and the database server 170]
Next, the configurations of the batch server 150 and the database server 170 will be described.

The batch server 150 and the database server 170 have the same hardware configuration as the commuter travel expense calculation server 100.

[Hardware configuration of employee terminal 200]
The employee terminal 200 is composed of a terminal assumed to be a stationary type such as the commuter travel expense calculation server 100, or a mobile terminal such as a smartphone or tablet. In the former case, the hardware configuration is the same as that of the commuter travel expense calculation server 100. On the other hand, in the latter case, the hardware configuration is composed of a CPU, a ROM that stores programs such as application software and data for executing the programs, a RAM for storing data read from the ROM and the calculation results required in the CPU's calculation process, and an I/F that mediates the input and output of data to various attached devices. These are connected to each other and capable of transmitting and receiving data by signal lines for transferring data.

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

[About the various tables]
Next, the data structures of the various tables stored in the storage device of the database server 170 will be described.

Figures 3(a) to (e) are diagrams showing the data structures of a company master table 400, a workplace master table 402, an employee information master table 404, an employee-specific route information table 406, and an employee-specific payment information table 408.

As shown in Figures 3(a) to (e), the storage device of the database server 170 stores a company master table 400 for registering company information, a workplace master table 402 for registering workplace information for each company, an employee information master table 404 for registering employee information, an employee route information table 406 for registering commuting route information for each employee, and an employee payment information table 408 for registering commuting transportation allowance payment information for each employee.

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

The company ID is information for identifying a company, and is composed of, for example, a unique number for each company (for example, numbers only or a combination of letters and numbers). The application control category is information that determines whether applications from employees can be accepted, and the employee group category information is information that indicates the category of paid employee group, other employee group, job type, office, affiliation, etc.

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

Here, the workplace ID is information for identifying the workplace, and is composed of, for example, a unique number for each workplace (for example, numbers only, a combination of letters and numbers). The calendar ID is information for identifying a calendar that lists the business days and holidays of the workplace set for each company, and is composed of, for example, a unique number for each type of calendar (for example, numbers only, a combination of letters and numbers). The fuel unit price type ID is information for identifying the unit price type of fuel set for each company, and is composed of, for example, a unique number for each unit price type (for example, numbers only, a combination of letters and numbers). The fuel unit price types include unit price types for each fuel, such as gasoline (regular), gasoline (high octane), and diesel (diesel), and unit price types for each type of eco-friendly vehicle, such as EV (electric vehicle), PHV (plug-in hybrid electric vehicle), and FCV (fuel cell vehicle). The map information includes location information of the workplace and information on the nearest station.

As shown in FIG. 3(c), the employee information master table 404 has one record registered for each combination of company ID, employee ID, and application start date. Each record contains main information including company ID, employee ID, employee name, employee name (kana), employee home postal code, employee home address, telephone number, email address, employer ID, employer name, department ID, department name, employee category, payment rule ID, password, authority level, map information, application start date, application end date, last update date, last updater, and other information.

Here, the department ID is information for identifying the department to which the employee belongs, and is composed of, for example, a unique number for each department (for example, numbers only, or a combination of letters and numbers). The employee classification is information for classifying employees as full-time employees, part-time employees, etc., and the authority level is information indicating one of personnel authority, superior authority, and employee authority. Personnel authority is the authority to use all functions related to commuting expenses operations in this system, superior authority is the authority to only apply for commuting routes and approve the contents of the application, and employee authority is the authority to only apply for commuting routes. In addition, the map information includes the location information of the employee's home and information on the nearest station.

One employee may belong to multiple workplaces. For example, an employee may commute to workplace A in the beginning of the month and to workplace B in the latter half of the month. For this reason, one or more workplace IDs and workplace names can be registered for each employee in the employee information master table 404.

As shown in FIG. 3(d), the employee-specific route information table 406 has one record registered for each combination of company ID, employee ID, and route ID. Each record contains main information including company ID, employee ID, vehicle ID, route direction type, nearest station to employee's home, workplace ID, workplace name, nearest station to workplace, route ID, commuting route, route usage period, 1-month amount, 3-month amount, 6-month amount, 12-month amount, one-way amount, one-way distance, one-way time, number of transfers, route reference date, application start date, application end date, last update date, last updater, and other information.

Here, the route direction type is information indicating the direction of the commuting means, and can be outbound, inbound, or round trip. The route ID is information for identifying the commuting route, and can be, for example, a unique number for each commuting route (for example, numbers only, or a combination of letters and numbers). The commuting route is the route from home to the workplace, and for example, if the commuting means is a train, it is "home → walk → nearest station (home) → intermediate station → nearest station (workplace) → walk → workplace", and if the commuting means is a car, it is "home → car → workplace". The one-month amount, three-month amount, six-month amount, and 12-month amount are the amounts of commuting transportation expenses for the set commuting means and route direction type for 1, 3, 6, and 12 months, and the route reference date is the reference date on which the commuting route becomes valid.

When the destination or arrival point of a commuting route is the workplace, the employee-specific route information table 406 registers the workplace ID and workplace name of the workplace that is the destination or arrival point in association with the commuting route. Also, since one employee may belong to multiple workplaces as described above, one or multiple route information can be registered for one employee in the employee-specific route information table 406. When registering route information for multiple workplaces, the employee-specific route information table 406 registers the workplace IDs and workplace names for multiple workplaces for one employee.

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

Here, the payment ID is information for identifying the payment information, and is composed of, for example, a unique number for each payment information (for example, numbers only, or a combination of letters and numbers). The payment method is information indicating the payment method for commuting expenses, such as incorporation into salary, transfer to a bank account, or payment in kind (cash), and the number of months for which payment is made and the number of regular months are either 1 month, 3 months, 6 months, or 12 months. The payment details are information indicating whether or not the payment is subject to continuous payment, whether or not the payment cycle is fixed, and whether or not the fare revision process is applicable.

Figures 4(a) to (e) are diagrams showing the data structures of the employee daily pay information table 410, the department information table 412, the system environment information table 414, the batch job definition information table 416, and the task scheduler information table 418.

As shown in Figures 4(a) to (e), the storage device of the database server 170 stores an employee-specific daily payment information table 410 that registers daily commuter allowance payment information for each employee, and a department information table 412 that registers information on approvers and proxy applicants for each department. In addition, a system environment information table 414 that registers system environment information such as the IP address of the batch server 150, a batch job definition information table 416 that registers batch job definition information including information such as the physical file name of the batch processing program, and a task scheduler information table 418 that registers information for executing tasks registered in the task scheduler are stored.

As shown in FIG. 4(a), the employee-specific daily payment information table 410 has one record registered for each combination of company ID, employee ID, route ID, and daily rate ID. Each record contains main information including company ID, employee ID, route ID, daily rate ID, start date, end date, payment date, payment method, period for daily rate payment, number of days for payment, type of direction of use (one-way/round trip), payment details, payment amount, total payment amount, and other information.

The per diem ID is information for identifying the per diem information, and is composed of, for example, a unique number for each per diem information (for example, numbers only or a combination of letters and numbers). The per diem payment period is information indicating the period for which commuting expenses are calculated on a per diem basis, the number of payment days is information on the number of days during the payment period for which commuting expenses are paid on a per diem basis, and the direction type (one-way/round trip) is information indicating the type of route direction used during the payment period. The payment details are information indicating whether or not the fare is subject to fare revision processing.

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

The approver ID here is the employee ID of an employee with supervisor authority who has the authority to approve commuting route applications for employees who belong to the department corresponding to the department ID, and the proxy applicant ID is the employee ID of an employee with authority to submit commuting route applications on behalf of other employees who belong to the same department.

As shown in FIG. 4(c), the system environment information table 414 stores main information including the batch server IP address, batch server user ID, password, service URL, packet name, actual cost packet name, and other information.

The batch server user ID is information for identifying a user who accesses the batch server 150, and is composed of, for example, a unique number for each user (for example, numbers only, or a combination of letters and numbers). The packet name is the packet name used to create the payroll linkage basic data, and the actual cost packet name is the packet name used to process actual costs.

As shown in FIG. 4(d), the batch job definition information table 416 registers main information including the tenant number, batch process ID, batch name, batch path, batch physical file name, and other information.

Here, the tenant number is the number of the tenant executing batch processing such as the creation process of payroll linkage basic data. The batch processing ID is information for identifying the type of batch processing, and is composed of, for example, a unique number for each type of batch processing (for example, numbers only, or a combination of letters and numbers). The batch path is the physical path (on the batch server 150 side) where the batch processing program is stored, and the batch processing physical file name is the physical file name of the batch processing program.

As shown in FIG. 4(e), the task scheduler information table 418 has one record registered for each combination of tenant number, batch processing ID, and task ID. Each record contains main information including the tenant number, batch processing ID, batch processing path, parameter information, task ID, status, execution flag, and other information.

Here, the batch processing path is information indicating the physical file name (full path) of the batch processing main program that oversees the batch processing, and the parameter information is parameter information read by the batch processing. For example, in the case of a batch processing that creates basic payroll linkage data (hereinafter referred to as "payroll linkage batch processing"), the information is for identifying payment information in which there has been a change in the amount of commuting expenses paid, and includes the company ID, employee ID, payment ID (and the pro rata ID in the case of pro rata payment information), etc.

FIG. 5 is a diagram showing the data structure of the fare information table 420. As shown in FIG.
As shown in FIG. 5, the storage device of the database server 170 stores a fare information table 420 in which fare information relating to fares for transportation such as trains and buses is registered.

As shown in FIG. 5, the fare information table 420 has one record registered for each fare ID. Each record stores main information including the fare ID, section information (e.g., the station numbers of the departure and arrival stations), fare type (e.g., one-month fare, three-month fare, six-month fare, 12-month fare, one-way fare), fare, fare revision date, last update date, last updater, and other information. When a fare revision occurs, records with different revision dates are registered for the same section. In this case, the fare associated with the record with the older revision date can be identified as the fare before revision, and the fare associated with the record with the newer revision date can be identified as the fare after revision.

The commuting expenses of an employee can be calculated by accumulating the fare for the commuting route based on the route information in the employee route information table 406 and the fare information in the fare information table 420. In addition, if commuting expenses are paid on a daily basis, they can be calculated by accumulating the fare for the commuting route based on the route information in the employee route information table 406, the daily payment information in the employee daily payment information table 410, and the fare information in the fare information table 420. The commuting expenses can be calculated using known technology (for example, JP 2003-90733 A).

In addition to tables 400 to 418, the storage device of database server 170 also stores tables in which various definition data for calculating commuting expenses and tables in which various basic data for linking commuting expenses with salary are registered, although these are not shown in the figure. Specific examples of basic data tables include a salary basic data table, a taxation basic data table, a social insurance basic data table, and an employment insurance basic data table.

Here, the basic salary data is data on the amount of the commuting allowance paid, the basic tax data is data on the taxable or non-taxable amount for the commuting allowance paid, the basic social insurance data is data on the amount of social insurance insurance for the commuting allowance paid, and the basic employment insurance data is data on the amount of employment insurance insurance for the commuting allowance paid.

[Operation]
Next, the operation of this embodiment will be described.
[Employee information registration process]
First, the operation of commute expense calculation server 100 when an employee having personnel authority (hereinafter referred to as a "personnel employee") registers employee information will be described.

FIG. 6 is a flowchart showing the employee information registration process.
The CPU 30 is made up of an MPU (Micro-Processing Unit) or the like, and starts up a predetermined program stored in a predetermined area of the ROM 32, and executes an employee information registration process shown in the flowchart of FIG. 6 in accordance with the program.

When the employee information registration process is executed by the CPU 30, as shown in FIG. 6, the process first proceeds to step S100 to determine whether a new employee information registration request has been received from the employee terminal 200, and if it is determined that a new registration request has been received (YES), the process proceeds to step S102.

FIG. 7 is a diagram showing the employee information list screen 500.
Here, when the personnel employee logs in to the transportation fee/salary linkage support service provision page with an account having personnel authority, the top page is displayed on the display device of the employee terminal 200 of the personnel employee. Although not shown in the figure, the top page displays main menu buttons such as "Application", "Employee Information", "Batch Processing", and "Business Master". 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 personnel employee selects the "Employee Information" menu button via the employee terminal 200 (by pressing with a mouse or touching with a finger, etc.), the employee information list screen 500 shown in FIG. 7 is displayed on the display device. Next, by selecting the registration button 50 at the bottom right of the employee information list screen 500, a new registration request for employee information is sent to the commute transportation expense calculation server 100.

In step S102, an employee information input process is executed.
FIG. 8 is a diagram showing the employee information new registration screen 501.

When the employee information input process is executed, first, employee information input screen information is sent to the employee terminal 200 of the human resources employee. As a result, the 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. On this screen, the human resources employee inputs the information to be registered in the employee information master table 404.

On the new employee information registration screen 501, the user can select the department to which the employee to be registered belongs using the drop menu 52 shown in FIG. 8. In addition, by pressing the map button 53 at the bottom right, the nearest station to the employee's home is automatically entered into a list of nearest stations, and by pressing the nearest station registration button 54, the user can enter any nearest station. In addition, by pressing the registration button 55, the nearest station entered can be confirmed.

Then, the process proceeds to step S104 to determine whether a registration request has been received from the employee terminal 200, and if it is determined that a registration request has been received (YES), the process proceeds to step S106.

At this point, 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, whereby a registration application is sent to the commuter travel expense calculation server 100.

In step S106, the contents of the entered employee information are checked, and if it is determined that no mandatory fields have been omitted, the entered employee information is registered in the employee information master table 404. When the processing in step S106 ends, the series of processes ends and the original process is resumed.

On the other hand, if it is determined in step S104 that a registration request has not been received (NO), the process proceeds to step S108 to determine whether a cancellation request has been received from the employee terminal 200, and if it is determined that a cancellation request has been received (YES), the process ends and returns to the original process.

When the back button 56 at the bottom right of the new employee information registration screen 501 shown in FIG. 8 is selected on the employee terminal 200 during the entry of employee information, a pop-up screen (not shown) is displayed asking whether to cancel the entry or not, and when the OK button is selected on the pop-up screen, a request to cancel the registration process is sent to the commute travel expense calculation server 100.

On the other hand, if it is determined in step S108 that a cancellation request has not been received (NO), the process proceeds to step S104.

On the other hand, if it is determined in step S100 that a new registration request has not been received (NO), the process ends and returns to the original process.

[Import process]
Next, the operation of commute expense calculation server 100 when importing employee information will be described.

FIG. 9 is a diagram showing the import screen 502. As shown in FIG.
The import process is a process of reading employee information from a CSV (Comma Separated Values) file or the like, and registering the read employee information in the employee information master table 404. The import process function can be used, for example, by a human resources staff member.

For example, at least the employee information in the employee information master table 404 other than the map information is registered in the CSV file. The human resources staff member selects "Employee Information" as the target table name and selects the CSV file as the import file. Then, by entering other information and clicking the "Execute" button 59, the employee information is read from the selected CSV file and the read employee information is registered in the employee information master table 404. If no map information is registered in the CSV file, the map information is obtained by the nearest station information acquisition process in FIG. 10.

In a configuration in which the nearest station is obtained and set for each record in the CSV file during the import process, it is expected that it will take a considerable amount of time to complete the import of employee information due to factors such as the processing time of the station information search server. Therefore, as in this embodiment, employee information other than map information is read from the CSV file and immediately registered in the employee information master table 404, while location information and nearest station information are obtained and set sequentially by subsequent batch processing, thereby enabling early use of employee information.

[Nearest station information acquisition process]
Next, the operation of the commute travel expense calculation server 100 when acquiring the location information of the employee's home and the information of the nearest station to the employee's home will be described.

The nearest train station to an employee's home is entered when registering employee information, but this can be a lot of work when there are a large number of employees. This is particularly the case when the HR employee is tasked with registering the nearest train stations for other general employees, resulting in a lot of work for the HR employee. Therefore, in this embodiment, the HR employee only needs to enter the employee's home address when registering employee information, and a batch process is used to obtain location information, etc. from the employee home addresses for all target employees, and the obtained location information, etc. is registered in the employee information master table 404.

FIG. 10 is a flowchart showing the nearest station information acquisition process.
When the nearest station information acquisition process is executed by the CPU 30, as shown in FIG. 10, the process first proceeds to step S200.

In step S200, it is determined whether the employee information of the employee being processed has been newly registered or changed in the employee information master table 404, and if it is determined that the employee information has been newly registered or changed (YES), the process proceeds to step S202. Note that if the nearest station information acquisition process is executed after the employee information has been imported from the CSV file, it is determined in step S200 that the imported employee information has been newly registered.

In step S202, the employee ID and employee home address (character string) of the employee to be processed are obtained from the employee information master table 404, and the process proceeds to step S204, where the obtained employee ID and employee home address are registered in the batch list. For employees whose map information is registered, the processes in steps S202 and S204 may be skipped.

Then, the process proceeds to step S206 to determine whether or not the processing of steps S200 to S204 has been completed for all employees. If it is determined that the processing has been completed for all employees (YES), the process proceeds to step S208 to execute batch processing and terminate the series of processes.

On the other hand, if it is determined in step S206 that the processing of steps S200 to S204 has not been completed for all employees (NO), the processing target is changed to the next employee and the process proceeds to step S200.

On the other hand, if it is determined in step S200 that employee information has not been newly registered or changed (NO), the process proceeds to step S206.

[Batch processing]
Next, the batch processing in step S208 will be described.
FIG. 11 is a flowchart showing the batch processing.

When batch processing is executed in step S208, it first proceeds to step S250, as shown in FIG. 11.

In step S250, the employee ID and the employee's home address are obtained from the batch list, and the process proceeds to step S252.

In step S252, the location information of the employee's home is obtained from the map search server by sending a request including the character string of the employee's home address obtained in step S250 to the map search server, and the process proceeds to step S254.

In step S254, a request including the location information obtained in step S252 is sent to the station information search server to obtain information about the nearest station to the employee's home from the station information search server, and the process proceeds to step S256.

In step S256, the location information and nearest station information acquired in steps S252 and S254 are registered in the employee information master table 404 as employee information corresponding to the employee ID acquired in step S250, and the process proceeds to step S258.

In step S258, it is determined whether the processing of steps S250 to S256 has been completed for all records in the batch list, and if it is determined that processing has been completed for all records (YES), the series of processes ends and the process returns to the original process.

On the other hand, if it is determined in step S258 that processing has not been completed for all records (NO), the process changes to the next record and proceeds to step S250.

[New commute route information application process]
Next, we will explain the operation of commute travel expense calculation server 100 when an employee newly applies for commute route information. Note that, in reality, access to tables 400 to 418 is performed by commute travel expense calculation server 100 communicating with database server 170, but for the sake of simplicity, the following explanation will be given assuming that commute travel expense calculation server 100 accesses tables 400 to 418.

FIG. 12 is a flowchart showing the process for applying for new commute route information.
When the new commute route information application process is executed by the CPU 30, as shown in FIG. 12, first, the process proceeds to step S300 to determine whether or not a new application request has been received from the employee terminal 200, and if it is determined that a new application request has been received (YES), the process proceeds to step S302.

A new application for commuting route information is made, for example, when a new employee registers commuting route information for the first time, when an employee moves and their commuting route changes, or when a workplace is added or changed.

In step S102, the application information input process is executed. In the application information input process, the employee can input commuting route information, such as the commuting means (vehicle ID), reason for application, nearest station to the employee's home, nearest station to the workplace, and route direction type, via the input screen.

FIG. 13 is a diagram showing commute route application screen 510.
In the application information input process, first, a commute route application screen 510 is displayed as shown in Fig. 13. On the commute route application screen 510, the applicant (employee) inputs the application start date, commuting means, transportation company, reason for application, employee home address, company name, place of work, and route direction type, etc.

For the employee home address, the employee home address corresponding to the applicant's employee ID is retrieved from the employee information master table 404 and displayed.

For the place of employment, the place of employment corresponding to the applicant's employee ID is obtained from the employee information master table 404 and displayed in the drop-down list 52. If multiple places of employment are registered for one employee, multiple places of employment are displayed in the drop-down list 52. The applicant selects one of these places of employment.

You can select one of three route direction types: "Outbound," "Return," and "Round trip." In other words, you can set separate commuting routes for the outbound, return, and round trip if you are only using the outbound route, only the return route, if the commuting routes are different for the outbound and return trips, or if you are using both the outbound and return trips.

FIG. 14 is a diagram showing commute route application screen 520.
The applicant enters other commuting route information and clicks the "Next" button 53, whereupon a commuting route application screen 520 is displayed, as shown in Fig. 14. In the commuting route application screen 520, the applicant enters the nearest station to the employee's home, any intermediate stations, the nearest station to the workplace, etc.

For the nearest station to the employee's home, the nearest station to the employee's home that corresponds to the applicant's employee ID is obtained from the employee information master table 404 and displayed in the text box 54. If multiple nearest stations to the employee's home are registered, multiple nearest stations are displayed in the text box 54. The nearest station to the employee's home can also be manually entered by clicking the "Search" button 55.

For the nearest station to the workplace, the nearest station to the workplace selected on the commute route application screen 510 that corresponds to the applicant's employee ID is retrieved from the employee information master table 404 and displayed in the text box 56. If multiple nearest stations to the workplace are registered, multiple nearest stations are displayed in the text box 56. Note that the nearest station to the workplace can also be manually entered by clicking the "Search" button 57.

After entering other commute route information, the applicant clicks the "Next" button 58, and candidate commute routes between the nearest station to the employee's home and the nearest station to the workplace are displayed. If there are multiple nearest stations to the employee's home or workplace, candidate commute routes between the nearest station to the employee's home and the nearest station to the workplace are displayed for all combinations of those nearest stations. The applicant can select one of the candidate commute routes displayed and apply for the selected commute route as their commute route.

Then, the process proceeds to step S304 to determine whether a registration request has been received from the employee terminal 200, and if it is determined that a registration request has been received (YES), the process proceeds to step S306.

In step S306, information on the applicant's department (department ID) is obtained from the employee information master table 404, and approval recipient information (employee ID of an employee with approval authority) corresponding to the obtained department ID is obtained from the department information table 412.

The department ID is identification information specific to the workflow, and can be set so that employees across multiple different real organizations have the same department ID. For example, the same department ID "B1" can be set for 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 also a real organization. Note that real organizations are registered using the employee group ID in the employee information master table 404.

For example, suppose that employees A and F are employees with supervisor authority and have been given approval authority in the workflow. Also, suppose that employee E is a general employee and has been given proxy application authority. Here, approval authority is the authority to approve the application contents of employees who belong to the same department (e.g. B1) in the workflow, and proxy application authority is the authority for employees other than the human resources department to make applications on behalf of other employees. In other words, employees A and F who have approval authority can approve applications made by employees B to E and G to I in the same department B1. Also, employee E who has proxy application authority can process applications on behalf of employees A to D and F to I in the same department B1.

As a result, even if the real organizations are different, approval processing and proxy application processing can be performed across real organizations as long as they are managed with the same department ID defined in the department information table 412. In other words, an amoeba-like approval route can be constructed.

Next, the process proceeds to step S308, where an approval route is constructed based on the obtained approval destination information. After that, an approval request for the application information is sent to each approver at the route destination based on the constructed approval route.

For example, if a general employee (other than A and F) in department B1 applies for a commuter route, approval will be provided by both employees A and F, and after approval, the route will be inspected by three personnel staff members J through L in charge of department B1. Note that personnel staff members have the authority to inspect any department.

In other words, the approval route will be "employees A and F" first, and after employee A approves first, it will be "employee A → personnel employees J-L". On the other hand, after employee F approves first, it will be "employee F → personnel employees J-L". In other words, approval only needs to be done by either employee A or F, and approval by both is not required. In addition, inspection after approval will be carried out by the three personnel employees J-L in charge of department B1, and inspection can also be carried out by any one of personnel employees J-L.

In this way, approval and inspection are carried out, and the application is approved, and the application information is registered in the employee-specific route information table 406, the employee-specific payment information table 408, and the employee-specific daily payment information table 410. In other words, when a new commuting route is registered, a change occurs in the payment information or daily payment information stored in the employee-specific payment information table 408 or the employee-specific daily payment information table 410, causing a change in the amount of commuting expenses paid.

When the process of step S308 is completed, the series of processes ends and the process returns to the original process.
On the other hand, if it is determined in step S304 that a registration application has not been received (NO), the process proceeds to step S310 to determine whether or not a cancellation request has been received from the employee terminal 200, and if it is determined that a cancellation request has been received (YES), the process ends and returns to the original process.

On the other hand, if it is determined in step S310 that a cancellation request has not been received (NO), the process proceeds to step S304.

On the other hand, if it is determined in step S300 that a new application request has not been received (NO), the system waits in step S300 until a new application request is received.

[Payment information addition/modification processing]
Next, the operation when a personnel staff member adds or modifies the payment information registered in the employee-specific payment information table 408 and the employee-specific daily prorated payment information table 410 will be described.

When a HR employee logs in to the commuter expense/salary linkage service provider page with an account that has HR authority, the service's homepage is displayed on the display device of the HR employee's employee terminal 200. Although not shown in the figure, this homepage displays main menu buttons such as "Application," "Employee Information," and "Business Master." Although not shown in the figure, these main menu buttons are always displayed at the top of the screen and can be selected from pages other than the homepage. When the HR employee selects the "Employee Information" menu button via the employee terminal 200 (by pressing the mouse or touching with a finger, etc.), the employee information list screen 500 shown in FIG. 7 is displayed on the display device. Here, the HR employee has the authority to perform tasks related to the calculation of commuter expense payment amounts.

The payment information addition/modification process is a process executed on the route list screen 800 that is displayed after selecting an employee to be added or modified on the employee information list screen 500 and selecting the route list button 51. The route list screen 800 displays one or more approved commuting routes used by the selected employee. If the selected employee belongs to multiple workplaces, the route list screen 800 displays the commuting route from home to the workplace or the commuting route from the workplace to home for each of the multiple workplaces.

Figure 15 is a flowchart showing the payment information addition/modification process. Figure 16 is a diagram showing the route list screen 800. Figure 17 is a diagram showing the payment information list screen 801.

When the payment information addition/modification process is executed by the CPU 30, the process first proceeds to step S400, as shown in FIG. 15.

In step S400, based on information from the employee terminal 200, it is determined whether the Modify Route button 80 has been selected for a commuting route selected from the list of commuting routes for the selected employee displayed on the route list screen 800. If it is determined that the Modify Route button 80 has been selected (YES), the screen information of the payment information list screen 801 is sent to the employee terminal 200. In other words, when the Modify Route button 80 is selected on the route list screen 800 shown in FIG. 16, the payment information list screen 801 shown in FIG. 17 is displayed on the display device of the employee terminal 200.

Next, the process proceeds to step S402, where 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 the Add button 82 has been selected (YES), the screen information of the payment information setting screen is sent to the employee terminal 200. That is, if the Modify button 83 is selected with pro rata payment information selected on the payment information list screen 801 shown in FIG. 17, a pro rata payment information setting screen (not shown) is displayed on the display screen of the employee terminal 200. Note that, although not shown, if the Modify button 83 is selected with regular payment information selected, a screen that allows additional settings of regular payment information different from the pro rata payment information setting screen is displayed, and if the Add button 82 is selected with nothing selected, a screen that allows additional settings of both regular and pro rata payment information is displayed.

Then, the process proceeds to step S404 to execute the payment information addition process. As the payment information addition process, the process of adding payment information based on the information entered by the human resources employee on the pro rata payment information setting screen will be described.

The personnel staff enters the necessary information on the pro rata payment information setting screen via the employee terminal 200. Specifically, the staff enters the period for which the pro rata payment is applicable, the number of days for which the payment is applicable, and the type of direction of use (one way/round trip). The pro rata payment information is set, for example, when the joining date is an odd day and the employee starts working partway through the month, and commuting expenses are paid on a pro rata basis only for the days the employee works in that month. Or, for example, when the employee needs to work from home due to the spread of an infectious disease, and the employee works only two days a week, and commuting expenses are paid on a pro rata basis only for the days the employee works. Therefore, the period for which the pro rata payment is applicable is set as the period for which the pro rata payment is applicable.

Here, for the direction of travel type, select round trip if the same commuter route was used on the outbound and return journeys, and select one-way if different commuter routes were used on the outbound and return journeys or if only one-way travel was used. This allows round trip or one-way travel to be set commonly for each date in the payment period. Also, if there are days when the same commuter route was used only one way and days when it was used both ways, the direction of travel type can be set individually for each date after selecting either one-way or round trip.

After inputting the pro rata payment information, by selecting the OK button (not shown) displayed on the pro rata payment information setting screen, it is determined that input of the pro rata payment information is complete, and the screen returns to the payment information list screen 801 shown in FIG. 17. The newly input pro rata payment information is added to the list on the payment information list screen 801, and by selecting the Confirm button at the bottom right, the new pro rata payment information is added to the employee pro rata payment information table 410. In other words, the addition of new pro rata payment information causes a change in the payment amount for commuting expenses.

When the process of step S404 ends, the series of processes ends and the process returns to the original process.
On the other hand, if it is determined in step S402 that the Add button 82 has not been selected (NO), the process proceeds to step S406, where it is determined, based on information from the employee terminal 200, whether or not the Modify button 83 has been selected for the selected payment information on the payment information list screen 801. If it is determined that the Modify button 83 has been selected (YES), screen information for the payment information setting screen is transmitted to the employee terminal 200. That is, if the Modify button 83 is selected with pro rata payment information that has already been registered selected on the payment information list screen 801 shown in FIG. 17, the pro rata payment information setting screen is displayed on the display screen of the employee terminal 200 with information already entered.

Next, the process proceeds to step S408, where the payment information correction process is executed. The payment information correction process is a process for correcting information already entered on the pro rata payment information setting screen, and is the same process as the payment information addition process, except that new information is entered or already entered information is changed (corrected), so a description of this process is omitted. Furthermore, correction of the pro rata payment information causes a change in the pro rata payment amount for commuting expenses in the pro rata payment information stored in the employee-specific pro rata payment information table 410. When the process of step S408 is completed, the series of processes is terminated and the original process is resumed.

On the other hand, if it is determined in step S406 that the Modify button 83 has not been selected (NO), the process proceeds to step S410, where it is determined whether any other button other than the Add button 82 and the Modify button 83 has been selected. If it is determined that any other button has been selected (YES), the screen information of the screen corresponding to the other button is sent to the employee terminal 200, and the process proceeds to step S412.

In step S412, the process corresponding to the other button that was selected is executed. The other buttons include a Cancel button, a Delete button, a Confirm button, and a Cancel button, as shown in FIG. 17. When the Cancel button is selected, the process of canceling the commuter pass is executed, when the Delete button is selected, the process of deleting the selected payment information is executed, and when the Cancel button is selected, the process of canceling the commuter route correction and returning to the route list screen 800 is executed. When the process in step S412 is completed, the series of processes is terminated and the original process is resumed.

On the other hand, if it is determined in step S410 that no other button has been selected (NO), the process proceeds to step S402.

On the other hand, if it is determined in step S400 that the route modification button 80 has not been selected (NO), the process waits in step S400 until the route modification button 80 is selected.

[Payment information addition/modification processing]
Regular employees can also use the same functions as the payment information addition/modification process described above. Regular employees can add to their own payment information. However, the difference is that the content of the payment information added by regular employees is finalized after approval from the approving party.

[Payroll link basic data creation task registration process]
Next, the operation of the commute expense calculation server 100 in the case where a salary linked basic data creation task is registered in the batch server 150 in response to a change in the amount of commute expense payment will be described.

FIG. 18 is a flowchart showing the salary-linked basic data creation task registration process.
When the payroll linked basic data creation task registration process is executed by the CPU 30, as shown in FIG. 18, first, the process proceeds to step S500.

In step S500, it is determined whether a change has occurred in the payment information in the employee-specific payment information table 408 or the employee-specific daily payment information table 410. If it is determined that a change has occurred in the payment information (YES), the process proceeds to step S502.

FIG. 19 is a diagram for explaining an example in which the amount of commuting expenses paid fluctuates.
As shown in Fig. 19, when an employee applies for a new commute route and the application is approved (permitted) by the superior and the human resources department, payment information according to the newly applied commute route is generated and registered in the employee-specific payment information table 408. Similarly, when a human resources employee applies for a new commute route on behalf of an employee, payment information according to the applied commute route is generated and registered in the employee-specific payment information table 408. In such cases, it is determined whether there has been a change in the payment information that would change the payment amount.

In addition, when monthly processing by personnel staff involves calculations such as the payment of commuting expenses on a pro rata basis, fluctuations occur in the registered details of the employee-specific pro rata payment information table 410 that change the payment amount, and these fluctuations are determined to be changes in the payment amount.

In addition, even if a difference occurs between the amount already paid due to a fare revision, the payment of the difference causes a change in the payment amount in the employee-specific payment information table 408 or employee-specific daily payment information table 410, and this change is determined to be a change in the payment amount. In addition, after the registration of the daily payment amount and the adjustment process of the difference due to the fare revision are completed, the salary data is output to the salary linkage system, and then the process of creating the next salary linkage basic data in advance is performed. At this time, if a change occurs in the salary linkage basic data created in advance due to daily payment or fare revision, etc., a change in the payment amount occurs in the payment information in the employee-specific payment information table 408 or employee-specific daily payment information table 410, and this is also determined to be a change in the payment amount. The change in the payment amount is determined, for example, by whether or not a revision date has been set in the fare information table 420 after the completion of the salary payment calculation process for the previous commuting expenses payment month.

In step S502, parameter information related to the payment information in which the payment amount has changed is checked. The parameter information to be checked includes the tenant number of the tenant executing the payroll linkage batch process, the company ID, the ID of the payroll linkage batch process program (hereinafter referred to as the "payroll linkage batch process ID"), and the payment ID of the payment information in which it was determined in step S500 that a change has occurred that has changed the payment amount.

The payment ID of the payment information that has been subject to the fare revision among the payment information set as the target for fare revision processing (hereinafter referred to as "payment information related to the fare revision") is, for example, as follows: Based on the employee-specific route information table 406 and the fare information table 420, the relevant route information is identified from the section information that has been subject to the fare revision, and the payment ID of the payment information for which commuting expenses have been calculated using the identified route information is obtained from the employee-specific payment information table 408. Parameter information including the obtained payment ID is registered in the task scheduler information table 418 in step S522.

The payment ID of the daily pro rata payment information that has been subject to fare revision among the daily pro rata payment information set as the target for fare revision processing (hereinafter referred to as "daily pro rata payment information related to fare revision") is, for example, as follows: Based on the employee-specific route information table 406 and the fare information table 420, the relevant route information is identified from the section information that has been subject to fare revision, and the payment ID and daily pro rata ID of the daily pro rata payment information for which commuting expenses have been calculated using the identified route information are obtained from the employee-specific daily pro rata payment information table 410. Parameter information including the obtained payment ID is registered in the task scheduler information table 418 in step S522.

Then, the process proceeds to step S504, where the physical file name (full path) of the batch processing main program is obtained from the batch job definition information table 416 stored in the storage device 42. Here, the batch processing main program is a program that provides overall control over various batch processes such as payroll linkage batch processing, and the batch processing that is executed is controlled by the contents of the parameters that are set when the batch processing main program is executed.

Next, the process proceeds to step S506, where the IP address, login user ID, and password of the batch server 150 are obtained from the system environment information table 414 stored in the storage device 42, and the process proceeds to step S508.

In step S508, the process logs in to the batch server 150 and establishes a session based on the information acquired in step S506. Then, the process proceeds to step S510.

In step S510, the task execution conditions are created by the task scheduler. The task execution conditions are such that the task is executed after a predetermined time (hereinafter referred to as the "start delay time") that takes into account the communication lag with the batch server 150. If the system times of the commuter travel expense calculation server 100 and the batch server 150 are the same, the start delay time is set to, for example, two minutes after the system time of the commuter travel expense calculation server 100. If the system times differ by a predetermined time, the predetermined time by which the system times differ is also taken into account. In other words, the task is scheduled to be executed after the start delay time from the registration of the task schedule, taking into account the communication lag.

In addition, the commuter travel expense calculation server 100 and the batch server 150 have a task scheduler installed in their operating systems (OS).

A task scheduler is one of the execution control systems for computer programs, which starts and ends programs based on schedules and conditions specified by the user, and records and reports the execution status and results. This makes it possible to automatically start and end specific commands and executable files on the OS based on a schedule.

Next, proceed to step S512 to create a task action. A task action consists of an execution program and execution parameters (arguments given to the execution program). Specifically, the execution program is a batch processing main program, and the execution parameters are the tenant number, payroll integration batch processing ID, and task ID. Here, the task ID is information for identifying the task to be registered in the task scheduler.

Next, proceed to step S514 to create a deletion setting for the action after the task is completed. Here, the process of creating basic salary linkage data when there is a change in the payment amount is a process that is performed immediately when a change occurs, and is not a process that is repeated periodically, so a setting is created to delete the action after the task is completed. Specifically, the time until the task is deleted if it is not scheduled to be executed again is set.

Then, proceed to step S516 to create an instance of the task scheduler. That is, create an instance of the batch processing main program (payroll linkage batch processing) to be executed by the task scheduler. That is, the batch processing main program, execution parameters, etc. are expanded on the main memory of the batch server 150 so that they can be processed and executed.

The payroll linkage batch process must be executed after it is determined that the commuter travel expense payment amount has changed, and before data related to the commuter travel expense payment amount and other payment amounts is output to other payroll calculation systems. Therefore, it is desirable to execute the payroll linkage batch process promptly after it is determined that a change has occurred in the payment amount.

In addition, the task scheduler executes processes on an instance-by-instance basis, allowing multiple instances to run in parallel.

Next, the process proceeds to step S518, where the various information created in steps S510 to S516 is registered in the task scheduler. That is, information such as the tenant number, company ID, payroll integration batch processing ID, task schedule (year, month, day, hour, minute), and executing user is registered.

Then, proceed to step S520, discard the session with the batch server 150, and proceed to step S522.

In step S522, task scheduler information, which is information necessary for executing the task registered in the task scheduler, is registered in the task scheduler information table 418. Specifically, the tenant number, batch process ID, batch process path, parameter information, task ID, status, execution flag, and other information are registered in the task scheduler information table 418. When the processing in step S522 ends, the series of processes ends and the process returns to the original process.

The processing in steps S508 to S520 is performed automatically, for example, using a command line interface installed in the OS (for example, "Windows PowerShell (registered trademark)" if the OS is Windows).

On the other hand, if it is determined in step S500 that no change has occurred in the payment information (NO), the process waits in step S500 until a change occurs in the payment information.

[Payroll link batch processing program execution process]
The payroll linkage batch processing program execution process is a process executed by the task scheduler in the batch server 150.

Figure 20 is a flowchart showing the payroll linkage batch processing program execution process. Figure 21 is a diagram showing the flow of the batch processing main program execution process by the task scheduler in the batch server 150.

The CPU of the batch server 150 starts a specific program stored in a specific area of the ROM, and executes the payroll linkage batch processing program execution process shown in the flowchart of Figure 20 in accordance with the program.

When the payroll linkage batch processing program execution process is executed by the CPU, it first proceeds to step S600, as shown in Figure 20.

In step S600, it is determined whether the execution time for the registered task has arrived, and if it is determined that the execution time has arrived (YES), the process proceeds to step S602.

In this case, as shown in FIG. 21, the task schedule is registered in the task scheduler so that the batch processing main program is executed after the start delay time from registration, so the execution time is after the start delay time from registration.

In step S602, the execution parameters registered in the task scheduler are checked. Here, the execution parameters are the tenant number, the payroll integration batch processing ID, and the task ID.

Next, the process proceeds to step S604, where parameter information required to execute the task corresponding to the execution parameters checked in step S602 is obtained from the task scheduler information table 418. Specifically, as shown in FIG. 21, parameter information corresponding to the tenant number, batch processing ID, and task ID of the task to be executed is obtained as parameter information.

Next, the process proceeds to step S606, where the batch processing main program is executed based on the various information registered in the task scheduler and the parameter information acquired in step S604, and the payroll linkage batch processing program is executed. The batch processing main program reads out the payroll linkage batch processing program (module) corresponding to the payroll linkage batch processing ID, for example, from a batch processing business module library (not shown) stored in the storage device of the batch server 150. The read-out payroll linkage batch processing program is then executed.

When the payroll linkage batch processing program is executed, as shown in FIG. 21, the calculated values of the payroll linkage basic data (salary basic data, taxation basic data, social insurance basic data, and employment insurance basic data) are recalculated based on the changes in the payment information corresponding to the parameter information acquired in step S604, and the calculated values of the various basic data registered in the various basic data tables are updated to the recalculated data.

The salary payment calculation process that calculates the amount of commuting expenses includes a first calculation process that calculates the amount of commuting expenses and the amount of payment that varies depending on the commuting expenses out of the amount of payment paid to the employee. The salary payment calculation process also includes a second calculation process that calculates other payment amounts (e.g. overtime pay, etc.). Furthermore, there is a third calculation process that calculates the payment amount based on the results of the first and second calculation processes. Note that the second and third calculation processes are, for example, processes performed in another salary calculation system. In the salary linkage batch process, the first calculation process is executed.

The payroll link batch process does not calculate the amount of commuting expenses to be paid in the current month all at once, but instead distributes it over time for each payment information unit. For example, when a new application for a commuting route or an application for a change is made, the payment amount related to that application is calculated at that time, and when a fare revision is made, the payment amount related to the fare revision is calculated at that time.

In addition, in the salary linkage batch process, the commuter transportation expense payment amount is calculated for each specified period (for each month in which the commuter transportation expense is paid (for example, every month, every three months, etc.)). Therefore, the salary linkage batch processing program is executed within the period from the completion of the salary payment calculation process for the previous commuter transportation expense payment month to the execution timing of the salary payment calculation process for the next commuter transportation expense payment month. Here, the "execution timing of the salary payment calculation process" refers to the timing when the second calculation process and the third calculation process are executed, in which the second calculation process and the third calculation process are, for example, monthly batch processes. In addition, in the salary payment calculation process for the commuter transportation expense payment month, the uncalculated calculation process of the first calculation process, the second calculation process, and the third calculation process is executed.

Figure 22 is a time chart showing the calculation of payment information and daily payment information related to fare revisions.

In the example of Figure 22, if a fare revision occurs after the previous salary payment calculation process is completed, and this fare revision causes a change in the commuter travel allowance payment amounts for employees A and C, a salary linkage batch process is executed for the payment information for employee A and the payment information for employee C. If a fare revision occurs again after that, and this fare revision causes a change in the commuter travel allowance payment amounts for employees B and D, a salary linkage batch process is executed for the payment information for employee B and the payment information for employee D. Then, when it is time to execute the next salary payment calculation process, the second calculation process and the third calculation process are executed. In this way, when a fare revision occurs, the payment information for the relevant employee is recalculated, rather than the payment information for all employees being recalculated each time.

Next, the process proceeds to step S608, where the task scheduler information after the task is completed is deleted from the task scheduler information table 418, the process ends, and the process returns to the original process.

On the other hand, if it is determined in step S600 that the time to execute the task has not yet arrived (NO), the process waits in step S600 until the execution time arrives.

[Effects of the embodiment]
Next, the effects of this embodiment will be described.
In this embodiment, the home addresses of employees are obtained from the employee information master table 404, nearest station information is obtained from the station information search server based on the obtained home addresses of the employees, and the obtained nearest station information is set to the employee information in the employee information master table 404. This batch processing (FIG. 11) is performed for multiple employees at once.

This allows the process of setting the nearest stations for multiple employees to be performed all at once, reducing the effort required to register the nearest station information to employees' homes compared to previous versions.

Furthermore, in this embodiment, employee information is obtained from a CSV file or the like in which at least employee information including the employee's home address is registered, and the obtained employee information is registered in the employee information master table 404. At the same time, nearest station information is obtained from a station information search server based on the employee's home address contained in the employee information in the CSV file or the like, and a batch process (FIG. 11) is performed after the registration of employee information (information other than map information) in the employee information master table 404 has been completed, in which the obtained nearest station information is set for the employee information in the employee information master table 404.

As a result, employee information such as a CSV file is registered in the employee information master table 404, while location information and nearest station information are obtained and set by batch processing after registration is complete, enabling employee information to be used quickly.

Furthermore, in this embodiment, route information regarding the commuting route used by an employee to travel between his/her home and each of multiple workplaces to which the employee belongs, and daily payment information regarding the employee's actual use of multiple commuting routes are obtained, and the payment amount for an employee using multiple commuting routes is calculated based on the obtained route information and daily payment information, as well as the fare information in the fare information table 420.

This makes it possible to calculate the amount of transportation expenses to be paid on a pro-rata basis to employees who work at multiple workplaces, depending on the commuting route they use.

Furthermore, in this embodiment, based on the route information in the employee route information table 406 and the fare information in the fare information table 420, the payment information that is subject to fare revision is identified, and a payroll linkage batch process is executed to calculate the payment amount related to the identified payment information.

This allows the salary link batch processing to be executed in a time-series distributed manner when there is a fare revision, reducing the load on the salary payment calculation processing. In other words, when there is a fare revision, the payment amount related to the fare revision can be recalculated, reducing the load on the salary payment calculation processing compared to calculating the amount for all employees at once.

Furthermore, in this embodiment, when it is determined that there has been a change in payment information that causes a change in the amount of commuter expenses paid, a payroll linkage batch process is executed to calculate or recalculate the amount of commuter expenses paid.

This allows the salary link batch processing to be executed in a time-series distributed manner when the amount of commuter travel expenses changes, reducing the load on the salary payment calculation processing. In other words, when the amount of commuter travel expenses changes, the commuter travel expenses of the employee related to the change or the payment amount that changes depending on the commuter travel expenses can be recalculated, reducing the load on the salary payment calculation processing compared to calculating the amount for all employees at once.

Furthermore, in this embodiment, the task is scheduled to be executed after a start delay time from the registration of the task schedule, taking into account communication lags, and the payroll linkage batch processing program is executed after a predetermined time has elapsed since registration.

This reduces the possibility that payroll linkage batch processing cannot be executed by the batch server 150 if a communication lag occurs.

Furthermore, in this embodiment, when an employee or proxy applicant (including a human resources employee) applies for or applies for a proxy for commuting route information, the application is approved by the superior employee and the human resources employee, and the payment information for the target employee is registered in the employee-specific payment information table 408 for the first time, it is determined that a change has occurred in the commuter transportation allowance payment amount. In addition, when an application for commuting route information is approved and the payment information registered in the employee-specific payment information table 408 is changed, it is determined that a change has occurred in the commuter transportation allowance payment amount.

In addition, if new pro rata payment information is registered in the employee-specific pro rata payment information table 410, it is determined that a change has occurred in the amount of commuting expenses paid. Furthermore, if a change has occurred in the existing pro rata payment information registered in the employee-specific pro rata payment information table 410 through monthly processing by a personnel employee, it is determined that a change has occurred in the amount of commuting expenses paid.

Furthermore, if a fare revision results in a difference between the payment amount corresponding to the revised fare and the payment amount already paid, new pro rata payment information is registered in the employee-specific pro rata payment information table 410 to pay the difference, or existing pro rata payment information that has already been registered is changed. In this case, too, it is determined that a change has occurred in the payment amount for commuting expenses.

In addition, after the salary linkage basic data is linked (output to the salary linkage system) when a change occurs in the amount of commuting expenses paid, the next salary linkage basic data created in advance will also change, so in this case too, it will be determined that a change has occurred in the amount paid.

This allows distributed processing when changes occur in the amount of commuting expenses paid for reasons other than commuting route applications, such as daily pro rata payments or fare revisions, and further reduces the load on salary payment calculation processing. In addition, because it is determined that a change has occurred in the amount of commuting expenses paid based on the registration of payment information or daily pro rata payment information in employee-specific payment information table 408 or employee-specific daily pro rata payment information table 410, it is possible to more reliably determine whether or not the amount of payment has changed.

[Correspondence]
In this embodiment, steps S200 to S208 correspond to the station information setting means of Inventions 1 to 3, and the memory device of the database server 170 corresponds to the target person information storage means of Inventions 1 to 3, the route information storage means of Invention 1 or 3, or the fare information storage means of Invention 1 or 3.

[Modifications]
In the above embodiment, the nearest station information is registered in the employee information registration process, but this is not limited to this. It is also possible to adopt a configuration in which the registration of the nearest station information is optional, or a configuration in which the nearest station information is not registered in the employee information registration process, but is registered by the nearest station information acquisition process of Figure 10.

Furthermore, in the above embodiment and its modified example, the execution timing and other execution conditions of the nearest station information acquisition process in FIG. 10 were not explained, but, for example, a configuration can be adopted in which the process is executed when the user instructs execution of the nearest station information acquisition process, or a configuration in which batch processing is scheduled and executed at that execution timing.

In addition, in the above embodiment and its modified examples, the execution timing and other execution conditions of the batch processing in FIG. 11 were not described, but for example, a configuration in which the batch processing is executed when the user instructs the execution of the batch processing, or a configuration in which the batch processing is scheduled and executed at the execution timing can be adopted. The batch processing may be executed consecutively with the nearest station information acquisition processing in FIG. 10, or may be executed at a different timing from the nearest station information acquisition processing in FIG. 10.

In addition, in the above embodiment and its modified example, the batch processing in FIG. 11 is executed by the commuter travel expense calculation server 100, but this is not limited to the above, and a configuration in which it is executed by the batch server 150, similar to the salary payment calculation process, can be adopted.

In the above embodiment and its modified example, employee information is acquired and set from a CSV file or the like in which at least employee information including the employee's home address is registered, but this is not limiting, and a configuration in which workplace information is acquired from a CSV file or the like in which at least workplace information including the workplace address is registered can be adopted. Workplace information is acquired from a CSV file or the like in which at least workplace information including the workplace address is registered, and the acquired workplace information is registered in the workplace master table 402. Then, nearest station information is acquired from a station information search server based on the workplace address included in the workplace information in the CSV file or the like, and a batch process is performed after the registration of workplace information (information other than map information) in the CSV file or the like in the workplace master table 402 is completed.

In addition, in the above embodiment and its modified example, the process of obtaining the nearest station information to the employee's home is performed for multiple employees at once, but this is not limited to the above, and a configuration can be adopted in which the process of obtaining the nearest station information to the employee's home is performed sequentially for multiple employees.

In addition, in the above embodiment and its modified example, the nearest station information acquisition process did not explain whether to acquire the nearest station information using the employee's home address in a CSV file or the like, or using the employee's home address acquired from a CSV file or the like and registered in the employee information master table 404, but either information can be used.

In addition, in the above embodiment and its modified examples, location information and nearest station information are registered in the employee information master table 404, but this is not limiting, and location information does not need to be registered.

In the above embodiment and its modified example, the processes of FIG. 10 and FIG. 11 may be applied to the case of acquiring the nearest station to the workplace or other destinations. In the case of the nearest station to the workplace, for example, a configuration can be adopted in which the address of the workplace is acquired from the workplace master table 402, nearest station information is acquired from the station information search server based on the acquired workplace address, and batch processing (FIG. 11) is performed for multiple workplaces in a batch to set the acquired nearest station information to the workplace information in the workplace master table 402. In the case of the nearest station to other destinations, for example, a configuration can be adopted in which destination information including the destination address is registered in the destination information table, the destination address is acquired from the destination information table, nearest station information is acquired from the station information search server based on the acquired destination address, and batch processing (FIG. 11) is performed for multiple destinations in a batch to set the acquired nearest station information to the destination information in the destination information table. Note that the above modified example regarding the setting of the nearest station to the employee's home can be applied to the configuration regarding the setting of the nearest station to the workplace.

In addition, in the above embodiment and its modified examples, the transportation allowance amount was calculated based on the daily payment information (period eligible for daily payment, number of days eligible for payment, etc.) in the employee daily payment information table 410 as information regarding an employee's actual use of multiple commuting routes, but it is not limited to this, and the transportation allowance amount can also be calculated based on the payment information (period eligible for payment, number of months eligible for payment, etc.) in the employee daily payment information table 408.

In addition, in the above embodiment and its modified examples, in the application information input process in step S102, one of multiple workplaces to which the applicant (employee) belongs is selected, but this is not limited to the above, and a configuration in which one of multiple workplaces set for the company to which the employee belongs can be selected can also be adopted. In this case, workplaces to which the employee does not belong may be included as candidates.

In addition, in the above embodiment and its modified examples, the payment amount calculation means of inventions 1, 3, 4, and 6 has been described as corresponding to the process of calculating the payment amount of transportation expenses when the addition of payment information made by an employee is approved by the approval party, but is not limited to this and can also correspond to the process of calculating the payment amount of transportation expenses in the batch server 150.

In addition, in the above embodiment and its modified examples, the fare information in the fare information table 420 is used to identify the payment information that is the subject of the fare revision, but this is not limited to the above. For example, section information regarding the section in which the fare revision occurred, route information regarding the commuter route in which the fare revision occurred, and other revision information regarding the fare revision can be used. In other words, any information that can determine that a fare revision has occurred is sufficient, and information on the fares before and after the revision or the revision date is not necessarily required.

In the above embodiment and its modified example, the payment amount related to the fare revision is recalculated when the fare revision occurs, but this is not limited to the above. A configuration can be adopted in which the payment amount of the commuting expenses to be paid in the current month and related to the fare revision is calculated at the time of the fare revision. In this case, based on the route information in the employee route information table 406 and the fare information in the fare information table 420, the payment that is subject to the fare revision is identified, and a salary linkage batch process is executed to calculate the payment amount related to the identified payment. The payment that is subject to the fare revision can be identified, for example, by identifying the commuting route related to the fare revision, or by identifying the employees who use the commuting route related to the fare revision.

In addition, in the above embodiment and its modified examples, it is determined that a change has occurred in the amount of commuting expenses paid when new payment information or daily rate payment information is registered in the employee-specific payment information table 408 or the employee-specific daily rate payment information table 410, or when the payment information or daily rate payment information is changed, but this is not the only possible configuration. For example, other configurations may be used, such as a configuration in which it is determined that a change has occurred in the amount of payment when a commuting route is applied for and the application is approved.

In addition, in the above embodiment and its variations, the system is realized as a network system, but the system is not limited to this and can also be realized as a single device or application.

In addition, in the above embodiment and its modified examples, the payroll linkage batch processing is configured to be executed by the batch server 150 using a task scheduler, but this is not limited to the above, and it is also possible to adopt a configuration in which the payroll payment calculation processing is executed only by the commute travel expense calculation server 100, or a configuration in which the payroll payment calculation processing is executed in cooperation with other servers other than the batch server 150.

In addition, in the above embodiment and its modified examples, the case where the invention is applied to a network system consisting of the Internet 199 has been described, but the invention is not limited to this, and may be applied, for example, to a so-called intranet that communicates in the same manner as the Internet 199. Of course, the invention can be applied to a network of any communication method, not limited to a network that communicates in the same manner as the Internet 199.

In addition, in the above embodiment and its modified examples, the processes shown in the flowcharts of Figures 12, 15, 18, and 20 are executed by executing a program that is pre-stored in ROM. However, this is not limited to the above, and the program showing these procedures may be loaded into RAM from a storage medium on which the program is stored and executed.

In addition, in the above embodiment and its modified examples, the present invention is applied to cases such as calculating commuting expenses for employees, but it is not limited to this and can be applied to other cases without departing from the spirit of the present invention. For example, the present invention can be applied when calculating travel expenses for business trips and other travel expenses, when calculating travel expenses paid to persons other than employees, and when calculating travel expenses for using routes other than the commuting route.

100... Commuting travel expense calculation server, 150... Batch server, 170... Database server, 200... Employee terminal, 30... CPU, 32... ROM, 34... RAM, 38... I/F, 39... Bus, 40... Input device, 42... Storage device, 44... Display device, 199... Internet, 400... Company master table, 402... Workplace master table, 404... Employee information master table, 406... Employee route information table, 408... Employee payment information table, 410... Employee daily rate payment information table, 412... Department information table, 414... System environment information table, 416... Batch job definition information table, 418... Task scheduler information table, 420... Fare information table

Claims (6)

an employee information acquiring means for acquiring employee information from a file in which employee information including home address information of a plurality of employees is registered;
an employee information registration means for registering the employee information acquired by the employee information acquisition means into an employee information storage means;
a batch list registration means for registering the address information included in the employee information in a batch list when the employee information is registered or changed in the employee information storage means;
a station information setting means for performing an acquisition and setting process of acquiring nearest station information from the address information included in the batch list for all the address information in the batch list, and setting the acquired nearest station information to the corresponding employee information in the employee information storage means;
a payment amount calculation means for calculating a payment amount of commuting expenses when the employee uses the route, based on route information stored in a route information storage means for storing route information related to the route used by the employee to travel between the nearest station to his/her home and his/her workplace, and fare information stored in a fare information storage means for storing fare information related to the route,
A payment calculation system characterized in that the employee information in said employee information storage means is available for use immediately after registration by said employee information registration means, independently of execution of said acquisition and setting process. a first employee information acquisition means for acquiring employee information including home address information of each employee;
a second employee information acquiring means for acquiring employee information from a file in which employee information including home address information of a plurality of employees is registered;
an employee information registration means for registering the employee information acquired by the first employee information acquisition means or the second employee information acquisition means into an employee information storage means;
a batch list registration means for registering the address information included in the employee information in a batch list when the employee information is registered or changed in the employee information storage means;
a station information setting means for performing an acquisition and setting process of acquiring nearest station information from the address information included in the batch list for all the address information in the batch list, and setting the acquired nearest station information to the corresponding employee information in the employee information storage means;
a payment amount calculation means for calculating a payment amount of commuting expenses when the employee uses the route, based on route information stored in a route information storage means for storing route information related to the route used by the employee to travel between the nearest station to his/her home and his/her workplace, and fare information stored in a fare information storage means for storing fare information related to the route,
A payment calculation system characterized in that the employee information in said employee information storage means is available for use immediately after registration by said employee information registration means, independently of execution of said acquisition and setting process. In any one of claims 1 and 2,
A payment calculation system characterized in that, when the registered or changed employee information includes the nearest station information, the batch list registration means does not register the address information included in the employee information in the batch list. a workplace information acquiring means for acquiring workplace information for a plurality of employees from a file in which workplace information including address information of the workplaces of the employees is registered;
a workplace information registration means for registering the workplace information acquired by the workplace information acquisition means in a workplace information storage means;
a batch list registration means for registering the address information included in the workplace information in a batch list when the workplace information is registered or changed in the workplace information storage means;
a station information setting means for performing an acquisition and setting process of acquiring nearest station information from the address information included in the batch list for all the address information in the batch list, and setting the acquired nearest station information to the corresponding workplace information in the workplace information storage means;
a payment amount calculation means for calculating a payment amount of commuting expenses when the employee uses the route, based on route information stored in a route information storage means for storing route information related to the route used by the employee to travel between his/her home and the nearest station to his/her workplace, and fare information stored in a fare information storage means for storing fare information related to the route,
A payment calculation system characterized in that the workplace information in said workplace information storage means is available immediately after registration by said workplace information registration means, independently of execution of said acquisition and setting process. A first workplace information acquisition means for individually acquiring workplace information including address information of the workplace of each employee;
A second workplace information acquisition means for acquiring workplace information for a plurality of employees from a file in which workplace information including address information of the workplaces of the employees is registered;
a workplace information registration means for registering the workplace information acquired by the first workplace information acquisition means or the second workplace information acquisition means into a workplace information storage means;
a batch list registration means for registering the address information included in the workplace information in a batch list when the workplace information is registered or changed in the workplace information storage means;
a station information setting means for performing an acquisition and setting process of acquiring nearest station information from the address information included in the batch list for all the address information in the batch list, and setting the acquired nearest station information to the corresponding workplace information in the workplace information storage means;
a payment amount calculation means for calculating a payment amount of commuting expenses when the employee uses the route, based on route information stored in a route information storage means for storing route information related to the route used by the employee to travel between his/her home and the nearest station to his/her workplace, and fare information stored in a fare information storage means for storing fare information related to the route,
A payment calculation system characterized in that the workplace information in said workplace information storage means is available immediately after registration by said workplace information registration means, independently of execution of said acquisition and setting process. In any one of claims 4 and 5,
A payment calculation system characterized in that the batch list registration means does not register the address information contained in the registered or changed workplace information in the batch list if the nearest station information is included in the registered or changed workplace information.

Images