JP6855077B2 - Transportation expense application approval support system, method, and program - Google Patents

Description

The present invention relates to a transportation expense application approval support system, a method, and a program that support the approval work of a transportation expense application.

In a company, when an employee goes on a business trip or goes out, the employee who is the person who went on a business trip or goes out often reimburses the transportation expenses and settles them all at the end of the month. Then, the employee (hereinafter referred to as "applicant") prepares a transportation expense application form in which the date and time of going out, the destination, the travel route, the means of transportation, the fare, etc. are entered in order to apply for the settlement of the transportation expenses. , Must be submitted to the approver.

The submitted transportation expense application will be checked by the approver. The approver checks the means of transportation such as railroads, buses, and taxis, routes, means of transportation, and fares described in the transportation expense application, and approves them if it is determined to be appropriate.

On the other hand, the approver denies if it determines that the contents of the means of transportation, route, fare, etc. described in the transportation expense application cannot be reasonably explained.

Such checking and approval work is a burden for the approver.

Therefore, for example, as in Patent Document 1, a technique for reducing the burden of approval work of a transportation expense application is disclosed.

However, the technique disclosed in Patent Document 1 is premised on the applicant using a recording medium such as a transportation IC card for payment of transportation fare.

Therefore, the technique disclosed in Patent Document 1 can be used for collating the content recorded on the recording medium with the content of the transportation expense application, but for confirming the validity of the means of transportation. Cannot be used for. Therefore, if, for example, a bus or taxi fare is applied for as a means of transportation in the transportation expense application form, it is not possible to confirm whether or not the use of the bus or taxi was appropriate in the first place.

Japanese Unexamined Patent Publication No. 2014-29601

The present invention has been made in view of such circumstances, and in order to improve the convenience of the approver of the transportation expense application, the approval work of the approver for the transportation expense application especially regarding the use of a bus or taxi is supported. The purpose is to provide transportation expense application approval support systems, methods, and programs.

In order to achieve the above object, the following measures are taken in the present invention.

That is, the first aspect of the present invention is a system for supporting the approval work of the approver for the transportation expense application for the use of a bus or taxi, and the customer ID of the customer to be visited, the date and time of the visit, and the date and time of the visit. A visit information database that stores the visitor in association with the customer, a customer information database that stores the customer's customer ID and customer location in association with each other, and a station master that stores the station name, station ID, and station location in association with each other. Based on the visit date and time and the visitor entered in the transportation expense application form, the first search means for searching the visit date and time and the customer ID associated with the visitor from the visit information database, and the first From the station master, the station is based on the second search method that searches the customer information database for the customer position associated with the customer ID searched by the search method, and the station ID of the station entered in the transportation expense application form. A third search means for searching the station position associated with the ID, a calculation means for calculating the distance between the customer position searched by the second search means, and the station position searched by the third search means. , It is equipped with a display means for displaying the distance calculated by the calculation means so that the approver can permit or deny the use of the bus or taxi.

A second aspect of the present invention, the transportation fee application approval support system of the first aspect, the calculated by the calculation unit distance, further comprising a comparing means for comparing and listening distance, the threshold distance is calculated The distance that a bus or taxi is allowed to use if the distance calculated by the means is greater than or equal to the threshold distance .

According to the transportation expense application approval support system, method, and program of the present invention, it is possible to support the approval work of the approver for the transportation expense application especially related to the use of a bus or taxi, thereby improving the convenience of the approver. It will be possible.

