Information processing device, information processing method, and program

Abstract

To provide an information processing device, a program, and a creation support method for checking the consistency between scheduled work information and work performance information.SOLUTION: An expense checking device 1 includes a checking unit 102 and an output unit 103. The checking unit 102 retrieves from a work information storage unit 101 scheduled information and performance information corresponding to the same date information for each employee identifier and checks whether the scheduled information matches the performance information. The output unit 103 outputs information on the checking results obtained by the checking unit 102. The work information storage unit 101 stores the scheduled information and the performance information in association with one or more employee identifiers. The scheduled information is information related to scheduled work of employees and has location identification information for specifying the worksite and date information for specifying the day. The performance information is information related to the work performances of employees and has location identification information and date information.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to an information processing apparatus and the like for inspecting the consistency between scheduled work information and actual work performance information.

Background Art

[0002] Conventionally, there have been various labor management systems. For example, there has been a labor management system that exerted coercion to answer questions regarding overtime schedules and the like (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art, it has been impossible to obtain the accurate movement route of an employee using one or more types of information among the scheduled information and the actual performance information of the employee.

Means for Solving the Problems

[0005] The information processing apparatus according to the first invention of the present invention includes a scheduled information that is information regarding the scheduled work of an employee and includes location specifying information for specifying a work location and date information for specifying a date, and actual performance information that is information regarding the actual performance of the employee's work and includes location specifying information and date information. From a work information storage unit in which the actual performance information is stored in association with one or more employee identifiers, for each employee identifier, scheduled information and actual performance information corresponding to the same date information are acquired, and an inspection unit that inspects whether the scheduled information and the actual performance information match, and an output unit that outputs information regarding the inspection result in the inspection unit.

[0006] This configuration allows for checking the consistency between planned and actual information and outputting the check results.

[0007] Furthermore, the information processing device of this second invention, compared to the first invention, is an information processing device in which the output unit comprises a notification unit that notifies an employee identified by an employee identifier corresponding to the inspection result of the inspection unit.

[0008] This configuration allows for checking the consistency between planned and actual information and notifying employees of the check results.

[0009] Furthermore, in contrast to the second invention, the information processing device of this third invention is an information processing device in which, when the inspection result from the inspection unit is found to be inconsistent, the notification unit notifies the employee identified by the employee identifier corresponding to the inspection result of information regarding the inspection result.

[0010] This configuration allows for checking the consistency between planned and actual information, and if there is a discrepancy, it can notify the employee of the discrepancy.

[0011] Furthermore, the information processing device of the fourth invention further comprises, in addition to the second or third invention, an information processing device that includes a re-inspection unit which determines whether the actual performance information received from the terminal device of the employee who notified the notification unit of the inspection result is inconsistent with the second or third invention and the notification unit has notified the employee of the inspection result, satisfies predetermined conditions, and a re-processing unit which performs different processing according to the determination result of the re-inspection unit.

[0012] This configuration allows for appropriate processing when planned information and actual information do not match.

[0013] Furthermore, the information processing device of the fifth invention is an information processing device that, in addition to the third invention, comprises a performance receiving unit that receives performance information from the terminal device of an employee to whom the inspection results in the inspection unit indicate that the inspection results do not match, and to which the notification unit notifies information regarding the inspection results, and a performance storage unit that stores the performance information in the work information storage unit, associating it with the employee's employee identifier.

[0014] This configuration allows for appropriate processing when planned information and actual information do not match.

[0015] Furthermore, the information processing device of the sixth invention is an information processing device in which, for any one of the first to fifth inventions, the performance information is one or more of the following: entry and exit information relating to an employee's entry into and exit from the workplace, sales activity information relating to sales activities, input information entered by an employee in order to perform their job, and employee location information including one or more location information received from a mobile terminal held by an employee.

[0016] This configuration allows for the verification of consistency between planned and actual data using appropriate performance data. [Effects of the Invention]

[0017] According to the information processing device of the present invention, it is possible to obtain the precise movement path of an employee. [Brief explanation of the drawing]

[0018] [Figure 1] Conceptual diagram of information system A in Embodiment 1 [Figure 2] Block diagram of information system A [Figure 3] Block diagram of the expense inspection device 1 that constitutes the information system A. [Figure 4] Flowchart illustrating an example of operation of the same cost inspection device 1. [Figure 5] A flowchart illustrating an example of the same inspection process. [Figure 6] A flowchart illustrating an example of the statistical testing process. [Figure 7] Flowchart for explaining the processing example of the same leakage inspection [Figure 8] Figure showing the same output example [Figure 9] Figure showing the same output example [Figure 10] Block diagram of another system including the same expense inspection device 1 [Figure 11] Conceptual diagram of information system B in Embodiment 2 [Figure 12] Block diagram of the same information system B [Figure 13] Block diagram of the information processing device 5 constituting the same information system B [Figure 14] Flowchart for explaining the operation example of the same information processing device 5 [Figure 15] Flowchart for explaining the example of the same inspection process [Figure 16] Flowchart for explaining the example of the same movement route acquisition process [Figure 17] Flowchart for explaining the same commuting route acquisition process [Figure 18] Flowchart for explaining the same route acquisition process between workplaces [Figure 19] Flowchart for explaining the same return route acquisition process [Figure 20] [[ID=4I]]Flowchart for explaining the same re-inspection process [Figure 21] Flowchart for explaining the operation example of the same terminal device 6 [Figure 22] Overview diagram of the computer system in the above embodiment [Figure 23] Block diagram of the same computer system

Mode for Carrying Out the Invention

[0019] Hereinafter, embodiments of an information processing device and the like will be described with reference to the drawings. In the embodiments, components denoted by the same reference numerals perform the same operations, so the description may be omitted again.

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

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

[0022] Furthermore, in this embodiment, we will describe an information system that includes an expense inspection device for checking whether the approver of the expense application meets the requirements.

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

[0024] Furthermore, in this embodiment, we will describe an information system that includes an expense inspection device that uses external information to detect any omissions in the application of expenses that should be applied for.

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

[0026] Expense Inspection Device 1 is a device that inspects the submitted expense information. Expense Inspection Device 1 is typically a server, such as a cloud server or ASP server. The type of Expense Inspection Device 1 is not specified.

[0027] Applicant Terminal 2 is the terminal used by the applicant. The applicant is the user submitting the expense claim. Applicant Terminal 2 can be, for example, a personal computer, tablet, smartphone, etc., and the type is not limited.

[0028] External Server 3 stores the external information described below and provides this information to the Expense Inspection Device 1. Note that all or part of the external information described below may reside in the Expense Inspection Device 1. Furthermore, if all of the external information described below resides in the Expense Inspection Device 1, External Server 3 is unnecessary. External Server 3 is typically a server, such as a cloud server or ASP server. The type of External Server 3 is not specified.

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

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

[0031] The expense inspection device 1 comprises a storage unit 11, a reception unit 12, a processing unit 13, and an output unit 14. The storage unit 11 comprises, for example, an expense information storage unit 111, an applicant group storage unit 112, a company regulations information storage unit 113, a restaurant group storage unit 114, an adult entertainment establishment group storage unit 115, a counterparty group storage unit 116, a card usage expense storage unit 117, and a means of transportation information storage unit 118. The applicant group storage unit 112 comprises a personal information storage unit 1121, an attendance information storage unit 1122, an entry / exit information storage unit 1123, a business activity information storage unit 1124, a card statement information storage unit 1125, and a business vehicle location information storage unit 1126. The means of transportation information storage unit 118 comprises a calculation information storage unit 1181 and a map information storage unit 1182. The reception unit 12 comprises an expense reception unit 121. The processing unit 13 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.

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

[0033] The expense information storage unit 111, applicant group storage unit 112, company regulations information storage unit 113, restaurant group storage unit 114, adult entertainment establishment group storage unit 115, counterparty group storage unit 116, card usage expense storage unit 117, and means of transportation information storage unit 118 in the expense inspection device 1 may be located in other external devices.

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

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

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

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

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

[0039] Expense information is stored in the expense information storage unit 111. Typically, two or more expense information items are stored in the expense information storage unit 111. Expense information is information that identifies the details of the expense that has been requested. Expense information includes, for example, expenditure amount information, recipient identifier, store identifier, counterparty identifier, date of use information, payment method identifier, account, description, and approver identifier. Expenditure amount information is information that identifies the amount spent as an expense. The recipient identifier is information that indicates the recipient of the receipt and identifies the company or other entity that will pay the amount. The store identifier is information that identifies the store where the expense was used. The store identifier is, for example, the store name, store ID, store URL, or store telephone number. The counterparty identifier is information that identifies the counterparty to whom the expense was used. The counterparty identifier is information that identifies the recipient to whom benefits such as entertainment or gifts were provided. The counterparty identifier is, for example, the organization name (e.g., company name, group name), name, and counterparty ID. Date of use information is information that identifies 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," or "○○PAY." The account is information that identifies the classification of the expense. The account can also be called the expense type identifier. Examples of accounts include business trip expenses, travel expenses (or transportation expenses), accommodation expenses, business trip expenses, entertainment expenses, and meeting expenses. The approver identifier is information that identifies the approver of the expense. Examples of approver identifiers include the applicant identifier and the job title identifier. The applicant identifier is information that identifies the applicant who applied for the expense, for example, the name and ID. The job title identifier is information that identifies the job title, for example, the job title (for example, "department head" or "director") and ID. The expense information in the expense information storage unit 111 is usually associated with the applicant identifier.

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

[0041] Expense information may include images of receipts. An image of a receipt is, for example, an image obtained by photographing a receipt. It goes without saying that the data structure of the image (JPEG, GIF, etc.) is not restricted.

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

[0043] The applicant set storage unit 112 stores the applicant set. The applicant set is unique information for each applicant corresponding to each applicant. The applicant set may be, for example, a set of personal information, a set of attendance information, a set of entry / exit information, a set of sales activity information, a set of card statement information, or a set of sales vehicle location information, as described later.

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

[0045] Furthermore, for two pieces of information to be considered to correspond, it is sufficient that one piece of information can be retrieved from the other. For example, one piece of information and the other piece of information may be linked, one piece of information and the other piece of information may be stored in the same buffer, or one piece of information may contain the other piece of information.

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

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

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

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

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

[0051] The company regulations information storage unit 113 stores company regulations information. Company regulations information is information that indicates the company's regulations. Company regulations information is information about the regulations of the company to which the applicant belongs. For example, company regulations information may include overtime hours information, information on one or more approvers, and information on one or more payment methods.

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

[0053] Approver information is information that identifies who can approve expenses. Approver information includes, 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 head," "director").

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

[0055] Restaurant collection storage unit 114 stores restaurant collections. A restaurant collection has information on one or more restaurants. Restaurant information is information about a restaurant. Restaurant information may include, for example, a restaurant identifier that identifies the restaurant, and price information. Restaurant information may also include address information, telephone number information, etc. The restaurant identifier may be, for example, the restaurant name or ID. Price information may be, for example, information that identifies an appropriate amount to spend at a restaurant. Price information may be, for example, information that identifies the amount of money one person spends at the restaurant. Price information may be, for example, information that shows the average amount one person spends at the restaurant. Price information may also be, for example, information that identifies the upper limit of the amount one person spends at the restaurant. Price information may also be, for example, information that identifies the upper limit of the amount spent in a single visit.

[0056] The adult entertainment establishment collection storage unit 115 stores adult entertainment establishment collections. Each collection of adult entertainment establishments has one or more adult entertainment establishment information. The adult entertainment establishment information may include, for example, an adult entertainment establishment identifier that identifies the establishment. The adult entertainment establishment information may also include price information, address information, telephone number information, etc. The adult entertainment establishment information may also include, for example, information that identifies establishments that the applicant is not allowed to visit.

[0057] The recipient set storage unit 116 stores recipient sets. Each recipient set has one or more recipient information entries. Recipient information entries include, for example, a recipient identifier and an affiliation identifier that identifies the recipient's affiliation. Recipient information entries include, for example, information on public officials. Recipient information entries include, for example, information on members of parliament. Recipient information entries include, for example, information that identifies a person to whom the applicant is not permitted to provide benefits. Providing benefits includes, for example, entertaining someone or giving them a gift.

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

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

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

[0061] Map information is stored in the map information storage unit 1182. This map information is, for example, map information used for navigation. The map information is, for example, in KIWI format.

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

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

[0064] The expense reception unit 121 is preferably able to receive expense information that includes a receipt image. The expense reception unit 121 may also separately receive the receipt image and other information that constitutes the expense information. However, the receipt image and the other information should be received in correspondence.

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

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

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

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

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

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

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

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

[0073] The image inspection means 1311 performs character recognition processing on a receipt image, for example, and obtains one or more strings. The process of performing character recognition processing and obtaining information constituting expense information from a receipt image is publicly known technology. The image inspection means 1311 then determines which of the following information the obtained strings represent: payment amount information, store identifier, counterparty identifier, date of use information, account, description, or payment method information, and associates the string 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 strings is an information classification problem (clustering problem) and is publicly known technology.

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

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

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

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

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

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

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

[0081] The image inspection means 1311 uses training data, for example, which includes negative examples of one or more fraudulent receipt images and positive examples of one or more legitimate receipt images, to perform a learning process using a machine learning algorithm and construct a learning model. Next, the image inspection means 1311 provides the receipt images contained in the expense information received by the expense reception unit 121 and the learning model to a machine learning prediction processing module, performs prediction processing, and obtains a prediction result of whether or not the receipt is fraudulent. The learning model may be, for example, a learning model for detecting fraudulent manipulation of amounts on receipts, a learning model for checking whether or not there is a signature on a receipt, or a learning model for detecting unclear receipt images. In addition, the learning model is usually a learning model for binary classification of whether or not the receipt is fraudulent.

[0082] The statistical processing unit 132 performs statistical processing based on one or more expense information items stored in the expense information storage unit 111, which are associated with the applicant identifier associated with the received 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 expense information items stored in the expense information storage unit, which are associated with the said applicant identifier, and obtains the statistical processing results. The timing of the statistical processing unit 132's statistical processing is not specified. For example, the statistical processing unit 132 performs statistical processing upon receiving instructions from the user. For example, the statistical processing unit 132 performs statistical processing upon receiving expense information.

[0083] The statistical processing unit 132 obtains store frequency information using store identifiers included in two or more expense information items, which are, for example, two or more expense information items stored in the expense information storage unit 111 and which correspond to one applicant identifier. Store frequency information is information about the frequency of use of a store identified by one store identifier. Store frequency information is information that indicates the frequency of use. Store frequency information is, for example, information that indicates the total number of times used, or information that indicates the number of times used in a unit period. A unit period is, for example, one month, six months, or one year. It is preferable for the statistical processing unit 132 to obtain store frequency information for each applicant identifier.

[0084] The statistical processing unit 132 obtains entertainment frequency information using two or more expense information items stored in the expense information storage unit 111, which include a counterparty identifier associated with a single applicant identifier. The entertainment frequency information is information regarding the frequency of expenditures to a counterparty identified by a single counterparty identifier. Expenditures to a counterparty are payments made for the provision of benefits to the counterparty, such as payments for entertainment to the counterparty or payments for gifts to the counterparty. The entertainment frequency information is information indicating the frequency of benefit provision. For example, the entertainment frequency information may include 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 obtain entertainment frequency information for each applicant identifier.

[0085] The statistical processing unit 132 obtains the number of fraudulent transactions, which is the number of times an assessment result corresponding to fraud has been obtained for expense information corresponding to a single applicant identifier, and associates this with a single applicant identifier. It is preferable for the statistical processing unit 132 to obtain the number of fraudulent transactions for each applicant identifier.

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

[0087] 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, for example, associated with the applicant identifier.

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

[0089] The first reception desk 22 receives various instructions and information. These instructions and information include, for example, expense information and response information. Response information refers to information indicating a response to the test results.

[0090] The first processing unit 23 performs various processes. These various processes include, for example, converting instructions and information received by the first receiving unit 22 into instructions and information for a data structure to be transmitted. These various processes also include, for example, converting information received by the first receiving unit 25 into information for a data structure to be output.

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

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

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

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

[0095] The following describes specific examples of inspections performed by the inspection unit 131. While the following primarily describes cases of fraud, if the case is not fraudulent, the inspection unit 131 typically obtains an inspection result indicating that the case is "legitimate." Furthermore, if the case is deemed legitimate, the inspection unit 131 typically associates the expense information subject to inspection with an applicant identifier and stores it in the expense information storage unit 111.

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

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

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

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

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

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

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

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

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

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

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

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

[0108] The inspection unit 131 provides the transportation expense calculation module with information indicating the company's location and one or more location identifiers from the business activity information, and uses the calculation information for calculating transportation expenses to obtain one or more transportation expenses. Preferably, the transportation expenses obtained here are the cheapest transportation expenses. Furthermore, if two or more transportation expenses are obtained, it is when there are two or more travel routes. The technology for obtaining transportation expenses and the technology for obtaining the cheapest transportation expenses are publicly known technologies, so a detailed explanation is omitted. The inspection unit 131 also obtains expenditure amount information from the expense information received by the expense reception unit 121.

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

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

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

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

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

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

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

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

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

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

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

[0120] The inspection unit 131 obtains applicant information associated with the applicant identifier linked to the expense information related to transportation expenses received by the expense reception unit 121, and uses the applicant information, or the applicant information and means of transport information, to perform an inspection for fraud related to transportation expense claims and obtain the inspection results.

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

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

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

[0124] The inspection unit 131 obtains applicant information associated with the applicant identifier linked to the expense information regarding taxi fares received by the expense reception unit 121, and uses the applicant information, or the applicant information and means of transport information, to conduct an inspection for fraud related to the claim for transportation expenses and obtains the inspection results.

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

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

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

[0128] The inspection unit 131 obtains from the personal information storage unit 1121 the regular route information associated with the applicant identifier that is 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 from the expense information received by the expense reception unit 121 that has one or more route information having a departure identifier and an arrival identifier.

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

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

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

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

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

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

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

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

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

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

[0139] The inspection unit 131 determines whether the expense information received by the expense reception unit 121 is similar to one or more past expense information stored in the expense information storage unit 111 that is associated with the same applicant identifier as the expense information, and whether it satisfies predetermined conditions, and obtains the inspection result.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0160] The inspection unit 131 retrieves attendance information corresponding to a single applicant identifier from the attendance information storage unit 1122. Next, the inspection unit 131 determines whether the retrieved attendance information corresponds to information related to an overseas business trip. If the attendance information corresponds to information related to an overseas business trip, the inspection unit 131 determines whether there is expense information in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the work day information in the attendance information, and has an expense type identifier for the expenses applied for during the overseas business trip (for example, "overseas daily allowance" or "overseas business trip allowance"). If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result stating that "expenses corresponding to the overseas business trip have not been applied for."

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

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

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

