JP2014029601A - Travel expense adjustment system, travel expense adjustment method, travel expense adjustment program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a travel expense adjustment system, a travel expense adjustment method, and a travel expense adjustment program to support an effective adjustment of travel expenses for business trips.SOLUTION: A controlling unit 21 in an application support server 20, after authenticating an applicant, specifies a travel schedule yet to be adjusted, acquires use information, performs filtering processing before executing schedule collation processing. The controlling unit 21, when the travel schedule and the use information are matched, identifies a place of departure and a destination, acquires a route candidate, specifies a season ticket section, and calculates travel expenses. The controlling unit 21, when the travel schedule and the use information are not matched, executes processing for confirming mismatch. The controlling unit 21, when a schedule is not registered, performs processing for posterior registration of the schedule. The controlling unit 21 acquires the route candidate for a schedule which does not match the use information.

Description

  The present invention relates to a transportation expense settlement system, a transportation expense settlement method, and a transportation expense settlement program for supporting settlement of transportation expenses paid on the road such as a business trip.

  When an employee goes out in a company, the employee often changes the transportation expenses of the transportation used by the employee once and pays it later. At the time of settlement of the transportation expenses, it is necessary to submit to the company an application form in which the transportation expenses and route information changed by the employees are entered. For this reason, it is necessary to record the route and amount used for the movement, which is a burden on the employee.

In view of this, techniques for efficiently applying for transportation expenses have been studied (see, for example, Patent Documents 1 and 2).
In the technique described in Japanese Patent Laid-Open No. 2004-228561, a travel expense adjustment process is performed by linking a bus / railway usage history read from an IC card reader connected to a multifunction peripheral and attendance management data. In the technique described in this document, a multi-function machine connected to be communicable with an outing payment application server that accepts an application for outing payment is used. After logging in to the MFP according to the user identification information, the history information read from the IC card is stored. Then, out of the history information, the outing payment information that does not include the history information corresponding to the regular route that does not generate a fare every time the transportation is used is displayed on the display unit. And the instruction | indication transmitted to an outing payment application server as an outing payment application is received.

  In the technique described in Patent Document 2, the transportation fee is applied at the same time as using the transportation facility. In the technology described in this document, the transportation processing unit reads the organization ID and the user ID recorded on the IC card presented by the user at the time of charge settlement related to the use of the transportation, and the user's Read biological information. Then, the organization ID, user ID, biometric information, and fee information are transmitted to a transportation cost processing unit such as a company. Then, the transportation cost processing unit authenticates the organization ID, user ID, and biometric information, and determines whether the work record registered in the work record information database and the use time of the transportation facility are appropriate according to the authentication result. Then, only when it is recognized that it is appropriate, the fee settlement related to the use of transportation is performed.

Japanese Patent Laying-Open No. 2011-118881 (first page, FIG. 1) Japanese Patent Laying-Open No. 2011-86137 (first page, FIG. 1)

  By using the techniques described in these patent documents, it is possible to apply for transportation expense adjustment using the usage information stored in transportation cards such as IC cards. However, there are cases where a plurality of routes can be used even when going out to a specific place. Therefore, if the route assumed by the company is different from the route actually used by the employee, the application based on the usage information may not be appropriate. In addition, when going out in a business activity, the approval of a superior or the like is usually obtained in advance. Furthermore, when there are a plurality of business activity bases, the user may repeatedly go out to a specific place. Even in such a case, it is desirable to be able to reduce the burden of application and approval for transportation expense settlement.

  The present invention has been made in order to solve the above-mentioned problems. A transportation expense settlement system, a transportation expense settlement method, and a transportation expense for supporting efficient settlement of transportation expenses paid on a business trip or the like. The purpose is to provide a settlement program.

  In order to solve the above problems, the invention described in claim 1 includes a schedule storage unit that records an event schedule including a user, an event place, and an event period, and an application management storage that records an application for payment of transportation expenses. And a control part for supporting application for transportation expense settlement, wherein the control part acquires a user event schedule from the schedule storage part, and the user For the recording medium used at the time of use of the institution, the usage information including the usage date, the movement source, and the movement destination is acquired as a collation target. If the usage information corresponding to the event schedule can be specified based on the verification result, the usage information is included in the usage information. That an application for settlement of travel expenses and required to be registered in the application management storage unit.

  The gist of the invention described in claim 2 is that, in the transportation expense settlement system according to claim 1, the usage information of the transportation facility corresponding to the event period of the event schedule is acquired as a collation target.

  The invention according to claim 3 further includes a user information storage unit that records working hours in the transportation expense settlement system according to claim 1 or 2, wherein the control unit is configured to store the user information from the user information storage unit. The gist of the invention is to specify the working hours of the user and obtain only the usage information of the working hours as a verification target in the transportation usage information.

  According to a fourth aspect of the present invention, in the transportation expense settlement system according to any one of the first to third aspects, the control unit specifies a schedule immediately before the event schedule in the schedule storage unit, and The gist is to specify the event location of the immediately preceding schedule as a movement source, and to collate the event schedule with the usage information using the movement source.

  The invention according to claim 5 is the transportation expense adjustment system according to any one of claims 1 to 4, wherein the control unit specifies a schedule immediately after the event schedule in the schedule storage unit, and The gist is to specify the event location of the schedule immediately after as the destination, and to collate the event schedule with the usage information using the destination.

  According to a sixth aspect of the present invention, in the transportation expense adjustment system according to any one of the first to fifth aspects, the control unit moves from the source to the destination based on an event period of the event schedule. The gist is that when the failure information on the transportation route is retrieved and the failure information is acquired, the event schedule is compared with the usage information based on the failure information.

  According to a seventh aspect of the present invention, in the transportation expense settlement system according to any one of the first to sixth aspects, when the control unit acquires usage information that does not correspond to the event schedule, the event schedule The gist is to output a reminder to confirm this.

  The invention according to claim 8 is the transportation expense settlement system according to any one of claims 1 to 7, wherein when the control unit obtains approval information about the transportation expense settlement application, The gist of the invention is to execute the transportation cost charging process on a recording medium used by the user when using the transportation facility.

  The invention according to claim 9 is a schedule storage unit that records an event schedule including a user, an event place, and an event period, an application management storage unit that records an application for transportation expense settlement, and an application for transportation expense settlement. A method for supporting transportation expense settlement using a transportation expense settlement system including a control section for supporting, wherein the control section acquires a user event schedule from the schedule storage section, and the user For the recording medium to be used when using the transportation facility, the usage information including the usage date, the movement source, and the movement destination is acquired as a verification target, and the event location and event period of the event schedule, the usage date of the usage information, the movement source If the usage information corresponding to the event schedule can be identified based on the verification result, An application for settlement of Murrell transportation costs and required to be registered in the application management storage unit.

  The invention according to claim 10 includes a schedule storage unit that records an event schedule including a user, an event place, and an event period, an application management storage unit that records an application for transportation expense settlement, and an application for transportation expense settlement. A program for supporting transportation expense settlement using a transportation expense settlement system comprising a control section for supporting, wherein the control section acquires a user event schedule from the schedule storage section, and the user For the recording medium to be used when using the transportation facility, the usage information including the usage date, the movement source, and the movement destination is acquired as a verification target, and the event location and event period of the event schedule, the usage date of the usage information, the movement source If the usage information corresponding to the event schedule can be identified based on the collation result based on the collation result, An application for settlement of travel expenses included in the information and summarized in that to function as a means for registering the application management storage unit.

(Function)
According to the invention described in claim 1, 9 or 10, the control unit obtains the event schedule of the user from the schedule storage unit and uses the date of use for the recording medium that the user uses when using the transportation facility. The usage information including the movement source and the movement destination is acquired as a collation target. The event location and event period of the event schedule are compared with the usage date, source and destination of the usage information, and if usage information corresponding to the event schedule can be identified based on the verification result, the usage information Register the application for payment of included transportation expenses in the application management storage unit. Thereby, the transportation expenses can be settled based on the usage information corresponding to the event schedule.

  According to invention of Claim 2, the utilization information of the transport system corresponding to the event period of an event schedule is acquired as collation object. Thereby, the usage information according to the event schedule can be specified.

  According to invention of Claim 3, a control part specifies a user's working time from a user information storage part. In the usage information of transportation facilities, only the usage information of working hours is acquired as a verification target. Thereby, the usage information can be specified in consideration of the work status of the user.

  According to the fourth aspect of the present invention, the control unit specifies the immediately preceding schedule of the event schedule and specifies the event location of the immediately preceding schedule as the movement source in the schedule storage unit. Then, using the movement source, the event schedule and the usage information are collated. Thereby, the movement origin for calculating a transportation expense can be specified based on the immediately preceding schedule.

  According to the invention described in claim 5, the control unit specifies the schedule immediately after the event schedule in the schedule storage unit, and specifies the event location of the immediately following schedule as the destination. Then, using the destination, the event schedule is collated with the usage information. Thereby, based on the schedule immediately after, the destination for calculating a transportation expense can be specified.

  According to the invention described in claim 6, when the control unit retrieves the failure information about the transportation route from the movement source to the movement destination based on the event period of the event schedule and acquires the failure information, Based on the information, the event schedule and the usage information are collated. Accordingly, it is possible to calculate the transportation cost to be settled in consideration of a failure that has occurred in the transportation facility.

  According to the seventh aspect of the present invention, when the control unit acquires the usage information that does not correspond to the event schedule, it outputs a warning for confirming the event schedule. Thereby, the event schedule and the usage information can be matched by the post-registration of the event schedule.

  According to the invention described in claim 8, when the control unit obtains the approval information for the application for the settlement of transportation expenses, the transportation charge is charged to the recording medium used by the user when using the transportation facility. Execute the process. Thereby, payment of transportation expenses can be received efficiently.

  According to the present invention, it is possible to provide a transportation expense settlement system, a transportation expense settlement method, and a transportation expense settlement program for supporting efficient settlement of transportation expenses paid on a business trip or the like.