It is a figure which shows the flow of the transportation expense application creation processing by the transportation expense application creation support system. It is a conceptual diagram which shows an example of the screen for making a transportation expense application which is displayed from the display at the time of processing the making of a transportation expense application by the transportation expense application creation support system. It is a flow chart which shows the flow of the transportation expense calculation processing by the transportation expense application form creation support system. It is a flow chart which shows the flow of the transportation expense application approval processing about a railway by the transportation expense application approval support system. It is a conceptual diagram which shows an example of the approval screen which is displayed from the display at the time of the transportation expense application approval processing about a railroad by a transportation expense application approval support system. It is a figure which shows the flow of the transportation cost calculation processing about a railroad by a transportation cost application approval support system. It is a flow chart which shows the flow of the transportation expense application approval processing about a bus and a taxi by the transportation expense application approval support system. It is a conceptual diagram which shows an example of the approval screen which is displayed from the display at the time of the transportation expense application approval processing about a bus or taxi by the transportation expense application approval support system. It is a flow chart which shows the flow of the update process of the settlement history information database and the route amount history database in the transportation expense application approval support system.

For example, the transportation expense application creation support system to which the transportation expense application creation support method according to the embodiment of the present invention is applied, and the transportation expense application approval support system to which the transportation expense application approval support method is applied are groups. It is realized as a function built into the wear.

Groupware is system software for information sharing utilizing computer networks within an organization such as a company. The aim is to improve work efficiency through various functions used for work such as exchanging and sharing information between computers (users) connected to the network, and schedule management. Various functions are integrated into one system, and they provide services to users while organically combining them.

Groupware can be built using a web browser by applying internet / intranet technology. Since this type does not require dedicated software on the client side, only the host needs to be installed, and the client operating system does not have to be selected.

Since groupware is known in this way, the description of the general functions and configurations of groupware itself is omitted in this specification, and the following is a transportation expense application creation support system and a transportation expense application approval support system. The function of is explained.

(Transportation expense application creation support system)
The transportation expense application creation support system built into the groupware will be explained.

The transportation expense application preparation support system is used by the applicant who prepares the transportation expense application.

FIG. 1 is a diagram showing a flow of a transportation expense application creation process by the transportation expense application creation support system.

As shown in FIG. 1, the transportation expense application creation support system includes a visit information database (hereinafter referred to as "visit information DB") 10, a customer information database 20, and a settlement history information database (hereinafter, "payment history information"). 30 (referred to as "DB") and the station master 40 are used.

The visit information DB 10 is a database that stores past visit records by various visitors, and stores the visit date and time a, which is the date and time of the visit, the visitor b who made the visit, and the customer IDc, which is the visit destination. I remember it by associating it.

The customer information database 20 stores the customer IDc, the customer name d, the customer address e, and the customer position f in association with each other. There is a one-to-one correspondence between the customer IDc and the customer name d. The customer address e is the address of the customer, and there may be a plurality of customer addresses e with respect to the customer IDc. The customer position f is a coordinate representing the position of the customer address e. Therefore, the customer address e and the customer position f also have a one-to-one correspondence.

The settlement history information DB 30 is a database that stores the settlement conditions for transportation expense settlement made in the past, and the application date h, customer IDc, and customer position where the transportation expense application form was created are stored in the applicant IDg that identifies the applicant. f, the station IDi of the station used, the station position j of the station, and the last disembarkation station flag k are associated and stored. The final disembarkation station flag k is a flag indicating whether or not the station corresponding to the station IDi has been approved as the final disembarkation station for the customer position f in the past, and the station corresponding to the station IDi is the final disembarkation for the customer position f. If it has been approved as a station in the past, it is set to "true", otherwise it is set to "false".

The station master 40 stores the station IDi of the station, the station name m, the station address n, and the station position p in association with each other. The station position p is a coordinate representing the position of the station address n.

When creating a transportation expense application, the applicant activates the transportation expense application creation support system from the groupware menu. Then, as shown in the operation screen A, the visit date and time a and the visitor b are input.

