Payment calculation system

Abstract

This system provides a suitable payment calculation method for calculating the amount of transportation expenses paid to employees with multiple locations, based on the commuting route they use. [Solution] The commuter expense calculation server 100 acquires route information for each of the multiple locations, regarding the commute routes used for travel between the workplace and that location, and acquires usage information regarding the actual use of multiple commute routes by the employee. Based on the acquired route information, usage information, and fare information in the fare information table 416, the server calculates the amount of commuter expense payable when an employee uses multiple commute routes. This makes it possible to apply for and calculate commuter expenses even for commutes from locations other than one's home (such as family homes, temporary residences, or residences at assignment locations), and allows for the calculation of the amount of commuter expense payable to employees with multiple locations, based on the commute routes used.

Description

Technical Field

[0001] The present invention relates to a system for assisting in calculating the payment amount for a payee, and particularly to a payment calculation system suitable for calculating the payment amount when paying transportation expenses according to the use of the commuting route to employees having multiple bases.

Background Art

[0002] Conventionally, systems for managing the commuting transportation expenses paid by companies and the like to payees such as employees and calculating the payment amount have been widely used. In particular, in recent years, with the spread of telecommuting and other changes in work styles, there has been a demand for a technology that performs actual expense settlement according to the actual number of work days and commuting records instead of paying a uniform commuting ticket fee. As a technology for realizing this, for example, the technologies described in Patent Document 1 and Non-Patent Document 1 are known.

[0003] In addition, there is also a case where one employee belongs to multiple workplaces such as offices and moves to different workplaces depending on the day. As a technology for realizing this, for example, the technology described in Patent Document 2 is known. The technology described in Patent Document 2 calculates transportation expenses based on the usage record for the route from the payee's home to each workplace.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Non-Patent Documents

[0005]

Non-Patent Document 1

[0006] With the increasing diversification of work styles in recent years, it is anticipated that there will be a rise in cases where individuals base their personal lives in multiple locations, such as their parents' home, temporary residences, or residences at their work locations, and commute from these locations to their workplaces.

[0007] However, the technologies described in Patent Documents 1 and 2 and Non-Patent Document 1 all assume that the only starting point for commuting is the recipient's "home," making it difficult to properly manage routes and usage records for travel from multiple locations and calculate the amount of transportation expenses to be reimbursed.

[0008] Therefore, the present invention has been made in view of the unresolved problems of the conventional technology, and aims to provide a payment calculation system suitable for calculating the amount of transportation expenses paid to employees with multiple locations, based on the commuting route they use. [Means for solving the problem]

[0009] [Invention 1] To achieve the above objective, the payment calculation system of Invention 1 comprises: route information acquisition means for acquiring route information relating to the routes used by the recipient for travel between their workplace and each of several bases that are the bases of the recipient's private life; usage history information acquisition means for acquiring usage history information relating to the recipient's actual use of the multiple routes; and payment amount calculation means for calculating the amount of transportation expenses to be paid when the recipient uses the multiple 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 the fare information in the fare information storage means that stores fare information relating to the fares for the routes.

[0010] In this configuration, the route information acquisition means acquires route information for each of the multiple locations, relating to the routes used by the recipient for travel between that location and their workplace. The usage history information acquisition means acquires usage history information relating to the recipient's use of multiple routes. Then, the payment amount calculation means calculates the amount of transportation expenses to be paid to the recipient based on the acquired route information and usage history information, as well as the fare information stored in the fare information storage means.

[0011] Here, "private life base" refers to the place where the recipient of the allowance bases their private life. This includes the recipient's home, as well as their parents' home, temporary residence, residence at the assignment location for those on temporary assignments, a friend's house, or a vacation home. On the other hand, accommodations where an employee stays temporarily based on a work order and is used solely for the purpose of performing work (so-called business trip destinations) are not included in the definition of "base" as used herein. The same applies hereafter to the allowance calculation system of Invention 3.

[0012] Furthermore, the "route information acquisition means" may, for example, input route information from an input device, acquire or receive route information from an external terminal, read route information from a storage device or storage medium, or generate or calculate route information through information processing. Therefore, acquisition includes at least input, acquisition, reception, reading (including retrieval), generation, and calculation. The same applies to the "usage history information acquisition means." The concept of acquisition is the same hereafter.

[0013] Furthermore, "route information" can consist of, for example, the route itself, or it can consist of information for identifying the route (e.g., name, number, ID, code, link information such as URL), or feature information relating to the route's outline, statistics, or other characteristics. Route information can also consist of, for example, characters, numbers, figures, codes, symbols, images, audio, or other information. Route information can also consist of keywords related to the route (e.g., one or more keywords indicating part of the route's name). The same applies to "usage history information" and "fare information." The same applies hereafter to the payment calculation system of Invention 3.

[0014] Furthermore, the "fare information storage means" stores fare information by any means and at any time. It may store fare information in advance, or it may store fare information by external input or the like when the drawing creation support device 100 is in operation without storing fare information in advance. The same applies hereafter to the payment calculation system of Invention 3.

[0015] Furthermore, this system may be implemented as a single device, apparatus, terminal, or other device, or as a network system in which multiple devices, apparatus, terminals, or other devices are connected in a communicative manner. In the latter case, each component may belong to any of the multiple devices, as long as they are connected in a communicative manner. The same applies hereafter to the payment calculation system of Invention 3.

[0016] [Invention 2] Furthermore, the payment calculation system of Invention 2 is an payment calculation system of Invention 1, wherein the route information acquisition means acquires route information relating to a route used for travel between a first base among the plurality of bases and a first workplace among the one or more workplaces, and the route information acquired by the route information acquisition means includes a conformity determination means that determines whether the route used for travel between the first base and the first workplace conforms to the route conformity criteria, and a registration control means that restricts the registration of the route information acquired by the route information acquisition means when the conformity determination means determines that the route does not conform to the route conformity criteria, and the payment amount calculation means calculates the amount of the payment for the transportation expenses of the person to be paid based on the registered route information.