The system schematic of embodiment of this invention. It is explanatory drawing of the data recorded on each data memory | storage part of embodiment of this invention, Comprising: (a) is an authentication dictionary memory | storage part, (b) is an application management memory | storage part, (c) is a schedule memory | storage part, (d ) Is an explanatory diagram of the employee management information storage unit. Explanatory drawing of the process sequence of 1st Embodiment. Explanatory drawing of the process sequence of 1st Embodiment. Explanatory drawing of the process sequence of 1st Embodiment. It is explanatory drawing of the process sequence of 2nd Embodiment, Comprising: (a) is an application assistance process, (b) is explanatory drawing of a route collation process. It is explanatory drawing of other embodiment, Comprising: (a) is normal movement, (b) is continuous movement, (c) is explanatory drawing of a process sequence. It is explanatory drawing of the process sequence of other embodiment, Comprising: (a) is evidence confirmation processing, (b) is explanatory drawing of the output process of a confirmation screen. Explanatory drawing of the process sequence of other embodiment.

<First Embodiment>
DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments embodying the present invention will be described with reference to FIGS. In the present embodiment, it is assumed that when a company employee goes out on a business trip or the like using a transportation facility, the transportation expenses paid for the outing are settled.

  In this embodiment, as shown in FIG. 1, when going out using a transportation facility, a recording medium 70 on which usage information of electronic value including electronic money is recorded is used. Examples of the recording medium 70 include a portable terminal 71 and a transportation card 72. Note that the recording medium 70 is not limited to the portable terminal 71 or the transportation card 72. The mobile terminal 71 and the transportation card 72 are used for electronic value usage information (use date, time, entrance station information, entry station information, usage amount, balance, usage notes, etc.), mobile terminal 71 and traffic. Data relating to a medium code for identifying the institution card 72 is held.

  When using transportation, the portable terminal 71 or transportation card 72 is held over the card reader of the ticket gate 80. In this case, the ticket gate 80 records the boarding station code for specifying the movement source in the portable terminal 71 or the transportation card 72 as the usage information at the entrance station which is the boarding station. On the other hand, the ticket gate 80 records the getting-off station code for specifying the moving destination in the portable terminal 71 or the transportation card 72 as the usage information at the departure station which is the getting-off station. Further, the ticket gate 80 calculates the transportation cost from the boarding station to the getting-off station, and subtracts it from the balance recorded in the portable terminal 71 and the transportation card 72. Further, the ticket gate 80 transmits the usage information together with the medium code to the transportation server 85. The transportation server 85 accumulates usage information in the usage information storage unit in association with the medium code.

  Further, when the mobile terminal 71 is charged with electronic value in order to settle the transportation expenses, the amount for transportation expenses settlement is deducted from the financial institution account held by the company and recorded in the portable terminal 71. Add to balance.

  In addition, when the electronic value is charged to the transportation card 72, it is added to the balance recorded on the transportation card 72 using a card charging terminal such as a POS terminal in a ticket machine or a store (for example, a convenience store). To do.

The settlement of the transportation expenses using such electronic value is performed based on the application of the user (going out) and the approval of the approver. In order to settle the transportation expenses, an application support server 20 shown in FIG. 1 is used.
The application support server 20 is connected to the client terminals (10, 15), the schedule management server 30, and the employee management server 50 via a network such as a LAN. Further, the application support server 20 is connected to the traffic information providing server 60 and the transport agency server 85 via a network such as the Internet.

  The client terminals (10, 15) are computer terminals used by users such as applicants and approvers. The applicant uses the client terminal 10 to apply for transportation expenses. The approver confirms the application content using the client terminal 15 and approves it. The client terminals (10, 15) include a display unit configured from a display (not shown) and the like, and an input unit configured from a keyboard, a pointing device, and the like.

  The application support server 20 is a computer system that supports employee transportation expenses. As shown in FIG. 1, the application support server 20 includes a control unit 21, an authentication dictionary storage unit 22, and an application management storage unit 23. In addition, the application support server 20 has an address storage unit that records an address management record in which data related to an address is recorded with respect to an identifier (base identifier) for specifying a place to go (such as a company base or a customer). Not shown).

  The control unit 21 is realized by control means (CPU, RAM, ROM, etc.). And this control part 21 performs the process (each process of a payment information acquisition stage, an application assistance stage, a payment assistance stage, etc.) mentioned later. By executing the transportation expense adjustment program for this purpose, the control unit 21 functions as each means such as the adjustment information acquisition means 211, the application support means 212, the payment support means 213, and the like.

  The payment information acquisition means 211 executes a process of acquiring schedule information about a target (outing) for which the transportation expenses are to be adjusted. This settlement information acquisition means 211 includes a storage unit (settlement target memory) that temporarily stores transportation cost settlement targets (movement source, movement destination).

The application support means 212 executes a process for applying for transportation expenses based on the schedule information.
The payment support means 213 executes processing for supporting payment of transportation expenses to be settled for the user.

  As shown in FIG. 2A, an authentication dictionary record 220 for authenticating a transportation expense adjustment target in advance is recorded in the authentication dictionary storage unit 22. This authentication dictionary record 220 is recorded when conditions for authenticating in advance are registered for going out based on a schedule. This authentication dictionary record 220 includes data relating to an authentication management code, authentication conditions, departure place, destination, route, amount of money, and supplementary matters.

Data related to an identifier for specifying each authentication condition is recorded in the authentication management code data area.
In the authentication condition data area, data related to conditions for specifying the outing that has been authenticated in advance is recorded. This authentication condition can be set according to the department or project to which the employee belongs.

  In each data area of the departure place and the destination, data relating to an identifier for identifying the departure place and the destination that have been authenticated in advance is recorded. For this starting point and destination, it is possible to use each base of a company or a base identifier or address of a place where the user is away.

In the route data area, data relating to the transportation route (type of transportation, boarding station, getting-off station) from the departure point to the destination is recorded.
In the amount data area, data relating to transportation costs required for traveling using this route is recorded. The route and the amount of money are periodically acquired from the traffic information providing server 60 described later, and updated based on the route information.

  In the supplementary matter data area, data relating to supplementary matters regarding the authentication condition is recorded. As a supplementary matter, for example, the history (reason) of registration of the authentication dictionary record 220 is recorded.

  In the application management storage unit 23, as shown in FIG. 2B, an application management record 230 for managing the application for transportation expense settlement is recorded. This application management record 230 is generated and recorded when the transportation expense adjustment target is extracted. The application management record 230 includes data relating to an application management code, an applicant, an affiliation code, an approver, an application date, a title, a usage date, a route, an amount, a memo, an authentication status, an approval status, and a payment status. .

In the application management code data area, data relating to an identifier for specifying each application is recorded.
In the applicant data area, data relating to an identifier for identifying an employee (applicant) who applies for transportation expense settlement is recorded. In the present embodiment, an employee code recorded in the employee management information storage unit 52 is used as an identifier for identifying the applicant.

In the affiliation code data area, data relating to an identifier for specifying the organization (department) to which the applicant belongs is recorded.
In the approver data area, data relating to an identifier for identifying an employee (approver) who approves an application in this organization is recorded. In the present embodiment, an employee code recorded in the employee management information storage unit 52 is used as an identifier for identifying the approver.

In the application date data area, data relating to the date of application for transportation expense settlement is recorded.
In the title data area, data relating to an identifier for identifying an event of a schedule that is a target of transportation expense settlement is recorded. For example, a title representing an event or a schedule management code is used.

In the use date data area, data relating to the date (start, end) of using the transportation facility is recorded.
In the route data area, data relating to the transportation route used for going out is recorded. This route includes information on the type of transportation used and information on the boarding station and the getting-off station.

In the amount data area, data relating to the amount of transportation expenses is recorded.
In the memo data area, data relating to the explanation necessary for this application is recorded.
In the authentication status data area, an identifier for determining the presence or absence of authentication (pre-authentication) prior to the approval request is recorded. In this data area, when pre-authentication is performed using the authentication dictionary storage unit 22, an authenticated flag is recorded.

  In the approval status data area, a flag for specifying the approval status of the application for transportation expense settlement is recorded. When an approval request is made to the approver, a pending flag is recorded in this data area. Also, an approved flag is recorded when the approval is given by the approver, and a return flag is recorded when it is returned.

  In the payment status data area, a flag for identifying the payment status of the transportation expenses for going out in this schedule is recorded. When the application management record 230 is registered, an unsettled flag is recorded as an initial value in this data area. Then, when the travel expenses for the outing in this event are settled, a settled flag is recorded.

  The schedule management server 30 is a computer system that manages employee schedules. The schedule management server 30 includes a schedule storage unit 32 for managing employee schedules.

  As shown in FIG. 2C, a schedule management record 320 is recorded in the schedule storage unit 32 regarding a schedule (event schedule) of events (including going out) involving employees. The schedule management record 320 is recorded when a schedule for each event related to an employee is registered. The schedule management record 320 includes data relating to a schedule management code, employee code, affiliation code, registration date, title, start date / time, end date / time, event location, and explanation. Further, the schedule management record 320 for going out includes data relating to an outing approval status, a report approval status, and a payment status. In addition, you may make it record the data regarding going-out approval status-payment status in a memory | storage part different from the schedule memory | storage part 32. FIG. In this case, data relating to the outing approval status to the payment status is recorded in association with the schedule management code.

