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

Description

The present invention relates to an information processing device that checks the consistency between work schedule information and actual work information.

In the past, there have been various labor management systems. For example, there was a labor management system that forced employees to answer questions about overtime plans, etc. (See, for example, Patent Document 1).

JP 2019-12431 A

However, in conventional technology, it was not possible to obtain an accurate employee's travel route using one or more types of information from among the employee's schedule information and actual performance information.

The information processing device of the first invention is an information processing device that acquires, from a work information storage unit in which schedule information, which is information regarding an employee's work schedule and has location-specific information that identifies a work location and day information that identifies a day, and actual information, which is information regarding an employee's work results and has location-specific information and day information, are stored in association with one or more employee identifiers, schedule information and actual information corresponding to the same day information for each employee identifier, and is equipped with an inspection unit that inspects whether the schedule information and actual information match, and an output unit that outputs information regarding the inspection result in the inspection unit.

This configuration allows you to check the consistency between planned information and actual information and output the inspection results.

The information processing device of the second invention is an information processing device in which the output unit is equipped with a notification unit that notifies an employee identified by an employee identifier corresponding to the test result of information relating to the test result in the testing unit.

This configuration allows you to check the consistency between planned information and actual information and notify employees of the results of the check.

The information processing device of the third invention is an information processing device in which, compared to the second invention, the notification unit is an information processing device that notifies an employee identified by an employee identifier corresponding to the test result of information relating to the test result when the test result in the inspection unit indicates a mismatch.

This configuration allows you to check the consistency between the planned information and the actual information, and if there is a mismatch, notify the employee of that fact.

The information processing device of the fourth invention is an information processing device further including a re-examination unit that determines whether the inspection result of the inspection unit is not consistent with that of the second or third invention, and whether the performance information received from the terminal device of the employee to whom the notification unit notified the information regarding the inspection result satisfies a predetermined condition, and a re-processing unit that performs different processing depending on the judgment result of the re-examination unit.

This configuration allows appropriate processing to be performed if the planned information and actual information do not match.

The information processing device of the fifth invention is an information processing device that, in contrast to the third invention, further includes a performance receiving unit that receives performance information from the terminal device of the employee to whom the notification unit has notified the employee about the inspection result, and a performance accumulation unit that associates the performance information with the employee's employee identifier and accumulates it in the work information storage unit.

This configuration allows appropriate processing to be performed if the planned information and actual information do not match.

The information processing device of the sixth invention is an information processing device according to any one of the first to fifth inventions, in which the performance information is one or more of entry/exit information regarding an employee's entry into and exit from a workplace, sales activity information regarding sales activities, input information input by an employee to perform work, and employee location information including one or more location information received from a mobile terminal held by the employee.

This configuration allows the consistency between the planned information and the actual information to be checked using appropriate actual information.

The information processing device of the present invention can obtain the exact movement route of employees.

Conceptual diagram of information system A in embodiment 1. Block diagram of information system A A block diagram of the expense verification device 1 constituting the information system A. A flowchart illustrating an example of the operation of the expense inspection device 1. A flowchart illustrating an example of the inspection process A flowchart illustrating an example of the statistical inspection process. A flowchart for explaining a processing example of the leakage inspection A diagram showing an example of the output A diagram showing an example of the output FIG. 2 is a block diagram of another system including the expense inspection device 1. Conceptual diagram of information system B in embodiment 2 Block diagram of information system B A block diagram of an information processing device 5 constituting 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 inspection process A flowchart illustrating an example of the process of acquiring the travel route, etc. A flowchart for explaining the process of acquiring the commute route, etc. Flowchart for explaining the process of obtaining routes between workplaces A flowchart for explaining the process of obtaining a route home, etc. A flowchart explaining the process of the re-examination, etc. A flowchart for explaining an example of the operation of the terminal device 6 Overview of the computer system according to the above embodiment. Block diagram of the computer system

Embodiments of an information processing device and the like will be described below with reference to the drawings. Note that components with the same reference numerals in the embodiments perform similar operations, and therefore may not be described again.

(Embodiment 1)
In this embodiment, an information system including an expense inspection device that accepts expense information, inspects for fraud using external information or previously applied expense information, and outputs the inspection results will be described. Note that the external information is information other than expense information, and includes, for example, a set of applicants to be described later, company regulation information to be described later, a set of restaurants to be described later, a set of adult entertainment establishments to be described later, a set of recipients to be described later, card usage expense information to be described later, and transportation information to be described later. In addition, the targets of the inspection for fraud include, for example, business trip expenses, transportation expenses, duplicate applications, inspection of the reuse of receipts, accommodation expenses, and expenditures for after-parties.

In this embodiment, an information system including an expense inspection device is described that performs inspections for fraud using statistical processing results using information corresponding to two or more pieces of expense information, and outputs the inspection results. The statistical processing results are, for example, the frequency of use of a particular store, the frequency of providing benefits to a particular counterparty, and the number of times a particular person commits fraud.

In addition, in this embodiment, we will explain an information system that includes an expense verification device that checks whether the approver of an expense request meets the requirements.

In addition, in this embodiment, an information system including an expense inspection device that inspects receipt images is described. Note that the inspection of receipt images includes, for example, inspection of incomplete information written on the receipt image, inspection of incomplete timestamps on the receipt image, inspection of unclear receipt images, inspection of inappropriate payment methods written on the receipt image, and inspection of forged handwritten amounts on the receipt image.

Furthermore, in this embodiment, we will explain an information system that includes an expense inspection device that uses external information to detect missed claims for expenses that should be claimed.

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

The expense checking device 1 is a device that checks the expense information submitted. The expense checking device 1 is usually a so-called server, such as a cloud server or an ASP server. The type of the expense checking device 1 is not important.

The applicant terminal 2 is a terminal used by the applicant. The applicant is a user who applies for expenses. The applicant terminal 2 may be, for example, a personal computer, a tablet terminal, a smartphone, etc., and the type of device is not important.

The external server 3 stores external information, which will be described later, and is a device that provides the external information to the expense checking device 1. All or part of the external information, which will be described later, may be present in the expense checking device 1. Furthermore, if all of the external information, which will be described later, is present in the expense checking device 1, the external server 3 is not necessary. The external server 3 is typically a so-called server, such as a cloud server, an ASP server, etc. The type of the external server 3 is not important.

The expense verification device 1, the applicant terminal 2, and the external server 3 are typically capable of communicating 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 expense inspection device 1 that constitutes information system A.

The expense inspection device 1 includes 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 regulation 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 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 entrance/exit information storage unit 1123, a business activity information storage unit 1124, a card statement information storage unit 1125, and a business vehicle position information storage unit 1126. The transportation information storage unit 118 includes a calculation information storage unit 1181, and a map information storage unit 1182. The reception unit 12 includes an expense reception unit 121. The processing unit 13 includes 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 includes a first storage unit 21, a first reception unit 22, a first processing unit 23, a first transmission unit 24, a first reception unit 25, and a first output unit 26.

The expense information storage unit 111, applicant group storage unit 112, company regulation 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, and transportation information storage unit 118 in the expense verification device 1 may exist in other external devices.

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

The inspection unit 131 may use various information in the storage unit 11 to perform the inspection process described below, or may use various information stored in the external server 3 or information transmitted from the external server 3 to perform the inspection process described below.

The external server 3 is, for example, a server that receives an inquiry including information identifying a departure station (an example of a departure identifier described later) and information identifying an arrival station (an example of an arrival identifier described later), and outputs one or more travel fares. Such an external server 3 has a calculation information storage unit 1181 that stores fare calculation information described later. In addition, such an external server 3 is a JORDAN (registered trademark) server (URL "https://www.jorudan.co.jp/") or a NAVITIME (registered trademark) server (URL "https://www.navitime.co.jp/").

The external server 3 is, for example, a server that receives an inquiry including a departure identifier and an arrival identifier, and outputs a taxi fare. The external server 3 has a calculation information storage unit 1181 that stores taxi fare calculation information, which will be described later, and a map information storage unit 1182. The external server 3 is also a taxisite server (URL: "https://www.taxisite.com/far/").

Various types of information are stored in the storage unit 11. Examples of such information include expense information, which will be described later, and external information, which will be described later.

Expense information is stored in the expense information storage unit 111. Usually, two or more pieces of expense information are stored in the expense information storage unit 111. Expense information is information that specifies the contents of the expense that has been applied for. Expense information includes, for example, expenditure amount information, destination identifier, store identifier, other party identifier, use date information, payment method identifier, subject, summary, and approver identifier. Expenditure amount information is information that specifies the amount used as an expense. The destination identifier is information that indicates the destination of the receipt and is information that identifies the company or the like that pays the amount. The store identifier is information that identifies the store that used the expense. The store identifier is, for example, the store name, store ID, store URL, and store telephone number. The other party identifier is information that identifies the other party that used the expense. The other party identifier is information that identifies the other party to whom a benefit such as entertainment or a gift was provided. The other party identifier is, for example, the organization name (for example, company name, organization name), name, and other party ID. Use date information is information that specifies the date on which the expense was used. The payment method identifier is information that identifies the payment method. The payment method identifier is, for example, "cash," "credit card," "electronic money," "XX PAY," etc. The item is information that specifies the classification of the expense. The item may be called an expense type identifier. The item is, for example, business trip expenses, travel expenses (or transportation expenses), accommodation expenses, business trip expenses, entertainment expenses, and conference expenses. The approver identifier is information that identifies the approver of the expenses. The approver identifier is, for example, an applicant identifier or a position identifier. The applicant identifier is information that identifies the applicant who applied for the expenses, such as a name or ID. The position identifier is information that identifies a position, such as a position name (for example, "department manager" or "director") or an ID. The expense information in the expense information storage unit 111 is usually associated with an applicant identifier.

If the expense information is information on transportation expenses, the expense information includes, for example, transportation expense information including date of use information and one or more section information including a departure identifier, an arrival identifier, and fare information. It is preferable that the expense information includes an expense type identifier indicating transportation expenses. If the expense information is information on business trip expenses, the expense information includes, for example, date of use information. It is preferable that the expense information includes an expense type identifier indicating business trip expenses. If the expense information is information on accommodation expenses, the expense information includes, for example, date of use information specifying the date of stay at an accommodation facility. If the expense information is entertainment expenses or meeting expenses, the expense information is, for example, associated with an applicant identifier, and includes date of use information and a store identifier identifying the store where the expenses were spent.

The expense information may include a receipt image. The receipt image is an image of a receipt. The receipt image is, for example, an image obtained by photographing a receipt. It goes without saying that the data structure of the receipt image is not important, such as JPEG, GIF, etc.

Expense information includes, for example, participant information and number of people information. Participant information is information (e.g., name) that identifies those who participated in the use of expenses (e.g., those who ate and drank). Number of people information is the number of people who participated in the use of expenses.

The applicant set storage unit 112 stores an applicant set. The applicant set is information unique to each applicant that corresponds to each applicant. The applicant set is, for example, a set of personal information described below, a set of attendance information described below, a set of entrance and exit information described below, a set of business activity information described below, a set of card statement information described below, or a set of business vehicle location information described below.

The personal information storage unit 1121 stores one or more pieces of personal information. The personal information is information about the applicant. An applicant identifier is associated with the personal information. The personal information includes, for example, the applicant's name, the name of the company to which the applicant belongs, the company ID, the name of the department to which the applicant belongs, the department ID, a job title identifier that identifies the position, regular period information that identifies the period of the applicant's regular period, the number of fraudulent incidents, and an email address. The number of fraudulent incidents is the number of times the applicant has submitted a fraudulent expense claim, or the number of times the applicant's fraud has been detected. The email address is any information that identifies the destination to which information is sent, and may be a SNS ID, etc., and is broadly understood.

In addition, two pieces of information correspond to each other if the other piece of information can be obtained from the first piece of information. For example, the first piece of information and the other piece of information are linked, the first piece of information and the other piece of information are stored in the same buffer, the first piece of information contains the other piece of information, etc.

The attendance information storage unit 1122 stores one or more pieces of attendance information. The attendance information is information related to the attendance of the applicant. The attendance information is usually associated with an applicant identifier. The attendance information includes work day information. The work day information is information for identifying the days on which the applicant identified by the corresponding applicant identifier worked. The work day information is usually information indicating work days, but may be information indicating non-work days. If the work day information is information indicating non-work days, days other than the days indicated by the work day information are work days. The attendance information usually has work time information that identifies the time worked. The work time information has, for example, a work start time and a work end time. 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 the attendance of employees, and is a device related to publicly known technology, so a detailed description will be omitted.

The entrance/exit information storage unit 1123 stores one or more pieces of entrance/exit information. The entrance/exit information is information related to the entrance/exit of the applicant. The entrance/exit refers to the entry to the applicant's place of work (which may also be called the place of work) and the exit from the place of work. The entrance/exit information may also be said to be coming to the office to start work on a work day, and the exit to leave the office after work ends on a work day. The entrance/exit information is usually associated with the applicant identifier. The entrance/exit information includes, for example, work day information and work time information. The work time information includes, for example, the start time and end time of work. The work time information includes, for example, information that specifies the time worked. The entrance/exit information is information that is configured by punching a time card and inputting the arrival or departure of the work to the entrance/exit system. The entrance/exit information may be the same as the attendance information. The entrance/exit information in the entrance/exit information storage unit 1123 is, for example, information received from an external server 3 (entrance/exit management server). The entrance/exit management server (entrance/exit management system) is a device related to publicly known technology, so a detailed explanation will be omitted.

The sales activity information storage unit 1124 stores one or more pieces of sales activity information. The sales activity information is information related to sales activities. The sales activity information is, for example, information on business day reports. The sales activity information is usually associated with an applicant identifier. The sales activity information includes business day information and one or more location identifiers. The sales activity information may include a character string indicating the content of the sales activity. The business day information is information that identifies the day of the applicant's sales activity. The location identifier is information that identifies the location visited. The location identifier is, 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 important.

The card statement information storage unit 1125 stores one or more pieces of card statement information. The card statement information is information showing the details of the credit card used by the applicant. The card statement information is usually associated with an applicant identifier. The card statement information includes, for example, usage date information, a payee identifier (for example, a store identifier) that identifies the payee, amount information, and a card identifier. The card identifier is information that identifies the card, such as a 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 business vehicle position information storage unit 1126 stores one or more pieces of business vehicle position information. The business vehicle position information is information that specifies the position of a business vehicle used by the applicant. The business vehicle position information is usually associated with an applicant identifier. The business vehicle position information is associated with usage date information that specifies the day the business vehicle was used. The business vehicle position information is, for example, (latitude, longitude), but may also be a location identifier. The business vehicle position information is, for example, associated with a business vehicle identifier that identifies the business vehicle.

Company regulation information is stored in the company regulation information storage unit 113. Company regulation information is information that indicates company regulations. Company regulation information is information about the regulations of the company to which the applicant belongs. Company regulation information includes, for example, overtime time information, one or more approver information, and one or more payment method information.

Overtime information is information that specifies the overtime hours during which overnight stays are permitted. Examples of overtime information include "11pm" and "after midnight."

The approver information is information that identifies the potential approver of the expense. The approver information is, for example, an approver identifier that identifies the approver (e.g., applicant identifier, name), and a position identifier that identifies the approver's position (e.g., "department manager" or "director").

Payment method information is information that specifies unacceptable payment methods. Examples of payment method information are "○○ PAY", "electronic money", and "credit card".

The restaurant set storage unit 114 stores a restaurant set. A restaurant set has one or more pieces of restaurant information. Restaurant information is information about restaurants. Restaurant information has, for example, a restaurant identifier that identifies the restaurant and price information. Restaurant information may also have address information, telephone number information, etc. The restaurant identifier is, for example, the restaurant name or ID. Price information is, for example, information that specifies an appropriate amount to spend at a restaurant. Price information is, for example, information about the amount spent by one person at the restaurant. Price information is, for example, information indicating the average amount spent by one person at the restaurant. Price information may be, for example, information that specifies the upper limit of the amount spent by one person at the restaurant. Price information may be, for example, information that specifies the upper limit of the amount to spend in one session, etc.

The adult entertainment establishment set storage unit 115 stores an adult entertainment establishment set. The adult entertainment establishment set has one or more pieces of adult entertainment establishment information. The adult entertainment establishment information has, for example, an adult entertainment establishment identifier that identifies the adult entertainment establishment. The adult entertainment establishment information may also have price information, address information, telephone number information, etc. The adult entertainment establishment information is, for example, information that specifies establishments that the applicant may not visit.

The recipient set storage unit 116 stores a recipient set. The recipient set has one or more pieces of recipient information. The recipient information has, for example, a recipient identifier and an affiliation identifier that identifies the recipient's affiliation. The recipient information is, for example, information on a civil servant. The recipient information is, for example, information on a member of parliament. The recipient information is, for example, information that specifies persons to whom the applicant must not provide benefits. The provision of benefits is, for example, the act of entertaining or giving a gift.

The card usage expense storage unit 117 stores one or more expense type identifiers for which payment is planned by card. The expense type identifier may correspond to a card type identifier. The card type identifier is information that identifies the type of card. Examples of the card type identifier are "EX-IC card" and "corporate card." Examples of the expense type identifier are "Shinkansen" indicating the fare for the Shinkansen, and "entertainment expenses."

The transportation information storage unit 118 stores transportation information. The transportation information is information for calculating transportation costs when using transportation such as a train, bus, airplane, or taxi. The transportation information includes calculation information, which will be described later. The transportation information includes, for example, map information, which will be described later.

The calculation information storage unit 1181 stores calculation information. The calculation information is, for example, fare calculation information and taxi fare calculation information. The fare calculation information is, for example, information for calculating the fare for a means of transportation such as a train, bus, or airplane. The fare calculation information is, for example, information having one or more pairs of a departure identifier, an arrival identifier, and fare information. The departure identifier and the arrival identifier are, for example, a station name, an airport name, a bus stop name, a station ID, an airport ID, and a bus stop ID. The taxi fare calculation information is information for calculating a taxi fare. The taxi fare calculation information is, for example, an arithmetic formula for calculating a taxi fare using a distance as an input. The taxi fare calculation information is, for example, information having one or more pairs of a distance and a taxi fare.

Map information is stored in the map information storage unit 1182. The map information is, for example, information about a map used for navigation. The map information is, for example, information in the KIWI format.

The reception unit 12 receives various types of information and instructions. Here, reception usually refers to receiving information from a terminal such as the applicant terminal 2. However, reception may also be a concept that includes the reception of information input from an input device such as a keyboard, mouse, or touch panel, or the reception of information read from a recording medium such as an optical disk, magnetic disk, or semiconductor memory.

The expense acceptance unit 121 accepts one or more pieces of expense information. The expense acceptance unit 121 usually accepts expense information in association with an applicant identifier. The expense acceptance unit 121 accepts, for example, expense information and an applicant identifier. The expense acceptance unit 121 may accept, for example, one or more pieces of expense information for each of one or more applicants. The expense information is accepted, for example, from an applicant terminal, but may also be accepted from an administrator terminal (not shown), may be read from a recording medium, or may be accepted as input by the applicant.