[0017] In this configuration, the route information acquisition means acquires route information for travel between a first location out of multiple locations and a first workplace out of one or more workplaces. The conformity determination means determines whether the acquired route information for travel between the first location and the first workplace conforms to the route conformity criteria. If it is determined that the route does not conform to the route conformity criteria, the registration control means restricts the registration of the acquired route information. Then, the payment amount calculation means calculates the amount of transportation expenses to be paid to the recipient based on the registered route information.

[0018] Here, "route compliance criteria" include, for example, criteria set based on company regulations, laws and regulations, or generally accepted social standards. The same applies hereafter to the payment calculation system of Invention 4.

[0019] Furthermore, "restricting the registration of route information" means excluding route information from the calculation of transportation expense reimbursement. This includes, for example, refusing to register the route information in the database at all (rejection of the application), registering the route information but excluding it from the calculation of reimbursement until individual approval is obtained from the administrator (application put on hold, provisional registration), or displaying warnings or error messages to the applicant or the person with approval authority on the display unit. The same applies hereafter to the reimbursement calculation system of Invention 4.

[0020] 〔Invention 3〕Furthermore, the payment calculation system of Invention 3 includes a route information acquisition means for acquiring route information regarding a route used in the movement between a plurality of bases which are the bases in the private life of the payment recipient, a usage record information acquisition means for acquiring usage record information regarding the record of the payment recipient using a plurality of the routes, and a payment amount calculation means for calculating the payment amount of transportation expenses when the payment recipient uses a plurality of the routes based on the route information acquired by the route information acquisition means, the usage record information acquired by the usage record information acquisition means, and the freight information stored in the freight information storage means regarding the freight related to the route.

[0021] With such a configuration, the route information acquisition means acquires route information regarding the route used by the payment recipient in the movement between the first base and the second base, and the usage record information acquisition means acquires usage record information regarding the record of the payment recipient using a plurality of routes. Then, the payment amount calculation means calculates the payment amount of transportation expenses for the payment recipient based on the acquired route information and usage record information, and the freight information in the freight information storage means.

[0022] 〔Invention 4〕Furthermore, in the payment calculation system of Invention 4, the route information acquisition means in the payment calculation system of Invention 3 acquires route information regarding a route used in the movement between the first base and the second base among the plurality of bases, and a conformity determination means for determining whether the route used in the movement between the first base and the second base conforms to the route conformity standard for the route information acquired by the route information acquisition means, and a registration control means for restricting the registration of the route information acquired by the route information acquisition means when it is determined by the conformity determination means that the route does not conform to the route conformity standard. The payment amount calculation means calculates the payment amount of transportation expenses for the payment recipient based on the registered route information.

[0023] With such a configuration, route information acquisition means acquires route information regarding a route used for movement between a first base and a second base among a plurality of bases, and conformity determination means determines whether or not the route used for movement between the first base and the second base conforms to a route conformity standard for the acquired route information. As a result, if it is determined that the route does not conform to the route conformity standard, registration control means restricts the registration of the acquired route information. Then, payment amount calculation means calculates the payment amount of transportation expenses for the payment target person based on the registered route information.

[0024] Here, the "route conformity standard" includes, for example, a standard for being recognized as "commuting" under the Industrial Accident Compensation Insurance Act, or a standard based on company regulations equivalent thereto.

[0025] 〔Invention 5〕 Further, in the payment calculation system of Invention 5, in the payment calculation system according to any one of Inventions 2 and 4, the route conformity standard includes a standard regarding the repetitive continuity of the movement, or a standard regarding the temporal relevance between the movement date on which the movement was performed and the employment date of the payment target person.

Effect of the Invention

[0026] As described above, according to the payment calculation system of Invention 1 or 3, it is possible to calculate the payment amount when paying transportation expenses according to the use of a route to a payment target person having a plurality of bases.

[0027] Furthermore, according to the payment calculation system of Invention 2, even when the number of applicable routes increases due to combinations of a plurality of bases and a work place, it is possible to suppress the registration of route information that does not conform to the route conformity standard, so that the burden of tasks such as route confirmation or approval can be reduced.

[0028] Furthermore, according to the payment calculation system of Invention 4, even when the number of applicable routes increases due to combinations of a plurality of bases, it is possible to suppress the registration of route information that does not conform to the route conformity standard, so that the burden of tasks such as route confirmation or approval can be reduced.

[0029] Furthermore, according to the payment calculation system of Invention 5, it is possible to determine the appropriateness of a route based on the repetition and continuity of travel or the temporal relationship between the travel day and the work day. [Brief explanation of the drawing]

[0030] [Figure 1] This is a block diagram showing the configuration of the network system according to this embodiment. [Figure 2] This diagram shows the hardware configuration of the commuter expense calculation server 100. [Figure 3] This diagram shows the data structures of the company master table 400, workplace master table 402, employee information master table 404, employee location information table 406, and employee route information table 408. [Figure 4] This diagram shows the data structures of the employee payment information table 410, the employee daily payment information table 412, the department information table 414, and the fare information table 416. [Figure 5] This figure shows the data structures of the route matching condition table 418, the payment condition table 420, and the search result information table 422. [Figure 6] This is a flowchart showing the process for submitting commute route information. [Figure 7] This is a diagram of the commute route application screen 510. [Figure 8] This figure shows the route application screen 520 for travel between locations. [Figure 9] This is a flowchart showing the process for managing movement between locations. [Figure 10] This diagram illustrates examples of how to determine repetition, continuity, and relevance to employment. [Modes for carrying out the invention]

[0031] The embodiments of the present invention will be described below. Figures 1 to 10 show these embodiments.

[0032] In this embodiment, "employee" refers to eligible recipients, including full-time employees, contract employees, part-time employees, temporary workers, and other employees. "Base" refers to the place where an employee bases their private life (private life base). This includes the employee's home, as well as their parents' home, temporary residence, residence at the assignment location for employees on temporary assignments, a friend's house, or a vacation home.

[0033] 〔composition〕 First, the configuration of this embodiment will be described. Figure 1 is a block diagram showing the configuration of the network system according to this embodiment.

[0034] 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 payments (hereinafter referred to as the "commuter expense payroll linkage support service"), a database server 110 that manages various table information used by the commuter expense calculation server 100, a route search server 120 that searches for routes in response to requests, and employee terminals 200 used by employees and HR personnel of companies that use the commuter expense payroll linkage support service.