Data relating to an identifier for specifying each schedule is recorded in the schedule management code data area.
In the employee code data area, data relating to an identifier (an employee code recorded in the employee management information storage unit 52) for identifying an employee (user) related to the schedule is recorded.

In the affiliation code data area, data relating to an identifier for specifying the organization (department) to which the employee belongs is recorded.
In the registration date data area, data related to the date and time when this schedule is registered is recorded.

  In the title data area, data related to the title of the event (event content) of this schedule is recorded. As this title, for example, “XX development meeting participation” is recorded.

  In the start date / time data area, data regarding the start time (year / month / day and time) of this event period for this employee is recorded. In the case of moving directly from the home to the event place, a “direct output” flag is recorded.

  In the end date / time data area, data relating to the end time (year / month / day and time) of the event period for the employee is recorded. In the case of moving directly from the event location to the home, a “bounce” flag is recorded.

  In the event location data area, data relating to the location where this event is performed is recorded. In this data area, data relating to the base identifier and address of this base is recorded. Further, in this event place data area, information (outing flag) for identifying whether or not the event needs to go out is recorded. The event location is set by selecting from destinations registered in the authentication dictionary storage unit 22 or by directly inputting the event location if it is not registered in the authentication dictionary storage unit 22. When going out for an event, this event location is used as a destination.

In the explanation data area, data related to the detailed contents of the event (event contents) is recorded. For example, the purpose of the event is recorded in this data area.
In the outing approval status data area, a flag for identifying the approval status of the approver is recorded for this schedule. When the schedule management record 320 is registered, an unapproved flag is recorded as an initial value in this data area. When the approver approves the schedule for this schedule, an approved flag is recorded in this data area.

  In the report approval status data area, a flag for identifying the approval status of the approver is recorded for the report about this event. When the schedule management record 320 is registered, an unapproved flag is recorded as an initial value in this data area. When the approver confirms the report on the event of this schedule, the approved flag is recorded in this data area.

  In the payment status data area, a flag for identifying the payment status of the transportation expenses for going out in this schedule is recorded. When the schedule management record 320 is registered, an unsettled flag is recorded as an initial value in this data area. Then, when the travel expenses for the outing in this event are settled, a settled flag is recorded.

  The employee management server 50 is a computer system that manages employee attribute information and work information. The employee management server 50 includes an employee management information storage unit 52 for managing various information of each employee.

  The employee management information storage unit 52 functions as a user information storage unit. In the employee management information storage unit 52, as shown in FIG. 2D, an employee management record 520 that records employee attribute information is recorded. . This employee management record 520 is recorded when an employee is registered. This employee management record 520 includes data relating to an employee code, password, affiliation code, contact information, home address, work place, commuter pass section, and use medium.

Data relating to an identifier for identifying each employee is recorded in the employee code data area.
Data related to information (password) for authenticating the employee is recorded in the password data area.

In the affiliation code data area, data relating to an identifier for specifying the organization (department) to which the employee belongs is recorded.
In the contact data area, data relating to the contact information (e-mail address or telephone number) of the employee is recorded.

In the home address data area, data regarding the home address of the employee is recorded.
In the work location data area, data relating to an identifier for identifying a base where the employee is working is usually recorded.

  In the commuter pass section data area, data related to the commuting route to which the commuter pass is given is recorded up to the home and work place. In this data area, information related to the boarding / exiting station for commuting and the transportation system to be used is recorded.

  In the utilization medium data area, data relating to an identifier for identifying the recording medium 70 used when the employee pays the travel expenses when going out is recorded. In this data area, data relating to a medium type such as the portable terminal 71 or the transportation card 72 and a medium code is recorded.

  Further, the employee management information storage unit 52 stores an approver table for specifying an approver in each organization (department). In this approver table, the employee code of the approver is recorded for the affiliation code.

  The traffic information providing server 60 provides route information (a type of transportation to be used, a transfer guide, a required time and a charge) when using the transportation. Specifically, the traffic information providing server 60 acquires information on the boarding station and the getting-off station, and provides information on the use route between the boarding station and the getting-off station. This route information includes information on the use transportation, required time, and fee.

Next, the authentication process in this embodiment is demonstrated according to FIGS. Here, the application support process (FIG. 3), the confirmation process (FIG. 4), and the payment support process (FIG. 5) will be described in this order.
(Application support processing)
First, the application support process will be described with reference to FIG. This process is executed periodically, for example, in order to support the settlement of transportation expenses for the previous month at the beginning of the month.

  First, the control unit 21 of the application support server 20 executes an unsettled outing schedule specifying process (step S1-1). Specifically, the payment information acquisition unit 211 of the control unit 21 accesses the schedule storage unit 32 of the schedule management server 30. Then, the settlement information acquisition unit 211 identifies the schedule management record 320 in which the outing flag is recorded in the event place data area and the application for transportation expense settlement is not performed. Here, the schedule management record 320 in which the approved flag is recorded in the outing approval status data area and the report approval status data area, and the record in which the unapplied flag is recorded in the settlement status data area is extracted.

And the control part 21 of the application assistance server 20 specifies the schedule of a process target in the extracted schedule management record 320, and performs the following processes.
Here, the control unit 21 of the application support server 20 executes a move source and move destination specifying process (step S1-2). Specifically, the application support unit 212 of the control unit 21 accesses the employee management server 50. Then, the settlement information acquisition unit 211 extracts an employee management record 520 in which the employee code of the schedule management record 320 to be processed is recorded from the employee management information storage unit 52. Next, the payment information acquisition unit 211 acquires the work location information of the employee from the employee management record 520. Further, when the “direct output” flag and the “direct return” flag are recorded in the start date / time data area and the end date / time data area of the schedule management record 320, the settlement information acquisition unit 211 reads from the employee management record 520, Get the home address of this employee.

Then, the settlement information acquisition means 211 identifies the movement source and the movement destination of the forward path and the return path based on the presence / absence of the “direct output” flag and the “direct return” flag.
If neither the “direct” flag nor the “bounce” flag is recorded in the schedule management record 320, the settlement information acquisition unit 211 sets the work location as the movement source and the event location as the movement destination for the outbound route. For the return trip, the event location is specified as the source and the work location is specified as the destination.

  Further, when only the “direct output” flag is recorded in the schedule management record 320, the settlement information acquisition unit 211 identifies the home address as the movement source and the event place as the movement destination for the forward path, and for the return path. , Specify the event location as the source and the work location as the destination.

  In addition, when only the “bounce” flag is recorded in the schedule management record 320, the settlement information acquisition unit 211 identifies the work location as the movement source and the event location as the movement destination for the outward trip, and for the return trip Identify the event location as the source and the home address as the destination.

Further, when both the “direct output” flag and the “direct return” flag are recorded in the schedule management record 320, the settlement information acquisition unit 211 sets the home address as the movement source and the event location as the movement destination for the outbound route. As for the return trip, the event location is specified as the source and the home address is specified as the destination.
Then, the payment information acquisition unit 211 temporarily stores the transportation cost from the specified movement source to the movement destination in the payment target memory as a payment target.

  Next, the control part 21 of the application support server 20 performs a collation process with authentication conditions (step S1-3). Specifically, the application support unit 212 of the control unit 21 compares the title, event location, and description recorded in the schedule management record 320 with each authentication condition recorded in the authentication dictionary storage unit 22.

  Next, the control part 21 of the application support server 20 performs the determination process about whether the authentication conditions are satisfied (step S1-4). Specifically, the application support unit 212 of the control unit 21 determines that the authentication condition is satisfied when the content recorded in the schedule management record 320 corresponds to the authentication condition.

  When it is determined that the content recorded in the schedule management record 320 does not correspond to the authentication condition and does not satisfy the authentication condition (“NO” in step S1-4), the control unit 21 of the application support server 20 A route candidate acquisition process is executed (step S1-5). Specifically, the application support means 212 of the control unit 21 includes the date / time of the start date / time, the outbound information from the source (departure point) to the destination (destination), the date / time of the end date / time, and the source ( Return route information from the destination) to the destination (departure point) is provided to the traffic information providing server 60. When a base identifier is recorded as the event location, the application support unit 212 specifies an address management record in which the base identifier is recorded in an address storage unit (not shown), and manages the address. Get data about the location address from the record. Then, the application support unit 212 identifies a station that exists within a predetermined range from this address as a movement source or a movement destination.

  Next, the application support unit 212 acquires round-trip route information (route candidate) corresponding to the forward route information and the return route information from the traffic information providing server 60. This route information includes information on the required time and the amount of transportation expenses. Then, the application support unit 212 assigns a new application management code, generates an application management record 230 in which the acquired route information (route, amount) is recorded, and registers it in the application management storage unit 23. In the application management record 230, the employee code, affiliation code, and title recorded in the schedule management record 320 are recorded. Furthermore, the date of start and end date are recorded in the use date data area. When the traffic information providing server 60 acquires a plurality of route candidates, the application support unit 212 records all the route information in the route data area of the application management record 230.

  Next, the control unit 21 of the application support server 20 executes an unauthenticated recording process (step S1-6). Specifically, the application support unit 212 of the control unit 21 records an unauthenticated flag in the authentication status data area of the generated application management record 230.

  On the other hand, when the content recorded in the schedule management record 320 corresponds to the authentication condition and it is determined that the authentication condition is satisfied (in the case of “YES” in step S1-4), the control unit 21 of the application support server 20 An authenticated route acquisition process is executed (step S1-7). Specifically, the application support unit 212 of the control unit 21 acquires the route information recorded in the authentication dictionary record 220 that satisfies the authentication condition. Then, the application support unit 212 assigns a new application management code, generates an application management record 230 in which the acquired route information (route, amount) is recorded, and registers it in the application management storage unit 23. Also in this case, the employee code, the affiliation code, and the title recorded in the schedule management record 320 are recorded in the application management record 230. Furthermore, the date of start and end date are recorded in the use date data area.

  Next, the control unit 21 of the application support server 20 executes an authenticated recording process (step S1-8). Specifically, the application support unit 212 of the control unit 21 records an authenticated flag in the authentication status data area of the generated application management record 230.

  Next, the control unit 21 of the application support server 20 executes a commuter pass section specifying process (step S1-9). Specifically, the application support means 212 of the control unit 21 acquires commuter pass section information recorded in the employee management record 520 of this employee.