It is preferable for the expense acceptance unit 121 to accept expense information having a receipt image. The expense acceptance unit 121 may accept the receipt image and information other than the receipt image that constitutes the expense information separately. However, the receipt image and the information other than the receipt image are accepted so as to correspond to each other.

The processing unit 13 performs various types of processing. For example, various types of processing are performed by the inspection unit 131 and the statistical processing unit 132.

The inspection unit 131 inspects the expense information received by the expense reception unit 121 for fraud and obtains the inspection result. The inspection unit 131 may inspect the expense information stored in the expense information storage unit 111 for fraud and obtain the inspection result. The expense information stored in the expense information storage unit 111 is the expense information received by the expense reception unit 121. The inspection result is information related to the result of the inspection of the expense information. The inspection result includes, for example, information indicating whether it is fraudulent or not. The inspection result includes, for example, part or all of the fraudulent expense information. The inspection result is, for example, information indicating that it is not fraudulent (that it is legitimate). The inspection result includes, for example, one or more pieces of information among an expense information identifier, an applicant identifier, an expense type identifier, amount information, an inspection content identifier, and an application date. The expense information identifier is information that identifies the expense information, and is, 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 below. Examples of the examination content identifiers are "expenses for days other than work days," "unauthorized travel expenses," "unauthorized accommodation expenses," "accommodation expenses for days when accommodation is not permitted," "unauthorized transportation expenses," and "split receipts." Note that the contents of the examination content identifier and the data structure are not important.

The inspection unit 131, for example, uses external information to inspect the expense information accepted by the expense acceptance unit 121 for fraud and obtains the inspection results. External information is 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 in the external server 3.

The inspection unit 131, for example, uses expense information other than the expense information accepted by the expense acceptance unit 121 to inspect the expense information accepted by the expense acceptance unit 121 for fraud and obtains the inspection result. The expense information other than the expense information accepted by the expense acceptance unit 121 is, for example, expense information stored in the expense information storage unit 111, but may also be expense information stored in the external server 3.

The inspection unit 131, for example, obtains applicant information associated with an applicant identifier associated with the expense information accepted by the expense acceptance unit 121 from the applicant set, and uses the applicant information to inspect the expense information accepted by the expense acceptance unit 121 for fraud and obtains the inspection results. The applicant set is, for example, information stored in the applicant set storage unit 112, but may also be information stored in an external device (not shown). The applicant information is information associated with an applicant identifier, and is, for example, attendance information, entrance and exit information, business activity information, card statement information, and business vehicle location information.

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

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

In this specification, any algorithm may be used in the machine learning process. Examples of machine learning include deep learning, decision trees, random forests, SVM, and SVR. Examples of modules used in machine learning include TensorFlow modules and TinySVM.
(1) Character recognition processing method

The image inspection means 1311, for example, performs character recognition processing on a receipt image to obtain one or more character strings. The process of performing character recognition processing and obtaining information constituting expense information from a receipt image is a publicly known technique. The image inspection means 1311 determines whether the obtained character string is payment amount information, store identifier, recipient identifier, date of use information, subject, summary, or payment method information, and obtains the character string by associating it with information that identifies the type of information (which may also be called a class, category, etc.). The technique for determining the class of the obtained character string is an information classification problem (clustering problem), and is a publicly known technique.

The image inspection means 1311, for example, configures a learning device that performs a machine learning learning process for each class, with two or more character strings that belong to each class as positive examples and one or more character strings that do not belong to the class as negative examples, thereby performing a binary classification of whether or not the character string belongs to a class. The image inspection means 1311 then performs a machine learning prediction process using two or more learning devices for each of one or more character strings obtained from the receipt image, obtains prediction results and scores for each class, and determines the class with the highest class-belonging score as the class to which the character string belongs.

The image inspection means 1311 also performs a learning process using teacher data having two or more pairs of character strings and classes, and configures a single learning device that performs multi-value classification to output a class. Next, the image inspection means 1311 uses a learning device to perform machine learning prediction processing for each of one or more character strings obtained from the receipt image, and determines the class to which each character string belongs.

The image inspection means 1311, for example, uses a large amount of training data, which is a pair of character strings and classes, to obtain a learning device for classifying character strings by using a module that performs learning processing in a machine learning algorithm.
(2) Machine learning processing method

The image inspection means 1311 performs a learning process using a machine learning algorithm using, for example, a receipt image and two or more pieces of training data each having one or more pairs of a character string and a class, to obtain a learning device. Note that this learning device is a learning device that receives a receipt image as input and outputs one or more pairs of a character string and a class.

Next, the image inspection means 1311 provides the acquired learning device and the receipt image contained in the expense information accepted by the expense acceptance unit 121 to a module that performs prediction processing in the machine learning algorithm, and acquires one or more pairs of strings and classes.
(3) Method using both character recognition and machine learning

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

In addition, using one or more character strings obtained by any of the above methods (1) to (3), the image inspection means 1311 determines whether each of the one or more character strings satisfies a predetermined condition and obtains an image inspection result. The one or more character strings are, for example, any of payment amount information, store identifier, other party identifier, use date information, item, summary, and payment method information.

The image inspection means 1311 performs a learning process using a machine learning algorithm with training data having, for example, negative examples that are one or more fraudulent receipt images and positive examples that are one or more legitimate receipt images, to configure a learning device. Next, the image inspection means 1311 provides the receipt image contained in the expense information accepted by the expense acceptance unit 121 and the learning device to a module that performs machine learning prediction processing, performs prediction processing, and obtains a prediction result of whether or not it is fraudulent. The learning device is, for example, a learning device for detecting fraudulent manipulation of the amount in the receipt, a learning device for inspecting whether or not the receipt has been signed, and a learning device for detecting a blurred receipt image. The learning device is usually a learning device for binary classification of whether or not it is fraudulent.

The statistical processing unit 132 performs statistical processing based on one or more pieces of expense information stored in the expense information storage unit 111, which is one or more pieces of expense information associated with an applicant identifier that corresponds to the accepted expense information, and obtains the statistical processing results. For example, for each applicant identifier, the statistical processing unit 132 performs statistical processing based on one or more pieces of expense information associated with the applicant identifier and stored in the expense information storage unit, and obtains the statistical processing results. Note that the statistical processing unit 132 may perform statistical processing at any time. For example, the statistical processing unit 132 performs statistical processing upon receipt of a user instruction. For example, the statistical processing unit 132 performs statistical processing upon receipt of expense information.

The statistical processing unit 132 acquires store frequency information, for example, using a store identifier included in two or more pieces of expense information stored in the expense information storage unit 111 and corresponding to one applicant identifier. Store frequency information is information relating to the frequency of use of a store identified by one store identifier. Store frequency information is information indicating the frequency of use. Store frequency information is, for example, information indicating the total number of times used, or information indicating the number of times used in a unit period. The unit period is, for example, one month, six months, or one year. It is preferable for the statistical processing unit 132 to acquire store frequency information for each applicant identifier.

The statistical processing unit 132 acquires entertainment frequency information using a party identifier included in two or more pieces of expense information stored in the expense information storage unit 111 and corresponding to one applicant identifier. Entertainment frequency information is information related to the frequency of expenditures to a party identified by one party identifier. Expenditures to a party are payments for the provision of benefits to the party, such as payments for entertainment to the party or payments for gifts to the party. Entertainment frequency information is information indicating the frequency of the provision of benefits. Entertainment frequency information is, for example, information indicating the total number of times benefits have been provided, or information indicating the number of times benefits have been provided in a unit period. It is preferable for the statistical processing unit 132 to acquire entertainment frequency information for each applicant identifier.

The statistical processing unit 132 obtains the number of fraudulent incidents, which is the number of times that a review result corresponding to fraud was obtained, in association with one applicant identifier, as the review result for expense information corresponding to one applicant identifier. It is preferable for the statistical processing unit 132 to obtain the number of fraudulent incidents for each applicant identifier.

The result output unit 141 outputs the inspection results acquired by the inspection unit 131. The result output unit 141 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. The result output unit 141 outputs the statistical processing results in association with, for example, an applicant identifier.

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

The first reception unit 22 receives various instructions and information. The various instructions and information are, for example, expense information and response information. Response information is information that indicates a response to the test results.

The first processing unit 23 performs various types of processing. For example, various types of processing are processing to convert instructions and information accepted by the first accepting unit 22 into instructions and information with a data structure to be transmitted. For example, various types of processing are processing to convert information received by the first receiving unit 25 into information with a data structure to be output.

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

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

The first output unit 26 outputs various information. The various information is, for example, test results and image test results.

Here, output is a concept that includes display on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and handing over the processing results to other processing devices or other programs, etc.
(Specific example of inspection process)

Specific examples of inspections performed by the inspection unit 131 are described below. Note that, in the following, cases where there is fraud are mainly described, but in cases where there is no fraud, the inspection unit 131 normally obtains an inspection result indicating that the information is "legitimate." In addition, in cases where the information is legitimate, the inspection unit 131 normally associates the expense information to be inspected 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 character string accepted by the expense accepting unit 121, or may be information acquired from a receipt image accepted by the expense accepting unit 121. The character string accepted by the expense accepting unit 121 is, for example, information input by the applicant.
(1) Inspection using attendance information

The inspection unit 131 acquires, from the attendance information storage unit 1122, attendance information that is associated with an applicant identifier associated with the expense information accepted by the expense accepting unit 121 and that includes work date information that is the same as the use date information included in the expense information accepted by the expense accepting unit 121. Next, the inspection unit 131 uses the attendance information to inspect the expense information accepted by the expense accepting unit 121 for fraud and acquires the inspection result.
(1-1) Inspection of expenses other than on working days

The inspection unit 131 acquires, from the attendance information storage unit 1122, attendance information that is associated with an applicant identifier associated with the expense information accepted by the expense accepting unit 121, and that includes work day information that is the same as the use date information included in the expense information accepted by the expense accepting unit 121, for example. Next, the inspection unit 131 determines whether the attendance information is information for a day that is not a work day. If the information is information for a day that is not a work day, the inspection unit 131 acquires an inspection result indicating that the expense is an "illegal expense for a day that is not a work day." Note that the inspection unit 131 determines that the attendance information is information for a day that is not a work day because the attendance information includes "information indicating that it is a holiday" or does not include a work start time and a work end time, etc.
(1-2) Inspection of fraudulent travel expenses

The inspection unit 131 acquires an applicant identifier and date of use information associated with the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 acquires attendance information corresponding to the acquired applicant identifier and date of use information from the attendance information storage unit 1122. Next, if the inspection unit 131 determines that the acquired attendance information is not information indicating a business trip, it acquires an inspection result indicating "fake business trip fraud." Note that examples of "attendance information is not information indicating a business trip" include (a) when the attendance information does not contain information indicating a "business trip" and (b) when the attendance information contains information on the start time and end time of work.
(1-3) Inspection of hotel fee fraud

The inspection unit 131 acquires an applicant identifier and use date information associated with the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 acquires working hours information from the work day information corresponding to the acquired applicant identifier and use date information. Next, the inspection unit 131 uses the acquired working hours information to determine whether or not the stay at the accommodation facility is permitted, and acquires an inspection result.

More specifically, the inspection unit 131 compares the work end time included in the working time information with overtime information indicating the overtime hours during which overnight stays are permitted, and determines whether or not a predetermined overnight stay condition is satisfied. If the inspection unit 131 determines that the overnight stay condition is not satisfied, it acquires an inspection result indicating that "there is a fraudulent claim for accommodation fees." The overnight stay condition is a condition that uses the overtime time information and the work end time, and is, for example, "overtime time information = < work end time" or "overtime time information < work end time."
(2) Inspection using entrance and exit records

The inspection unit 131 obtains entrance/exit information corresponding to the applicant identifier associated with the expense information from the entrance/exit information storage unit 1123, which corresponds to the date specified by the use date information contained in the expense information, and uses the entrance/exit information to inspect the expense information accepted by the expense acceptance unit 121 for fraud and obtains the inspection results.
(2-1) Inspection of expenses other than on working days

The inspection unit 131 acquires an applicant identifier and date of use information associated with the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 performs a process of acquiring entrance/exit information corresponding to the acquired applicant identifier and date of use information from the entrance/exit information storage unit 1123. Next, the inspection unit 131 judges whether the entrance/exit information is information on a day that is not a workday. If the information is information on a day that is not a workday, the inspection unit 131 acquires an inspection result indicating that the information is "unauthorized expenses on a day that is not a workday." Note that the inspection unit 131 judges that the entrance/exit information is information on a day that is not a workday because the entrance/exit information includes "information indicating that it is a holiday" or does not include a work start time and a work end time, etc.
(2-2) Inspection of fraudulent travel expenses

The inspection unit 131 acquires the applicant identifier and the date of use information associated with the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 performs a process of acquiring the entrance/exit information corresponding to the acquired applicant identifier and the date of use information from the entrance/exit information storage unit 1123. Next, if the inspection unit 131 determines that the result of the entrance/exit information acquisition process is not information indicating a business trip, it acquires an inspection result indicating "fake business trip fraud." Note that, for example, cases where "the result of the entrance/exit information acquisition process is not information indicating a business trip" include (a) when the entrance/exit information can be acquired, and (b) when the work start time and work end time information contained in the acquired entrance/exit information are work start time information and work end time information of normal work. Note that the work start time information and work end time information of normal work are stored, for example, in company-defined information.
(2-3) Inspection of hotel fee fraud

The inspection unit 131 acquires the applicant identifier and use date information associated with the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 acquires the end time of work from the entrance/exit information corresponding to the acquired applicant identifier and use date information. Next, the inspection unit 131 uses the acquired end time of work to determine whether or not the stay at the accommodation facility is permitted, and acquires the inspection result.

More specifically, the inspection unit 131 compares the end time of work with overtime information indicating the overtime hours during which overnight stays are permitted, and determines whether or not the predetermined overnight stay conditions are met. If the inspection unit 131 determines that the overnight stay conditions are not met, it obtains an inspection result indicating that "there is a fraudulent claim for accommodation fees." The overtime work information is stored, for example, in company-defined 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 contained in the sales activity information which is associated with an applicant identifier associated with the expense information accepted by the expense acceptance unit 121 and has business day information which is the same as the date of use information contained in the expense information, and uses the one or more location identifiers to inspect the expense information accepted by the expense acceptance unit 121 for fraud and obtains the inspection results.
(3-1) Inspection of transportation expense fraud (i)

The inspection unit 131 provides the information indicating the company's location and one or more location identifiers contained in the sales activity information to the travel expense calculation module, and obtains one or more travel expenses using the calculation information for calculating travel expenses. It is preferable that the travel expenses obtained here are the lowest travel expenses. Furthermore, obtaining two or more travel expenses is performed when there are two or more travel routes. Furthermore, the technology for obtaining travel expenses and the technology for obtaining the lowest travel expenses are publicly known technologies, so detailed explanations are omitted. 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 information and the acquired transportation expenses to determine whether the expenditure information satisfies a predetermined condition for legitimate transportation expenses. If the condition for legitimate transportation expenses is not met, the inspection unit 131 obtains an inspection result indicating that the transportation expense claim is fraudulent. Note that the conditions for legitimate transportation expenses are, for example, "expense information = lowest transportation expense,""expense information matches one or more transportation expenses," and "expense information <= one or more transportation expenses."
(3-2) Inspection of transportation expense fraud (ii)

The inspection unit 131 acquires travel expense information having a departure identifier and an arrival identifier from the expense information accepted by the expense acceptance unit 121. The inspection unit 131 also acquires one or more location identifiers from the sales 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 satisfy a predetermined condition. If the distance between the departure identifier and all of the location identifiers does not satisfy the predetermined condition, the inspection unit 131 acquires an inspection result indicating that the travel expense claim is fraudulent. The inspection unit 131 determines whether the distance between the arrival identifier and any of the location identifiers is close enough to satisfy a predetermined condition. If the distance between the arrival identifier and all of the location identifiers does not satisfy the predetermined condition, the inspection unit 131 acquires an inspection result indicating that the travel expense claim is fraudulent.

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

The inspection unit 131 obtains card statement information corresponding to an applicant identifier associated with the expense information accepted by the expense acceptance unit 121 from the card statement information storage unit 1125, which has the same date of use information as the date of use information contained in the expense information, and uses the card statement information to inspect the expense information accepted by the expense acceptance unit 121 for fraud and obtains the inspection results.
(4-1) Inspection of split receipts

The inspection unit 131 obtains card statement information that is associated with the applicant identifier associated with the expense information accepted by the expense acceptance unit 121 and that has the same date of use information as the date of use information contained in the expense information from the card statement information storage unit 1125. If the inspection unit 131 determines that it is possible to obtain two or more pieces of card statement information and that the store identifiers contained in each of the two or more pieces of card statement information are the same, it obtains an inspection result indicating that "receipt division is fraudulent."
(4-2) Inspection of taxi use after company drinking parties

The inspection unit 131 acquires card statement information associated with the applicant identifier associated with the expense information accepted by the expense acceptance unit 121. The inspection unit 131 also uses information contained in the card statement information to determine whether or not the expense is for using a taxi. If the expense is for using a taxi, the inspection unit 131 acquires one or more pieces of participant information (e.g., the names of the participants) contained in the expense information that includes the same date of use information as the date of use information contained in the card statement information. Next, the inspection unit 131 determines whether or not all of the one or more pieces of participant information correspond to personal information contained in the personal information storage unit 1121 (employee database) (e.g., whether or not the names of the participants are included). If all of the one or more pieces of participant information correspond to personal information, the inspection unit 131 acquires an inspection result indicating that the expense is "using a taxi after an in-house drinking party."
(5) Inspection using commercial vehicle location information

The inspection unit 131 obtains, from the business vehicle location information storage unit 1126, one or more pieces of business vehicle location information that are associated with an applicant identifier that is associated with the expense information accepted by the expense acceptance unit 121 and that is associated with the same use date information as the use date information contained in the expense information. Next, the inspection unit 131 uses the business vehicle location information to inspect the expense information for fraud and obtains the inspection result.
(5-1) Inspection of unauthorized use of company vehicles (inspection of unauthorized locations)

The inspection unit 131 judges whether the one or more pieces of acquired commercial vehicle position information are close enough to a predetermined fraudulent location (e.g., a tourist spot) to satisfy a predetermined condition. If it is judged that the location information is close enough to satisfy the predetermined condition, the inspection unit 131 acquires an inspection result indicating that the use of a commercial vehicle is fraudulent. Note that the information on the predetermined fraudulent location is included in, for example, company-defined information.
(6) Inspection using card usage expense information

The inspection unit 131 inspects whether or not an expense type identifier corresponding to the expense information accepted by the expense acceptance unit 121 is stored in the card usage expense storage unit 117 as an expense type identifier corresponding to the owned card information corresponding to the applicant identifier associated with the expense information accepted by the expense acceptance unit 121, and acquires the inspection result. It is assumed that, for example, the card usage expense storage unit 117 stores information indicating that a credit card is used for dining expenses or entertainment expenses.
(7) Inspection using company-defined information