[0164] The inspection unit 131 obtains entry / exit information corresponding to a single applicant identifier from the entry / exit information storage unit 1123. Next, the inspection unit 131 determines whether the obtained entry / exit information corresponds to work that is not within the scope of salary. Next, if it determines that the entry / exit information corresponds to work that is not within the scope of salary, the inspection unit 131 determines whether there is expense information in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the work date information in the entry / exit information, and has an expense type identifier indicating labor wages (for example, "labor wages"). If it determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result stating that "no expense corresponding to the entry / exit information has been applied for."

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

[0166] The inspection unit 131 obtains entry / exit information corresponding to a single applicant identifier from the entry / exit information storage unit 1123. Next, the inspection unit 131 determines whether the obtained entry / exit information corresponds to business travel. If the entry / exit information corresponds to business travel, the inspection unit 131 determines whether there is expense information in the expense information storage unit 111 that corresponds to a single applicant identifier, has the same usage date information as the work day information in the entry / exit information, and has an expense type identifier for the expenses applied for during the business trip (for example, "business trip expenses" or "travel and transportation expenses"). If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "expenses corresponding to the business trip have not been applied for."

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

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

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

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

[0171] The algorithm used to determine whether sales activity information corresponds to business travel is not specified. Sales activity information may include a flag indicating whether or not it is a business trip. (b) Failure to submit travel expense claims