Next, the control unit 21 of the application support server 20 executes a transportation cost calculation process (step S1-10). Specifically, the application support unit 212 of the control unit 21 determines that the route recorded in the application management record 230 has a section that overlaps with the commuter pass section, the outbound route information and the return path excluding the overlapping section. Identify information (modification information). Then, the application support unit 212 transmits the correction information to the traffic information providing server 60 to acquire the correction route information (route, amount). Then, the application support unit 212 records the route and amount of the application management record 230 using the corrected route information.
The above process is repeated for all unsettled outing schedules.

  And the control part 21 of the application assistance server 20 performs a confirmation notification process (step S1-11). Specifically, the application support unit 212 of the control unit 21 acquires the employee code recorded in the newly registered application management record 230. Next, the application support unit 212 acquires contact information associated with the acquired employee code from the employee management information storage unit 52 of the employee management server 50. Then, the application support unit 212 transmits a confirmation notification to the acquired contact information. This confirmation notification includes a message indicating that the application for transportation expense settlement has been registered.

(Confirmation process)
Next, the confirmation process will be described with reference to FIG. This confirmation process is performed when the applicant applies for transportation expense settlement. Here, the applicant who has received the confirmation notification accesses the application support server 20 using the client terminal 10.

  First, the control part 21 of the application support server 20 performs an applicant authentication process (step S2-1). Here, user authentication processing for the applicant is performed. Specifically, the application support unit 212 of the control unit 21 outputs a user authentication screen on the display of the client terminal 10. This user authentication screen has an employee code and password entry field. The application support unit 212 acquires the employee code and password input on the user authentication screen, and performs user authentication using the employee management information storage unit 52 of the employee management server 50. If user authentication cannot be performed using the employee code and password, the use of the application support server 20 is rejected. On the other hand, when the user authentication is completed using the employee code and the password, the application support unit 212 temporarily stores the employee code specified by the user authentication.

  Next, the control part 21 of the application support server 20 performs the output process of a confirmation screen (step S2-2). Specifically, the application support means 212 of the control unit 21 is an application management record 230 in which an employee code authenticated by a user is recorded in the applicant data area, and an unapplied flag is recorded in the approval status data area. Extracted records. And the application support means 212 produces | generates the application confirmation screen which displayed the content of the extracted application management record 230 as a list. In this application confirmation screen, route information is output as a candidate route in association with the schedule date (start date and time and end date and time of the application management record 230). If a plurality of route candidates are recorded in the application management record 230, all route information is included as candidate routes on the application confirmation screen. Further, when an authenticated flag is recorded in the authentication status data area, an icon indicating that the authentication has been completed is included in the application confirmation screen.

  Further, in this icon, link information for specifying the authentication dictionary record 220 in the authentication dictionary storage unit 22 is recorded. By selecting this icon, the contents of the authentication dictionary record 220 can be displayed. Then, by confirming supplementary items in the authentication dictionary record 220, it is possible to determine whether or not authentication is appropriate.

  Then, the application support unit 212 outputs an application confirmation screen on the display of the client terminal 10. The applicant confirms the application contents using this application confirmation screen. When the confirmation of the application content is completed, the confirmation completion input is performed on the application confirmation screen. On the other hand, when the displayed route is different from the actually used route, the route is corrected on the application confirmation screen. Further, when a plurality of route candidates are included, the used route is selected. If an explanation is necessary for this application, the explanation is entered in the memo field of the application confirmation screen.

  And the control part 21 of the application assistance server 20 performs the determination process about whether it is a confirmation completion (step S2-3). Specifically, the application support unit 212 of the control unit 21 determines that the confirmation is completed when a confirmation completion input is performed on the authentication confirmation screen. On the other hand, when it is determined that the confirmation is not completed due to the correction input (in the case of “NO” in step S2-3), the control unit 21 of the application support server 20 executes a correction receiving process (step S2). -4). Specifically, the application support unit 212 of the control unit 21 updates the application management record 230 using the content corrected on the application confirmation screen.

  And the control part 21 of the application assistance server 20 performs the determination process about whether there exists any correction in the authenticated path | route (step S2-5). Specifically, the application support unit 212 of the control unit 21 confirms whether or not the authenticated flag is recorded in the corrected application management record 230.

  When the authenticated flag is recorded in the application management record 230 and it is determined that there is a correction in the authenticated route (in the case of “YES” in step S2-5), the control unit 21 of the application support server 20 is not authenticated. Is executed (step S2-6). Specifically, the application support unit 212 of the control unit 21 deletes the authenticated flag recorded in the authentication status data area of the application management record 230 and deletes the icon indicating that the application has been authenticated on the application confirmation screen. To do. Then, the process returns to step S2-3.

  On the other hand, when it is determined that there is no correction in the application management record 230 in which the authenticated flag is recorded in the authentication status data area and there is no correction in the authenticated route (in the case of “NO” in step S2-5), the application support server The control unit 21 of 20 skips the process of changing to unauthenticated (step S2-6) and returns to step S2-3.

  When it is determined that the confirmation is completed by inputting confirmation completion (in the case of “YES” in step S2-3), the control unit 21 of the application support server 20 executes an approval request process (step S2-). 7). Specifically, the application support unit 212 of the control unit 21 records a pending flag in the approval status data area of the application management record 230. Then, the application support unit 212 acquires the affiliation code recorded in the application management record 230 and acquires the employee code of the approver associated with the affiliation code in the approver table of the employee management server 50. The application support unit 212 records the approver's employee code in the approver data area of the application management record 230. Furthermore, the application support unit 212 acquires an email address associated with the approver's employee code from the employee management information storage unit 52 of the employee management server 50, and transmits an approval request to the email address. This approval request includes a message indicating that there is an unapproved transportation expense settlement application.

  The approver who has received the approval request accesses the application support server 20 using the client terminal 15. Also in this case, the control part 21 of the application support server 20 performs an approver authentication process (step S2-8). Here, the user authentication process for the approver is performed in the same manner as the user authentication process in step S2-1.

  Next, the control unit 21 of the application support server 20 executes an approval process (step S2-9). Specifically, the application support means 212 of the control unit 21 is an application management record 230 in which an employee code authenticated by a user is recorded in the approver data area, and an application flag is recorded in the approval status data area. To extract records. Then, the application support unit 212 generates an approval confirmation screen in which the contents of the extracted application management record 230 are displayed as a list. This approval confirmation screen includes route information associated with the schedule date (start date and time and end date and time of the application management record 230). Further, when an authenticated flag is recorded in the authentication status data area, an icon indicating that the authentication has been completed is included in the approval confirmation screen.

  Then, the application support unit 212 outputs an approval confirmation screen on the display of the client terminal 15. The approver confirms the application content using the approval confirmation screen and inputs the approval result. In this case, the application support unit 212 updates the application management record 230 using the approval result input on the application confirmation screen. Here, when the approval input is performed, the application support unit 212 records the approved flag in the approval status data area of the application management record 230. On the other hand, when a return input is made, the application support unit 212 records a return flag in the approval status data area of the application management record 230.

(Payment support processing)
Next, payment support processing will be described with reference to FIG. This payment support process is periodically executed.

  Here, the control part 21 of the application support server 20 performs the acquisition process of approval information (step S3-1). Specifically, the payment support means 213 of the control unit 21 has an application management storage unit 23 in which an approved flag is recorded in the approval status data area and an unsettled flag is recorded in the payment status data area. A record 230 is extracted.

  Next, the control part 21 of the application assistance server 20 performs the determination process about whether it is utilization of a portable terminal (step S3-2). Specifically, the payment support means 213 of the control unit 21 accesses the employee management information storage unit 52 of the employee management server 50. Next, the payment support means 213 acquires the employee management record 520 in which the employee code of the extracted application management record 230 is recorded. Then, the payment support means 213 specifies the use medium recorded in the employee management record 520. When a portable terminal is recorded as a usage medium, it is determined that the portable terminal is used.

  If it is determined that the mobile terminal is to be used (“YES” in step S3-2), the control unit 21 of the application support server 20 executes an autocharge process (step S3-3). Specifically, the payment support means 213 of the control unit 21 acquires the medium code recorded in the employee management record 520. Then, the payment support means 213 requests the transportation server 85 to charge the electronic value from the company account to the portable terminal 71 of the medium code for the amount recorded in the application management record 230. Thereby, the balance of electronic value is updated in the portable terminal 71.

  On the other hand, when the transportation card is registered as the use medium and it is determined that the mobile terminal is not used (“NO” in step S3-2), the control unit 21 of the application support server 20 issues a charge slip. Processing is executed (step S3-4). Specifically, the payment support means 213 of the control unit 21 creates and outputs an available charge slip at a store or the like. In this charge slip, information on the amount to be settled is printed. When this charge slip is brought to a predetermined store or the like, the charge slip is read at a POS terminal installed at the store or the like, and the electronic value corresponding to the amount displayed on the slip is transferred to the transportation card 72. Charge. As a result, the balance of the electronic value is updated in the transportation card 72. Then, the store or the like provides the collected charge slip to the company and collects the charged amount.