The inspection unit 131 uses the company specification information stored in the company specification information storage unit 113 to inspect whether the expense information accepted by the expense acceptance unit 121 matches the company specification specified by the company specification information, and obtains the inspection result. Specific examples of inspections using the company specification 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 transportation information

The inspection unit 131 inspects for fraudulent travel expenses using the expense information accepted by the expense acceptance unit 121 and the transportation information stored in the transportation information storage unit 118, and obtains the inspection results.
(8-1) Examination of train, bus, or airplane travel fare fraud

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

More specifically, the inspection unit 131 acquires transportation cost information having one or more section information having a departure identifier, an arrival identifier, and fare information from the expense information accepted by the expense acceptance unit 121. Next, the departure identifier and the arrival identifier of each of the one or more section information are provided to a transportation cost calculation module, and one or more transportation costs are acquired using the calculation information for calculating the transportation costs. It is preferable that the transportation cost acquired here is the lowest transportation cost. In addition, two or more transportation costs are acquired when there are two or more travel routes. In addition, the technology for acquiring transportation costs and the technology for acquiring the lowest transportation cost are publicly known technologies, so detailed explanations are omitted. It is also preferable that the transportation costs are acquired using an external server 3.

The inspection unit 131 also obtains expenditure amount information from the expense information accepted by the expense acceptance unit 121.

Next, the inspection unit 131 uses the fee information and the transportation expenses to determine whether the fee information satisfies a predetermined condition for legitimate transportation expenses. If the condition for legitimate transportation expenses is not met, the inspection unit 131 obtains an inspection result indicating that the transportation expenses claim is fraudulent. Note that the conditions for legitimate transportation expenses are, for example, "fee information = lowest transportation expenses,""fee information matches one or more transportation expenses," and "fee information <= one or more transportation expenses."
(8-2) Inspection of taxi fare fraud

The inspection unit 131 obtains applicant information associated with the applicant identifier associated with the expense information related to taxi fares received by the expense reception unit 121, and performs an inspection for fraud related to the claim of transportation expenses using the applicant information or the applicant information and the means of transportation information, and obtains the inspection results.

More specifically, the inspection unit 131 acquires transportation expense information having a departure identifier, an arrival identifier, and expenditure amount information from the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 acquires the distance traveled using the departure identifier, arrival identifier, and map information contained in the transportation expense information. Next, the inspection unit 131 acquires the taxi fare using the distance and calculation information for calculating the taxi fare. Note that the technology for acquiring the taxi fare is publicly known, so a detailed explanation is omitted here. Also, it is preferable to acquire the taxi fare using an external server 3.

The inspection unit 131 also obtains expenditure amount information from the expense information accepted by the expense acceptance unit 121.

Next, the inspection unit 131 uses the expenditure information and the taxi fare to determine whether or not the expenditure information satisfies a predetermined condition for a legitimate taxi fare. If the condition for a legitimate taxi fare is not met, the inspection unit 131 obtains an inspection result indicating that the travel expense claim is fraudulent. Note that the conditions for a legitimate travel expense are, for example, "expense information = taxi fare,""expense information - taxi fare <= threshold," and "expense information - taxi fare <threshold."
(8-3) Inspection for overlap with regular service sections

The inspection unit 131 obtains, from the personal information storage unit 1121, regular route information associated with the applicant identifier associated with the expense information related to transportation expenses received by the expense reception unit 121. Next, the inspection unit 131 obtains transportation expense information having one or more route information having a departure identifier and an arrival identifier from the expense information received by the expense reception unit 121.

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

The inspection unit 131 inspects the expense information for fraud using the store identifier contained in the expense information accepted by the expense acceptance unit 121 and the store information contained in the store set, and obtains the inspection result. Note that the store set is, for example, a restaurant set in the restaurant set storage unit 114 or a restaurant set in the adult entertainment establishment set storage unit 115, but may also be a restaurant set or adult entertainment establishment set present in an external device (not shown).
(9-1) Inspection of store fraud (use of adult entertainment establishments, etc.)

For example, inspection unit 131 obtains a shop identifier contained in the expense information accepted by expense acceptance unit 121. Next, inspection unit 131 checks whether the obtained shop identifier (adult entertainment establishment identifier) is stored in adult entertainment establishment collection storage unit 115, and if it is stored, obtains an inspection result indicating "fraudulent use of expenses at an adult entertainment establishment that should not be visited." Note that such inspection result preferably includes adult entertainment establishment information including the shop identifier in adult entertainment establishment collection storage unit 115.
(9-2) Inspection of monetary irregularities (a) Inspection of the total amount

For example, the inspection unit 131 obtains amount information paired with a store identifier included in the expense information received by the expense receiving unit 121 from the restaurant collection storage unit 114. Next, the inspection unit 131 obtains, for example, expenditure amount information included in the expense information received by the expense receiving unit 121. Next, the inspection unit 131 compares the obtained expenditure amount information with the obtained amount information to determine whether the information indicates an amount high enough to satisfy a predetermined condition. Then, when the information indicates an amount high enough to satisfy a predetermined condition, the inspection unit 131 obtains an inspection result indicating that "an illegal amount of expenses was used." Note that the predetermined condition is, 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." Note that it goes without saying that each threshold may be different.
(9-3) Inspection of whether entertainment expenses were used at restaurants

The inspection unit 131, for example, obtains the expense type identifier of the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 judges whether or not the expense type identifier corresponds to "entertainment expenses". If it corresponds to "entertainment expenses", the inspection unit 131 obtains a store identifier contained in the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 judges whether or not the store identifier is an identifier for a restaurant. If it is not an identifier for a restaurant, the inspection unit 131 obtains an inspection result indicating that "this is a fraudulent entertainment expense claim."

The inspection unit 131 determines whether the store identifier is an identifier for a restaurant, for example, based on whether the store identifier is stored in the restaurant set storage unit 114. The inspection unit 131 also performs a web search using the store identifier as a key, for example, and determines whether the store identifier is an identifier for a restaurant based on whether information indicating a restaurant (for example, izakaya, Italian, dish name, etc.) is present on the acquired web page. Other methods may be used for clustering store identifiers. In other words, any algorithm may be used to determine whether the store identifier is an identifier for a restaurant.
(b) Examination of per capita amounts

The inspection unit 131, for example, obtains amount information paired with a store identifier contained in the expense information accepted by the expense accepting unit 121 from the restaurant group storage unit 114. Next, the inspection unit 131, for example, obtains expenditure amount information contained in the expense information accepted by the expense accepting unit 121. The inspection unit 131 also obtains, for example, number of people information contained in the expense information accepted by the expense accepting unit 121, or number of people information obtained from participant information contained in the expense information. Next, the inspection unit 131 uses the obtained expenditure amount information and the obtained amount information and number of people information to determine whether the amount per person is high enough to satisfy a predetermined condition. Then, if the amount per person is high enough to satisfy the predetermined condition, the inspection unit 131 obtains an inspection result indicating that "an illegal amount of 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 may be different.
(10) Inspection using counterparty information

The inspection unit 131 inspects the expense information for fraud using the destination identifier included in the expense information accepted by the expense acceptance unit 121 and one or more destination information items included in the external information, and obtains the inspection result. The one or more destination information items are, for example, a destination set. The destination set is, for example, a destination set stored in the destination set storage unit 116.
(10-1) Inspection of benefits given to public officials

The inspection unit 131 acquires a counterparty identifier contained in the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 judges whether the acquired counterparty identifier exists in the counterparty set storage unit 116 in which information on public officials is stored. If it exists, the inspection unit 131 acquires an inspection result indicating "illegal provision of an illegal benefit to a public official."
(10-2) Inspection of benefits given to assembly members

The inspection unit 131 acquires a counterparty identifier contained in the expense information accepted by the expense acceptance unit 121. Next, the inspection unit 131 judges whether the acquired counterparty identifier exists in the counterparty set storage unit 116 in which information on the assembly member is stored. If it exists, the inspection unit 131 acquires an inspection result indicating "illegal provision of an illegal benefit to the assembly member."
(11) Inspection using past expense information (11-1) Inspection for duplicate applications

The inspection unit 131 determines whether the expense information accepted by the expense acceptance unit 121 is similar to one or more pieces of past expense information stored in the expense information storage unit 111 in association with the same applicant identifier as the applicant identifier associated with the expense information, and obtains the inspection result.

Two pieces of expense information are "close enough to satisfy a predetermined condition" if, for example, (a) a predetermined number or more pieces of information match among the expenditure amount information, store identifier, recipient identifier, usage date information, subject, summary, and approver identifier contained in the expense information accepted by the expense accepting unit 121, or (b) one or more pieces of predetermined information all match. Note that the predetermined one or more pieces of information are one or more pieces of information among the expenditure amount information, store identifier, and recipient identifier contained in the expense information accepted by the expense accepting unit 121.
(11-2) Inspection of the reuse of receipts

When the inspection unit 131 determines that the receipt image in the expense information accepted by the expense accepting unit 121 is similar enough to the receipt image in the past expense information stored in the expense information storage unit 111 to satisfy a predetermined condition, the inspection unit 131 obtains an inspection result indicating that "the receipt is being reused illegally." Note that the receipt image in the past expense information used by the inspection unit 131 for inspection is preferably a receipt image (a receipt image used in the past by the applicant himself) associated with the same applicant identifier as the applicant identifier associated with the expense information accepted by the expense accepting unit 121, but may be a receipt image associated with another applicant identifier. Specifically, for example, the inspection unit 131 inspects whether the receipt is being reused by using one of the following methods (a) and (b).
(a) Using image similarity

For example, the inspection unit 131 obtains a similarity between a receipt image included in the expense information accepted by the expense accepting unit 121 and a receipt image included in one or more pieces of past expense information stored in the expense information storage unit 111, and if the similarity is equal to or greater than a threshold, obtains an inspection result indicating that "the receipt is being reused illegally." Note that the inspection result may include the past expense information that was determined to be reused, the receipt image included in the past expense information that was determined to be reused, etc.
(b) Machine learning

The inspection unit 131 configures a learning device through a machine learning learning process using training data that has, for example, one or more pairs of two receipt images that a person has determined to be a reused receipt as a positive example, and one or more pairs of two different receipts as a negative example. Note that this learning device is a learning device that outputs whether or not the receipts are reused (whether or not they are the same).

Next, the inspection unit 131 performs machine learning prediction processing using the learning device, the receipt image included in the expense information accepted by the expense accepting unit 121, and the past receipt image in the expense information storage unit 111, and when an output result indicating reuse is obtained, obtains an inspection result indicating that "the reuse of receipts is fraudulent." Note that it is preferable that the past receipt image in the expense information storage unit 111 is a receipt image associated with an applicant identifier corresponding to the expense information accepted by the expense accepting unit 121.
(11-3) Checking the number of expense claims on the same day

The inspection unit 131 inspects two or more pieces of expense information corresponding to one applicant identifier, determines whether the number of pieces of expense information having the same date of use information is large enough to satisfy a predetermined condition, and obtains an inspection result. If the number of pieces of expense information is large enough to satisfy a predetermined condition, the inspection unit 131 obtains an inspection result indicating that the information is fraudulent.

The number of pieces of expense information having the same date of use information associated with one applicant identifier may be obtained by the statistical processing unit 132 .
(11-4) Inspection of fraudulent expenditures from after-parties

The inspection unit 131 inspects two or more pieces of expense information corresponding to one applicant identifier, determines whether the number of pieces of expense information having the same date of use but different restaurant identifiers is large enough to satisfy a predetermined condition, and obtains the inspection result. For example, if there are expense claims for two or more restaurants on the same day, this means that the expenses were used up to the after-party, and obtains the inspection result that it is "fraudulent expenditure for the after-party."
(12) Inspection using statistical processing results

The inspection unit 131 inspects whether or not the statistical processing result acquired by the statistical processing unit 132 satisfies a predetermined condition, and acquires the inspection result.
(12-1) Inspection using store frequency information

The inspection unit 131 inspects whether the store frequency information acquired by the statistical processing unit 132 is large enough to satisfy a predetermined condition, and acquires an inspection result. When the store frequency information is large enough to satisfy a store frequency condition, which is a predetermined condition, the inspection unit 131 acquires an inspection result indicating that "one store is being used too much." The store frequency condition is an example of an illegal condition. Examples of the store frequency condition are "store frequency information >= threshold" and "store frequency information >threshold." Furthermore, the store frequency condition is stored in the storage unit 11, for example.
(12-2) Inspection using entertainment frequency information

The inspection unit 131 inspects whether the entertainment frequency information acquired by the statistical processing unit 132 satisfies a predetermined condition, and acquires an inspection result. When the entertainment frequency information has a value large enough to satisfy the entertainment frequency condition, which is a predetermined condition, the inspection unit 131 acquires an inspection result indicating that "the number of times entertainment, etc., has been provided to one client is too many (possibility of collusion, etc.)." The entertainment frequency condition is an example of an improper condition. For example, the entertainment frequency condition is "entertainment frequency information >= threshold" or "entertainment frequency information >threshold." The entertainment frequency condition is stored in the storage unit 11, for example.
(12-3) Inspection of the number of fraudulent acts committed by an applicant

The inspection unit 131 inspects whether the number of fraudulent acts acquired by the statistical processing unit 132 satisfies a predetermined condition, that is, a fraud count condition, and acquires an inspection result indicating that "the applicant has committed many fraudulent acts." The predetermined condition is, for example, "the number of fraudulent acts up to now is equal to or greater than a threshold value," or "the number of fraudulent acts in a unit period (e.g., one year, three years) is equal to or greater than a threshold value." The fraud count condition is one example of a fraud condition. Examples of the fraud count condition are "number of fraudulent acts >= threshold value," and "number of fraudulent acts > threshold value." The fraud count condition is stored in the storage unit 11, for example.
(13) Detection of fraud by expense claim approvers

The checking unit 131 checks whether an approver identified by an approver identifier included in the accepted expense information is an approver specified by the approver information, and obtains a check result.
(13-1) When the approvers who can approve are managed

The inspection unit 131, for example, determines whether the approver identifier contained in the accepted expense information is included in the approver information stored in the company-defined information storage unit 113, and if not, obtains an inspection result indicating that the approver is an "unauthorized approver."
(13-2) When approval-enabled roles are managed

The inspection unit 131, for example, obtains a position identifier that pairs with the approver identifier contained in the accepted expense information from the personal information storage unit 1121, and determines whether the position identifier is included in the approver information stored in the company-defined information in the company-defined information storage unit 113.If not, it obtains an inspection result indicating that the approver is an "unauthorized approver."
(14) Detection of missing applications

The inspection unit 131 uses the applicant information corresponding to one applicant identifier to determine whether or not the expense information corresponding to the applicant information exists in the expense information storage unit 111 in which one or more pieces of expense information associated with one applicant identifier are stored, and performs inspection for missing applications to determine whether or not an application for expenses corresponding to the applicant information has been submitted, and obtains the inspection result. Note that the applicant information is, for example, attendance information, entrance and exit information, business activity information, card statement information, and business vehicle location information.
(14-1) Detection of missed claims using attendance information (a) Missed claims for labor wage expenses

The inspection unit 131 acquires attendance information corresponding to one applicant identifier from the attendance information storage unit 1122. Next, the inspection unit 131 judges whether the acquired attendance information is information corresponding to attendance outside the salary range. Next, if it is judged that the attendance information is information corresponding to attendance outside the salary range, the inspection unit 131 judges whether expense information corresponding to one applicant identifier, having the same date of use information as the working date information contained in the attendance information, and having an expense type identifier indicating labor wages (for example, "labor wages") exists in the expense information storage unit 111. If it is judged that the expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the attendance information have not been applied for."

Regarding whether the acquired attendance information is attendance outside the salary range, 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 outside the salary range. For example, the inspection unit 131 acquires an 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 work", "part-time"), it determines that the acquired attendance information is attendance outside the salary range. Note that the applicant type information is information contained in the personal information in the personal information storage unit 1121.
(b) Failure to claim travel expenses

The inspection unit 131 acquires attendance information corresponding to one applicant identifier from the attendance information storage unit 1122. Next, the inspection unit 131 judges whether the acquired attendance information corresponds to a business trip. If the attendance information corresponds to a business trip, the inspection unit 131 judges whether expense information corresponding to one applicant identifier, having the same date of use information as the work date information contained in the attendance information, and having an expense type identifier of expenses claimed for a business trip (e.g., "business trip expenses", "travel expenses") exists in the expense information storage unit 111. If the inspection unit 131 judges that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the business trip have not been claimed".

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

The inspection unit 131 acquires attendance information corresponding to one applicant identifier from the attendance information storage unit 1122. Next, the inspection unit 131 judges whether the acquired attendance information corresponds to an overseas business trip. If the attendance information corresponds to an overseas business trip, the inspection unit 131 judges whether expense information corresponding to one applicant identifier, having the same date of use information as the work date information contained in the attendance information, and having an expense type identifier of expenses claimed for an overseas business trip (for example, "overseas daily allowance" or "overseas business trip allowance") exists in the expense information storage unit 111. If the inspection unit 131 judges that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the overseas business trip have not been claimed."

For example, when the attendance information has an overseas business trip flag indicating an overseas business trip, the inspection unit 131 determines that the attendance information corresponds to an overseas business trip. Also, for example, when the attendance information has a location identifier indicating the destination of the overseas business trip, the inspection unit 131 determines that the attendance information corresponds to an overseas business trip.

The inspection unit 131 may also obtain, for example, the amount information specified for overseas business trips contained in the company-specified information in the company-specified information storage unit 113, compare it with the amount information of the corresponding expense information, and if there is a mismatch, obtain an inspection result indicating "fraudulent application of overseas daily allowance."

Furthermore, the inspection unit 131, for example, acquires sales activity information corresponding to one applicant identifier from the sales activity information storage unit 1124. Then, when the inspection unit 131 determines that the location identifier held by the sales activity information is a location identifier corresponding to an overseas business trip, it acquires the business day information held by the sales activity information. Next, the inspection unit 131 determines whether or not 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 acquired business day information, and has an expense type identifier for expenses claimed for an overseas business trip. When the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the overseas business trip have not been claimed."
(14-2) Detection of missed claims using entrance and exit information (a) Missed claims for labor and wage expenses

The inspection unit 131 acquires entry/exit information corresponding to one applicant identifier from the entry/exit information storage unit 1123. Next, the inspection unit 131 judges whether the acquired entry/exit information corresponds to work that is not included in the salary range. Next, if it is judged that the entry/exit information corresponds to work that is not included in the salary range, the inspection unit 131 judges whether expense information corresponding to one applicant identifier, having the same usage date information as the work date information contained in the entry/exit information, and having an expense type identifier indicating labor wages (for example, "labor wages") exists in the expense information storage unit 111. If it is judged that the expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the entry/exit information have not been applied for."

