Payment calculation system

Abstract

To provide a payment calculation system desirable for accurately calculating a commuting expense payment amount when a fare revision or the like happens.SOLUTION: A batch server 150 acquires route information regarding a commuting route used by an employee for moving between an own home and a place of work from an employee-specific route information table 406, and acquires prorated payment information including a use date or a use period in which the employee uses the commuting route from an employee-specific prorated payment information table 410. After that, the batch server calculates an amount of commuting transportation expense to be paid when the employee uses the commuting route, on the basis of the acquired route information and prorated payment information, as well as fare information in a fare information table 420. In calculation of the commuting transportation expense regarding the use date or the use period in which the commuting route is used, a fare of an applicable date or an applicable period corresponding to the use date or the use period is applied.SELECTED DRAWING: Figure 17

Description

[Technical Field]

[0001] The present invention relates to a system for assisting in the calculation of payment amounts for payment recipients, and in particular to a payment calculation system suitable for accurately calculating the payment amount for transportation expenses when there is a fare revision or the like. [Background technology]

[0002] Conventionally, a technique for calculating the amount of commuting expenses to be paid is known, for example, as described in Patent Document 1.

[0003] The technology described in Patent Document 1, when a commuter route with the route direction type set to "round trip" is selected, multiplies the round trip fare by the number of pay days for the round trip, multiplies the one-way fare by the number of pay days for one way (outbound and return), and adds up the results of these multiplications to calculate the daily pay amount (same document

[0071] ). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7300136 Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the technology described in Patent Document 1, the daily travel expense payment amount is calculated by multiplying the fare by the number of paydays. Therefore, if a fare revision occurs during a payroll calculation period (e.g., one month), the revised new fare applies to all applicable days in the payroll calculation period. For example, if work days are April 1-5 and April 21-25, the number of paydays is 5 + 5 = 10 days, and the daily travel expense payment amount is calculated by multiplying the fare for the commute route by 10 days. However, if the fare revision occurs on April 15, the daily travel expense payment amount is calculated by multiplying the revised new fare for the commute route by 10 days. In this case, if the new fare increases, the employee will be overpaid, and if the new fare decreases, the employee will be underpaid, resulting in an inaccurate calculation of the daily travel expense payment amount.

[0006] Therefore, the present invention has been made with a focus on the unresolved issues of the conventional technology, and aims to provide a payment calculation system suitable for accurately calculating the amount of travel expenses to be paid when there is a fare revision, etc. [Means for solving the problem]

[0007] [Invention 1] In order to achieve the above object, the payment calculation system of Invention 1 comprises: route information acquisition means for acquiring route information regarding a route used by a payment recipient to travel between his or her home and workplace; usage history information acquisition means for acquiring usage history information including the dates or periods of use when the payment recipient used the route; and payment amount calculation means for calculating the payment amount of transportation expenses when the payment recipient uses the route, based on the route information acquired by the route information acquisition means, the usage history information acquired by the usage history information acquisition means, and transportation expense information in a transportation expense information storage means that stores transportation expense information regarding the route in association with the dates or periods of use of the transportation expenses, and the payment amount calculation means applies the transportation expenses for the applicable dates or periods corresponding to the dates or periods of use when the route is used.

[0008] With this configuration, the route information acquisition means acquires route information regarding the route used by the grant recipient to travel between their home and their workplace, and the usage history information acquisition means acquires usage history information including the date or period of use on which the grant recipient used the route.Then, the payment amount calculation means calculates the payment amount for transportation expenses when the grant recipient uses the route based on the acquired route information and usage history information, and the fare information in the fare information storage means.When calculating the transportation expenses for the date or period of use on which the route was used, the travel expenses for the applicable date or applicable period corresponding to the date or period of use are applied.

[0009] Here, the route information includes, for example, route information regarding the route when using public transportation, route information regarding the route when using a car, etc., or route information regarding the route when traveling on foot. The same applies below to the payment calculation system of Invention 3.

[0010] Furthermore, the travel expense information includes, for example, fare information regarding fares when using public transport, or fuel cost information regarding fuel costs such as gasoline when using a car, etc. The same applies below to the payment calculation system of Invention 3.

[0011] Furthermore, this 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 connected so that they can communicate with each other. In the latter case, each component may belong to any of the multiple devices, etc., as long as they are connected so that they can communicate with each other. The same applies to the payment calculation system of Invention 3 below.

[0012] [Invention 2] Furthermore, the payment calculation system of Invention 2 is the payment calculation system of Invention 1, wherein the payment amount calculation means (1) applies the travel expenses for which the first usage date or usage period is the applicable date or applicable period to calculate the travel expenses for the first usage date or usage period during the target period when the route is used, and (2) applies the travel expenses for which the second usage date or usage period is the applicable date or applicable period to calculate the travel expenses for the second usage date or usage period during the target period when the route different from the first usage date or usage period is used.

[0013] With this configuration, the payment amount calculation means applies (1) the travel expenses for the first use date or use period during the target period in which the route is used, to the calculation of travel expenses for which the first use date or use period is the applicable date or period, and (2) the travel expenses for the second use date or use period during the target period in which the route is used, to the calculation of travel expenses for which the second use date or use period is the applicable date or period.

[0014] [Invention 3] Furthermore, the payment calculation system of Invention 3 comprises a route information acquisition means for acquiring route information relating to a plurality of different routes used by a single recipient to travel between their home and their workplace; a usage history information acquisition means for acquiring usage history information including usage dates or usage periods when the single recipient used the plurality of routes; and a payment amount calculation means for calculating the payment amount of transportation expenses when the single recipient uses the plurality of routes, based on the route information acquired by the route information acquisition means, the usage history information acquired by the usage history information acquisition means, and transportation expense information in a transportation expense information storage means that stores transportation expense information relating to the routes in association with the applicable dates or applicable periods of the transportation expenses, and the payment amount calculation means applies the transportation expenses for the applicable dates or applicable periods corresponding to the usage dates or usage periods when the route was used, for each route.

[0015] With this configuration, the route information acquisition means acquires route information regarding multiple different routes used by a single grant recipient to travel between their home and their workplace, and the usage history information acquisition means acquires usage history information including the dates or periods of use on which the single grant recipient used the multiple routes.Then, the payment amount calculation means calculates the payment amount for transportation expenses when the single grant recipient uses multiple routes based on the acquired route information and usage history information, and the fare information in the fare information storage means.For each route used by a single grant recipient, the travel expenses for the applicable date or applicable period corresponding to the dates or periods of use are applied to calculate the transportation expenses for the dates or periods of use on which that route was used.