As described above, according to the present embodiment, the following effects can be obtained.
(1) In the embodiment described above, the control unit 21 of the application support server 20 executes a verification process with the authentication condition (step S1-3). And when the content currently recorded on the schedule management record 320 corresponds to authentication conditions, and it determines with satisfying authentication conditions (in the case of "YES" in step S1-4), the control part 21 of the application assistance server 20 will be the following. An authenticated route acquisition process (step S1-7) and an authenticated recording process (step S1-8) are executed. Thereby, it is possible to efficiently settle out the travel expenses that are registered in the dictionary in advance.

  (2) In the above embodiment, when it is determined that the content recorded in the schedule management record 320 does not correspond to the authentication condition and does not satisfy the authentication condition (in the case of “NO” in step S1-4), the application support The control unit 21 of the server 20 executes a route candidate acquisition process (step S1-5). Thereby, it is possible to apply for transportation expense settlement while referring to route candidates according to the source and destination.

  (3) In the said embodiment, the control part 21 of the application assistance server 20 performs the specific process (step S1-9) of a commuter pass section, and the calculation process (step S1-10) of a transportation expense. Thereby, transportation expenses can be settled in consideration of the section using a commuter pass.

  (4) In the above-described embodiment, the control unit 21 of the application support server 20 executes a move source and move destination specifying process (step S1-2). Here, the payment information acquisition unit 211 identifies the movement source and the movement destination of the forward path and the return path based on the presence / absence of the “direct output” flag and the “direct return” flag. When going out, depending on the time of day, the user may go out or return home directly. Considering such a situation, the transportation expenses can be settled.

  (5) In the above embodiment, the control unit 21 of the application support server 20 executes a confirmation screen output process (step S2-2). Thereby, it is possible to make an application after confirming the transportation expense settlement route and the like.

  (6) In the above embodiment, when the authenticated flag is recorded in the authentication status data area, the control unit 21 of the application support server 20 includes an icon indicating that the application has been authenticated on the application confirmation screen. Thus, the approval work can be efficiently performed using the icon indicating that the authentication has been performed in advance.

  (7) In the above embodiment, the control unit 21 of the application support server 20 executes a determination process as to whether there is a correction in the authenticated route (step S2-5). When the authenticated flag is recorded in the application management record 230 and it is determined that there is a correction in the authenticated route (in the case of “YES” in step S2-5), the control unit 21 of the application support server 20 is not authenticated. Is executed (step S2-6). Thereby, when it deviates from the authentication condition, the approval work can be performed in consideration of this situation.

  (8) In the above embodiment, the control unit 21 of the application support server 20 executes an approval process (step S2-9). If an authenticated flag is recorded in the authentication status data area, an icon indicating that the authentication has been completed is included in the approval confirmation screen. Thus, the approval work can be efficiently performed using the icon indicating that the authentication has been performed in advance.

  (9) In the above embodiment, when it is determined that the mobile terminal is used (in the case of “YES” in Step S3-2), the control unit 21 of the application support server 20 executes the autocharge process (Step S3). -3). Thereby, when the portable terminal 71 is used, it is not necessary to charge at the charging terminal, and it is possible to receive the transportation expenses that are efficiently settled.

  (10) In the above embodiment, when the transportation card is registered as the use medium and it is determined that the mobile terminal is not used (“NO” in step S3-2), the control unit 21 of the application support server 20 Executes a charge slip issuing process (step S3-4). Thereby, even when auto-charging cannot be performed, the settled transportation expenses can be received efficiently.

<Second Embodiment>
A second embodiment embodying the present invention will be described with reference to FIG. In the first embodiment, based on the schedule registered in the schedule management server 30, a process for supporting an application for transportation expense settlement is executed. In the second embodiment, the transportation cost is settled based on the transportation usage information recorded in the portable terminal 71 or transportation card 72, and detailed description of similar parts is omitted.

  In this case, a keyword for filtering card information is registered in the settlement information acquisition unit 211. Specifically, in the use of the electronic value charged in the mobile terminal 71 or the transportation card 72, a keyword for extracting only the usage information that is a transportation expense settlement target is recorded.

  Furthermore, in this embodiment, a card reader is connected to the client terminal 10 used by the applicant. By using this card reader, the usage information and the medium code recorded in the portable terminal 71 and the transportation card 72 are acquired. By using this medium code, the usage information stored in the transportation server 85 can be acquired.

The employee management server 50 records the attendance calendar of each employee. In the attendance calendar, information on the scheduled attendance date and holidays of each employee is recorded.
Hereinafter, the application support process will be described with reference to FIG. This process is executed when an employee makes an application for transportation expense settlement.

As shown in FIG. 6A, first, the control unit 21 of the application support server 20 executes an applicant authentication process as in step S2-1 (step S4-1).
Next, the control part 21 of the application assistance server 20 performs the specific process of the unsettled outing schedule similarly to step S1-1 (step S4-2).

  Next, the control unit 21 of the application support server 20 executes usage information acquisition processing (step S4-3). Specifically, the payment information acquisition unit 211 of the control unit 21 outputs a message so that the portable terminal 71 or the transportation card 72 is held over the card reader on the display of the client terminal 10. Next, the settlement information acquisition unit 211 acquires the usage information read by the card reader of the client terminal 10 as a collation target. Here, the payment information acquisition unit 211 acquires the medium code from the portable terminal 71 or the transportation card 72, and acquires the usage information associated with the medium code from the transportation server 85 as a collation target. Good.

  Next, the control unit 21 of the application support server 20 executes a filtering process of usage information (step S4-4). Specifically, the payment information acquisition unit 211 of the control unit 21 specifies the usage purpose in the acquired usage information. In usage, payments other than transportation use (for example, purchase of goods) are excluded from processing. Further, the payment information acquisition means 211 accesses the employee management server 50 and acquires the attendance calendar information (attendance date) of this employee. Then, the payment information acquisition means 211 excludes the usage information about vacation days and holidays from the work calendar information.

  Next, the control part 21 of the application support server 20 performs a schedule collation process (step S4-5). Specifically, the payment information acquisition unit 211 of the control unit 21 supplies the filtered usage information and the specified schedule management record 320 to the application support unit 212. In this case, the application support unit 212 compares the use date and time recorded in the use information with the start date and time and the end date and time (event period) recorded in the schedule management record 320.

  Next, the control part 21 of the application support server 20 performs a route collation process (step S4-6). In this process, the following process shown in FIG. 6B is executed for each record corresponding to the use date of the use information and the event period (year / month / day).

Here, the control unit 21 of the application support server 20 executes the specifying process of the movement source and the movement destination similarly to step S1-2 (step S4-61).
Next, the control unit 21 of the application support server 20 executes a route candidate acquisition process (step S4-62) as in step S1-5.

  Next, the control part 21 of the application support server 20 performs the determination process about whether there exists a corresponding path | route (step S4-63). Specifically, the application support unit 212 of the control unit 21 confirms whether the route included in the usage information is included in the route candidates acquired in the previous step. When the route included in the usage information is included in the route candidates, it is determined that there is a corresponding route.

  When it is determined that the route included in the usage information is not included in the route candidate and there is no corresponding route (in the case of “NO” in step S4-63), the route matching process for this record is ended.

  On the other hand, when the route included in the usage information is included in the route candidate and it is determined that there is a corresponding route (in the case of “YES” in step S4-63), the control unit 21 of the application support server 20 Similar to steps S1-9 and S1-10, a commuter pass section specifying process (step S4-64) and a transportation cost calculating process (step S4-65) are executed.

  Next, the control unit 21 of the application support server 20 executes an application registration process (step S4-66). Specifically, the application support unit 212 of the control unit 21 generates an application management record 230 including an employee code, an affiliation code, an application date, a title, a usage date, a route, and an amount, and registers it in the application management storage unit 23. To do.

Then, when the processing is completed for all the records corresponding to the usage date of the usage information and the event period, the processing returns to the processing of FIG.
In this case, when the usage information included in the predetermined time from the event period cannot be detected and a record having no movement record corresponding to the schedule is detected, the control unit 21 of the application support server 20 executes inconsistency confirmation processing. (Step S4-7). Specifically, the application support unit 212 of the control unit 21 outputs a confirmation screen on the display of the client terminal 10. The confirmation screen includes a schedule management record 320 that does not correspond to the usage information, and a list display for alerting the usage information that does not correspond to the schedule management record 320.

  If there is no schedule management record 320 corresponding to the usage information, there is a possibility that the schedule registration is forgotten. When the schedule management record 320 is newly registered when the schedule registration is forgotten, a post-registration icon is selected.

  In this case, the control unit 21 of the application support server 20 executes a post-registration process for the schedule (step S4-8). Specifically, the application support unit 212 of the control unit 21 outputs a schedule registration screen on the display of the client terminal 10. This schedule registration screen includes input fields for a schedule title, start date / time, end date / time, location, description, and the like. And when the setting to each input column is complete | finished, the application assistance means 212 registers in the schedule management server 30 about the content input into the schedule registration screen.

  Next, the control part 21 of the application support server 20 performs an application registration process (step S4-9). Specifically, the application support unit 212 of the control unit 21 collates the post-registered schedule management record 320 with the usage information on the confirmation screen. If collation is possible, the application support unit 212 generates an application management record 230 and registers it in the application management storage unit 23.

  When there is no usage information corresponding to the schedule management record 320, there is a possibility that the transportation facility is used without using the portable terminal 71 or the transportation facility card 72 as in cash payment. When the mobile terminal 71 and the transportation card 72 are not used, an application icon is selected when an application for transportation expense is applied.