[0035] [Hardware configuration of commuter expense calculation server 100] Next, we will explain the configuration of the commuter expense calculation server 100.

[0036] Figure 2 shows the hardware configuration of the commuter expense calculation server 100. As shown in Figure 2, the commuter expense calculation server 100 consists 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 stores the control program for the CPU 30 in a predetermined area, a RAM (Random Access Memory) 34 for storing data read from the ROM 32 and other memory, as well as calculation results necessary for the calculation process of the CPU 30, and an I / F (Interface) 38 that mediates data input and output to external devices. These components are connected to each other and enable data exchange via a bus 39, which is a signal line for data transfer.

[0037] I / F38 is connected to an external device consisting of an input device 40, such as a keyboard and mouse, which can input data as a human interface; a storage device 42, which stores data and tables as files; a display device 44, which displays a screen based on an image signal; and a communication device (not shown) for connecting to the Internet 199.

[0038] [Hardware configuration of database server 110] The database server 110 has the same hardware configuration as the commuter expense calculation server 100.

[0039] [Hardware configuration of route search server 120] Next, we will explain the configuration of the route search server 120.

[0040] The route search server 120 has the same hardware configuration as the commuter expense calculation server 100.

[0041] The route search server 120 is configured to have a database that stores information on routes, fares, travel time, and distance. When the route search server 120 receives a request that includes the departure station, arrival station, and route search conditions, it searches the database for the route, fare, travel time, and distance from the departure station to the arrival station according to the route search conditions, and sends the retrieved route, fare, travel time, and distance as search results to the terminal that made the request.

[0042] A request may include one or more departure stations and one or more arrival stations. For a request that includes one departure station and one arrival station, the route search server 120 searches for the route, fare, travel time, and distance from the one departure station to the one arrival station, and returns the search results.

[0043] For a request that includes multiple departure stations and one arrival station, the route search server 120 searches for the route, fare, travel time, and distance from each departure station to the arrival station, and returns the search results. For example, if the departure stations are A and B and the arrival station is C, the search results will include route AC, its fare, travel time, and distance, and route BC, its fare, and travel time.

[0044] For a request that includes one departure station and multiple arrival stations, the route search server 120 searches for the route, fare, travel time, and distance from the departure station to each arrival station and returns the search results. For example, if the departure station is A and the arrival stations are B and C, the search results will include route AB, its fare, travel time, and distance, and route AC, its fare, travel time, and distance.

[0045] For a request that includes multiple departure stations and multiple arrival stations, the route search server 120 searches for the route, fare, travel time, and distance from each departure station to each arrival station, and returns the search results. For example, if the departure stations are A and B and the arrival stations are C and D, the search results will include route AC, its fare, travel time, and distance; route BC, its fare, travel time, and distance; route AD, its fare, travel time, and distance; and route BD, its fare, travel time, and distance.

[0046] Route search conditions can include, for example, (1) the route with the shortest travel time, (2) the route with the fewest transfers, (3) the route with the cheapest one-way fare, (4) the route with the cheapest 1-month pass fare, (5) the route with the cheapest 3-month pass fare, or (6) the route with the cheapest 6-month pass fare. Additionally, you can choose to (1) apply IC card fares, or (2) apply regular fares instead of IC card fares. For example, if the departure station is A, the arrival station is B, and you set the route search condition to (1), the search results will show the shortest route AB, its fare, travel time, and distance.

[0047] [Hardware configuration of employee terminals 200] The employee terminals 200 consist of stationary terminals such as PCs (Personal Computers) or portable terminals such as smartphones and tablets. Their hardware configuration includes a CPU, ROM, RAM, I / F, a touch panel display input device, and a wireless communication device, and, similar to the commuter expense calculation server 100, each component is interconnected via a bus.

[0048] [Regarding various tables] Next, we will explain the data structure of the various tables stored in the storage device of the database server 110.

[0049] Figures 3(a) to 3(e) show the data structures of the company master table 400, workplace master table 402, employee information master table 404, employee location information table 406, and employee route information table 408.

[0050] As shown in Figures 3(a) to (e), the storage device of the database server 110 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 location information table 406 for registering location information for each employee, and an employee route information table 408 for registering commuting route information for each employee.

[0051] As shown in Figure 3(a), the company master table 400 contains one record for each company ID. Each record contains key information, including company ID, company name, application control category, route suitability condition ID, payment condition ID, and other information.

[0052] Here, the company ID is information used to identify a company. The route compatibility condition ID and payment condition ID are information used to identify the condition information registered in the route compatibility condition table 418 (Figure 5(a)) and payment condition table 420 (Figure 5(b)), respectively, which will be described later.

[0053] As shown in Figure 3(b), the workplace master table 402 contains one record for each company ID and workplace ID. Each record contains key information, including company ID, workplace ID, workplace name, workplace address, calendar ID, map information, and other information.

[0054] Here, the Workplace ID is information used to identify the workplace. The Calendar ID is information used to identify the calendar, which is set for each company and shows the working days and holidays of the workplace. The map information includes the location of the workplace and the nearest station.

[0055] As shown in Figure 3(c), the employee information master table 404 contains one record for each company ID and employee ID. Each record contains key information including company ID, employee ID, employee name, department ID, employee category, payment rule ID, authority level, and other information.

[0056] Here, the Department ID is information used to identify the department to which the employee belongs. The Authority Level indicates one of the following: HR authority, superior authority (approver authority), or employee authority.

[0057] As shown in Figure 3(d), the employee-specific location information table 406 contains one record for each company ID, employee ID, and location ID. Each record contains key information including company ID, employee ID, location ID, location type, location name, location address, map information, start date of application, end date of application, and other information.

[0058] Here, the location ID is information used to identify each employee's location. The location type indicates whether the location is "home," "parents' home," "temporary residence," "assigned residence," or "other." The map information includes the location of the location and the nearest station. In this embodiment, it is possible to register multiple locations for a single employee.

[0059] As shown in Figure 3(e), the employee route information table 408 contains one record for each company ID, employee ID, and route ID. Each record contains key information including company ID, employee ID, route ID, route type, starting point ID, starting point name, nearest station to the starting point, ending point ID, ending point name, nearest station to the ending point, commute route, monthly amount, one-way amount, one-way distance, one-way time, suitability judgment result, payment condition judgment result, application start date, application end date, and other information.