[0016] [Invention 4] Furthermore, the payment calculation system of Invention 4 is the payment calculation system of Invention 3, wherein the multiple routes include at least a first route and a second route, and the payment amount calculation means (1) applies, to the calculation of transportation expenses for a first usage date or usage period during the target period when the first route is used, the travel expenses for which the first usage date or usage period is the applicable date or period; (2) applies, to the calculation of transportation expenses for a second usage date or usage period during the target period when the first route, which is different from the first usage date or usage period, the travel expenses for which the second usage date or usage period is the applicable date or period; (3) applies, to the calculation of transportation expenses for a third usage date or usage period during the target period when the second route is used, the travel expenses for which the third usage date or usage period is the applicable date or period; and (4) applies, to the calculation of transportation expenses for a fourth usage date or usage period during the target period when the second route, which is different from the third usage date or usage period, the travel expenses for which the fourth usage date or usage period is the applicable date or period.

[0017] With this configuration, the payment amount calculation means (1) applies the travel expenses for the first use date or use period during the target period when the first route is used to the travel expenses for which the first use date or use period is the applicable date or period, (2) applies the travel expenses for the second use date or use period during the target period when the first route is used to the travel expenses for which the second use date or use period is the applicable date or period, (3) applies the travel expenses for the third use date or use period during the target period when the second route is used to the travel expenses for which the third use date or use period is the applicable date or period, and (4) applies the travel expenses for the fourth use date or use period during the target period when the second route is used to the travel expenses for which the fourth use date or use period is the applicable date or period.

[0018] [Invention 5] Furthermore, the payment calculation system of Invention 5 is the payment calculation system of either Invention 3 or 4, wherein the multiple routes are routes used by the payment recipient to travel between his / her home and each of multiple workplaces to which the payment recipient belongs.

[0019] With this configuration, the route information acquisition means acquires route information relating to the route used by one payee for each of a plurality of workplaces. [Effects of the Invention]

[0020] As explained above, according to the payment calculation system of Invention 1, it is possible to calculate the payment amount of transportation expenses relatively accurately when there is a fare revision or the like.

[0021] Furthermore, according to the payment calculation system of Invention 2, the amount of travel expenses to be paid can be calculated relatively accurately if there is a fare revision or the like between the first use date or period and the second use date or period within the target period.

[0022] Furthermore, according to the payment calculation system of Invention 3, the amount of travel expenses to be paid can be calculated relatively accurately when there is a fare revision or the like for some or all of multiple routes.

[0023] Furthermore, according to the payment calculation system of Invention 4, if there is a revision of the fare for the first route between the first date or period of use and the second date or period of use during the target period, or if there is a revision of the fare for the second route between the third date or period of use and the fourth date or period of use during the target period, the amount of travel expenses to be paid can be calculated relatively accurately.

[0024] Furthermore, according to the payment calculation system of Invention 5, it is possible to calculate the payment amount when paying travel expenses according to the route used to a payment recipient who belongs to multiple workplaces. [Brief explanation of the drawings]

[0025] [Figure 1] 1 is a block diagram showing a configuration of a network system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of a commute expense calculation server 100. [Figure 3] 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. [Figure 4] 4A and 4B are diagrams showing the data structures of an employee-by-daily-prorated-payment 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. FIG. [Figure 5] 10 is a diagram showing the data structure of a fare information table 420. FIG. [Figure 6] 10 is a flowchart showing a new commute route information application process. [Figure 7] FIG. 5 shows a commute route application screen 510. [Figure 8]FIG. 5 shows a commute route application screen 520. [Figure 9] FIG. 5 shows an employee information list screen 500. [Figure 10] 10 is a flowchart showing a payment information addition / modification process. [Figure 11] FIG. 8 is a diagram showing a route list screen 800. [Figure 12] FIG. 8 shows a payment information list screen 801. [Figure 13] 10 is a flowchart showing a payroll linkage basic data creation task registration process. [Figure 14] FIG. 10 is a diagram illustrating an example in which the amount of commuting expenses paid fluctuates. [Figure 15] 10 is a flowchart showing the execution process of the payroll linkage batch processing program. [Figure 16] FIG. 10 is a diagram showing the flow of execution processing of a batch processing main program by a task scheduler in the batch server 150. [Figure 17] This is a time chart showing the calculation of payment information and daily payment information related to fare revisions. DETAILED DESCRIPTION OF THE INVENTION

[0026] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will now be described with reference to Figures 1 to 17.

[0027] In this embodiment, "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.

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

[0029] [Hardware configuration of commuter travel expense calculation server 100] Next, the configuration of the commute expense calculation server 100 will be described.

[0030] FIG. 2 is a diagram showing the hardware configuration of the commute expense calculation server 100. As shown in FIG. As shown in Figure 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 that has the control program etc. of the CPU 30 stored in advance in a specified area, a RAM (Random Access Memory) 34 that stores data read from the ROM 32 etc. and the 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 and capable of sending and receiving data by a bus 39, which is a signal line for transferring data.

[0031] The I / F 38 is connected to external devices such as an input device 40 consisting of a keyboard, mouse, etc. that can input data as a human interface, a memory 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.