In this case, the control unit 21 of the application support server 20 executes a route candidate acquisition process (step S4-10) as in step S1-5.
Next, the control unit 21 of the application support server 20 executes an application registration process (step S4-11). Specifically, the application support unit 212 of the control unit 21 outputs an application input screen on the display of the client terminal 10. In the application input screen, input fields for title, date of use, route, and amount are provided. Information relating to the title and event period (year / month / day) acquired from the schedule management record 320 having no corresponding usage information is initially set in each input column of title and usage date. In each entry field of the route and the amount, information regarding the route candidate (route and amount) acquired in the previous step is initially set. The applicant confirms the application content using this application input screen. If the application route and the actually used route are different, the route is corrected on the application confirmation screen. When confirmation is completed, input confirmation completion on the application input screen. The application support unit 212 that has detected the confirmation end input registers the application management record 230 by using the content corrected on the application input screen.
Next, the control part 21 of the application support server 20 performs an approval request process similarly to step S2-7 (step S4-12).

As described above, according to the present embodiment, the following effects can be obtained.
(11) In the embodiment described above, the control unit 21 of the application support server 20 executes a schedule matching process (step S4-5). Thereby, the difference between a schedule and utilization information can be grasped.

  (12) In the above embodiment, when the usage information included within a predetermined time from the event period cannot be detected and a record having no movement record corresponding to the schedule is detected, the control unit 21 of the application support server 20 The confirmation process is executed (step S4-7). Thereby, inconsistency can be confirmed in a schedule and utilization results.

  (13) In the above-described embodiment, the control unit 21 of the application support server 20 executes the schedule post-registration process (step S4-8) and the application registration process (step S4-9). As a result, if the schedule that does not correspond to the usage information is forgotten to be registered, the schedule can be registered afterwards.

  (14) In the above embodiment, in this case, the control unit 21 of the application support server 20 executes a route candidate acquisition process (step S4-10) and an application registration process (step S4-11). Thereby, it is possible to apply for transportation expense adjustment for usage information that does not correspond to the schedule.

In addition, you may change the said embodiment into the following aspects.
-In each above-mentioned embodiment, control part 21 of application support server 20 performs a move origin and move place specific processing (Steps S1-2, S4-61). The movement source and the movement destination may be specified using the preceding and following schedules. For example, as shown in FIG. 7A, a case is assumed in which the base A or the base C where the user is working usually goes out. In this case, the user usually moves from the base A to the base B, and returns to the base A after the event at the base B ends. Then, it moves again from the base A to the base C, and returns to the base A after the event at the base C ends. On the other hand, when the time interval between the event at the site B and the event at the site C is short, as shown in FIG. There are cases where the user moves directly to the base C. Therefore, the application support unit 212 compares the time required for movement between event locations in the two schedules with the length of time between the schedules of previous and subsequent events, and determines whether or not the movement is direct. For this reason, the application support means 212 retains data related to the direct movement allowable time for determining whether or not it is a direct movement from a previous outing destination to a subsequent outing destination. After the move source / destination specifying process (steps S1-2, S4-61), the move source / destination correction process is performed in consideration of direct movement. This process will be described with reference to FIG.

  First, the control unit 21 of the application support server 20 executes the immediately preceding schedule specifying process (step S5-1). Specifically, the application support means 212 of the control unit 21 sets the schedule management record 320 in which the employee code of the employee and the immediately preceding end date / time are recorded with respect to the start date / time of the schedule management record 320 to be processed. It is specified in the schedule storage unit 32 of the schedule management server 30.

  Next, the control part 21 of the application support server 20 performs the determination process about whether it moved continuously from the preceding event place (step S5-2). Specifically, the application support unit 212 of the control unit 21 calculates the schedule time difference between the start date / time of the schedule management record 320 to be processed and the end date / time of the schedule management record 320 of the immediately preceding schedule. Further, the application support unit 212 acquires the event location recorded in the schedule management record 320 to be processed and the event location recorded in the schedule management record 320 of the immediately preceding schedule. Next, the application support unit 212 transmits information about the two event places to the traffic information providing server 60, and acquires the required travel time between the two event places. Then, the application support unit 212 determines whether the movement is a continuous movement based on the schedule time difference and the required movement time. Here, when the time difference and the required movement time are included in the direct movement allowable time, it is determined that the movement is continuous.

  When it is determined that the movement is a continuous movement from the preceding event location (in the case of “YES” in Step S5-2), the control unit 21 of the application support server 20 executes a process of deleting the return path from the preceding event location (Step S5-2). 3). Specifically, the application support means 212 of the control unit 21 deletes the return route recorded in the settlement target memory as not subject to transportation expense settlement. In the above example, the return route from the base B to the base A is not subject to transportation expense adjustment.

  Next, the control unit 21 of the application support server 20 executes a correction process of the movement source of the subsequent schedule (step S5-4). Specifically, the application support unit 212 of the control unit 21 specifies the event location recorded in the schedule management record 320 of the immediately preceding schedule as the movement source. In the above-described example, the base B becomes the movement source on the outbound route to the base C.

  On the other hand, if it is determined that the movement is not a continuous movement from the preceding event location (“NO” in step S5-2), the control unit 21 of the application support server 20 deletes the return path from the preceding event location (step S5- 3) Skipping the correction process of the movement source of the subsequent schedule (step S5-4).

  Then, the route specifying process is executed using the movement source and the movement destination specified by the above process. As a result, depending on the preceding and following schedules, it is possible to specify the movement source and the movement destination in consideration of a schedule situation in which the movement is made directly from the outing destination to another outing destination.

  In the first embodiment, the application support process is executed based on the outing approval status and the report approval status recorded in the schedule management record 320. In this case, a trail of evidence (evidence) may be obtained. Here, the application support server 20 is further provided with an evidence storage unit. Reports and transportation usage information are registered in the evidence storage unit. The report includes information related to the schedule management code, title, event location, start date / time, and end date / time, corresponding to the outing schedule. As the usage information of the transportation facility, the usage information acquired from the mobile terminal 71 and the transportation card 72 and the usage information acquired from the transportation server 85 based on the medium code are registered.

Further, a card reader for reading information recorded on the portable terminal 71 or the transportation card 72 is connected to the client terminal 10 of the applicant.
The authentication condition stored in the authentication dictionary storage unit 22 includes information related to the evidence condition. In the evidence condition, the type of evidence (receipt, report, usage information, etc.) and necessary contents included in the evidence are set. If the evidence condition is recorded, the application support server 20 executes evidence confirmation processing. Evidence confirmation processing that is automatically executed in the application support server 20 will be described with reference to FIG.

  First, the control unit 21 of the application support server 20 executes a determination process as to whether evidence is necessary (step S6-1). Specifically, the application support means 212 of the control unit 21 determines based on the presence / absence of evidence conditions included in the authentication conditions recorded in the authentication dictionary storage unit 22.

If the evidence condition is not recorded and it is determined that the evidence is unnecessary (in the case of “NO” in step S6-1), the evidence confirmation process is terminated.
On the other hand, if the evidence condition is recorded and it is determined that the evidence is necessary (“YES” in step S6-1), the control unit 21 of the application support server 20 executes the evidence search process (step S6). -2). Specifically, the application support unit 212 of the control unit 21 searches the evidence storage unit for the evidence associated with the schedule management code. Instead of the schedule management code, the evidence storage unit may be used to search for the corresponding evidence using the title, event location, start date / time, and end date / time.

  Next, the control part 21 of the application support server 20 performs the determination process about whether the evidence conditions are satisfied (step S6-3). Specifically, the application support means 212 of the control unit 21 confirms the evidence type and content recorded in the evidence condition. If the evidence satisfying the evidence condition can be extracted, it is determined that the evidence condition is satisfied. On the other hand, when the evidence is not registered or when the necessary content is not included in the evidence, it is determined that the evidence condition is not satisfied.

  When it is determined that the evidence condition is satisfied (in the case of “YES” in step S6-3), the control unit 21 of the application support server 20 executes evidence-registered registration processing (step S6-4). Specifically, the application support means 212 of the control unit 21 records an evidence authenticated flag indicating that evidence has been confirmed in the authentication status data area of the application management record 230.

  On the other hand, when it is determined that the evidence condition is not satisfied (in the case of “NO” in step S6-3), the control unit 21 of the application support server 20 executes the evidence request registration process (step S6-5). . Specifically, the application support unit 212 of the control unit 21 records an evidence unconfirmed flag in the authentication status data area of the application management record 230.

And in the output process (step S2-2) of the confirmation screen according to the access from the client terminal 10 of the applicant, the process shown in FIG. 8B is executed.
Here, the control part 21 of the application support server 20 performs the determination process about whether evidence has been confirmed (step S6-6). Specifically, the application support unit 212 of the control unit 21 determines that the evidence has been confirmed when the evidence authenticated flag is recorded in the application management record 230.