[0172] The inspection unit 131 obtains one or more location identifiers from the business activity information storage unit 1124 that correspond to a single applicant identifier. Next, the inspection unit 131 uses the company's location information, which is stored in advance, and the one or more location identifiers obtained to determine whether or not transportation expenses are incurred. If it is determined that transportation expenses are incurred, the inspection unit 131 determines whether or not there is expense information in the expense information storage unit 111 that has the same usage date information as the business day information in the business activity information and has the expense type identifier "travel expenses". If the inspection unit 131 determines that such expense information does not exist in the expense information storage unit 111, the inspection unit 131 obtains an inspection result indicating that "no transportation expenses have been applied for".

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

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

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

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

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

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

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

[0180] The image inspection means 1311 acquires one or more sets of a combination of a character string and a class from the receipt image included in the expense information received by the expense reception unit 121. Next, for each set, the inspection unit 131 acquires the character string (for example, any one of payment amount information, store identifier, partner identifier, usage date information, item, summary, and settlement means information) corresponding to the class of the set and included in the expense information received by the expense reception unit 121. Next, for each set, the inspection unit 131 compares the character string of one class acquired from the receipt image with the character string of the same class included in the expense information received by the expense reception unit 121, and determines whether they have a predetermined relationship. If they do not have a predetermined relationship, the inspection unit 131 obtains an inspection result indicating fraud.

[0181] The predetermined relationship is that they are the same but are more similar as they satisfy the predetermined conditions (for example, the similarity is greater than or equal to a threshold value, only the difference between "(Co., Ltd.)" and "Corporation", only the difference in notation, etc.). (15-2) Inspection of Amount Processing (a) When Using Character Recognition Processing

[0182] The image inspection means 1311, for example, uses character recognition technology to acquire the character string and score of the amount area from the receipt image, and determines that there has been processing of the amount on the receipt when it is determined that the score is lower as it satisfies the predetermined conditions. The image inspection means 1311, for example, acquires all the characters of the receipt image by character recognition technology, detects the character "￥" from the set of these characters, and acquires the numerical string to the right of the character "￥" as the payment amount information. (b) When Using Machine Learning Processing

[0183] The image inspection means 1311, for example, uses one or more receipt images with forged amounts by handwriting and one or more receipt images without forgery as teacher data, performs learning processing by a machine learning algorithm, and constructs a learner that acquires an inspection result indicating whether the amount is forged by inputting the receipt image.

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

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

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

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

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

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

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

[0191] The image inspection means 1311 uses a machine learning algorithm to learn from one or more blurry receipt images and one or more clear receipt images, thereby constructing a learning device. This learning device takes a receipt image as input and obtains a result of determining whether the receipt image is blurry or clear.

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

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

[0194] The image inspection means 1311 uses, for example, one or more handwritten receipt images with a company seal as positive examples, and one or more receipt images without a company seal as negative examples, to perform a learning process using a machine learning algorithm and construct a learning device. This learning device takes a receipt image as input and outputs whether or not a company seal is affixed to it.

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

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

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

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

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

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

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

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

[0203] The reception unit 12, the expense reception unit 121, and the first receiving unit 25 are usually implemented by wireless or wired communication means, but they may also be implemented by means of receiving broadcasts.

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