[0032] [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.

[0033] The batch server 150 and the database server 170 have the same hardware configuration as the commute expense calculation server 100 .

[0034] [Hardware configuration of employee terminal 200] The employee terminal 200 is composed of a terminal intended to be a stationary type like the commuter travel expense calculation server 100, or a portable 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 that stores 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 sending and receiving data by signal lines for data transfer.

[0035] The I / F is connected with various accessory devices, such as a touch panel display input device that can input data and display a screen based on an image signal, a storage device, a wireless communication device, a video camera, and the like.

[0036] [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.

[0037] 3(a) to 3(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. FIG.

[0038] 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 information on commuting routes for each employee, and an employee payment information table 408 for registering commuting transportation expense payment information for each employee.

[0039] As shown in Fig. 3(a), one record is registered for each combination of company ID and application start date in the company master table 400. Each record contains main information including company ID, company name, application control category, employee group category information, application start date, application end date, last update date, last updater, and other information.

[0040] Here, 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 classification is information that determines whether or not applications from employees can be accepted, and the employee group classification information is information that indicates classifications such as job type, office, and affiliation of paid employee groups and other employee groups.

[0041] 3(b), one record is registered for each combination of company ID, company ID, and application start date in the workplace master table 402. Each record contains main information including company ID, company ID, company name, company 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.

[0042] 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 set for each company that lists the business days and holidays of the workplace, 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 fuel unit price type 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 (premium), and diesel (diesel), as well as 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.

[0043] 3(c), one record is registered for each combination of company ID, employee ID, and application start date in the employee information master table 404. 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, workplace ID, workplace name, department ID, department name, employee classification, payment rule ID, password, authority level, map information, application start date, application end date, last update date, last updater, and other information.

[0044] Here, the department ID is information used to identify the department to which an 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 that distinguishes between full-time employees, part-time employees, etc., and the authority level is information that indicates one of personnel authority, superior authority, and employee authority. Personnel authority is the authority to use all functions related to commuting expense management in this system, superior authority is the authority to only apply for commuting routes and approve the application contents, 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 about the nearest station.

[0045] 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.

[0046] 3(d), one record is registered for each combination of company ID, employee ID, and route ID in the employee route information table 406. 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.

[0047] Here, the route direction type indicates the direction of the commuter means used, and can be outbound, return, or round trip. The route ID is information for identifying the commuter route, and is composed, for example, of a unique number for each commuter route (for example, numbers only, or a combination of letters and numbers). The commuter route is the route from home to work. For example, if the commuter means is the train, it would be "home → walk → nearest station (home) → intermediate station → nearest station (workplace) → walk → work." For example, if the commuter means is the car, it would be "home → car → work." The one-month amount, three-month amount, six-month amount, and 12-month amount are the amounts of commuting expenses for the first, third, sixth, and twelve months for the specified commuter means and route direction type, and the route reference date is the reference date on which the commuter route becomes valid.

[0048] When the destination or arrival point of a commute route is the workplace, the workplace ID and workplace name for the workplace that is the destination or arrival point are registered in association with the commute route in the employee-specific route information table 406. Also, since one employee may belong to multiple workplaces as described above, one or multiple pieces of 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.

[0049] 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, number of payment months, payment / deduction amount, self-payment amount, type, period, remarks, cancellation date, payment details, number of subscription months, number of subscriptions, payment amount, total payment amount, total self-payment amount, and other information.

[0050] Here, the payment ID is information for identifying 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 inclusion in salary, transfer to a bank account, or payment in kind (cash), and the number of months for payment and the number of regular months are either 1 month, 3 months, 6 months, or 12 months. The payment details are information indicating whether the payment is continuous, whether the payment cycle is fixed, and whether the fare revision process is applicable.

[0051] 4(a) to 4(e) are diagrams showing the data structures of an employee daily 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.

[0052] 4(a) to 4(e), the storage device of the database server 170 stores an employee-specific daily payment information table 410 that registers daily commuter expense payment information for each employee, and a department information table 412 that registers information on approvers and proxy applicants for each department. In addition, the storage device stores 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.

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

[0054] Here, 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 per diem 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 per diem payment period. The payment details information is information indicating whether or not the fare is subject to fare revision processing.

[0055] 4(b), one record is registered for each company and each department in the department information table 412. Each record contains main information including the company ID, department ID, approver ID, proxy applicant ID, application start date, application end date, last update date, last updater, and other information.

[0056] Here, the approver ID is the employee ID of an employee with supervisory authority who has the authority to approve commuting route applications for employees belonging to the department corresponding to the department ID, and the proxy applicant ID is the employee ID of an employee with authority to apply for commuting route applications on behalf of other employees belonging to the same department.

[0057] 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.

[0058] Here, the batch server user ID is information for identifying a user accessing 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). Also, the packet name is the packet name used in creating the payroll linkage basic data, and the actual cost packet name is the packet name used in processing actual costs.

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

[0060] Here, the tenant number is the number of the tenant executing batch processing such as the creation process of payroll linked 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.

[0061] 4(e), one record is registered for each combination of tenant number, batch processing ID, and task ID in the task scheduler information table 418. 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.

[0062] Here, the batch processing path is information indicating the physical file name (full path) of the batch processing main program that controls 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 prorated ID in the case of prorated payment information), etc.

[0063] 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.

[0064] As shown in FIG. 5, the fare information table 420 stores one record for each fare ID. Each record stores key 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 (hereinafter referred to as the "pre-revision fare"), and the fare associated with the record with the newer revision date can be identified as the revised fare (hereinafter referred to as the "revised fare"). The revision date of a record is the date on which the fare applies. The period from the older revision date to the day before the new revision date of the records before and after the revision is the applicable period of the pre-revision fare, and the period after the revision date of the newer record is the applicable period of the revised fare. For past revisions, the fare before revision, the fare after revision, the date and period of application of the fare can be identified from the fare and revision date of the record.

[0065] An employee's commuting expenses 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. This calculation is performed in the payroll linkage batch process (described later) in step S406.

[0066] Furthermore, when commuting expenses are paid on a pro rata basis, the employee's commuting expenses can be calculated by accumulating the fares for the commuting route based on the route information in the employee route information table 406, the pro rata payment information in the employee daily payment information table 410, and the fare information in the fare information table 420. When calculating commuting expenses, for each commuting route, the fare for the applicable date or applicable period corresponding to the date or period of use is applied to calculate the commuting expenses for that commuting route. This calculation is performed in the payroll linkage batch processing (described below) in step S406, and the following calculation methods (1) to (5) can be used, for example.

[0067] (1) If an employee uses one commuting route during the payroll calculation period and the fare for that commuting route is not revised during the payroll calculation period. For example, if employee A uses commuter route X from April 1 to 5, a record including employee A's employee ID, the route ID of commuter route X, and the pro rata payment period "April 1 to April 5" is registered in employee-specific daily payment information table 410. In this case, the fare for commuter route X is added up for the number of days from April 1 to 5 (five days) to calculate commuter expenses. For example, if commuter route X is used one way (usage direction type = one way) on April 1 and 2, and commuter route X is used round trip (usage direction type = round trip) on April 3 to 5, commuter expenses are calculated by adding up the one-way fare for commuter route X for two days and the round trip fare for commuter route X for three days. The same applies below, where fares are added up for the number of days, taking into account both one-way and round trip use.

[0068] (2) If an employee uses only one commuting route during the payroll calculation period and the fare for that commuting route is revised during the payroll calculation period. For example, if employee A uses commuter route X from 4 / 1 to 5, and the fare for commuter route X is revised on 4 / 3, a record similar to (1) will be registered in employee-specific daily payment information table 410, and the pre-revision fare and post-revision fare for commuter route X will be registered in fare information table 420. In this case, the commuter transportation expenses will be calculated by adding together the amount obtained by accumulating the pre-revision fare for commuter route X for the number of days from 4 / 1 to 4 / 2 (2 days) and the amount obtained by accumulating the post-revision fare for commuter route X for the number of days from 4 / 3 to 4 / 5 (3 days).

[0069] (3) If an employee uses multiple commuting routes during the payroll calculation period and the fares for all of those routes are not revised during the payroll calculation period. For example, if employee A uses commute route X from April 1 to 5 and commute route Y from April 21 to 25, the employee-specific pro rata payment information table 410 will contain (1) a record including employee A's employee ID, the route ID of commute route X, and the pro rata payment period "April 1 to 5," and (2) a record including employee A's employee ID, the route ID of commute route Y, and the pro rata payment period "April 21 to 25." Commuter routes X and Y may be employed at the same or different workplaces. In this case, the commuter transportation expenses are calculated by adding together the fare for commute route X for the number of days from April 1 to 5 (five days) and the fare for commute route Y for the number of days from April 21 to 25 (five days).

[0070] (4) If an employee uses multiple commuting routes during the payroll calculation period and the fares for some of those routes are revised during the payroll calculation period. For example, if employee A uses commuter route X from 4 / 1 to 5 and commuter route Y from 4 / 21 to 25, and the fare for commuter route X is revised on 4 / 3, a record similar to (3) will be registered in employee-specific daily payment information table 410, and the pre-revision and post-revision fares for commuter route X will be registered in fare information table 420. In this case, the commuter transportation expenses are calculated by adding together the amount obtained by accumulating the pre-revision fare for commuter route X for the number of days from 4 / 1 to 4 / 2 (2 days), the amount obtained by accumulating the post-revision fare for commuter route X for the number of days from 4 / 3 to 4 / 5 (3 days), and the amount obtained by accumulating the fare for commuter route Y for the number of days from 4 / 21 to 4 / 25 (5 days).

[0071] (5) If an employee uses multiple commuting routes during the payroll calculation period and the fares for all of those routes are revised during the payroll calculation period. For example, if employee A uses commuter route X from April 1 to 5 and commuter route Y from April 21 to 25, and the fare for commuter route X is revised on April 3 and the fare for commuter route Y is revised on April 23, a record similar to (3) will be registered in employee-specific daily payment information table 410, and the pre-revision and post-revision fares for commuter routes X and Y will be registered in fare information table 420. In this case, the commuter transportation expenses are calculated by adding together the amount obtained by accumulating the pre-revision fare for commuter route X for the number of days from April 1 to 2 (2 days), the amount obtained by accumulating the post-revision fare for commuter route X for the number of days from April 3 to 5 (3 days), the amount obtained by accumulating the pre-revision fare for commuter route Y for the number of days from April 21 to 22 (2 days), and the amount obtained by accumulating the post-revision fare for commuter route Y for the number of days from April 23 to 25 (3 days).

[0072] Although not shown, the storage device of database server 170 stores, in addition to tables 400 to 418, tables in which various definition data for calculating commuter travel expenses are registered, tables in which various basic data for linking commuter travel expenses with salary are registered, etc. Specific examples of basic data tables include a salary basic data table, a tax basic data table, a social insurance basic data table, and an employment insurance basic data table.

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

[0074] [Operation] Next, the operation of this embodiment will be described. [New commute route information application process] First, we will explain the operation of commute 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 expense calculation server 100 communicating with database server 170, but for the sake of simplicity, the following explanation will be given assuming that commute expense calculation server 100 accesses tables 400 to 418.

[0075] FIG. 6 is a flowchart showing the process for applying for new commute route information. CPU 30 is made up of an MPU (Micro-Processing Unit) or the like, and starts a predetermined program stored in a predetermined area of ​​ROM 32, and executes the new commute route information application process shown in the flowchart of FIG. 6 in accordance with that program.

[0076] When the new commute route information application process is executed by the CPU 30, as shown in FIG. 6, it first proceeds to step S100 to determine whether 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), it proceeds to step S102.