If it is determined that the evidence has been confirmed (“YES” in step S6-6), the evidence confirmation process is terminated.
On the other hand, when it is determined that the evidence has not been confirmed because the evidence unconfirmed flag is recorded (in the case of “NO” in step S6-6), the control unit 21 of the application support server 20 performs the evidence request process. Execute (Step S6-7). Specifically, the application support unit 212 of the control unit 21 outputs an evidence registration request on the display of the client terminal 10 of the applicant. This evidence registration request includes the evidence type and contents set in the authentication condition. For example, when the transportation usage information is required, the application support means 212 causes the card reader connected to the client terminal 10 to read the usage information stored in the mobile terminal 71 or the transportation card 72. And register in the evidence storage unit. When a report is necessary, the created report is registered in the evidence storage unit.

In this case, similarly to step S6-3, the control unit 21 of the application support server 20 performs a determination process as to whether or not the evidence condition is satisfied (step S6-8).
When it is determined that the evidence condition is satisfied (in the case of “YES” in step S6-8), the control unit 21 of the application support server 20 registers the evidence-confirmed registration process as in step S6-4. Is executed (step S6-9).

  On the other hand, if it is determined that the evidence condition is not satisfied (in the case of “NO” in step S6-8), the control unit 21 of the application support server 20 executes a process not subject to approval application (step S6-10). . Specifically, the application support unit 212 of the control unit 21 excludes the application management record 230 from the application target, and records a pending flag.

  As a result, even when evidence is required, pre-authentication can be performed using evidence registered in advance. In addition, when the evidence condition is not satisfied, the registration of the evidence can be prompted.

  In the first embodiment, route candidate acquisition processing (step S1-5), authenticated route information acquisition processing (step S1-7) is executed based on the movement source and the movement destination. In this case, the authenticated route may be changed or a route candidate may be acquired in consideration of the failure state of the transportation facility. In this case, the failure information provided in the traffic information providing server 60 is used. This failure information includes route information on which a failure has occurred and failure duration information (failure occurrence date and time, failure recovery date and time). Then, the control unit 21 of the application support server 20 searches for the failure information of the transportation facility for the route candidate and the authenticated route before the predetermined time from the start date and time of the schedule management record 320 to be processed and after the predetermined time from the end date and time. To do. Here, when the failure information is acquired, these alternative routes are acquired from the traffic information providing server 60 except for the authenticated route and the route candidate where the failure has occurred.

  Furthermore, when the failure information is acquired, the failure state is recorded in the memo data area of the application management record 230 in the transportation facility. Thereby, it is possible to make an application by specifying a route in consideration of a failure occurring in the transportation facility.

  In the second embodiment, the control unit 21 of the application support server 20 executes a move source / destination specifying process (step S4-61) and a route information acquisition process (step S4-62). Here, application registration may be performed based on the route recorded in the usage information. Specifically, the application support unit 212 compares the required travel time of the route (original route) acquired from the traffic information providing server 60 with the required travel time of the route included in the usage information. If the required travel time of the route included in the usage information is shorter than the required travel time of the original route, the application registration is performed using the route included in the usage information.

  In the second embodiment, the control unit 21 of the application support server 20 executes the schedule matching process (step S4-5) and the inconsistency confirmation process (step S4-7). Here, a change route search process may be performed according to the failure occurrence state in the transportation facility. This process will be described with reference to FIG.

First, the control part 21 of the application support server 20 performs the acquisition process of a route candidate like step S1-5 (step S7-1).
Next, the control unit 21 of the application support server 20 executes a determination process as to whether or not the route matches the usage information (step S7-2). Specifically, the application support unit 212 of the control unit 21 compares the acquired route candidate with the route of the usage information. When the route of the usage information is included in the route candidate, it is determined that it matches the route of the usage information.

  When it is determined that the route matches the usage information path (in the case of “YES” in step S7-2), the control unit 21 of the application support server 20 executes an application registration process (step S7-3). Specifically, the application support means 212 of the control unit 21 records the usage information path in the path data area of the application management record 230 and records the usage information usage amount in the amount data area.

  When it is determined that the route of the usage information is not included in the route candidate and does not match the route of the usage information (in the case of “NO” in step S7-2), the control unit 21 of the application support server 20 A failure information search process is executed for (step S7-4). Specifically, the application support means 212 of the control unit 21 accesses the traffic information providing server 60 and acquires fault information of the transportation facility during the event period. This failure information includes information on the route where the failure has occurred and information on the failure duration. Then, the application support unit 212 searches the acquired failure information for failure information about the route candidate and within the predetermined time range of the event period (start date / time, end date / time).

  Next, the control part 21 of the application support server 20 performs the determination process about whether there was a failure in a transportation system (step S7-5). Specifically, the application support means 212 of the control unit 21 determines that there is a failure in the transportation system when the failure information within the predetermined time range of the event period is extracted for the route candidate.

  If it is determined that there is a failure in the transportation facility (in the case of “YES” in step S7-5), the control unit 21 of the application support server 20 adds failure information and executes an alternative route registration process ( Step S7-6). Specifically, the application support unit 212 of the control unit 21 records failure information in the memo data area of the application management record 230. Then, the application support unit 212 records the route and the amount included in the usage information in the application management record 230.

When the failure information cannot be extracted and it is determined that there is no failure in the transportation facility (in the case of “NO” in step S7-5), the control unit 21 of the application support server 20 performs steps S4-7 to S4-11. In the same manner as described above, a mismatch handling process is executed (step S7-7). And the control part 21 of the application assistance server 20 performs the approval request process (step S4-12) shown in FIG.
Thereby, it is possible to make an application by specifying a route in consideration of a failure occurring in the transportation facility.

  -In each above-mentioned embodiment, control part 21 of application support server 20 performs acquisition processing of a route candidate (Steps S1-5, S4-62, S4-10). Here, the route may be specified in consideration of the time required for movement. In this case, the application support unit 212 acquires the schedule management record 320 for the preceding schedule and the subsequent schedule from the schedule storage unit 32 of the schedule management server 30. Then, the application support unit 212 calculates a time difference from the end date / time of the schedule management record 320 of the preceding schedule to the start date / time of the schedule management record 320 to be processed. Further, the application support unit 212 calculates a time difference from the end date / time of the schedule management record 320 to be processed to the start date / time of the schedule management record 320 of the preceding schedule. Then, the application support unit 212 identifies routes that can move within these time differences as route candidates.

Further, the control unit 21 of the application support server 20 may specify the authenticated route based on the time difference between the preceding schedule and the subsequent schedule in the authenticated route acquisition process (step S1-7). . In this case, the time difference is included in the authentication condition, and the authenticated path corresponding to the time difference is registered in the authentication dictionary storage unit 22. Then, the application support unit 212 acquires an authenticated path corresponding to the calculated time difference between schedules from the authentication dictionary storage unit 22.
Thereby, a path | route can be specified according to a schedule condition.

  -In each above-mentioned embodiment, control part 21 of application support server 20 performs acquisition processing of a route candidate (Steps S1-5, S4-62, S4-10). Here, the route may be specified in consideration of the weather during movement. In this case, the control unit 21 of the application support server 20 can be connected to a weather information providing server that provides weather information via the Internet. This weather information providing server provides weather information corresponding to the date, time, and area acquired via the Internet. And the control part 21 of the application assistance server 20 accesses a weather information provision server, when acquiring a route candidate, the event period (start date-end date / time) of the schedule management record 320 of a process target, the area of an event place. Get weather information. Then, the application support unit 212 identifies route candidates based on the weather information. For example, in the case of bad weather, a route that uses less transit or a route that uses transportation that is less affected by the weather is preferentially specified as a route candidate.