[0205] The output unit 14, the result output unit 141, and the first transmission unit 24 are usually implemented by wireless or wired communication means, but may also be implemented by broadcasting means.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0226] (Step S416) The result output unit 141 outputs the leak test results obtained in step S415. The process returns to step S401. Outputting the test results here may include, for example, storing the test results in the storage unit 11, sending them to the applicant identified by the applicant identifier corresponding to the leak, or sending them to a terminal (not shown).

[0227] In the flowchart shown in Figure 4, processing is terminated by power-off or processing termination interrupts.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0247] The business trip expense inspection process is a process for inspections specific to business trip expenses. The business trip expense inspection process is, for example, (1-2) inspection of irregularities in business trip expenses, (2-2) inspection of irregularities in business trip expenses.

[0248] (Step S514) The inspection unit 131 uses the obtained inspection results to compose the output inspection results. Return to the upper-level process.

[0249] For example, if one or more irregular inspection results are obtained, the inspection unit 131 composes inspection results including all inspection results in case of irregularities. Also, if no irregular inspection result is obtained, the inspection unit 131 composes inspection results indicating that it is "legitimate".

[0250] Next, an example of the statistical inspection process in step S409 will be described using the flowchart in FIG. 6.

[0251] (Step S601) The statistical processing unit 132 substitutes 1 into the counter i.

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

[0253] Note that the i-th store identifier is the i-th store identifier among the uniquely processed store identifiers among one or more expense information corresponding to the applicant identifier to be inspected. Also, the period of the expense information to be inspected may be determined in advance or may be all periods.

[0254] (Step S603) The statistical processing unit 132 obtains the number of expense records that correspond to the applicant identifier under inspection and contain the i-th store identifier. The statistical processing unit 132 uses this number to obtain store frequency information. The store frequency information may be the same value as the number, or it may be the number divided by the period, etc. The store frequency information is usually a value calculated by an increasing function with the number as a parameter.

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

[0256] (Step S605) The inspection unit 131 obtains an inspection result indicating that "one store has been used too much," and an inspection result having the i-th store identifier, associating it with the applicant identifier being inspected. The inspection unit 131 may also increment the number of fraudulent transactions corresponding to the applicant identifier being inspected by 1.

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

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

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

[0260] The i-th counterparty identifier is the i-th counterparty identifier obtained by uniquely processing the counterparty identifiers among one or more expense information items corresponding to the applicant identifier being inspected. The period for the expense information to be inspected may be predetermined or may be the entire period.

[0261] (Step S609) The statistical processing unit 132 obtains the number of expense records that correspond to the applicant identifier of the subject of inspection and contain the i-th counterparty identifier. The statistical processing unit 132 uses this number to obtain counterparty frequency information. The counterparty frequency information may be the same value as the number, or it may be the number divided by the period, etc. The counterparty frequency information is usually a value calculated by an increasing function with the number as a parameter.

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

[0263] (Step S611) The inspection unit 131 obtains an inspection result indicating that "the number of times entertainment etc. has been provided to one client is too high," and an inspection result having the i-th client identifier, associating it with the applicant identifier under inspection. The inspection unit 131 may also increment the number of fraudulent activities corresponding to the applicant identifier under inspection by 1.

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