[0077] Here, new applications for commute route information are made, for example, when a new employee registers commute route information for the first time, when an employee moves and their commute route changes, or when an employee adds or changes their workplace.

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

[0079] FIG. 7 is a diagram showing the commute route application screen 510. In the application information input process, first, the commute route application screen 510 is displayed, as shown in Figure 7. On the commute route application screen 510, the applicant (employee) enters the application start date, commuting means, transportation company, reason for application, employee home address, company name, workplace, and route direction type, etc.

[0080] 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.

[0081] For the place of employment, the place of employment corresponding to the applicant's employee ID is retrieved 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.

[0082] The route direction type can be selected from one of three options: "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 for the outbound and return routes are different, or if you are using both the outbound and return routes.

[0083] FIG. 8 is a diagram showing commute route application screen 520. The applicant enters other commute route information and clicks the "Next" button 53, which displays the commute route application screen 520 as shown in Figure 8. On the commute 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.

[0084] 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 retrieved 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, all of the 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.

[0085] For the nearest station to the workplace, the nearest station to the workplace corresponding to the applicant's employee ID for the workplace selected on the commute route application screen 510 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, all of the 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.

[0086] The applicant enters other commute route information and clicks the "Next" button 58, which displays candidate commute routes between the nearest station to the employee's home and the nearest station to the workplace. 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 the selected commute route as their commute route.

[0087] Next, the process proceeds to step S104, where it is determined whether or not a registration request has been received from the employee terminal 200. If it is determined that a registration request has been received (YES), the process proceeds to step S106.

[0088] In step S106, information about 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.

[0089] Here, the department ID is identification information exclusive to the workflow, and it is possible to set the same department ID for employees across multiple different real organizations. 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 the real organizations are registered using the employee group ID in the employee information master table 404.

[0090] For example, suppose that employees A and F are employees with supervisor authority and are given approval authority in the workflow. Employee E is a general employee and is given proxy application authority. Here, approval authority is the authority to approve the application content 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 submit applications on behalf of other employees. In other words, employees A and F who have approval authority can approve applications from employees B to E and G to I who belong to the same department B1. Employee E who has proxy application authority can process applications on behalf of employees A to D and F to I who belong to the same department B1.

[0091] This allows approval processing and proxy application processing to be performed across different real organizations, even if the organizations are different, 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.

[0092] Next, the process proceeds to step S108, where an approval route is constructed based on the acquired approval destination information, and an approval request for the application information is then sent to each approver at the route destination based on the constructed approval route.

[0093] For example, if a regular employee (other than A and F) belonging to department B1 applies for a commuter route, approval will be given to both employees A and F, and after approval, the route will be inspected by an employee with personnel authority (hereinafter referred to as "human resources employee"), such as the three human resources employees J to L in charge of department B1. Note that human resources employees have the authority to inspect any department.

[0094] In other words, the approval route is first "employees A and F," and after employee A approves first, it becomes "employee A → HR employees J-L." On the other hand, after employee F approves first, it becomes "employee F → HR employees J-L." In other words, approval only needs to be given by either employee A or F, and approval by both is not required. Furthermore, inspection after approval will be carried out by the three HR employees J-L in charge of department B1, and inspection only needs to be carried out by any one of HR employees J-L.