[0060] Here, the Route ID is information used to identify the commute route. The Route Type indicates whether the commute route is "travel between a base and a workplace" or "travel between bases." The Origin ID and Destination ID indicate the starting and ending points of the journey, and depending on the Route Type, either the Base ID or the Workplace ID is registered. For example, if the Route Type is "travel between a base and a workplace," the Base ID (first base) is registered as the Origin ID, and the Workplace ID (first workplace) is registered as the Destination ID (or vice versa). On the other hand, if the Route Type is "travel between bases," both the Base ID (first base, second base) is registered as the Origin ID and Destination ID. The commute route is the route from the starting point specified by the Origin ID to the ending point specified by the Destination ID. For example, if the mode of transportation is train, it would be "home → walking → nearest station (home) → intermediate station → nearest station (workplace) → walking → workplace," and if the mode of transportation is car, it would be "home → car → workplace."

[0061] Furthermore, the conformity determination result is information indicating the result of the route conformity determination process described later (for example, "conformity" or "non-conformity (requires confirmation)"). Similarly, the payment condition determination result is information indicating the result of the payment condition determination process described later.

[0062] Figures 4(a) to 4(d) show the data structures of the employee payment information table 410, the employee daily payment information table 412, the department information table 414, and the fare information table 416.

[0063] As shown in Figures 4(a) to 4(d), the storage device of the database server 110 stores the following: an employee-specific payment information table 410 for registering payment information for commuting expenses for each employee; an employee-specific daily payment information table 412 for registering payment information for daily commuting expenses for each employee; a department information table 414 for registering information such as approvers for each department to which the employee belongs; and a fare information table 416 for registering fare information.

[0064] As shown in Figure 4(a), the employee payment information table 410 has one record registered for each company ID, employee ID, route ID, and payment ID. Each record contains key information including company ID, employee ID, route ID, payment ID, start date, end date, payment date, payment method, payment period, payment / deduction amount, tax classification, total payment amount, and other information.

[0065] Here, the payment ID is information used to identify payment information. The tax classification indicates whether the payment amount is taxable or tax-exempt.

[0066] As shown in Figure 4(b), the employee-specific daily payment information table 412 has one record registered for each employee ID, route ID, and daily payment ID. Each record contains key information including company ID, employee ID, route ID, daily payment ID, payment period, number of days covered, type of travel (one-way / round-trip), tax classification, payment amount, and other information. This table is used when settling transportation expenses based on actual route usage information, etc.

[0067] As shown in Figure 4(c), the department information table 414 contains one record for each company and each department. Each record contains key information including the company ID, department ID, approver ID, proxy applicant ID, and other information.

[0068] As shown in Figure 4(d), the fare information table 416 has one record registered for each fare ID. Each record contains key information including the fare ID, section information (e.g., departure station and arrival station), fare type, fare, fare revision date, and other information.

[0069] Employee commuting expenses can be calculated by accumulating the fares related to the commuting route based on the route information in employee-specific route information table 408 and the fare information in fare information table 416.

[0070] Figures 5(a) to 5(c) show the data structures of the route matching condition table 418, the payment condition table 420, and the search result information table 422.

[0071] As shown in Figures 5(a) to (c), the storage device of the database server 110 stores a route suitability condition table 418 for registering conditions for determining route suitability, a payment condition table 420 for registering conditions for inter-site travel to be eligible for commuting expense reimbursement, and a search result information table 422 for registering search result information related to the search results of the route search server 120.

[0072] As shown in Figure 5(a), the route compatibility condition table 418 contains one record for each route compatibility condition ID. Each record contains key information including the route compatibility condition ID, condition name, applicable targets, judgment criteria, threshold, control details in case of non-compliance, and other information. The condition information consists of the condition name, applicable targets, judgment criteria, threshold, and control details.

[0073] Here, the criteria for judgment (route suitability criteria) are set as follows: for example, "distance between base and workplace," "time required between base and workplace," and "distance from base to the nearest public transportation." The threshold is the upper or lower limit that is permissible for each judgment criterion. In addition, the control actions for non-compliance are set as follows: "registration not possible (rejected)" and "warning display (requires confirmation)."

[0074] As shown in Figure 5(b), the payment conditions table 420 contains one record for each payment condition ID. Each record contains key information including the payment condition ID, condition name, applicable target (e.g., employees on temporary assignment away from home), judgment criteria, threshold, judgment period, and other information. The condition information consists of the condition name, applicable target, judgment criteria, threshold, and judgment period.

[0075] Here, the criteria for determination (route suitability criteria) are set based on the requirements for being recognized as "commuting" under the Workers' Accident Compensation Insurance Act, including "repetition and continuity" and "work-relatedness." For example, a threshold for "repetition and continuity" is set as the minimum number of travels during the determination period (e.g., one month) (e.g., one or more times). For example, a threshold for "work-relatedness" is set as the maximum time interval between the travel day and the work day (e.g., within one day before or after the travel day).

[0076] As shown in Figure 5(c), the search results information table 422 contains one record for each company ID, employee ID, workplace ID, search date and time, and route. Each record contains key information including company ID, employee ID, workplace ID, search date and time, departure station, arrival station, route search conditions, route, fare, distance, travel time, distance, and other information.

[0077] Here, the route is the route found by the route search server 120, specifically the route from the nearest station to the home to the nearest station to the workplace. The fare includes monthly, three-month, six-month, and twelve-month commuter passes, as well as one-way fares.

[0078] [Operation] Next, the operation of this embodiment will be described. Although access to the various tables is actually performed by the commuter expense calculation server 100 communicating with the database server 110, for the sake of simplicity, the following explanation will assume that the commuter expense calculation server 100 accesses the various tables.

[0079] [Commuting route information application processing (between base and workplace)] First, we will explain the operation of the commute expense calculation server 100 when an employee submits information about their commute route between their base of operations and their workplace.

[0080] Figure 6 is a flowchart showing the process for requesting commute route information. The CPU 30 executes the commute route information application process shown in the flowchart of Figure 6, according to a predetermined program stored in a predetermined area of ​​the ROM 32.