[0265] (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.

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

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

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

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

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

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

[0272] (Step S702) The inspection unit 131 determines whether the i-th applicant identifier exists in the storage unit 11. If the i-th applicant identifier exists, the process proceeds to step S703; otherwise, it returns to the higher-level process. The i-th applicant identifier is the identifier of the i-th applicant to be inspected.

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

[0274] (Step S704) The inspection unit 131 determines whether there is date information indicating the j-th day of the inspection target. If there is date information indicating the j-th day, it proceeds to step S705; if not, it proceeds to step S722. Assume that the days for leakage inspection are predetermined, and the information for specifying the days for leakage inspection is stored in a buffer (not shown).

[0275] (Step S705) The inspection unit 131 determines whether there is attendance information corresponding to the i-th applicant identifier and having the same working day information as the date information indicating the j-th day in the attendance information storage unit 1122. If it exists, it proceeds to step S706; if not, it proceeds to step S709.

[0276] (Step S706) The inspection unit 131 acquires from the attendance information storage unit 1122 the attendance information corresponding to the i-th applicant identifier and having the same working day information as the date information indicating the j-th day. The inspection unit 131 uses the acquired attendance information to perform an inspection for leakage in expense applications. Such inspection is, for example, the process described in “(14-1) Detection of Application Leakage Using Attendance Information”.

[0277] (Step S707) The inspection unit 131 determines whether there is a leakage based on the result of the inspection in step S706. If there is a leakage, it proceeds to step S708; if not, it proceeds to step S709.

[0278] (Step S708) The inspection unit 131 acquires the inspection result indicating that there is a leakage and the content of the leakage, in association with the i-th applicant identifier and the j-th date information.

[0279] (Step S709) The inspection unit 131 determines whether there is entry / exit information corresponding to the i-th applicant identifier and having the same working day information as the date information indicating the j-th day in the entry / exit information storage unit 1123. If it exists, it proceeds to step S710; if not, it proceeds to step S713.

[0280] (Step S710) The inspection unit 131 obtains entry / exit information from the entry / exit information storage unit 1123 that corresponds to the i-th applicant identifier and has the same working day information as the day information indicating the j-th day. The inspection unit 131 uses the obtained entry / exit information to check for omissions in expense applications. Such an inspection is the process described, for example, in "(14-2) Detection of application omissions using entry / exit information".

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

[0282] (Step S712) The inspection unit 131 obtains an inspection result indicating that a leak was found and the details of the leak, associating it with the i-th applicant identifier and the j-th date information.

[0283] (Step S713) The inspection unit 131 determines whether there is business activity information in the business activity information storage unit 1124 that corresponds to the i-th applicant identifier and has the same business day information as the day information indicating the j-th day. If it exists, proceed to step S714; otherwise, proceed to step S717.

[0284] (Step S714) The inspection unit 131 obtains from the sales activity information storage unit 1124 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. The inspection unit 131 uses the obtained sales activity information to check for omissions in expense claims. Such an inspection is the process described, for example, in "(14-3) Detection of Omissions in Claims Using Sales Activity Information".

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

[0286] (Step S716) The inspection unit 131 obtains an inspection result indicating that a leak was found and the details of the leak, associating it with the i-th applicant identifier and the j-th date information.

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

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

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

[0290] (Step S720) The inspection unit 131 obtains an inspection result indicating that a leak was found and the nature of the leak, associating it with the i-th applicant identifier and the j-th date information.

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

[0292] (Step S722) The inspection unit 131 generates an inspection result corresponding to the i-th applicant identifier. The inspection unit 131 temporarily stores the inspection result, for example, in association with the i-th applicant identifier. The inspection result may include, for example, the results of one or more leak inspections. If there are no leaks, the inspection result is information indicating "no leaks".

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

[0294] Next, an example of the operation of the applicant terminal 2 will be described. The first reception unit 22 of the applicant terminal 2 receives expense information input from the user. Next, the first processing unit 23 reads the applicant identifier stored in the first storage unit 21. The first processing unit 23 then constructs transmission information having the received expense information and the read 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.

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

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

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

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

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

[0300] The statistical processing unit 132 then constructs the statistical processing results that are output as a result of the above processing.

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

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

[0303] Furthermore, 802 is a table consisting of records that contain the applicant identifier (applicant), store name, and store frequency information (number of records) corresponding to the store frequency information that has been determined to be high risk.

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

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

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

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

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

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

[0310] As described above, according to this embodiment, by using external information or expense information other than the submitted expense information, appropriate inspections can be performed against inappropriate expense claims.

[0311] Furthermore, according to this embodiment, by using applicant information, appropriate inspections can be conducted against inappropriate expense claims.

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

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

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

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

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

[0317] Furthermore, according to this embodiment, by using the information on the card owned by the applicant, appropriate inspections can be conducted to identify inappropriate expense claims.

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

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

[0320] Furthermore, according to this embodiment, by using a collection of store records, appropriate inspections can be conducted against inappropriate expense claims.

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

[0322] Furthermore, according to this embodiment, it is possible to appropriately detect inappropriate business trip expenses, inappropriate transportation expenses, duplicate applications, reuse of receipts, fraudulent accommodation expenses, fraudulent after-party expenses, etc.

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

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

[0325] Furthermore, according to this embodiment, it is possible to detect that the frequency of expenditures corresponding to a specific customer is high.

[0326] Furthermore, according to this embodiment, it is possible to detect when a particular person is committing a lot of fraud.

[0327] Furthermore, according to this embodiment, it is possible to detect if the approver of the expense application does not meet the requirements.

[0328] Furthermore, according to this embodiment, it is possible to detect when expense claims have been missed.

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

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

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

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

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

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

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

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

[0337] Furthermore, the expense management device 4, upon receiving expense information from the applicant terminal 2, transmits the expense information to the expense inspection device 1 for inspection. In response to the transmission of the expense information, the expense management device 4 receives the 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. If the inspection results are invalid, the expense management device 4 transmits the inspection results to the applicant terminal 2.

[0338] With the system configuration described above, comprising an expense inspection device 1 and one or more expense management devices 4, the expense inspection device 1 can function as an expense information inspection server. In addition, the expense management device 4 can obtain expense inspection functionality by using the expense inspection device 1, in addition to its conventional expense information management function.

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

[0340] The processing in this embodiment may be implemented by software. This software may be distributed by software download or the like. Alternatively, this software may 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 implements the expense inspection device in this embodiment is the following program. In other words, this program causes a computer to function as an expense reception unit that receives expense information that identifies the contents 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 perform an inspection for fraudulent use of the expense information received by the expense reception unit and obtain the inspection results, and a result output unit that outputs the inspection results obtained by the inspection unit.

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

[0342] Furthermore, in this embodiment, we will describe an information system that includes an information processing device that uses employee schedule information and actual performance information to check whether work is being carried out as scheduled, obtains the check results, and processes using the check results.

[0343] Furthermore, in this embodiment, we will describe an information system that includes an information processing device for notifying an employee if the inspection result is found to be invalid.

[0344] Furthermore, in this embodiment, we will describe an information system that includes an information processing device that determines whether travel expense information, which is the cost associated with an employee's movement, falls under the categories of commuting expenses or transportation expenses, and outputs the travel expense information in association with the said category.

[0345] Furthermore, in this embodiment, we will describe an information system that includes different information processing devices for storing travel expense information depending on whether the travel expense information is categorized as commuting expenses or transportation expenses.

[0346] Furthermore, in this embodiment, we will describe an information system that includes an information processing device that acquires commuting expenses using information on commuter passes and information on means of transportation such as private cars.

[0347] Furthermore, in this embodiment, we will describe an information system that includes an information processing device for processing and storing information on commuting expenses that are not "0" in a commuting expense database. It should also be noted that processing may be performed to store information on commuting expenses of "0".

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

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

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

[0351] Furthermore, in this embodiment, we will describe an information system that includes an information processing device that re-examines the received actual information after it has been determined that the actual information does not match the planned information.

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

[0353] The information processing device 5 is a server that implements the functions of the present invention, and is a server that receives and processes information from terminal devices 6, access control information acquisition devices 7, etc. The information processing device 5 is, for example, a cloud server, an ASP server, etc., but its type is not limited.

[0354] Terminal device 6 is a terminal used by an employee. An employee is someone whose work is managed by the organization, and may include not only full-time employees but also part-time employees and other non-regular employees. Terminal device 6 can be, for example, a personal computer, tablet, smartphone, etc., and the type is not limited.

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

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

[0357] The personnel information management device 9 is a device that manages personnel information, including commuting expense information, and also checks personnel information. The personnel information management device 9 is typically a so-called server, such as a cloud server or ASP server. The type of personnel information management device 9 is not specified.

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

[0359] 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.

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

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

[0362] The work information storage unit 517 includes a schedule information storage unit 5171 and a performance information storage unit 5172.

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

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

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

[0366] The transmitting unit 55 includes a modified transmitting unit 551.

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

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

[0369] Various types of information are stored in the storage unit 51 that constitutes the information processing device 5. These types of information include, for example, home location information, work location information, regular information, mobile information, commute route information, default information, work information, scheduled information, and actual information, which will be described later.

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

[0371] The work location information storage unit 512 stores one or more work location information. The work location information includes a work location identifier and location identification information. The work location identifier is information that identifies the work location, such as the work location name, store name, or work location ID. The location identification information is information that identifies the location of the work location, such as the work location information (latitude, longitude), work location address, work location name, work location identifier, or store name.

[0372] The period information storage unit 513 stores one or more period information entries. The period information is associated with an employee identifier. The period information identifies whether or not an employee has a commuter pass. In other words, the period information indicates whether or not an application for a commuter pass has been made, and whether or not the commuter pass fare has been paid. The period information may be information indicating that an employee has a commuter pass, or information indicating that an employee does not have a commuter pass.

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

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

[0375] The default storage unit 516 stores one or more default scheduled information or one or more default actual information. The default scheduled information or default actual information is associated with an employee identifier. The default scheduled information or default actual information may also be included in the commute route information. The default scheduled information or default actual information is, for example, location identification information of the employee's workplace. The default scheduled information usually contains location identification information of the workplace where the employee works. The default actual information usually contains location identification information of the workplace where the employee works.

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

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

[0378] The schedule information in the schedule information storage unit 5171 may be, for example, default schedule information with day information added, or it 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.

[0379] Schedule information is, for example, shift schedule information that identifies work shifts. Shift schedule information has, for example, one or more records, each containing day information and a work location identifier that identifies the work location. Shift schedule information also has, for example, one or more records, each containing 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. In other words, an employee may work at two or more locations in a single day. In such a case, the employee will be moving between different work locations.

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

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

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

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

[0384] 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 modified by the employee from the terminal device 6, for example. Note that the modified schedule information is different from the default schedule information.

[0385] The performance receiving unit 522 receives performance information. The performance receiving unit 522 receives performance information associated with an employee identifier. 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, for example. Modified performance information is scheduled information that differs from the default performance information. The performance receiving unit 522 receives performance information associated with an employee identifier from the entry / exit information acquisition device 7, for example. Such performance information includes entry / exit information. Such performance information has location identification information. The performance receiving unit 522 receives employee location information including sales activity information, input information, or one or more location pieces from the terminal device 6.

[0386] The inspection result from the inspection unit 533, described later, indicates that the results do not match, and the notification unit 534, described later, receives performance information from the employee's terminal device 6 that notified the employee of the information regarding the inspection result. This performance information is the performance information that the employee believes to be correct.

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

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

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

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

[0391] The change determination unit 530 retrieves the default schedule information or default actual information corresponding to one or more employee identifiers from the default storage unit 516, which stores the default schedule information or default actual information associated with each employee identifier. The unit then 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. The timing of this determination is not relevant.

[0392] The scheduled or actual work information stored in the work information storage unit 517 refers to the received scheduled or actual work information, and may also refer to information that will be stored in the work information storage unit 517 in the future.

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

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

[0395] The schedule storage unit 531 stores schedule information associated with an employee identifier. The schedule storage unit 531 stores the schedule information received by the schedule receiving unit 521, associated with an employee identifier, in the schedule information storage unit 5171, also associated with the employee identifier.

[0396] The schedule storage unit 531 contains information related to modifications from the default schedule information. The system may use the received information to obtain the modified schedule information and store it in the schedule information storage unit 5171.

[0397] The performance storage unit 532 stores performance information associated with the employee identifier of each employee. The performance storage unit 532 stores the performance information received by the performance receiving unit 522, associated with the employee identifier, in the performance information storage unit 5172, also associated with the employee identifier.

[0398] The performance data storage unit 532 contains information related to corrections from the default performance data. Using the received information, the corrected performance data may be obtained and the schedule information may be stored in the performance data storage unit 5172.

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

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

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

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

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

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

[0405] Next, the inspection unit 533 determines whether one or more locations identified by one or more location identification pieces included in the scheduled information match one or more locations identified by one or more location identification pieces included in the sales activity information. If they match, it is determined that the scheduled information and the actual information match; if even one does not match, it is determined that the scheduled information and the actual information do not match. If there are two or more work locations for an employee on a given day, the inspection unit 533 retrieves two or more locations identified by two or more location identification pieces included in the scheduled information in order of work time, and retrieves two or more locations identified by two or more location identification pieces included in the sales activity information in order of work time (order of appearance). Then, including the order of the locations, it determines whether two or more locations corresponding to the scheduled information match two or more locations corresponding to the actual information.

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

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

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

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

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

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

[0412] Next, the inspection unit 533 obtains a work location identifier corresponding to the acquired employee location information from the work location information storage unit 512. The inspection unit 533 also obtains location identification information (e.g., location information (latitude, longitude)) corresponding to the work location identifier, 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 work location identified by the work location identifier is the work location where the employee was. The inspection unit 533 then determines whether one or more work location identifiers obtained using the employee location information match the work location identifiers indicated by one or more location identification information included in the scheduled information, including their order. If they match, it determines that the scheduled information and the actual information match; if even one does not match, it determines that the scheduled information and the actual information do not match.

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

[0414] If the inspection unit 533 determines that there is information indicating teleworking in the scheduled information associated with the employee identifier under consideration and the day information for the day to be processed, and if there is a work location identifier or information corresponding to the work location identifier in the location identification information in the actual information associated with the employee identifier under consideration and the day information for the day to be processed, the inspection unit 533 determines that the scheduled information and the actual information do not match.

[0415] If the inspection unit 533 determines that there is information indicating teleworking in the schedule information associated with the employee identifier of interest and the day information for the day to be processed, it retrieves all employee location information associated with the employee identifier of interest and the day information for the day to be processed from the actual information storage unit 5172. Next, the inspection unit 533 retrieves the home location information paired with the employee identifier from the home location storage unit 511. Then, it determines whether the distance between the location information corresponding to the retrieved home location information and the employee location information satisfies a predetermined condition. If the predetermined condition is met, the schedule information and actual information match; if the predetermined condition is not met, the schedule information and actual information do not match. The predetermined condition is that the distance between the two points indicated by the two location information is within or less than a threshold.

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

[0417] The travel route acquisition unit 535 acquires one or more location-specific pieces of information from one or more types of information among the scheduled information or actual information stored in the work information storage unit 517, which corresponds to one employee identifier and one day's information, and acquires travel route information using the one or more location-specific pieces of information.

[0418] Travel route information is information about the travel routes of employees identified by an employee identifier. Travel route information is information that has one or more point-specific pieces of information, or information that can be obtained from one or more point-specific pieces of information. Examples of travel route information include "Home → Workplace X → Home" and "Home → Station A → Station B → Workplace X → Station B → Station C → Workplace Y → Station C → Station A → Home".

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

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

[0421] Furthermore, the movement route acquisition unit 535 acquires second location identification information that is paired with the second work location identifier from the work location information storage unit 512. The movement route acquisition unit 535 also acquires second movement route information from the first work location to the second work location using the first location identification information and the second location identification information. The movement route acquisition unit 535 may, for example, pass the first location identification information and the second location identification information to a server that returns movement route information, and receive the second movement route information from that server.

[0422] 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. Alternatively, the travel route acquisition unit 535 may acquire commuting route information corresponding to the employee identifier from the commuting route storage unit 515 and use that commuting route information to acquire third travel route information from the workplace to the home. Alternatively, the travel route acquisition unit 535 may pass the second location identification information and the home location information to a server that returns travel route information and receive third travel route information from that server.

[0423] Information that includes daily information, a first work location identifier that identifies the first work location at the start of work, and a second work location identifier that identifies the second work location at the end of work, is, for example, shift schedule information.

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

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

[0426] The travel route acquisition unit 535 acquires travel route information on a daily basis and for each employee identifier. The timing of when the travel route acquisition unit 535 acquires the travel route information is not specified.

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

[0428] It is preferable for the movement path acquisition unit 535 to acquire movement path information using the planned information or the actual information only when the inspection unit 533 has obtained an inspection result indicating that the planned information and the actual information match.

[0429] The travel expense acquisition unit 536 acquires travel expense information to identify travel expenses using planned or actual information. The travel expense acquisition unit 536 acquires travel expense information to identify travel expenses using, for example, travel route information acquired by the travel route acquisition unit 535. Travel expenses are expenses related to travel for the employee's business. Travel expenses are, for example, expenses incurred for travel. Travel expenses are usually expenses that the company should bear. Travel expenses are usually commuting expenses or transportation expenses.

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

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

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

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

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

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

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

[0437] For example, if the travel route information indicates "home → workplace X → home", the subject determination unit 537 determines that both the travel expense information corresponding to the route "home → workplace X" and the travel expense information corresponding to "workplace X → home" are subject "commuting expenses".

[0438] 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 accounted for 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 accounted for 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.

[0439] The re-inspection unit 538 determines whether the actual performance information received from the employee terminal device 6 to which the inspection unit 534 notified information regarding the inspection results, which indicates that the inspection results from the inspection unit 533 do not match, meets predetermined conditions. The predetermined conditions include, for example, that the information matches the planned information, that it includes information on predetermined items (e.g., reasons for non-matching, information indicating no problems, etc.), that it includes predetermined information (e.g., information indicating approval by a supervisor), that it includes information with a data volume exceeding a threshold (e.g., that the reasons are sufficiently described), and that the actual performance information was received within a predetermined time after the inspection result indicating non-matching was notified.

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

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

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

[0443] Here, output usually refers to transmission to another device (e.g., terminal device 6), but it may also be a concept that includes the transfer of processing results to other processing devices or other programs, display on a screen, projection using a projector, printing with a printer, sound output, storage on a recording medium, etc.

[0444] The travel route output unit 541 outputs the travel route information acquired by the travel route acquisition unit 535. The travel route output unit 541 typically outputs the travel route information in association with the employee identifier and day information. For example, the travel route output unit 541 outputs the first travel route information, the second travel route information, and the third travel route information acquired by the travel route acquisition unit 535. Here, output may also be a process such as transmission to another device (e.g., terminal device 6), passing to another module, or storage in the storage unit 51.

[0445] 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 the employee identifier and the date information.

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

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

[0448] For example, if the travel expense output unit 542 determines that the account determined by the account determination unit 537 is an account related to commuting expenses, it performs processing to store travel expense information in the commuting expense database 91, which manages commuting expenses.

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

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

[0451] The transmitting unit 55 transmits various types of information. These types of information are change information. Change information is information indicating that the default schedule information or default actual information has been changed. For example, change information may include revised schedule information, revised actual information, information on the parts that have been revised in the default schedule information, and information on the parts that have been revised in the default actual information.

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

[0453] For example, if the change determination unit 530 determines that the information is different, the change transmission unit 551 transmits the change information to the contacts indicated by one or more contact information corresponding to the employee identifier.

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

[0455] The terminal storage unit 61, which constitutes the terminal device 6, stores various types of information. These types of information include, for example, employee identifiers.

[0456] The terminal reception unit 62 receives various instructions and information. These instructions and information include, for example, scheduled information, actual information (e.g., sales activity information, input information), corrections to default scheduled information, and corrections to default actual information. The terminal reception unit 62 preferably receives scheduled information that has been corrected from the default scheduled information. The terminal reception unit 62 preferably receives actual information that has been corrected from the default actual information.

[0457] Any means of inputting instructions and information is acceptable, such as a touch panel, keyboard, mouse, or menu screen.

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

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

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

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

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

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

[0464] The card reader 71 is, for example, an IC card reader, and is a means of obtaining an employee identifier from a medium (card, mobile terminal, etc.) on which the employee identifier is stored, using short-range wireless communication such as Bluetooth (registered trademark).

[0465] The transportation expense database 81, which constitutes the accounting information management device 8, stores travel expense information corresponding to the account "transportation expenses" associated with an employee identifier. The travel expense information in the transportation expense database 81 is usually associated with daily 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 account "transportation expenses," associated with an employee identifier.

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

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

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

[0469] The receiving unit 52, the scheduled receiving unit 521, the actual receiving unit 522, and the terminal receiving unit 65 are usually implemented by wireless or wired communication means, but may also be implemented by means of receiving broadcasts.

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

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

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

[0473] The terminal output unit 66 may or may not be considered to include output devices such as displays and speakers. The terminal output unit 66 can be implemented using driver software for an output device, or driver software for an output device and an output device.

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

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

[0476] The information regarding the modification of the schedule information may be the modified schedule information itself, or it may be information about the parts that have been modified from the default schedule information. The change determination unit 530 may also 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.

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

[0478] The contact information may include, for example, a supervisor. It may also include, for example, the employee in question. Furthermore, the change information here refers to information indicating that the schedule information has been changed from the default information, and may also be the changed schedule information itself.

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

[0480] The information regarding the modification of performance information may be the modified performance information itself, or it may be information about the parts that have been modified from the default performance information. In addition, the change determination unit 530 may obtain the default performance information that is paired 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.

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

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

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

[0484] The processing unit 53 determines, for example, when a predetermined time (for example, the final time of work [for example, 10pm]) has arrived, or when performance information has been received, that it is time to perform an inspection.

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

[0486] (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 goes to step S1408; otherwise, the process returns to step S1401.

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

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

[0489] (Step S1410) The processing unit 53 performs the process of acquiring the travel route, etc. An example of the process of acquiring the travel route, etc. will be explained using the flowchart in Figure 16. The process of acquiring the travel route, etc. consists of the process of acquiring travel route information, the process of acquiring travel expense information, and the process of determining the category of travel expenses.

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

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

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

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

[0494] Furthermore, the notification unit 534 may send a screen prompting the employee (terminal device 6) to enter correct performance information, etc., identified by the employee identifier. The notification unit 534 may also send information indicating that the inspection results did not match to the contacts indicated by one or more contact details corresponding to the employee identifier. The information indicating that the inspection results did not match may also be considered to include information from the screen prompting the employee to enter correct performance information, and information from the screen prompting the employee to enter the reason for the mismatch.

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

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

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

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

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

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

[0501] In the flowchart in Figure 14, processing is terminated by power-off or processing termination interrupts.

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

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

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

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

[0506] (Step S1504) The inspection unit 533 determines whether the schedule information obtained in step S1502 is information indicating work. If it is information indicating work, the unit proceeds to step S1505; otherwise, the unit proceeds to step S1515. Note that information indicating work means information about a workday, not information about a day off.

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

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

[0509] (Step S1506) The inspection unit 533 determines whether or not the i-th location identification information exists in the schedule information obtained in step S1502. If the i-th location identification information exists, the unit proceeds to step S1507; otherwise, the unit proceeds to step S1513.

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

[0511] (Step S1508) The inspection unit 533 determines whether or not the i-th location identification information exists in the performance information obtained in step S1503. If the i-th location identification information exists, the unit proceeds to step S1509; otherwise, the unit proceeds to step S1512.

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

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

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

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

[0516] (Step S1512) The inspection unit 533 assigns "information indicating that it does not match" to the variable "inspection result". It returns to the higher-level process.

[0517] (Step S1513) The inspection unit 533 determines whether or not the i-th location identification information exists in the performance information obtained in step S1503. If the i-th location identification information exists, the unit proceeds to step S1512; otherwise, the unit proceeds to step S1514.

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

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

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

[0521] (Step S1601) The travel route acquisition unit 535 acquires the employee identifier of the employee whose travel route information is to be acquired.

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

[0523] (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 acquisition process. The commute route acquisition process will be explained using the flowchart in Figure 17.

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

[0525] (Step S1605) The travel route acquisition unit 535 determines whether or not the i-th location identification information exists in the planned information or actual information acquired in step S1602. If the i-th location identification information exists, the unit proceeds to step S1606; otherwise, the unit proceeds to step S1609.

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

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

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

[0529] (Step S1609) The travel route acquisition unit 535, etc., acquires travel route information from the last workplace identified by the last (i-1) point identification information to home. It returns to the higher-level process. This process is called the return-home route acquisition process. The return-home route acquisition process will be explained using the flowchart in Figure 19.

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

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

[0532] (Step S1702) The travel route acquisition unit 535 determines whether the travel information acquired in step S1701 indicates that the user will use a vehicle (e.g., a private car) for commuting. If the information indicates that the user will use a vehicle for commuting, the unit proceeds to step S1703; if the information indicates that the user will not use a vehicle for commuting, the unit proceeds to step S1705. If travel information could not be acquired in step S1701, the unit usually proceeds to step S1705.

[0533] (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 mobile device)". The first travel route information is a part of the travel route information that makes up the travel route information that is ultimately output.

[0534] (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. It returns to the higher-level processing. At this point, the account determination unit 537 may acquire the account "commuting expenses".

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

[0536] (Step S1706) The travel expense acquisition unit 536 acquires periodic information paired with the employee identifier of the target employee from the periodic information storage unit 513. However, there may be cases where the travel expense acquisition unit 536 is unable to acquire periodic information.

[0537] (Step S1707) The travel expense acquisition unit 536 determines whether the regular information acquired in step S1706 indicates that the user has acquired a commuter pass. If the information indicates that the user has acquired a commuter pass, the unit proceeds to step S1708; otherwise, the unit proceeds to step S1709. If regular information could not be acquired in step S1706, the unit usually proceeds to step S1709.

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

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

[0540] (Step S1710) The subject determination unit 537 acquires the subject "commuting expenses".

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

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

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

[0544] (Step S1801) The travel path acquisition unit 535 acquires two point identification pieces of information.

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

[0546] (Step S1803) The travel expense acquisition unit 536 acquires travel expense information between two work locations using two location identification pieces of information. The travel expense acquisition unit 536, for example, transmits the two location identification pieces of information to an external server (not shown) and receives travel expense information or information that will become the travel expense information from the server. The travel expense acquisition unit 536, for example, acquires travel expense information from the travel expense information or information that will become the travel expense information received in step S1802.

[0547] (Step S1804) Subject determination unit 537 acquires the subject "Transportation expenses".

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

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

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

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

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

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

[0554] (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. It returns to the higher-level processing. At this point, the account determination unit 537 may acquire the account "commuting expenses".

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

[0556] (Step S1906) The travel expense acquisition unit 536 acquires periodic information paired with the employee identifier of the target employee from the periodic information storage unit 513. However, there may be cases where the travel expense acquisition unit 536 is unable to acquire periodic information.

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

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

[0559] (Step S1909) The travel expense acquisition unit 536 acquires travel expense information from the last place of work to home. The travel expense acquisition unit 536 acquires travel expense information that is paired with the employee identifier of the employee in question, for example, from the storage unit 51, from the place of work to home. The travel expense acquisition unit 536 also sends, for example, the last place identification information and the home location identification information to a server (not shown), receives travel expense information or travel expense information that forms the basis of the travel expense information, and acquires the travel expense information.

[0560] (Step S1910) The subject determination unit 537 acquires the subject "commuting expenses".

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

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

[0563] Next, the re-inspection and other processes in step S1415 will be explained using the flowchart in Figure 20.

[0564] (Step S2001) The re-examination unit 538 determines whether or not performance information is included in the received information. If performance information is included, the process proceeds to step S1408; otherwise, the process proceeds to step S2002.

[0565] (Step S2002) The re-examination unit 538 acquires the received information.

[0566] (Step S2003) The re-inspection unit 538 acquires predetermined conditions for the storage unit 51.

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

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

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

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

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

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

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

[0574] (Step S2104) The terminal processing unit 63 converts the information received in step S2103 into information for output. The terminal output unit 66 outputs the information. The process returns to step S2101.

[0575] (Step S2105) The terminal processing unit 63 determines whether it is time to transmit mobile location information. If it is time to transmit mobile location information, the unit proceeds to step S2106; otherwise, the unit proceeds to step S2108.

[0576] (Step S2106) The terminal processing unit 63 acquires mobile location information. The terminal processing unit 63 acquires the employee identifier of the terminal storage unit 61 and constitutes information having the employee identifier and mobile location information, and having a structure for transmission.

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

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

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

[0580] In the flowchart shown in Figure 21, processing is terminated by power-off or processing termination interrupts.

[0581] As described above, according to this embodiment, accurate information about an employee's travel route can be obtained using one or more types of information from employee schedule information and actual travel information.

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

[0583] Furthermore, in this embodiment, the consistency between planned information and actual information can be checked, and if they are not consistent, the employee can be notified of the discrepancy.

[0584] Furthermore, in this embodiment, travel expense information can be obtained. Also, the appropriate account category for the travel expense information can be obtained.

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

[0586] Furthermore, in this embodiment, appropriate commuting expenses can be obtained using regular information.

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

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

[0589] Furthermore, in this embodiment, information on appropriate travel routes can be output for travel expense information of employees who move between two or more workplaces in a single day.

[0590] Furthermore, in this embodiment, it is possible to determine the appropriate account for travel expense information of employees who move between two or more workplaces in a single day.

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

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

[0593] Furthermore, in this embodiment, appropriate processing can be performed if the planned information and the actual information do not match.

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

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

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

[0597] Furthermore, the software that implements the information processing device 5 in this embodiment is a program as follows. In other words, this program is a program that causes a computer that can access a work information storage unit, which stores one or more types of information, such as scheduled information which is information about an employee's work schedule and has location identification information that identifies the place of work, or actual information which is information about an employee's actual work and has location identification information, in association with one or more employee identifiers, to function as a travel route acquisition unit that acquires location identification information corresponding to an employee identifier from the work information storage unit and uses the location identification information to acquire travel route information relating to the travel route of an employee identified by the employee identifier, and a travel route output unit that outputs the travel route information.

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

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

[0600] In Figure 23, the computer 301 includes, in addition to the CD-ROM drive 3012, an MPU 3013, a bus 3014 connected to the CD-ROM drive 3012, a ROM 3015 for storing programs such as boot-up programs, a RAM 3016 connected to the MPU 3013 for temporarily storing 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, the computer 301 may further include a network card that provides connectivity to a LAN.

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

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

[0603] In the above program, steps such as sending information and receiving information do not include hardware-based processing, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).

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

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

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

[0607] It goes without saying that the present invention is not limited to the embodiments described above, and various modifications are possible, all of which are also included within the scope of the present invention. [Industrial applicability]

[0608] As described above, the information processing device according to the present invention has the effect of being able to acquire the accurate movement routes of employees and is useful as a server or the like that makes up a corporate system. [Explanation of symbols]

[0609] 1. Cost Inspection Device 2. Applicant's terminal 3. External Servers 4. Expense Management System 5. Information Processing Device 6 Terminal devices 7. Building entry / exit information acquisition device 8. Accounting Information Management System 9 Human resources information management device 11, 51 Storage section 12 Reception Department 13, 53 Processing Unit Output section 14, 54 21 First storage unit 22 First Reception Department 23 First Processing Unit 24 First Transmitter 25 First receiving unit 26 First output section 52 Receiving section 55 Transmitter 61 Terminal storage section 62 Terminal Reception Section 63 Terminal Processing Unit 64 Terminal Transmitter 65 Terminal receiving unit 66 Terminal output section 71 Card Reader 81 Transportation Expense Database 91 Commuting Expense Database 111 Expense Information Storage Unit 112 Applicant Collection Storage Unit 113 Company Regulations Information Storage Unit 114 Restaurant Storage Unit 115 Adult Entertainment Establishment Collection Storage Unit 116 Recipient Data Storage Unit 117 Card Usage Expense Storage Section 118 Transportation Information Storage Unit 121 Expense Reception Department 131, 533 Inspection Department 132 Statistical Processing Section 141 Result Output Section 511 Home location storage unit 512 Workplace Information Storage Unit 513 Periodic Information Storage Unit 514 Mobile Information Storage Unit 515 Commuter Route Storage Unit 516 Default storage unit 517 Work Information Storage Unit 521 Scheduled Receiving Unit 522 Performance Receiving Unit 530 Change Judgment Unit 531 Scheduled Storage Unit 532 Performance Accumulation Department 534 Notification Department 535 Movement path acquisition unit 536 Traveling Expenses Acquisition Department 537 Subject Selection Department 538 Re-examination Department 539 Reprocessing Unit 541 Output section for travel path 542 Travel Expense Output Unit 551 Change Transmission Section 1121 Personal Information Storage Section 1122 Attendance Information Storage Unit 1123 Building Entry / Exit Information Storage Unit 1124 Sales Activity Information Storage Unit 1125 Card statement information storage unit 1126 Vehicle location information storage unit 1181 Calculation Information Storage Unit 1182 Map Information Storage Unit 1311 Image inspection method 5171 Schedule Information Storage Unit 5172 Performance Information Storage Unit

Claims

1. A work information storage unit stores information about an employee's work schedule, which includes information indicating teleworking and day information specifying a day, and actual work information, which includes location information and day information, associated with one or more employee identifiers. From this storage unit, for each employee identifier, the inspection unit retrieves the schedule information and actual work information corresponding to the same day information, and checks whether the actual work information indicates teleworking. The system comprises an output unit that outputs information regarding the inspection results in the inspection unit, The aforementioned inspection unit is If it is determined that there is information indicating teleworking in the scheduled information associated with an employee identifier and the day information to be processed, and if there is a work location identifier or information corresponding to the work location identifier in the location identification information in the actual information associated with the employee identifier and the day information to be processed, then it is determined that the scheduled information and the actual information do not match. The output unit is, An information processing device that outputs information regarding inspection results indicating that the scheduled information and actual information of an employee identified by the aforementioned employee identifier do not match.

2. The output unit is, The information processing apparatus according to claim 1, further comprising a notification unit for notifying an employee identified by an employee identifier corresponding to the inspection result of the inspection unit.

3. The aforementioned notification unit, The information processing device according to claim 2, wherein if the inspection results from the inspection unit indicate that the results do not match, the device notifies the employee identified by the employee identifier corresponding to the inspection result of information regarding the inspection result.

4. The inspection results from the aforementioned inspection unit indicate that the results do not match, and the re-inspection unit determines whether the performance information received from the terminal device of the employee who was notified by the notification unit regarding the said inspection results meets predetermined conditions. The information processing apparatus according to claim 2 or 3, further comprising a reprocessing unit that performs different processing according to the judgment result in the re-inspection unit.

5. The inspection results from the aforementioned inspection unit indicate that the inspection results do not match, and the performance receiving unit receives performance information from the terminal device of the employee to whom the notification unit notified information regarding the inspection results, The information processing apparatus according to claim 3, further comprising: a performance storage unit that stores the performance information in the work information storage unit, associating it with the employee identifier of the employee.

6. A creation support method comprising all the processing performed by the information processing device described in any one of claims 1 to 5.

7. Computers, A program for causing an information processing device to function as described in any one of claims 1 to 5.

Images