Regarding whether the acquired entry/exit information is attendance outside the salary range, the inspection unit 131, for example, acquires the day of the week information contained in the entry/exit information, and if the day of the week information is a day that is not a work day (for example, Saturday, Sunday, or public holiday), determines that the acquired entry/exit information is attendance outside the salary range. The inspection unit 131, for example, acquires an applicant identifier corresponding to the entry/exit information, and if the applicant type information paired with the applicant identifier is predetermined information (for example, "part-time work" or "part-time"), determines that the acquired entry/exit information is work outside the salary range.
(b) Failure to claim travel expenses

The inspection unit 131 acquires entrance/exit information corresponding to one applicant identifier from the entrance/exit information storage unit 1123. Next, the inspection unit 131 judges whether the acquired entrance/exit information corresponds to a business trip. If the entrance/exit information corresponds to a business trip, the inspection unit 131 judges whether expense information corresponding to one applicant identifier, having the same date of use information as the work date information contained in the entrance/exit information, and having an expense type identifier of expenses claimed for a business trip (for example, "business trip expenses", "travel expenses") exists in the expense information storage unit 111. If the inspection unit 131 judges that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the business trip have not been claimed".

The inspection unit 131 determines that the entrance/exit information corresponds to a business trip, for example, when the entrance/exit information does not have start time information and end time information. The inspection unit 131 determines that the entrance/exit information corresponds to a business trip, for example, when the entrance/exit information does not have start time information and end time information, corresponds to one applicant identifier, and determines that the attendance information having the same work day information as the use date information is information indicating attendance (not absence).
(14-3) Detection of missed applications using sales activity information (a) Missed travel expenses

The inspection unit 131 acquires sales activity information corresponding to one applicant identifier from the sales activity information storage unit 1124. Next, the inspection unit 131 judges whether the acquired sales activity information is information corresponding to a business trip. If the sales activity information is information corresponding to a business trip, the inspection unit 131 judges whether expense information corresponding to one applicant identifier, having the same date of use information as the business day information contained in the sales activity information, and having an expense type identifier of expenses claimed for a business trip (for example, "business trip expenses", "travel expenses") exists in the expense information storage unit 111. If the inspection unit 131 judges that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the business trip have not been claimed."

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

In addition, for example, if the sales activity information has a location identifier, the inspection unit 131 determines that the sales activity information corresponds to a business trip.

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

The inspection unit 131 acquires one or more location identifiers contained in the sales activity information corresponding to one applicant identifier from the sales activity information storage unit 1124. Next, the inspection unit 131 determines whether or not travel expenses will be incurred using pre-stored company location information and the acquired one or more location identifiers. If it is determined that travel expenses will be incurred, the inspection unit 131 determines whether or not expense information having the same usage date information as the business day information contained in the sales activity information and an expense type identifier of "travel expenses" exists in the expense information storage unit 111. If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that the "travel expenses have not been claimed."

The inspection unit 131 determines whether or not transportation expenses will be incurred by using, for example, the calculation information 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 transportation expense information is output. The inspection unit 131 also obtains, for example, the distance between the company's location information and the location identifier by using map information, and determines whether or not transportation expenses will be incurred based on whether or not the distance is equal to or greater than a threshold. The calculation module is a known technology.
(14-4) Detection of missed applications using company vehicle location information (a) Missed travel expenses applications

The inspection unit 131 acquires one or more pieces of business vehicle location information corresponding to one applicant identifier and one or more pieces of use date information from the business vehicle location information storage unit 1126. Next, the inspection unit 131 determines whether the acquired one or more pieces of business vehicle location information are information corresponding to a business trip. If the business vehicle location information is information corresponding to a business trip, the inspection unit 131 determines whether or not there is expense information in the expense information storage unit 111 that corresponds to one applicant identifier, has the same use date information as one piece of use date information corresponding to the business vehicle location information, and has an expense type identifier (e.g., "business trip expenses") for expenses claimed during a business trip. If the inspection unit 131 determines that such expense information is not present in the expense information storage unit 111, the inspection unit 131 acquires an inspection result indicating that "expenses corresponding to the business trip have not been claimed."

The inspection unit 131, for example, uses one or more pieces of business vehicle position information and pre-stored company position information to obtain the maximum value of the distance between the position indicated by the business vehicle position information and the company using the map information in the map information storage unit 1182, and if it determines that the maximum value of the distance is equal to or greater than the distance at which travel expenses are incurred, it determines that the sales activity information corresponds to a business trip. Note that information on the minimum distance at which travel expenses are incurred is stored, for example, in the company-defined information storage unit 113.

In addition, the inspection unit 131 determines that the business activity information corresponds to a business trip when, for example, a business trip flag is associated with one or more pieces of business vehicle location information. The business trip flag is a flag that indicates that the business trip is occurring.

The output unit 14 outputs various information. The various information includes, for example, the results of the examination, the results of the image examination, and the results of the statistical processing. Here, the output is usually transmitted to the applicant terminal 2, but may also be transmitted to another device such as an accounting terminal, stored in the expense examination device 1, or displayed on a display.
(15) Receipt image inspection performed by the image inspection means 1311

The image inspection means 1311 performs, for example, one or more of character recognition processing and machine learning processing (such as any of the above methods (1) to (3)), obtains one or more character strings, determines whether each of the one or more character strings satisfies a predetermined condition, and obtains an image inspection result. The one or more character strings are, for example, any of payment amount information, store identifier, other party identifier, use date information, item, summary, and payment method information.

Examples of inspections performed by the image inspection means 1311 are the following (15-1) to (15-9). The image inspection means 1311 performs, for example, one or more of the inspections (15-1) to (15-9) and obtains image inspection results. Note that (15-1) to (15-9) are examples of receipt image inspections.
(15-1) Check for mismatch between receipt image and expense information string

The image inspection means 1311 obtains one or more pairs of character strings and classes from a receipt image contained in the expense information accepted by the expense acceptance unit 121. Next, for each pair, the inspection unit 131 obtains a character string (e.g., any of payment amount information, store identifier, recipient identifier, date of use information, subject, summary, and payment method information) contained in the expense information accepted by the expense acceptance unit 121 that corresponds to the class contained in the pair. Next, the inspection unit 131 compares, for each pair, a character string of one class obtained from the receipt image with a character string of the same class contained in the expense information accepted by the expense acceptance unit 121, and determines whether or not they have a predetermined relationship. If they do not have the predetermined relationship, the inspection unit 131 obtains an inspection result indicating fraud.

The predetermined relationship is a match, but similar enough to satisfy a predetermined condition (for example, the degree of similarity is above a threshold, the only difference is between "(stock)" and "Kaishokaisha", the only difference is the spelling, etc.).
(15-2) Inspection of monetary amount manipulation (a) When character recognition processing is used

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

The image inspection means 1311, for example, configures a learning device that uses one or more receipt images with handwritten forged amounts and one or more receipt images without forged amounts as training data, performs learning processing using a machine learning algorithm, and obtains an inspection result as to whether or not the amount has been forged using the receipt images as input.

Next, the image inspection means 1311, for example, uses the receipt image accepted by the expense acceptance unit 121 and a learning device to perform prediction processing using a machine learning algorithm, and obtains image inspection results indicating whether the amount written on the receipt image has been handwritten forged.
(15-3) Inspection of inappropriate tax classifications, etc.

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

An example of a fraudulent pattern is when a character string corresponding to the class "summary" includes the character string "gift" and a character string corresponding to the class "tax category" includes "10%". Such a fraudulent pattern is a tax category fraud. For example, when the image inspection means 1311 determines using the acquired character string that a character string corresponding to the class "summary" includes the character string "gift" and a character string corresponding to the class "tax category" includes "10%", the image inspection means 1311 acquires an image inspection result indicating "tax category fraud".
(15-4) Inspection of address errors

The image inspection means 1311 obtains one or more character strings from the receipt image and associates them with a class.

Next, when the image inspection means 1311 determines that the character string corresponding to the class "addressee" does not match the company name stored in the storage unit 11, it acquires an image inspection result indicating that the addressee on the receipt is inaccurate. Also, for example, when the image inspection means 1311 determines that the character string corresponding to the class "addressee" is an inappropriate character string such as "Dear Sir" stored in the storage unit 11 using the acquired character string, it acquires an image inspection result indicating that the addressee on the receipt is inaccurate.
(15-5) Inspection of receipt signature

The image inspection means 1311 uses training data in which one or more receipts with a signature are treated as positive examples and one or more receipts without a signature are treated as negative examples to construct a learning device through a machine learning algorithm. The image inspection means 1311 then performs a prediction process using the received receipt image and the learning device to obtain information indicating the presence or absence of 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 not being signed.
(15-6) Inspection of Blurred Receipt Images (a) When Character Recognition Processing is Used (First Blurred Processing)

The image inspection means 1311 performs a first blurring process using character recognition technology to obtain a character recognition score together with one or more character strings from the receipt image received by the expense receiving unit 121, and to determine that the receipt image is blurred if the score is low enough to satisfy a predetermined condition. Note that the technology of performing character recognition, obtaining character strings, and outputting the character recognition score (which may also be called likelihood) is a publicly known technology.
(b) When machine learning processing is used (second blurring process)

The image inspection means 1311 performs a learning process on one or more blurred receipt images and one or more clear receipt images using a machine learning algorithm to form a learning device. Note that this learning device is a learning device that receives a receipt image as input and obtains a judgment result as to whether the receipt image is blurred or clear.

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

The image inspection unit 1311 obtains the payment method information (e.g., "OOPAY"), which is a character string, from the receipt image, inspects whether the payment method information is the payment method information included in the company-defined information, and obtains the image inspection result. The company-defined information is stored in the company-defined information storage unit 113.
(15-8) Inspection of the presence of a square seal on a handwritten receipt (a) Using machine learning processing

The image inspection means 1311, for example, performs learning processing using a machine learning algorithm with one or more handwritten receipt images with a square stamp as positive examples and one or more receipt images without a square stamp as negative examples to form a learning device. Note that this learning device is a learning device that receives a receipt image as input and outputs whether or not a square stamp is present.

Next, the image inspection means 1311 uses the received receipt image and the learning device to perform prediction processing using a machine learning algorithm, and obtains an image inspection result indicating whether or not a square stamp is present.
(b) When image recognition processing is used

The image inspection means 1311 performs character recognition processing on the received receipt image to determine whether or not handwritten characters are present (e.g., whether or not the score is equal to or less than a threshold value). If it is determined that handwritten characters are present, the image inspection means 1311 determines, for example, by image recognition, whether or not a square mark whose pixel values are those of a red area and which has a roughly rectangular outline is present. If it is determined that a square mark is not present, the image inspection means 1311 obtains an image inspection result indicating that no square mark is pressed.
(15-9) Time stamp inspection

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

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

Next, the image inspection means 1311 determines whether the date indicated by the acquired date information is a predetermined period of time or more from the receipt issue date, and acquires the image inspection result. The predetermined period of time or more is, for example, "three days or more" or "four days or more."

The image inspection means 1311 normally obtains the receipt issue date from the receipt image, but may obtain the receipt issue date as a character string included in the expense information received by the expense reception unit 121. Furthermore, the technology for adding a timestamp to a receipt image and the technology for obtaining a timestamp contained in a receipt image are publicly known technologies.

The storage unit 11, expense information storage unit 111, applicant group storage unit 112, company regulation 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, transportation means information storage unit 118, personal information storage unit 1121, attendance information storage unit 1122, entrance and exit information storage unit 1123, business activity information storage unit 1124, card statement information storage unit 1125, business vehicle position information storage unit 1126, calculation information storage unit 1181, map information storage unit 1182, and first storage unit 21 are preferably non-volatile recording media, but can also be realized with volatile recording media.

The process by which information is stored in the storage unit 11, etc. is not important. 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 inputted via an input device may be stored in the storage unit 11, etc.

The reception unit 12, expense reception unit 121, and first reception unit 25 are typically realized by wireless or wired communication means, but may also be realized by means of receiving broadcasts.

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

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

The first reception unit 22 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen, etc.

The first output unit 26 may be considered to include, or may not include, an output device such as a display, a speaker, etc. The first output unit 26 may be realized by driver software for an output device, or a combination of driver software for an output device and an output device, etc.
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 acceptance unit 121 determines whether or not expense information associated with the application form identifier has been received from the applicant terminal 2. If expense information has been received, the process proceeds to step S402; if expense information has not been 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 a process for inspecting the expense application for fraud. An example of the inspection process is described using the flowchart in FIG. 5.

(Step S403) The inspection unit 131 judges whether the inspection result acquired in step S402 is "legitimate". If it is "legitimate", the process proceeds to step S404, and if it is not "legitimate", the process proceeds to step S405.

(Step S404) The processing unit 13 or a storage unit (not shown) associates the expense information received in step S401 with the application form identifier and stores it in the expense information storage unit 111. Return to step S401. Note that in step S404, the result output unit 141 may send an inspection result indicating that the expense information is "legitimate" to the applicant terminal 2 that sent the expense information.

(Step S405) The result output unit 141 transmits the inspection results acquired in step S402 to the applicant terminal 2 that transmitted the expense information. Return to step S401. Note that in step S405, the inspection unit 131 may increment the number of fraudulent attempts corresponding to the applicant identifier that corresponds to the expense information by 1. Also, in step S405, the processing unit 13 or a storage unit (not shown) may associate the expense information received in step S401 with the application form identifier and store it in the expense information storage unit 111.

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

The processing unit 13 obtains the time from a clock (not shown), and if the time is after a predetermined time, determines that it is time to perform a statistical check. The processing unit 13 also determines that it is time to perform a statistical check if an instruction for a statistical check is received. A statistical check is a check for fraud using the results of statistical processing of expense information. It is preferable that the statistical check is 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 or not 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 or not the i-th applicant identifier exists depends on whether or not the i-th applicant to be inspected exists.