Moreover, you may make it the control part 21 of the application assistance server 20 identify an authenticated path | route according to the weather also in the acquisition process (step S1-7) of an authenticated path | route. In this case, the weather is included in the authentication condition, and the authenticated route corresponding to the weather is registered in the authentication dictionary storage unit 22. Then, the application support unit 212 acquires an authenticated route corresponding to the weather information acquired from the weather information providing server from the authentication dictionary storage unit 22.
Thereby, a route can be specified according to the weather.

  -In the said 1st Embodiment, the control part 21 of the application assistance server 20 performs the change process to unauthenticated (step S2-6). In addition, on the approval confirmation screen, the authenticated route may be changed, or the changed part may be output. In this case, the correction history is registered in the application management record 230. Thereby, it is possible to efficiently perform the approval work while confirming the corrected content.

  In each of the above embodiments, for example, application support processing is periodically executed in order to support settlement of transportation expenses for the previous month at the beginning of the month. The timing for executing the application support process is not limited to this. For example, after the end date / time recorded in the schedule management record 320 of the schedule storage unit 32 elapses, it is also possible to make a payment target. Further, an alarm for prompting settlement may be output after a predetermined period (for example, 3 business days) has passed since the end date and time.

  In each of the above embodiments, when the “direct output” flag is recorded in the schedule management record 320, the settlement information acquisition unit 211 identifies the home address as the movement source. When the “bounce” flag is recorded in the schedule management record 320, the settlement information acquisition unit 211 specifies the home address as the destination. Instead of this, in the case of direct departure or bounce, the station included in the commuter pass section recorded in the employee management record 520 of the employee management information storage unit 52 may be specified as the source or destination. Good.

  In the first embodiment, the authentication dictionary storage unit 22 records an authentication dictionary record 220 for authenticating a transportation expense adjustment target in advance. The authentication dictionary record 220 includes data relating to an authentication management code, authentication conditions, departure place, destination, route, and amount. Here, the authentication dictionary record 220 may be recorded for each employee. In this case, the employee code of the employee who applies each authentication condition is recorded in the authentication dictionary record 220. Then, in the verification process (step S1-3) with the authentication condition, the employee code recorded in the schedule management record 320 is specified, and the verification process is performed using the authentication condition of the authentication dictionary record 220 in which the employee code is recorded. Execute.

  In the second embodiment, a determination process for determining whether there is a corresponding route is performed (step S4-63). Here, when the application amount is equal to or less than the transportation cost of the route candidate, another route may be allowed.

  In the second embodiment, the control unit 21 of the application support server 20 executes usage information filtering processing (step S4-4). Here, the payment information acquisition means 211 of the control unit 21 excludes the usage information on vacation days and holidays from the attendance calendar information. In addition to this, filtering may be performed according to the time of attendance. In this case, the working time zone information of the applicant on the going out date is acquired from the employee management server 50. Then, the usage information outside the reference time range is filtered from the working hours.

  In each of the above embodiments, the control unit 21 of the application support server 20 executes a charge slip issuing process (step S3-4). Instead of this, the control unit 21 may transfer the amount applied to the applicant's account.

  In the first embodiment, the control unit 21 of the application support server 20 executes an approval process (step S2-9). Here, when an authenticated flag is recorded in the authentication status data area, an icon indicating that the authentication has been completed is included in the approval confirmation screen. The approval method in the case where the authenticated flag is recorded in the authentication status data area is not limited to this, and it is sufficient that the approval procedure can be simplified as compared with an application that has not been authenticated.

  In the second embodiment, the route matching process is executed (step S4-6). Here, the route recorded in the authentication dictionary storage unit 22 may be collated. Also in this case, the authenticated flag is recorded in the authentication status data area of the application management record 230. Then, during the approval process, the approval procedure is simplified compared to an application that has not been authenticated. For example, if an authenticated flag is recorded in the authentication status data area, an icon indicating that the authentication has been completed is included in the approval confirmation screen during the approval process.

  In the first embodiment, the application for transportation expense adjustment is made after confirming the application contents by the applicant, and the transportation expense is settled after confirmation of the application contents by the approver. Here, these processes may be simplified. For example, the control unit 21 of the application support server 20 periodically searches the schedule management server 30 for a schedule management record 320 for going out. When the end date / time recorded in the schedule management record 320 has passed and the schedule management record 320 in which the unsettled flag is recorded in the settlement status data area is detected, the control unit 21 goes out to this employee. Confirmation process of schedule execution is performed. In this confirmation process, the confirmation of the going-out situation is performed by outputting a confirmation dialog or sending a confirmation mail to the client terminal 10 of the employee (outing person). This confirmation notification includes information about the start date / time, end date / time, and event location recorded in the schedule management record 320.

  Then, the going-out person accesses the application support server 20 using the client terminal 10 and inputs the going-out confirmation for the confirmation notification. In this case, the control unit 21 of the application support server 20 specifies a work place using the employee management record 520 of the outing person recorded in the employee management information storage unit 52. Then, the control unit 21 determines whether or not there is an authentication dictionary record 220 in which the work location is recorded as the departure place and the event location recorded in the schedule management record 320 is recorded as the destination in the authentication dictionary storage unit 22. Confirm. The departure place is not limited to the work place. For example, when it is determined that the event has moved continuously from the preceding event location based on the schedule time difference and the required travel time, the event location of the immediately preceding schedule may be specified as the move source.

  If the authentication dictionary record 220 can be extracted as a selection candidate in the authentication dictionary storage unit 22, the control unit 21 displays a dialog for confirming whether the route of the authentication dictionary record 220 is acceptable. On the display. When the client terminal 10 receives an approval input for this route, the control unit 21 regards that the application by the outsider and the approval by the approver have been performed, and records this transportation cost (recorded in the authentication dictionary record 220). Settlement processing is performed. As a result, transportation expenses can be settled by simple processing.

  Further, in the outing confirmation input, a route used for the outing person to go out may be input. Specifically, when an outing confirmation input is performed, the control unit 21 of the application support server 20 records the work location as the departure place in the authentication dictionary storage unit 22 and the event recorded in the schedule management record 320. It is checked whether there is an authentication dictionary record 220 in which a place is recorded as a destination. Also in this case, the departure place is not limited to the work place, and the event place of the immediately preceding schedule may be specified as the movement source as described above. If such an authentication dictionary record 220 can be extracted in the authentication dictionary storage unit 22, the control unit 21 compares the route input by the outsider with the route recorded in the authentication dictionary record 220. . If the two match, the control unit 21 considers that the application by the outsider and the approval by the approver have been performed, and performs a settlement process for the transportation cost.

  Furthermore, when there are a plurality of authentication dictionary records 220 that are candidates for selection, an outsider may be allowed to select the authentication dictionary record 220 used for transportation expense settlement. In this case, the control unit 21 of the application support server 20 stores the authentication dictionary record 220 in which the work place of the outsider is recorded as the departure place and the event place recorded in the schedule management record 320 is recorded as the destination. Extract. Then, the control unit 21 displays a list of the extracted authentication dictionary records 220 on the display of the client terminal 10. Here, when the authentication dictionary record 220 is selected, the control unit 21 uses the authentication dictionary record 220 to regard that the application by the outsider and the approval by the approver have been performed, Checkout process is performed.

  DESCRIPTION OF SYMBOLS 10,15 ... Client terminal, 20 ... Application support server, 21 ... Control part, 211 ... Settlement information acquisition means, 212 ... Application support means, 213 ... Payment support means, 22 ... Authentication dictionary memory | storage part, 23 ... Application management memory | storage part 30 ... Schedule management server 32 ... Schedule storage unit 50 ... Employee management server 52 ... Employee management information storage unit 60 ... Traffic information providing server 70 ... Recording medium 71 ... Portable terminal 72 ... Transportation card 80 ... Ticket gate, 85 ... Transportation server.

Claims (10)

A schedule storage unit that records event schedules including users, event locations, and event periods;
An application management storage unit that records applications for transportation expenses,
A transportation expense settlement system comprising a control unit that supports an application for transportation expense settlement,
The control unit is
From the schedule storage unit, obtain the event schedule of the user,
For the recording medium used by the user when using the transportation facility, the usage information including the usage date, the movement source, and the movement destination is acquired as a verification target,
The event location and event period of the event schedule are compared with the use date of the usage information, the movement source, the movement destination,
If the usage information corresponding to the event schedule can be identified based on the collation result, the application for payment of the transportation cost included in the usage information is registered in the application management storage unit. Expense settlement system.   The transportation expense settlement system according to claim 1, wherein the transportation usage information corresponding to the event period of the event schedule is acquired as a verification target. A user information storage unit that records working hours is further provided.
The control unit is
From the user information storage unit, specify the working hours of the user,
3. The transportation expense adjustment system according to claim 1, wherein, in the use information of the transportation facility, only the use information of the working hours is acquired as a collation target. The control unit is
In the schedule storage unit, specify the schedule immediately before the event schedule,
Identify the event location of the previous schedule as the source,
The transportation expense settlement system according to any one of claims 1 to 3, wherein the event schedule and the usage information are collated using the movement source. The control unit is
In the schedule storage unit, specify a schedule immediately after the event schedule,
Specify the event location of the schedule immediately after as the destination,
The transportation expense settlement system according to any one of claims 1 to 4, wherein the event schedule and the usage information are collated using the destination. The control unit is
Based on the event period of the event schedule, search for fault information about the transportation route from the source to the destination,
The transportation expense settlement system according to any one of claims 1 to 5, wherein when the failure information is acquired, the event schedule and the usage information are collated based on the failure information.   The said control part outputs the alerting for checking an event schedule, when the utilization information which does not respond | correspond to the said event schedule is acquired, The Claim 1 characterized by the above-mentioned. Transportation expense settlement system. The control unit is
2. The transportation fee charging process is performed on a recording medium used when the user uses transportation when the approval information for the application for the settlement of the transportation fee is acquired. The transportation expense adjustment system as described in any one of -7. A schedule storage unit that records event schedules including users, event locations, and event periods;
An application management storage unit that records applications for transportation expenses,
A method for supporting transportation expense settlement using a transportation expense settlement system including a control unit that supports application for transportation expense settlement,
The control unit is
From the schedule storage unit, obtain the event schedule of the user,
For the recording medium used by the user when using the transportation facility, the usage information including the usage date, the movement source, and the movement destination is acquired as a verification target,
The event location and event period of the event schedule are compared with the use date of the usage information, the movement source, the movement destination,
If the usage information corresponding to the event schedule can be identified based on the collation result, the application for payment of the transportation cost included in the usage information is registered in the application management storage unit. Expense settlement method. A schedule storage unit that records event schedules including users, event locations, and event periods;
An application management storage unit that records applications for transportation expenses,
A program that supports transportation expense settlement using a transportation expense settlement system with a control unit that supports application for transportation expense settlement,
The control unit
From the schedule storage unit, obtain the event schedule of the user,
For the recording medium used by the user when using the transportation facility, the usage information including the usage date, the movement source, and the movement destination is acquired as a verification target,
The event location and event period of the event schedule are compared with the use date of the usage information, the movement source, the movement destination,
If the usage information corresponding to the event schedule can be identified based on the collation result, the application information storage unit may function as a means for registering an application for payment of transportation expenses included in the usage information. A characteristic transportation expense settlement program.

Images