When the visit date and time a and the visitor b are input, the transportation expense application creation support system searches the visit information DB 10 for the customer IDc stored in association with the visit date and time a and the visitor b ( Search # 1).

The transportation expense application creation support system further searches the customer position f associated with the customer IDc searched by the search # 1 from the customer information DB 20 (search # 2).

The transportation expense application creation support system further displays a predetermined number of station IDi associated with the station position p close to the customer position f searched by search # 2 from the station master 40 in the order of being close to the customer position f. Search (for example, 3) (search # 3).

Further, the transportation expense application creation support system searches the station IDi associated with the customer position f searched by the search # 2 from the accumulated history information DB 30 (search # 4).

Instead of search # 4, as shown by the alternate long and short dash line in FIG. 1, the station IDi of the last getting-off station corresponding to the customer IDc searched by search # 1 is searched from the settlement history information DB 30. (Search # 4').

Further, as a modification, the transportation expense application creation support system searches for the station IDi of a predetermined number of stations located close to the customer position f in the search # 3, but instead searches for the customer position f in terms of road distance or access. You may search for station IDi of a predetermined number of stations that are close in time.

For example, even if the location is close, it takes a long time to reach due to bad road conditions, and conversely, even if the location is far away, the road is connected by a straight road. If the circumstances are good, it may be possible to reach the station in a short time, so the station closest to the location is not always the final stop.

In this way, instead of searching for the station IDi of the station located close to the customer position f, the station master 40 further searches for the station IDi of the station close to the customer position f in terms of road distance or access time. For example, traffic information z including map information and road information is stored. The traffic information z may reflect the real-time traffic situation acquired from an external site. As a result, in the search # 3, the customer position f searched by the search # 2 and the station position j and the traffic information z stored in the station master 40 are taken into consideration, so that the road distance or the access time is close. It is also possible to search for station IDi of a predetermined number of stations.

In this way, the transportation expense application creation support system searches for station IDi of a plurality of stations that are close in position to the customer position f, road distance, or access time in search # 3. Can be done.

On the other hand, the station IDi searched by search # 4 (or search # 4') may or may not be searched by search # 3, but the search result by search # 4 (or search # 4') may or may not be searched. Is preferably considered in preference to the search result by search # 3.

The transportation expense application creation support system further searches the station name m corresponding to the station IDi searched in this way from the station master 40, and displays the searched station name m from the display as illustrated in FIG. 2, for example. By doing so, it is possible to suggest to the applicant as a candidate for the final stop at the time of visiting the customer (# 5). In the present embodiment, the suggestion is not limited to displaying from a display as shown in FIG. 2, but also includes simply outputting data to a computer.

By the above-mentioned search # 1, search # 2, search # 3, and search # 4 (or search # 4'), the transportation expense application preparation support system can select the candidate for the last station to get off at the time of visiting the customer. It is possible to suggest one or more to the applicant.

FIG. 2 is a conceptual diagram showing an example of a screen for creating a transportation expense application that is displayed on the display during the processing of creating a transportation expense application by the transportation expense application creation support system.

The applicant can confirm that this display is related to the transportation expense application form related to the train by looking at the classification column K on the transportation expense application form creation screen α. Further, since the visit date and time a is displayed below the classification column K, the applicant can check the specific visit date and time a. Below the visit date and time a, the station name m suggested in # 5 is shown.

In the example of the transportation expense application creation screen α shown in FIG. 2, three station names m (Shinagawa, Hamamatsucho, Daimon) are suggested and displayed as candidates for the final stop station in # 5. As a modification, the station IDi may be displayed instead of displaying the station name m.

The applicant can easily complete the transportation expense application form by selecting the station name m of the actual final disembarkation station from the station names m suggested as the final disembarkation station while referring to the transportation expense application creation screen α. It becomes possible to create in. If the suggested station name m does not include the station name m of the actual final disembarkation station, the applicant puts the station name of the actual final disembarkation station on the transportation expense application creation screen α. Enter text directly. When the station name is text-entered on the transportation expense application creation screen α in this way, the transportation expense application creation support system can create a transportation expense application based on the input station name.

Further, in the example shown in FIG. 2, the corresponding charge q is also suggested and displayed.

Such a calculation process of the charge q will be described with reference to FIG.

FIG. 3 is a flow chart showing the flow of the transportation cost calculation process by the transportation cost application preparation support system.

The transportation expense application creation support system uses the route amount history database (hereinafter, “route amount history DB”) 50 for the transportation expense calculation process.

The route amount history DB 50 associates the visitor b, the two station IDs corresponding to the two station names that define the boarding section, and the transportation cost amount q of the boarding section as conditions for the transportation cost settlement made in the past. I remember.

In the transportation expense application creation support system, as shown in the operation screen B, the visitor b, the boarding station ID, and the getting-off station ID are input by the applicant (# 7), and the route amount history DB 50 is displayed. The visitor b and the two station IDs corresponding to the boarding station ID and the getting-off station ID, that is, the amount q associated with the station ID1 and the station ID2 are acquired, and the acquired amount q is suggested (# 8). ). The amount q suggested in this way is displayed on the transportation expense application creation screen α as shown in FIG.

As described above, the transportation expense application preparation support system can suggest the final stop station and the amount of money at the time of the visit to the customer based on the simple input by the applicant. As a result, the applicant can efficiently prepare the transportation expense application form by utilizing the suggested contents.

(Transportation expense application approval support system)
Next, the transportation expense application approval support system incorporated in the groupware will be described.

The transportation expense application approval support system is used by the approver who approves the transportation expense application.

FIG. 4 is a flow chart showing the flow of the transportation expense application approval processing for railways by the transportation expense application approval support system.

The transportation expense application approval support system also uses the visit information DB 10, the customer information database 20, the settlement history information DB 30, and the station master 40. These have already been explained, so avoid duplicate explanations.

When approving the transportation expense application, the approver activates the transportation expense application approval support system from the groupware menu. Then, as shown in the operation screen C, the visit information DB 10 is associated with the visit date / time a and the visitor b based on the visit date / time a and the visitor b entered in the transportation expense application form. Search for customer IDc (search # 11).

The transportation expense application approval support system further searches the customer position f associated with the customer IDc searched by the search # 11 from the customer information DB 20 (search # 12).

The transportation expense application approval support system further searches the station IDi associated with the station position p that satisfies the predetermined criteria from the station master 40 based on the customer position f searched by the search # 12 (search # 13). ). The number of station IDi searched by search # 13 is not limited to a single number, and may be a plurality of stations.

The predetermined standard can be, for example, a position from the customer position f, a road distance, or an access time. Specifically, satisfying the predetermined criteria means that the geographical distance from the customer position f is within a certain distance, the road distance from the customer position f is within a certain distance, or the access time from the customer position f. It can be said that it is within a certain time.

In search # 13, in order to search for a station that is positionally close to the customer position f, the customer position f searched by the search # 12 and the station position j stored in the station master 40 are taken into consideration. In order to search for a station that is close to the customer position f in terms of road distance or access time, the customer position f searched by search # 12, the station position j stored in the station master 40, and the traffic information z are used. Will be considered.

Furthermore, the transportation expense application approval support system has been approved in the past as the last stop station for the customer position f searched by search # 12, and the station of the station where the last stop station flag k is set to "true". IDi is searched from the accumulated history information DB 30 (search # 14).

In addition, the transportation expense application approval support system has been approved in the past as the last stop for the customer IDc searched by the search # 11, as shown by the alternate long and short dash line in FIG. 4, instead of the search # 14. Then, the station IDi of the station for which the final disembarkation station flag k is set to "true" may be searched from the settlement history information DB 30 (search # 14').

By the above-mentioned search # 11, search # 12, search # 13, and search # 14 (or search # 14'), the transportation expense application approval support system is a candidate for the last station to get off at the time of visiting the customer. It is possible to search for one or more station IDi.

The transportation expense application approval support system searches for the station name m corresponding to the station IDi searched in this way from the station master 40, and creates an approval screen β as shown in FIG. 5 based on the search results. , Show from the display.

FIG. 5 is a conceptual diagram showing an example of an approval screen displayed on the display when the transportation expense application approval processing for railways is performed by the transportation expense application approval support system.

The approval screen β can display not only the station name m corresponding to the searched station IDi but also the customer name d. Furthermore, the outlet r1 is displayed near the place where the customer name d is displayed, and it seems that XX station (station name m) is often used when visiting XX (customer name d). You can also display comments and advice. Furthermore, the charge q can be displayed.

The calculation process of the charge q will be described with reference to FIG.

FIG. 6 is a diagram showing a flow of transportation cost calculation processing related to railways by the transportation cost application approval support system.

The transportation expense application approval support system also uses the route amount history DB 50 as described above for the transportation expense calculation process, similarly to the transportation expense application creation support system.

In the transportation expense application approval support system, as shown on the operation screen D by the approver, when the visitor b, the boarding station ID, and the getting-off station ID are input (# 17), the visit is made from the route amount history DB 50. The person in charge b and the two station IDs corresponding to the boarding station ID and the getting-off station ID, that is, the amount q associated with the station ID1 and the station ID2 are acquired.

The amount q thus acquired is displayed on the approval screen β as shown in FIG. 5 (# 18).

The approval screen β displays the blowout r2 near the place where the amount q is displayed, and comments and advice such as "It seems that XX stations are often XX yen". Etc. can also be displayed.

Both blowouts r1 and r2 are hidden by tapping the x mark displayed in the upper right.

The transportation expense application approval support system can also determine whether or not the searched station name m matches the station name entered in the transportation expense application (# 15). If they do not match, the last station that was applied for in the transportation expense application and the last station that was searched by the transportation expense application approval support system are one by issuing an alarm or setting a flag. You can also notify the approver that you have not done so (# 16).

In this way, the approver can easily check the contents of the transportation expense application form. Further, the approval screen β displays buttons for operations (approval (y1), rejection (y2), remand (y3)) according to these check results. The approval screen β also displays a button for email notification (y4) to the applicant.

In this way, the transportation expense application approval support system can improve the efficiency of the approval work by the approver for the transportation expense application for railways.

In the above, the example in which the determination # 15 is performed based on the station name match has been described, but as a modification, the determination # 15 can also be performed based on the station ID match. In this case, the station ID is entered in the transportation expense application form instead of the station name such as the boarding station m1 or the getting-off station m2, and the transportation expense application approval support system searches for search # 13 and search # 14 (search # 14'). This is done by determining whether or not the station IDi searched in the above matches the station IDi entered in the transportation expense application form.

The above has specifically explained the approval support process for transportation expense applications related to railways, but as explained below, the transportation expense application approval support system is used not only for transportation expense applications related to railways, but also for transportation related to buses and taxis. It can also be applied to the approval support process of the expense application form.

FIG. 7 is a flow chart showing the flow of the transportation expense application approval processing for buses and taxis by the transportation expense application approval support system.

When the approver approves the transportation expense application for buses and taxis submitted by the applicant, the approver activates the transportation expense application approval support system from the groupware menu. Then, as shown in the operation screen E, based on the visit date and time a and the visitor person in charge b entered in the transportation expense application form, the visit information DB 10 is associated with the visit date and time a and the visitor person in charge b. Search for the existing customer IDc (search # 21).

The transportation expense application approval support system further searches the customer position f associated with the customer IDc searched by the search # 21 from the customer information DB 20 (search # 22).

As shown in the operation screen F, the transportation expense application approval support system further obtains the station position p associated with the station ID2 from the station master 40 based on the getting-off station ID2 entered in the transportation expense application. Search (Search # 23).

The transportation expense application approval support system further calculates the distance t between the customer position f searched by search # 22 and the station position p searched by search # 23 (# 24). The distance t is the distance between the customer position f and the station position p of the station closest to the customer position f.

The transportation expense application approval support system further displays the distance t from a display or the like (# 25).

The transportation expense application approval support system further compares the distance t with the specified threshold (# 26). The threshold condition can be, for example, a threshold distance that is the distance at which the use of a bus or taxi is permitted. Such a threshold distance is determined individually for each company, for example, 1.2 km. Then, when the distance t is greater than or equal to the threshold distance, the approver can permit the use of a bus or taxi, while when the distance t is less than the threshold distance, the approver can permit the use of a bus or taxi. You can deny the use of. The threshold distance may be different for buses and taxis. Further, as an additional threshold condition, traffic information, weather information, time zone information, etc. can be appropriately added to the threshold distance and applied.

The transportation expense application approval support system can also calculate the fare for a bus or taxi based on the distance t, create an approval screen γ as illustrated in FIG. 8, and display it on the display. The method of calculating the fare is not particularly limited in the present invention, and for example, the fare calculation may be performed using each fare table published by the bus company and the taxi company.

FIG. 8 is a conceptual diagram showing an example of an approval screen displayed on the display when the transportation expense application approval processing for a bus or taxi is performed by the transportation expense application approval support system.

On the approval screen γ, as item 1 (NO.1), the customer name d corresponding to the customer IDc searched by the search # 21 and the transportation expense application form as illustrated in the operation screen F are entered. The transportation system (railway) v, the name m of each station corresponding to the boarding station ID1 and the getting-off station ID2, and the amount q2 are displayed. Further, as item 2 (NO.2), the transportation system (taxi) u and the amount q1 entered in the transportation expense application form are displayed as illustrated on the operation screen E. Further, the outlet r3 may be displayed at the transportation (taxi) u, and the station name m, the customer name d, and the distance t may be displayed as appropriate. The blowout r3 is hidden by tapping the x mark displayed in the upper right.

By referring to such an approval screen γ, the approver can easily check the contents of the transportation expense application form for buses and taxis. Then, when it can be determined that the content is appropriate, the approval operation can be performed by clicking the approval w button or the like. On the other hand, if it cannot be determined that the content is appropriate, the transportation expense application can be returned to the applicant by any appropriate means.

In this way, the transportation expense application approval support system can also improve the efficiency of approval work by the approver for the transportation expense application for buses and taxis.

Next, a case where new information is accumulated in the history information DB 30 based on the approved expense settlement information will be described.

FIG. 9 is a flow chart showing the flow of update processing of the settlement history information database and the route amount history database in the transportation expense application approval support system.

The operation screen G exemplifies the items included in the approved transportation expense application form.

In the example shown in FIG. 9, the approved transportation expense application includes the visit date and time a, the person in charge of visit b, the transportation (railway) v, the boarding station ID, the getting-off station ID, and the amount q1 as items. ing.

The transportation expense application approval support system is linked from the visit information DB 10 to the visit date and time a and the person in charge b included in the transportation expense application by using the items included in the approved transportation expense application. Search for the customer IDc (search # 31).

The transportation expense application approval support system further searches the customer position f associated with the customer IDc searched by the search # 31 from the customer information DB 20 (search # 32).

The transportation expense application approval support system further searches the station position p associated with the station IDi included in the approved transportation expense application form from the station master 40 (search # 33).

The transportation expense application approval support system was further searched by the visit date and time a, the visitor b, and the station ID, the customer IDc searched by search # 31, and search # 32 included in the approved transportation expense application. The customer position f and the station position p searched by the search # 33 are linked and saved in the settlement history information DB 30 (# 34). Further, at the time of saving, the application date h as the saved date and the applicant IDs which are the identification information of the person who executed the saving operation are also saved in association with these.

In addition, the transportation expense application approval support system links the boarding station ID, the getting-off station ID, the visitor b, and the amount q1 included in the approved transportation expense application, and the station ID1 and the station ID2, respectively. , The visitor b, and the amount q1 are stored in the route amount history DB 50 (# 35).

By using the settlement history information DB 30 and the route amount history DB 50 in which new information is accumulated in the transportation expense application creation support system and the transportation expense application approval support system, the transportation expense application creation support system and the transportation expense application creation support system can be used. Since the accuracy of the search performed by the transportation expense application approval support system is improved, the reliability of the transportation expense application creation support system and the transportation expense application approval support system can be further improved.

The best mode for carrying out the present invention has been described above with reference to the accompanying drawings, but the present invention is not limited to such a configuration. Within the scope of the claimed technical idea, those skilled in the art can come up with various modifications and modifications, and these modifications and modifications are also the technical scope of the present invention. It is understood that it belongs to.

10 Visit information database 20 Customer information database 30 Settlement history information database 40 Station master 50 Route amount history database

Claims (4)

It is a system to support the approval work of the approver for the transportation expense application for the use of buses and taxis.
A visit information database that stores the customer ID of the customer who is the visit destination, the date and time of the visit, and the person in charge of the visit,
A customer information database that stores the customer ID and customer location of the customer in association with each other,
A station master that stores the station name, station ID, and station position in association with each other,
A first search means for searching the visit date and time and the customer ID associated with the visitor from the visit information database based on the visit date and time and the visitor entered in the transportation expense application form.
A second search means for searching the customer information database for the customer position associated with the customer ID searched by the first search means, and
A third search means for searching the station position associated with the station ID from the station master based on the station ID of the station entered in the transportation expense application form.
A calculation means for calculating the distance between the customer position searched by the second search means and the station position searched by the third search means, and
A transportation expense application approval support system including a display means for displaying the distance calculated by the calculation means so that the approver can permit or deny the use of a bus or taxi. The distance calculated by said calculating means, and e further Bei comparison means for comparing the listening distance, said threshold distance, bus and taxi when the distance calculated by said calculating means is the threshold distance or more The transportation expense application approval support system according to claim 1 , which is the distance at which the use of the taxi is permitted. It is a method implemented by the transportation expense application approval support system to support the approval work of the approver for the transportation expense application for the use of buses and taxis.
The transportation expense application approval support system
A visit information database that stores the customer ID of the customer who is the visit destination, the date and time of the visit, and the person in charge of the visit,
A customer information database that stores the customer ID and customer location of the customer in association with each other,
Using the station name of the station, the station ID, and the station master that stores the station position in association with each other,
Based on the visit date and time and the visitor entered in the transportation expense application form, the first search step of searching the visit date and time and the customer ID associated with the visitor from the visit information database, and
A second search process for searching the customer information database for the customer position associated with the customer ID searched by the first search process, and
A third search process for searching the station position associated with the station ID from the station master based on the station ID of the station entered in the transportation expense application form, and
A calculation process for calculating the distance between the customer position searched by the second search process and the station position searched by the third search process, and a calculation process.
A method of carrying out a display step of displaying the distance calculated by the calculation step so that the approver can permit or deny the use of a bus or taxi. It is a program to support the approval work of the approver for the transportation expense application for the use of buses and taxis.
A visit information database that stores the customer ID of the customer who is visiting, the date and time of the visit, and the person in charge of the visit,
A customer information database that stores the customer ID and customer location of the customer in association with each other,
Using the station name of the station, the station ID, and the station master that stores the station position in association with each other,
To the processor
A first search function that searches the visit date and time and the customer ID associated with the visitor from the visit information database based on the visit date and time and the visitor entered in the transportation expense application form.
A second search function that searches the customer information database for the customer position associated with the customer ID searched by the first search function.
A third search function for searching the station position associated with the station ID from the station master based on the station ID of the station entered in the transportation expense application form.
A calculation function for calculating the distance between the customer position searched by the second search function and the station position searched by the third search function, and
A program for realizing a display function for displaying the distance calculated by the calculation function so that the approver can permit or deny the use of a bus or taxi.

Images