(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 application. An example of such statistical inspection processing is described using the flowchart in FIG. 6.

(Step S410) The processing unit 13 outputs the test results acquired in step S409 in association with the i-th applicant identifier. The processing unit 13 stores the test results in the storage unit 11 in association with the i-th applicant identifier, for example. The processing unit 13 also transmits the test results associated with the i-th applicant identifier, for example, to a terminal not shown.

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

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

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

(Step S414) The processing unit 13 judges whether it is time to perform an omission check. If it is time to perform an omission check, the process proceeds to step S415. If it is not time to perform an omission check, the process returns to step S401.

The processing unit 13 obtains the time from a clock (not shown), and if the time is after a predetermined time, determines that it is time to perform a declaration omission check. The processing unit 13 also determines that it is time to perform a declaration omission check if an instruction to perform a declaration omission check is received. A declaration omission check is a check for omissions in expense claims. It is preferable that the declaration omission check be performed periodically (for example, once a month).

(Step S415) The processing unit 13 performs a check for omissions in the expense claim. An example of the omission check process is described using the flowchart in FIG. 7.

(Step S416) The result output unit 141 outputs the test results of the leak test obtained in step S415. Return to step S401. Outputting the test results here means, for example, storing the test results in the storage unit 11, sending them to an applicant identified by the applicant identifier corresponding to the leak, sending them to a terminal not shown, etc.

In the flowchart in Figure 4, processing ends when the power is turned off or an interrupt occurs to end processing.

Next, an example of the inspection process in step S402 will be described using the flowchart in FIG.

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

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

(Step S503) The image inspection means 1311 performs receipt image inspection and obtains the inspection results.

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

(Step S504) The inspection unit 131 performs a common inspection and obtains the inspection results. A common inspection is an inspection that is not dependent on the expense type identifier (which may be a subject) of the expense information.

Common inspections include, for example, (1-1) and (2-1) inspections of expenses not incurred on working days, (4-1) inspections of receipt splitting, (5-1) inspections of unauthorized use of company vehicles, (6) inspections using card-used expense information, (10) inspections using recipient 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 an expense type identifier from the received expense information.

(Step S506) The inspection unit 131 determines whether the expense type identifier acquired in step S505 is "transportation expenses (travel expenses may be used)." If it is "transportation expenses," the process proceeds to step S507, and if it is not "transportation expenses," the process proceeds to step S508.

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

The transportation expense inspection process is a process for inspections specific to transportation expenses. Examples of the transportation expense inspection process include the above-mentioned (3-1) inspection for transportation expense fraud (i), (3-2) inspection for transportation expense fraud (ii), (4-2) inspection for taxi use after an office drinking party, (8-1) inspection for train, bus, or airplane transportation expense fraud, (8-2) inspection for taxi fare fraud, and (8-3) inspection for overlap with regular commuter routes.

(Step S508) The inspection unit 131 determines whether the expense type identifier acquired in step S505 is "entertainment expenses (or entertainment expenses)." If it is "entertainment expenses," the process proceeds to step S509, and if it is not "entertainment expenses," the process proceeds to step S510.

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

The entertainment expense inspection process is a process for inspections specific to entertainment expenses. Examples of entertainment expense inspection processes include (9-1) inspection of store fraud (use of adult entertainment establishments, etc.), (9-2) inspection of amount fraud, (9-3) inspection of whether entertainment expenses include use of restaurants, (10) inspection using counterparty information, and (11-4) inspection of fraudulent expenditures for after-parties.

(Step S510) The inspection unit 131 determines whether the expense type identifier acquired in step S505 is "accommodation expenses". If it is "accommodation expenses", the process proceeds to step S511, and if it is not "accommodation expenses", the process proceeds to step S512.

(Step S511) The inspection unit 131 performs accommodation fee inspection processing and obtains the inspection results. Go to step S514.

The accommodation expense inspection process is a process for inspections specific to accommodation expenses. Examples of accommodation expense inspection processes include (1-3) inspection of accommodation expense fraud and (2-3) inspection of accommodation expense fraud.

(Step S512) The inspection unit 131 determines whether the expense type identifier acquired in step S505 is "travel expenses". If it is "travel expenses", the process proceeds to step S513, and if it is not "travel expenses", the process proceeds to step S512.

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

The travel expense inspection process is a process for inspections specific to travel expenses. Examples of the travel expense inspection process include (1-2) Inspection of travel expense fraud and (2-2) Inspection of travel expense fraud.

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

For example, if one or more fraudulent inspection results are obtained, the inspection unit 131 constructs an inspection result that includes all the inspection results in the case of fraud. Also, if no fraudulent inspection results are obtained, the inspection unit 131 constructs an inspection result that indicates "legitimate."

Next, an example of the statistical inspection process in step S409 will be described using the flowchart in FIG. 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 one or more pieces of expense information corresponding to the applicant identifier to be inspected (the i-th applicant identifier in step S408) and among the store identifiers in the one or more pieces of expense information in the expense information storage unit 111. If the i-th store identifier exists, the process proceeds to step S603, and 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 among the store identifiers in one or more pieces of expense information corresponding to the applicant identifier of the subject of inspection that have been uniquely processed. The period of the expense information of the subject of inspection may be predetermined or may be the entire period.

(Step S603) The statistical processing unit 132 obtains the number of pieces of expense information that correspond to the applicant identifier to be inspected and that include 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 may be a value obtained by dividing the number by a period, etc. The store frequency information is usually a value calculated using an increasing function with the number as a parameter.

(Step S604) The inspection unit 131 determines whether the store frequency information acquired in step S603 is large enough to satisfy a predetermined store frequency condition. If the store frequency condition is satisfied, the process proceeds to step S605; if the store frequency condition is not satisfied, the process proceeds to step S606.

(Step S605) The inspection unit 131 obtains the inspection result indicating that "one store is used too much" and the inspection result having the i-th store identifier in association with the applicant identifier to be inspected. Note that the inspection unit 131 may increment the number of fraudulent attempts corresponding to the applicant identifier to be inspected by 1.

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

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

(Step S608) The statistical processing unit 132 determines whether the i-th recipient identifier exists in the store identifier in the one or more pieces of expense information in the expense information storage unit 111, which is one or more pieces of expense information corresponding to the applicant identifier to be inspected. If the i-th recipient identifier exists, the process proceeds to step S609, and if the i-th recipient identifier does not exist, the process proceeds to step S613.

The i-th recipient identifier is the i-th recipient identifier among the recipient identifiers in one or more pieces of expense information corresponding to the applicant identifier to be inspected, which are uniquely processed. The period of the expense information to be inspected may be predetermined or may be the entire period.

(Step S609) The statistical processing unit 132 obtains the number of pieces of expense information that correspond to the applicant identifier to be inspected and that contain the i-th recipient identifier. The statistical processing unit 132 uses this number to obtain recipient frequency information. Note that the recipient frequency information may be the same value as the number, or may be a value obtained by dividing the number by a period, etc. The recipient frequency information is usually a value calculated using an increasing function with the number as a parameter.

(Step S610) The inspection unit 131 determines whether the destination frequency information acquired in step S603 is large enough to satisfy a predetermined destination frequency condition. If the destination frequency condition is satisfied, the process proceeds to step S611. If the destination frequency condition is not satisfied, the process proceeds to step S612.

(Step S611) The inspection unit 131 obtains the inspection result indicating that "the number of times entertainment, etc., was too many for one client" and the inspection result having the i-th client identifier in association with the applicant identifier to be inspected. Note that the inspection unit 131 may increment the number of fraudulent attempts corresponding to the applicant identifier to be inspected by 1.

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

(Step S613) The inspection unit 131 obtains the number of fraudulent attempts 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 attempts obtained in step S613 satisfies the fraudulent attempt count condition. If the number of fraudulent attempts condition is met, the process proceeds to step S615. If the number of fraudulent attempts condition is not met, the process proceeds to step S616.

(Step S615) The inspection unit 131 obtains an inspection result indicating that the applicant has committed a large number of fraudulent acts in association with the applicant identifier being inspected. Note that the inspection result may be only the applicant identifier with a large number of fraudulent acts.

(Step S616) The inspection unit 131 determines whether or not a fraudulent inspection result was obtained as a result of the statistical inspection. If an inspection result was obtained, the process returns to the upper process, and if an inspection result was not obtained, the process proceeds to step S617.

(Step S617) The inspection unit 131 assigns "legitimate" to the variable "inspection result". Then it returns to the upper process.

Next, an example of the leak inspection process in step S415 will be described using the flowchart in FIG.

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

(Step S702) The inspection unit 131 determines whether or not the i-th applicant identifier exists in the storage unit 11. If the i-th applicant identifier exists, the process proceeds to step S703, and if the i-th applicant identifier does not exist, the process returns to the upper level process. The i-th applicant identifier is the identifier of the i-th applicant to be 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 day information indicating the jth day to be inspected exists. If day information indicating the jth day exists, the process proceeds to step S705, and if not, the process proceeds to step S722. Note that the day on which the leak inspection will be performed is determined in advance, and information specifying the day on which the leak inspection will be performed is stored in a buffer (not shown).

(Step S705) The inspection unit 131 determines whether attendance information corresponding to the i-th applicant identifier and having the same work day information as the day information indicating the j-th day exists in the attendance information storage unit 1122. If it exists, the process proceeds to step S706; if it does not exist, the process proceeds to step S709.

(Step S706) The inspection unit 131 obtains attendance information that corresponds to the i-th applicant identifier and has the same working day information as the day information indicating the j-th day from the attendance information storage unit 1122. The inspection unit 131 uses the obtained attendance information to check for missing expense claims. This inspection is, for example, the process described in "(14-1) Detecting Missing Claims Using Attendance Information".

(Step S707) The inspection unit 131 determines whether or not there is a leak based on the result of the inspection in step S706. If there is a leak, the process proceeds to step S708; if there is no leak, the process proceeds to step S709.

(Step S708) The inspection unit 131 obtains the inspection results indicating the presence of an omission and the details of the omission, in association with the i-th applicant identifier and the j-th day information.

(Step S709) The inspection unit 131 determines whether or not entry/exit information corresponding to the i-th applicant identifier and having the same work day information as the day information indicating the j-th day exists in the entry/exit information storage unit 1123. If it exists, the process proceeds to step S710; if it does not exist, the process proceeds to step S713.

(Step S710) The inspection unit 131 obtains entry/exit information that corresponds to the i-th applicant identifier and has the same work day information as the day information indicating the j-th day from the entry/exit information storage unit 1123. The inspection unit 131 uses the obtained entry/exit information to check for missing expense claims. This inspection is, for example, the process described in "(14-2) Detecting Missing Claims Using Entry/Exit Information".

(Step S711) The inspection unit 131 determines whether or not there is a leak based on the result of the inspection in step S710. If there is a leak, the process proceeds to step S712; if there is no leak, the process proceeds to step S713.

(Step S712) The inspection unit 131 obtains the inspection results indicating the presence of an omission and the details of the omission, in association with the i-th applicant identifier and the j-th day information.

(Step S713) The inspection unit 131 determines whether sales activity information corresponding to the i-th applicant identifier and having the same business day information as the day information indicating the j-th day exists in the sales activity information storage unit 1124. If it exists, the process proceeds to step S714; if it does not exist, the process proceeds to step S717.

(Step S714) The inspection unit 131 obtains sales activity information that corresponds to the i-th applicant identifier and has the same business day information as the day information indicating the j-th day from the sales activity information storage unit 1124. The inspection unit 131 uses the obtained sales activity information to check for missing expense claims. This inspection is, for example, the process described in "(14-3) Detecting Missing Claims Using Sales Activity Information".

(Step S715) The inspection unit 131 determines whether or not there is a leak based on the result of the inspection in step S714. If there is a leak, the process proceeds to step S716; if there is no leak, the process proceeds to step S717.

(Step S716) The inspection unit 131 obtains the inspection results indicating the presence of an omission and the details of the omission, in association with the i-th applicant identifier and the j-th day information.

(Step S717) The inspection unit 131 determines whether or not commercial vehicle location information that corresponds to the i-th applicant identifier and has the same business day information as the day information indicating the j-th day exists in the commercial vehicle location information storage unit 1126. If it exists, the process proceeds to step S718; if it does not exist, the process proceeds to step S721.

(Step S718) The inspection unit 131 obtains one or more pieces of business vehicle location information that correspond to the i-th applicant identifier and have the same business day information as the day information indicating the j-th day from the business vehicle location information storage unit 1126. The inspection unit 131 uses the one or more pieces of business vehicle location information obtained to check for missing expense claims. This inspection is, for example, the process described in "(14-4) Detecting Missing Claims Using Business Vehicle Location Information".

(Step S719) The inspection unit 131 determines whether or not there is a leak based on the result of the inspection in step S718. If there is a leak, the process proceeds to step S720; if there is no leak, the process proceeds to step S721.

(Step S720) The inspection unit 131 obtains the inspection results indicating the presence of an omission and the details of the omission, in association with the i-th applicant identifier and the j-th day information.

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

(Step S722) The inspection unit 131 constructs an inspection result corresponding to the i-th applicant identifier. Note that the inspection unit 131 temporarily stores the inspection result, for example, in association with the i-th applicant identifier. The inspection result includes, for example, the results of one or more inspections for omissions. If there are no omissions, the inspection result is information indicating "no omissions."

(Step S723) The inspection unit 131 increments the 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 input of expense information from a user. Next, the first processing unit 23 reads out the applicant identifier stored in the first storage unit 21. The first processing unit 23 then composes transmission information having the received expense information and the read out applicant identifier. Next, the first transmission unit 24 transmits the transmission information having the expense information and the applicant identifier to the expense inspection device 1.

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

Below, we will explain an example of the 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 statistically processes the expense information of each applicant for a certain period (for example, one month in December 2019) in the expense information storage unit 111 for each applicant, and obtains store frequency information for each applicant identifier and each store identifier. The statistical processing unit 132 also obtains the number of pieces of expense information for each applicant identifier.

Then, the statistical processing unit 132 obtains the statistical processing results in which the store frequency information for each applicant identifier and each store identifier is plotted on a graph with the store frequency information on the vertical axis and the number of expense information for each applicant identifier on the horizontal axis.

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. High risk can also 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 to be used, and the store frequency information.

Then, the statistical processing unit 132 constructs the statistical processing results to be 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 FIG. 8.

In FIG. 8, 801 is the result of statistical processing in which store frequency information is plotted on a graph. The vertical axis of 801 is the maximum number of cases per person and store (store frequency information). The horizontal axis of 801 is the number of applications per person.

Also, 802 is a table consisting of records having an applicant identifier (applicant), store name, and store frequency information (number of cases) corresponding to store frequency information determined to be high risk.

(Specific Example 2)
The second specific example is an example of acquiring information on the case where a person is on a business trip but has still stamped their time.

For example, for each applicant identifier, if the attendance information indicates a business trip, or if expense information for business trips or transportation expenses has been applied for, the statistical processing unit 132 determines that the day corresponding to the work day information in the attendance information or the usage day information in the expense information is the day of the business trip.

Next, the statistical processing unit 132 obtains the frequency (e.g., the number of times in a given month) at which a work start time and a work end time exist (are punched in) and which is the entry/exit information that contains the same work day information as the work day information contained in the attendance information or the usage day information contained in the expense information. Such information is the frequency at which a time is punched in during a business trip.

The statistical processing unit 132 also obtains, for example, for each applicant identifier, the average value of the difference between the working hours indicated by each month's attendance information and the working hours indicated by the entry/exit information that includes the same working day information as the working day information contained in the attendance information. Such information is the discrepancy between the attendance information and the time stamp.

Then, the statistical processing unit 132 creates a statistical processing result, which is a graph in which, for each applicant identifier, dots for the applicant identifier are plotted on a graph with the horizontal axis representing the frequency of time-stamping during business trips and the vertical axis representing the discrepancy between attendance information and time-stamping.

Next, the result output unit 141 outputs the statistical processing results. An example of such an output is shown in FIG. 9. In FIG. 9, the applicants corresponding to the dots in the area 901 are applicants who are likely to be committing fraud.

As described above, according to this embodiment, by using external information or expense information other than the expense information applied for, it is possible to appropriately check for inappropriate expense applications.

In addition, according to this embodiment, by using the applicant information, inappropriate expense applications can be appropriately inspected.

In addition, according to this embodiment, by using the applicant's attendance information, inappropriate expense claims can be properly inspected.

In addition, according to this embodiment, by using the applicant's entrance and exit information, inappropriate expense applications can be properly inspected.

In addition, according to this embodiment, by using the applicant's business activity information, inappropriate expense claims can be properly inspected.

In addition, according to this embodiment, by using the applicant's credit card statement information, inappropriate expense claims can be properly inspected.

In addition, according to this embodiment, by using the applicant's business vehicle location information, inappropriate expense claims can be properly inspected.

In addition, according to this embodiment, by using information from the card owned by the applicant, inappropriate expense claims can be properly inspected.

In addition, according to this embodiment, by using company-specific information, inappropriate expense claims can be properly inspected.

In addition, according to this embodiment, by using transportation information, appropriate inspections can be carried out for inappropriate expense claims.

In addition, according to this embodiment, by using store collections, inappropriate expense claims can be properly inspected.

Furthermore, this embodiment allows for proper detection of inappropriate spending on inappropriate parties.

In addition, this embodiment can properly detect inappropriate business trip expenses, inappropriate transportation expenses, duplicate applications, reuse of receipts, unauthorized accommodation expenses, unauthorized after-party expenses, etc.

In addition, according to this embodiment, by using the results of statistical processing based on two or more pieces of expense information, it is possible to appropriately check for inappropriate expense claims.

Furthermore, this embodiment can detect whether a particular store is frequently used.

In addition, this embodiment can detect high frequency of expenditures to specific recipients.

In addition, this embodiment can detect when a particular person is committing fraud more frequently.

In addition, this embodiment can detect when the approver of an expense request does not meet the requirements.

In addition, this embodiment can detect missed expense claims.

Furthermore, this embodiment allows for proper inspection of receipt images.

Furthermore, this embodiment allows for proper inspection of the information written on the receipt image.

In addition, this embodiment allows you to check for errors in the timestamp of a receipt image.

In addition, this embodiment makes it possible to inspect blurry receipt images.

Furthermore, this embodiment allows for checking for inappropriate payment methods.

Furthermore, this embodiment makes it possible to check for forged handwritten amounts.

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 device. In such a case, the expense inspection device 1 has, for example, the structure of FIG. 10. In other words, in such a case, the applicant set storage unit 112, company-defined information storage unit 113, card usage expense storage unit 117, personal information storage unit 1121, attendance information storage unit 1122, entrance/exit information storage unit 1123, business activity information storage unit 1124, card statement information storage unit 1125, and business vehicle location information storage unit 1126 of the expense inspection device 1 exist, for example, for each organization identifier. In other words, the applicant set, company-defined information, card usage expense information, personal information, attendance information, entrance/exit information, business activity information, card statement information, and business vehicle location information are associated with the organization identifier.

The expense information that the expense inspection device 1 receives 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 an applicant set, etc., associated with the organization identifier corresponding to the expense information, and obtains the inspection results. The result output unit 141 then transmits the inspection results to the expense management device 4. The organization identifier is information that identifies an organization, such as a company name or company ID. An organization is, for example, a company, organization, or department.

Furthermore, the expense management device 4, which receives expense information from the applicant terminal 2, transmits the expense information to the expense inspection device 1 in order to inspect the expense information. In response to the transmission of the expense information, the expense management device 4 receives inspection results from the expense inspection device 1. The expense management device 4 then stores the expense information only if the inspection results are valid. Furthermore, if the inspection results are fraudulent, the expense management device 4 transmits the inspection results to the applicant terminal 2.

The above-described system configuration having the expense checking device 1 and one or more expense management devices 4 allows the expense checking device 1 to function as an expense information checking server. Furthermore, the expense management device 4 can obtain an expense checking function by using the expense checking device 1, in addition to the conventional expense information management function.

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

The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software that realizes the expense inspection device in this embodiment is a program as described below. In other words, this program causes a computer to function as an expense reception unit that receives expense information that specifies the content of an expense application, 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 inspect the expense information received by the expense reception unit for fraud and obtains 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 including an information processing device that acquires and outputs travel route information related to an employee's travel route using the employee's schedule information or performance information will be described. Note that the employee is also, for example, the applicant in the first embodiment.

In addition, in this embodiment, we will explain an information system that includes an information processing device that uses employee schedule information and actual performance information to check whether employees are working as scheduled, obtains the inspection results, and performs processing using the inspection results.

In addition, in this embodiment, we will explain an information system equipped with an information processing device that notifies employees if the above inspection results are invalid.

In addition, in this embodiment, we will explain an information system that has an information processing device that determines whether travel expense information, which is the cost associated with an employee's travel, is an item of commuting expenses or transportation expenses, and outputs the travel expense information by associating it with the item.

In addition, in this embodiment, we will explain an information system equipped with an information processing device that stores different databases for travel expense information when the travel expense information item is commuting expenses and when it is transportation expenses.

In addition, in this embodiment, we will explain an information system equipped with an information processing device that acquires commuting expenses using information on commuter passes and information on means of transportation such as personal cars.

In addition, in this embodiment, an information system having an information processing device that performs processing to accumulate non-zero commuting expense information in a commuting expense database is described. Note that processing to accumulate zero commuting expense information may also be performed.

In addition, in this embodiment, we will explain an information system equipped with an information processing device that acquires travel route information using information on a means of transportation such as a personal car.

In addition, in this embodiment, an information system having an information processing device that notifies an appropriate notification destination (e.g., a superior) when scheduled information or actual performance information differs from default scheduled information or actual performance information is described.

In addition, in this embodiment, we will explain an information system equipped with an information processing device that notifies employees when actual information does not match scheduled information and appropriate actual information cannot be obtained even after the scheduled time has passed.

Furthermore, in this embodiment, an information system is described that includes an information processing device that re-examines received actual information after it is determined that the actual information does not match the scheduled information.

Figure 11 is a conceptual diagram of information system B in this embodiment. Information system B includes an information processing device 5, one or more terminal devices 6, one or more entrance and 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 realizes the functions of the present application and receives and processes information from the terminal device 6, the entrance/exit information acquisition device 7, etc. The information processing device 5 is, for example, a cloud server, an ASP server, etc., but the type is not important.

The terminal device 6 is a terminal used by an employee. An employee is a person whose work is managed by an organization, and may include not only full-time employees but also non-regular employees such as part-time workers. The terminal device 6 may be, for example, a personal computer, a tablet terminal, a smartphone, etc., and the type of device is not important.

The entrance/exit information acquisition device 7 is a device that acquires entrance/exit information. For example, an entrance/exit information acquisition device 7 exists corresponding to each of one or more workplaces where an employee works. However, there may be only one device for two or more workplaces. The entrance/exit information acquisition device 7 may include, for example, a card reader 71 that acquires information from a card held by an employee. The entrance/exit information acquisition device 7 only needs to acquire entrance/exit information, which is information on an employee's entry into or exit from a workplace. The entrance/exit information acquisition device 7, for example, associates the acquired entrance/exit information with an employee identifier and transmits it to the information processing device 5. The entrance/exit information acquisition device 7 can be realized using publicly known technology, so a detailed description will be omitted.

The accounting information management device 8 is a device that manages expense information including transportation expense information and checks expense information. The accounting information management device 8 may have some or all of the functions of the expense checking device 1 of embodiment 1. The accounting information management device 8 is usually a so-called server, such as a cloud server or an ASP server. It should be noted that the type of accounting information management device 8 is not important.

The personnel information management device 9 is a device that manages personnel information including commuting expense information and inspects personnel information. The personnel information management device 9 is usually a so-called server, such as a cloud server or an ASP server. The type of personnel information management device 9 is not important.

The information processing device 5 can communicate with the terminal device 6, the entrance/exit information acquisition device 7, the accounting information management device 8, and the personnel information management device 9, usually 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 information processing device 5 that constitutes information system B.

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

The storage unit 51 includes a home location storage unit 511, a workplace information storage unit 512, a commuter pass information storage unit 513, a mobile information storage unit 514, a commuter route storage unit 515, a default storage unit 516, and a work information storage unit 517. Note that the storage unit 51 and each storage unit within the storage unit 51 may exist in an external device other than the information processing device 5. The storage unit 51 may also include a transportation expense database 81 and a commuter expense database 91, which will be described later.

The work information storage unit 517 includes a schedule information storage unit 5171 and an actual performance information storage unit 5172.

The receiving unit 52 includes a schedule receiving unit 521 and a performance receiving unit 522.

The processing unit 53 includes a change judgment unit 530, a schedule accumulation unit 531, a performance accumulation unit 532, an inspection unit 533, a notification unit 534, a travel route acquisition unit 535, a travel cost acquisition unit 536, an item 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 cost output unit 542.

The transmission unit 55 includes a change transmission unit 551.

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

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

Various types of information are stored in the storage unit 51 constituting the information processing device 5. Examples of the various types of information include home location information (described later), workplace information (described later), regular schedule information (described later), mobile information (described later), commuting route information (described later), default information (described later), work information (described later), schedule information (described later), and performance information (described later).

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

The workplace information storage unit 512 stores one or more pieces of workplace information. The workplace information has a workplace identifier and location specification information. The workplace identifier is information that identifies the workplace, such as the workplace name, store name, and workplace ID. The location specification information is information that specifies the location of the workplace, such as the workplace location information (latitude, longitude), the workplace address, workplace name, workplace identifier, and store name.

The commuter pass information storage unit 513 stores one or more pieces of commuter pass information. The commuter pass information is associated with an employee identifier. The commuter pass information is information that specifies whether or not a commuter pass has been obtained. In other words, the commuter pass information is information that indicates whether or not an application for a commuter pass has been made and whether or not the commuter pass fee has been paid. The commuter pass information may be information that a commuter pass has been obtained, or information that a commuter pass has not been obtained.

The mobile object information storage unit 514 stores one or more pieces of mobile object information. Mobile object information is information that specifies the use of a mobile object (e.g., a personal car) for commuting. The mobile object information is stored in association with an employee identifier. Mobile objects are, for example, automobiles, motorcycles, and bicycles. Mobile object information is usually information indicating the use of a mobile object, but may also be information indicating that a mobile object is not used. Furthermore, using a mobile object for commuting usually means using an employee's mobile object for commuting, but the owner of the mobile object does not matter.

The commute route storage unit 515 stores one or more pieces of commute route information. Commuter route information is information that specifies a commute route. Commuter route information is associated with an employee identifier. Commuter route information has, for example, the name of the nearest station from home and the name of one or more transfer stations. Commuter route information has, for example, the name of the nearest station from home, the name of one or more transfer stations, and the name of the nearest station to the workplace. Commuter route information is, for example, "Home → Station A → Station B → Station C → Workplace" or "Station A → Station B → Station C." Commuter route information paired with an employee identifier for an employee who uses a mobile device to commute to work has, for example, location-specific information for the home and location-specific information for the 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 default actual information is associated with an employee identifier. The default schedule information or default actual information may be included in the commuting route information. The default schedule information or default actual information is, for example, location specific information of the employee's workplace. The default schedule information typically has location specific information of the workplace where the employee works. The default actual information typically has location specific information of the workplace where the employee works.

The work information storage unit 517 stores one or more types of information, including one or more pieces of schedule information described below and one or more pieces of actual performance information described below. It is preferable that the work information storage unit 517 stores one or more pieces of schedule information and one or more pieces of actual performance information.

The schedule information storage unit 5171 stores one or more schedule information. Schedule information is information related to an employee's work schedule. Schedule information has location specification information that specifies the work location. Schedule information is associated with an employee identifier. Schedule information has day information that specifies the day. Schedule information may be associated with day information. Note that one piece of information being associated with other information means that the other information can be obtained from one piece of information, one piece of information may include the other information, the other information may include one piece of information, one piece of information and the other information may be linked, one piece of information and the other information may be stored in the same buffer, etc.

The schedule information in the schedule information storage unit 5171 is, for example, information in which date information has been added to default schedule information, and may be information automatically generated by the processing unit 53. The schedule information in the schedule information storage unit 5171 may also be information received from the employee's terminal device 6.

The schedule information is, for example, shift schedule information that specifies work shifts. The shift schedule information has, for example, one or more records that have day information and a work location identifier that identifies the work location. The shift schedule information has, for example, one or more records that have day information and a first work location identifier that identifies the first work location at the start of a shift and a second work location identifier that identifies the second work location at the end of a shift. In other words, an employee may work at two or more locations in one day. In such cases, the employee will move between different work locations.

The performance information storage unit 5172 stores one or more pieces of performance information. The performance information is information related to the performance of an employee's work. The performance information has location-specific information. The performance information is associated with an employee identifier. The performance information has day information that specifies the day. The performance information may also be associated with day information.

The performance information in the performance information storage unit 5172 is, for example, information in which date information is added to default performance information, and may be information automatically generated by the processing unit 53. The performance information in the performance information storage unit 5172 may be information received from the employee's terminal device 6.

The performance information is, for example, one or more of entrance and exit information, sales activity information, input information, and employee location information. The entrance and exit information is information about an employee's entry into and exit from the workplace. The entrance and exit information corresponds to an employee identifier. The entrance and exit information includes, for example, day information that specifies a work day and work time information. The work time information includes, for example, a work start time and an end time. The sales activity information is information about sales activities. The sales activity information is, for example, information about the daily sales report. The sales activity information includes day information that specifies a work day and one or more pieces of location information. The sales activity information may include a character string indicating the content of the sales activity. The location information here is information that specifies the location visited. The location identifier is, 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 important. The input information is information entered by the employee to carry out his or her work. The input information corresponds to day information and time information. The time information is information about the time when the input information was entered. The employee location information is information that includes one or more pieces of location information received from a mobile terminal (here, terminal device 6) held by the employee.

The receiving unit 52 receives various types of information. The various types of information are, for example, schedule information, performance information, information regarding changes to default schedule information, and information regarding changes to default performance information. The various types of information are, for example, home location information, workplace information, commuter pass information, mobile information, commuting 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. The schedule receiving unit 521 receives schedule information from the terminal device 6, for example. The schedule receiving unit 521 receives schedule information that has been modified by an employee from the terminal device 6, for example. Note that modified schedule information is schedule information that 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 planned information that differs from the default performance information. For example, the performance receiving unit 522 receives performance information associated with an employee identifier from the entrance/exit information acquisition device 7. Such performance information includes entrance/exit information. Such performance information has location identification information. The performance receiving unit 522 receives sales activity information, input information, or employee location information including one or more location information from the terminal device 6.

The inspection result of the inspection unit 533 described below indicates that the inspection results do not match, and the notification unit 534 described below receives performance information from the terminal device 6 of the employee who was notified of the information regarding the inspection result. This performance information is performance information that the employee considers to be correct.

The processing unit 53 performs various types of processing. The various types of processing are, for example, processing performed by the change determination unit 530, the schedule accumulation unit 531, the performance accumulation unit 532, the inspection unit 533, the notification unit 534, the travel route acquisition unit 535, the travel cost acquisition unit 536, the subject determination unit 537, the re-inspection unit 538, and the re-processing unit 539.

The processing unit 53 performs different processes depending on the inspection result of the inspection unit 533 described below. For example, if the inspection result of the inspection unit 533 is that "the plan information and the actual performance information do not match," the processing unit 53 notifies the terminal device 6 corresponding to the employee identifier paired with the plan information or the actual performance information of information related to the inspection result. On the other hand, if the inspection result of the inspection unit 533 is that "the plan information and the actual performance information match," the processing unit 53 does not issue the notification.

For example, when the inspection result of the inspection unit 533 indicates that "the plan information and the actual performance information match," the processing unit 53 stores information about the inspection result in association with the plan information or the employee identifier that pairs with the actual performance information. On the other hand, when the inspection result of the inspection unit 533 indicates that "the plan information and the actual performance information do not match," the processing unit 53 does not perform the storage process.

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

The change determination unit 530 obtains default schedule information or default actual information corresponding to the employee identifier from the default storage unit 516, in which default schedule information or default actual information is stored in association with one or more employee identifiers, and compares the default schedule information or default actual information with the schedule information or actual information in the work information storage unit 517 to determine whether they are different. Note that the timing of this determination is not important.

The scheduled information or actual performance information in the work information storage unit 517 is the scheduled information or actual performance information that has been received, and may be information that will be stored in the work information storage unit 517 in the future.

The change determination unit 530 may determine whether information regarding modifications from the default schedule information has been received from the terminal device 6 in association with the employee identifier.

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

The schedule accumulation unit 531 accumulates schedule information in association with an employee identifier. The schedule accumulation unit 531 accumulates the schedule information received by the schedule receiving unit 521 in association with an employee identifier in the schedule information storage unit 5171 in association with the employee identifier.

The schedule accumulation unit 531 may use the received information regarding modifications to the default schedule information to obtain the modified schedule information and accumulate the modified schedule information in the schedule information storage unit 5171.

The performance accumulation unit 532 accumulates performance information in association with the employee identifier of the employee. The performance accumulation unit 532 accumulates the performance information received by the performance receiving unit 522 in association with the employee identifier in the performance information storage unit 5172 in association with the employee identifier.

The performance accumulation unit 532 is information regarding modifications from the default performance information, and may use the received information to obtain the modified performance information and accumulate the schedule information in the performance information storage unit 5172.

The inspection unit 533 uses the schedule information and actual performance information corresponding to the same day information that specifies the same day to inspect whether the schedule information and actual performance information match. The inspection unit 533 uses the schedule information and actual performance information corresponding to the same day information for each employee identifier to inspect whether the schedule information and actual performance information match.

The inspection unit 533 performs, for example, the following inspections (1) to (5).
(1) Checking the consistency of schedule information such as shift schedule information with store entry and exit information

The inspection unit 533 acquires one or more pieces of location-specific information included in the schedule information corresponding to the employee identifier of interest and the day information of the day to be processed from the schedule information storage unit 5171. The inspection unit 533 also acquires one or more pieces of location-specific information included in one or more pieces of store entry/exit information corresponding to the employee identifier of interest and the day information of the day to be processed from the performance information storage unit 5172. Next, the inspection unit 533 determines whether one or more locations specified by the one or more pieces of location-specific information included in the schedule information match one or more locations specified by the one or more pieces of location-specific information included in the one or more pieces of store entry/exit information. If they match, it is determined that the schedule information and the performance information match, and if even one does not match, it is determined that the schedule information and the performance information do not match.

If there are two or more work locations for an employee on that day, the inspection unit 533 acquires two or more locations specified by two or more location specifying information included in the schedule information in the order of work time, and acquires two or more locations specified by two or more location specifying information included in each of the two or more store entry and exit information in the order of work time. It then determines whether the two or more locations corresponding to the schedule information match the two or more locations corresponding to the performance information, including the order of the locations.

The location information included in the schedule information may be different data, for example, the store name, and the location information included in the performance information may be location information (latitude, longitude). In such a case, 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 judges whether the location information (latitude, longitude) and the location information (latitude, longitude) included in the performance information satisfy a predetermined proximity condition. The condition is that the distance between the two pieces of location information is equal to or smaller than a threshold value.
(2) Checking the consistency between schedule information such as shift schedule information and sales activity information

The inspection unit 533 acquires one or more pieces of location-specific information included in the schedule information associated with the employee identifier of interest and the day information of the day to be processed from the schedule information storage unit 5171. The inspection unit 533 also acquires one or more pieces of location-specific information included in the sales activity 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, in the sales activity information, a character string (e.g., "Company A, Company B") at a predetermined position (e.g., immediately after) for a clue term (e.g., <visited destination>) is acquired, and location-specific information (e.g., address, location information (latitude, longitude)) paired with the character string (e.g., "Company A" and "Company B") is acquired from the storage unit 51 or an external server not shown.

Next, the inspection unit 533 judges whether or not one or more locations specified by one or more location specifying information included in the schedule information match one or more locations specified by one or more location specifying information included in the sales activity information. If they match, it is judged that the schedule information and the performance information match, and if there is even one mismatch, it is judged that the schedule information and the performance information do not match. If there are two or more work locations for the employee on that day, the inspection unit 533 acquires two or more locations specified by two or more location specifying information included in the schedule information in the order of work time, and acquires two or more locations specified by two or more location specifying information included in the sales activity information in the order of work time (in order of appearance). It is then judged whether or not two or more locations corresponding to the schedule information match two or more locations corresponding to the performance information, including the order of the locations.

The location specifying information included in the schedule information may be, for example, a store name, and the location specifying information included in the performance information may be, for example, location information (latitude, longitude), and the two pieces of location specifying information may be different data.
(3) Checking the consistency between schedule information such as shift schedule information and work input information

The inspection unit 533 acquires one or more pieces of location-specific information included in the schedule information associated with the employee identifier of interest and the day information of the day to be processed from the schedule information storage unit 5171 in which shift schedule information is stored. The inspection unit 533 also acquires 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. Note that, for example, the input information is, for example, a file, and the day information is acquired from the update date and time information. Next, the inspection unit 533 acquires location-specific information (for example, location information (latitude, longitude)) that is paired with the acquired input information. Note that the input information is associated with the location-specific information where the information was input.

Next, the inspection unit 533 judges whether or not one or more locations specified by one or more location specifying information included in the schedule information match one or more locations specified by one or more location specifying information corresponding to the input information. If they match, it is judged that the schedule information and the actual information match, and if even one of them does not match, it is judged that the schedule information and the actual information do not match.

If there are two or more work locations for the employee on that day, the inspection unit 533 acquires two or more locations specified by two or more location identification information included in the schedule information in the order of work time, and acquires two or more locations specified by two or more location identification information corresponding to the input information in the order of work time (order of update date and time). Then, it determines whether the two or more locations corresponding to the schedule information and the two or more locations corresponding to the performance information match, including the order of the locations.

The location specifying information included in the schedule information may be, for example, a store name, and the location specifying information included in the performance information may be, for example, location information (latitude, longitude), and the two pieces of location specifying information may be different data.
(4) Checking the consistency of schedule information such as shift schedule information with employee location information

The inspection unit 533 acquires one or more pieces of location-specific information included in the schedule information that corresponds to the employee identifier of interest and the day information of the day to be processed from the schedule information storage unit 5171. The inspection unit 533 also acquires all employee location information that corresponds to the employee identifier of interest and the day information of the day to be processed from the performance information storage unit 5172. The employee location information is location information received from the employee's terminal device 6, and corresponds to date and time information.

Next, the inspection unit 533 acquires a workplace identifier corresponding to the acquired employee location information from the workplace information storage unit 512. The inspection unit 533 acquires location specification information (e.g., location information (latitude, longitude)) corresponding to the workplace identifier, and if it determines that the distance between the location information and the employee location information is within or less than a threshold, it determines that the workplace identified by the workplace identifier is the workplace where the employee was located. The inspection unit 533 then determines whether one or more workplace identifiers acquired using the employee location information match, including the order, with the workplace identifiers indicated by one or more location specification information included in the schedule information. If they match, it is determined that the schedule information and actual information match, and if even one does not match, it is determined that the schedule information and actual information do not match.

As mentioned above, the decision taking into consideration the order applies when an employee works at two or more work locations.
(5) In the case of working from home

When the inspection unit 533 determines that information indicating telecommuting is present in the plan information corresponding to the employee identifier of interest and the day information of the day being processed, and when a workplace identifier or information corresponding to a workplace identifier is present in the location-specific information in the actual information corresponding to the employee identifier of interest and the day information of the day being processed, the inspection unit 533 determines that the plan information and actual information do not match.

When the inspection unit 533 determines that there is information indicating telecommuting in the schedule information associated with the employee identifier of interest and the day information of the day to be processed, it acquires all employee location 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. Next, the inspection unit 533 acquires home point information paired with the employee identifier from the home point storage unit 511. It then determines whether the distance between the location information corresponding to the acquired home point information and the employee location information satisfies a specified condition. If the specified condition is satisfied, the schedule information and the performance information match, and if the specified condition is not satisfied, the schedule information and the performance information do not match. The specified condition is that the distance between the two points indicated by both pieces of location information is within a threshold or is smaller than the threshold.

When the inspection result in the inspection unit 533 indicates a mismatch, the notification unit 534 notifies the employee identified by the employee identifier corresponding to the inspection result of information related to the inspection result. Note that the notification unit 534 may also notify the employee of information related to the inspection result when the inspection result in the inspection unit 533 indicates a match. Furthermore, the information related to the inspection result is, for example, the inspection result, information on a screen that prompts the input of correct schedule information, and information on a screen that prompts the input of the reason for the mismatch, etc. Note that the notification provided by the notification unit 534 may be a notification in response to a user instruction, or a spontaneous notification. In other words, the notification may be of the push type or the pull type.

The travel route acquisition unit 535 acquires one or more location-specific information from one or more types of information among the schedule information or actual performance information stored in the work information storage unit 517, which corresponds to an employee identifier and day information, and acquires travel route information using the one or more location-specific information.

Travel route information is information related to the travel route of an employee identified by an employee identifier. Travel route information is information that has one or more pieces of location-specific information, or information that can be obtained from one or more pieces of location-specific information. Examples of travel route information are "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 and location identification information corresponding to one or more workplaces from the schedule information or performance information, passes the location identification information corresponding to the home and location identification information corresponding to one or more workplaces to a server that returns travel route information (for example, the server in Non-Patent Document 1, the NAVITIME (registered trademark) server [URL: https://www.navitime.co.jp/]), and receives the travel route information from the server. The server is accessed using, for example, an API, but the connection method is not important.

For example, when the schedule information or performance information has day information, a first workplace identifier that identifies a first workplace at the start of work, and a second workplace identifier that identifies a second workplace at the end of work (when the schedule information is information indicating that an employee works at two or more workplaces in one day), the travel route acquisition unit 535 acquires, for example, home location information corresponding to the employee identifier from the home location storage unit 511, and also acquires first location specification information that pairs with the first workplace identifier corresponding to the employee identifier from the workplace information storage unit 512. Next, the travel route acquisition unit 535 acquires first travel route information from the home to the workplace at the start of work using the home location information and the first location specification information. The travel route acquisition unit 535 may also acquire commuting route information corresponding to the employee identifier from the commuting route storage unit 515, and acquire first travel route information from "home to workplace" using the commuting route information. The travel route acquisition unit 535 may also pass the home location information and the first location identification information to a server (not shown) that returns travel route information, and receive the first travel route information from the server.

The travel route acquisition unit 535 also acquires second location identification information that pairs with the second workplace identifier from the workplace information storage unit 512. The travel route acquisition unit 535 also acquires second travel route information from the first workplace to the second workplace using the first location identification information and the second location identification information. The travel route acquisition unit 535 may, for example, pass the first location identification information and the second location identification information to a server that returns the travel route information, and receive the second travel route information from the 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 workplace to the home. 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 the commuting route information to acquire third travel route information from "workplace to home." The travel route acquisition unit 535 may also 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 the server.

In addition, information having day 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 is, for example, shift schedule information.

The travel route acquisition unit 535 acquires mobile object information corresponding to the employee identifier from the mobile object information storage unit 514. The travel route acquisition unit 535 determines whether the mobile object information is information indicating the use of a mobile object for commuting. If the mobile object information is information indicating the use of a mobile object for commuting, the travel route acquisition unit 535 acquires travel route information specifying a road route from the home to the workplace using one or more types of information among the schedule information and the actual information and the home location information corresponding to the employee identifier. If the mobile object information is information indicating the use of a mobile object for commuting, the travel route acquisition unit 535 reads out, for example, the commuting route information stored in the commuting route storage unit 515, which is travel route information specifying a road route from the home to the workplace. If the mobile object information is information indicating the use of a mobile object for commuting, the travel route acquisition unit 535 may, for example, pass the home location information and the workplace location specification information to a server (not shown) that returns travel route information specifying a road route, and receive travel route information specifying a road route from the home to the workplace from the server.

It is preferable that the travel route acquisition unit 535 uses 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 preferable that the travel route acquisition unit 535 queries different servers when acquiring travel route information that specifies a road route and when acquiring travel route information that specifies a transportation route.

The movement route acquisition unit 535 acquires movement route information for each day and for each employee identifier. The timing at which the movement route acquisition unit 535 acquires the movement route information is not important.

The travel route acquisition unit 535 may acquire travel route information using performance information or may acquire travel route information using schedule information.

It is preferable that the travel route acquisition unit 535 acquires travel route information using the scheduled information or the actual information only when the inspection unit 533 obtains an inspection result indicating that the scheduled information and the actual information match.

The travel expense acquisition unit 536 acquires travel expense information that identifies travel expenses using the schedule information or actual performance information. The travel expense acquisition unit 536 acquires travel expense information that identifies travel expenses, for example, using travel route information acquired by the travel route acquisition unit 535. Note that travel expenses are expenses related to travel for an employee's business. Travel expenses are, for example, expenses incurred for travel. Travel expenses are typically expenses that should be borne by the company. Travel expenses are typically commuting expenses or transportation expenses.

The timing at which the travel expense acquisition unit 536 acquires the travel expense information does not matter. The travel expense acquisition unit 536 may acquire the travel expense information at the same time as the travel route acquisition unit 535 acquires the travel route information. In other words, one or more pieces of location identification information acquired using the schedule information or performance information may be passed to a server (not shown), and the travel route information and travel expense information may be received from the server at the same time. Even in such cases, the travel expense information is usually acquired using the travel route information.

The travel expense acquisition unit 536 acquires commuter pass information corresponding to the employee identifier from the commuter pass information storage unit 513. Next, the travel expense acquisition unit 536 determines whether the commuter pass information is information indicating that a commuter pass has been acquired. Then, if the commuter pass information is information indicating that a commuter pass has been acquired and the travel expense information is determined by the item determination unit 537 to correspond to an item related to commuting expenses, the travel expense acquisition unit 536 acquires travel expense information of "0".

The travel expenses acquisition unit 536 acquires mobile object information corresponding to the employee identifier from the mobile object information storage unit 514. Next, the travel expenses acquisition unit 536 determines whether the mobile object information is information indicating the use of a mobile object for commuting. If the mobile object information is information indicating the use of a mobile object for commuting and the subject determined by the subject determination unit 537 is determined to be a subject related to commuting expenses, the travel expenses acquisition unit 536 acquires travel expenses information of "0".

The travel cost acquisition unit 536 passes one or more pieces of location-specific information contained in the travel route information, or information obtained from the one or more pieces of location-specific information, to a server (not shown) (for example, the server in Non-Patent Document 1, the NAVITIME (registered trademark) server [URL: https://www.navitime.co.jp/]) and acquires the travel costs between the points from the server. The travel cost acquisition unit 536 then totals the travel costs between the points and acquires the travel cost information. Note that the server can be accessed using, for example, an API, but the connection method is not important.

The account determination unit 537 obtains commuting route information corresponding to the employee identifier from the commuting route storage unit 515. Using the commuting route information and the location specification information contained in the travel route information corresponding to the employee identifier, the account determination unit 537 determines 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. Note that an account related to commuting expenses is usually "commuting expenses." Also, an account related to transportation expenses is usually "transportation expenses" or "travel expenses." However, the name of the account does not matter. Also, the location specification information contained in the travel route information corresponding to the employee identifier is, for example, the location specification information contained in the actual result information, but it may also be the location specification information contained in the schedule information.

The subject determination unit 537 determines, for example, that travel expense information corresponding to information about a partial route in the travel route information that overlaps with the commute route information corresponds to a subject related to commute expenses. Also, the subject determination unit 537 determines, for example, that travel expense information corresponding to information about a partial route in the travel route information that does not overlap with the commute route information corresponds to a subject related to transportation expenses.

The subject determination unit 537 determines, for example, that among the travel route information, travel expense information corresponding to travel route information from start point location information corresponding to the home to end point location information corresponding to the workplace corresponds to an subject related to commuting expenses. The subject determination unit 537 determines, for example, that travel expense information corresponding to travel route information from start point location information corresponding to the workplace to end point location information corresponding to the home corresponds to an subject related to commuting expenses. The subject determination unit 537 determines, for example, that travel expense information corresponding to a route other than such a route corresponds to an subject related to transportation expenses.

For example, if the travel route information indicates "Home → Workplace X → Home," the account determination unit 537 determines that the travel expense information corresponding to the route "Home → Workplace X" and the travel expense information corresponding to "Workplace X → Home" are both classified 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 that 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" are to be classified as "commuting expenses." On the other hand, the account determination unit 537 determines that the travel expense information corresponding to "Workplace X → Station B → Station C → Workplace Y" is to be classified as "transportation expenses." In this way, it is preferable for the account determination unit 537 to determine that the travel expense information corresponding to some routes is commuting expenses and the travel expense information corresponding to other routes is transportation expenses.

The re-inspection unit 538 judges whether the inspection result of the inspection unit 533 is a result of an inspection that indicates a mismatch, and whether the performance information received from the terminal device 6 of the employee to whom the notification unit 534 notified the information regarding the inspection result satisfies a predetermined condition. The predetermined condition is, for example, a match with the planned information, inclusion of information on a predetermined item (e.g., a reason for the mismatch, information indicating that there is no problem, etc.), inclusion of predetermined information (e.g., information indicating that the supervisor has approved), inclusion of information with a data amount equal to or greater than a threshold (e.g., a sufficient description of the reason), receipt of the performance information within a predetermined time after notification of the inspection result of a mismatch, etc.

The re-inspection unit 538 may perform the same processing as the inspection unit 533. In such a case, the predetermined condition is that the information matches the schedule information.

The reprocessing unit 539 performs different processing depending on the result of the judgment in the reexamination unit 538. For example, if the result of the reexamination by the reexamination unit 538 satisfies a predetermined condition, the reprocessing unit 539 pairs the received performance information with the employee identifier and stores it in the performance information storage unit 5172. Also, if the result of the reexamination by the reexamination unit 538 does not satisfy the predetermined condition, the reprocessing unit 539 does not store the received performance information. If the result of the reexamination by the reexamination unit 538 does not satisfy the predetermined condition, the reprocessing unit 539 notifies the employee identified by the employee identifier, for example, of information that the result of the reexamination was "inappropriate". Also, if the result of the reexamination by the reexamination unit 538 satisfies the predetermined condition, the reprocessing unit 539 notifies the employee identified by the employee identifier, for example, of information that the result of the reexamination was "appropriate". Also, if the result of the reexamination by the reexamination unit 538 satisfies the predetermined condition, the reprocessing unit 539 does not, for example, provide any notification.

The output unit 54 outputs various information. Examples of the various information include travel route information, travel cost information, and test results. Test results are information related to the test results in the test unit 533.

In this case, output usually means transmission to another device (e.g., terminal device 6), but it may also be a concept that includes passing the processing results to other processing devices or other programs, showing them on a display, projecting them using a projector, printing them on a printer, outputting them as sound, storing them on a recording medium, etc.

The movement route output unit 541 outputs the movement route information acquired by the movement route acquisition unit 535. The movement route output unit 541 usually outputs the movement route information in association with an employee identifier and day information. The movement route output unit 541 outputs, for example, the first movement route information, the second movement route information, and the third movement route information acquired by the movement route acquisition unit 535. Here, output may mean transmission to another device (for example, terminal device 6), a process of passing to another module, storage in the storage unit 51, etc.

The travel expense output unit 542 outputs the travel expense information acquired by the travel expense acquisition unit 536. The travel expense output unit 542 typically outputs the travel expense information in association with an employee identifier and day information.

It is preferable that the travel expense output unit 542 outputs travel expense information in association with subject identification information that identifies the subject determined by the subject determination unit 537. Note that the subject identification information is, for example, "transportation expenses," "commuting expenses," "travel expenses," etc., or an ID that identifies the subject.

For example, if the subject determined by the subject determination unit 537 is determined to be a subject related to transportation expenses, the travel expense output unit 542 performs processing to accumulate the travel expense information in the transportation expense database 81 that manages transportation expenses in association with the employee identifier. For example, if the travel expense output unit 542 determines that the subject determined by the subject determination unit 537 is a subject related to commuting expenses, the travel expense output unit 542 does not perform processing to accumulate the travel expense information in the transportation expense database 81.

For example, if the subject determined by the subject determination unit 537 is determined to be a subject related to commuting expenses, the travel expense output unit 542 performs processing to accumulate travel expense information in the commuting expenses database 91, which manages commuting expenses.

When the travel expense acquisition unit 536 acquires travel expense information that is not "0" and the subject determination unit 537 determines that the subject determined is a subject related to commuting expenses, the travel expense output unit 542 performs processing to accumulate the travel expense information in the commuting expenses database 91 that manages commuting expenses.

The transportation expenses database may exist in the information processing device 5 or in the accounting information management device 8. The commuting expenses database may exist 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. The various types of information are change information. The change information is information indicating that the default schedule information or the default actual information has been changed. The change information is, for example, corrected schedule information, corrected actual information, information on the parts of the default schedule information that have been corrected, and information on the parts of the default actual information that have been corrected.

When the default schedule information or the default performance information is changed, the change sending unit 551 sends the change information to the contacts indicated by one or more pieces of contact information corresponding to the employee identifier.

For example, if the change determination unit 530 determines that there is a difference, the change sending unit 551 sends the change information to the contacts indicated by one or more pieces of contact information corresponding to the employee identifier.

The change information is information that indicates that the schedule information has been changed from the default schedule information, or information that indicates that the actual information has been changed from the default schedule information. The contact information may be any information that indicates a contact, such as the IP address of the terminal device 6, the MAC address of the terminal device 6, the employee's email address, the telephone number of the terminal device 6, or an ID. The contact information is stored in the storage unit 51 in association with the employee identifier.

The terminal storage unit 61 constituting the terminal device 6 stores various types of information. The various types of information are, for example, employee identifiers.

The terminal reception unit 62 receives various instructions and information. The various instructions and information are, for example, schedule information, performance information (e.g., sales activity information, input information), modification of default schedule information, and modification of default performance information. It is preferable that the terminal reception unit 62 receives schedule information that has been modified from the default schedule information. It is preferable that the terminal reception unit 62 receives performance information that has been modified from the default performance information.

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

The device processing unit 63 performs various types of processing. For example, various types of processing are processing to convert instructions and information accepted by the device accepting unit 62 into instructions and information with a data structure to be transmitted. For example, various types of processing are processing to convert information received by the device receiving unit 65 into information with a data structure to be output.

The terminal transmission unit 64 transmits various instructions and information. The various instructions and information are, for example, schedule information, performance information, details of corrections to schedule information, and details of corrections to performance information.

The terminal receiving unit 65 receives various types of information. The various types of information include, for example, travel route information, travel cost information, and test results. Note that the test results may be information on a screen that prompts the user to enter correct performance information.

The terminal output unit 66 outputs various information, such as travel route information, travel cost information, and test results.

Here, output is a concept that includes displaying on a display, projecting using a projector, printing on a printer, outputting sound, sending to an external device, storing on a recording medium, and passing on the processing results to other processing devices or other programs, etc.

The card reader 71 constituting the entrance/exit information acquisition device 7 is a device that reads an employee identifier from a card (e.g., an IC card) on which the employee identifier is stored. The entrance/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-specific information of the workplace held by the entrance/exit information acquisition device 7 to the information processing device 5.

The card reader 71 is, for example, an IC card reader, but is a means for acquiring an employee identifier from a medium (card, mobile terminal, etc.) on which the employee identifier is stored via short-range wireless communication such as Bluetooth (registered trademark).

The travel expense database 81 constituting the accounting information management device 8 stores travel expense information corresponding to the item "travel expenses" in association with an employee identifier. The travel expense information in the travel expense database 81 is usually associated with day information. 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 item "travel expenses" in association with an employee identifier.

The commuting expenses database 91 constituting the personnel information management device 9 stores travel expense information corresponding to the item "commuting expenses" in association with an employee identifier. The travel expense information in the commuting expenses database 91 is usually associated with day information. The travel expense information may also be associated with travel route information. It is preferable that the personnel information management device 9 stores information related to employee personnel in addition to the travel expense information corresponding to the item "commuting expenses."

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

The process by which information is stored in the storage unit 51, etc. is not important. 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 inputted 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 typically realized by wireless or wired communication means, but may also be realized by means of receiving broadcasts.

The processing unit 53, change determination unit 530, schedule accumulation unit 531, result accumulation unit 532, inspection unit 533, travel route acquisition unit 535, travel cost acquisition unit 536, subject determination unit 537, re-inspection unit 538, re-processing unit 539, and terminal processing unit 63 can usually be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are usually realized by software, and the software is recorded in a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor is, for example, a CPU, MPU, GPU, etc., and the type does not matter.

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

The terminal reception unit 62 can be realized by a device driver for an input means such as a touch panel or keyboard, or control software for a menu screen, etc.

The terminal output unit 66 may or may not include an output device such as a display or speaker. The terminal output unit 66 may be realized by driver software for an output device, or by a combination of driver software for an output device and an output device, etc.

Next, an example of the operation of information system B will be described. First, an example of the operation of information processing device 5 will be described using the flowchart in FIG. 14.

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

The information regarding the modification of the schedule information may be the modified schedule information or information on the modified parts of the default schedule information. Here, the change determination unit 530 may obtain the default schedule information that is paired with 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 change information to be sent. The processing unit 53 acquires an employee identifier. The processing unit 53 acquires one or more pieces of contact information corresponding to the employee identifier from the storage unit 51. The change sending unit 551 sends the acquired change information to one or more contacts identified by each of the one or more pieces of contact information. Return to step S1401.

The contact person may, for example, be a superior. The contact person may, for example, be the employee in question. The change information here may be information indicating that the schedule information has been changed from the default information, or it may be the changed schedule information.

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

The information regarding the modification of the performance information may be the modified performance information or information on the parts that have been modified from the default performance information. Here, the change determination unit 530 may also obtain default performance information that pairs with the employee identifier from the default storage unit 516, and determine whether the default performance information and the received performance information are different or the same.

(Step S1404) The processing unit 53 uses the information received in step S1403 to construct change information to be sent. The processing unit 53 acquires an employee identifier. The processing unit 53 acquires one or more pieces of contact information corresponding to the employee identifier from the storage unit 51. The change sending unit 551 sends the change information to one or more contacts identified by each of the one or more pieces of contact information. Return to step S1401.

The contact information may include, for example, the superior. The contact information may also include, for example, the employee. The change information here is information indicating that the performance information has been changed from the default information, and may also be the changed performance information.

(Step S1405) The processing unit 53 judges whether it is time to check whether the scheduled information and the actual information match. If it is time to check, the process proceeds to step S1406, and if it is not time to check, the process proceeds to step S1414.

The processing unit 53 determines that it is time to perform an inspection, for example, when a predetermined time (for example, the last working hour [for example, 10 p.m.]) arrives or when performance information is received.

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

(Step S1407) The processing unit 53 determines whether or not the i-th employee to be inspected exists. If the i-th employee to be inspected exists, the process proceeds to step S1408, and if the i-th employee to be inspected does not exist, the process returns to step S1401.

(Step S1408) The inspection unit 533 pairs with the employee identifier of the i-th inspection target employee and checks whether the schedule information and actual performance information corresponding to the day information of the target day match. An example of such inspection processing will be described using the flowchart in FIG. 15.

(Step S1409) The processing unit 53 determines whether or not the scheduled information and actual information match as a result of the inspection in step S1408. If they match, the process proceeds to step S1410, and if they do not match, the process proceeds to step S1413. Note that a match means that the inspection result is valid.

(Step S1410) The processing unit 53 performs a process for acquiring travel routes, etc. An example of the process for acquiring travel routes, etc. is described with reference to the flowchart in FIG. 16. The process for acquiring travel routes, etc. is a process for acquiring travel route information, a process for acquiring travel expense information, and a process for determining the category of travel expenses.

(Step S1411) The movement route output unit 541 outputs the movement route information acquired in step S1410 in association with the employee identifier. For example, the movement route output unit 541 notifies the employee identified by the employee identifier of the movement route information. For example, the movement route output unit 541 notifies the contacts indicated by one or more pieces of contact information paired with the employee identifier of the movement route information. For example, the movement route output unit 541 accumulates the movement route information in the storage unit 51, etc. in association with the employee identifier and date information.

Here, the travel expense output unit 542 may output travel expense information in association with the employee identifier. The travel expense output unit 542 may also output the item and travel expense information in association with the employee identifier.

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

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

The notification unit 534 may send a screen or the like that prompts the employee (terminal device 6) identified by the employee identifier to input correct performance information. The notification unit 534 may also send information that the test results did not match to a contact point indicated by one or more pieces of contact information that correspond to the employee identifier. The information that the test results did not match may be considered to include information on a screen that prompts the employee to input correct performance information and information on a screen that prompts the employee to input the reason for the non-match.

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

(Step S1415) The retest unit 538 etc. performs processing such as retesting. Return to step S1401. Such processing such as retesting will be explained using the flowchart in FIG. 20.

(Step S1416) The performance receiving unit 522 determines whether performance information has been received in association with the employee identifier. If performance information has been received, the process proceeds to step S1417; if performance information has not been received, the process returns to step S1401.

The performance information received here may be, for example, one or more of the following: entrance and exit information, sales activity information, input information entered by employees to carry out their work, and employee location information including one or more location information.

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

The output unit 54 normally acquires the day information, associates it with the day information, and accumulates the information received in step S1416 in the performance information storage unit 5172. The output unit 54 may acquire the day information from a clock (not shown), or may acquire the day information received together with the performance information.

In the flowchart in Figure 14, processing ends when the power is turned off or an interrupt occurs to end processing.

Next, an example of the inspection process in step S1408 will be described using the flowchart in FIG.

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

(Step S1502) The inspection unit 533 acquires schedule information that is paired with the employee identifier acquired in step S1501 and is paired with the day information of the target day from the schedule information storage unit 5171. Note that the inspection unit 533 may acquire the day information of the target day from a clock (not shown), or may acquire day information received together with other information such as performance information.

(Step S1503) The inspection unit 533 acquires performance information that is paired with the employee identifier acquired in step S1501 and is paired with the day information of the target day from the performance information storage unit 5172. Note that the inspection unit 533 may acquire performance information that was received immediately before.

(Step S1504) The inspection unit 533 determines whether the schedule information acquired in step S1502 is information indicating work. If it is information indicating work, the process proceeds to step S1505, and if it is not information indicating work, the process proceeds to step S1515. Note that information indicating work refers to information on a day on which the user will work, and not information on a day off.

For example, if the schedule information has one or more pieces of location-specific information, the inspection unit 533 determines that the schedule information is information indicating work. For example, if the schedule information indicates "annual leave" or "holiday" or is "NULL," the inspection unit 533 determines that the schedule information is not information indicating work.

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

(Step S1506) The inspection unit 533 determines whether the i-th location identification information is present in the schedule information acquired in step S1502. If the i-th location identification information is present, the process proceeds to step S1507, and if the i-th location identification information is not present, the process proceeds to step S1513.

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

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

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

(Step S1510) The inspection unit 533 determines whether the i-th location identification information in the schedule information matches the i-th location identification information in the performance information. If they match, the process proceeds to step S1511; if they do not match, the process proceeds to step S1512.

If the data type of the ith location identification information in the schedule information does not match the data type of the ith location identification information in the performance information, the inspection unit 533 matches the types of both data and then judges whether the two data match. The types of both data do not match, for example, when one is (latitude, longitude) and the other is a workplace identifier. In such a case, the inspection unit 533 acquires, for example, a workplace identifier that pairs with the (latitude, longitude) closest to one (latitude, longitude) from the workplace information storage unit 512. Alternatively, the inspection unit 533 acquires a (latitude, longitude) that pairs with the workplace identifier from the workplace information storage unit 512, and judges whether the distance between the (latitude, longitude) and the (latitude, longitude) of the other information is within a threshold or is smaller than the threshold.

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

(Step S1512) The inspection unit 533 assigns "information indicating no match" to the variable "inspection result". It then returns to the upper process.

(Step S1513) The inspection unit 533 determines whether the i-th location identification information is present in the performance information acquired in step S1503. If the i-th location identification information is present, the process proceeds to step S1512, and if the i-th location identification information is not present, the process proceeds to step S1514.

(Step S1514) The inspection unit 533 assigns the "match information" to the variable "inspection result". It then returns to the upper process.

(Step S1515) The inspection unit 533 determines whether the performance information acquired in step S1503 is performance information indicating that work has been performed. If the performance information is performance information indicating that work has been performed, the process proceeds to step S1512, and if the performance information is not performance information indicating that work has been performed, the process proceeds to step S1514.

Next, an example of the process of acquiring travel routes, etc. in step S1410 will be described using the flowchart in FIG. 16.

(Step S1601) The travel route acquisition unit 535 acquires the employee identifier of the employee for whom travel route information, etc. is to be acquired.

(Step S1602) The travel route acquisition unit 535 acquires, from the work information storage unit 517, schedule information or actual performance information that is paired with the employee identifier acquired in step S1601 and that is paired with the day information for the day for which travel route information, etc. is to be acquired. The travel route acquisition unit 535 acquires the first location identification information excluding the home from the schedule information or actual performance information acquired in step S1602. Note that the location identification information is stored in the schedule information or actual performance information in the order of the locations to which the employee has traveled.

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

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

(Step S1605) The travel route acquisition unit 535 determines whether the i-th location identification information is present in the schedule information or performance information acquired in step S1602. If the i-th location identification information is present, the process proceeds to step S1606, and if the i-th location identification information is not present, the process proceeds to step S1609.

(Step S1606) The travel route acquisition unit 535 acquires the i-th point identification information excluding the home from the schedule information or performance information acquired in step S1602.

(Step S1607) The travel route acquisition unit 535 etc. acquires travel route information etc. between two workplaces. This process is called the workplace route etc. acquisition process. The workplace route etc. acquisition process will be explained using the flowchart in FIG. 18.

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

(Step S1609) The travel route acquisition unit 535 etc. acquires travel route information etc. from the last workplace identified by the last ("i-1"th) point identification information to the home. Return to the upper process. This process is called the home route etc. acquisition process. The home route etc. acquisition process will be explained using the flowchart in FIG. 19.

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

(Step S1701) The movement route acquisition unit 535 attempts to acquire moving object information that pairs with the employee identifier of the target employee from the moving object information storage unit 514. Note that there may be cases where moving object information that pairs with the employee identifier cannot be acquired.

(Step S1702) The travel route acquisition unit 535 judges whether the mobile object information acquired in step S1701 is information indicating that a mobile object (e.g., personal car) is used for commuting. If the information indicates that a mobile object is used for commuting, the process proceeds to step S1703, and if the information indicates that a mobile object is not used for commuting, the process proceeds to step S1705. Note that if mobile object information could not be acquired in step S1701, the process generally proceeds to step S1705.

(Step S1703) The travel route acquisition unit 535 uses the first travel route information indicating "Home → Workplace corresponding to the first location identification information (using a mobile object)". The first travel route information is a part of the travel route information that is finally output.

(Step S1704) The travel expense acquisition unit 536 acquires travel expense information "0" in association with the first travel route information acquired in step S1703. The process returns to the upper level process. Note that here, the subject determination unit 537 may acquire the subject "commuting expenses".

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

(Step S1706) The travel expense acquisition unit 536 acquires the regular schedule information paired with the employee identifier of the target employee from the regular schedule information storage unit 513. Note that the travel expense acquisition unit 536 may not be able to acquire the regular schedule information.

(Step S1707) The travel expense acquisition unit 536 determines whether the commuter pass information acquired in step S1706 is information indicating that a commuter pass has been obtained. If the information indicates that a commuter pass has been obtained, the process proceeds to step S1708; if the information does not indicate that a commuter pass has been obtained, the process proceeds to step S1709. Note that if the commuter pass information could not be acquired in step S1706, the process generally proceeds to step S1709.

(Step S1708) The travel expense acquisition unit 536 acquires travel expense information "0". The process returns to the upper level process. Note that here, the subject decision unit 537 may acquire the subject "commuting expenses".

(Step S1709) The travel expense acquisition unit 536 acquires travel expense information from the home to the workplace corresponding to the first location identification information. The travel expense acquisition unit 536 acquires, for example, travel expense information paired with the employee identifier of the target employee from the storage unit 51, travel expense information from the home to the workplace. 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 the travel expense information or the travel expense information that is the basis of the travel expense information, and acquires the travel expense information. The server is, for example, a server having the technology of Non-Patent Document 1, which is a publicly known technology.

(Step S1710) The item determination unit 537 obtains the item "commuting expenses."

(Step S1711) The travel expense output unit 542 performs processing to associate the travel expense information acquired in step S1709 with the item "commuting expenses" acquired in step S1710 and the employee identifier, and accumulates the information in the commuting expenses database 91. It then returns to the upper-level processing.

The travel expense output unit 542 transmits, for example, the employee identifier, the day 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, the day information, and the travel expense information, and stores the travel expense information in the commuting expense database 91 in association with the employee identifier and the day information.

Next, the process of obtaining routes between workplaces in step S1607 will be explained using the flowchart in FIG. 18.

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

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

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

(Step S1804) The subject determination unit 537 obtains the subject "Transportation expenses."

(Step S1805) The travel expense output unit 542 performs processing to associate the travel expense information with the item "travel expenses" and the employee identifier, and accumulates it in the travel expense database 81. It then returns to the upper-level processing.

The travel expense output unit 542, for example, transmits the travel expense information, the employee identifier, and the day information to the accounting information management device 8. The accounting information management device 8 receives the travel expense information, the employee identifier, and the day information, and stores the travel expense information in the transportation expense database 81 in association with the employee identifier and the day information.

Next, the process of obtaining the route home, etc. in step S1609 will be explained using the flowchart in FIG. 19.

(Step S1901) The movement route acquisition unit 535 attempts to acquire moving object information that pairs with the employee identifier of the target employee from the moving object information storage unit 514. Note that there may be cases where moving object information that pairs with the employee identifier cannot be acquired.

(Step S1902) The travel route acquisition unit 535 determines whether the mobile object information acquired in step S1901 is information indicating that a mobile object (e.g., personal car) is used for commuting. If the information indicates that a mobile object is used for commuting, the process proceeds to step S1903, and if the information indicates that a mobile object 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 corresponding to the last location identification information → home (using a mobile device)". The third travel route information is a part of the travel route information that is finally output.

(Step S1904) The travel expense acquisition unit 536 acquires travel expense information "0" in association with the third travel route information acquired in step S1903. The process returns to the upper level process. Note that here, the item determination unit 537 may acquire the item "commuting expenses".

(Step S1905) The travel route acquisition unit 535 acquires commuting route information from the home to the workplace that is paired with the employee identifier of the target employee from the commuting route storage unit 515. Note that such commuting route information is, for example, "Workplace X → Station B → Station A → Home."

(Step S1906) The travel expense acquisition unit 536 acquires the regular schedule information paired with the employee identifier of the target employee from the regular schedule information storage unit 513. Note that the travel expense acquisition unit 536 may not be able to acquire the regular schedule information.

(Step S1907) The travel expense acquisition unit 536 determines whether the commuter pass information acquired in step S1906 is information indicating that the user has a commuter pass. If the information indicates that the user has a commuter pass, the process proceeds to step S1908. If the information does not indicate that the user has a commuter pass, the process proceeds to step S1909.

(Step S1908) The travel expense acquisition unit 536 acquires travel expense information "0". The process returns to the upper level process. Note that here, the subject determination unit 537 may acquire the subject "commuting expenses".

(Step S1909) The travel expense acquisition unit 536 acquires travel expense information from the last workplace to the home. The travel expense acquisition unit 536 acquires, for example, travel expense information paired with the employee identifier of the target employee, travel expense information from the workplace to the home, from the storage unit 51. The travel expense acquisition unit 536 also 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 is the basis of the travel expense information, and acquires the travel expense information.

(Step S1910) The item determination unit 537 obtains the item "commuting expenses."

(Step S1911) The travel expense output unit 542 performs processing to associate the travel expense information acquired in step S1909 with the item "commuting expenses" acquired in step S1910 and the employee identifier, and accumulates the information in the commuting expenses database 91. It then returns to the upper-level processing.

The travel expense output unit 542 transmits, for example, the employee identifier, the day 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, the day information, and the travel expense information, and stores the travel expense information in the commuting expense database 91 in association with the employee identifier and the day information.

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

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

(Step S2002) The retest unit 538 acquires the received information.

(Step S2003) The retest unit 538 acquires the predetermined conditions from the storage unit 51.

(Step S2004) The re-examination unit 538 determines whether the information acquired in step S2002 satisfies the condition acquired in step S2003. If the condition is satisfied, the process proceeds to step S2005; if the condition is not satisfied, the process proceeds to step S1413.

(Step S2005) The reprocessing unit 539 associates the information acquired in step S2002 with the employee identifier and day information, and returns it to the upper process where it is accumulated in the storage unit 51.

In the flowchart of FIG. 20, the re-examination unit 538 may determine whether or not performance information has been received by the scheduled time from the terminal device 6 of the employee to whom the notification unit 534 has notified information relating to the inspection result, when the inspection result from the inspection unit 533 indicates a mismatch. It is preferable that the re-processing unit 539 performs different processing depending on whether or not performance information has been received by the scheduled time.

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

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

(Step S2102) The device processing unit 63 acquires the employee identifier from the device storage unit 61, and constructs information having the employee identifier and information related to the correction of the schedule information or the performance information. The device 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 information has been received from the information processing device 5. If information has been received, the process proceeds to step S2104, and if information has not been received, the process proceeds to step S2105. Note that the information here is, for example, default schedule information, default performance information, travel route information, travel expense information, and subject.

(Step S2104) The device processing unit 63 converts the information received in step S2103 into information structured to be output. The terminal output unit 66 outputs the information. Return to step S2101.

(Step S2105) The device processing unit 63 determines whether it is time to transmit the mobile unit location information. If it is time to transmit the mobile unit location information, the process proceeds to step S2106. If it is not time to transmit the mobile unit location information, the process proceeds to step S2108.

(Step S2106) The device processing unit 63 acquires the mobile unit location information. The device processing unit 63 acquires the employee identifier from the device storage unit 61, and configures information having the employee identifier and the mobile unit location information, and having a structure to be transmitted.

(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 performance information (e.g., sales activity information, input information) has been received. If performance information has been received, the process proceeds to step S2109; if not, the process returns to step S2101.

(Step S2109) The device processing unit 63 acquires the employee identifier from the device storage unit 61, and configures information to be transmitted, which includes the employee identifier and the accepted performance information. The device transmission unit 64 transmits the information to the information processing device 5. Return to step S2101.

In the flowchart in Figure 21, processing ends when the power is turned off or an interrupt occurs to end processing.

As described above, according to this embodiment, accurate information on an employee's travel route can be obtained using one or more types of information from among the employee's schedule information and actual performance information.

In addition, in this embodiment, the consistency between an employee's schedule information and actual performance information can be checked.

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

In addition, in this embodiment, travel expense information can be obtained. Also, appropriate items for the travel expense information can be obtained.

In addition, in this embodiment, travel expense information corresponding to the travel expense item can be stored in the travel expense database 81.

In addition, in this embodiment, commuter pass information can be used to obtain appropriate commuting expenses.

In addition, in this embodiment, appropriate commuting expenses can be obtained for employees who apply to commute by personal car or other mobile means.

In addition, in this embodiment, travel expense information corresponding to the commuting expense item can be stored in the commuting expense database 91.

In addition, in this embodiment, appropriate travel route information can be output for travel expense information for employees who travel between two or more work locations in a day.

In addition, in this embodiment, appropriate items can be determined for travel expense information of employees who travel between two or more work locations in one day.

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

In addition, in this embodiment, if there is a change from the default scheduled information or actual performance information, the appropriate person, such as a supervisor, can be notified.

In addition, in this embodiment, if the planned information and actual information do not match, appropriate processing can be performed.

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

The information processing device 5 may have the functions of the expense inspection device 1 described in the first embodiment (such as the function of inspecting expense information). The information processing device 5 may inspect for fraud regarding the application of travel expense information (transportation expenses or commuting expenses) using performance information such as entrance and exit information and sales activity information, for example.

The notification unit 534 in the information processing device 5 may be provided by the output unit 54. In other words, the inclusion relationships of the components in the information processing device 5 and the like do not matter. It goes without saying that each component only needs to fulfill its respective function.

The software for realizing the information processing device 5 in this embodiment is the following program. In other words, this program is a program for causing a computer that can access a work information storage unit in which one or more types of information among schedule information, which is information about an employee's work schedule and has location-specific information that specifies the work location, and actual information, which is information about an employee's work results and has location-specific information, to be stored in association with one or more employee identifiers, to function as a travel route acquisition unit that acquires location-specific information corresponding to an employee identifier from the work information storage unit and acquires travel route information related to the travel route of an employee identified by the employee identifier using the location-specific information, and a travel route output unit that outputs the travel route information.

FIG. 22 also shows the appearance of a computer that executes the programs described in this specification to realize the expense inspection device 1 and the like of the various embodiments described above. The above-mentioned embodiments can be realized by computer hardware and a computer program executed thereon. FIG. 22 is an overview of this computer system 300, and FIG. 23 is a block diagram of the system 300.

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

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

The program that causes the computer system 300 to execute the functions of the information processing device 5 of the above-mentioned embodiment 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 sent to the computer 301 via a network (not shown) and stored on the hard disk 3017. The program is loaded into the RAM 3016 when executed. The program may be loaded directly from the CD-ROM 3101 or the network.

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

In the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmission step (processing that is performed only by hardware).

The computer that executes the above program may be a single computer or multiple computers. In other words, centralized processing or distributed processing may be performed. In other words, the information processing device 5 may be a standalone device or may be composed of two or more devices.

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

In addition, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in multiple devices.

The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these are also included within the scope of the present invention.

As described above, the information processing device of the present invention has the effect of being able to obtain accurate employee movement routes, and is useful as a server that constitutes 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 Entry and 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 reception unit 26 First output unit 52 Reception unit 55 Transmission unit 61 Terminal storage unit 62 Terminal reception unit 63 Terminal processing unit 64 Terminal transmission unit 65 Terminal reception unit 66 Terminal output unit 71 Card reader 81 Transportation expenses database 91 Commuting expenses database 111 Expense information storage unit 112 Applicant group storage unit 113 Company regulation 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 Transportation means information storage unit 121 Expense acceptance unit 131, 533 Inspection unit 132 Statistical processing unit 141 Result output unit 511 Home location storage unit 512 Workplace information storage unit 513 Regular commuter 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 Results reception unit 530 Change determination unit 531 Schedule accumulation unit 532 Results accumulation unit 534 Notification unit 535 Travel route acquisition unit 536 Travel expense acquisition unit 537 Account 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 Entry/exit information storage unit 1124 Business activity information storage unit 1125 Card statement information storage unit 1126 Business vehicle position information storage unit 1181 Calculation information storage unit 1182 Map information storage unit 1311 Image inspection means 5171 Schedule information storage unit 5172 Performance information storage unit

Claims (5)

an inspection unit which acquires, from a work information storage unit in which schedule information, which is information regarding an employee's work schedule and which has location specifying information specifying a work location and day information specifying a day, and performance information, which is information regarding an employee's work performance and which has location specifying information and day information, and which is sales activity information which is information regarding an employee's sales activity, or input information which an employee has entered to perform a job, or performance information which is employee location information including one or more location information received from a mobile terminal held by the employee, are stored in association with one or more employee identifiers, and which acquires schedule information and performance information corresponding to the same day information for each employee identifier and inspects whether the schedule information and performance information match;
a notification unit that notifies an employee identified by an employee identifier corresponding to the test result of information regarding the test result in the test unit;
a re-examination unit which judges whether or not the performance information received from the terminal device of the employee to whom the notification unit has notified the information regarding the inspection result satisfies a predetermined condition when the inspection result in the inspection unit indicates a mismatch;
A re-processing unit that performs different processing depending on the judgment result of the re-inspection unit,
The reprocessing unit includes:
An information processing device which, if the re-examination unit determines that the predetermined condition is satisfied, stores the performance information in a pair with the employee identifier, and, if the re-examination unit determines that the predetermined condition is not satisfied, does not store the performance information . The notification unit is
2. The information processing apparatus according to claim 1 , wherein, when the inspection result in the inspection section indicates a mismatch, information relating to the inspection result is notified to an employee identified by an employee identifier corresponding to the inspection result. a result receiving unit that receives result information from a terminal device of an employee to which the notification unit has notified the employee of the result of the inspection, the result of the inspection being inconsistent;
3. The information processing apparatus according to claim 1 , further comprising a performance accumulation unit that accumulates said performance information in said work information storage unit in association with an employee identifier of said employee. 4. An information processing method comprising all the steps performed by the information processing device according to claim 1 . Computer ,
A program for causing the information processing device according to any one of claims 1 to 3 to function as the information processing device .

Images