[0081] When the commute route information application process is executed on the CPU 30, as shown in Figure 6, it first proceeds to step S100 to determine whether or not an application request has been received from the employee terminal 200. If it is determined that an application request has been received (YES), it proceeds to step S102.

[0082] In step S102, the application information input process is executed. In the application information input process, screen configuration information for configuring the application screen is sent to the employee terminal 200, and the application screen is displayed on the display device of the employee terminal 200.

[0083] Figure 7 shows the commute route application screen 510. As shown in Figure 7, the applicant (employee) enters the start date of application, starting point, ending point, route type, etc. on the commute route application screen 510.

[0084] Regarding the route type, the employee terminal 200 displays options such as "Location-Workplace," "Location-Location," and "Outbound" in a dropdown list 52 based on the received screen configuration information. The applicant selects "Location-Workplace."

[0085] For the starting point (location), the location corresponding to the applicant's employee ID is obtained from the employee location information table 406, and the obtained location information is included in the screen configuration information. On the employee terminal 200, one or more locations are displayed in the dropdown list 52 based on the received screen configuration information. If multiple locations (for example, home, parents' home) are registered, multiple locations will be displayed in the dropdown list 52, and the applicant can select one of them (for example, parents' home).

[0086] For the destination (workplace), the workplace corresponding to the applicant's employee ID (or the workplace set by the company) is obtained from the workplace master table 402, etc., and the obtained workplace information is included in the screen configuration information. On the employee terminal 200, one or more workplaces are displayed in the dropdown list 54 based on the received screen configuration information. If multiple workplaces are registered, multiple workplaces are displayed in the dropdown list 54, and the applicant can select any of them (for example, office B).

[0087] The applicant enters the remaining information and clicks button 58, "Route Search". Next, the process moves to step S104 to obtain information regarding the starting and ending points selected in step S102. Specifically, the address, location information, nearest station information, etc., are obtained from the employee-specific location information table 406 and the work location master table 402.

[0088] Next, the process moves to step S106 to execute the route search process. In the route search process, a request is generated to the route search server 120 based on the origin and destination information obtained in step S104. The generated request is then sent to the route search server 120, and the search results for the sent request are received from the route search server 120. The search results include one or more candidates for route, fare, travel time, and distance. The search results and route search conditions are registered in the search results information table 422, associated with the company ID, employee ID, workplace ID, and search date and time.

[0089] Next, the process moves to step S108 to execute the route selection process. In the route selection process, screen configuration information for displaying a list of route candidates related to the route search server 120's search results is sent to the employee terminal 200, and the applicant is prompted to select one of the routes. Once the applicant has selected a route and clicks the "Apply" button (not shown in the diagram), the process moves to step S110.

[0090] Step S110 executes the route suitability determination process. The route suitability determination process determines whether the submitted route meets the route suitability conditions. Specifically, first, the route suitability condition ID applicable to the company is obtained from the company master table 400, and the condition information corresponding to the obtained route suitability condition ID is obtained from the route suitability condition table 418. Next, it is determined whether the submitted route meets each of the judgment criteria and thresholds in the obtained condition information. For example, if the judgment criterion is set to "travel time" and the threshold to "120 minutes", it is determined whether the travel time of the submitted route is within 120 minutes. Also, if the judgment criterion is set to "distance from base to workplace" and the threshold to "2km", it is determined whether the distance of the submitted route is within 2km.

[0091] Next, the process moves to step S112 to determine whether the result of step S110 is compliant or not. If it is determined to be compliant (YES), that is, if all route compliance conditions are met, the process moves to step S114.

[0092] In step S114, the approval route construction process is executed. In the approval route construction process, the applicant's department ID is obtained from the employee information master table 404, and the approval destination information (approver ID) corresponding to the obtained department ID is obtained from the department information table 414, and the approval route is constructed. Then, based on the constructed approval route, an approval request for the requested route is sent to each approver at the route destination. Once approval and inspection are performed and the application is permitted, the route information of the requested route is registered in the employee-specific route information table 408. At this time, the judgment result from step S110 is also registered as the conformity judgment result.

[0093] Once the process in step S114 is completed, the series of processes ends and the program returns to the original process. On the other hand, if in step S112 the result of the determination in step S110 is determined to be non-compliant (NO), that is, if at least one route compliance condition is not met, the process proceeds to step S116.

[0094] Step S116 executes the registration restriction process. This process restricts the registration of route information for the requested route. The content of the control follows the "Control Content in Case of Non-Compliance" in the Route Compatibility Condition Table 418. For example, if the control content is "Registration Not Possible (Rejected)", the application is rejected, and the employee terminal 200 displays a message indicating that the application has been rejected and the reason for it (for example, "The required time exceeds the limit"). If the control content is "Warning Display (Requires Confirmation)", a warning message is displayed on the employee terminal 200, the applicant is asked to enter a special reason, and the route information is provisionally registered with the status "Requires Confirmation". In this case, individual confirmation by the approver (HR personnel, etc.) is required in the subsequent approval process.

[0095] Once the process in step S116 is completed, the series of processes ends and the process returns to the original state. In the case of provisional registration, the process may proceed to step S114.

[0096] On the other hand, if it is determined in step S100 that no application request will be received (NO), the system waits in step S100 until an application request is received.

[0097] [Inter-site travel management processing] Next, we will explain the operation of the commuter expense calculation server 100 when it determines whether or not to provide transportation expenses and calculates the amount to be paid based on the actual usage of transportation expenses for employees working away from home, etc., between bases (travel between residences).

[0098] Figure 8 shows the route application screen 520 for travel between locations. Employees who travel between locations (for example, those on temporary assignments away from their families) apply for their travel routes in advance. As shown in Figure 8, on the route application screen 520, the employee selects "Location-to-Location" as the route type, and then selects the starting point (for example, the employee's residence at the assignment location) and the ending point (for example, their home) to apply for the route. The applied route is processed in the same way as the commute route information application process (Figure 6) (including suitability assessment and approval processes) and registered in the employee-specific route information table 408.

[0099] Figure 9 is a flowchart showing the inter-site travel management process. The inter-site travel management process is performed, for example, as part of the monthly payroll calculation process.

[0100] When the inter-site travel management process is executed on the CPU 30, as shown in Figure 9, it first proceeds to step S200 to set the employees and period (for example, the current month) to be processed, and then proceeds to step S202.

[0101] In step S202, route information for the target employee, where the route type is "inter-location travel," is retrieved from the employee-specific route information table 408. The retrieved route information includes information about the starting and ending points.

[0102] Next, the process moves to step S204, where usage information for the route related to the route information obtained in step S202 (hereinafter referred to as the "target route") is acquired for the target period. For example, based on the daily payment information registered in the employee-specific daily payment information table 412, or information linked from an external system (e.g., an attendance management system), the date and time (travel date) and number of times for travel made using the target route (hereinafter referred to as "travel on the target route") are acquired.

[0103] Next, the process moves to step S206 to obtain the payment conditions applicable to the target employee. Specifically, the payment condition ID applicable to that company is obtained from the company master table 400, and the condition information corresponding to the obtained payment condition ID is obtained from the payment condition table 420.

[0104] Next, the process moves to step S208 to execute the payment eligibility determination process. In the payment eligibility determination process, it is determined whether the usage information obtained in step S204 satisfies the payment eligibility conditions obtained in step S206. Specifically, the requirements of "repetition and continuity" and "employment relevance" are determined.

[0105] Figure 10 illustrates examples of how to determine repetition, continuity, and employment relevance. In determining "repetition and continuity," it is determined whether more than the set threshold (e.g., 1 time) has been reached during the assessment period (e.g., 1 month) set in the payment conditions table 420. In the example in Figure 10, one movement occurred in November, so the requirement of repetition and continuity is met.

[0106] In determining "employment relevance," it is determined whether the temporal relationship between the day of the transfer and the employee's workday meets a set threshold (for example, within one day before or after the transfer day). Workdays are identified based on the calendar ID, etc., in the workplace master table 402. In the example in Figure 10, the day after the transfer day (November 22nd) (November 23rd) is a workday, so the employment relevance requirement is met.

[0107] Next, the process moves to step S210 to determine whether the result of step S208 meets the eligibility requirements. If it is determined that the eligibility requirements are met (YES), that is, if both the requirements for repetition and continuity and employment relevance are met, the process moves to step S212.

[0108] In step S212, travel along the target route is confirmed as eligible for reimbursement of commuting expenses. Specifically, the usage information regarding the actual use of the target route (daily payment information in employee-specific daily payment information table 412) is set to "non-taxable" as the tax classification. The determination result is also registered in the payment condition determination results in employee-specific route information table 408.

[0109] Next, the process moves to step S214 to execute the payment amount calculation process. In the payment amount calculation process, the amount of commuting expenses to be paid is calculated based on the route information and fare information in the fare information table 416 for the target route, and registered in the employee-specific daily payment information table 412. In addition, the payment amount is calculated based on that route information, and the payment information is registered in the employee-specific payment information table 410 or the employee-specific daily payment information table 412. The same process is followed for commuting routes other than the target route, where the payment amount is calculated and the payment information is registered.

[0110] On the other hand, if it is determined in step S210 that the payment conditions are not met (NO), the process moves to step S216, where the travel along the target route is excluded from the payment of commuting expenses and is processed as, for example, travel expenses.

[0111] Once the processing in step S214 or S216 is completed, the series of processes ends and the program returns to the original process.

[0112] [Commuting expense calculation process (between base and workplace)] Next, we will explain the operation of the commuter expense calculation server 100 when calculating the amount of commuter expense reimbursement based on actual usage for travel between a base and the workplace (for example, from home to the workplace, from parents' home to the workplace, etc.). This process is executed in parallel with, or before or after, the inter-base travel management process described above (Figure 9).

[0113] First, specify the employees to be processed and the period (for example, the current month). Next, for the target employee, route information where the route type is "travel between base and workplace" is retrieved from employee-specific route information table 408. Here, if multiple route information entries are registered for a single employee (for example, Route A: Home - 1st workplace, Route B: Parents' home - 1st workplace), all of that route information is retrieved.

[0114] Next, usage information for each acquired route during the target period is obtained. This usage information is obtained based on, for example, information registered in the employee-specific daily payment information table 412, usage history data from transportation IC cards, or attendance clock-in / out data (including clock-in / out location information) from the attendance management system. Specifically, for each day during the target period, the route used to commute to work (i.e., which location was the starting point) is identified, and the number of times each route was used is tallied.

[0115] Next, the amount of commuting expenses to be paid is calculated. Specifically, for each route, the amount to be paid for each route is calculated by multiplying the "one-way fare" registered in the employee-specific route information table 408 or the "fare" obtained from the fare information table 416 by the obtained "number of uses". For example, if route A is used 10 times and route B is used 5 times, the amount to be paid will be (one-way fare for route A × 10) + (one-way fare for route B × 5).

[0116] Furthermore, if providing a commuter pass is cheaper (for example, if the number of uses of Route A exceeds the cost of a one-month commuter pass), a comparative calculation may be performed using the cost of a commuter pass as the payment amount, and the cheaper option may be determined as the payment amount.

[0117] Next, payment information is registered based on the calculated payment amount and usage record. The calculated payment amount is registered in the employee-specific payment information table 410 or the employee-specific daily payment information table 412. In this case, travel between the base and the workplace is treated as non-taxable commuting expenses in principle, so the tax category is set to "non-taxable" (however, this excludes the portion exceeding the non-taxable limit under tax law).

[0118] As described above, even if an employee commutes to work from a location other than their "home," such as their "parents' home," it is possible to automatically calculate and pay appropriate commuting expenses based on registered route information and usage history.

[0119] 〔effect〕 Next, the effects of this embodiment will be described. In this embodiment, route information is obtained for each of the multiple locations regarding the commuting route used for travel between the workplace and that location, usage information is obtained regarding the actual use of multiple commuting routes by the employee, and the amount of commuting expenses paid when an employee uses multiple commuting routes is calculated based on the obtained route information, usage information, and fare information in the fare information table 416.

[0120] This makes it possible to apply for and calculate commuting expenses even when commuting from locations other than one's home (such as family home, temporary residence, or residence at the assignment location), and allows for the calculation of the amount of commuting expenses to be paid to employees with multiple locations, based on the commuting route used.

[0121] Furthermore, in this embodiment, route information relating to the commuting route used for travel between a first location out of multiple locations and a first workplace out of one or more workplaces is acquired, and it is determined whether or not the commuting route relating to the acquired route information meets the route suitability conditions. If it is determined that the route does not meet the route suitability conditions, the registration of the acquired route information is restricted.

[0122] This allows for the suppression of registering route information that does not meet the route suitability criteria, even if the number of applicable commuting routes increases due to combinations of multiple locations and workplaces. As a result, the burden of tasks such as verifying or approving commuting routes can be reduced.

[0123] Furthermore, in this embodiment, route information is acquired regarding the route used for travel between the first base and the second base, usage information is acquired regarding the employee's use of multiple routes, and the amount of commuting expenses paid when an employee uses multiple routes is calculated based on the acquired route information, usage information, and fare information in the fare information table 416.

[0124] This makes it possible to apply for and calculate commuting expenses for travel between locations, and to calculate the amount of commuting expenses paid to employees with multiple locations, based on the commuting route they use.

[0125] Furthermore, in this embodiment, route information is acquired regarding the route used for travel between the first and second locations among multiple locations, it is determined whether the acquired route information conforms to the payment conditions, and if it is determined that it does not conform to the payment conditions, the registration of the acquired route information is restricted.

[0126] This makes it possible to suppress the registration of route information that does not meet the payment conditions, even if the number of routes that can be applied for increases due to the combination of multiple locations, thereby reducing the burden of tasks such as route verification or approval.

[0127] Furthermore, in this embodiment, the payment conditions include conditions relating to the repetition and continuity of travel along the target route, or conditions relating to the temporal relationship between the travel date on which the travel along the target route took place and the employee's working day.

[0128] This makes it possible to determine the appropriateness of a route based on the repetition and continuity of movement along the target route or the temporal relationship between the travel day and the workday.

[0129] In this embodiment, the storage device 42 corresponds to the fare information storage means of Invention 1 or 3, step S202 corresponds to the route information acquisition means of Inventions 1 to 4, step S204 corresponds to the usage history information acquisition means of Invention 1 or 3, and step S214 corresponds to the payment amount calculation means of Inventions 1 to 4. Furthermore, steps S110 and S208 correspond to the suitability determination means of Invention 2 or 4, and steps S112, S116, S210, and S216 correspond to the registration control means of Invention 2 or 4.

[0130] [Variation] In the above embodiment and its modifications, the amount of transportation expenses paid was calculated based on the acquired route information and usage history information. However, the system is not limited to this, and a configuration can be adopted in which route information or usage history information is registered without calculating the amount of transportation expenses paid. For example, instead of being a transportation expense settlement system, it can be configured as a commuting route management system for identifying or managing routes that meet the requirements of "commuting" under the Workers' Accident Compensation Insurance Act, and can be configured to maintain a database of travel routes from multiple locations and travel routes between locations. This allows companies that do not reimburse actual transportation expenses (for example, by providing a fixed allowance or requiring employees to bear the cost themselves) to use it as a document management tool to prove that the travel was on a reasonable route in the event of a commuting accident.

[0131] Furthermore, in the above embodiment and its modifications, the processing in steps S110 and S208 determined compliance using predetermined rule-based criteria (thresholds such as distance, time, and number of times). However, the system is not limited to this, and a configuration can be adopted that uses a machine learning model such as AI (Artificial Intelligence) to determine compliance. For example, a machine learning model can be trained using historical data of route information that has been previously approved or rejected, and the decision history of approvers, as training data. Using this trained model, the probability of compliance (likelihood of approval) of newly submitted route information can be calculated, and if this probability is above a predetermined value, the system can be automatically determined to be compliant. This enables flexible judgments that reflect complex geographical conditions that cannot be easily determined by clear numerical criteria (for example, the rationality of winter detour routes in snowy regions) and traffic conditions specific to the region, thereby improving both approval accuracy and operational efficiency.

[0132] Furthermore, in the above embodiment and its modifications, the process in step S204 acquires usage information from the attendance management system or employee input, but it is not limited to this. It is also possible to adopt a configuration that acquires objective movement data such as usage history data of transportation IC cards or GPS (Global Positioning System) location information logs from mobile terminals such as smartphones owned by employees, and uses this as usage information. In addition, it is possible to configure the system to compare the route information of the applied route with the acquired actual movement data (GPS logs, etc.) and issue a warning or notify the administrator if there is a significant discrepancy between the two (for example, if an employee is habitually using a route different from the applied route, or if they are commuting from a location other than the applied base). This makes it possible to prevent fraudulent receipt of benefits and expedite fact-finding when determining workers' compensation.

[0133] Furthermore, while the above embodiments and their modifications exemplify route suitability criteria by using travel time, distance, etc., the system is not limited to these. Other criteria such as fares (economic efficiency), number of transfers (rationality), types of available transportation, and environmental impact indicators (e.g., CO2 emissions) can also be adopted as route suitability criteria. For example, when multiple route options exist, the system can be configured to determine only the route with CO2 emissions below a predetermined value, or the route with the lowest CO2 emissions, as "suitable," or to provide an incentive (points, etc.) to employees who select a route. This can enhance the market value of the system as one that supports companies' ESG (Environment, Social, Governance) management and SDGs (Sustainable Development Goals) initiatives.

[0134] Furthermore, in the above embodiment and its modifications, the system is configured to register and calculate route information individually for each of the multiple locations. However, it is not limited to this configuration, and it is possible to adopt a configuration in which the route to the main location (e.g., home) is calculated as a fixed amount for commuter passes, and the route to the secondary location (e.g., parents' home) is calculated as actual expenses based on usage. In this case, based on usage information, the calculation method can be to deduct a prorated amount from the commuter pass for the number of days commuting from the secondary location occurs, or to adjust and pay the difference between the two. This prevents overpayment (double payment) in cases such as when an employee who has purchased a commuter pass temporarily commutes from their parents' home.

[0135] Furthermore, in the above embodiments and their modifications, registration was restricted if the submitted route did not meet the route suitability conditions. However, the system is not limited to this, and can be configured to automatically search for alternative routes (recommended routes) that are cheaper, shorter, or have a lower environmental impact than the submitted route, and recommend these alternative routes to the applicant. For example, if a route with lower fares than the submitted route exists, it may be presented with a message such as "You can be approved if you change to this route," and the applicant can change their route with a single click. This can help reduce commuting expenses for the entire company and alleviate the commuting burden on employees.

[0136] Furthermore, while the above embodiment and its variations simply calculate the payment amount by adding up the fares, the system is not limited to this. It can also employ a configuration that determines and simulates the most economical or tax-advantageous payment method. For example, based on usage data for a certain period (e.g., the past month), the system can compare the total amount when actual expenses are reimbursed each time for travel from multiple locations with the amount when a commuter pass is purchased for the main location. Alternatively, it can calculate the combination that best utilizes the tax-exempt limit based on travel data from multiple locations, thereby recommending the most beneficial payment method for both the company and the employee.

[0137] Furthermore, while the above embodiments and their modifications require that both repetition and continuity and relevance to employment be satisfied, the requirements are not limited to this, and it is also possible to require that either one of these be satisfied, or to add other requirements (for example, the purpose of the travel, the expenses incurred for the travel, etc.).

[0138] Furthermore, in the above embodiment and its modifications, inter-base travel deemed to meet the payment conditions is uniformly treated as tax-exempt. However, the system is not limited to this, and for example, a configuration can be adopted in which any portion exceeding the tax-exempt limit under the Income Tax Act is treated as taxable.

[0139] Furthermore, in the above embodiment and its modifications, the amount of transportation expenses paid was calculated based on the daily payment information (period of daily payment, number of days of payment, etc.) in the employee-specific daily payment information table 412 as information regarding the actual use of multiple commuting routes by a single employee. However, the amount of transportation expenses paid can also be calculated based on the payment information (period of payment, number of months of payment, etc.) in the employee-specific payment information table 410.

[0140] Furthermore, in the above embodiment and its modifications, the commuter expense calculation server 100 and the database server 110 are configured as separate servers, but the system is not limited to this, and these functions may be implemented on a single server device. Alternatively, the system may be built on a cloud computing environment.

[0141] Furthermore, while the above embodiments and their modifications have described their application to a network system consisting of the Internet 199, the invention is not limited to this, and may also be applied to, for example, a so-called intranet that communicates using the same method as the Internet 199. Of course, it is not limited to networks that communicate using the same method as the Internet 199, but can be applied to any network using any communication method.

[0142] Furthermore, in the above embodiments and their modifications, the process shown in the flowcharts of Figures 6 and 9 was described in the case of executing a program that is pre-stored in ROM 32. However, the invention is not limited to this, and the program describing these procedures may be read into RAM 34 from a storage medium in which the program is stored and then executed.

[0143] Furthermore, the above embodiments and their modified forms (including their respective constituent technologies) are mutually applicable.

[0144] Furthermore, while the above embodiments and their modifications applied the present invention to the calculation of employees' commuting expenses, the invention is not limited to these cases and can be applied to other cases without departing from the spirit of the invention. For example, the present invention can be applied to the calculation of business trip expenses and other transportation expenses, as well as to the calculation of transportation expenses paid to persons other than employees. [Explanation of symbols]

[0145] 30…CPU, 32…ROM, 34…RAM, 38…I / F, 39…Bus, 40…Input device, 42…Storage device, 44…Display device, 52, 54, 56…Dropdown list, 58…Button, 100…Commuting expense calculation server, 110…Database server, 199…Internet, 200…Employee terminal, 400…Company master table, 402…Workplace master table, 404…Employee information master table, 406…Employee-specific location information table, 408…Employee-specific route information table, 410…Employee-specific payment information table, 412…Employee-specific daily payment information table, 414…Department information table, 416…Fare information table, 418…Route suitability condition table, 420…Payment condition table, 422…Search result information table, 510…Commuting route application screen, 520…Route application screen

Claims

1. Route information acquisition means for acquiring route information regarding the routes used by the recipient for travel between their workplace and each of several locations that serve as the recipient's base of operations in their private life, A means for acquiring usage information to acquire usage information regarding the actual usage of multiple routes by the person eligible for payment, A payment calculation system characterized by comprising: a payment amount calculation means that calculates the amount of transportation expenses to be paid when the recipient uses multiple routes, based on route information acquired by the route information acquisition means, usage history information acquired by the usage history information acquisition means, and fare information stored in a fare information storage means that stores fare information relating to the fares for the routes.

2. In claim 1, The route information acquisition means acquires route information relating to the route used for travel between the first of the multiple locations and the first of the one or more workplaces. A conformity determination means for determining whether the route used for travel between the first base and the first workplace conforms to the route conformity criteria, based on the route information acquired by the route information acquisition means. The system includes a registration control means that restricts the registration of route information acquired by the route information acquisition means when the conformity determination means determines that the route does not conform to the route conformity criteria, The payment amount calculation means is a payment calculation system characterized by calculating the amount of transportation expenses to be paid to the recipient based on registered route information.

3. In Claim 1, The route information acquisition means acquires second route information relating to a second route used for travel between multiple locations that are the bases of the recipient's private life. The means for acquiring the usage history information acquires second usage history information relating to the fact that the recipient has used multiple second routes, The payment amount calculation means is characterized by calculating the amount of transportation expenses to be paid when the recipient uses multiple of the second routes, based on the second route information obtained by the route information acquisition means, the second usage history information obtained by the usage history information acquisition means, and the fare information stored in the fare information storage means.

4. In claim 3, The route information acquisition means acquires the second route information relating to the second route used for travel between the first and second bases among the plurality of bases, With respect to the second route information acquired by the route information acquisition means, a conformity determination means determines whether the second route used for travel between the first base and the second base conforms to the route conformity criteria. The system includes a registration control means that restricts the registration of the second route information acquired by the route information acquisition means when the conformity determination means determines that the route does not conform to the route conformity criteria, The payment amount calculation means is characterized by calculating the amount of payment for the transportation expenses of the person eligible for payment based on the registered second route information.

5. In any one of claims 2 and 4, The payment calculation system is characterized in that the route suitability criteria include criteria relating to the repetition and continuity of the movement, or criteria relating to the temporal relationship between the day the movement took place and the working day of the person eligible for payment.

Images