[0095] In this way, approval and inspection are carried out and the application is permitted, and the application information is registered in employee-specific route information table 406, employee-specific payment information table 408, and 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 employee-specific payment information table 408 or employee-specific daily payment information table 410, causing a change in the amount of commuting expenses paid.

[0096] When the process of step S108 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 S104 that a registration request has not been received (NO), the process proceeds to step S110 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.

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

[0098] On the other hand, if it is determined in step S100 that a new application request has not been received (NO), the process waits in step S100 until a new application request is received.

[0099] [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 rate payment information table 410 will be described.

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

[0101] The payment information addition / modification process is a process that is executed on the route list screen 800 that is displayed after selecting an employee to add or modify 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.

[0102] Fig. 10 is a flowchart showing the payment information addition / modification process, Fig. 11 is a diagram showing a route list screen 800, Fig. 12 is a diagram showing a payment information list screen 801.

[0103] When the payment information addition / modification process is executed by the CPU 30, as shown in FIG. 10, the process first proceeds to step S200.

[0104] In step S200, it is determined based on information from the employee terminal 200 whether the commute route edit button 80 has been selected for a commute route selected from the list of commute routes for the selected employee displayed on the route list screen 800. If it is determined that the commute route edit button 80 has been selected (YES), the screen information for the payment information list screen 801 is sent to the employee terminal 200. In other words, if the commute route edit button 80 is selected on the route list screen 800 shown in FIG. 11, the payment information list screen 801 shown in FIG. 12 is displayed on the display device of the employee terminal 200.

[0105] Next, the process proceeds to step S202, where it is determined based on information from employee terminal 200 whether or not the Add button 82 has been selected on payment information list screen 801. If it is determined that the Add button 82 has been selected (YES), screen information for the payment information setting screen is sent to employee terminal 200. That is, if the Modify button 83 is selected with pro rata payment information selected on payment information list screen 801 shown in FIG. 12, a pro rata payment information setting screen (not shown) is displayed on the display screen of 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 setting 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 setting of both regular and pro rata payment information is displayed.

[0106] Next, the process proceeds to step S204, where the payment information addition process is executed. As the payment information addition process, the process of adding payment information based on the information entered by the human resources employee on the daily pro rata payment information setting screen will be described.

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

[0108] Here, the type of direction of travel is selected as "round trip" if the same commuter route was used on the outbound and return journeys, and as "one way" if different commuter routes were used on the outbound and return journeys or if only one-way travel was used. This allows either "round trip" or "one way" to be set in common for each date in the period covered by the pro rata payment. Furthermore, if there are days when the same commuter route was used only one way and days when it was used for both a round trip and a return journey, the type of direction of travel can be set individually for each date after selecting either "one way" or "round trip."

[0109] Furthermore, after entering the prorated payment information, if the OK button (not shown) displayed on the prorated payment information setting screen is selected, it is determined that the entry of the prorated payment information is complete, and the screen returns to the payment information list screen 801 shown in Fig. 12. Then, the newly entered prorated payment information is added to the list on the payment information list screen 801, and if the Confirm button at the bottom right is selected, the new prorated payment information is added to the employee prorated payment information table 410. In other words, the addition of new prorated payment information causes a change in the amount of commuting expenses paid.

[0110] When the process in step S204 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 S202 that the Add button 82 has not been selected (NO), the process proceeds to step S206, 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 sent 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. 12, the pro rata payment information setting screen is displayed on the display screen of the employee terminal 200 with the information already entered.

[0111] Next, the process proceeds to step S208, where the payment information correction process is executed. The payment information correction process is a process for correcting information that has already been entered on the pro rata payment information setting screen, and is similar to the payment information addition process except for whether new information is entered or already entered information is changed (corrected), so a description thereof will be 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 S208 is completed, the series of processes ends and the process returns to the original process.

[0112] On the other hand, if it is determined in step S206 that the Modify button 83 has not been selected (NO), the process proceeds to step S210, where it is determined whether or not any other button has been selected, excluding the Add button 82 and the Modify button 83. If it is determined that any other button has been selected (YES), the process transmits screen information of the screen corresponding to the other button to the employee terminal 200, and proceeds to step S212.

[0113] In step S212, the process corresponding to the selected button is executed. As shown in FIG. 12, the other buttons include a cancel button, a delete button, a confirm button, and a cancel button. If the cancel button is selected, the process to cancel the commuter pass is executed, if the delete button is selected, the process to delete the selected payment information is executed, and if the cancel button is selected, the process to cancel the commuter route modification and return to the route list screen 800 is executed. When the process in step S212 is completed, the series of processes is terminated and the original process is resumed.

[0114] On the other hand, if it is determined in step S210 that no other button has been selected (NO), the process proceeds to step S202.

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

[0116] [Payment information addition / modification processing] Regular employees can also use the same functions as the payment information addition and modification process described above. Regular employees can add their own payment information. However, the difference is that additions made by regular employees are finalized after obtaining approval from the approving authority.

[0117] [Payroll link basic data creation task registration process] Next, the operation of the commute expense calculation server 100 when a payroll 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.

[0118] FIG. 13 is a flowchart showing the payroll 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. 13, the process first proceeds to step S300.

[0119] In step S300, it is determined whether or not a change has occurred in the payment information in the employee-specific payment information table 408 or the employee-specific daily prorated payment information table 410. If it is determined that a change has occurred in the payment information (YES), the process proceeds to step S302.

[0120] FIG. 14 is a diagram illustrating an example in which the amount of commuter travel expenses paid fluctuates. As shown in Figure 14, when an employee applies for a new commute route and this application is approved by the supervisor and the Human Resources Department, payment information according to the newly applied commute route is generated and registered in 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 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.

[0121] In addition, when monthly processing by a human resources employee involves calculating the daily payment of commuting expenses, for example, fluctuations occur in the registered details of the employee-specific daily payment information table 410, causing a change in the payment amount, and this fluctuation is determined to be a change in the payment amount.

[0122] Furthermore, if a fare revision results in a difference between the amount already paid and the actual amount, the payment of that difference will result in a change in the payment amount in the employee-specific payment information table 408 or the employee-specific daily prorated payment information table 410, and this change is therefore determined to be a change in the payment amount. After the registration of the daily prorated payment amount and the adjustment process for the difference due to the fare revision are completed, the payroll data is output to the payroll linkage system, and then the process of creating the next payroll linkage basic data is performed in advance. If a change occurs in the payroll linkage basic data created in advance due to a daily prorated payment or fare revision, this will also result in a change in the payment amount in the employee-specific payment information table 408 or the employee-specific daily prorated payment information table 410, and therefore a change in the payment amount is determined to have occurred. A change in the payment amount is determined, for example, by determining whether a revision date has been set in the fare information table 420 since the completion of the salary payment calculation process for the previous commuter travel expense payment month.

[0123] In step S302, 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 processing, the company ID, the ID of the payroll linkage batch processing program (hereinafter referred to as the "payroll linkage batch processing ID"), and the payment ID of the payment information in which it was determined in step S300 that a change in the payment amount has occurred.

[0124] The payment ID of the payment information that has been subject to a 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 S322.

[0125] The payment ID of the pro rata payment information that has been subject to a fare revision among the pro rata payment information set as the target for fare revision processing (hereinafter referred to as "pro rata payment information related to a 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 and pro rata ID of the pro rata payment information for which commuting expenses have been calculated using the identified route information are obtained from the employee-specific pro rata payment information table 410. Parameter information including the obtained payment ID is registered in the task scheduler information table 418 in step S322.

[0126] Next, the process proceeds to step S304, 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 controls various batch processes such as payroll linked batch processing, and the batch processing that is executed is controlled by the contents of parameters that are set when the batch processing main program is executed.

[0127] Next, the process proceeds to step S306, 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 S308.

[0128] In step S308, based on the information acquired in step S306, the user logs in to the batch server 150 and establishes a session, after which the process proceeds to step S310.

[0129] In step S310, the task scheduler creates a task execution condition. The task execution condition is created so that the task will be executed after a predetermined time (hereinafter referred to as the "start delay time") that takes into account communication lag with the batch server 150. If the system times of the commute 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 commute 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 communication lag into account.

[0130] Furthermore, the commute expense calculation server 100 and the batch server 150 have a task scheduler installed in their operating systems (OS).

[0131] A task scheduler is a computer program execution control system that starts and stops programs based on schedules and conditions specified by the user, and records and reports the execution status and results. This allows specific commands and executable files on the OS to be started and stopped automatically based on a schedule.

[0132] Next, the process proceeds to step S312, where a task action is created. The task action is composed 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 linkage batch processing ID, and task ID. Here, the task ID is information for identifying the task to be registered in the task scheduler.

[0133] Next, proceed to step S314 and create a deletion setting for the action after the task is completed. Here, the process of creating basic payroll linked 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 performed repeatedly on a regular basis, so create a setting to delete the action after the task is completed. Specifically, set the time until deletion if the task is not scheduled to be executed again.

[0134] Next, the process proceeds to step S316, where an instance of the task scheduler is created. That is, an instance of the batch processing main program (payroll linked batch processing) to be executed by the task scheduler is created. That is, the batch processing main program, execution parameters, etc. are deployed on the main memory of the batch server 150, and made ready for processing and execution.

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

[0136] Furthermore, in the task scheduler, processing is executed in units of instances, and multiple instances can be executed in parallel.

[0137] Next, the process proceeds to step S318, where the various information created in steps S310 to S316 is registered in the task scheduler. That is, information such as the tenant number, company ID, payroll linkage batch processing ID, task schedule (year, month, day, hour, minute), and execution user is registered.

[0138] Next, the process proceeds to step S320, where the session with the batch server 150 is discarded, and the process proceeds to step S322.

[0139] In step S322, 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 S322 ends, the series of processes ends and the process returns to the original processing.

[0140] The processing of steps S308 to S320 is automatically performed using, for example, a command line interface installed in the OS (for example, "Windows PowerShell (registered trademark)" when the OS is Windows).

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

[0142] [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.

[0143] 15 is a flowchart showing the execution process of the payroll linked batch processing program. FIG. 16 is a diagram showing the flow of the execution process of the batch processing main program by the task scheduler in the batch server 150.

[0144] The CPU of the batch server 150 starts a predetermined program stored in a predetermined area of ​​the ROM, and executes the payroll linkage batch processing program execution process shown in the flowchart of Figure 15 in accordance with the program.

[0145] When the payroll linked batch processing program execution process is executed in the CPU, it first proceeds to step S400 as shown in FIG.

[0146] In step S400, it is determined whether or not it is time to execute the registered task, and if it is determined that the execution time has arrived (YES), the process proceeds to step S402.

[0147] In this case, as shown in FIG. 16, 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.

[0148] In step S402, the execution parameters registered in the task scheduler are checked. Here, the execution parameters are the tenant number, the payroll linkage batch process ID, and the task ID.

[0149] Next, the process proceeds to step S404, where parameter information required for executing the task corresponding to the execution parameters checked in step S402 is obtained from the task scheduler information table 418. Specifically, as shown in Fig. 16, parameter information corresponding to the tenant number, batch processing ID, and task ID of the task to be executed is obtained as parameter information.

[0150] Next, the process proceeds to step S406, 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 S404, 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.

[0151] When the payroll linkage batch processing program is executed, as shown in Figure 16, 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 S404, and the calculated values ​​of the various basic data registered in the various basic data tables are updated to the recalculated data.

[0152] Here, the salary payment calculation process that calculates the amount of commuting expenses includes a first calculation process that calculates the amount of commuting expenses paid to employees and the amount of expenses that varies depending on the commuting expenses. The salary payment calculation process also includes a second calculation process that calculates other payment amounts (e.g., overtime pay). 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 processes that are performed, for example, in another salary calculation system. The first calculation process is executed in the salary linkage batch process.

[0153] The payroll link batch process does not calculate the amount of commuter travel expenses to be paid in the current month all at once, but rather executes the calculations in chronological order for each payment information unit. For example, when a new or changed commute route application is made, the payment amount for that application is calculated at that time, and when a fare revision is made, the payment amount for the fare revision is calculated at that time.

[0154] Furthermore, in the payroll linkage batch processing, the amount of commuter travel expenses paid is calculated at predetermined intervals (for each month in which commuter travel expenses are paid (for example, every month, every three months, etc.)). Therefore, the payroll linkage batch processing program is executed within the period from the completion of the payroll payment calculation process for the previous commuter travel expenses payment month until the execution timing of the payroll payment calculation process for the next commuter travel expenses payment month. Here, the "execution timing of the payroll payment calculation process" refers to the timing when the second and third calculation processes of the payroll payment calculation process are executed, for example, as monthly batch processes. Furthermore, in the payroll payment calculation process for the commuter travel expenses payment month, the uncalculated calculation processes of the first, second, and third calculation processes are executed.

[0155] FIG. 17 is a time chart showing a case where payment information and daily pro rata payment information relating to a fare revision are calculated.

[0156] In the example of Figure 17, if a fare revision occurs after the completion of the previous payroll calculation process, and this fare revision causes a change in the amount of commuting expenses paid to employees A and C, a payroll linkage batch process is executed for employee A's pay information and employee C's pay information. If another fare revision occurs thereafter, and this fare revision causes a change in the amount of commuting expenses paid to employees B and D, a payroll linkage batch process is executed for employee B's pay information and employee D's pay information. After that, when it is time to execute the next payroll calculation process, the second calculation process and the third calculation process are executed. In this way, when there is a fare revision, the pay information for the relevant employee is recalculated, rather than the pay information for all employees being recalculated each time.

[0157] Next, the process proceeds to step S408, where the task scheduler information after the task completion is deleted from the task scheduler information table 418, the series of processes is terminated, and the process returns to the original process.

[0158] On the other hand, if it is determined in step S400 that the execution time for the task has not yet arrived (NO), the process waits in step S400 until the execution time arrives.

[0159] [Effects of the embodiment] Next, the effects of this embodiment will be described. In this embodiment, route information regarding the commute route used by the employee to travel between their home and workplace, and daily payment information including the date or period of use (period eligible for daily payment) when the employee used the commute route are obtained, and the amount of commute expenses to be paid when the employee uses the commute route is calculated based on the obtained route information and daily payment information, as well as the fare information in fare information table 420, by applying the fare for the applicable date or applicable period corresponding to the date or period of use.

[0160] This allows for a relatively accurate calculation of the amount of commuting expenses paid in the event of a fare revision.

[0161] Furthermore, in this embodiment, (1) when calculating commuter expenses for the first use day or use period during the payroll calculation period when a commuter route is used, the fare for which the first use day or use period is the applicable date or applicable period is applied, and (2) when calculating commuter expenses for the second use day or use period during the payroll calculation period when a commuter route different from the first use day or use period is used, the fare for which the second use day or use period is the applicable date or applicable period is applied.

[0162] This allows for a relatively accurate calculation of the amount of commuting expenses paid if there is a fare revision between the first use date or period and the second use date or period during the payroll calculation period.

[0163] Furthermore, in this embodiment, route information regarding multiple different commuting routes used by an employee to travel between their home and workplace, and daily payment information including the dates or periods of use (periods eligible for daily payment) when the employee used multiple commuting routes are obtained, and based on the obtained route information and daily payment information, as well as the fare information in fare information table 420, the commuter transportation expenses for each commuting route used by the employee are calculated for the dates or periods of use when that commuting route was used, by applying the fare for the applicable date or applicable period corresponding to that date or period of use, thereby calculating the amount of commuter transportation expenses to be paid when the employee uses those commuting routes.

[0164] This allows for relatively accurate calculation of the amount of commuting expenses paid when fares are revised for some or all of multiple commuting routes.

[0165] Furthermore, in this embodiment, (1) when calculating commuter expenses for the first use day or use period during the payroll calculation period when the first commuter route is used, the fare for which the first use day or use period is the applicable date or period is applied; (2) when calculating commuter expenses for the second use day or use period during the payroll calculation period when the first commuter route, which is different from the first use day or use period, is applied, the fare for which the second use day or use period is the applicable date or period is applied; (3) when calculating commuter expenses for the third use day or use period during the payroll calculation period when the second commuter route is used, the fare for which the third use day or use period is the applicable date or period is applied; and (4) when calculating commuter expenses for the fourth use day or use period during the payroll calculation period when the second commuter route, which is different from the third use day or use period, is applied, the fare for which the fourth use day or use period is the applicable date or period is applied.

[0166] This allows for a relatively accurate calculation of the amount of commuting expenses to be paid if the fare for the first commuting route is revised between the first use date or period and the second use date or period during the payroll calculation period, or if the fare for the second commuting route is revised between the third use date or period and the fourth use date or period during the payroll calculation period.

[0167] Furthermore, in this embodiment, the multiple commuting routes are the commuting routes used by an employee to travel between his / her home and each of the multiple workplaces to which the employee belongs.

[0168] This makes it possible to calculate the amount of commuting expenses paid to employees who work at multiple workplaces according to the commuting route they use.

[0169] 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.

[0170] This allows the payroll link batch processing to be executed in a time-series distributed manner when there is a fare revision, thereby reducing the load on the payroll calculation processing. In other words, when there is a fare revision, the pay amount related to the fare revision can be recalculated, which reduces the load on the payroll calculation processing compared to calculating all employees' amounts at once.

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

[0172] This allows the payroll link batch process to be executed in a time-series distributed manner when the amount of commuting expenses changes, thereby reducing the load on the payroll calculation process. In other words, when the amount of commuting expenses changes, the amount of commuting expenses for the employee related to the change or the amount of expenses that changes depending on the commuting expenses can be recalculated, thereby reducing the load on the payroll calculation process compared to calculating the amounts for all employees at once.

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

[0174] This reduces the possibility that the batch server 150 will be unable to execute payroll linkage batch processing if a communication lag occurs.

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

[0176] Furthermore, it is determined that a change has occurred in the amount of commuting expenses paid when new pro rata payment information is registered in the employee-specific pro rata payment information table 410. Furthermore, it is determined that a change has occurred in the amount of commuting expenses paid when there is a change in the existing pro rata payment information registered in the employee-specific pro rata payment information table 410 due to monthly processing by a personnel employee.

[0177] 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.

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

[0179] This allows distributed processing even when there is a change in the amount of commuter travel expenses paid for reasons other than the commute route application, such as pro rata payment or fare revisions, and further reduces the load on salary payment calculation processing. Also, because it is determined that there has been a change in the amount of commuter travel expenses paid when payment information or pro rata payment information is registered in employee-specific payment information table 408 or employee-specific pro rata payment information table 410, it is possible to more reliably determine whether the amount of payment has changed.

[0180] [Correspondence] In this embodiment, the storage device of the database server 170 corresponds to the travel expense information storage means of invention 1 or 3, step S204 corresponds to the route information acquisition means of invention 1 or 3 or the usage history information acquisition means of invention 1 or 3, and step S406 corresponds to the payment amount calculation means of inventions 1 to 4.

[0181] [Modification] In the above embodiment and its modifications, the fare of the means of transport is used to calculate the commuting expenses, but this is not limiting and fuel costs such as gasoline costs can also be used. For example, the following configuration can be adopted.

[0182] The storage device of database server 170 stores a fuel unit price master table that registers information on the fuel unit price of cars and motorcycles used for commuting, and a fuel efficiency master table that registers information on the fuel efficiency of cars and motorcycles used for commuting. Based on the route information, daily payment information, and fuel cost information in these master tables, the system calculates the commuting expenses for the date or period of use when the commuting route is used by applying the fuel cost for the applicable date or applicable period corresponding to that date or period of use, thereby calculating the commuting expenses paid when an employee uses the commuting route. Publicly known technology (Patent Publication No. 7291920, Joint Publication

[0078]

[0079] ) can be used to calculate commuting expenses using fuel costs.

[0183] Furthermore, in the above embodiment and its variations, the commuter transportation cost is calculated by accumulating the fare for the commute route for the number of days of use (i.e., the commuter transportation cost is calculated by adding up the fare applicable to each day of use), but this is not limited to this. If the fare applicable to a certain period of use is the same, the commuter transportation cost can be calculated by multiplying the fare applicable to that period of use by the number of days in that period of use. In addition, any calculation method can be used to calculate the commuter transportation cost for the days or periods of use when a commuter route is used, as long as the fare for the applicable day or period corresponding to that day or period of use can be applied.

[0184] Furthermore, in the above embodiment and its variations, the amount of commuting expenses paid was calculated based on the daily payment information (daily payment period, number of payment days, etc.) in the employee-specific daily payment information table 410 as information regarding the employee's actual use of the commuting route, but this is not limited to this, and the amount of commuting expenses paid can also be calculated based on the payment information (payment period, number of payment months, etc.) in the employee-specific payment information table 408.

[0185] In the above embodiment and its variations, in the application information input process in step S102, one of multiple workplaces to which the employee belongs is selected, but this is not limiting, and a configuration in which one of multiple workplaces set for the company to which the employee belongs can be selected may be adopted. In this case, workplaces to which the employee does not belong may be included as candidates.

[0186] In addition, in the above embodiment and its variations, the fare information in the fare information table 420 is used to identify the payment information that has been subject to a fare revision, but this is not limiting, and other information related to the fare revision, such as section information related to the section where the fare revision occurred, route information related to the commuter route where the fare revision occurred, or other revision information related to 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.

[0187] In addition, in the above embodiment and its variations, the payment amount related to the fare revision is recalculated when a fare revision occurs. However, this is not limited to this. A configuration can be adopted in which the payment amount of commuter transportation expenses that should be paid in the current month and that are related to the fare revision are 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 payroll linkage batch process is executed to calculate the payment amount for the identified payment. The payment that is subject to the fare revision can be identified, for example, by identifying the commuter route that is subject to the fare revision or by identifying the employees who use the commuter route that is subject to the fare revision.

[0188] Furthermore, in the above embodiment and its variations, it is determined that a change has occurred in the amount of commuting expenses paid when new payment information or pro rata payment information is registered in the employee-specific payment information table 408 or the employee-specific daily payment information table 410, or when that payment information or daily pro rata payment information is changed, but this is not the only possible configuration. For example, it may be configured to determine that a change has occurred in the amount of commuting expenses when a commuting route is applied for and the application is approved.

[0189] Furthermore, in the above embodiment and its modifications, the system is realized as a network system, but the present invention is not limited to this and can be realized as a single device or application.

[0190] Furthermore, in the above embodiment and its variations, 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 this. For example, it is 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.

[0191] Furthermore, in the above embodiment and its modifications, the case where the present invention is applied to a network system consisting of the Internet 199 has been described, but the present invention is not limited to this, and may be applied, for example, to a so-called intranet that communicates using the same method as the Internet 199. Of course, the present invention is not limited to a network that communicates using the same method as the Internet 199, and may be applied to a network of any communication method.

[0192] Furthermore, in the above-described embodiments and their variations, the processes shown in the flowcharts of Figures 6, 10, 13 and 15 are all described as being executed by executing a program that is pre-stored in ROM, but this is not limiting, and the program showing these procedures may be read into RAM from a storage medium on which the program is stored and executed.

[0193] In the above embodiment and its modifications, the present invention is applied to cases such as calculating employee commuting expenses, but it is not limited to this and can be applied to other cases within the scope of the present invention. For example, the present invention can be applied to cases such as calculating business trip expenses and other transportation expenses, calculating transportation expenses paid to persons other than employees, and calculating transportation expenses for using routes other than the commuting route. [Explanation of symbols]

[0194] 100...commuter 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

1. route information acquisition means for acquiring route information regarding the route used by the recipient to travel between his / her home and workplace; a usage history information acquisition means for acquiring usage history information including the date or period of use when the grant recipient used the route; a payment amount calculation means for calculating a payment amount of transportation expenses when the grantee uses the route, based on the route information acquired by the route information acquisition means, the usage history information acquired by the usage history information acquisition means, and travel expense information in a travel expense information storage means that stores travel expense information related to the route in association with the applicable date or applicable period of the travel expense, The payment calculation system is characterized in that the payment amount calculation means applies the travel expenses for the applicable date or applicable period corresponding to the date or period of use when calculating the travel expenses for the date or period of use using the route.

2. In claim 1, The payment calculation system is characterized in that the payment amount calculation means (1) applies travel expenses for which the first usage date or usage period is the applicable date or applicable period when calculating travel expenses for a first usage date or usage period during the target period in which the route is used, and (2) applies travel expenses for which the second usage date or usage period is the applicable date or applicable period when calculating travel expenses for a second usage date or usage period during the target period in which the route, which is different from the first usage date or usage period, is used.

3. a route information acquisition means for acquiring route information relating to a plurality of different routes used by a single recipient to travel between his / her home and workplace; a usage history information acquisition means for acquiring usage history information including a usage date or a usage period in which the one grant recipient uses the plurality of routes; a payment amount calculation means for calculating a payment amount for transportation expenses when the one grant recipient uses a plurality of the routes, based on the route information acquired by the route information acquisition means, the usage history information acquired by the usage history information acquisition means, and travel expense information in a travel expense information storage means that stores travel expense information related to the route in association with the applicable date or applicable period of the travel expense, The payment calculation system is characterized in that the payment amount calculation means applies the travel expenses for the applicable date or applicable period corresponding to the date or period of use when calculating the travel expenses for each route related to the date or period of use when the route was used.

4. In claim 3, the plurality of paths include at least a first path and a second path; The payment calculation system is characterized in that: (1) when calculating transportation expenses for a first usage date or usage period during the target period when the first route is used, the payment calculation means applies travel expenses for which the first usage date or usage period is the applicable date or period; (2) when calculating transportation expenses for a second usage date or usage period during the target period when the first route, which is different from the first usage date or usage period, the payment calculation means applies travel expenses for which the second usage date or usage period is the applicable date or period; (3) when calculating transportation expenses for a third usage date or usage period during the target period when the second route is used, the payment calculation means applies travel expenses for which the third usage date or usage period is the applicable date or period; and (4) when calculating transportation expenses for a fourth usage date or usage period during the target period when the second route, which is different from the third usage date or usage period, the payment calculation means applies travel expenses for which the fourth usage date or usage period is the applicable date or period.

5. In any one of claims 3 and 4, A payment calculation system characterized in that the multiple routes are routes used by the payment recipient to travel between his / her home and each of multiple workplaces to which the payment recipient belongs.

Images