JP7828675B2 - Information processing device, information processing method, and program - Google Patents

Description

This invention relates to an information processing device, etc., that has functions such as acquiring and outputting travel route information related to the travel routes of employees.

Traditionally, there have been websites that allow users to easily understand the impact of a change in destination on the travel costs of multiple travelers. These websites output routes using public transportation based on input of departure and arrival stations (see, for example, Non-Patent Document 1).

Jorudan, [online], [searched September 4, 2020], Internet [URL: https://www.jorudan.co.jp/]

However, conventional technology could not obtain accurate employee travel routes using one or more types of information from employee schedules and actual travel information.

The first information processing device of this invention comprises a work information storage unit that stores one or more types of information, associated with one or more employee identifiers, including scheduled information (information relating to an employee's work schedule and containing location identification information), and actual work information (information relating to an employee's actual work and containing location identification information), and a travel path acquisition unit that acquires travel path information relating to the travel route of an employee identified by the employee identifier using the location identification information, and a travel path output unit that outputs the travel path information.

This configuration allows for the acquisition of accurate employee movement routes.

Furthermore, the information processing device of this second invention, compared to the first invention, further comprises an inspection unit that checks whether scheduled information and actual information match, using scheduled information and actual information corresponding to the same day information that identifies the same day, and a processing unit that performs different processing according to the inspection results of the inspection unit.

This configuration allows for verification of the consistency between planned and actual data.

Furthermore, the information processing device of this third invention, compared to the second invention, is an information processing device in which the processing unit includes a notification unit that, when the inspection result from the inspection unit indicates a mismatch, notifies the employee identified by the employee identifier corresponding to the inspection result of information regarding the inspection result.

This configuration allows for checking the consistency between planned and actual information, and notifying employees of any discrepancies.

Furthermore, the information processing device of this fourth invention is an information processing device that, in addition to any one of the first to third inventions, further comprises a travel expense acquisition unit that acquires travel expense information specifying travel expenses using planned information or actual information, and a travel expense output unit that outputs travel expense information.

This configuration allows for the acquisition of travel expense information using travel route information.

Furthermore, the information processing device of this fifth invention, compared to the fourth invention, further comprises a commuting route storage unit that stores commuting route information, each employee identifier associated with one or more employee identifiers, and an account determination unit that uses the commuting route information and location identification information contained in the travel route information associated with the employee identifier to determine whether all or part of the travel expense information corresponds to an account related to commuting expenses or whether all or part of the travel expense information corresponds to an account related to transportation expenses. The travel expense output unit outputs the travel expense information associated with the account identification information that identifies the account determined by the account determination unit.

This configuration allows for the acquisition of travel expense information using travel route information.

Furthermore, the information processing device of this sixth invention differs from the fifth invention in that, when the travel expense output unit determines that the account determined by the account determination unit is an account related to transportation expenses, it performs processing to store travel expense information in the transportation expense database, associating it with the employee. However, when the account determination unit determines that the account determined is an account related to commuting expenses, it does not perform processing to store travel expense information in the transportation expense database.

This configuration allows travel expense information corresponding to the travel expense category to be stored in the travel expense database.

Furthermore, the information processing device of the seventh invention, compared to the sixth invention, is an information processing device in which the travel expense acquisition unit determines whether or not a commuter pass has been obtained, and the travel expense information is the travel expense information of "0" when the travel expense information corresponding to the employee identifier indicates that a commuter pass has been obtained, and the account determination unit has determined that the travel expense information corresponds to an account related to commuter expenses.

This configuration allows for obtaining appropriate commuting expenses using regular travel information.

Furthermore, the information processing device of this eighth invention, in contrast to the sixth or seventh invention, is an information processing device in which the travel expense acquisition unit stores travel information in a travel information storage unit, which identifies the use of an employee's travel vehicle for commuting, and the travel information corresponding to the employee identifier is information indicating that a travel vehicle is used for commuting, and if the account determination unit determines that the account is an account related to commuting expenses, the travel expense information is set to "0".

This configuration allows employees who apply for commuting by private car or other means of transport to receive appropriate commuting expenses.

Furthermore, the information processing device of this ninth invention, in relation to any one of the sixth to eighth inventions, is an information processing device in which, when the travel expense acquisition unit acquires travel expense information that is not "0", and the account determination unit determines that the determined account is an account related to commuting expenses, the travel expense output unit performs processing to store the travel expense information in the commuting expense database that manages commuting expenses.

This configuration allows travel expense information corresponding to the commuting expense category to be stored in the commuting expense database.

Furthermore, the information processing device of this tenth invention, with respect to any one of the first to ninth inventions, has scheduled information or actual information which includes daily information, a first work location identifier that identifies the first work location at the start of work, and a second work location identifier that identifies the second work location at the end of work. The travel route acquisition unit acquires home location information corresponding to an employee identifier from a home location storage unit which stores home location information that identifies the address of the employee's home or the nearest transportation point to their home, associated with one or more employee identifiers. The work location information storage unit which stores one or more work location information having a work location identifier and location identification information acquires the first work location identifier corresponding to the employee identifier. This information processing device obtains first location identification information paired with a work location identifier, uses home location information and the first location identification information to obtain first travel route information from home to the work location at the start of work, obtains second location identification information paired with a second work location identifier from the work location information storage unit, uses the first and second location identification information to obtain second travel route information from the first work location to the second work location, uses the second location identification information and home location information to obtain third travel route information from the second work location to home, and the travel route output unit outputs the first travel route information, second travel route information, and third travel route information.

This configuration allows for the output of appropriate travel routes for employees who move between two or more work locations.

Furthermore, the information processing device of this eleventh invention, compared to the tenth invention, further comprises a subject determination unit that determines that travel expense information corresponding to the first travel route information and the third travel route information corresponds to a subject related to commuting expenses, and determines that travel expense information corresponding to the second travel route information corresponds to a subject related to transportation expenses. The travel expense output unit outputs the travel expense information in association with subject identification information that identifies the subject determined by the subject determination unit.

This configuration allows for the determination of appropriate expense categories for travel expenses of employees who move between two or more work locations.

Furthermore, the information processing device of this twelfth invention, in relation to any one of the first to eleventh inventions, is an information processing device in which the travel route acquisition unit acquires travel route information that identifies the road route from the employee's home to the workplace, using the travel information that identifies the employee's home address, which is stored in a travel information storage unit associated with one or more employee identifiers, and the travel information that identifies the employee's home address, which is stored in a home location storage unit associated with one or more employee identifiers, and the home location information that identifies the employee's home address, which is stored in a home location storage unit associated with one or more employee identifiers.

This configuration allows for the acquisition of appropriate travel routes for employees who commute using mobile devices.

Furthermore, the information processing device of this thirteenth invention further comprises, for any one of the first to twelfth inventions, a change determination unit that retrieves default schedule information or default performance information corresponding to an employee identifier from a default storage unit where default schedule information or default performance information is stored in association with one or more employee identifiers, compares the default schedule information or default performance information with the schedule information or performance information in the work information storage unit and determines whether they are different, and a change transmission unit that, if the change determination unit determines they are different, transmits change information indicating that the default information has been changed to the contact information indicated by one or more contact pieces of information corresponding to the employee identifier.

This configuration allows for notification to be sent to the appropriate person, such as a supervisor, if there are any changes from the default schedule or actual results.

Furthermore, the information processing device of this fourteenth invention, compared to the second invention, further comprises a re-inspection unit that determines whether the performance information received from the terminal device of the employee who notified the notification unit of the inspection result is inconsistent and satisfies predetermined conditions, and a reprocessing unit that performs different processing according to the determination result of the re-inspection unit.

This configuration allows for appropriate action to be taken when the planned results and actual results do not match.

Furthermore, the information processing device of this fifteenth invention is an information processing device that, in addition to the fourteenth invention, comprises a performance receiving unit that receives performance information from the terminal device of an employee who has received notification from the notification unit regarding the inspection result, where the inspection result from the inspection unit does not match the inspection result, and a performance storage unit that stores the performance information in the work information storage unit, associating it with the employee's employee identifier.

This configuration allows for appropriate action to be taken when the planned results and actual results do not match.

Furthermore, the information processing device of this sixteenth invention is an information processing device in which, for any one of the first to fifteenth inventions, the performance information is one or more of the following: entry/exit information regarding an employee's entry into and exit from their workplace, sales activity information regarding sales activities, input information entered by an employee for the purpose of performing their work, and employee location information including one or more location information received from a mobile terminal held by an employee.

This configuration allows for the acquisition of accurate employee travel routes using performance data.

According to the information processing device of the present invention, it is possible to obtain the precise travel route of an employee.

Conceptual diagram of information system A in Embodiment 1 Block diagram of the same information system A Block diagram of the expense inspection device 1 that constitutes the information system A. Flowchart illustrating an example of operation of the cost inspection device 1. A flowchart illustrating an example of the same inspection process. A flowchart illustrating an example of the statistical testing process. A flowchart illustrating an example of the leak detection process. Figure showing an example of the same output. Figure showing an example of the same output. Block diagram of other systems including the same cost inspection device 1. Conceptual diagram of information system B in Embodiment 2 Block diagram of the same information system B Block diagram of the information processing device 5 that constitutes the information system B. A flowchart illustrating an example of the operation of the information processing device 5. A flowchart illustrating an example of the same inspection process. A flowchart illustrating an example of the process for acquiring the travel route, etc. Flowchart explaining the process of obtaining the commute route, etc. Flowchart explaining the process of obtaining routes and other information between work locations. Flowchart explaining the process of obtaining the return route, etc. Flowchart explaining the process for re-examination, etc. A flowchart illustrating an example of the operation of the terminal device 6. Overview of the computer system in the above embodiment Block diagram of the computer system

The following describes embodiments of the information processing device, etc., with reference to the drawings. Note that components denoted by the same reference numerals in these embodiments perform similar operations, and therefore, their repeated descriptions may be omitted.

(Embodiment 1)
This embodiment describes an information system including an expense inspection device that receives expense information, performs fraud-related inspections using external information or previously submitted expense information, and outputs inspection results. External information includes information other than expense information, such as the applicant list, company regulations information, restaurant list, adult entertainment establishment list, counterparty list, card usage expense information, and transportation information described later. The targets of fraud inspection include, for example, business trip expenses, transportation expenses, duplicate applications, reuse of receipts, accommodation expenses, and after-party expenses.

Furthermore, this embodiment describes an information system including an expense inspection device that performs an inspection for fraud using statistical processing results based on information corresponding to two or more expense information items, and outputs the inspection results. The statistical processing results include, for example, the frequency of use of a specific store, the frequency of providing benefits to a specific party, and the number of times a specific person has committed fraud.

Furthermore, this embodiment describes an information system that includes an expense verification device for checking whether the approver of the expense application meets the requirements.

Furthermore, in this embodiment, an information system including an expense inspection device for inspecting receipt images will be described. The inspection of receipt images includes, for example, checking for deficiencies in the information written on the receipt image, checking for deficiencies in the timestamp of the receipt image, checking for unclear receipt images, checking for inappropriate payment methods indicated on the receipt image, and checking for falsification of handwritten amounts on the receipt image.

Furthermore, in this embodiment, we will describe an information system that includes an expense inspection device that uses external information to detect any omissions in expense applications that should be submitted.

Figure 1 is a conceptual diagram of information system A in this embodiment. Information system A comprises an expense inspection device 1, one or more applicant terminals 2, and one or more external servers 3.

Expense verification device 1 is a device that performs verification of submitted expense information. Expense verification device 1 is typically a server, such as a cloud server or ASP server. The type of expense verification device 1 is not specified.

Applicant Terminal 2 is the device used by the applicant. The applicant is the user submitting the expense claim. Applicant Terminal 2 can be, for example, a personal computer, tablet, smartphone, etc., regardless of type.

External server 3 stores the external information described later and provides this information to the expense inspection device 1. Note that all or part of the external information described later may reside on the expense inspection device 1. Furthermore, if all of the external information described later resides on the expense inspection device 1, external server 3 is unnecessary. External server 3 is typically a server, such as a cloud server or ASP server. The type of external server 3 is not specified.

The expense inspection device 1, the applicant terminal 2, and the external server 3 can typically communicate with each other via a network such as the internet or a dedicated line.

Figure 2 is a block diagram of information system A in this embodiment. Figure 3 is a block diagram of the expense inspection device 1 that constitutes information system A.

The expense inspection device 1 comprises a storage unit 11, a reception unit 12, a processing unit 13, and an output unit 14. The storage unit 11 includes, for example, an expense information storage unit 111, an applicant group storage unit 112, a company regulations information storage unit 113, a restaurant group storage unit 114, an adult entertainment establishment group storage unit 115, a counterparty group storage unit 116, a card usage expense storage unit 117, and a means of transportation information storage unit 118. The applicant group storage unit 112 includes a personal information storage unit 1121, an attendance information storage unit 1122, an entry/exit information storage unit 1123, a business activity information storage unit 1124, a card statement information storage unit 1125, and a business vehicle location information storage unit 1126. The means of transportation information storage unit 118 includes a calculation information storage unit 1181 and a map information storage unit 1182. The reception unit 12 comprises an expense reception unit 121. The processing unit 13 comprises an inspection unit 131 and a statistical processing unit 132. The inspection unit 131 includes an image inspection means 1311. The output unit 14 includes a result output unit 141.

The applicant terminal 2 comprises a first storage unit 21, a first reception unit 22, a first processing unit 23, a first transmission unit 24, a first receiving unit 25, and a first output unit 26.

The expense information storage unit 111, applicant list storage unit 112, company regulations information storage unit 113, restaurant list storage unit 114, adult entertainment establishment list storage unit 115, counterparty list storage unit 116, card usage expense storage unit 117, and transportation information storage unit 118 in the expense inspection device 1 may reside in other external devices.

It is preferable that the external server 3 stores one of the following: a restaurant aggregation storage unit 114, an adult entertainment establishment aggregation storage unit 115, a counterparty aggregation storage unit 116, a card usage expense storage unit 117, and a means of transportation information storage unit 118.

Furthermore, the inspection unit 131 may perform the inspection process described later using the various information stored in the storage unit 11, or it may perform the inspection process described later using the various information stored in the external server 3 or information transmitted from the external server 3.

External server 3 is a server that receives queries including, for example, information identifying the departure station (an example of a departure identifier described later) and information identifying the arrival station (an example of an arrival identifier described later), and outputs one or more transportation costs. Such external server 3 has a calculation information storage unit 1181 that stores fare calculation information described later. Furthermore, such external server 3 is a server of Jorudan (registered trademark) (URL "https://www.jorudan.co.jp/") or a server of NAVITIME (registered trademark) (URL "https://www.navitime.co.jp/").

External server 3 is a server that receives queries including, for example, a departure identifier and an arrival identifier, and outputs the taxi fare. This external server 3 has a calculation information storage unit 1181 and a map information storage unit 1182 for storing the taxi fare calculation information described later. Furthermore, this external server 3 is the taxisite server (URL "https://www.taxisite.com/far/").

The storage unit 11 stores various types of information. These types of information include, for example, expense information (described later) and external information (also described later).

The expense information storage unit 111 stores expense information. Typically, two or more expense information entries are stored in the expense information storage unit 111. Expense information is information that identifies the details of the claimed expense. Expense information includes, for example, expenditure amount information, recipient identifier, store identifier, counterparty identifier, date of use information, payment method identifier, account, description, and approver identifier. Expenditure amount information identifies the amount spent as an expense. The recipient identifier is information indicating the recipient of the receipt and identifying the company or other entity paying the amount. The store identifier identifies the store where the expense was used. Examples of store identifiers include the store name, store ID, store URL, and store telephone number. The counterparty identifier identifies the counterparty to whom the expense was used. Examples of counterparty identifiers include the organization name (e.g., company name, group name), name, and counterparty ID. Date of use information identifies the date the expense was used. The payment method identifier identifies the payment method. The payment method identifier is, for example, "cash," "credit card," "electronic money," or "○○ PAY." The account is information that identifies the classification of the expense. The account can also be called the expense type identifier. Examples of accounts include business trip expenses, travel expenses (or transportation expenses), accommodation expenses, business trip expenses, entertainment expenses, and meeting expenses. The approver identifier is information that identifies the approver of the expense. Examples of approver identifiers include the applicant identifier and the job title identifier. The applicant identifier is information that identifies the applicant who submitted the expense claim, for example, their name and ID. The job title identifier is information that identifies their job title, for example, their job title (e.g., "department head," "director") and ID. The expense information in the expense information storage unit 111 is usually associated with the applicant identifier.

If the expense information concerns transportation expenses, it includes, for example, transportation expense information that includes usage date information and one or more section information containing departure identifiers, arrival identifiers, and fare information. It is preferable that the expense information includes an expense type identifier indicating transportation expenses. If the expense information concerns business trip expenses, it includes, for example, usage date information. It is preferable that the expense information includes an expense type identifier indicating business trip expenses. If the expense information concerns accommodation expenses, it includes, for example, usage date information that identifies the day the employee stayed at the accommodation facility. If the expense information concerns entertainment expenses or meeting expenses, it includes, for example, an applicant identifier associated with the expense information, and includes usage date information and a store identifier that identifies the store where the expense was incurred.

Expense information may include images of receipts. A receipt image is simply an image of a receipt. For example, a receipt image might be an image obtained by taking a photograph of a receipt. Needless to say, the data structure of the receipt image (JPEG, GIF, etc.) is not restricted.

Expense information includes, for example, participant information and number of people information. Participant information identifies individuals who used the expense (e.g., those who ate or drank), such as their names. Number of people information is the number of people who used the expense.

The applicant collection storage unit 112 stores the applicant collection. The applicant collection consists of unique information corresponding to each applicant. For example, the applicant collection may include a collection of personal information (described later), attendance information (described later), building entry/exit information (described later), sales activity information (described later), card statement information (described later), or sales vehicle location information (described later).

The personal information storage unit 1121 stores one or more pieces of personal information. The personal information is information about the applicant. Each piece of personal information is associated with an applicant identifier. For example, the personal information may include the applicant's name, company name, company ID, department name, department ID, job title identifier, commuter pass information specifying the applicant's commuter pass route, number of fraudulent activity records, and email address. The number of fraudulent activity records refers to the number of times the applicant has submitted fraudulent expense claims or the number of times fraud by the applicant has been detected. The email address can be any information that identifies the recipient of the information, and may include SNS IDs, etc., and is interpreted broadly.

Furthermore, for two pieces of information to be considered associated, it is sufficient that one piece of information can be retrieved from the other. For example, this could mean that one piece of information is linked to the other, that both pieces of information are stored in the same buffer, or that one piece of information contains the other.

The attendance information storage unit 1122 stores one or more attendance information entries. Attendance information is information relating to the applicant's attendance. Attendance information is usually associated with an applicant identifier. Attendance information includes workday information. Workday information is information used to identify the days the applicant, identified by the corresponding applicant identifier, worked. Workday information usually indicates workdays, but may also indicate non-workdays. If the workday information indicates non-workdays, then any day other than those indicated by the workday information is considered a workday. Attendance information usually includes work time information that identifies the hours worked. Work time information includes, for example, the start time and end time of work. The attendance information in the attendance information storage unit 1122 is, for example, information received from an external server 3 (attendance management server). The attendance management server (attendance management system) is a server that manages employee attendance and is a device relating to publicly known technology, so a detailed explanation is omitted.

The entry/exit information storage unit 1123 stores one or more entries/exit information. Entry/exit information is information relating to the applicant's entry and exit. Entry/exit refers to the applicant's entry into and exit from their workplace (which can also be called their place of work). Entry can also be defined as arriving at work to begin work on a workday, and departure as leaving work after finishing work on a workday. Entry/exit information is usually associated with an applicant identifier. Entry/exit information includes, for example, workday information and work time information. Work time information includes, for example, the start time and end time of work. Work time information also includes, for example, information that identifies the hours worked. Entry/exit information is composed of information obtained from time card punching and inputting arrival or departure into the entry/exit system. Note that entry/exit information may be the same as attendance information. The entry/exit information in the entry/exit information storage unit 1123 is, for example, information received from an external server 3 (entry/exit management server). Since the access control server (access control system) is based on publicly known technology, a detailed explanation will be omitted.

The sales activity information storage unit 1124 stores one or more sales activity information entries. Sales activity information is information related to sales activities. For example, sales activity information may include sales report information. Sales activity information is usually associated with an applicant identifier. Sales activity information includes sales day information and one or more location identifiers. Sales activity information may also contain strings or other information indicating the content of the sales activity. Sales day information is information that identifies the day of the applicant's sales activity. Location identifiers are information that identifies the visited locations. Location identifiers may include, for example, (latitude, longitude), company name, location name, place name, station name, bus stop name, etc. The data structure of the sales activity information is not specified.

The card statement information storage unit 1125 stores one or more card statement information entries. Card statement information is information indicating the details of the credit card used by the applicant. Card statement information is usually associated with an applicant identifier. Card statement information includes, for example, usage date information, a payee identifier (e.g., a store identifier) that identifies the payee, amount information, and a card identifier. The card identifier is information that identifies the card, for example, the card number. The card statement information in the card statement information storage unit 1125 is, for example, information received from an external server 3 (card management company server).

The vehicle location information storage unit 1126 stores one or more vehicle location information entries. Vehicle location information identifies the location of a vehicle used by the applicant. Vehicle location information is usually associated with an applicant identifier. Vehicle location information is also associated with usage date information, which identifies the day the vehicle was used. Vehicle location information is, for example, (latitude, longitude), but may also be a location identifier. Vehicle location information is also associated with a vehicle identifier, for example, which identifies the vehicle.

The company regulations information storage unit 113 stores company regulations information. Company regulations information is information that indicates the company's rules. It is information related to the rules of the company to which the applicant belongs. For example, company regulations information may include overtime time information, information on one or more approvers, and information on one or more payment methods.

Overtime information refers to information that identifies the overtime hours at which overnight stays are permitted. Examples of overtime information include "23:00" and "after 24:00."

Approver information identifies individuals who may be approving expenses. This information includes, for example, an approver identifier (e.g., applicant identifier, name) and a position identifier (e.g., "Department Head," "Director") that identifies the approver.

Payment method information refers to information that identifies unacceptable payment methods. Examples of payment method information include "○○ PAY," "electronic money," and "credit card."

The restaurant data storage unit 114 stores restaurant data sets. Each restaurant data set contains information on one or more restaurants. Restaurant data is information about a restaurant. For example, restaurant data may include a restaurant identifier, price information, address information, telephone number information, etc. The restaurant identifier may be, for example, the restaurant name or ID. Price information may be, for example, information that identifies an appropriate amount to spend at a restaurant. Price information may be, for example, information about the amount spent by one person at that restaurant. Price information may be, for example, information indicating the average amount spent by one person at that restaurant. Price information may also be, for example, information that identifies the upper limit of the amount spent by one person at that restaurant. Price information may also be, for example, information that identifies the upper limit of the amount spent in a single visit.

The adult entertainment establishment data storage unit 115 stores data on adult entertainment establishments. Each data set contains one or more pieces of information on adult entertainment establishments. The information on adult entertainment establishments may include, for example, an adult entertainment establishment identifier that identifies the establishment. The information may also include price information, address information, telephone number information, etc. The information on adult entertainment establishments may also include, for example, information that identifies establishments that the applicant is not permitted to visit.

The recipient set storage unit 116 stores recipient sets. Each recipient set contains one or more recipient information entries. Recipient information includes, for example, a recipient identifier and an affiliation identifier that identifies the recipient's affiliation. Recipient information may include, for example, information on public officials. Recipient information may include, for example, information on members of parliament. Recipient information may include, for example, information identifying individuals to whom the applicant is prohibited from providing benefits. Providing benefits refers to acts such as entertaining or giving gifts.

The card expense storage unit 117 stores one or more expense type identifiers for expenses scheduled to be paid by card. Expense type identifiers may correspond to card type identifiers. Card type identifiers are information that identifies the type of card. Examples of card type identifiers include "EX-IC card" and "corporate card." Examples of expense type identifiers include "Shinkansen" (bullet train) fares and "entertainment expenses."

The transportation information storage unit 118 stores transportation information. This transportation information is used to calculate transportation costs when using a means of transport such as a train, bus, airplane, or taxi. The transportation information includes calculation information, which will be described later. For example, the transportation information includes map information, which will be described later.

The calculation information storage unit 1181 stores calculation information. This calculation information includes, for example, fare calculation information and taxi fare calculation information. Fare calculation information is, for example, information for calculating fares for transportation methods such as trains, buses, or airplanes. Fare calculation information includes, for example, information having one or more sets of departure identifiers, arrival identifiers, and fare information. Departure identifiers and arrival identifiers are, for example, station names, airport names, bus stop names, station IDs, airport IDs, and bus stop IDs. Taxi fare calculation information is information for calculating taxi fares. Taxi fare calculation information is, for example, a calculation formula for calculating taxi fares using distance as input. Taxi fare calculation information includes, for example, information having one or more sets of distance and taxi fare combinations.

The map information storage unit 1182 stores map information. This map information is, for example, map information used for navigation. The map information is, for example, in KIWI format.

The reception unit 12 receives various types of information and instructions. Here, "reception" typically refers to receiving information from terminals such as the applicant terminal 2. However, "reception" may also encompass the reception of information entered from input devices such as keyboards, mice, and touch panels, as well as information read from recording media such as optical discs, magnetic discs, and semiconductor memory.

The expense reception unit 121 receives one or more expense information entries. Typically, the expense reception unit 121 receives expense information associated with an applicant identifier. For example, the expense reception unit 121 receives expense information and an applicant identifier. The expense reception unit 121 may, for example, receive one or more expense information entries for each of the one or more applicants. Expense information is received, for example, from the applicant's terminal, but may also be received from an administrator terminal (not shown), read from a recording medium, or entered by the applicant.

The expense reception unit 121 is preferably capable of receiving expense information that includes a receipt image. The expense reception unit 121 may also separately receive the receipt image and other information that constitutes the expense information. However, the receipt image and the other information should be received in a corresponding manner.

The processing unit 13 performs various processes. These various processes include, for example, those performed by the inspection unit 131 and the statistical processing unit 132.

The inspection unit 131 performs an inspection for fraudulent expense information received by the expense reception unit 121 and obtains the inspection results. The inspection unit 131 may also perform an inspection for fraudulent expense information stored in the expense information storage unit 111 and obtain the inspection results. The expense information stored in the expense information storage unit 111 is the expense information received by the expense reception unit 121. The inspection results are information related to the results of the expense information inspection. The inspection results include, for example, information indicating whether or not the expense is fraudulent. The inspection results include, for example, some or all of the fraudulent expense information. The inspection results include, for example, information indicating that the expense is not fraudulent (that it is legitimate). The inspection results include, for example, one or more pieces of information from among expense information identifier, applicant identifier, expense type identifier, amount information, inspection content identifier, application date, etc. The expense information identifier is information that identifies the expense information, for example, an ID. The inspection content identifier is information that identifies the inspection content. The inspection content identifier is usually stored in the storage unit 11 in association with the inspection process described later. Examples of inspection type identifiers include "expenses incurred on non-working days," "fraudulent travel expense claims," "fraudulent accommodation expense claims," "accommodation expenses for days when accommodation was not permitted," "fraudulent transportation expense claims," and "receipt splitting." The content and data structure of the inspection type identifiers are not specified.

The inspection unit 131, for example, uses external information to inspect the expense information received by the expense reception unit 121 for any irregularities and obtains the inspection results. External information refers to information other than expense information. The external information used by the inspection unit 131 may be stored in the storage unit 11 of the expense inspection device 1, or it may be stored in the external server 3.

The inspection unit 131 uses, for example, expense information other than that received by the expense reception unit 121 to perform an inspection for fraudulent activity in the expense information received by the expense reception unit 121, and obtains the inspection results. The expense information other than that received by the expense reception unit 121 is, for example, expense information stored in the expense information storage unit 111, but it may also be expense information stored in the external server 3.

The inspection unit 131, for example, obtains applicant information from the applicant set that corresponds to the applicant identifier associated with the expense information received by the expense reception unit 121. Using this applicant information, it performs an inspection for fraudulent activity in the expense information received by the expense reception unit 121 and obtains the inspection results. The applicant set is, for example, information stored in the applicant set storage unit 112, but it may also be information stored in an external device (not shown). The applicant information is information associated with the applicant identifier, and includes, for example, attendance information, entry/exit information, sales activity information, card statement information, and sales vehicle location information.

The image inspection means 1311 inspects the receipt image contained in the expense information received by the expense reception unit 121 and obtains the image inspection result. Note that the image inspection result shown is an example of an inspection result.

The image inspection means 1311 obtains one or more character strings from the receipt image, uses these strings to check whether the receipt image is legitimate, and obtains the image inspection result. The image inspection means 1311 uses one or more of either character recognition processing or machine learning processing to obtain one or more character strings from the receipt image.

In this specification, the algorithms used in machine learning processing are not limited. Examples of machine learning include deep learning, decision trees, random forests, SVM, SVR, etc. Examples of modules used in machine learning include TensorFlow modules, TinySVM, etc.
(1) Method using character recognition processing

The image inspection means 1311 performs character recognition processing on, for example, a receipt image and obtains one or more character strings. The process of performing character recognition processing and obtaining information constituting expense information from a receipt image is publicly known technology. Furthermore, the image inspection means 1311 determines which of the following information the obtained character string represents: payment amount information, store identifier, counterparty identifier, usage date information, account, description, or payment method information. It then associates this character string with information identifying the type of information (which could also be called a class, category, etc.) and obtains the character string. The technique for determining the class of the obtained character string is an information classification problem (clustering problem) and is also publicly known technology.

The image inspection means 1311, for example, configures a learner that performs binary classification of whether or not a string belongs to a class by performing machine learning training on each class, using two or more strings belonging to that class as positive examples and one or more strings not belonging to that class as negative examples. Then, for each of the one or more strings obtained from the receipt image, the image inspection means 1311 performs machine learning prediction processing using the two or more learners, obtains prediction results and scores for each class, and determines the class to belong to the one with the highest score.

Furthermore, the image inspection means 1311 configures a single learning device that performs multi-class classification, for example, by performing a learning process on training data consisting of two or more pairs of strings and classes, and outputting the classes. Next, the image inspection means 1311 uses the learning device to perform machine learning prediction processing on each of the one or more strings obtained from the receipt image, determining the class to which each string belongs.

The image inspection means 1311, for example, uses a large amount of training data, which consists of pairs of strings and classes, to acquire a learner for classifying strings, using a learning processing module from a machine learning algorithm.
(2) Method using machine learning

The image inspection means 1311 uses, for example, a receipt image and two or more training data sets, each containing one or more pairs of strings and classes, to perform a learning process using a machine learning algorithm and acquire a learner. This learner takes a receipt image as input and outputs one or more pairs of strings and classes.

Next, the image inspection means 1311 provides the acquired learner data and the receipt images contained in the expense information received by the expense reception unit 121 to a module of the machine learning algorithm that performs prediction processing, and acquires one or more pairs of strings and classes.
(3) A method that uses both character recognition processing and machine learning processing.

The image inspection means 1311, for example, uses both (1) and (2) above to obtain strings for each class. If no match is found in the processing of (1) and (2) for each class, it uses the score obtained from the character recognition process and the score obtained from the machine learning process to obtain the string with the higher score that satisfies the condition.

Furthermore, using one or more strings obtained by any of the methods (1) to (3) above, the image inspection means 1311 determines whether each of the one or more strings satisfies predetermined conditions and obtains the image inspection result. The one or more strings may, for example, be any of the following: payment amount information, store identifier, counterparty identifier, usage date information, account, description, or payment method information.

The image inspection means 1311 uses training data, for example, consisting of negative examples (one or more fraudulent receipt images) and positive examples (one or more legitimate receipt images), to perform a learning process using a machine learning algorithm and construct a learning model. Next, the image inspection means 1311 provides the receipt images contained in the expense information received by the expense reception unit 121, along with the learning model, to a machine learning prediction processing module to perform prediction processing and obtain a prediction result indicating whether or not the receipt is fraudulent. The learning model could be, for example, a learning model for detecting fraudulent manipulation of amounts on receipts, a learning model for checking for signatures on receipts, or a learning model for detecting unclear receipt images. Furthermore, the learning model is typically a binary classification model for determining whether or not an item is fraudulent.

The statistical processing unit 132 performs statistical processing based on one or more expense information entries associated with the applicant identifier associated with the received expense information, which are stored in the expense information storage unit 111, and obtains the statistical processing results. For example, the statistical processing unit 132 performs statistical processing based on one or more expense information entries associated with each applicant identifier, which are stored in the expense information storage unit, and obtains the statistical processing results. The timing of the statistical processing unit 132's statistical processing is not restricted. For example, the statistical processing unit 132 performs statistical processing upon receiving user instructions. For example, the statistical processing unit 132 performs statistical processing upon receiving expense information.

The statistical processing unit 132 obtains store frequency information using, for example, two or more expense information records stored in the expense information storage unit 111, which are associated with a single applicant identifier. Store frequency information is information regarding the frequency of use of a store identified by a single store identifier. Store frequency information indicates the frequency of use. For example, store frequency information may indicate the total number of uses or the number of uses within a unit period. The unit period may be, for example, one month, six months, or one year. It is preferable for the statistical processing unit 132 to obtain store frequency information for each applicant identifier.

The statistical processing unit 132 obtains entertainment frequency information using the counterparty identifier contained in two or more expense information records stored in the expense information storage unit 111, which are associated with a single applicant identifier. Entertainment frequency information is information regarding the frequency of expenditures to a counterparty identified by a single counterparty identifier. Expenditures to a counterparty refer to payments for the provision of benefits to the counterparty, such as payments for entertainment or gifts. Entertainment frequency information indicates the frequency of benefit provision. For example, it may indicate the total number of times benefits were provided or the number of times benefits were provided within a unit period. It is preferable for the statistical processing unit 132 to obtain entertainment frequency information for each applicant identifier.

The statistical processing unit 132 obtains the number of fraudulent transactions, which is the number of times a fraudulent transaction was detected in the expense information corresponding to a single applicant identifier, and associates this number with the applicant identifier. It is preferable for the statistical processing unit 132 to obtain the number of fraudulent transactions for each applicant identifier.

The result output unit 141 outputs the inspection results acquired by the inspection unit 131. The result output unit 141 also outputs the image inspection results acquired by the image inspection means 1311.

The result output unit 141 outputs the statistical processing results acquired by the statistical processing unit 132. For example, the result output unit 141 outputs the statistical processing results associated with the applicant identifier.

The first storage unit 21, which constitutes the applicant terminal 2, stores various types of information. These types of information include, for example, the applicant identifier and expense information.

The first reception desk 22 receives various instructions and information. These instructions and information include, for example, expense information and response information. Response information refers to information indicating responses to inspection results.

The first processing unit 23 performs various processes. These processes include, for example, converting instructions and information received by the first receiving unit 22 into instructions and information for the data structure to be transmitted. Another example of these processes is converting information received by the first receiving unit 25 into information for the data structure to be output.

The first transmission unit 24 transmits various instructions and information. These instructions and information include, for example, expense information, applicant identifiers, and response information.

The first receiving unit 25 receives various types of information. These types of information include, for example, inspection results and image inspection results.

The first output unit 26 outputs various types of information. These types of information include, for example, inspection results and image inspection results.

Here, "output" is a concept that includes display on a screen, projection using a projector, printing with a printer, sound output, transmission to an external device, storage on a recording medium, and transfer of processing results to other processing devices or other programs.
(Specific examples of inspection procedures)

The following describes specific examples of inspections performed by the inspection unit 131. While the following primarily describes cases of fraud, in cases of legitimate activity, the inspection unit 131 typically obtains an inspection result indicating "legitimate." Furthermore, in cases of legitimate activity, the inspection unit 131 typically associates the expense information subject to inspection with the applicant identifier and stores it in the expense information storage unit 111.

The information contained in the expense information used by the inspection unit 131 for inspection may be a string received by the expense reception unit 121, or information obtained from the receipt image received by the expense reception unit 121. The string received by the expense reception unit 121 may be, for example, information entered by the applicant.
(1) Inspection using attendance information

The inspection unit 131 obtains, for example, attendance information from the attendance information storage unit 1122 that is associated with an applicant identifier linked to the expense information received by the expense reception unit 121, and that includes the same workday information as the usage day information included in the expense information received by the expense reception unit 121. Next, the inspection unit 131 uses this attendance information to inspect the expense information received by the expense reception unit 121 for any irregularities and obtains the inspection results.
(1-1) Inspection of expenses incurred on days other than working days

The inspection unit 131 obtains attendance information from the attendance information storage unit 1122, for example, attendance information that is associated with an applicant identifier linked to expense information received by the expense reception unit 121, and which includes the same workday information as the usage day information included in the expense information received by the expense reception unit 121. Next, the inspection unit 131 determines whether the attendance information is for a day that is not a workday. If it is for a day that is not a workday, the inspection unit 131 obtains an inspection result indicating that it is an "unauthorized expense for a day that is not a workday." The inspection unit 131 determines that the attendance information is for a day that is not a workday based on whether the attendance information includes "information indicating that it is a holiday," or whether the attendance information does not include the start time and end time of work.
(1-2) Inspection of fraudulent travel expenses

The inspection unit 131 obtains the applicant identifier and usage date information associated with the expense information received by the expense reception unit 121. Next, the inspection unit 131 obtains attendance information corresponding to the obtained applicant identifier and usage date information from the attendance information storage unit 1122. Next, if the inspection unit 131 determines that the obtained attendance information does not indicate a business trip, it obtains an inspection result indicating "fraudulent fictitious business trip." The case where "the attendance information does not indicate a business trip" is, for example, (a) the attendance information does not contain information indicating a "business trip," or (b) the attendance information contains information on the start time and end time of work.
(1-3) Inspection of fraudulent accommodation charges

The inspection unit 131 obtains the applicant identifier and usage date information associated with the expense information received by the expense reception unit 121. Next, the inspection unit 131 obtains working hours information from the working day information corresponding to the obtained applicant identifier and usage date information. Then, using the obtained working hours information, the inspection unit 131 determines whether or not accommodation at the lodging facility is permitted and obtains the inspection result.

More specifically, the inspection unit 131 compares the end time of work recorded in the work time information with the overtime time information indicating the overtime hours for which accommodation is permitted, and determines whether the predetermined accommodation conditions are met. If the inspection unit 131 determines that the accommodation conditions are not met, it obtains an inspection result stating that "the claim for accommodation expenses is fraudulent." The accommodation conditions are based on the overtime time information and the end time of work, for example, "overtime time information = < end time of work" and "overtime time information < end time of work."
(2) Inspection using entry and exit information

The inspection unit 131 obtains entry/exit information from the entry/exit information storage unit 1123, which is entry/exit information associated with the applicant identifier associated with the expense information and corresponds to the date specified by the usage date information contained in the expense information. Using this entry/exit information, it performs an inspection for fraudulent activity in the expense information received by the expense reception unit 121 and obtains the inspection results.
(2-1) Inspection of expenses incurred on days other than working days

The inspection unit 131 obtains the applicant identifier and usage date information associated with the expense information received by the expense reception unit 121. Next, the inspection unit 131 processes the entry/exit information corresponding to the obtained applicant identifier and usage date information to be obtained from the entry/exit information storage unit 1123. Next, the inspection unit 131 determines whether the entry/exit information is for a day that is not a working day. If it is for a day that is not a working day, the inspection unit 131 obtains an inspection result indicating that it is an "illegal expense for a day that is not a working day". The inspection unit 131 determines that the entry/exit information is for a day that is not a working day by whether the entry/exit information includes "information indicating that it is a holiday" or whether the entry/exit information does not include the start time and end time of work.
(2-2) Inspection of fraudulent travel expenses

The inspection unit 131 obtains the applicant identifier and usage date information associated with the expense information received by the expense reception unit 121. Next, the inspection unit 131 processes the entry/exit information corresponding to the obtained applicant identifier and usage date information from the entry/exit information storage unit 1123. Next, if the inspection unit 131 determines that the result of the entry/exit information acquisition process is not information indicating a business trip, it obtains an inspection result indicating "fraudulent fictitious business trip". The case where "the result of the entry/exit information acquisition process is not information indicating a business trip" is, for example, (a) when entry/exit information is obtained, or (b) when the information on the start time and end time of work contained in the obtained entry/exit information is the start time information and end time of work for normal work. The start time information and end time of work for normal work is stored, for example, in the company regulations information.
(2-3) Inspection of fraudulent accommodation charges

The inspection unit 131 obtains the applicant identifier and usage date information associated with the expense information received by the expense reception unit 121. Next, the inspection unit 131 obtains the end time of work from the entry/exit information corresponding to the obtained applicant identifier and usage date information. Then, using the obtained end time of work, the inspection unit 131 determines whether or not accommodation at the lodging facility is permitted and obtains the inspection result.

More specifically, the inspection unit 131 compares the end time of work with overtime information indicating the overtime hours for which accommodation is permitted, and determines whether the predetermined accommodation conditions are met. If the inspection unit 131 determines that the accommodation conditions are not met, it obtains an inspection result stating that "the claim for accommodation expenses is fraudulent." The overtime information is stored, for example, in the company regulations information.
(3) Inspection using sales activity information

The inspection unit 131 obtains from the sales activity information storage unit 1124 one or more location identifiers from the sales activity information storage unit 1124 that are sales activity information associated with the applicant identifier associated with the expense information received by the expense reception unit 121, and that have the same business day information as the usage date information in the expense information, and uses these one or more location identifiers to perform an inspection for fraud in the expense information received by the expense reception unit 121 and obtains the inspection results.
(3-1) Inspection of fraudulent travel expenses (i)

The inspection unit 131 provides the transportation expense calculation module with information indicating the company's location and one or more location identifiers from the business activity information. Using the calculation information for calculating transportation expenses, it obtains one or more transportation expenses. It is preferable that the obtained transportation expense is the cheapest option. Obtaining two or more transportation expenses occurs when there are two or more travel routes. The transportation expense acquisition technology and the technology for obtaining the cheapest transportation expense are publicly known technologies, so a detailed explanation is omitted. The inspection unit 131 also obtains expenditure amount information from the expense information received by the expense reception unit 121.

Next, the inspection unit 131 uses the expenditure amount information and the acquired transportation expenses to determine whether the expenditure amount information meets the predetermined conditions for legitimate transportation expenses. If the conditions for legitimate transportation expenses are not met, an inspection result indicating that "the transportation expense claim is fraudulent" is obtained. The conditions for legitimate transportation expenses are, for example, "expense amount information = the cheapest transportation expense,""expense amount information matches one or more transportation expenses," and "expense amount information <= one or more transportation expenses."
(3-2) Inspection of fraudulent travel expenses (ii)

The inspection unit 131 obtains transportation expense information containing departure identifiers and arrival identifiers from the expense information received by the expense reception unit 121. The inspection unit 131 also obtains one or more location identifiers from the business activity information. The inspection unit 131 then determines whether the distance between the departure identifier and any of the location identifiers is close enough to meet predetermined conditions. If the distance between the departure identifier and all of the location identifiers does not meet the predetermined conditions, the inspection unit 131 obtains an inspection result indicating that "the transportation expense claim is fraudulent." The inspection unit 131 also determines whether the distance between the arrival identifier and any of the location identifiers is close enough to meet predetermined conditions. If the distance between the arrival identifier and all of the location identifiers does not meet the predetermined conditions, the inspection unit 131 obtains an inspection result indicating that "the transportation expense claim is fraudulent."

Furthermore, the technique for calculating the distance between the departure identifier or arrival identifier and each point identifier is publicly known.
(4) Inspection using card statement information

The inspection unit 131 obtains card statement information from the card statement information storage unit 1125 that is associated with an applicant identifier linked to the expense information received by the expense reception unit 121, and has the same usage date information as the usage date information contained in the expense information. Using this card statement information, the unit performs an inspection for fraudulent activity in the expense information received by the expense reception unit 121 and obtains the inspection results.
(4-1) Inspection of receipt splitting

The inspection unit 131 obtains from the card statement information storage unit 1125 card statement information that is associated with the applicant identifier linked to the expense information received by the expense reception unit 121 and has the same usage date information as the usage date information in the expense information. If the inspection unit 131 can obtain two or more card statement information and determines that the store identifiers in each of the two or more card statement information are the same, it obtains an inspection result indicating that "there is fraud in the splitting of receipts."
(4-2) Inspection of taxi use after company drinking parties

The inspection unit 131 obtains card statement information associated with the applicant identifier linked to the expense information received by the expense reception unit 121. The inspection unit 131 also uses the information contained in the card statement information to determine whether or not the expense is for taxi use. If it is for taxi use, the inspection unit 131 obtains one or more participant information items (for example, the names of the participants) included in the expense information that contains the same usage date information as the usage date information contained in the card statement information. Next, the inspection unit 131 determines whether or not all of the one or more participant information items correspond to personal information held in the personal information storage unit 1121 (employee database) (for example, whether or not they include the names of the participants). If all of the one or more participant information items correspond to personal information, the inspection unit 131 obtains an inspection result indicating that it is "taxi use after a company drinking party".
(5) Inspection using the location information of company vehicles

The inspection unit 131 obtains from the vehicle location information storage unit 1126 one or more vehicle location information that corresponds to the applicant identifier associated with the expense information received by the expense reception unit 121, and that corresponds to the same usage date information as the usage date information contained in the expense information. Next, the inspection unit 131 uses the vehicle location information to perform an inspection for fraud in the expense information and obtains the inspection results.
(5-1) Inspection of the misuse of company vehicles (inspection of illegal locations)

The inspection unit 131 determines whether the acquired location information for one or more company vehicles is close enough to a predetermined illegal location (for example, a tourist spot) to meet predetermined conditions. If it determines that the location is close enough to meet the predetermined conditions, the inspection unit 131 obtains an inspection result indicating that "the company vehicle is being used illegally." The information on predetermined illegal locations is included, for example, in company regulations.
(6) Inspection using card usage expense information

The inspection unit 131 checks whether the expense type identifier associated with the expense information received by the expense reception unit 121 is stored in the card usage expense storage unit 117 as the expense type identifier associated with the owned card information associated with the applicant identifier associated with the expense information received by the expense reception unit 121, and obtains the inspection result. For example, it is assumed that the card usage expense storage unit 117 stores that food and beverage expenses or entertainment expenses are paid by credit card.
(7) Inspection using company regulations

The inspection unit 131 uses the company regulations information stored in the company regulations information storage unit 113 to inspect whether the expense information received by the expense reception unit 121 conforms to the company regulations specified by the company regulations information, and obtains the inspection result. Specific examples of inspections using company regulations information include, for example, (2-2), (2-3), (13-1) and (13-2) described later, (14-3)(a) described later, and (14-4)(a) described later.
(8) Inspection using information on means of transportation

The inspection unit 131 uses the expense information received by the expense reception unit 121 and the transportation information stored in the transportation information storage unit 118 to conduct an inspection for fraudulent travel expenses and obtain the inspection results.
(8-1) Inspection of fraudulent train, bus, or airplane travel expenses

The inspection unit 131 obtains applicant information associated with the applicant identifier linked to the expense information related to transportation expenses received by the expense reception unit 121. Using the applicant information, or the applicant information and the means of transportation information, it performs an inspection for fraud related to transportation expense claims and obtains the inspection results.

More specifically, the inspection unit 131 obtains transportation expense information from the expense information received by the expense reception unit 121, which includes one or more section information entries containing a departure identifier, an arrival identifier, and fare information. Next, the departure identifier and arrival identifier from each of the one or more section information entries are provided to the transportation expense calculation module, and one or more transportation expenses are obtained using the calculation information for calculating transportation expenses. It is preferable that the transportation expenses obtained here be the cheapest transportation expenses. Furthermore, obtaining two or more transportation expenses occurs when there are two or more travel routes. The transportation expense acquisition technology and the technology for obtaining the cheapest transportation expenses are publicly known technologies, so a detailed explanation is omitted. It is also preferable to obtain the transportation expenses using an external server 3.

Furthermore, the inspection unit 131 obtains expenditure amount information from the expense information received by the expense reception unit 121.

Next, the inspection unit 131 uses the fare information and the transportation expenses to determine whether the fare information meets the predetermined conditions for legitimate transportation expenses. If the conditions for legitimate transportation expenses are not met, an inspection result indicating that "the transportation expense claim is fraudulent" is obtained. The conditions for legitimate transportation expenses are, for example, "fare information = the cheapest transportation expense,""fare information matches one or more transportation expenses," and "fare information <= one or more transportation expenses."
(8-2) Inspection of fraudulent taxi fares

The inspection unit 131 obtains applicant information associated with the applicant identifier linked to the expense information regarding taxi fares received by the expense reception unit 121. Using this applicant information, or the applicant information and transportation method information, the unit performs an inspection for fraud related to transportation expense claims and obtains the inspection results.

More specifically, the inspection unit 131 obtains transportation expense information, which includes a departure identifier, an arrival identifier, and expenditure amount information, from the expense information received by the expense reception unit 121. Next, it obtains the distance traveled using the departure identifier, arrival identifier, and map information contained in the transportation expense information. Then, the inspection unit 131 obtains the taxi fare using this distance and calculation information for calculating the taxi fare. Note that the technology for obtaining the taxi fare is publicly known, so a detailed explanation is omitted. Furthermore, it is preferable to obtain the taxi fare using an external server 3.

Furthermore, the inspection unit 131 obtains expenditure amount information from the expense information received by the expense reception unit 121.

Next, the inspection unit 131 uses the expenditure amount information and the taxi fare to determine whether the expenditure amount information meets the predetermined conditions for a legitimate taxi fare. If the conditions for a legitimate taxi fare are not met, the inspection result "that the transportation expense claim is fraudulent" is obtained. The conditions for a legitimate transportation expense are, for example, "expense amount information = taxi fare", "expense amount information - taxi fare <= threshold", and "expense amount information - taxi fare <threshold".
(8-3) Checking for overlap with regular routes

The inspection unit 131 retrieves from the personal information storage unit 1121 the regular route information associated with the applicant identifier linked to the expense information related to transportation expenses received by the expense reception unit 121. Next, the inspection unit 131 retrieves transportation expense information from the expense information received by the expense reception unit 121, which includes one or more route information entries having departure identifiers and arrival identifiers.

Next, the inspection unit 131 uses the means of transport information to determine whether there is any overlap between the section specified by the regular section information and the sections specified by one or more section information. For example, the inspection unit 131 uses the means of transport information to create a set of station names (station name group 1) by arranging the station names within the sections of one or more section information in order. Then, the inspection unit 131 uses the means of transport information to obtain a set of station names (station name group 2) by arranging the station names within the section specified by the regular section information in order. Then, the inspection unit 131 determines whether there are two or more consecutive identical station names in station name group 1 and station name group 2. If there are two or more consecutive identical station names, the inspection unit 131 obtains an inspection result indicating that "the requested transportation expenses include the regular section."
(9) Inspection using store information

The inspection unit 131 uses the store identifier contained in the expense information received by the expense reception unit 121 and the store information contained in the store set to perform an inspection for fraudulent expense information and obtain the inspection results. The store set is, for example, the restaurant set in the restaurant set storage unit 114 or the restaurant set in the adult entertainment establishment set storage unit 115, but it may also be a restaurant set or adult entertainment establishment set located in an external device (not shown).
(9-1) Inspection of store misconduct (use of adult entertainment establishments, etc.)

The inspection unit 131, for example, obtains a store identifier from the expense information received by the expense reception unit 121. Next, the inspection unit 131 checks whether the obtained store identifier (adult entertainment establishment identifier) is stored in the adult entertainment establishment aggregation storage unit 115, and if it is stored, it obtains an inspection result indicating "fraudulent use of expenses at an adult entertainment establishment that should not be visited." It is preferable that such an inspection result includes adult entertainment establishment information containing the store identifier in the adult entertainment establishment aggregation storage unit 115.
(9-2) Inspection of financial irregularities (a) Inspection of the total amount

The inspection unit 131, for example, obtains amount information from the restaurant aggregation storage unit 114 that corresponds to the store identifier in the expense information received by the expense reception unit 121. Next, the inspection unit 131 obtains expenditure amount information from the expense information received by the expense reception unit 121. Next, the inspection unit 131 compares the obtained expenditure amount information with the obtained amount information and determines whether the information indicates an amount high enough to satisfy predetermined conditions. Then, if the information indicates an amount high enough to satisfy predetermined conditions, the inspection unit 131 obtains an inspection result indicating that "an improper amount of expense was used." The predetermined conditions are, for example, "expense amount information - amount information >= threshold", "expense amount information - amount information >threshold","expense amount information / amount information >= threshold", and "expense amount information / amount information >threshold". It goes without saying that each threshold may be different.
(9-3) Inspection of whether or not entertainment expenses involve the use of restaurants.

The inspection unit 131, for example, obtains the expense type identifier from the expense information received by the expense reception unit 121. Next, the inspection unit 131 determines whether the expense type identifier corresponds to "entertainment expenses." If it does, the inspection unit 131 obtains the store identifier from the expense information received by the expense reception unit 121. Next, the inspection unit 131 determines whether the store identifier is an identifier for a restaurant. If it is not a restaurant identifier, the inspection unit 131 obtains an inspection result indicating that "this is a fraudulent entertainment expense claim."

The inspection unit 131 determines whether a store identifier is a restaurant identifier by, for example, whether the store identifier is stored in the restaurant aggregation storage unit 114. Alternatively, the inspection unit 131 may perform a web search using the store identifier as a key and determine whether a store identifier is a restaurant identifier by checking whether the retrieved web pages contain information indicating a restaurant (e.g., izakaya, Italian, dish name, etc.). Furthermore, other methods may be used for clustering the store identifiers. In other words, the algorithm used to determine whether a store identifier is a restaurant identifier is not limited.
(b) Examination of the amount per person

The inspection unit 131 obtains, for example, amount information from the restaurant aggregation storage unit 114 that corresponds to the store identifier in the expense information received by the expense reception unit 121. Next, the inspection unit 131 obtains, for example, expenditure amount information from the expense information received by the expense reception unit 121. The inspection unit 131 also obtains, for example, the number of people information from the expense information received by the expense reception unit 121, or the number of people information obtained from the participant information in the expense information. Next, the inspection unit 131 uses the obtained expenditure amount information, the obtained amount information, and the number of people information to determine whether the amount per person is high enough to meet predetermined conditions. If the amount per person is high enough to meet predetermined conditions, the inspection unit 131 obtains an inspection result indicating that "an amount of fraudulent expenses was used." The predetermined conditions are, for example, "(Expenditure amount information / Number of people information) - Amount information >= Threshold", "(Expenditure amount information / Number of people information) - Amount information >Threshold","(Expenditure amount information / Number of people information) / Amount information >= Threshold", and "(Expenditure amount information / Number of people information) / Amount information >Threshold". Needless to say, each threshold can be different.
(10) Inspection using counterparty information

The inspection unit 131 uses the counterparty identifier contained in the expense information received by the expense reception unit 121 and one or more counterparty information contained in the external information to perform an inspection for fraudulent expense information and obtain the inspection result. One or more counterparty information is, for example, a set of counterparties. The set of counterparties is, for example, the set of counterparties in the counterparty set storage unit 116.
(10-1) Inspection of the provision of benefits to public officials

The inspection unit 131 obtains the counterparty identifier contained in the expense information received by the expense reception unit 121. Next, the inspection unit 131 determines whether the obtained counterparty identifier exists in the counterparty collection storage unit 116 where information on public officials is stored. If it exists, it obtains an inspection result indicating "impropriety in providing improper benefits to a public official."
(10-2) Inspection of the provision of benefits to lawmakers

The inspection unit 131 obtains the recipient identifier contained in the expense information received by the expense reception unit 121. Next, the inspection unit 131 determines whether the obtained recipient identifier exists in the recipient collection storage unit 116 where the information of the member of parliament is stored. If it exists, it obtains an inspection result indicating "impropriety in providing an improper benefit to the member of parliament."
(11) Inspection using past expense information (11-1) Inspection of duplicate applications

The inspection unit 131 determines whether the expense information received by the expense reception unit 121 and one or more past expense records stored in the expense information storage unit 111, which are associated with the same applicant identifier as the expense information, are similar enough to satisfy predetermined conditions, and obtains the inspection result.

For two sets of expense information to be "similar enough to satisfy predetermined conditions," this means, for example, that among the expenditure amount information, store identifier, counterparty identifier, date of use information, account, description, and approver identifier contained in the expense information received by the expense receiving unit 121, (a) a predetermined number or more of the information match, or (b) all of one or more predetermined pieces of information match. The predetermined one or more pieces of information are one or more of the expenditure amount information, store identifier, and counterparty identifier contained in the expense information received by the expense receiving unit 121.
(11-2) Inspection of the reuse of receipts

If the inspection unit 131 determines that the receipt image in the expense information received by the expense reception unit 121 and the receipt image in the past expense information stored in the expense information storage unit 111 are similar enough to satisfy predetermined conditions, it obtains an inspection result indicating that "there is fraudulent reuse of receipts." It is preferable that the receipt image in the past expense information used by the inspection unit 131 for inspection is an image associated with the same applicant identifier as the applicant identifier associated with the expense information received by the expense reception unit 121 (an image of a receipt previously used by the applicant), but an image associated with a different applicant identifier is also acceptable. Specifically, for example, the reuse of receipts is inspected using either of the following methods (a) or (b).
(a) When using image similarity

The inspection unit 131, for example, obtains the similarity between the receipt image of the expense information received by the expense reception unit 121 and the receipt images of one or more past expense information items stored in the expense information storage unit 111. If the similarity is equal to or greater than a threshold, the inspection unit obtains an inspection result indicating that "there is fraud in the reuse of receipts." The inspection result may also include past expense information that has been determined to be reused, the receipt images of past expense information that has been determined to be reused, etc.
(b) In the case of machine learning

The inspection unit 131 constructs a learning model using training data that includes, for example, one or more pairs of receipt images that a human judged to be reused as positive examples, and one or more pairs of two different receipts as negative examples, through a machine learning training process. This learning model outputs whether or not the receipts are reused (i.e., identical or not).

Next, the inspection unit 131 uses the learning device, the receipt image contained in the expense information received by the expense reception unit 121, and the past receipt images in the expense information storage unit 111 to perform machine learning prediction processing. If it obtains an output result indicating reuse, it acquires an inspection result stating that "the reuse of receipts is fraudulent." It is preferable that the past receipt images in the expense information storage unit 111 are receipt images associated with the applicant identifier corresponding to the expense information received by the expense reception unit 121.
(11-3) Inspection of the large number of expense claims on the same day

The inspection unit 131 inspects two or more expense records associated with a single applicant identifier, determines whether the number of expense records with the same usage date information is large enough to meet predetermined conditions, and obtains the inspection result. If the number of expense records is large enough to meet predetermined conditions, the inspection unit 131 obtains an inspection result indicating fraud.

The number of expense entries with the same usage date information that correspond to a single applicant identifier may be obtained by the statistical processing unit 132.
(11-4) Inspection of fraudulent spending on after-party expenses

The inspection unit 131 inspects two or more expense entries associated with a single applicant identifier, determines whether the number of expense entries with the same usage date information but different restaurant identifiers is large enough to meet predetermined conditions, and obtains the inspection result. For example, if there are expense applications for two or more restaurants on the same day, it means that expenses were also used for after-parties, and the inspection result obtained indicates that "there is fraud due to after-party expenses."
(12) Tests using statistical processing results

The inspection unit 131 checks whether the statistical processing results obtained by the statistical processing unit 132 meet predetermined conditions and obtains the inspection results.
(12-1) Tests using store frequency information

The inspection unit 131 checks whether the store frequency information acquired by the statistical processing unit 132 is large enough to satisfy predetermined conditions, and obtains the inspection result. If the store frequency information is large enough to satisfy the predetermined store frequency condition, the inspection unit 131 obtains an inspection result indicating that "one store is being used too much." The store frequency condition is an example of a fraudulent condition. For example, the store frequency condition is "store frequency information >= threshold" or "store frequency information >threshold". The store frequency condition is stored in the storage unit 11, for example.
(12-2) Examination using information on the frequency of hospitality services

The inspection unit 131 checks whether the entertainment frequency information acquired by the statistical processing unit 132 meets predetermined conditions and obtains the inspection result. If the entertainment frequency information is large enough to meet the predetermined conditions, the inspection unit 131 obtains an inspection result indicating that "the number of times entertainment etc. is provided to one client is too high (potential for collusion, etc.)." The entertainment frequency conditions are an example of fraudulent conditions. For example, the entertainment frequency conditions are "entertainment frequency information >= threshold" and "entertainment frequency information >threshold". The entertainment frequency conditions are stored in, for example, the storage unit 11.
(12-3) Inspection of the number of times an applicant has committed fraud.

The inspection unit 131 checks whether the number of fraudulent transactions obtained by the statistical processing unit 132 satisfies predetermined conditions, namely the fraudulent transaction count conditions, and obtains an inspection result indicating that "the applicant has a high number of fraudulent transactions." The predetermined conditions are, for example, "the total number of fraudulent transactions to date is equal to or greater than the threshold" or "the number of fraudulent transactions in a unit period (e.g., 1 year, 3 years) is equal to or greater than the threshold." Note that the fraudulent transaction count conditions are just examples of fraudulent conditions. For example, the fraudulent transaction count conditions are "number of fraudulent transactions >= threshold" or "number of fraudulent transactions >threshold." The fraudulent transaction count conditions are stored, for example, in the storage unit 11.
(13) Detection of fraud by approvers of expense claims

The inspection unit 131 checks whether the approver identified by the approver identifier in the received expense information is the same approver identified by the approver information, and obtains the inspection result.
(13-1) When there are approved approvers in control

The inspection unit 131, for example, determines whether the approver identifier contained in the received expense information is included in the approver information stored in the company regulations information of the company regulations information storage unit 113. If it is not included, it obtains an inspection result indicating that the approver is "an improper approver."
(13-2) When the positions that can be approved are managed

For example, the inspection unit 131 obtains a job title identifier that corresponds to the approver identifier in the received expense information from the personal information storage unit 1121, determines whether the job title identifier is included in the approver information stored in the company regulations information storage unit 113, and if it is not included, obtains an inspection result indicating that the approver is "an improper approver".
(14) Detection of application omissions

The inspection unit 131 uses applicant information corresponding to a single applicant identifier to determine whether expense information corresponding to the applicant information exists in the expense information storage unit 111, which stores one or more expense information associated with a single applicant identifier. It then checks for any missing applications to determine whether an application for the corresponding expense has been submitted and obtains the inspection result. The applicant information may include, for example, attendance information, entry/exit information, sales activity information, card statement information, and company vehicle location information.
(14-1) Detection of application omissions using attendance information (a) Omission of application for labor wage expenses

The inspection unit 131 retrieves attendance information corresponding to a single applicant identifier from the attendance information storage unit 1122. Next, the inspection unit 131 determines whether the retrieved attendance information corresponds to attendance that does not fall within the scope of payroll. If it determines that the attendance information corresponds to attendance that does not fall within the scope of payroll, the inspection unit 131 determines whether there is expense information in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the work day information in the attendance information, and has an expense type identifier indicating labor wages (e.g., "labor wages"). If it determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result stating that "expenses corresponding to the attendance information have not been applied for."

To determine whether the acquired attendance information is attendance that does not fall within the scope of pay, the inspection unit 131, for example, acquires the day of the week information contained in the attendance information, and if the day of the week information is a day that is not a working day (for example, Saturday, Sunday, or public holiday), it determines that the acquired attendance information is attendance that does not fall within the scope of pay. The inspection unit 131 also, for example, acquires the applicant identifier corresponding to the attendance information, and if the applicant type information paired with the applicant identifier is predetermined information (for example, "part-time worker" or "casual worker"), it determines that the acquired attendance information is attendance that does not fall within the scope of pay. The applicant type information is information contained in the personal information stored in the personal information storage unit 1121.
(b) Failure to submit travel expense claims

The inspection unit 131 retrieves attendance information corresponding to a single applicant identifier from the attendance information storage unit 1122. Next, the inspection unit 131 determines whether the retrieved attendance information corresponds to a business trip. If the attendance information corresponds to a business trip, the inspection unit 131 determines whether expense information exists in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the workday information in the attendance information, and has the expense type identifier (e.g., "business trip expenses," "travel expenses") for the expenses applied for during the business trip. If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "expenses corresponding to the business trip have not been applied for."

Furthermore, the inspection unit 131 determines, for example, that attendance information corresponds to a business trip if it has a business trip flag indicating that the attendance information is for a business trip. Also, the inspection unit 131 determines, for example, that attendance information corresponds to a business trip if it does not have start time information and end time information. Also, the inspection unit 131 determines, for example, that attendance information corresponds to a business trip if it has a location identifier indicating the destination of the business trip.
(c) Failure to apply for overseas daily allowances

The inspection unit 131 retrieves attendance information corresponding to a single applicant identifier from the attendance information storage unit 1122. Next, the inspection unit 131 determines whether the retrieved attendance information corresponds to an overseas business trip. If the attendance information corresponds to an overseas business trip, the inspection unit 131 determines whether expense information exists in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the workday information in the attendance information, and has an expense type identifier for the expenses applied for during the overseas business trip (e.g., "overseas daily allowance," "overseas business trip allowance"). If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "expenses corresponding to the overseas business trip have not been applied for."

Furthermore, the inspection unit 131 determines, for example, that attendance information corresponds to an overseas business trip if it contains an overseas business trip flag indicating that the attendance information is for an overseas business trip. Also, the inspection unit 131 determines, for example, that attendance information corresponds to an overseas business trip if it contains a location identifier indicating the destination of the overseas business trip.

Furthermore, the inspection unit 131 may, for example, obtain the amount information for overseas business trips contained in the company regulations information storage unit 113, compare it with the amount information in the corresponding expense information, and if they do not match, obtain an inspection result indicating "fraudulent application for overseas daily allowance."

Furthermore, the inspection unit 131 obtains, for example, sales activity information corresponding to a single applicant identifier from the sales activity information storage unit 1124. If the inspection unit 131 determines that the location identifier in the sales activity information corresponds to a location identifier for an overseas business trip, it obtains the business day information in that sales activity information. Next, the inspection unit 131 determines whether there is expense information in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the obtained business day information, and has an expense type identifier for expenses applied for during an overseas business trip. If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result stating that "expenses corresponding to the overseas business trip have not been applied for."
(14-2) Detection of application omissions using entry and exit information (a) Omission of application for labor wage expenses

The inspection unit 131 retrieves entry/exit information corresponding to a single applicant identifier from the entry/exit information storage unit 1123. Next, the inspection unit 131 determines whether the retrieved entry/exit information corresponds to work outside the scope of pay. If it determines that the entry/exit information corresponds to work outside the scope of pay, the inspection unit 131 determines whether there is expense information in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the work date information in the entry/exit information, and has an expense type identifier indicating labor wages (e.g., "labor wages"). If it determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result stating that "expenses corresponding to the entry/exit information have not been applied for."

Regarding whether the acquired entry and exit information is attendance that does not fall within the scope of pay, the inspection unit 131, for example, acquires the day of the week information contained in the entry and exit information, and if the day of the week information is a day that is not a working day (for example, Saturday, Sunday, or public holiday), it determines that the acquired entry and exit information is attendance that does not fall within the scope of pay. The inspection unit 131, for example, acquires the applicant identifier corresponding to the entry and exit information, and if the applicant type information paired with the applicant identifier is predetermined information (for example, "part-time worker" or "casual worker"), it determines that the acquired entry and exit information is work that does not fall within the scope of pay.
(b) Failure to submit travel expense claims

The inspection unit 131 retrieves entry/exit information corresponding to a single applicant identifier from the entry/exit information storage unit 1123. Next, the inspection unit 131 determines whether the retrieved entry/exit information corresponds to a business trip. If the entry/exit information corresponds to a business trip, the inspection unit 131 determines whether expense information exists in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the workday information contained in the entry/exit information, and has an expense type identifier for the expenses applied for during the business trip (e.g., "business trip expenses," "travel and transportation expenses"). If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "expenses corresponding to the business trip have not been applied for."

Furthermore, the inspection unit 131 determines, for example, that entry/exit information corresponds to a business trip if it does not have start time information and end time information. The inspection unit 131 determines, for example, that entry/exit information corresponds to a business trip if it determines that the attendance information, which corresponds to a single applicant identifier and has the same workday information as the usage date information, indicates attendance (not absence).
(14-3) Detection of application omissions using sales activity information (a) Omission of travel expense applications

The inspection unit 131 retrieves sales activity information corresponding to a single applicant identifier from the sales activity information storage unit 1124. Next, the inspection unit 131 determines whether the retrieved sales activity information corresponds to a business trip. If the sales activity information corresponds to a business trip, the inspection unit 131 determines whether expense information exists in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the sales activity information, and has the expense type identifier (e.g., "business trip expenses," "travel and transportation expenses") for the expenses applied for during the business trip. If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "expenses corresponding to the business trip have not been applied for."

Furthermore, the inspection unit 131, for example, uses the location identifier contained in the sales activity information and predetermined company location information to obtain the distance between the location identified by the location identifier and the company using the map information stored in the map information storage unit 1182. If it determines that this distance is greater than or equal to the distance at which travel expenses are incurred, it determines that the sales activity information corresponds to a business trip. The information regarding the minimum distance at which travel expenses are incurred is stored, for example, in the company regulations information storage unit 113.

Furthermore, the inspection unit 131 determines, for example, that the sales activity information corresponds to business travel information when the sales activity information includes a location identifier.

The algorithm used to determine whether sales activity information corresponds to business travel is not specified. Sales activity information may include a flag indicating whether or not it is a business trip.
(b) Failure to claim travel expenses

The inspection unit 131 retrieves one or more location identifiers from the business activity information storage unit 1124 that correspond to a single applicant identifier. Next, the inspection unit 131 uses the pre-stored company location information and the retrieved one or more location identifiers to determine whether or not transportation expenses are incurred. If it determines that transportation expenses are incurred, the inspection unit 131 determines whether or not expense information exists in the expense information storage unit 111 that has the same usage date information as the business day information in the business activity information and has the expense type identifier "travel expenses." If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "transportation expenses have not been applied for."

Regarding whether or not transportation expenses are incurred, the inspection unit 131 determines this using, for example, the calculation information stored in the calculation information storage unit 1181. Specifically, the inspection unit 131 provides, for example, the company's location information and a location identifier to a calculation module that calculates transportation expenses, and determines whether or not information on transportation expenses is output. The inspection unit 131 also obtains, for example, the distance between the company's location information and the location identifier using map information, and determines whether or not transportation expenses are incurred based on whether or not this distance is above a threshold. The calculation module is based on publicly known technology.
(14-4) Detection of application omissions using company vehicle location information (a) Omission of travel expense applications

The inspection unit 131 obtains one or more vehicle location information entries corresponding to one applicant identifier and one usage date from the vehicle location information storage unit 1126. Next, the inspection unit 131 determines whether the obtained vehicle location information corresponds to a business trip. If the vehicle location information corresponds to a business trip, the inspection unit 131 determines whether there is expense information in the expense information storage unit 111 that corresponds to one applicant identifier, has the same usage date information as the vehicle location information, and has an expense type identifier (e.g., "business trip expenses") for the expenses applied for during the business trip. If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "expenses corresponding to the business trip have not been applied for."

Furthermore, the inspection unit 131, for example, uses the location information of one or more sales vehicles and the company's location information stored in advance to obtain the maximum distance between the location indicated by the sales vehicle location information and the company using the map information stored in the map information storage unit 1182. If it determines that this maximum distance is greater than or equal to the distance at which travel expenses are incurred, it determines that the sales activity information corresponds to travel. The information regarding the minimum distance at which travel expenses are incurred is stored, for example, in the company regulations information storage unit 113.

Furthermore, the inspection unit 131 determines that the business activity information corresponds to a business trip if, for example, there is a business trip flag associated with one or more business vehicle location information entries. The business trip flag is a flag that indicates that the activity is a business trip.

The output unit 14 outputs various types of information. These types of information include, for example, inspection results, image inspection results, and statistical processing results. Here, output usually means transmission to the applicant terminal 2, but it may also mean transmission to other devices such as accounting terminals, storage in the expense inspection device 1, display on a display, etc.
(15) Receipt image inspection performed by image inspection means 1311

The image inspection means 1311 performs one or more processes from among, for example, character recognition processing and machine learning processing (such as any of the methods (1) to (3) above), obtains one or more strings, determines whether each of the one or more strings satisfies predetermined conditions, and obtains the image inspection result. The one or more strings are, for example, one of the following: payment amount information, store identifier, counterparty identifier, usage date information, account, description, or payment method information.

Examples of inspections performed by the image inspection means 1311 are (15-1) to (15-9) below. The image inspection means 1311 performs, for example, one or more of the inspections from (15-1) to (15-9) and obtains the image inspection results. Note that (15-1) to (15-9) are examples of receipt image inspections.
(15-1) Checking for discrepancies between receipt images and expense information text.

The image inspection means 1311 obtains one or more pairs of strings and classes from the receipt image containing the expense information received by the expense reception unit 121. Next, for each pair, the inspection unit 131 obtains the string corresponding to the class in that pair, which is contained in the expense information received by the expense reception unit 121 (for example, one of the following: payment amount information, store identifier, counterparty identifier, usage date information, account, description, or payment method information). Next, for each pair, the inspection unit 131 compares the string of one class obtained from the receipt image with the string of the same class in the expense information received by the expense reception unit 121, and determines whether a predetermined relationship exists. If a predetermined relationship does not exist, the inspection unit 131 obtains an inspection result indicating fraud.

Furthermore, a predetermined relationship is one of agreement, but it must also be similar enough to satisfy predetermined conditions (for example, the similarity must be above a threshold, the only difference being "(株)" and "株式会社", the only difference being the spelling, etc.).
(15-2) Inspection of monetary value processing (a) When character recognition processing is used

The image inspection means 1311, for example, uses character recognition technology to obtain a string of characters and a score from the amount region of the receipt image, and determines that the amount on the receipt has been altered if it determines that the score is low enough to meet predetermined conditions. For example, the image inspection means 1311 obtains all the characters in the receipt image using character recognition technology, detects the character "￥" from the set of characters, and obtains the string of numbers next to the character "￥" as payment amount information.
(b) When machine learning processing is used

The image inspection means 1311, for example, uses one or more receipt images with falsified amounts (by handwriting) and one or more receipt images without falsification as training data. It performs a learning process using a machine learning algorithm and configures a learning device that takes a receipt image as input to obtain an inspection result determining whether or not the amount has been falsified.

Next, the image inspection means 1311 uses, for example, the receipt image received by the expense reception unit 121 and a learning device to perform prediction processing using a machine learning algorithm and obtain an image inspection result indicating whether or not the amount written on the receipt image has been falsified by handwriting.
(15-3) Inspection of inappropriate tax classifications, etc.

The image inspection means 1311 extracts two or more character strings from the receipt image. Next, the image inspection means 1311 determines whether the two or more character strings match a predetermined fraudulent pattern. If they match a fraudulent pattern, the image inspection means 1311 obtains an inspection result indicating that the information is fraudulent.

An example of a fraudulent pattern is when the string corresponding to the class "Summary" contains the string "Souvenir" and the string corresponding to the class "Tax Classification" contains "10%". Such a fraudulent pattern constitutes a tax classification error. For example, if the image inspection means 1311 determines, using the acquired string, that the string corresponding to the class "Summary" contains "Souvenir" and the string corresponding to the class "Tax Classification" contains "10%", it obtains an image inspection result indicating "Tax classification error".
(15-4) Inspection of address deficiencies

The image inspection means 1311 obtains one or more strings from the receipt image, associating them with a class.

Next, if the image inspection means 1311 determines that the string corresponding to the class "Recipient Name" does not match the company name stored in the storage unit 11, it obtains an image inspection result indicating that the recipient name on the receipt is incorrect. Also, for example, if the image inspection means 1311 uses the obtained string to determine that the string corresponding to the class "Recipient Name" is an inappropriate string such as "To Whom It May Concern" stored in the storage unit 11, it obtains an image inspection result indicating that the recipient name on the receipt is incorrect.
(15-5) Checking whether the receipt is signed.

The image inspection means 1311 constructs a learning model using a machine learning algorithm, for example, by using training data in which one or more receipts with signatures are used as positive examples and one or more receipts without signatures are used as negative examples. The image inspection means 1311 then performs prediction processing using the received receipt image and the learning model to obtain information indicating whether or not there is a signature. If the image inspection means 1311 determines that there is no signature, it obtains an image inspection result indicating the defect of the receipt lacking a signature.
(15-6) Inspection of the blurriness of receipt images (a) When using character recognition processing (first blurriness processing)

The image inspection means 1311 uses character recognition technology to obtain a character recognition score along with one or more character strings from the receipt image received by the expense reception unit 121. If the score is low enough to meet predetermined conditions, it performs a first blurring process to determine that the receipt image is blurry. It should be noted that the technology for performing character recognition, obtaining character strings, and outputting a character recognition score (which can also be called likelihood) is publicly known technology.
(b) When using machine learning processing (second blurring process)

The image inspection means 1311 uses a machine learning algorithm to train one or more blurry receipt images and one or more clear receipt images, thereby constructing a learning model. This learning model takes a receipt image as input and obtains a judgment result on whether the receipt image is blurry or clear.

Next, the image inspection means 1311 uses the receipt image received by the expense reception unit 121 and a learning device to perform prediction processing using a machine learning algorithm and obtain an inspection result indicating whether the receipt image is unclear or clear.
(15-7) Inspection of payment methods

The image inspection means 1311 obtains payment method information (for example, "○○ PAY"), which is a string of characters, from the receipt image, and checks whether the payment method information is the same as the payment method information contained in the company regulations information, and obtains the image inspection result. The company regulations information is stored in the company regulations information storage unit 113.
(15-8) Checking for the presence or absence of a company seal on handwritten receipts (a) When using machine learning processing

The image inspection means 1311 uses, for example, one or more handwritten receipt images with a company seal as positive examples, and one or more receipt images without a company seal as negative examples. It performs a learning process using a machine learning algorithm to construct a learning model. This learning model takes receipt images as input and outputs whether or not a company seal is present.

Next, the image inspection means 1311 uses the received receipt image and a learning device to perform prediction processing using a machine learning algorithm and obtain an image inspection result indicating whether or not a company seal has been affixed.
(b) When using image recognition processing

The image inspection means 1311 performs character recognition processing on the received receipt image to determine whether or not handwritten characters are present (for example, whether or not the score is below or equal to a threshold). If it is determined that handwritten characters are present, the image inspection means 1311 determines, for example, by image recognition, whether or not there is a square seal whose pixel value is in the red area and which has a roughly rectangular outline. If it is determined that there is no square seal, the image inspection means 1311 obtains an image inspection result indicating that no square seal has been stamped.
(15-9) Checking the timestamp

The image inspection means 1311 acquires the date information indicated by the timestamp on the received receipt image. This date information indicates the date on which the timestamp was added to the receipt image.

Next, the image inspection means 1311 obtains the receipt issuance date corresponding to the received receipt image.

Next, the image inspection means 1311 determines whether the date indicated by the acquired date information has elapsed for a predetermined period of time relative to the receipt issuance date, and obtains the image inspection result. The predetermined period of time is, for example, "three days or more" or "four days or more."

The image inspection means 1311 typically obtains the receipt issuance date from the receipt image, but it may also obtain the receipt issuance date as a string included in the expense information received by the expense reception unit 121. Furthermore, techniques for adding a timestamp to a receipt image and techniques for obtaining a timestamp from a receipt image are publicly known technologies.

The storage unit 11, expense information storage unit 111, applicant group storage unit 112, company regulations information storage unit 113, restaurant group storage unit 114, adult entertainment establishment group storage unit 115, counterparty group storage unit 116, card usage expense storage unit 117, means of transportation information storage unit 118, personal information storage unit 1121, attendance information storage unit 1122, entry/exit information storage unit 1123, sales activity information storage unit 1124, card statement information storage unit 1125, company vehicle location information storage unit 1126, calculation information storage unit 1181, map information storage unit 1182, and the first storage unit 21 are preferably made of non-volatile recording media, but can also be made of volatile recording media.

The process by which information is stored in the storage unit 11, etc., is not specified. For example, information may be stored in the storage unit 11, etc., via a recording medium, information transmitted via a communication line, etc., may be stored in the storage unit 11, etc., or information input via an input device may be stored in the storage unit 11, etc.

The reception unit 12, the expense reception unit 121, and the first receiving unit 25 are typically implemented using wireless or wired communication means, but they may also be implemented using means for receiving broadcasts.

The processing unit 13, inspection unit 131, statistical processing unit 132, image inspection means 1311, and first processing unit 23 can typically be implemented using a processor, memory, etc. The processing procedure of the processing unit 13 is usually implemented in software, and this software is recorded on a recording medium such as ROM. However, it may also be implemented in hardware (dedicated circuitry). The processor can be of any type, such as an MPU, CPU, or GPU.

The output unit 14, the result output unit 141, and the first transmission unit 24 are typically implemented using wireless or wired communication means, but may also be implemented using broadcasting means.

The first reception unit 22 can be implemented using device drivers for input means such as touch panels and keyboards, or control software for menu screens.

The first output unit 26 may or may not be considered to include output devices such as a display or speakers. The first output unit 26 can be implemented using driver software for an output device, or a driver software for an output device and an output device.
It is equipped with.

Next, an example of the operation of the expense inspection device 1 will be explained using the flowchart in Figure 4.

(Step S401) The expense reception unit 121 determines whether or not it has received expense information associated with the application identifier from the applicant terminal 2. If expense information is received, the process proceeds to step S402; if expense information is not received, the process proceeds to step S406.

(Step S402) The processing unit 13 performs an inspection process on the expense information received in step S401. The inspection process is the process of checking for fraud in expense claims. An example of the inspection process will be explained using the flowchart in Figure 5.

(Step S403) The inspection unit 131 determines whether the inspection result obtained in step S402 is "valid" or not. If it is "valid", proceed to step S404; otherwise, proceed to step S405.

(Step S404) The processing unit 13 or the storage unit (not shown) stores the expense information received in step S401 in the expense information storage unit 111, associating it with the application identifier. The process returns to step S401. In step S404, the result output unit 141 may also send an inspection result indicating "valid" to the applicant terminal 2 that sent the expense information.

(Step S405) The result output unit 141 transmits the inspection results obtained in step S402 to the applicant terminal 2 that sent the expense information. The process returns to step S401. Note that in step S405, the inspection unit 131 may increment the number of fraudulent transactions corresponding to the applicant identifier corresponding to the expense information by 1. Also, in step S405, the processing unit 13 or an storage unit (not shown) may store the expense information received in step S401 in the expense information storage unit 111, associating it with the application form identifier.

(Step S406) The processing unit 13 determines whether or not it is time to perform a statistical test. If it is time to perform a statistical test, the process proceeds to step S407; otherwise, it proceeds to step S414.

The processing unit 13 obtains the time from a clock (not shown) and determines that it is time to perform a statistical check if the time is after a predetermined time. Furthermore, the processing unit 13 determines that it is time to perform a statistical check when it receives an instruction to do so. A statistical check is an inspection for fraud using the statistical processing results of expense information. It is preferable that the statistical check be performed periodically (for example, once a month).

(Step S407) The processing unit 13 assigns 1 to counter i.

(Step S408) The processing unit 13 determines whether the i-th applicant identifier exists in the expense information storage unit 111. If the i-th applicant identifier exists, the process proceeds to step S409; if the i-th applicant identifier does not exist, the process proceeds to step S412. Whether the i-th applicant identifier exists or not determines whether the i-th applicant to be inspected exists or not.

(Step S409) The processing unit 13 performs statistical processing on the expense information corresponding to the i-th applicant identifier and uses the results of the statistical processing to check for fraud in the expense claim. An example of such statistical check processing will be explained using the flowchart in Figure 6.

(Step S410) The processing unit 13 outputs the inspection result obtained in step S409, associating it with the i-th applicant identifier. The processing unit 13 stores the inspection result in the storage unit 11, associating it with the i-th applicant identifier. The processing unit 13 also transmits the inspection result associated with the i-th applicant identifier to a terminal (not shown).

(Step S411) The processing unit 13 increments counter i by 1. The process returns to step S408.

(Step S412) The statistical processing unit 132 constructs the statistical processing results to be output.

(Step S413) The result output unit 141 outputs the statistical processing results configured in step S412. The process returns to step S401. Note that outputting the statistical processing results includes, for example, storing the results in the storage unit 11 or transmitting the results to a terminal (not shown).

(Step S414) The processing unit 13 determines whether or not it is time to perform an inspection for undeclared income. If it is time to perform an inspection for undeclared income, the process proceeds to step S415; otherwise, it returns to step S401.

The processing unit 13 obtains the time from a clock (not shown) and determines that it is time to perform an underreporting check if the time is after a predetermined time. Furthermore, the processing unit 13 determines that it is time to perform an underreporting check when it receives an instruction for one. An underreporting check is an inspection for omissions in expense claims. It is preferable that underreporting checks be performed periodically (for example, once a month).

(Step S415) The processing unit 13 performs an omission check for expense claims. An example of the omission check process will be explained using the flowchart in Figure 7.

(Step S416) The result output unit 141 outputs the leak test results obtained in step S415. The process returns to step S401. Outputting the test results here includes, for example, storage of the test results in the storage unit 11, transmission to the applicant identified by the applicant identifier corresponding to the leak, and transmission to a terminal (not shown).

In the flowchart shown in Figure 4, processing terminates upon power off or processing completion interruption.

Next, an example of the inspection process in step S402 will be explained using the flowchart in Figure 5.

(Step S501) The inspection unit 131 determines whether the received expense information includes a receipt image. If a receipt image is included, the process proceeds to step S502; otherwise, the process proceeds to step S505.

(Step S502) The image inspection means 1311 obtains one or more pairs of strings and classes from the receipt image. Since this process has been described above, a detailed explanation is omitted here.

(Step S503) The image inspection means 1311 performs an image inspection of the receipt and obtains the inspection result.

The receipt image inspection is, for example, one or more of the inspections described in (15-1) to (15-9) above.

(Step S504) The inspection unit 131 performs a common inspection and obtains the inspection results. A common inspection is an inspection that does not depend on the expense type identifier (which may also be an account name) in the expense information.

Common inspections include, for example, (1-1) and (2-1) inspections of expenses incurred on non-working days, (4-1) inspections of split receipts, (5-1) inspections of fraudulent use of company vehicles, (6) inspections using card expense information, (10) inspections using counterparty information, (11-1) inspections of duplicate applications, (11-2) inspections of reuse of receipts, (11-3) inspections of a large number of expense applications on the same day, and (13) detection of fraud by expense application approvers.

(Step S505) The inspection unit 131 obtains the expense type identifier from the received expense information.

(Step S506) The inspection unit 131 determines whether the expense type identifier obtained in step S505 is "transportation expenses (travel expenses may also be used)". If it is "transportation expenses", proceed to step S507; otherwise, proceed to step S508.

(Step S507) The inspection unit 131 performs the entertainment expense inspection process and obtains the inspection results. Proceed to step S514.

The transportation expense inspection process is a process specifically for inspecting transportation expenses. Examples of transportation expense inspections include (3-1) inspection of fraudulent transportation expenses (i), (3-2) inspection of fraudulent transportation expenses (ii), (4-2) inspection of taxi use after company drinking parties, (8-1) inspection of fraudulent train, bus, or airplane transportation expenses, (8-2) inspection of fraudulent taxi fares, and (8-3) inspection of overlap with regular commuter routes.

(Step S508) The inspection unit 131 determines whether the expense type identifier obtained in step S505 is "entertainment expenses (or hospitality expenses)". If it is "entertainment expenses", proceed to step S509; otherwise, proceed to step S510.

(Step S509) The inspection unit 131 performs the entertainment expense inspection process and obtains the inspection results. Proceed to step S514.

Entertainment expense inspection procedures are specific to the inspection of entertainment expenses. Examples of entertainment expense inspection procedures include: (9-1) inspection of fraudulent use of establishments (such as adult entertainment venues), (9-2) inspection of fraudulent amounts, (9-3) inspection of whether entertainment expenses are incurred at restaurants, (10) inspection using information on business partners, and (11-4) inspection of fraudulent use of after-party expenses.

(Step S510) The inspection unit 131 determines whether the expense type identifier obtained in step S505 is "accommodation expenses". If it is "accommodation expenses", proceed to step S511; otherwise, proceed to step S512.

(Step S511) The inspection unit 131 performs the accommodation expense inspection process and obtains the inspection results. Proceed to Step S514.

Accommodation expense inspection procedures are processes specifically for inspecting accommodation expenses. Examples of accommodation expense inspection procedures include (1-3) inspections for fraudulent accommodation expenses and (2-3) inspections for fraudulent accommodation expenses.

(Step S512) The inspection unit 131 determines whether the expense type identifier obtained in step S505 is "travel expenses". If it is "travel expenses", proceed to step S513; otherwise, proceed to step S512.

(Step S513) The inspection unit 131 performs the travel expense inspection process and obtains the inspection results. Proceed to Step S514.

Business trip expense inspection procedures are processes specifically for inspecting business trip expenses. Examples of business trip expense inspection procedures include (1-2) inspection for fraudulent business trip expenses and (2-2) inspection for fraudulent business trip expenses.

(Step S514) The inspection unit 131 uses the acquired inspection results to construct the output inspection results. It then returns to the higher-level processing unit.

For example, if one or more fraudulent inspection results are obtained, the inspection unit 131 constructs an inspection result that includes all inspection results indicating fraud. Conversely, if no fraudulent inspection results are obtained, the inspection unit 131 constructs an inspection result indicating "legitimate."

Next, an example of the statistical testing process in step S409 will be explained using the flowchart in Figure 6.

(Step S601) The statistical processing unit 132 assigns 1 to counter i.

(Step S602) The statistical processing unit 132 determines whether the i-th store identifier exists among the store identifiers in the expense information storage unit 111, which are one or more expense information items corresponding to the applicant identifier to be inspected (the i-th applicant identifier in step S408). If the i-th store identifier exists, the process proceeds to step S603; if the i-th store identifier does not exist, the process proceeds to step S607.

The i-th store identifier is the i-th store identifier obtained by uniquely processing the store identifiers among one or more expense information entries corresponding to the applicant identifier being inspected. Furthermore, the period for the expense information being inspected may be predetermined or may encompass the entire period.

(Step S603) The statistical processing unit 132 obtains the number of expense entries corresponding to the applicant identifier of the subject of inspection and containing the i-th store identifier. The statistical processing unit 132 uses this number to obtain store frequency information. Note that the store frequency information may be the same value as the number, or it may be the number divided by the period, etc. The store frequency information is usually calculated using an increasing function with the number as a parameter.

(Step S604) The inspection unit 131 determines whether the store frequency information obtained in step S603 is large enough to satisfy the predetermined store frequency conditions. If the store frequency conditions are met, the process proceeds to step S605; otherwise, the process proceeds to step S606.

(Step S605) The inspection unit 131 obtains an inspection result indicating "excessive use of one store" and an inspection result containing the i-th store identifier, associating them with the applicant identifier being inspected. The inspection unit 131 may also increment the number of fraudulent transactions corresponding to the applicant identifier being inspected by 1.

(Step S606) The statistical processing unit 132 increments counter i. The process returns to step S602.

(Step S607) The statistical processing unit 132 assigns 1 to counter i.

(Step S608) The statistical processing unit 132 determines whether an i-th counterparty identifier exists among the store identifiers in one or more expense information entries in the expense information storage unit 111 that correspond to the applicant identifier being inspected. If an i-th counterparty identifier exists, the process proceeds to step S609; if an i-th counterparty identifier does not exist, the process proceeds to step S613.

The i-th counterparty identifier is the i-th counterparty identifier obtained by uniquely processing the counterparty identifiers among one or more expense information entries corresponding to the applicant identifier being inspected. Furthermore, the period for the expense information being inspected may be predetermined or may encompass the entire period.

(Step S609) The statistical processing unit 132 obtains the number of expense entries containing the i-th counterparty identifier, corresponding to the applicant identifier being inspected. The statistical processing unit 132 uses this number to obtain counterparty frequency information. The counterparty frequency information may be the same value as the number, or it may be the number divided by the period, etc. The counterparty frequency information is usually calculated using an increasing function with the number as a parameter.

(Step S610) The inspection unit 131 determines whether the counterparty frequency information obtained in step S603 is large enough to satisfy the predetermined counterparty frequency conditions. If the counterparty frequency conditions are met, the process proceeds to step S611; otherwise, the process proceeds to step S612.

(Step S611) The inspection unit 131 obtains an inspection result indicating that "the number of times entertainment, etc., was provided to one client is excessive," and an inspection result containing the i-th client identifier, associating it with the applicant identifier being inspected. The inspection unit 131 may also increment the number of fraudulent activities corresponding to the applicant identifier being inspected by 1.

(Step S612) The statistical processing unit 132 increments counter i. The process returns to step S608.

(Step S613) The inspection unit 131 obtains the number of fraudulent transactions corresponding to the applicant identifier being inspected from the personal information storage unit 1121.

(Step S614) The inspection unit 131 determines whether the number of fraudulent transactions obtained in step S613 satisfies the fraudulent transaction count condition. If the fraudulent transaction count condition is met, the process proceeds to step S615; otherwise, the process proceeds to step S616.

(Step S615) The inspection unit 131 obtains an inspection result indicating that "the applicant has committed fraud many times," associating it with the applicant identifier being inspected. Note that the inspection result may only include the applicant identifier with a high number of fraudulent activity.

(Step S616) The inspection unit 131 determines whether or not it was able to obtain an inspection result for fraud based on the statistical inspection. If an inspection result was obtained, it returns to the higher-level process; if no inspection result was obtained, it proceeds to step S617.

(Step S617) The inspection unit 131 assigns the value "valid" to the variable "inspection result". It then returns to the higher-level process.

Next, an example of the leak test process in step S415 will be explained using the flowchart in Figure 7.

(Step S701) The inspection unit 131 assigns 1 to counter i. Counter i is the counter for the applicant being inspected.

(Step S702) The inspection unit 131 determines whether the i-th applicant identifier exists in the storage unit 11. If the i-th applicant identifier exists, the process proceeds to step S703; if the i-th applicant identifier does not exist, the process returns to the higher-level processing unit. The i-th applicant identifier is the identifier of the i-th applicant being inspected.

(Step S703) The inspection unit 131 assigns 1 to counter j. Counter j is the counter for the day being inspected.

(Step S704) The inspection unit 131 determines whether or not date information exists for the j-th day of the inspection target. If date information exists for the j-th day, the process proceeds to step S705; otherwise, it proceeds to step S722. It is assumed that the days for leak testing are predetermined, and the information specifying the leak testing days is stored in a buffer (not shown).

(Step S705) The inspection unit 131 determines whether attendance information exists in the attendance information storage unit 1122 that has the same workday information as the day information indicating the j-th day, corresponding to the i-th applicant identifier. If it exists, proceed to step S706; otherwise, proceed to step S709.

(Step S706) The inspection unit 131 retrieves attendance information from the attendance information storage unit 1122 that corresponds to the i-th applicant identifier and has the same workday information as the day information indicating the j-th day. The inspection unit 131 uses the retrieved attendance information to check for omissions in expense claims. This check is, for example, the process described in "(14-1) Detection of Omissions Using Attendance Information."

(Step S707) The inspection unit 131 determines whether or not there was a leak based on the inspection results in step S706. If there is a leak, proceed to step S708; otherwise, proceed to step S709.

(Step S708) The inspection unit 131 obtains inspection results indicating whether a leak was found and the nature of the leak, associating them with the i-th applicant identifier and the j-th date information.

(Step S709) The inspection unit 131 determines whether there is entry/exit information in the entry/exit information storage unit 1123 that corresponds to the i-th applicant identifier and has the same workday information as the j-th day. If it exists, proceed to step S710; otherwise, proceed to step S713.

(Step S710) The inspection unit 131 retrieves entry/exit information from the entry/exit information storage unit 1123 that corresponds to the i-th applicant identifier and has the same workday information as the j-th day. The inspection unit 131 uses the retrieved entry/exit information to check for omissions in expense applications. This check is, for example, the process described in "(14-2) Detection of Omissions Using Entry/Exit Information."

(Step S711) The inspection unit 131 determines whether or not there was a leak based on the inspection results in step S710. If there is a leak, proceed to step S712; otherwise, proceed to step S713.

(Step S712) The inspection unit 131 obtains inspection results indicating whether a leak was found and the nature of the leak, associating them with the i-th applicant identifier and the j-th date information.

(Step S713) The inspection unit 131 determines whether business activity information corresponding to the i-th applicant identifier and having the same business day information as the j-th day exists in the business activity information storage unit 1124. If it exists, proceed to step S714; otherwise, proceed to step S717.

(Step S714) The inspection unit 131 retrieves business activity information from the business activity information storage unit 1124 that corresponds to the i-th applicant identifier and has the same business day information as the j-th day. The inspection unit 131 uses the retrieved business activity information to check for omissions in expense claims. This check is, for example, the process described in "(14-3) Detection of Omissions Using Business Activity Information."

(Step S715) The inspection unit 131 determines whether or not there was a leak based on the inspection results in step S714. If there is a leak, proceed to step S716; otherwise, proceed to step S717.

(Step S716) The inspection unit 131 obtains inspection results indicating whether a leak was found and the nature of the leak, associating them with the i-th applicant identifier and the j-th date information.

(Step S717) The inspection unit 131 determines whether there is a vehicle location information in the vehicle location information storage unit 1126 that corresponds to the i-th applicant identifier and has the same business day information as the j-th day. If it exists, proceed to step S718; otherwise, proceed to step S721.

(Step S718) The inspection unit 131 obtains one or more business vehicle location information from the business vehicle location information storage unit 1126 that corresponds to the i-th applicant identifier and has the same business day information as the day information indicating the j-th day. The inspection unit 131 uses the obtained one or more business vehicle location information to check for omissions in expense claims. Such an inspection is, for example, the process described in "(14-4) Detection of Omissions Using Business Vehicle Location Information."

(Step S719) The inspection unit 131 determines whether or not there was a leak based on the inspection results in step S718. If there is a leak, proceed to step S720; otherwise, proceed to step S721.

(Step S720) The inspection unit 131 obtains inspection results indicating whether a leak was found and the nature of the leak, associating them with the i-th applicant identifier and the j-th date information.

(Step S721) The inspection unit 131 increments counter j by 1. Return to step S704.

(Step S722) The inspection unit 131 generates an inspection result corresponding to the i-th applicant identifier. The inspection unit 131 temporarily stores the inspection result, for example, associated with the i-th applicant identifier. The inspection result may contain, for example, the results of one or more leak inspections. If no leaks are found, the inspection result indicates "no leaks."

(Step S723) The inspection unit 131 increments counter i by 1. Return to step S702.

Next, an example of the operation of the applicant terminal 2 will be described. The first reception unit 22 of the applicant terminal 2 receives expense information input from the user. Next, the first processing unit 23 reads the applicant identifier stored in the first storage unit 21. Then, the first processing unit 23 constructs transmission information containing the received expense information and the read applicant identifier. Next, the first transmission unit 24 transmits the transmission information containing the expense information and the applicant identifier to the expense inspection device 1.

Next, the first receiving unit 25 receives the inspection results from the cost inspection device 1. The first processing unit 23 is configured to output the received inspection results. The first output unit 26 outputs the inspection results.
(Specific examples of statistical processing results)

The following describes an example of statistical processing results acquired by the statistical processing unit 132 of the expense inspection device 1 in this embodiment and output by the result output unit 141.

(Specific example 1)
The statistical processing unit 132 processes the expense information stored in the expense information storage unit 111 for each applicant over a certain period (for example, one month in December 2019), and obtains store frequency information for each applicant identifier and each store identifier. The statistical processing unit 132 also obtains the number of expense entries for each applicant identifier.

The statistical processing unit 132 then obtained statistical processing results, plotting the store frequency information for each applicant identifier and each store identifier on a graph with the store frequency information on the vertical axis and the number of expense information items for each applicant identifier on the horizontal axis.

Furthermore, the statistical processing unit 132 determines that the risk is high if the store frequency condition "Store frequency information >= 3" in the storage unit 11 is met. A high risk can be said to mean fraud. The statistical processing unit 132 then obtains the applicant identifier of the applicant determined to be high risk, the store identifier of the store used, and the store frequency information.

The statistical processing unit 132 then generates the statistical processing results that are output as a result of the above processing.

Next, the result output unit 141 outputs the statistical processing results (801, 802). An example of such output is shown in Figure 8.

In Figure 8, 801 represents the statistical processing results plotted on the graph of store frequency information. The vertical axis of 801 represents the maximum number of cases per person and per store (store frequency information). The horizontal axis of 801 represents the number of applications per person.

Furthermore, 802 is a table consisting of records containing the applicant identifier (applicant), store name, and store frequency information (number of records) corresponding to store frequency information deemed to be high risk.

(Specific example 2)
Specific example 2 is an example of obtaining information when there is a time stamp despite the employee being on a business trip.

The statistical processing unit 132 determines, for example, that if attendance information indicates a business trip for each applicant identifier, or if expense information for business trip expenses or transportation expenses is submitted, the date corresponding to the workday information in the attendance information or the usage date information in the expense information is the day the business trip took place.

Next, the statistical processing unit 132 obtains the frequency (for example, the number of times in a given month) of entries and exits that include the same workday information as the workday information or expense information, and where the start and end times of work are recorded. This information represents the frequency of clock-ins during business trips.

Furthermore, the statistical processing unit 132 obtains, for example, the average difference between the working hours shown in each attendance record for a month and the working hours shown in the entry/exit information, which includes the same working day information as the attendance record, for each applicant identifier. This information represents the discrepancy between the attendance record and the time stamp.

The statistical processing unit 132 then constructs a statistical processing result graph in which, for each applicant identifier, the frequency of time stamps during business trips is plotted on the horizontal axis, and the discrepancy between attendance information and time stamps is plotted on the vertical axis, with the applicant identifiers plotted as dots.

Next, the result output unit 141 outputs the statistical processing results. An example of such output is shown in Figure 9. In Figure 9, the applicants corresponding to the dots in area 901 are those who are highly likely to have committed fraud.

In summary, according to this embodiment, by using external information or expense information other than the submitted expense information, appropriate inspections can be performed against inappropriate expense claims.

Furthermore, according to this embodiment, by using applicant information, appropriate inspections can be conducted to identify inappropriate expense claims.

Furthermore, according to this embodiment, by using the applicant's attendance information, appropriate inspections can be conducted to identify inappropriate expense claims.

Furthermore, according to this embodiment, by using the applicant's entry and exit information, appropriate inspections can be conducted to identify inappropriate expense claims.

Furthermore, according to this embodiment, by using the applicant's business activity information, appropriate inspections can be conducted against inappropriate expense claims.

Furthermore, according to this embodiment, by using the applicant's credit card statement information, appropriate inspections can be conducted to identify inappropriate expense claims.

Furthermore, according to this embodiment, by using the applicant's company vehicle location information, appropriate inspections can be conducted to identify inappropriate expense claims.

Furthermore, according to this embodiment, by using the information on the applicant's card, appropriate inspections can be conducted to identify inappropriate expense claims.

Furthermore, according to this embodiment, by using company regulations information, appropriate inspections can be conducted against inappropriate expense claims.

Furthermore, according to this embodiment, by using information on means of transportation, appropriate inspections can be performed against inappropriate expense claims.

Furthermore, according to this embodiment, by using a store aggregation system, appropriate inspections can be conducted against inappropriate expense claims.

Furthermore, according to this embodiment, inappropriate spending to inappropriate parties can be appropriately detected.

Furthermore, this embodiment allows for the proper detection of inappropriate business trip expenses, inappropriate transportation expenses, duplicate applications, reuse of receipts, fraudulent accommodation expenses, fraudulent after-party expenses, etc.

Furthermore, according to this embodiment, by using statistical processing results based on two or more expense information sources, appropriate inspections regarding inappropriate expense claims can be performed.

Furthermore, according to this embodiment, it is possible to detect that a particular store is frequently used.

Furthermore, according to this embodiment, it is possible to detect that expenditures corresponding to a specific customer are frequent.

Furthermore, this embodiment makes it possible to detect when a particular individual is committing a significant amount of fraud.

Furthermore, according to this embodiment, it is possible to detect if the approver of an expense claim does not meet the requirements.

Furthermore, according to this embodiment, it is possible to detect instances where expense claims have been missed.

Furthermore, according to this embodiment, proper inspection of receipt images can be performed.

Furthermore, according to this embodiment, the information contained in the receipt image can be properly inspected.

Furthermore, according to this embodiment, it is possible to check for defects in the timestamp of the receipt image.

Furthermore, according to this embodiment, it is possible to inspect unclear receipt images.

Furthermore, according to this embodiment, it is possible to inspect for inappropriate payment methods.

Furthermore, according to this embodiment, it is possible to inspect for falsification of amounts by handwriting.

Furthermore, in this embodiment, the expense inspection device 1 preferably functions as a device that receives expense information from one or more external expense management devices 4, inspects the expense information, and transmits the inspection results to the expense management devices. In this case, the expense inspection device 1 has, for example, the structure shown in Figure 10. That is, in this case, the applicant collection storage unit 112, company regulations information storage unit 113, card usage expense storage unit 117, personal information storage unit 1121, attendance information storage unit 1122, entry/exit information storage unit 1123, sales activity information storage unit 1124, card statement information storage unit 1125, and sales vehicle location information storage unit 1126 of the expense inspection device 1 exist, for example, for each organizational identifier. In other words, the applicant collection, company regulations information, card usage expense information, personal information, attendance information, entry/exit information, sales activity information, card statement information, and sales vehicle location information are associated with the organizational identifier.

Furthermore, the expense information received by the expense inspection device 1 from the expense management device 4 is associated with an organization identifier. When the expense inspection device 1 receives expense information from the expense management device 4, the inspection unit 131 performs an inspection using the applicant set, etc., associated with the organization identifier corresponding to the expense information, and obtains the inspection result. The result output unit 141 then transmits the inspection result to the expense management device 4. Note that the organization identifier is information that identifies an organization, such as a company name or company ID. An organization, for example, can be a company, group, or department.

Furthermore, the expense management device 4, upon receiving expense information from the applicant terminal 2, transmits the expense information to the expense inspection device 1 for verification. The expense management device 4 then receives the inspection results from the expense inspection device 1 in response to the transmission of the expense information. The expense management device 4 stores the expense information only if the inspection results are valid. If the inspection results are invalid, the expense management device 4 transmits the inspection results to the applicant terminal 2.

With the system configuration described above, comprising the expense inspection device 1 and one or more expense management devices 4, the expense inspection device 1 can function as an expense information inspection server. Furthermore, the expense management device 4, in addition to its conventional expense information management functions, can acquire expense inspection functions by using the expense inspection device 1.

Furthermore, the expense inspection device 1 can receive two or more expense information items from one or more expense management devices 4, and by including an expense information storage unit 111 for each organization, it can also perform the statistical processing described above.

Furthermore, the processing in this embodiment may be implemented using software. This software may be distributed via software download or similar means. Alternatively, this software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments described herein. The software implementing the expense inspection device in this embodiment is as follows: This program causes the computer to function as an expense reception unit that receives expense information identifying the content of expense applications; an inspection unit that uses external information other than the expense information, or expense information other than the expense information received by the expense reception unit, to perform an inspection for fraudulent activity in the expense information received by the expense reception unit and obtain the inspection results; and a result output unit that outputs the inspection results obtained by the inspection unit.

(Embodiment 2)
In this embodiment, an information system is described that includes an information processing device that acquires and outputs travel route information relating to an employee's travel route using the employee's scheduled or actual travel route information. Note that the employee is, for example, the applicant in Embodiment 1.

Furthermore, this embodiment describes an information system that includes an information processing device that uses employee schedule information and actual performance information to check whether work is being performed as scheduled, obtains the check results, and processes the results.

Furthermore, in this embodiment, we will describe an information system that includes an information processing device for notifying employees if the inspection result is deemed invalid.

Furthermore, this embodiment describes an information system that includes an information processing device that determines whether travel expense information, which is the cost associated with employee travel, falls under either commuting expenses or transportation expenses, and outputs the travel expense information associated with that account.

Furthermore, in this embodiment, we will describe an information system equipped with different information processing devices for storing travel expense information depending on whether the expense category is commuting expenses or transportation expenses.

Furthermore, this embodiment describes an information system equipped with an information processing device that acquires commuting expenses using information on commuter passes and means of transportation such as private cars.

Furthermore, this embodiment describes an information system comprising an information processing device that performs processing for storing information on commuting expenses that are not "0" in a commuting expense database. Note that processing for storing information on commuting expenses of "0" may also be performed.

Furthermore, in this embodiment, we will describe an information system equipped with an information processing device that acquires travel route information using information on means of transportation such as a private car.

Furthermore, this embodiment describes an information system that includes an information processing device that notifies an appropriate recipient (e.g., a supervisor) when the scheduled information or actual information differs from the default scheduled information or actual information.

Furthermore, this embodiment describes an information system that includes an information processing device for notifying employees when actual performance information does not match scheduled information and appropriate actual performance information cannot be obtained even after the scheduled time has elapsed.

Furthermore, this embodiment describes an information system that includes an information processing device for re-examining received performance information after it has been determined that the performance information does not match the planned information.

Figure 11 is a conceptual diagram of information system B in this embodiment. Information system B comprises an information processing device 5, one or more terminal devices 6, one or more entry/exit information acquisition devices 7, an accounting information management device 8, and a personnel information management device 9.

The information processing device 5 is a server that implements the functions of this invention. It receives and processes information from terminal devices 6, access control devices 7, etc. The information processing device 5 may be, for example, a cloud server or an ASP server, but its type is not limited.

Terminal device 6 is a terminal used by employees. Employees are those whose work is managed by the organization, and may include not only full-time employees but also part-time and other non-regular employees. Terminal device 6 may be, for example, a personal computer, tablet, smartphone, etc., and the type is not limited.

The entry/exit information acquisition device 7 is a device that acquires entry and exit information. The entry/exit information acquisition device 7 exists, for example, corresponding to one or more work locations where an employee works. However, one entry/exit information acquisition device 7 may cover two or more work locations. The entry/exit information acquisition device 7 may include, for example, a card reader 71 that acquires information from a card held by an employee. The entry/exit information acquisition device 7 only needs to acquire entry/exit information, which is information about an employee's entry into or exit from their work location. For example, the entry/exit information acquisition device 7 associates the acquired entry/exit information with an employee identifier and transmits it to the information processing device 5. Since the entry/exit information acquisition device 7 can be implemented using publicly known technology, a detailed explanation is omitted.

The accounting information management device 8 is a device that manages expense information, including transportation expense information, and inspects expense information. The accounting information management device 8 may have some or all of the functions of the expense inspection device 1 in Embodiment 1. The accounting information management device 8 is typically a so-called server, such as a cloud server or ASP server. The type of accounting information management device 8 is not limited.

The personnel information management device 9 is a device that manages personnel information, including commuting expense information, and also inspects personnel information. The personnel information management device 9 is typically a server, such as a cloud server or ASP server. The type of personnel information management device 9 is not specified.

The information processing device 5 can communicate with the terminal device 6, the entry/exit information acquisition device 7, the accounting information management device 8, and the personnel information management device 9, typically via a network such as the internet or a dedicated line.

Figure 12 is a block diagram of information system B in this embodiment. Figure 13 is a block diagram of the information processing device 5 that constitutes information system B.

The information processing device 5 comprises a storage unit 51, a receiving unit 52, a processing unit 53, an output unit 54, and a transmission unit 55.

The storage unit 51 includes a home location storage unit 511, a work location information storage unit 512, a regular information storage unit 513, a mobile information storage unit 514, a commute route storage unit 515, a default storage unit 516, and a work information storage unit 517. Note that the storage unit 51 and each of its storage units may reside in an external device other than the information processing device 5. Furthermore, the storage unit 51 may also include a transportation expense database 81 and a commute expense database 91, as described later.

The work information storage unit 517 includes a scheduled information storage unit 5171 and a performance information storage unit 5172.

The receiving unit 52 includes a scheduled receiving unit 521 and a real-time receiving unit 522.

The processing unit 53 includes a change determination unit 530, a schedule storage unit 531, a performance storage unit 532, an inspection unit 533, a notification unit 534, a travel route acquisition unit 535, a travel expense acquisition unit 536, an account determination unit 537, a re-inspection unit 538, and a re-processing unit 539.

The output unit 54 includes a travel route output unit 541 and a travel expense output unit 542.

The transmitting unit 55 includes a modified transmitting unit 551.

The terminal device 6 comprises a terminal storage unit 61, a terminal receiving unit 62, a terminal processing unit 63, a terminal transmission unit 64, a terminal receiving unit 65, and a terminal output unit 66.

The entry/exit information acquisition device 7 includes, for example, a card reader 71. The accounting information management device 8 includes a transportation expense database 81. The personnel information management device 9 includes a commuting expense database 91.

The storage unit 51, which constitutes the information processing device 5, stores various types of information. These types of information include, for example, home location information, work location information, regular schedule information, mobile information, commute route information, default information, work information, scheduled information, and actual performance information, as described later.

The home location storage unit 511 stores one or more home location information entries. The home location information is associated with an employee identifier. Home location information is information that identifies the employee's home address or the nearest transportation point to their home. For example, home location information includes address information, location information (latitude, longitude), nearest train station, and nearest bus stop. The employee identifier is information that identifies the employee, such as the employee's ID and name. The nearest transportation point is, for example, the nearest train station or nearest bus stop.

The work location information storage unit 512 stores one or more work location information entries. Each work location information entry includes a work location identifier and location identification information. The work location identifier is information that identifies the work location, such as the work location name, store name, or work location ID. The location identification information is information that identifies the specific location of the work location, such as the work location's location information (latitude, longitude), address, work location name, work location identifier, or store name.

The periodic information storage unit 513 stores one or more periodic information entries. Each periodic information entry is associated with an employee identifier. The periodic information identifies whether or not a commuter pass is held. In other words, it indicates whether or not an application for a commuter pass has been submitted and whether or not the commuter pass fare is being reimbursed. The periodic information may indicate that a commuter pass is held, or it may indicate that a commuter pass is not held.

The mobile vehicle information storage unit 514 stores one or more mobile vehicle information entries. Mobile vehicle information refers to information that identifies the use of a mobile vehicle (e.g., a personal car) for commuting. The mobile vehicle information is stored in association with an employee identifier. A mobile vehicle can be, for example, a car, motorcycle, or bicycle. While the mobile vehicle information usually indicates the use of a mobile vehicle, it may also indicate that a mobile vehicle is not used. Furthermore, using a mobile vehicle for commuting usually refers to using the employee's own mobile vehicle for commuting, regardless of who owns the vehicle.

The commute route storage unit 515 stores one or more pieces of commute route information. Commuter route information is information that identifies the commute route. Commuter route information is associated with an employee identifier. For example, commute route information may include the name of the nearest station from home and the names of one or more transfer stations. Alternatively, it may include the name of the nearest station from home, one or more transfer stations, and the name of the nearest station to the workplace. For example, commute route information may be "Home → Station A → Station B → Station C → Workplace" or "Station A → Station B → Station C". For employees who use transportation for commuting, the commute route information paired with the employee identifier may include, for example, location identification information for home and location identification information for workplace.

The default storage unit 516 stores one or more default schedule information or one or more default actual information. The default schedule information or actual information is associated with an employee identifier. The default schedule information and actual information may also be included in the commute route information. For example, the default schedule information and actual information are location identification information for the employee's workplace. The default schedule information typically contains location identification information for the employee's workplace. The default actual information typically contains location identification information for the employee's workplace.

The work information storage unit 517 stores one or more types of information from the one or more scheduled information and one or more actual information described later. It is preferable that the work information storage unit 517 stores one or more scheduled information and one or more actual information.

The schedule information storage unit 5171 stores one or more schedule information entries. The schedule information is information related to an employee's work schedule. The schedule information includes location identification information that identifies the work location. The schedule information is associated with an employee identifier. The schedule information includes date information that identifies the day. The schedule information may also be associated with the date information. Note that for one piece of information to be associated with another piece of information, it is sufficient that the other information can be retrieved from the first piece of information; the first piece of information may contain the other information; the other information may contain the first piece of information; the first piece of information and the other information may be linked; the first piece of information and the other information may be stored in the same buffer, etc.

The schedule information stored in the schedule information storage unit 5171 may be, for example, default schedule information with date information added, or it may be information automatically generated by the processing unit 53. The schedule information stored in the schedule information storage unit 5171 may also be information received from the employee's terminal device 6.

Schedule information, for example, is shift schedule information that identifies work shifts. Shift schedule information has, for example, one or more records containing daily information and a work location identifier that identifies the work location. Shift schedule information also has, for example, one or more records containing daily information, a first work location identifier that identifies the first work location at the start of work, and a second work location identifier that identifies the second work location at the end of work. In other words, an employee may work at two or more locations in a single day. In such cases, the employee will be moving between different work locations.

The performance information storage unit 5172 stores one or more performance information entries. The performance information is information regarding an employee's work performance. The performance information includes location identification information. The performance information is associated with an employee identifier. The performance information includes date information that identifies the day. The performance information may also be associated with the date information.

The performance information stored in the performance information storage unit 5172 may be, for example, default performance information with daily information added, or information automatically generated by the processing unit 53. The performance information stored in the performance information storage unit 5172 may also be information received from the employee's terminal device 6.

Performance information includes, for example, one or more of the following: entry/exit information, sales activity information, input information, and employee location information. Entry/exit information refers to information regarding an employee's entry into and exit from their workplace. Entry/exit information is associated with an employee identifier. Entry/exit information includes, for example, day information to identify the workday and work time information. Work time information includes, for example, the start time and end time of work. Sales activity information refers to information regarding sales activities. Sales activity information includes, for example, information from a sales report. Sales activity information includes day information to identify the workday and one or more location-specific pieces of information. Sales activity information may also include strings of characters indicating the content of the sales activity. Here, location-specific information is information that identifies the visited location. Location identifiers include, for example, (latitude, longitude), company name, location name, place name, station name, bus stop name, etc. The data structure of sales activity information is not specified. Input information is information entered by employees for the purpose of performing their work. Input information is associated with day information and time information. Time information refers to information about the time the input information was entered. Employee location information refers to information including one or more location data points received from a mobile device (in this case, terminal device 6) held by the employee.

The receiving unit 52 receives various types of information. These include, for example, scheduled information, actual information, information regarding changes to default scheduled information, and information regarding changes to default actual information. Other types of information include, for example, home location information, work location information, regular information, mobile information, commute route information, and default information.

The schedule receiving unit 521 receives schedule information. The schedule receiving unit 521 receives schedule information associated with an employee identifier. For example, the schedule receiving unit 521 receives schedule information from the terminal device 6. For example, the schedule receiving unit 521 receives schedule information modified by the employee from the terminal device 6. Note that modified schedule information is different from the default schedule information.

The performance receiving unit 522 receives performance information. The performance receiving unit 522 receives performance information associated with an employee identifier. For example, the performance receiving unit 522 receives performance information from the terminal device 6. For example, the performance receiving unit 522 receives performance information modified by an employee from the terminal device 6. Note that modified performance information is scheduled information different from the default performance information. For example, the performance receiving unit 522 receives performance information associated with an employee identifier from the entry/exit information acquisition device 7. Such performance information includes entry/exit information. Such performance information includes location identification information. The performance receiving unit 522 receives sales activity information, input information, or employee location information including one or more location pieces from the terminal device 6.

The inspection results from the inspection unit 533 (described later) indicate a mismatch. The notification unit 534 (described later) receives performance information from the employee's terminal device 6, which notified the employee of the inspection results. This performance information is the performance information that the employee considers to be correct.

The processing unit 53 performs various processes. These various processes include, for example, those performed by the change determination unit 530, the schedule storage unit 531, the actual storage unit 532, the inspection unit 533, the notification unit 534, the travel route acquisition unit 535, the travel expense acquisition unit 536, the account determination unit 537, the re-inspection unit 538, and the reprocessing unit 539.

The processing unit 53 performs different processing depending on the inspection results from the inspection unit 533, which will be described later. For example, if the inspection result from the inspection unit 533 indicates that "the planned information and the actual information do not match," the processing unit 53 notifies the terminal device 6 corresponding to the employee identifier paired with the planned information or the actual information of the inspection result. On the other hand, if the inspection result from the inspection unit 533 indicates that "the planned information and the actual information match," the processing unit 53 does not send such notification.

For example, if the inspection result from the inspection unit 533 indicates that "the planned information and the actual information match," the processing unit 53 stores information related to that inspection result, associating it with the employee identifier paired with the planned information or the actual information. On the other hand, if the inspection result from the inspection unit 533 indicates that "the planned information and the actual information do not match," the processing unit 53 does not perform this storage process.

The processing unit 53 stores various types of information received by the receiving unit 52 in the corresponding storage unit. These types of information include, for example, home location information, work location information, regular information, mobile information, commute route information, default information, work information, schedule information, and actual performance information.

The change determination unit 530 retrieves the default schedule information or default performance information corresponding to one or more employee identifiers from the default storage unit 516, which stores default schedule information or default performance information associated with each employee identifier. It then compares this default schedule information or default performance information with the schedule information or performance information in the work information storage unit 517 to determine whether they are different. The timing of this determination is not relevant.

Furthermore, the scheduled or actual work information stored in the work information storage unit 517 refers to the received scheduled or actual work information, and may also include information that will be stored in the work information storage unit 517 in the future.

The change determination unit 530 may also determine, in association with the employee identifier, whether or not it has received information from the terminal device 6 regarding a modification from the default schedule information.

The change determination unit 530 may also determine, in association with the employee identifier, whether or not it has received information from the terminal device 6 regarding modifications from the default performance information.

The schedule storage unit 531 stores schedule information associated with employee identifiers. The schedule storage unit 531 stores the schedule information received by the schedule receiving unit 521, associated with employee identifiers, in the schedule information storage unit 5171, also associated with those employee identifiers.

The schedule storage unit 531 contains information regarding modifications from the default schedule information. Using the received information, the modified schedule information may be acquired and stored in the schedule information storage unit 5171.

The performance data storage unit 532 stores performance information associated with the employee's employee identifier. The performance data storage unit 532 stores the performance information received by the performance data receiving unit 522, associated with the employee identifier, in the performance data storage unit 5172, also associated with the employee identifier.

The performance data storage unit 532 contains information regarding corrections to the default performance data. Using the received information, the corrected performance data may be acquired, and the planned information may be stored in the performance data storage unit 5172.

The inspection unit 533 uses the scheduled and actual information corresponding to the same day information to check whether the scheduled and actual information match. For each employee identifier, the inspection unit 533 uses the scheduled and actual information corresponding to the same day information to check whether the scheduled and actual information match.

The inspection unit 533 performs, for example, the inspections shown in (1) to (5) below.
(1) Checking the consistency between scheduled information such as shift schedules and store entry/exit information.

The inspection unit 533 retrieves one or more location identification pieces from the scheduled information storage unit 5171, which are included in the scheduled information that corresponds to the employee identifier of interest and the day information of the day to be processed. The inspection unit 533 also retrieves one or more location identification pieces from the actual information storage unit 5172, which are included in one or more store entry/exit information that corresponds to the employee identifier of interest and the day information of the day to be processed. Next, the inspection unit 533 determines whether the one or more locations identified by the one or more location identification pieces included in the scheduled information match the one or more locations identified by the one or more location identification pieces included in the one or more store entry/exit information. If they match, it is determined that the scheduled information and actual information match; if even one does not match, it is determined that the scheduled information and actual information do not match.

If an employee has two or more work locations on a given day, the inspection unit 533 retrieves the locations specified by the two or more location identification pieces included in the scheduled information, in order of work time, and also retrieves the locations specified by the two or more location identification pieces included in the two or more store entry/exit information, in order of work time. Then, it determines whether the two or more locations corresponding to the scheduled information match the two or more locations corresponding to the actual information, including the order of the locations.

Furthermore, the location identification information included in the planned information may be different data, such as a store name, while the location identification information included in the actual information may be location information (latitude, longitude). In such cases, the location information (latitude, longitude) corresponding to the store name is managed in the work location information storage unit 512, and the inspection unit 533 determines whether the location information (latitude, longitude) and the location information (latitude, longitude) included in the actual information meet predetermined proximity conditions. The condition is that the distance between the two locations is less than or equal to a threshold.
(2) Checking the consistency between scheduled information such as shift schedules and sales activity information.

The inspection unit 533 retrieves one or more location-specific pieces of information from the schedule information storage unit 5171, which are associated with the employee identifier of interest and the date information of the day to be processed. The inspection unit 533 also retrieves one or more location-specific pieces of information from the sales activity information, which are associated with the employee identifier of interest and the date information of the day to be processed, from the performance information storage unit 5172. For example, in the sales activity information, a predetermined string of characters (e.g., "Company A, Company B") corresponding to a key term (e.g., <Visiting Destination>) is retrieved, and location-specific information (e.g., address, location information (latitude, longitude)) paired with this string (e.g., "Company A", "Company B") is retrieved from the storage unit 51 or an external server (not shown).

Next, the inspection unit 533 determines whether one or more locations specified by one or more location-specific information included in the scheduled information match one or more locations specified by one or more location-specific information included in the sales activity information. If they match, it is determined that the scheduled information and the actual information match; if even one does not match, it is determined that the scheduled information and the actual information do not match. Furthermore, if an employee has two or more work locations on a given day, the inspection unit 533 retrieves two or more locations specified by two or more location-specific information included in the scheduled information in order of work time, and also retrieves two or more locations specified by two or more location-specific information included in the sales activity information in order of work time (order of appearance). Then, including the order of the locations, it determines whether two or more locations corresponding to the scheduled information match two or more locations corresponding to the actual information.

Furthermore, the location identification information included in the planned information may be different data, such as a store name, while the location identification information included in the actual information may be location information (latitude, longitude).
(3) Checking the consistency between scheduled information such as shift schedules and the information entered for work.

The inspection unit 533 retrieves one or more location-specific pieces of information from the schedule information storage unit 5171, where the shift schedule information is stored, which are associated with the employee identifier of interest and the day information of the day to be processed. The inspection unit 533 also retrieves all input information associated with the employee identifier of interest and the day information of the day to be processed from the performance information storage unit 5172. For example, the input information may be a file, and the day information is obtained from the update date and time information. Next, the inspection unit 533 retrieves location-specific information (for example, location information (latitude, longitude)) that corresponds to the retrieved input information. It is assumed that the input information is associated with the location-specific information that was entered.

Next, the inspection unit 533 determines whether the one or more locations identified by one or more location identification pieces included in the planned information match the one or more locations identified by one or more location identification pieces corresponding to the input information. If they match, it is determined that the planned information and the actual information match; if even one does not match, it is determined that the planned information and the actual information do not match.

If an employee has two or more work locations on a given day, the inspection unit 533 retrieves the locations specified by the two or more location identification pieces included in the scheduled information, in order of work time, and also retrieves the locations specified by the two or more location identification pieces corresponding to the input information, in order of work time (in order of update date and time). Then, it determines whether the two or more locations corresponding to the scheduled information and the two or more locations corresponding to the actual information match, including the order of the locations.

Furthermore, the location identification information included in the planned information may be different data, such as a store name, while the location identification information included in the actual information may be location information (latitude, longitude).
(4) Checking the consistency between scheduled information such as shift schedules and employee location information.

The inspection unit 533 obtains one or more location-specific pieces of information from the scheduled information storage unit 5171, which are associated with the employee identifier of interest and the date information of the day to be processed. The inspection unit 533 also obtains all employee location information associated with the employee identifier of interest and the date information of the day to be processed from the actual information storage unit 5172. Note that the employee location information is location information received from the employee's terminal device 6 and is associated with the date and time information.

Next, the inspection unit 533 obtains a work location identifier corresponding to the acquired employee location information from the work location information storage unit 512. The inspection unit 533 also obtains location identification information (e.g., location information (latitude, longitude)) corresponding to the work location identifier. If it determines that the distance between this location information and the employee location information is within or below a threshold, it determines that the work location identified by the work location identifier is the work location where the employee was. The inspection unit 533 then determines whether one or more work location identifiers obtained using the employee location information match the work location identifiers indicated by one or more location identification information included in the scheduled information, including their order. If they match, it determines that the scheduled information and the actual information match; if even one does not match, it determines that the scheduled information and the actual information do not match.

The decision considering the order of work is made, as mentioned above, when an employee works at two or more locations.
(5) In the case of working from home

If the inspection unit 533 determines that information indicating teleworking exists in the scheduled information associated with the employee identifier under consideration and the day information for the processing target, and if the location identification information in the actual information associated with the employee identifier under consideration and the day information for the processing target contains a work location identifier or information corresponding to the work location identifier, the inspection unit 533 determines that the scheduled information and the actual information do not match.

The inspection unit 533, upon determining that information indicating teleworking exists within the schedule information associated with the employee identifier under consideration and the day information for the processing target, retrieves all employee location information associated with the employee identifier under consideration and the day information for the processing target from the actual information storage unit 5172. Next, the inspection unit 533 retrieves the home location information corresponding to the employee identifier from the home location storage unit 511. Then, it determines whether the distance between the location information corresponding to the retrieved home location information and the employee location information satisfies a predetermined condition. If the predetermined condition is met, the schedule information and actual information match; if the predetermined condition is not met, the schedule information and actual information do not match. The predetermined condition is that the distance between the two points indicated by the two location information is within or less than a threshold.

If the inspection result from the inspection unit 533 indicates a mismatch, the notification unit 534 notifies the employee identified by the employee identifier corresponding to the inspection result with information regarding the inspection result. The notification unit 534 may also notify the employee with information regarding the inspection result if the inspection result from the inspection unit 533 indicates a match. The information regarding the inspection result may include, for example, the inspection result itself, information on a screen prompting the user to enter correct schedule information, and information on a screen prompting the user to enter the reason for the mismatch. The notification from the notification unit 534 may be either a user-initiated notification or a voluntary notification. In other words, the notification may be push-type or pull-type.

The movement path acquisition unit 535 acquires one or more location-specific pieces of information from one or more types of information among the scheduled or actual information stored in the work information storage unit 517, which corresponds to one employee identifier and one day's information, and uses these one or more location-specific pieces of information to acquire movement path information.

Travel route information refers to information about the travel routes of employees identified by employee identifiers. Travel route information consists of information containing one or more location-specific pieces of information, or information that can be obtained from one or more location-specific pieces of information. Examples of travel route information include: "Home → Workplace X → Home" and "Home → Station A → Station B → Workplace X → Station B → Station C → Workplace Y → Station C → Station A → Home".

The travel route acquisition unit 535 acquires location identification information corresponding to the home address and location identification information corresponding to one or more work locations from the scheduled or actual travel information. It then passes this location identification information to a server that returns travel route information (for example, the server described in Non-Patent Document 1, or the NAVITIME® server [URL: https://www.navitime.co.jp/]), and receives the travel route information from the server. Access to the server can be via API, for example, but the connection method is not specified.

For example, if the scheduled information or actual information is information that includes daily information, a first work location identifier that identifies the first work location at the start of work, and a second work location identifier that identifies the second work location at the end of work (i.e., if the scheduled information indicates that the employee will work at two or more work locations in one day), the travel route acquisition unit 535 will, for example, acquire home location information corresponding to the employee identifier from the home location storage unit 511, and the travel route acquisition unit 535 will acquire first location identification information that is paired with the first work location identifier corresponding to the employee identifier from the work location information storage unit 512. Next, the travel route acquisition unit 535 will use the home location information and the first location identification information to acquire first travel route information from home to the work location at the start of work. Alternatively, the travel route acquisition unit 535 may acquire commuting route information corresponding to the employee identifier from the commuting route storage unit 515 and use that commuting route information to acquire first travel route information from home to work location. Furthermore, the travel route acquisition unit 535 may pass home location information and first location identification information to a server (not shown) that returns travel route information, and receive the first travel route information from that server.

Furthermore, the movement path acquisition unit 535 acquires second location identification information, which is paired with the second work location identifier, from the work location information storage unit 512. The movement path acquisition unit 535 also uses the first location identification information and the second location identification information to acquire second movement path information from the first work location to the second work location. The movement path acquisition unit 535 may, for example, pass the first location identification information and the second location identification information to a server that returns movement path information, and receive the second movement path information from that server.

Furthermore, the travel route acquisition unit 535 uses the second location identification information and the home location information to acquire third travel route information from the second work location to the home. Alternatively, the travel route acquisition unit 535 may acquire commuting route information corresponding to the employee identifier from the commuting route storage unit 515 and use this commuting route information to acquire third travel route information from the work location to the home. Alternatively, the travel route acquisition unit 535 may pass the second location identification information and the home location information to a server that returns travel route information and receive the third travel route information from that server.

Furthermore, information containing daily information, a first work location identifier identifying the first work location at the start of work, and a second work location identifier identifying the second work location at the end of work, is, for example, shift schedule information.

The travel route acquisition unit 535 acquires travel information corresponding to the employee identifier from the travel information storage unit 514. The travel route acquisition unit 535 determines whether the travel information indicates that the travel vehicle is used for commuting. If the travel information indicates that the travel vehicle is used for commuting, the travel route acquisition unit 535 uses one or more types of information (planned information or actual information) and the home location information corresponding to the employee identifier to acquire travel route information that specifies the road route from home to the workplace. If the travel information indicates that the travel vehicle is used for commuting, the travel route acquisition unit 535 may, for example, read travel route information stored in the commuting route storage unit 515, which specifies the road route from home to the workplace. If the travel information indicates that the travel vehicle is used for commuting, the travel route acquisition unit 535 may, for example, pass the home location information and the workplace location identification information to a server (not shown) that returns travel route information specifying the road route, and receive travel route information specifying the road route from home to the workplace from the server.

It is preferable for the travel route acquisition unit 535 to use different APIs when acquiring travel route information that specifies a road route and when acquiring travel route information that specifies a transportation route. It is also preferable for the travel route acquisition unit 535 to query different servers when acquiring travel route information that specifies a road route and when acquiring travel route information that specifies a transportation route.

The travel route acquisition unit 535 acquires travel route information daily and for each employee identifier. The timing of the travel route acquisition unit 535's acquisition of travel route information is not specified.

The travel route acquisition unit 535 may acquire travel route information using actual travel route information or using planned travel route information.

It is preferable for the travel path acquisition unit 535 to acquire travel path information using the planned information or the actual information only when the inspection unit 533 obtains an inspection result indicating that the planned information and the actual information match.

The travel expense acquisition unit 536 acquires travel expense information to identify travel expenses using planned or actual travel information. For example, the travel expense acquisition unit 536 acquires travel expense information to identify travel expenses using travel route information acquired by the travel route acquisition unit 535. Travel expenses refer to expenses related to employee travel for business purposes. Travel expenses are, for example, the costs incurred for travel. Travel expenses are typically expenses that the company should bear. Travel expenses are typically commuting expenses or transportation expenses.

The timing of the acquisition of travel expense information by the travel expense acquisition unit 536 is not specified. The acquisition of travel expense information by the travel expense acquisition unit 536 and the acquisition of travel route information by the travel route acquisition unit 535 may occur at the same time. In other words, one or more location-specific information points acquired using planned or actual travel information may be passed to a server (not shown), and travel route information and travel expense information may be received simultaneously from that server. Even in such cases, travel expense information is usually acquired using travel route information.

The travel expense acquisition unit 536 acquires the regular travel information corresponding to the employee identifier from the regular travel information storage unit 513. Next, the travel expense acquisition unit 536 determines whether the regular travel information indicates that a commuter pass has been acquired. If the travel expense acquisition unit 536 determines that the regular travel information indicates a commuter pass has been acquired, and the account determination unit 537 determines that the travel expense information corresponds to an account related to commuter expenses, then the travel expense acquisition unit 536 acquires travel expense information of "0".

The travel expense acquisition unit 536 acquires travel information corresponding to the employee identifier from the travel information storage unit 514. Next, the travel expense acquisition unit 536 determines whether the travel information indicates that travel is used for commuting. If the travel information indicates that travel is used for commuting, and the account determined by the account determination unit 537 is determined to be an account related to commuting expenses, the travel expense acquisition unit 536 acquires travel expense information of "0".

The travel expense acquisition unit 536 passes one or more point-specific pieces of information contained in the travel route information, or information obtained from one or more such point-specific pieces of information, to a server (not shown) (for example, the server described in Non-Patent Document 1, or the NAVITIME® server [URL: https://www.navitime.co.jp/]), and obtains the travel expenses between points from the server. The travel expense acquisition unit 536 then sums the travel expenses between points and obtains travel expense information. Access to the server can be done using, for example, an API, but the connection method is not specified.

The subject determination unit 537 obtains commuting route information corresponding to the employee identifier from the commuting route storage unit 515. Using this commuting route information and the location identification information contained in the travel route information corresponding to the employee identifier, the subject determination unit 537 determines whether all or part of the travel expense information corresponds to a commuting expense account, or whether all or part of the travel expense information corresponds to a transportation expense account. The commuting expense account is usually "commuting expenses." The transportation expense account is usually "transportation expenses" or "travel and transportation expenses." However, the name of the account is not specified. The location identification information contained in the travel route information corresponding to the employee identifier is, for example, the location identification information contained in the actual travel information, but it may also be the location identification information contained in the planned travel information.

The subject determination unit 537 determines, for example, that travel expense information corresponding to a portion of the travel route that overlaps with the commuting route information corresponds to a subject related to commuting expenses. Furthermore, the subject determination unit 537 determines, for example, that travel expense information corresponding to a portion of the travel route that does not overlap with the commuting route information corresponds to a subject related to transportation expenses.

The subject determination unit 537 determines, for example, that travel expense information corresponding to the travel route information from the starting point location information corresponding to the home to the ending point location information corresponding to the workplace corresponds to a subject related to commuting expenses. The subject determination unit 537 also determines that travel expense information corresponding to the travel route information from the starting point location information corresponding to the workplace to the ending point location information corresponding to the home corresponds to a subject related to commuting expenses. The subject determination unit 537 also determines that travel expense information corresponding to routes other than those specified corresponds to a subject related to transportation expenses.

For example, if the travel route information indicates "home → workplace X → home," the account determination unit 537 determines that both the travel expense information corresponding to the route "home → workplace X" and the travel expense information corresponding to "workplace X → home" are accounted for as "commuting expenses."

For example, if the travel route information indicates "Home → Station A → Station B → Workplace X → Station B → Station C → Workplace Y → Station C → Station A → Home," the account determination unit 537 determines the travel expense information corresponding to "Home → Station A → Station B → Workplace X" and the travel expense information corresponding to "Workplace Y → Station C → Station A → Home" as the account "Commuting Expenses." On the other hand, the account determination unit 537 determines the travel expense information corresponding to "Workplace X → Station B → Station C → Workplace Y" as the account "Transportation Expenses." Thus, it is preferable for the account determination unit 537 to determine that travel expense information corresponding to some routes is commuting expenses, and travel expense information corresponding to other routes is transportation expenses.

The re-inspection unit 538 determines whether the actual performance information received from the employee's terminal device 6, to which the notification unit 534 notified information regarding the inspection result, meets predetermined conditions, given that the inspection result from the inspection unit 533 indicates a mismatch. These predetermined conditions include, for example, matching the planned information, including information on predetermined items (e.g., reasons for mismatch, information indicating no problems), including predetermined information (e.g., information indicating supervisor approval), including information exceeding a threshold (e.g., sufficient explanation of the reasons), and receiving the actual performance information within a predetermined time after notifying the inspection result of mismatch.

The re-inspection unit 538 may perform the same processing as the inspection unit 533. In this case, the predetermined conditions must match the scheduled information.

The reprocessing unit 539 performs different processing depending on the judgment result of the re-inspection unit 538. For example, if the re-inspection by the re-inspection unit 538 meets predetermined conditions, the reprocessing unit 539 stores the received performance information in the performance information storage unit 5172, paired with the employee identifier. If the re-inspection by the re-inspection unit 538 does not meet the predetermined conditions, the reprocessing unit 539 does not store the received performance information. If the re-inspection by the re-inspection unit 538 does not meet the predetermined conditions, the reprocessing unit 539 notifies the employee identified by the employee identifier, for example, that the re-inspection result was "inappropriate." If the re-inspection by the re-inspection unit 538 meets the predetermined conditions, the reprocessing unit 539 notifies the employee identified by the employee identifier, for example, that the re-inspection result was "appropriate." If the re-inspection by the re-inspection unit 538 meets the predetermined conditions, the reprocessing unit 539 does not provide any notification.

The output unit 54 outputs various types of information. These types of information include, for example, travel route information, travel expense information, and inspection results. The inspection results refer to information related to the inspection results from the inspection unit 533.

Here, "output" typically refers to transmission to another device (e.g., terminal device 6), but it may also encompass concepts such as handing over processing results to other processing devices or other programs, displaying on a screen, projection using a projector, printing with a printer, sound output, and storage on a recording medium.

The travel path output unit 541 outputs the travel path information acquired by the travel path acquisition unit 535. Typically, the travel path output unit 541 outputs the travel path information associated with the employee identifier and daily information. For example, the travel path output unit 541 outputs the first travel path information, the second travel path information, and the third travel path information acquired by the travel path acquisition unit 535. Here, output may also include transmission to other devices (e.g., terminal device 6), transfer to other modules, or storage in the storage unit 51.

The travel expense output unit 542 outputs the travel expense information acquired by the travel expense acquisition unit 536. Typically, the travel expense output unit 542 outputs the travel expense information associated with the employee identifier and date information.

The travel expense output unit 542 preferably outputs travel expense information in association with the account identification information that identifies the account determined by the account determination unit 537. The account identification information may include, for example, "transportation expenses," "commuting expenses," "travel expenses," or an ID that identifies the account.

The travel expense output unit 542, for example, if the account determined by the account determination unit 537 is determined to be an account related to transportation expenses, performs processing to store the travel expense information in the transportation expense database 81, which manages transportation expenses, by associating it with the employee identifier. The travel expense output unit 542 does not perform processing to store the travel expense information in the transportation expense database 81 if, for example, the account determined by the account determination unit 537 is determined to be an account related to commuting expenses.

The travel expense output unit 542, for example, if the item determined by the item determination unit 537 is determined to be an item related to commuting expenses, performs processing to store the travel expense information in the commuting expense database 91, which manages commuting expenses.

The travel expense output unit 542 performs a process to store the travel expense information in the commuting expense database 91, which manages commuting expenses, when the travel expense acquisition unit 536 acquires travel expense information that is not "0", and the account determination unit 537 determines that the account determined is an account related to commuting expenses.

The transportation expense database may reside in the information processing device 5 or in the accounting information management device 8. The commuting expense database may reside in the information processing device 5 or in the personnel information management device 9. The accounting information management device 8 and the personnel information management device 9 may be a single device.

The transmission unit 55 transmits various types of information. These types of information are change information. Change information indicates that the default schedule information or default actual information has been changed. For example, change information may include revised schedule information, revised actual information, information on the parts of the default schedule information that have been modified, and information on the parts of the default actual information that have been modified.

The change transmission unit 551 transmits the change information to the contacts indicated by one or more contact details corresponding to the employee identifier when the default schedule information or the default actual information is changed.

The change transmission unit 551, for example, if the change determination unit 530 determines that the information is incorrect, transmits the change information to the contacts indicated by one or more contact information corresponding to the employee identifier.

Change information refers to information indicating that the scheduled information has been changed from the default scheduled information, or that the actual information has been changed from the default scheduled information. Contact information can be any information indicating contact details, such as the IP address of terminal device 6, the MAC address of terminal device 6, the employee's email address, the telephone number of terminal device 6, or their ID. The contact information is stored in the storage unit 51, associated with the employee identifier.

The terminal storage unit 61, which constitutes the terminal device 6, stores various types of information. This information includes, for example, employee identifiers.

The terminal reception unit 62 receives various instructions and information. These instructions and information include, for example, schedule information, actual performance information (e.g., sales activity information, input information), corrections to default schedule information, and corrections to default performance information. It is preferable for the terminal reception unit 62 to receive schedule information corrected from the default schedule information. It is also preferable for the terminal reception unit 62 to receive actual performance information corrected from the default performance information.

The means of inputting various instructions and information can be anything, such as a touch panel, keyboard, mouse, or menu screen.

The terminal processing unit 63 performs various processes. These processes include, for example, converting instructions and information received by the terminal receiving unit 62 into instructions and information for the data structure to be transmitted. Another example is converting information received by the terminal receiving unit 65 into information for the data structure to be output.

The terminal transmission unit 64 transmits various instructions and information. These instructions and information include, for example, scheduled information, actual information, details of revisions to the scheduled information, and details of revisions to the actual information.

The terminal receiving unit 65 receives various types of information. These types of information include, for example, travel route information, travel expense information, and inspection results. Note that the inspection results may also be information displayed on a screen prompting the user to input correct performance data.

The terminal output unit 66 outputs various types of information. These types of information include, for example, travel route information, travel expense information, and inspection results.

Here, "output" is a concept that includes display on a screen, projection using a projector, printing with a printer, sound output, transmission to external devices, storage on recording media, and transfer of processing results to other processing devices or other programs.

The card reader 71, which constitutes the entry/exit information acquisition device 7, is a device that reads employee identifiers from a card (for example, an IC card) that stores employee identifiers. The entry/exit information acquisition device 7 transmits, for example, the employee identifier read by the card reader 71, date and time information indicating the date and time of reading, and location identification information of the workplace held by the entry/exit information acquisition device 7 to the information processing device 5.

The card reader 71 is, for example, an IC card reader, but it is a means of obtaining an employee identifier from a medium (card, mobile terminal, etc.) that stores the employee identifier via short-range wireless communication such as Bluetooth (registered trademark).

The transportation expense database 81, which constitutes the accounting information management device 8, stores travel expense information corresponding to the account "transportation expenses" associated with employee identifiers. The travel expense information in the transportation expense database 81 is usually associated with daily information. Furthermore, the travel expense information may also be associated with travel route information. The accounting information management device 8 may have some or all of the functions of the expense inspection device 1 of Embodiment 1. In other words, the accounting information management device 8 may store expense information, including travel expense information corresponding to the account "transportation expenses," associated with employee identifiers.

The commuting expense database 91, which constitutes the personnel information management device 9, stores travel expense information corresponding to the account "commuting expenses," associated with employee identifiers. The travel expense information in the commuting expense database 91 is usually associated with daily information. The travel expense information may also be associated with travel route information. It is preferable that the personnel information management device 9 also stores personnel information related to employees, in addition to the travel expense information corresponding to the account "commuting expenses."

The storage unit 51, home location storage unit 511, work location information storage unit 512, regular information storage unit 513, mobile information storage unit 514, commute route storage unit 515, default storage unit 516, work information storage unit 517, scheduled information storage unit 5171, actual information storage unit 5172, terminal storage unit 61, transportation expense database 81, and commute expense database 91 are preferably made of non-volatile recording media, but can also be made of volatile recording media.

The process by which information is stored in the storage unit 51, etc., is not specified. For example, information may be stored in the storage unit 51, etc., via a recording medium, information transmitted via a communication line, etc., may be stored in the storage unit 51, etc., or information input via an input device may be stored in the storage unit 51, etc.

The receiving unit 52, the scheduled receiving unit 521, the actual receiving unit 522, and the terminal receiving unit 65 are usually implemented using wireless or wired communication means, but they may also be implemented using means for receiving broadcasts.

The processing unit 53, change determination unit 530, planned storage unit 531, actual storage unit 532, inspection unit 533, travel route acquisition unit 535, travel expense acquisition unit 536, account determination unit 537, re-inspection unit 538, re-processing unit 539, and terminal processing unit 63 can typically be implemented using a processor, memory, etc. The processing procedures of the processing unit 13, etc., are typically implemented in software, and this software is recorded on a recording medium such as ROM. However, it may also be implemented in hardware (dedicated circuitry). The processor can be, for example, a CPU, MPU, GPU, etc., and its type is not specified.

The notification unit 534, output unit 54, travel route output unit 541, travel expense output unit 542, transmission unit 55, change transmission unit 551, and terminal transmission unit 64 are typically implemented by wireless or wired communication means, but may also be implemented by broadcasting means.

The terminal reception unit 62 can be implemented using device drivers for input means such as touch panels and keyboards, or control software for menu screens.

The terminal output unit 66 may or may not be considered to include output devices such as displays and speakers. The terminal output unit 66 can be implemented using driver software for the output device, or a combination of driver software and the output device itself.

Next, we will explain an example of the operation of information system B. First, we will explain an example of the operation of information processing device 5 using the flowchart in Figure 14.

(Step S1401) The change determination unit 530 determines, by associating it with the employee identifier, whether or not it has received information regarding a modification from the default schedule information. If information regarding a modification of the schedule information has been received, the process proceeds to step S1402; otherwise, it proceeds to step S1403.

Furthermore, the information regarding the modification of the schedule information may be the modified schedule information itself, or information regarding the parts modified from the default schedule information. The change determination unit 530 may also obtain the default schedule information corresponding to the employee identifier from the default storage unit 516 and determine whether the default schedule information and the received schedule information are different or the same.

(Step S1402) The processing unit 53 uses the information received in step S1401 to construct the change information to be transmitted. The processing unit 53 obtains the employee identifier. The processing unit 53 obtains one or more contact information entries corresponding to the employee identifier from the storage unit 51. The change transmission unit 551 transmits the obtained change information to one or more contacts identified by each of the one or more contact information entries. The process returns to step S1401.

The contact information may include, for example, a supervisor. It may also include, for example, the employee in question. Furthermore, the change information here refers to information indicating that the schedule information has been changed from the default information; the changed schedule information itself is also acceptable.

(Step S1403) The change determination unit 530 determines, in association with the employee identifier, whether or not it has received information regarding a modification from the default performance information. If information regarding a modification of performance information has been received, the process proceeds to step S1404; otherwise, it proceeds to step S1405.

Furthermore, the information regarding the modification of performance data may be the modified performance data itself, or information regarding the parts modified from the default performance data. Also, the change determination unit 530 may obtain the default performance data corresponding to the employee identifier from the default storage unit 516 and determine whether the default performance data and the received performance data are different or the same.

(Step S1404) The processing unit 53 uses the information received in step S1403 to construct the change information to be transmitted. The processing unit 53 obtains the employee identifier. The processing unit 53 obtains one or more contact information entries corresponding to the employee identifier from the storage unit 51. The change transmission unit 551 transmits the change information to one or more contacts identified by each of the one or more contact information entries. The process returns to step S1401.

The contact information may include, for example, the supervisor. It may also include, for example, the employee in question. The change information here refers to information indicating that the performance information has been changed from the default information; the changed performance information itself may also be included.

(Step S1405) The processing unit 53 determines whether it is time to perform an inspection to check whether the planned information and the actual information match. If it is time to perform the inspection, the process proceeds to step S1406; otherwise, it proceeds to step S1414.

Furthermore, the processing unit 53 determines, for example, that it is time to perform an inspection when a predetermined time (for example, the end of the workday [for example, 10 PM]) has arrived, or when performance information has been received.

(Step S1406) The processing unit 53 assigns 1 to counter i.

(Step S1407) The processing unit 53 determines whether the i-th employee to be inspected exists. If the i-th employee to be inspected exists, the process proceeds to step S1408; otherwise, the process returns to step S1401.

(Step S1408) The inspection unit 533 pairs the employee identifier of the i-th employee to be inspected and checks whether the scheduled information and actual information corresponding to the day information for the target day match. An example of this inspection process will be explained using the flowchart in Figure 15.

(Step S1409) The processing unit 53 determines whether the planned information and the actual information matched based on the results of the inspection in step S1408. If they matched, the process proceeds to step S1410; otherwise, it proceeds to step S1413. Note that a match means the inspection result is valid.

(Step S1410) The processing unit 53 performs the travel route acquisition process. An example of the travel route acquisition process will be explained using the flowchart in Figure 16. The travel route acquisition process includes the process of acquiring travel route information, the process of acquiring travel expense information, and the process of determining the travel expense categories.

(Step S1411) The travel route output unit 541 outputs the travel route information acquired in step S1410, associating it with the employee identifier. The travel route output unit 541, for example, notifies the employee identified by the employee identifier of the travel route information. The travel route output unit 541, for example, notifies the contacts indicated by one or more contact information paired with the employee identifier. The travel route output unit 541, for example, stores the travel route information in the storage unit 51, etc., associating it with the employee identifier and the day information.

Furthermore, the travel expense output unit 542 may output travel expense information associated with an employee identifier. Alternatively, the travel expense output unit 542 may output both the expense account and the travel expense information associated with an employee identifier.

(Step S1412) The processing unit 53 increments counter i by 1. The process returns to step S1407.

(Step S1413) The notification unit 534 notifies the employee (terminal device 6) identified by the employee identifier that the inspection results did not match. Return to step S1401.

Furthermore, the notification unit 534 may send a screen prompting the input of correct performance information to the employee (terminal device 6) identified by the employee identifier. The notification unit 534 may also send information indicating that the inspection results did not match to the contact information indicated by one or more contact details corresponding to the employee identifier. This information regarding the mismatch in inspection results may also include information from the screen prompting the input of correct performance information and information from the screen prompting the input of the reason for the mismatch.

(Step S1414) The receiving unit 52 determines whether or not it has received information for re-examination. If information for re-examination has been received, the process proceeds to step S1415; if information for re-examination has not been received, the process proceeds to step S1416.

(Step S1415) The re-inspection unit 538, etc., performs re-inspection and other processing. The process returns to Step S1401. This re-inspection and other processing will be explained using the flowchart in Figure 20.

(Step S1416) The performance receiving unit 522 determines whether or not performance information has been received, associated with the employee identifier. If performance information is received, the process proceeds to step S1417; otherwise, it returns to step S1401.

The performance information received here includes, for example, one or more of the following: entry/exit information, sales activity information, input information entered by employees for the purpose of performing their work, and employee location information including one or more location details.

(Step S1417) The output unit 54 stores the information received in step S1416 in the performance information storage unit 5172, associating it with the employee identifier. Return to step S1401.

The output unit 54 typically acquires date information and stores the information received in step S1416 in the performance information storage unit 5172, associating it with the date information. The output unit 54 may acquire date information from a clock (not shown) or it may acquire date information received together with the performance information.

In the flowchart shown in Figure 14, processing terminates upon power off or processing completion interruption.

Next, an example of the inspection process in step S1408 will be explained using the flowchart in Figure 15.

(Step S1501) The inspection unit 533 obtains the employee identifier of the employee to be inspected.

(Step S1502) The inspection unit 533 obtains schedule information from the schedule information storage unit 5171 that is paired with the employee identifier obtained in step S1501 and with the date information for the target day. The inspection unit 533 may obtain the date information for the target day from a clock (not shown), or it may obtain the date information received together with other information such as performance information.

(Step S1503) The inspection unit 533 retrieves performance information from the performance information storage unit 5172 that is paired with the employee identifier obtained in step S1501 and with the daily information for the target day. The inspection unit 533 may also retrieve the performance information received immediately before.

(Step S1504) The inspection unit 533 determines whether the schedule information obtained in step S1502 indicates work. If it indicates work, the process proceeds to step S1505; otherwise, it proceeds to step S1515. Note that information indicating work refers to information about working days, not days off.

Furthermore, the inspection unit 533 determines, for example, that if the scheduled information contains one or more location-specific pieces of information, the scheduled information indicates work. The inspection unit 533 determines, for example, that the scheduled information does not indicate work if it indicates "annual leave," "holiday," or "NULL."

(Step S1505) The inspection unit 533 assigns 1 to counter i.

(Step S1506) The inspection unit 533 determines whether the i-th location identification information exists in the schedule information obtained in step S1502. If the i-th location identification information exists, the process proceeds to step S1507; if the i-th location identification information does not exist, the process proceeds to step S1513.

(Step S1507) The inspection unit 533 obtains the i-th location identification information from the scheduled information acquired in step S1502.

(Step S1508) The inspection unit 533 determines whether the i-th location identification information exists in the performance information acquired in step S1503. If the i-th location identification information exists, the process proceeds to step S1509; if the i-th location identification information does not exist, the process proceeds to step S1512.

(Step S1509) The inspection unit 533 obtains the i-th location identification information from the performance information acquired in step S1503.

(Step S1510) The inspection unit 533 determines whether the i-th location identification information in the planned information matches the i-th location identification information in the actual information. If they match, the process proceeds to step S1511; otherwise, it proceeds to step S1512.

Furthermore, if the data type of the i-th location identification information in the planned information does not match the data type of the i-th location identification information in the actual information, the inspection unit 533 will match the data types of both data and then determine whether the two data match. A case where the data types do not match is, for example, when one is (latitude, longitude) and the other is a work location identifier. In such a case, the inspection unit 533 will, for example, obtain from the work location information storage unit 512 the work location identifier that is paired with the (latitude, longitude) closest to one of the (latitude, longitude) data. Alternatively, the inspection unit 533 will obtain from the work location information storage unit 512 the (latitude, longitude) paired with the work location identifier and determine whether the distance between that (latitude, longitude) and the (latitude, longitude) of the other information is within or below a threshold.

(Step S1511) The inspection unit 533 increments counter i by 1. Return to step S1506.

(Step S1512) The inspection unit 533 assigns "information indicating a mismatch" to the variable "inspection result". It then returns to the higher-level processing unit.

(Step S1513) The inspection unit 533 determines whether the i-th location identification information exists in the performance information obtained in step S1503. If the i-th location identification information exists, the process proceeds to step S1512; if the i-th location identification information does not exist, the process proceeds to step S1514.

(Step S1514) The inspection unit 533 assigns the "information indicating a match" to the variable "inspection result". It then returns to the higher-level processing unit.

(Step S1515) The inspection unit 533 determines whether the performance information obtained in step S1503 indicates that work was performed. If it is performance information indicating that work was performed, the process proceeds to step S1512; otherwise, the process proceeds to step S1514.

Next, an example of the process for acquiring the travel path, etc., in step S1410 will be explained using the flowchart in Figure 16.

(Step S1601) The movement path acquisition unit 535 acquires the employee identifier of the employee whose movement path information is to be acquired.

(Step S1602) The travel route acquisition unit 535 acquires from the work information storage unit 517 the scheduled or actual information that corresponds to the employee identifier acquired in step S1601, and the scheduled or actual information that corresponds to the day information of the day for which the travel route information is to be acquired. The travel route acquisition unit 535 acquires the first location identification information, excluding the home address, from the scheduled or actual information acquired in step S1602. It is assumed that the scheduled or actual information stores location identification information in the order of the locations the employee traveled to.

(Step S1603) The travel route acquisition unit 535, etc., acquires travel route information, etc., from the home to the first work location identified by the first point identification information. This process is called the commute route acquisition process. The commute route acquisition process will be explained using the flowchart in Figure 17.

(Step S1604) The movement path acquisition unit 535 assigns 2 to counter i.

(Step S1605) The travel path acquisition unit 535 determines whether the i-th location identification information exists in the planned information or actual information acquired in step S1602. If the i-th location identification information exists, the process proceeds to step S1606; if the i-th location identification information does not exist, the process proceeds to step S1609.

(Step S1606) The travel route acquisition unit 535 acquires the i-th location identification information, excluding the home address, from the planned or actual location information acquired in step S1602.

(Step S1607) The movement route acquisition unit 535, etc., acquires movement route information between two work locations. This process is called the inter-work location route acquisition process. The inter-work location route acquisition process will be explained using the flowchart in Figure 18.

(Step S1608) The movement path acquisition unit 535 increments counter i by 1. Return to step S1605.

(Step S1609) The travel route acquisition unit 535, etc., acquires travel route information from the last work location identified by the last (i-1) location identification information to the user's home. It then returns to the higher-level processing. This process is called the return-home route acquisition process. The return-home route acquisition process will be explained using the flowchart in Figure 19.

Next, the process of acquiring the commute route, etc., in step S1604 will be explained using the flowchart in Figure 17.

(Step S1701) The movement path acquisition unit 535 attempts to acquire movement information paired with the employee identifier of the target employee from the movement information storage unit 514. However, there may be cases where the movement information paired with the employee identifier cannot be acquired.

(Step S1702) The travel route acquisition unit 535 determines whether the travel information acquired in step S1701 indicates that "travel (e.g., a private car) is used for commuting." If the information indicates that travel is used for commuting, the process proceeds to step S1703. If the information indicates that travel is not used for commuting, the process proceeds to step S1705. If travel information could not be acquired in step S1701, the process usually proceeds to step S1705.

(Step S1703) The travel route acquisition unit 535 uses the first travel route information, which indicates "Home → Workplace corresponding to the first location identification information (using mobile device)". The first travel route information is a part of the travel route information that constitutes the final output travel route information.

(Step S1704) The travel expense acquisition unit 536 acquires travel expense information "0" by associating it with the first travel route information acquired in step S1703. It then returns to the higher-level processing. Note that the account determination unit 537 may acquire the account "Commuting Expenses" at this point.

(Step S1705) The travel route acquisition unit 535 acquires commute route information from the commute route storage unit 515, which is the commute route information from the employee's home to the workplace, paired with the employee identifier of the target employee. For example, such commute route information might be "Home → Station A → Station B → Workplace X". Alternatively, the travel route acquisition unit 535 may transmit the employee's home location information and workplace location identification information to a server (not shown), and receive the travel route information from the home to the workplace from that server.

(Step S1706) The travel expense acquisition unit 536 acquires periodic information corresponding to the employee identifier of the target employee from the periodic information storage unit 513. Note that the travel expense acquisition unit 536 may not be able to acquire periodic information in some cases.

(Step S1707) The travel expense acquisition unit 536 determines whether the regular pass information acquired in step S1706 indicates that a "commuter pass has been acquired." If the information indicates that a "commuter pass has been acquired," the system proceeds to step S1708. If the information does not indicate that a "commuter pass has been acquired," the system proceeds to step S1709. Note that if regular pass information could not be acquired in step S1706, the system usually proceeds to step S1709.

(Step S1708) The travel expense acquisition unit 536 acquires travel expense information "0". It returns to the higher-level processing. Note that the account determination unit 537 may acquire the account "commuting expenses" at this point.

(Step S1709) The travel expense acquisition unit 536 acquires travel expense information from the employee's home to the workplace corresponding to the first location identification information. The travel expense acquisition unit 536, for example, acquires travel expense information paired with the employee identifier of the target employee from the storage unit 51. The travel expense acquisition unit 536 also transmits, for example, the home location identification information and the first location identification information to a server (not shown), receives travel expense information or travel expense information that forms the basis of the travel expense information, and acquires the travel expense information. Such a server is, for example, a server possessing the technology described in Non-Patent Document 1, and is publicly known technology.

(Step S1710) The subject determination unit 537 acquires the subject "Commuting Expenses".

(Step S1711) The travel expense output unit 542 processes the travel expense information acquired in step S1709, associating it with the account "commuting expenses" acquired in step S1710 and the employee identifier, and stores it in the commuting expense database 91. It then returns to the higher-level processing.

The travel expense output unit 542 transmits, for example, the employee identifier, the daily information, and the travel expense information acquired in step S1709 to the personnel information management device 9. The personnel information management device 9 receives the employee identifier, daily information, and travel expense information, associates the travel expense information with the employee identifier and daily information, and stores the travel expense information in the commuting expense database 91.

Next, the process of acquiring the route between work locations in step S1607 will be explained using the flowchart in Figure 18.

(Step S1801) The travel path acquisition unit 535 acquires two location identification pieces of information.

(Step S1802) The travel route acquisition unit 535 acquires second travel route information between the two work locations identified by the two location identification pieces. The travel route acquisition unit 535, for example, transmits the two location identification pieces to an external server (not shown) and receives the second travel route information from that server.

(Step S1803) The travel expense acquisition unit 536 acquires travel expense information between two work locations using two location-specific pieces of information. For example, the travel expense acquisition unit 536 transmits the two location-specific pieces of information to an external server (not shown) and receives travel expense information or information that forms the basis of the travel expense information from that server. For example, the travel expense acquisition unit 536 acquires travel expense information from the travel expense information or information that forms the basis of the travel expense information received in step S1802.

(Step S1804) The subject determination unit 537 acquires the subject "Transportation Expenses".

(Step S1805) The travel expense output unit 542 processes the travel expense information, associating it with the account "Transportation Expenses" and the employee identifier, and stores it in the transportation expense database 81. It then returns to the higher-level processing.

The travel expense output unit 542 transmits, for example, travel expense information, employee identifiers, and date information to the accounting information management device 8. The accounting information management device 8 receives the travel expense information, employee identifiers, and date information, and stores the travel expense information in the travel expense database 81, associating it with the employee identifier and date information.

Next, the process of acquiring the return route, etc., in step S1609 will be explained using the flowchart in Figure 19.

(Step S1901) The movement path acquisition unit 535 attempts to acquire movement information paired with the employee identifier of the target employee from the movement information storage unit 514. However, there may be cases where movement information paired with the employee identifier cannot be acquired.

(Step S1902) The travel route acquisition unit 535 determines whether the travel information acquired in step S1901 indicates that "a travel vehicle (e.g., a private car) is used for commuting." If the information indicates that a travel vehicle is used for commuting, the process proceeds to step S1903. If the information indicates that a travel vehicle is not used for commuting, the process proceeds to step S1905.

(Step S1903) The travel route acquisition unit 535 acquires third travel route information indicating "workplace → home (using mobile device) corresponding to the last point identification information." This third travel route information is a part of the travel route information that constitutes the final output travel route information.

(Step S1904) The travel expense acquisition unit 536 acquires travel expense information "0" by associating it with the third travel route information acquired in step S1903. It then returns to the higher-level processing. Note that the account determination unit 537 may acquire the account "Commuting Expenses" at this point.

(Step S1905) The travel route acquisition unit 535 acquires commute route information from the commute route storage unit 515, which is the commute route information from home to the workplace, paired with the employee identifier of the target employee. For example, this commute route information might be "Workplace X → Station B → Station A → Home".

(Step S1906) The travel expense acquisition unit 536 acquires the periodic information corresponding to the employee identifier of the target employee from the periodic information storage unit 513. Note that the travel expense acquisition unit 536 may not be able to acquire the periodic information in some cases.

(Step S1907) The travel expense acquisition unit 536 determines whether the regular information acquired in step S1906 indicates that a commuter pass has been obtained. If the information indicates that a commuter pass has been obtained, the unit proceeds to step S1908; otherwise, it proceeds to step S1909.

(Step S1908) The travel expense acquisition unit 536 acquires travel expense information "0". It returns to the higher-level processing. Note that at this point, the account determination unit 537 may acquire the account "commuting expenses".

(Step S1909) The travel expense acquisition unit 536 acquires travel expense information from the last work location to the employee's home. The travel expense acquisition unit 536, for example, acquires travel expense information paired with the employee identifier of the employee in question, from the storage unit 51. Furthermore, the travel expense acquisition unit 536 transmits, for example, the last location identification information and the home location identification information to a server (not shown), receives the travel expense information or the travel expense information that forms the basis of the travel expense information, and acquires the travel expense information.

(Step S1910) The subject determination unit 537 acquires the subject "Commuting Expenses".

(Step S1911) The travel expense output unit 542 processes the travel expense information acquired in step S1909, associating it with the account "commuting expenses" acquired in step S1910 and the employee identifier, and stores it in the commuting expense database 91. It then returns to the higher-level processing.

The travel expense output unit 542 transmits, for example, the employee identifier, the daily information, and the travel expense information acquired in step S1909 to the personnel information management device 9. The personnel information management device 9 receives the employee identifier, daily information, and travel expense information, associates the travel expense information with the employee identifier and daily information, and stores the travel expense information in the commuting expense database 91.

Next, the re-inspection and other processing steps in step S1415 will be explained using the flowchart in Figure 20.

(Step S2001) The re-inspection unit 538 determines whether the received information includes performance information. If performance information is included, the process proceeds to step S1408; otherwise, it proceeds to step S2002.

(Step S2002) The re-inspection unit 538 acquires the received information.

(Step S2003) The re-inspection unit 538 acquires the predetermined conditions of the storage unit 51.

(Step S2004) The re-inspection unit 538 determines whether the information obtained in step S2002 satisfies the conditions obtained in step S2003. If the conditions are met, the process proceeds to step S2005; otherwise, it proceeds to step S1413.

(Step S2005) The reprocessing unit 539 associates the information acquired in step S2002 with the employee identifier and the date information, and returns it to the higher-level processing unit that stores it in the storage unit 51.

Furthermore, in the flowchart of Figure 20, the re-inspection unit 538 may determine whether the inspection result from the inspection unit 533 is inconsistent, and whether the performance information was received by the employee's terminal device 6, to which the notification unit 534 notified information regarding the inspection result, within the timeframe up to the scheduled time. It is preferable that the re-processing unit 539 performs different processing depending on whether the performance information was received or not within the timeframe up to the scheduled time.

Next, an example of the operation of terminal device 6 will be explained using the flowchart in Figure 21.

(Step S2101) The terminal reception unit 62 determines whether or not it has received a correction to the scheduled information or actual information. If a correction to the scheduled information or actual information has been received, the process proceeds to step S2102. If a correction to the scheduled information or actual information has not been received, the process proceeds to step S2103.

(Step S2102) The terminal processing unit 63 obtains the employee identifier from the terminal storage unit 61 and constructs information containing the employee identifier and information related to the correction of scheduled or actual information. The terminal transmission unit 64 transmits the constructed information to the information processing device 5. Return to step S2101.

(Step S2103) The terminal receiving unit 65 determines whether or not it has received information from the information processing device 5. If information is received, the process proceeds to step S2104; if no information is received, the process proceeds to step S2105. Here, the information includes, for example, default schedule information, default actual information, travel route information, travel expense information, and account details.

(Step S2104) The terminal processing unit 63 converts the information received in step S2103 into information with an output structure. The terminal output unit 66 outputs this information. The process returns to step S2101.

(Step S2105) The terminal processing unit 63 determines whether it is time to transmit the mobile object's position information. If it is time to transmit the mobile object's position information, the process proceeds to step S2106; otherwise, it proceeds to step S2108.

(Step S2106) The terminal processing unit 63 acquires the mobile object location information. The terminal processing unit 63 acquires the employee identifier from the terminal storage unit 61 and constructs information that includes the employee identifier and the mobile object location information, and has a structure for transmission.

(Step S2107) The terminal transmission unit 64 transmits the information configured in step S2106 to the information processing device 5. Return to step S2101.

(Step S2108) The terminal reception unit 62 determines whether or not it has received performance information (e.g., sales activity information, input information). If performance information has been received, the process proceeds to step S2109; otherwise, it returns to step S2101.

(Step S2109) The terminal processing unit 63 obtains the employee identifier from the terminal storage unit 61 and constitutes information to be transmitted, which includes the employee identifier and the received performance information. The terminal transmission unit 64 transmits this information to the information processing device 5. The process returns to Step S2101.

In the flowchart shown in Figure 21, processing terminates upon power off or processing completion interruption.

In summary, according to this embodiment, accurate information about an employee's travel route can be obtained using one or more types of information from employee schedule information and actual travel information.

Furthermore, in this embodiment, it is possible to check the consistency between employee schedule information and actual performance information.

Furthermore, in this embodiment, the consistency between planned information and actual information can be checked, and if there is a discrepancy, the employee can be notified of the discrepancy.

Furthermore, in this embodiment, travel expense information can be acquired. Additionally, the appropriate category of travel expense information can be acquired.

Furthermore, in this embodiment, travel expense information corresponding to the travel expense category can be stored in the travel expense database 81.

Furthermore, in this embodiment, appropriate commuting expenses can be obtained using regular travel information.

Furthermore, in this embodiment, employees who apply for commuting by private car or other means of transportation can receive appropriate commuting expenses.

Furthermore, in this embodiment, travel expense information corresponding to the commuting expense category can be stored in the commuting expense database 91.

Furthermore, in this embodiment, it is possible to output information on appropriate travel routes for travel expenses of employees who move between two or more work locations in a single day.

Furthermore, in this embodiment, it is possible to determine the appropriate expense category for travel expenses of employees who move between two or more work locations in a single day.

Furthermore, in this embodiment, information on appropriate travel routes can be obtained for employees who commute using a mobile device.

Furthermore, in this embodiment, if there are any changes from the default schedule information or actual performance information, the appropriate person, such as a supervisor, can be notified.

Furthermore, in this embodiment, appropriate processing can be performed when the planned information and the actual information do not match.

Furthermore, in this embodiment, the accurate travel routes of employees can be obtained using appropriate performance information.

Furthermore, the information processing device 5 may have the functions of the expense inspection device 1 described in Embodiment 1 (such as the function of inspecting expense information). For example, the information processing device 5 may use actual performance information such as entry/exit information and sales activity information to inspect for fraud related to travel expense information (transportation expenses or commuting expenses).

Furthermore, the notification unit 534 in the information processing device 5 may also be equipped with an output unit 54. In other words, the inclusion relationships of the components in the information processing device 5, etc., are not relevant. It goes without saying that each component only needs to perform its own function.

Furthermore, the software that implements the information processing device 5 in this embodiment is as follows: This program causes a computer that can access a work information storage unit, where one or more types of information—specifically, schedule information (information relating to an employee's work schedule and containing location identification information to identify the work location) or actual work information (information relating to an employee's actual work and containing location identification information)—are stored in association with one or more employee identifiers. The program functions as a travel path acquisition unit, which acquires location identification information corresponding to an employee identifier from the work information storage unit, and uses this location identification information to acquire travel path information relating to the travel route of the employee identified by that employee identifier; and as a travel path output unit, which outputs the travel path information.

Furthermore, Figure 22 shows the external appearance of a computer that executes the program described herein to realize the various embodiments of the cost inspection device 1, etc., described above. The embodiments described above can be realized with computer hardware and computer programs executed thereon. Figure 22 is an overview of this computer system 300, and Figure 23 is a block diagram of the system 300.

In Figure 22, the computer system 300 includes a computer 301 with a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

In Figure 23, the computer 301 includes, in addition to the CD-ROM drive 3012, an MPU 3013, a bus 3014 connected to the CD-ROM drive 3012, a ROM 3015 for storing programs such as boot-up programs, a RAM 3016 connected to the MPU 3013 for temporarily storing application program instructions and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs, and data. Although not shown here, the computer 301 may further include a network card providing connectivity to a LAN.

The program that causes the computer system 300 to execute the functions of the information processing device 5, etc., as described above, may be stored on the CD-ROM 3101, inserted into the CD-ROM drive 3012, and then transferred to the hard disk 3017. Alternatively, the program may be transmitted to the computer 301 via a network (not shown) and stored on the hard disk 3017. The program is loaded into the RAM 3016 during execution. The program may also be loaded directly from the CD-ROM 3101 or the network.

The program does not necessarily have to include an operating system (OS) or third-party program that causes the computer 301 to execute the functions of the information processing device 5, etc., as described in the above embodiment. The program only needs to include the instruction portion that calls appropriate functions (modules) in a controlled manner to obtain the desired result. The operation of the computer system 300 is well known, and a detailed explanation is omitted.

Furthermore, the above program does not include hardware-based processing in steps such as transmitting or receiving information, such as processing performed by modems or interface cards in the transmission step (processing that can only be performed by hardware).

Furthermore, the computer executing the above program may be a single unit or multiple units. That is, it may perform centralized processing or distributed processing. In other words, the information processing device 5 may be a standalone device or may consist of two or more devices.

Furthermore, it goes without saying that in each of the above embodiments, two or more communication means present in a single device may be physically implemented in a single medium.

Furthermore, in each of the above embodiments, each process may be implemented by centralized processing using a single device, or by distributed processing using multiple devices.

The present invention is not limited to the embodiments described above, and various modifications are possible, which are also included within the scope of the present invention.

As described above, the information processing device according to the present invention has the effect of being able to acquire the accurate movement routes of employees and is useful as a server or other component in a corporate system.

1 Expense Inspection Device 2 Applicant Terminal 3 External Server 4 Expense Management Device 5 Information Processing Device 6 Terminal Device 7 Building Entry/Exit Information Acquisition Device 8 Accounting Information Management Device 9 Personnel Information Management Device 11, 51 Storage Unit 12 Reception Unit 13, 53 Processing Unit 14, 54 Output Unit 21 First Storage Unit 22 First Reception Unit 23 First Processing Unit 24 First Transmission Unit 25 First Receiving Unit 26 First Output Unit 52 Receiving Unit 55 Transmission Unit 61 Terminal Storage Unit 62 Terminal Reception Unit 63 Terminal Processing Unit 64 Terminal Transmission Unit 65 Terminal Receiving Unit 66 Terminal Output Unit 71 Card Reader 81 Transportation Expense Database 91 Commuting Expense Database 111 Expense Information Storage Unit 112 Applicant Group Storage Unit 113 Company Regulations Information Storage Unit 114 Restaurant Group Storage Unit 115 Adult Entertainment Establishment Collection Storage Unit 116, Partner Collection Storage Unit 117, Card Usage Expense Storage Unit 118, Means of Transportation Information Storage Unit 121, Expense Reception Units 131, 533, Inspection Unit 132, Statistical Processing Unit 141, Result Output Unit 511, Home Location Storage Unit 512, Work Location Information Storage Unit 513, Regular Information Storage Unit 514, Mobile Information Storage Unit 515, Commuting Route Storage Unit 516, Default Storage Unit 517, Work Information Storage Unit 521, Schedule Reception Unit 522, Actual Reception Unit 530, Change Judgment Unit 531, Schedule Storage Unit 532, Actual Storage Unit 534, Notification Unit 535, Travel Route Acquisition Unit 536, Travel Expense Acquisition Unit 537, Item Determination Unit 538, Re-inspection Unit 539, Re-processing Unit 541, Travel Route Output Unit 542, Travel Expense Output Unit 551 Change transmission unit 1121 Personal information storage unit 1122 Attendance information storage unit 1123 Building entry/exit information storage unit 1124 Sales activity information storage unit 1125 Card statement information storage unit 1126 Company vehicle location information storage unit 1181 Calculation information storage unit 1182 Map information storage unit 1311 Image inspection means 5171 Schedule information storage unit 5172 Actual information storage unit

Claims (11)

A work information storage unit stores scheduled information, which is information about an employee's work schedule and includes location-specific information that identifies the work location, and actual work information, which is information about an employee's actual work and includes location-specific information , in association with one or more employee identifiers. A travel route acquisition unit retrieves location-specific information corresponding to an employee identifier from this storage unit and uses the location-specific information to retrieve travel route information relating to the travel route of the employee identified by that employee identifier .
An inspection department that uses scheduled information and actual information for the same day to check whether the scheduled information and actual information match,
If the inspection results from the aforementioned inspection unit indicate that the results do not match, the notification unit notifies the employee identified by the employee identifier corresponding to the inspection result of information regarding the inspection result.
If the inspection results from the inspection unit indicate that the results do not match, the performance receiving unit receives performance information from the terminal device of the employee who notified the notification unit of the information regarding the inspection results,
A re-inspection unit that determines whether the performance information received by the performance receiving unit satisfies predetermined conditions,
If the result of the judgment by the re-inspection unit does not meet predetermined conditions, the re-inspection unit notifies the employee that the result of the re-inspection was "unsuitable," and if the result of the judgment by the re-inspection unit meets predetermined conditions, the re-inspection unit notifies the employee identified by the employee identifier that the result of the re-inspection was "suitable," or does not notify the employee.
A commuting route storage unit stores commuting route information that identifies commuting routes, associated with one or more employee identifiers. The commuting route storage unit retrieves commuting route information corresponding to an employee identifier, and using the commuting route information and the location identification information contained in the travel route information corresponding to the employee identifier, it determines that travel expenses corresponding to information on the portion of the travel route information that overlaps with the commuting route information correspond to an account related to commuting expenses, and that travel expenses corresponding to information on the portion of the travel route information that does not overlap with the commuting route information correspond to an account related to transportation expenses .
A travel expense acquisition unit acquires travel expenses, which are the travel expenses for the portion of the travel route information that overlaps with the commuting route information, by associating them with the account identification information "commuting expenses," and acquires transportation expenses, which are the travel expenses for the portion of the travel route information that does not overlap with the commuting route information, by associating them with the account identification information "transportation expenses . "
The system comprises a travel expense output unit that, if the result of the judgment in the re-examination unit satisfies predetermined conditions, outputs the commuting expenses acquired by the travel expense acquisition unit in association with the item identification information "commuting expenses", and a travel expense output unit that outputs the travel expenses acquired by the travel expense acquisition unit in association with the item identification information "transportation expenses" ,
The aforementioned predetermined conditions are:
Information processing device wherein the notification unit receives the actual information from the terminal device of the employee who notified the information regarding the inspection result, and the actual information received matches the scheduled information, includes information indicating the reason why the actual information does not match or that there is no problem, or information indicating that it has been approved by a supervisor, includes information with a data volume exceeding a threshold, or the actual information was received within a predetermined time after notifying the employee of an inspection result indicating that it does not match . The aforementioned travel expense output unit is,
The information processing apparatus according to claim 1, wherein the processing is performed so that the transportation expenses acquired by the travel expense acquisition unit are stored in a transportation expense database for managing transportation expenses in association with the aforementioned employees, and the processing is not performed so that the commuting expenses acquired by the travel expense acquisition unit are stored in the transportation expense database. The aforementioned travel expense acquisition unit is:
If the commuter pass information that identifies whether or not a commuter pass is held is the commuter pass information in the commuter pass information storage unit which is stored in association with one or more employee identifiers, and the commuter pass information corresponding to the employee identifier indicates that a commuter pass is held, and the account determination unit determines that the travel expense corresponds to an account related to commuting expenses, then the travel expense information is set to "0" for travel expenses.
The aforementioned travel expense output unit is,
The information processing apparatus according to claim 1 , wherein the commuting expenses acquired by the travel expense acquisition unit are not output in association with the aforementioned subject-specific information "commuting expenses" . The aforementioned travel expense acquisition unit is:
The information processing device according to claim 2 or 3, wherein mobile information that identifies the use of a mobile vehicle for commuting is mobile information in a mobile information storage unit that is stored in association with one or more employee identifiers, the mobile information corresponding to the employee identifier is information indicating that a mobile vehicle is used for commuting, and if the subject determination unit determines that the subject is a subject related to commuting expenses, the said mobile expense information is set to "0" as mobile expense information. The aforementioned travel expense output unit is,
The information processing apparatus according to any one of claims 1 to 4, wherein if the travel expense acquisition unit acquires travel expense information that is not "0", and the item determination unit determines that the item determined is an item related to commuting expenses, the apparatus performs processing to store the travel expense information in a commuting expense database that manages commuting expenses. The aforementioned planned or actual information is,
It has daily information, a first work location identifier that identifies the first work location at the start of work, and a second work location identifier that identifies the second work location at the end of work,
The aforementioned movement path acquisition unit,
From a home location storage unit, which stores home location information that identifies the address of an employee's home or the nearest transportation point to their home, associated with one or more employee identifiers, the home location information corresponding to the employee identifier is obtained. From a work location information storage unit, which stores one or more work location information having a work location identifier and location identification information, first location identification information paired with the first work location identifier corresponding to the employee identifier is obtained. Using the home location information and the first location identification information, first travel route information from home to the work location at the start of work is obtained. From the work location information storage unit, second location identification information paired with the second work location identifier is obtained. Using the first location identification information and the second location identification information, second travel route information from the first work location to the second work location is obtained. Using the second location identification information and the home location information, third travel route information from the second work location to home is obtained.
The subject determination unit said above,
It is determined that the travel expense information corresponding to the first travel route information and the third travel route information corresponds to an account related to commuting expenses, and that the travel expense information corresponding to the second travel route information corresponds to an account related to transportation expenses.
The aforementioned travel expense output unit is,
The information processing device according to claim 1, which outputs the travel expense information in association with subject identification information that identifies the subject determined by the subject determination unit. The aforementioned movement path acquisition unit,
The information processing device according to any one of claims 1 to 6, wherein the mobile information that identifies the use of a mobile vehicle for commuting is mobile information stored in a mobile information storage unit which is associated with one or more employee identifiers, and when the mobile information that identifies the use of a mobile vehicle for commuting is information indicating that a mobile vehicle is used for commuting, the device obtains travel route information that identifies the route of the road from the employee's home to the workplace using one or more types of information from the scheduled information or the actual information, and home location information that identifies the address of the employee's home is home location information stored in a home location storage unit which is associated with one or more employee identifiers, and the home location information that identifies the address of the employee's home. A change determination unit retrieves default schedule information or default performance information corresponding to one or more employee identifiers from a default storage unit where such information is stored, compares the default schedule information or performance information with the schedule information or performance information in the work information storage unit, and determines whether they are different.
The information processing apparatus according to any one of claims 1 to 7, further comprising: a change transmission unit that, when the change determination unit determines that the information is different, transmits change information indicating that the information has been changed from the default information to the contacts indicated by one or more contact pieces of information corresponding to the employee identifier. The aforementioned performance information is,
An information processing device according to any one of claims 1 to 8, wherein the information processing device includes one or more of the following: entry and exit information regarding an employee's entry into and exit from their workplace; sales activity information regarding sales activities; input information entered by an employee in order to perform their work; and employee location information including one or more location information received from a mobile terminal held by an employee. An information processing method in which a computer performs all processing performed by an information processing device according to any one of claims 1 to 9 . Computers,
A program for causing an information processing device to function as described in any one of claims 1 to 9 .