Inspection apparatus, inspection method, and program

Abstract

To solve the problem that a conventional inspection device cannot inspect a book document corresponding to an electronic book preservation law or the like.SOLUTION: An inspection device 1 includes an account book document acquisition part 131 for acquiring account book document information having one or more kinds of information between character string information and a document image, an inspection part 133 for determining whether or not the account book document information matches an inspection condition corresponding to the Electronic Account Book Preservation Act and acquiring an inspection result, and an output part 14 for outputting the inspection result.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an inspection device for inspecting book document information. [Background technology]

[0002] Conventionally, there have been expense management devices that manage expense information (see, for example, Patent Document 1 and Non-Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-224545 [Non-patent literature]

[0004] [Non-Patent Document 1] “Expense reimbursement system for growing and transforming companies | Money Forward Cloud Expenses,” [online], [Retrieved December 21, 2021], Internet [URL: https: / / biz.moneyforward.com / expense] Summary of the Invention [Problem to be solved by the invention]

[0005] However, the prior art has not been able to inspect accounting documents that comply with the Electronic Bookkeeping Act and the like. [Means for solving the problem]

[0006] The inspection device of the first invention is an inspection device that includes a ledger document acquisition unit that acquires ledger document information having one or more types of information selected from character string information and document images, an inspection unit that determines whether the ledger document information meets inspection conditions and acquires inspection results, and an output unit that outputs the inspection results.

[0007] This configuration makes it possible to inspect accounting documents that comply with the Electronic Bookkeeping Act and other regulations.

[0008] Furthermore, the inspection device of the second invention is an inspection device in which, compared to the first invention, the inspection unit determines whether or not an image condition regarding the document image is satisfied, and obtains the inspection result.

[0009] With this configuration, document images can be inspected in accordance with the Electronic Bookkeeping Act and the like.

[0010] In addition, the inspection device of the third invention is an inspection device in which, compared to the second invention, the inspection unit acquires one or more character strings from a document image, determines whether the one or more character strings satisfy the reading condition that predetermined information including one or more of the following information: amount, date, and business partner, can be acquired from the document image, and obtains the inspection result.

[0011] With this configuration, document images can be inspected in accordance with the Electronic Bookkeeping Act and the like.

[0012] In addition, the inspection device of the fourth invention is an inspection device in which, compared to the second invention, the inspection unit acquires the file format of the document image, determines whether the file format satisfies the file format conditions, and acquires the inspection results.

[0013] With this configuration, document images can be inspected in accordance with the Electronic Bookkeeping Act and the like.

[0014] Furthermore, the inspection device of the fifth invention is an inspection device in which, compared to the second invention, the inspection unit acquires the resolution of the document image, determines whether the resolution satisfies the resolution condition, and acquires the inspection result.

[0015] With this configuration, document images can be inspected in accordance with the Electronic Bookkeeping Act and the like.

[0016] In addition, the inspection device of the sixth invention is an inspection device in which, compared to the second invention, the inspection unit acquires the resolution and size of the document image, uses the resolution and size to acquire the paper size of the paper that is the basis of the document image, determines whether the paper size satisfies the paper size conditions, and acquires the inspection results.

[0017] With this configuration, document images can be inspected in accordance with the Electronic Bookkeeping Act and the like.

[0018] Furthermore, the inspection device of the seventh invention differs from the second invention in that the inspection unit acquires the gradation of the document image, determines whether the gradation satisfies the gradation conditions, and acquires the inspection result.

[0019] With this configuration, document images can be inspected in accordance with the Electronic Bookkeeping Act and the like.

[0020] Furthermore, the inspection device of the eighth invention is an inspection device according to any one of the first to seventh inventions, in which the string information or document image contained in the ledger document information has a date, the inspection unit acquires the date from the string information or document image, acquires the acquisition date when the ledger document acquisition unit acquired the string information or document image, determines whether the difference between the date and the acquisition date satisfies the input period condition, and acquires the inspection result.

[0021] This configuration makes it possible to inspect accounting documents that comply with the Electronic Bookkeeping Act and other regulations.

[0022] Furthermore, the inspection device of the ninth invention is an inspection device according to any one of the first to eighth inventions, in which the inspection unit acquires one or more character strings from a document image acquired by the ledger document acquisition unit, determines whether a consistency condition is satisfied, which is a condition regarding the consistency between the one or more character strings and the character string information acquired by the ledger document acquisition unit, and acquires an inspection result.

[0023] This configuration enables consistency inspection in accordance with the Electronic Bookkeeping Act and the like.

[0024] Furthermore, the inspection device of the tenth invention is an inspection device in which, compared to the ninth invention, the ledger document acquisition unit acquires one or more pieces of character string information and two or more document images, and further includes a correspondence detection unit that detects correspondence between one piece of character string information and two or more document images, and the inspection unit determines whether or not the one piece of character string information and the two or more document images in the correspondence detected by the correspondence detection unit satisfy a consistency condition, and obtains an inspection result.

[0025] With this configuration, consistency inspections that comply with the Electronic Bookkeeping Act and the like can be carried out appropriately.

[0026] Furthermore, the inspection device of the eleventh invention is an inspection device in which, compared to the ninth invention, the ledger document acquisition unit acquires two or more pieces of character string information and one or more document images, and further includes a correspondence detection unit that detects correspondence between the two or more pieces of character string information and one document image, and the inspection unit determines whether the two or more pieces of character string information and the one document image in the correspondence detected by the correspondence detection unit satisfy a consistency condition, and obtains an inspection result.

[0027] With this configuration, consistency inspections that comply with the Electronic Bookkeeping Act and the like can be carried out appropriately.

[0028] Furthermore, the inspection device of the twelfth invention is an inspection device in which, compared to the ninth invention, the ledger document acquisition unit acquires two or more pieces of character string information and one or more document images, and further includes a correspondence detection unit that detects correspondence between the two or more pieces of character string information and the two or more document images, and the inspection unit determines whether the two or more pieces of character string information and the two or more document images in the correspondence detected by the correspondence detection unit satisfy a consistency condition, and obtains an inspection result.

[0029] With this configuration, consistency inspections that comply with the Electronic Bookkeeping Act and the like can be carried out appropriately.

[0030] Furthermore, the inspection device of the thirteenth invention is an inspection device according to any one of the tenth to twelfth inventions, in which there are at least two ledger and document management devices used by one user, and the inspection device further includes an identifier conversion information storage unit in which one or more identifier conversion information indicating a correspondence between a first user identifier in a first ledger and document management device used by the user and a second user identifier in a second ledger and document management device used by the user is stored, the ledger and document acquisition unit acquires character string information associated with the user identifier and a document image associated with the user identifier, and the correspondence detection unit refers to the identifier conversion information storage unit and detects that there is a correspondence using the identifier conversion information even if the user identifier associated with the character string information and the user identifier associated with the document image are different.

[0031] With this configuration, it is possible to appropriately check the consistency in accordance with the Electronic Bookkeeping Act and the like, using information acquired from two or more accounting document management devices.

[0032] Furthermore, the inspection device of the fourteenth invention is an inspection device in which, compared to any one of the first to thirteenth inventions, the ledger document acquisition unit acquires at least one type of information from one or more ledger document management devices: character string information and document images.

[0033] This configuration makes it possible to provide an environment for adding an inspection function for book and document information without adding functions to one or more book and document management devices.

[0034] Furthermore, the inspection device of the fifteenth invention differs from the fourteenth invention in that the ledger document acquisition unit acquires string information from one ledger document management device and acquires document images from another ledger document management device, and the inspection unit uses the string information and document images acquired from the different ledger document management devices to determine whether or not the inspection conditions are met and obtains the inspection results.

[0035] With this configuration, inspection can be performed using character string information and document images obtained from different ledger document management devices.

[0036] Furthermore, the inspection device of the sixteenth invention is an inspection device that, compared to the fourteenth or fifteenth invention, further comprises a notification unit that notifies the inspection results to notification destinations specified by one or more notification destination information corresponding to the accounting document information on which the inspection results are based.

[0037] With this configuration, the inspection results of the book and document information acquired from the external book and document management device can be notified to an appropriate notification destination.

[0038] The inspection device of the seventeenth aspect of the present invention is the inspection device of the sixteenth aspect of the present invention, wherein the notification unit notifies different notification destinations of the inspection results depending on the inspection results.

[0039] With this configuration, the test results can be notified to different notification destinations depending on the test results.

[0040] Furthermore, the inspection device of the eighteenth invention is an inspection device in which, compared to the sixteenth or seventeenth invention, it further includes a notification destination acquisition unit that acquires one or more pieces of notification destination information corresponding to the accounting document information acquired by the accounting document acquisition unit from an accounting document management device in which the accounting document information is stored, and the notification unit notifies the notification destinations specified by each of the one or more pieces of notification destination information acquired by the notification destination acquisition unit of the inspection device.

[0041] With this configuration, notification destination information can also be acquired from the ledger document management device, and the inspection results can be notified using the notification destination information.

[0042] Furthermore, the inspection device of the 19th invention is an inspection device in which, compared to any one of the 16th to 18th inventions, the accounting document acquisition unit acquires two or more pieces of accounting document information for a specified period for each user from the accounting document management device, and the inspection unit uses two or more pieces of expense information to inspect one or more pieces of expense information and obtains the inspection results.

[0043] With this configuration, an examination can be performed using two or more pieces of expense information for a predetermined period for each user.

[0044] Furthermore, the inspection device of the twentieth invention is an inspection device according to any one of the sixteenth to nineteenth inventions, wherein the accounting document acquisition unit acquires accounting document information from one or more accounting document management devices.

[0045] This configuration makes it possible to provide an environment for adding an inspection function for book and document information without adding functions to one or more book and document management devices.

[0046] Furthermore, the inspection device of the twenty-first invention is an inspection device that, compared to the twentieth invention, further comprises an access information storage unit that stores, for each of the one or more ledger document management devices, access information for accessing each of the one or more ledger document management devices, and the ledger document acquisition unit acquires ledger document information for each of the one or more ledger document management devices using the corresponding access information.

[0047] This configuration makes it possible to provide an environment for adding an inspection function for book and document information without adding functions to one or more book and document management devices.

[0048] Furthermore, the inspection device of the twenty-second invention is an inspection device in which, compared to the twentieth or twenty-first invention, the accounting document acquisition unit acquires accounting document information at different times for each accounting document management device, for each organization using a accounting document management device, or for each user using a accounting document management device.

[0049] With this configuration, the test results can be notified to each user at an appropriate time.

[0050] Furthermore, the inspection device of the twenty-third invention is an inspection device according to any one of the twentieth to twenty-second inventions, wherein the accounting document acquisition unit acquires one or more pieces of accounting document information for different periods for each accounting document management device, or for each organization that uses a accounting document management device, or for each user that uses a accounting document management device.

[0051] With this configuration, expense information for an appropriate period can be checked for each user, etc.

[0052] Furthermore, the inspection device of the twenty-fourth invention is an inspection device according to any one of the twentieth to twenty-third inventions, wherein the accounting document acquisition unit receives accounting document information from one or more accounting document management devices.

[0053] With this configuration, the accounting document information can be inspected in accordance with a request from the accounting document management device.

[0054] The inspection device of a twenty-fifth aspect of the present invention is the inspection device of any one of the twentieth to twenty-fourth aspects of the present invention, wherein the notification unit transmits the inspection results to the ledger document management device.

[0055] With this configuration, it is possible to inspect the accounting document information in accordance with a request from the accounting document management device, and to transmit the inspection results to the accounting document management device. [Effects of the Invention]

[0056] The inspection device according to the present invention can inspect book documents that comply with the Electronic Bookkeeping Law and the like. [Brief explanation of the drawings]

[0057] [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 inspection device 1 [Figure 4] A flowchart illustrating an example of the operation of the inspection device 1 [Figure 5] 1 is a flowchart illustrating a first example of processing of the same test, etc. [Figure 6] 10 is a flowchart illustrating a second example of the processing of the same test, etc. [Figure 7] 10 is a flowchart illustrating an example of the notification destination information acquisition process. [Figure 8] A flowchart illustrating an example of the correspondence determination process [Figure 9]A flowchart illustrating an example of the correspondence information determination process [Figure 10] Flowchart illustrating an example of same-to-many determination processing [Figure 11] A flowchart illustrating an example of the consistency condition determination process [Figure 12] 10 is a flowchart illustrating an example of the image condition determination process. [Figure 13] A flowchart illustrating an example of the input period condition determination process [Figure 14] FIG. 10 shows the access information management table. [Figure 15] The table showing the information acquisition unit management table [Figure 16] The notification destination management table [Figure 17] A diagram showing an example of the same bookkeeping document information [Figure 18] Figure showing an example of the test results output [Figure 19] Block diagram of information system B in embodiment 2 [Figure 20] A flowchart illustrating an example of the operation of the inspection device 4 [Figure 21] Overview of the computer system in the above embodiment [Figure 22] Block diagram of the computer system DETAILED DESCRIPTION OF THE INVENTION

[0058] Hereinafter, embodiments of an inspection device and the like will be described with reference to the drawings. Note that, in the embodiments, components with the same reference numerals perform similar operations, and therefore, repeated description may be omitted.

[0059] (Embodiment 1) In this embodiment, an information system equipped with an inspection device that acquires accounting document information, inspects whether it meets inspection conditions, and outputs the inspection results will be described. Note that the inspection conditions are, for example, image conditions (to be described later), input period conditions (to be described later), and consistency conditions (to be described later).

[0060] Ledger document information is information about ledger documents. Ledger document information is usually electronic transaction data that must be stored under the Electronic Bookkeeping Act. Ledger documents preferably contain information about amounts, dates, and business partners. Examples of ledger documents include receipts, contracts, receipts, IOUs, bankbooks, checks, promissory notes, securities delivery statements, bond applications, contract applications, invoices, delivery notes, waybills, export certificates, inspection reports, warehouse reports, cargo receipts, estimates, and purchase orders. Ledger document information is electronic data of ledger documents. Ledger document information usually contains text information and document images. However, ledger document information may consist of only one of text information and document images. Text information is information consisting of one or more character strings. Document images are images, such as PDF, JPEG, PNG, and GIF, but the format is not important. The document image is, for example, an image of a receipt, an image of an invoice, or an image of a contract.

[0061] In addition, in this embodiment, we will explain an information system equipped with an inspection device that inspects whether a piece of ledger document information meets inspection conditions and outputs inspection results, even if the string information contained in the piece of ledger document information and the document image have a 1:n, n:1, or n:m relationship.

[0062] In addition, in this embodiment, an information system including an inspection device that associates one or more pieces of character string information constituting one piece of ledger document information with one or more document images will be described.

[0063] In addition, in this embodiment, an information system including a checking device that checks consistency conditions using character string information and document images acquired from different routes will be described.

[0064] In this embodiment, an inspection device will be described that acquires accounting document information from one or more accounting document management devices, inspects the accounting document information, and transmits the inspection results to one or more parties.

[0065] In this embodiment, an inspection device will be described in which the destination of notification of the inspection results varies depending on the inspection results.

[0066] In this embodiment, an inspection device will be described that also acquires notification information of one or more parties from the ledger document management device and transmits inspection results to the parties using the notification information.

[0067] In this embodiment, an inspection device will be described that acquires two or more pieces of book document information for a predetermined period for each user and inspects the two or more pieces of book document information.

[0068] In addition, in this embodiment, access information is managed for each ledger document management device, and an inspection device is described that uses the access information to access the ledger document management device and acquires ledger document information from the ledger document management device.

[0069] In addition, in this embodiment, an inspection device in which the timing for acquiring book and document information differs for each book and document management device, each organization, each user, etc. will be described.

[0070] Furthermore, in this embodiment, an inspection device that acquires book and document information for different periods for each book and document management device, each organization, each user, etc. will be described.

[0071] In this embodiment, information X being associated with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not important. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, or information Y may be included in information X, etc.

[0072] 1 is a conceptual diagram of an information system A in this embodiment. The information system A comprises an inspection device 1, one or more ledger document management devices 2, and one or more terminal devices 3. Note that the information system A may comprise only the inspection device 1 and one or more terminal devices 3. In such a case, the inspection device 1 inspects only the ledger document information that it receives.

[0073] The inspection device 1 is a device that inspects accounting document information. It is preferable that the inspection device 1 inspects whether the accounting document information is proper. It is preferable that the inspection device 1 inspects whether the accounting document information complies with the Electronic Bookkeeping Act. It is preferable that the inspection device 1 is a device that inspects accounting document information stored in one or more accounting document management devices 2 that are devices separate from the inspection device 1. The inspection device 1 may accumulate and manage accounting document information. It is preferable that the inspection device 1 inspects the accounting document information managed by the inspection device 1.

[0074] The ledger document management device 2 is a device that accumulates and manages one or more pieces of ledger document information received from a terminal device 3, etc. The ledger document information managed by the ledger document management device 2 is inspected by the inspection device 1. Therefore, the ledger document management device 2 does not need to have a function for inspecting ledger document information.

[0075] The inspection device 1 and the ledger document management device 2 are usually so-called servers, such as a cloud server, an ASP server, etc. The inspection device 1 and the ledger document management device 2 may be of any type.

[0076] The terminal device 3 is a terminal used by a user. The user may be, for example, a person who applies for accounting documents, a person who manages expenses (such as an accounting department member or a company representative), a manager of the accounting document management device 2, or a manager of the inspection device 1. The terminal device 3 may be, for example, a so-called personal computer, a tablet terminal, a smartphone, or the like, and the type of the terminal device is not important.

[0077] Fig. 2 is a block diagram of the information system A in this embodiment. Fig. 3 is a block diagram of the inspection device 1.

[0078] The inspection device 1 includes a storage unit 11, a receiving unit 12, a processing unit 13, and an output unit 14. The storage unit 11 includes an access information storage unit 111, an identifier conversion information storage unit 112, and an accounting document storage unit 113. The processing unit 13 includes an accounting document acquisition unit 131, a correspondence detection unit 132, an inspection unit 133, and a notification destination acquisition unit 134. The output unit 14 includes a notification unit 141.

[0079] The ledger document management device 2 includes a management storage unit 21, a management reception unit 22, a management processing unit 23, a management transmission unit 24, a management reception unit 25, and a management output unit 26.

[0080] The terminal device 3 includes a terminal storage unit 31, a terminal reception unit 32, a terminal processing unit 33, a terminal transmission unit , a terminal reception unit 35, and a terminal output unit .

[0081] Various types of information are stored in the storage unit 11 constituting the inspection device 1. The various types of information include, for example, access information (to be described later), identifier conversion information (to be described later), accounting document information (to be described later), one or more pieces of timing information, one or more pieces of period information, one or more pieces of notification destination information, and one or more execution modules for accessing each of the accounting document management devices 2.

[0082] The timing information is information that specifies the timing of acquiring accounting document information from the accounting document management device 2. Examples of the timing information include "end of every month," "23:00 every Friday," and "every day." The timing information is stored, for example, for each accounting document management device 2, for each organization that uses the accounting document management device 2, or for each user that uses the accounting document management device 2. In other words, the timing of acquiring expense information may differ for each accounting document management device 2, for each organization that uses the accounting document management device 2, or for each user that uses the accounting document management device 2. The timing information is associated with, for example, a device identifier, an organization identifier, or a user identifier. The device identifier is information that identifies the accounting document management device 2, such as a device ID, an IP address, or a URL for accessing a database that stores accounting document information. The organization identifier is information that identifies the organization to which the user who applies for accounting documents belongs. The organization identifier is, for example, an organization ID or an organization name. The organization is, for example, a company, a department, or an organization. The user identifier is information that identifies a user. The user identifier is, for example, a user ID, an email address, or a telephone number. The user identifier is preferably, for example, the user ID of the user used in the accounting document management device 2.

[0083] The period information is information that identifies the period of time for which the accounting document information acquired from the accounting document management device 2 is to be inspected. The period information may also be information that identifies the period for which the accounting document information is to be inspected at one time. The period may be determined by the transaction date, which is a date contained in the accounting document information, or by the acquisition date on which the accounting document information was acquired by the inspection device 1 or the accounting document management device 2. Examples of period information include one month, one year, six months, one week, and "until the end of December 2021." The period information is stored, for example, for each accounting document management device 2, each organization that uses the accounting document management device 2, or each user that uses the accounting document management device 2. In other words, the period for which accounting document information is acquired at one time may differ for each accounting document management device 2, each organization that uses the accounting document management device 2, or each user that uses the accounting document management device 2. The period information is associated with, for example, a device identifier, an organization identifier, or a user identifier.

[0084] The notification destination information is information that specifies the destination to which the test results are to be notified. The notification destination information is, for example, an email address, a telephone number, a user ID of the notification app, or information that specifies a storage area of ​​the server that can be viewed by the user (for example, a URL). The notification destination information is associated with, for example, a user identifier, an organization identifier, or a device identifier. The stored notification destination information may be different for each accounting document management device 2, each organization, or each user.

[0085] The notification destination information may be associated with the conditions using the inspection results. In other words, the notification destination of the inspection results may differ depending on the inspection results. For example, the notification destination of the inspection results may differ depending on whether the inspection results are "incorrect" or "valid." Furthermore, the notification destination of the inspection results may differ depending on the type of inaccuracy in the inspection results (for example, inaccuracy in inconsistent conditions, inaccuracy in image conditions, or inaccuracy in duplicate conditions).

[0086] Furthermore, the one or more pieces of notification destination information in the storage unit 11 may be information associated with the accounting document information and received from the accounting document management device 2. The one or more pieces of notification destination information in the storage unit 11 may be information stored before the accounting document information is inspected.

[0087] The access information storage unit 111 stores one or more pieces of access information. The access information storage unit 111 stores access information for each ledger document management device 2. The access information is information for accessing the ledger document management device 2. The access information can also be said to be information that identifies a method for accessing the ledger document management device 2. The access information is, for example, information that identifies an API for accessing the ledger document management device 2, an execution module for accessing the ledger document management device 2, the name of the execution module for accessing the ledger document management device 2, and the name of a function for accessing the ledger document management device 2. Each of the one or more pieces of access information is associated with a ledger document management device 2. The access information is associated with, for example, a device identifier.

[0088] The identifier conversion information storage unit 112 stores one or more pieces of identifier conversion information. The identifier conversion information is information indicating the correspondence between a first user identifier and a second user identifier. The first user identifier and the second user identifier are identifiers of the same user but are used in different devices. The first user identifier is, for example, a user identifier managed by the inspection device 1 or a user identifier managed by the accounting document management device 2. That is, accounting document information of a single user may be acquired from different devices among one or more accounting document management devices 2 or inspection devices 1. Furthermore, character string information and document images constituting one accounting document information of a single user may be acquired from different devices among one or more accounting document management devices 2 or inspection devices 1. Furthermore, two or more pieces of character string information constituting one accounting document information of a single user may be acquired from different devices among one or more accounting document management devices 2 or inspection devices 1. Furthermore, two or more pieces of document images constituting one accounting document information of a single user may be acquired from different devices among one or more accounting document management devices 2 or inspection devices 1.

[0089] The accounting document storage unit 113 stores one or more pieces of accounting document information. The accounting document information is usually associated with a user identifier. It is preferable that the accounting document information is associated with the organization identifier of the organization to which the user belongs.

[0090] The character string information included in the accounting document information preferably includes one or more of the following information: amount, date (transaction date), and business partner. The accounting document information is, for example, expense information.

[0091] Expense information is information that identifies the details of the expense that has been claimed. Expense information includes, for example, expenditure amount information (also simply referred to as the amount), a destination identifier, a store identifier (also simply referred to as the store), a business partner identifier (also simply referred to as the business partner), usage date information (also simply referred to as the date), a payment method identifier, an account, a summary, and an approver identifier. Expenditure amount information is information that identifies the amount used as an expense. The destination identifier is information that indicates the destination of the receipt and is information that identifies the company or other entity that will pay the amount. The store identifier is information that identifies the store that used the expense. The store identifier is, for example, the store name, store ID, store URL, or store telephone number. The business partner identifier is information that identifies the business partner that used the expense. The business partner identifier is information that identifies the party that provided benefits such as entertainment or a gift. The business partner identifier is, for example, the organization name (e.g., company name or organization name), name, and business partner ID. Usage date 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," "○○ PAY," etc. The item is information that identifies the classification of the expense. The item may also be called an expense type identifier. The item is, for example, business trip expenses, travel and transportation expenses (or transportation expenses), accommodation expenses, business trip expenses, entertainment expenses, and meeting expenses. The approver identifier is information that identifies the person who approves the expense. The approver identifier is, for example, an applicant identifier or a position identifier. The applicant identifier is information that identifies the applicant who applied for the expense, such as a name or ID. The position identifier is information that identifies a position, such as a job title (e.g., "department manager" or "director") or ID. Expense information is usually associated with the user identifier of the user who applied. Expense information may include a receipt image, which is an example of a document image. The receipt image is an image of the receipt. The receipt image is, for example, an image obtained by photographing a receipt. It goes without saying that the data structure of the receipt image is not important, such as JPEG or GIF. The receipt image is an example of a document image. The expense information includes, for example, participant information and number of people information. The participant information is information (e.g., name) that identifies those who participated in the expense use (e.g., those who ate or drank). The number of people information is the number of people who participated in the expense use.

[0092] The receiving unit 12 receives various information and instructions, such as accounting document information, notification destination information, and access information.

[0093] The processing unit 13 performs various processes, such as processes performed by an accounting document acquisition unit 131, a correspondence detection unit 132, an inspection unit 133, and a notification destination acquisition unit .

[0094] The processing unit 13 may perform billing processing for use of the inspection function of the inspection device 1. The billing processing is processing for charging a user, an organization, or the accounting document management device 2. The billing processing includes calculating the billing amount, debit processing for billing, and notifying the billing amount. It is preferable that the processing unit 13 obtains different billing amounts depending on the frequency of inspection of accounting document information (timing information or period information), the items to be inspected, the period of accounting document information used for inspection (inspection period information), etc.

[0095] The ledger document acquisition unit 131 acquires ledger document information having one or more types of information of character string information and document images. It is preferable that the ledger document acquisition unit 131 acquires ledger document information having character string information and document images.

[0096] The ledger document acquisition unit 131 may acquire one or more pieces of ledger document information from the ledger document storage unit 113. The ledger document acquisition unit 131 may acquire one or more pieces of ledger document information received by the receiving unit 12. The ledger document acquisition unit 131 may acquire one or more pieces of ledger document information from one or more ledger document management devices 2. The ledger document acquisition unit 131 may acquire string information and document images constituting one piece of ledger document information from different ledger document management devices 2. In this case, the ledger document acquisition unit 131 actively acquires one or more pieces of expense information from the ledger document management device 2, for example. It is preferable that the ledger document acquisition unit 131 searches one or more ledger document management devices 2 and acquires one or more pieces of expense information. The ledger document acquisition unit 131 may acquire string information and document images constituting one piece of ledger document information at different times.

[0097] The character string information and document images included in a piece of ledger document information acquired by the ledger document acquisition unit 131 usually have a one-to-one correspondence, but may also have a one-to-n correspondence (n is a natural number greater than or equal to 2), an n-to-1 correspondence, or an n-to-m correspondence (m is a natural number greater than or equal to 2). In other words, the ledger document acquisition unit 131 may acquire one or more pieces of character string information and two or more document images that may be included in a piece of ledger document information. The ledger document acquisition unit 131 may acquire two or more pieces of character string information and one or more document images that may be included in a piece of ledger document information. The ledger document acquisition unit 131 may acquire two or more pieces of character string information and two or more document images that may be included in a piece of ledger document information.

[0098] It is preferable that the ledger document acquisition unit 131 acquires character string information associated with one user identifier and a document image associated with the one user identifier.

[0099] It is preferable that the ledger document acquisition unit 131 acquires at least one type of information from one or more ledger document management devices 2, such as character string information and document images.

[0100] The accounting document acquisition unit 131 may acquire character string information from one accounting document management device 2 and acquire document images from another accounting document management device 2.

[0101] It is preferable that the accounting document acquisition unit 131 acquires access information corresponding to one or more accounting document management devices 2 from the access information storage unit 111, and uses the access information to acquire one or more accounting document information from each accounting document management device 2.

[0102] The accounting document acquisition unit 131 acquires one or more pieces of accounting document information for a predetermined period using the acquired access information for each of one or more accounting document management devices 2. The predetermined period may be, for example, one day, one week, or one month.

[0103] The ledger document acquisition unit 131, for example, acquires one or more pieces of ledger document information for a predetermined period for each user from the ledger document management device 2. The ledger document acquisition unit 131, for example, acquires one or more user identifiers for each ledger document management device 2 from the storage unit 11. Next, for each acquired user identifier, the ledger document acquisition unit 131 acquires one or more pieces of ledger document information for a predetermined period from the ledger document management device 2 corresponding to the user identifier. The ledger document acquisition unit 131 acquires, for example, one or more pieces of ledger document information for a predetermined period paired with the user identifier from the ledger document management device 2.

[0104] The accounting document acquisition unit 131 acquires, for example, one or more pieces of accounting document information paired with the device identifier of the accounting document management device 2, or the organization identifier, or the user identifier.

[0105] The ledger document acquisition unit 131 acquires one or more pieces of ledger document information for different periods, for example, for each ledger document management device 2, for each organization that uses the ledger document management device 2, or for each user that uses the ledger document management device 2. Note that the period is usually a period relative to the current day. Ledger document information for a period is, for example, "today's ledger document information (e.g., expense information)," "ledger document information for the past week," "ledger document information for the past month," "ledger document information for the past year," etc. In other words, when acquiring ledger document information from the first ledger document management device 2, the ledger document acquisition unit 131 acquires one month's worth of ledger document information, and when acquiring ledger document information from the second ledger document management device 2, the ledger document acquisition unit 131 acquires one day's worth (today's worth). For example, when acquiring ledger document information for company A, the ledger document acquisition unit 131 acquires one month's worth of ledger document information, and when acquiring ledger document information for company B, the ledger document acquisition unit 131 acquires one day's worth (today's worth). For example, when acquiring the accounting document information of user A who is a section chief, the accounting document acquisition unit 131 acquires one day's worth of accounting document information (today's worth), and when acquiring the accounting document information of user B who is a department manager, the accounting document acquisition unit 131 acquires one month's worth of accounting document information.

[0106] The accounting document acquisition unit 131 acquires, for example, period information paired with a device identifier that identifies the accounting document management device 2 from the storage unit 11. Next, the accounting document acquisition unit 131 acquires, for example, accounting document information for the period indicated by the period information from the accounting document management device 2.

[0107] The accounting document acquisition unit 131 acquires, for example, period information paired with an organization identifier from the storage unit 11. Next, the accounting document acquisition unit 131 acquires, for example, one or more pieces of accounting document information for the period indicated by the period information, which is one or more pieces of accounting document information paired with the organization identifier, from the accounting document management device 2 corresponding to the organization identifier. Note that the accounting document management device 2 corresponding to the organization identifier is a accounting document management device 2 in which accounting document information applied for by one or more users belonging to the organization identified by the organization identifier is stored.

[0108] The accounting document acquisition unit 131 acquires, for example, period information paired with a user identifier from the storage unit 11. Next, the accounting document acquisition unit 131 acquires, for example, one or more pieces of accounting document information for the period indicated by the period information, which is one or more pieces of accounting document information paired with the user identifier, from the accounting document management device 2 corresponding to the user identifier. Note that the accounting document management device 2 corresponding to the user identifier is the accounting document management device 2 in which accounting document information applied for by a user identified by the user identifier is stored.

[0109] The accounting document acquisition unit 131 acquires accounting document information at different times, for example, for each accounting document management device 2, for each organization using the accounting document management device 2, or for each user using the accounting document management device 2.

[0110] For example, the ledger document acquisition unit 131 acquires, for each ledger document management device 2, timing information managed in pairs with a device identifier that identifies the ledger document management device 2 from the storage unit 11. Next, the ledger document acquisition unit 131 acquires one or more pieces of ledger document information from the ledger document management device 2, for example, at a time specified by the timing information.

[0111] For example, the ledger document acquisition unit 131 acquires, for each organization, timing information managed in pair with an organization identifier that identifies the organization from the storage unit 11. Next, for example, when the timing information is identified, the ledger document acquisition unit 131 acquires one or more pieces of ledger document information paired with the organization identifier from the ledger document management device 2 corresponding to the organization identifier. Note that the ledger document management device 2 corresponding to the organization identifier is the ledger document management device 2 identified by the device identifier paired with the organization identifier.

[0112] For example, the ledger document acquisition unit 131 acquires, for each user, timing information managed in pair with a user identifier that identifies the user from the storage unit 11. Next, for example, when the timing information is identified, the ledger document acquisition unit 131 acquires one or more pieces of ledger document information paired with the user identifier from the ledger document management device 2 corresponding to the user identifier. Note that the ledger document management device 2 corresponding to the user identifier is the ledger document management device 2 identified by the device identifier paired with the user identifier.

[0113] The correspondence detection unit 132 detects correspondence between character string information constituting one piece of ledger document information and a document image.

[0114] The correspondence between character string information constituting one ledger document information and a document image is preferably one-to-one, but may also be one-to-n, n-to-1, or n-to-m. That is, the correspondence detection unit 132 detects, for example, the correspondence between one character string information constituting one ledger document information and two or more document images. This processing is called one-to-many determination processing. The correspondence detection unit 132 detects the correspondence between two or more character string information and one document image. This processing is called many-to-one determination processing. The correspondence detection unit 132 detects, for example, the correspondence between two or more character string information constituting one ledger document information and two or more document images. This processing is called many-to-many determination processing.

[0115] The correspondence detection unit 132 refers to the identifier conversion information storage unit 112 and detects that even if the user identifier associated with the character string information and the user identifier associated with the document image are different, they are associated using the identifier conversion information.

[0116] The correspondence detection unit 132 determines that the string information and the document image may correspond when identifier conversion information that associates a first user identifier corresponding to the string information with a second user identifier corresponding to the document image is stored in the identifier conversion information storage unit 112.

[0117] The one-to-many determination process, many-to-one determination process, and many-to-many determination process performed by the correspondence detection unit 132 will be described in detail later.

[0118] The inspection unit 133 determines whether or not one or more pieces of book or document information acquired by the book or document acquisition unit 131 match the inspection conditions, and acquires the inspection results.

[0119] The inspection unit 133 uses, for example, character string information and document images acquired from different ledger document management devices 2 to determine whether or not the inspection conditions are met, and acquires the inspection results.

[0120] The inspection conditions are conditions for determining whether the accounting document information is appropriate. Preferably, the inspection conditions are conditions for determining whether the accounting document information complies with the rules set forth in the Electronic Bookkeeping Act. The inspection conditions are stored, for example, in the storage unit 11. The inspection conditions are, for example, image conditions, which will be described later, input period conditions, which will be described later, and consistency conditions, which will be described later. The image conditions are, for example, reading conditions, which will be described later, file format conditions, which will be described later, resolution conditions, which will be described later, paper size conditions, which will be described later, and gradation conditions, which will be described later. (1) Inspection of "image conditions"

[0121] The inspection unit 133 determines whether or not each of one or more document images contained in the book document information to be inspected satisfies the image conditions, and acquires the inspection result. (1-1) Checking the "reading conditions"

[0122] The inspection unit 133 acquires one or more character strings from a document image contained in the ledger document information to be inspected, determines whether or not one or more predetermined pieces of information are included in the one or more character strings, and acquires an inspection result. In other words, the reading condition is that one or more predetermined pieces of information can be read from the document image. For example, if the predetermined information is included, the inspection unit 133 acquires an inspection result of "legitimate," and if the predetermined information is not included, the inspection unit 133 acquires an inspection result of "illegitimate." The predetermined information is, for example, one or more pieces of information from the amount, date (transaction date), and customer. It is preferable that the predetermined information be the amount, date, and customer.

[0123] More specifically, the inspection unit 133 acquires one or more character strings from a document image, for example, by a known character recognition process. The inspection unit 133 classifies each of the acquired one or more character strings, for example, by using a known classification technique, to determine whether each character string represents an amount, a date, a business partner, or none of the above. Note that the method for acquiring one or more character strings from a document image and the method for classifying the character strings are not important.

[0124] The inspection unit 133, for example, inspects a document image contained in the ledger document information and determines whether the document image is an appropriate image. For example, the inspection unit 133 performs character recognition processing on the document image and acquires each element contained in the document image (e.g., "amount," "date," and "client") and a clarity score. The inspection unit 133 then determines whether the clarity is equal to or greater than a threshold. If the clarity is less than or equal to the threshold, the "reading condition" is not satisfied and the inspection result is "incorrect." If the clarity is equal to or greater than the threshold, the inspection result is "valid." In such cases, the inspection unit 133 uses, for example, a known module that performs character recognition processing on an image and acquires a score. (1-2) Checking "File format conditions"

[0125] The inspection unit 133 acquires the file format of the document image to be inspected, determines whether the file format satisfies the file format conditions, and acquires the inspection result. The file format conditions require that the file format of the document image be a predetermined format. The predetermined formats are, for example, PDF, JPEG, PNG, and GIF. The inspection unit 133, for example, acquires the file extension of the document image, determines the file format using the extension, determines whether the document image satisfies the file format conditions, and acquires the inspection result. (1-3) Checking "resolution conditions"

[0126] The inspection unit 133 acquires the resolution of the document image, determines whether the resolution satisfies the resolution condition, and acquires the inspection result. The resolution condition is a condition related to the resolution of the document image, and typically requires that the resolution be equal to or greater than a threshold value. The threshold value is, for example, "200 dpi," but is not limited thereto. (1-4) Inspection of "Paper size conditions"

[0127] The inspection unit 133 acquires the resolution and size of the document image to be inspected, acquires the paper size of the paper that is the source of the document image using the resolution and size, determines whether the paper size satisfies the paper size condition, and acquires the inspection result. The paper size condition is a condition related to the paper size, and typically requires that the paper size be equal to or smaller than a threshold value. The threshold value is, for example, A3 size or A4 size, but is not limited thereto. (1-5) Inspection of "Gradation Conditions"

[0128] The inspection unit 133 acquires the gradation of the document image to be inspected, determines whether the gradation satisfies the gradation condition, and acquires the inspection result. The gradation condition is a condition related to the gradation, and typically, the gradation is equal to or greater than a threshold value. Note that the gradation may be, for example, 256 colors, full color (RGB 256 colors), but is not limited thereto. (2) Checking the "input period conditions"

[0129] The inspection unit 133 acquires a date (transaction date) from the character string information or document image to be inspected. The inspection unit 133 also acquires the acquisition date on which the ledger document acquisition unit 131 acquired the character string information or document image. The inspection unit 133 then determines whether the difference between the relevant date and the acquisition date satisfies the input period condition, and acquires the inspection result. In other words, the input period condition is a condition related to the input period, and typically, the difference between the relevant date and the acquisition date is within or less than a threshold value. The threshold value is, for example, two months and seven business days. The date of the ledger document is the date (for example, a receipt). The acquisition date is the date on which the inspection device 1 or the ledger document management device 2 received the ledger document (the date on which it was applied). (3) Checking the "consistency conditions"

[0130] The inspection unit 133 acquires one or more character strings from the document image acquired by the ledger document acquisition unit 131, determines whether or not a consistency condition, which is a condition regarding the consistency between the one or more character strings and the character string information acquired by the ledger document acquisition unit 131, is satisfied, and acquires the inspection result.

[0131] The consistency condition is, for example, that the amount, date, and customer acquired from the document image match the amount, date, and customer included in the character string information.

[0132] The inspection unit 133, for example, determines whether a piece of character string information in the correspondence detected by the correspondence detection unit 132 and two or more document images satisfy a consistency condition and acquires an inspection result. The inspection unit 133, for example, determines whether the amount included in the piece of character string information in the correspondence detected by the correspondence detection unit 132 matches the total amount acquired from each of two or more document images. The inspection unit 133, for example, determines whether the date included in the piece of character string information in the correspondence detected by the correspondence detection unit 132 matches all of the dates acquired from each of two or more document images. The inspection unit 133, for example, determines whether the business partner included in the piece of character string information in the correspondence detected by the correspondence detection unit 132 matches all of the business partners acquired from each of two or more document images.

[0133] The inspection unit 133, for example, determines whether two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 and a document image satisfy a consistency condition and acquires an inspection result. The inspection unit 133, for example, determines whether the sum of the amounts contained in the two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 matches the amount acquired from a document image. The inspection unit 133, for example, determines whether all dates contained in the two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 match the dates acquired from a document image. The inspection unit 133, for example, determines whether all business partners contained in the two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 match the business partners acquired from a document image.

[0134] The inspection unit 133, for example, determines whether two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 and two or more document images satisfy a consistency condition and acquires an inspection result. The inspection unit 133, for example, determines whether the sum of the amounts contained in the two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 matches the sum of the amounts acquired from the two or more document images. The inspection unit 133, for example, determines whether all dates contained in the two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 match all dates acquired from the two or more document images. The inspection unit 133, for example, determines whether all business partners contained in the two or more pieces of character string information in the correspondence detected by the correspondence detection unit 132 match all business partners acquired from the two or more document images. (5) Checking for "overlapping conditions"

[0135] The inspection unit 133 acquires inspection period information (for example, "1 year") from the storage unit 11. Next, the accounting document acquisition unit 131 acquires all accounting document information for the period indicated by the inspection period information, which is paired with the user identifier corresponding to the accounting document information to be inspected. Next, the inspection unit 133 determines whether or not there is accounting document information identical to the accounting document information to be inspected among all the acquired accounting document information. Here, if there is identical accounting document information, the inspection unit 133 acquires the judgment result "fraudulent". (6) Examination of "budgetary conditions"

[0136] When the accounting document information to be inspected by the inspection unit 133 is, for example, expense information, the following inspection of "budget conditions" may be performed.

[0137] That is, the inspection unit 133 acquires, for example, an inappropriate condition (for example, "cumulative expenses<=500,000 yen") and inspection period information (for example, this month) from the storage unit 11. Next, the ledger document acquisition unit 131 acquires expense information for the period indicated by the inspection period information (for example, this month). Next, the inspection unit 133 determines whether the accumulated expenses, which are the total amount of expense information (including the expense information to be inspected) for the period corresponding to the acquired inspection period information, satisfy the inappropriate condition. If the inappropriate condition is satisfied, the inspection unit 133 acquires the inspection result "inappropriate", and if not, acquires the inspection result "legitimate".

[0138] It is preferable that the inspection unit 133 obtains, for example, an invalid condition paired with a device identifier, an organization identifier, or a user identifier corresponding to the expense information to be inspected from the storage unit 11, and inspects the budget condition using the invalid condition. In other words, the budget condition may differ for each ledger document management device 2, organization, or user.

[0139] The inspection unit 133 preferably acquires, for example, the fraud conditions and inspection period information paired with the device identifier, organization identifier, or user identifier corresponding to the expense information to be inspected from the storage unit 11, and inspects the budget conditions using the fraud conditions and inspection period information. In other words, the budget conditions and inspection period may differ for each ledger document management device 2, organization, or user.

[0140] The notification destination acquisition unit 134 acquires one or more pieces of notification destination information corresponding to the accounting document information acquired by the accounting document acquisition unit 131. The accounting document information acquired by the accounting document acquisition unit 131 is accounting document information to be inspected.

[0141] The notification destination acquisition unit 134 acquires, for example, one or more pieces of notification destination information stored in the storage unit 11. For example, the notification destination acquisition unit 134 acquires, from the storage unit 11, one or more pieces of notification destination information corresponding to a user identifier corresponding to the acquired accounting document information. The acquired accounting document information is the accounting document information to be inspected. For example, the notification destination acquisition unit 134 acquires, from the storage unit 11, one or more pieces of notification destination information paired with an organization identifier corresponding to the acquired accounting document information.

[0142] The notification destination acquisition unit 134 acquires, from the storage unit 11, for example, one or more pieces of notification destination information paired with the device identifier of the ledger document management device 2 from which the ledger document information has been acquired.

[0143] The notification destination acquisition unit 134 acquires, for example, one or more pieces of notification destination information corresponding to the accounting document information acquired by the accounting document acquisition unit 131 from the accounting document management device 2 in which the accounting document information is stored. It is preferable that the notification destination acquisition unit 134 acquires one or more pieces of notification destination information associated with the accounting document information. For example, the notification destination acquisition unit 134 receives one or more pieces of notification destination information from the accounting document management device 2 every time accounting document information is acquired.

[0144] The notification destination acquisition unit 134 preferably acquires different notification destination information depending on, for example, the inspection result. The notification destination acquisition unit 134 acquires, for example, one or more pieces of notification destination information that match a condition using the inspection result from the storage unit 11. The notification destination acquisition unit 134 acquires different notification destination information, for example, when the inspection result is "fraudulent" and when the inspection result is "valid." Acquiring different notification destination information also includes not acquiring notification destination information when the inspection result is "normal." For example, when the inspection result is "fraudulent," the notification destination acquisition unit 134 acquires notification destination information such as the supervisor, accounting officer, or legal officer of the user who applied for the accounting document information.

[0145] The output unit 14 outputs various types of information, such as test results. Here, "output" typically refers to transmission to an external device such as the terminal device 3, but may also refer to displaying on a display, projecting using a projector, printing on a printer, outputting sound, storing on a recording medium, or transferring processing results to another processing device or another program.

[0146] The notification unit 141 notifies the inspection result acquired by the inspection unit 133 to the notification destinations specified by one or more pieces of notification destination information corresponding to the accounting document information on which the inspection result is based.

[0147] It is preferable that the notification unit 141 notifies the test results to the notification destinations specified by the one or more pieces of notification destination information acquired by the notification destination acquisition unit 134 .

[0148] The notification unit 141 may transmit the inspection results acquired by the inspection unit 133 to the ledger document management device 2. Then, the ledger document management device 2 may receive and store the inspection results. Alternatively, the ledger document management device 2 may receive the inspection results and transmit the inspection results or information acquired from the inspection results to one or more notification destinations.

[0149] It is preferable that the notification unit 141 notifies different notification destinations of the inspection result depending on the inspection result. That is, for example, it is preferable that the notification unit 141 notifies different notification destinations of the inspection result depending on whether the inspection result is valid or invalid. Furthermore, the notification unit 141 may notify the notification destinations specified by one or more pieces of notification destination information only when the inspection result is "illegal." For example, when the inspection result is "illegal," the notification unit 141 may notify all notification destinations specified by two or more pieces of notification destination information, and when the inspection result is "valid," the notification unit 141 may notify only the user who applied for the accounting document information. Note that different notification destinations depending on the inspection result may include cases where notification is made and cases where notification is not made.

[0150] Various types of information are stored in the management storage unit 21 that constitutes the accounting document management device 2. The various types of information are, for example, one or more pieces of accounting document information. The accounting document information is usually associated with a user identifier. The accounting document information is usually associated with an organization identifier. The various types of information are, for example, a device identifier. The management storage unit 21 may also be called an accounting document storage unit.

[0151] The management reception unit 22 receives various instructions and information, such as an instruction to send accounting document information and an instruction to search for accounting document information.

[0152] The management processing unit 23 performs various processes. For example, the various processes are processes for storing accounting document information in the management storage unit 21. The management processing unit 23 acquires one or more pieces of accounting document information corresponding to an instruction to send accounting document information from the management storage unit 21. The management processing unit 23 acquires one or more pieces of accounting document information corresponding to an instruction to search for accounting document information from the management storage unit 21.

[0153] The management transmission unit 24 transmits various types of information, such as test results received from the test device 1.

[0154] The management receiving unit 25 receives various types of information, such as accounting document information and inspection results.

[0155] The management output unit 26 outputs various types of information, such as test results. Here, "output" typically means transmission to an external device, but it may also be display on a display, projection using a projector, printing on a printer, sound output, storage on a recording medium, or delivery of processing results to another processing device or another program.

[0156] Various types of information are stored in the terminal storage unit 31 constituting the terminal device 3. The various types of information include, for example, expense information and test results.

[0157] The terminal reception unit 32 receives various information or instructions. The various information or instructions may be, for example, accounting document information. The means for inputting the various information or instructions may be any means, such as a numeric keypad, keyboard, mouse, or menu screen.

[0158] The device processing unit 33 performs various types of processing. For example, the various types of processing are processing for converting instructions and information received by the terminal receiving unit 32 into instructions and information with a data structure to be transmitted. For example, the various types of processing are processing for converting information received by the terminal receiving unit 35 into information with a data structure to be output.

[0159] The terminal transmitting unit 34 transmits various instructions and information, such as accounting document information.

[0160] The terminal receiving unit 35 receives various types of information, such as test results.

[0161] The terminal output unit 36 ​​outputs various types of information, such as accounting document information and inspection results.

[0162] The storage unit 11, the access information storage unit 111, the identifier conversion information storage unit 112, the accounting document storage unit 113, the management storage unit 21, and the terminal storage unit 31 are preferably non-volatile recording media, but can also be realized as volatile recording media.

[0163] There is no restriction on the process by which information is stored in the storage unit 11 etc. 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.

[0164] The receiving unit 12, the management receiving unit 25, and the terminal receiving unit 35 are usually realized by wireless or wired communication means.

[0165] The processing unit 13, accounting document acquisition unit 131, correspondence detection unit 132, inspection unit 133, notification destination acquisition unit 134, management processing unit 23, and terminal processing unit 33 can usually be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type does not matter.

[0166] The accounting document acquisition unit 131 may be realized by a wireless or wired communication means.

[0167] The output unit 14, the notification unit 141, the management transmission unit 24, and the terminal transmission unit 34 are typically realized by wireless or wired communication means.

[0168] The management reception unit 22 is preferably realized by a wireless or wired communication means, but may also be realized by a device driver for an input means such as a touch panel or keyboard, or control software for a menu screen.

[0169] The management output unit 26 is realized by, for example, a wireless or wired communication means, but may also be realized by driver software for an output device, or a combination of driver software for an output device and the output device.

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

[0171] The terminal output unit 36 ​​may or may not include an output device such as a display, a speaker, etc. The terminal output unit 36 ​​may be realized by driver software for an output device, or by a combination of driver software for an output device and the output device, etc.

[0172] Next, a description will be given of an example of the operation of the information system A. First, a description will be given of an example of the operation of the inspection device 1 with reference to the flowchart of FIG.

[0173] (Step S401) The ledger document acquisition unit 131 determines whether it is time to acquire ledger document information from any of the ledger document management devices 2. If it is time to acquire ledger document information, the process proceeds to step S402, and if it is not time to acquire ledger document information, the process proceeds to step S412.

[0174] For example, the accounting document acquisition unit 131 uses timing information to determine whether it is time to acquire accounting document information.

[0175] (Step S402) The accounting document obtaining unit 131 assigns 1 to the counter i.

[0176] (Step S403) The ledger document acquisition unit 131 determines whether or not the i-th ledger document management device 2 corresponding to the timing of acquiring the ledger document information exists. If the i-th ledger document management device 2 exists, the process proceeds to step S404, and if not, the process returns to step S401. Note that here, the ledger document acquisition unit 131 may also determine whether or not the i-th device identifier or the i-th access information exists in the storage unit 11.

[0177] (Step S404) The ledger document obtaining unit 131 obtains the access information corresponding to the i-th device identifier from the access information storage unit 111.

[0178] (Step S405) The accounting document obtaining unit 131 assigns 1 to the counter j.

[0179] (Step S406) The ledger document acquisition unit 131 determines whether or not the jth information acquisition unit exists, which is an information acquisition unit corresponding to the i-th ledger document management device 2. If the jth information acquisition unit exists, the process proceeds to step S407; if not, the process proceeds to step S413.

[0180] The information acquisition unit is the unit for acquiring accounting document information from the accounting document management device 2 at one time. The information acquisition unit may be a unit with different inspection items or inspection conditions. The information acquisition unit may be, for example, per organization identifier or per user identifier. The information acquisition unit may also be one. When there is one information acquisition unit, the accounting document acquisition unit 131 acquires accounting document information for each accounting document management device 2. In other words, one information acquisition unit may be one accounting document management device 2.

[0181] (Step S407) The accounting document acquisition unit 131 acquires, from the storage unit 11, timing information corresponding to the j-th information acquisition unit in the i-th accounting document management device 2.

[0182] (Step S408) The ledger document acquisition unit 131 acquires the current time from a clock (not shown). Next, the ledger document acquisition unit 131 uses the timing information acquired in step S407 to determine whether the current time is the timing to acquire ledger document information. If it is the timing to acquire ledger document information, the process proceeds to step S409; if it is not the timing to acquire ledger document information, the process proceeds to step S412.

[0183] (Step S409) The accounting document obtaining unit 131 obtains, from the storage unit 11, period information corresponding to the j-th information obtaining unit in the i-th accounting document management device 2.

[0184] (Step S410) The accounting document acquisition unit 131 acquires accounting document information corresponding to the jth information acquisition unit, which is one or more accounting document information for the period specified by the period information in step S409, from the i-th accounting document management device 2 using the access information acquired in step S404.

[0185] (Step S411) The inspection unit 133 performs an inspection using one or more pieces of book document information acquired in step S410 and notifies the inspection result. An example of such processing such as inspection will be described with reference to the flowcharts of FIGS. 5 and 6.

[0186] (Step S412) The ledger document obtaining unit 131 increments the counter j by 1. The process returns to step S406.

[0187] (Step S413) The ledger document obtaining unit 131 increments the counter i by 1. The process returns to step S403.

[0188] (Step S414) The receiving unit 12 determines whether or not one or more pieces of accounting document information have been received from the terminal device 3. If accounting document information has been received, the process proceeds to step S415, and if accounting document information has not been received, the process returns to step S401. Note that the one or more pieces of accounting document information received are associated with a user identifier.

[0189] (Step S415) The inspection unit 133 performs an inspection using one or more pieces of book document information received in step S414 and notifies the inspection result. An example of such processing such as inspection will be described with reference to the flowcharts of FIGS. 5 and 6.

[0190] (Step S416) The processing unit 13 judges whether or not the result of the inspection in step S415 was "valid." If it is "valid," the process proceeds to step S417, and if it is "invalid," the process returns to step S401.

[0191] (Step S417) The processing unit 13 associates the one or more pieces of accounting document information received in step S414 with the user identifier and stores them in the accounting document storage unit 113. Note that it is preferable that the processing unit 13 obtains today's date from a clock (not shown) and stores the one or more pieces of accounting document information in association with the date.

[0192] In the flowchart of FIG. 4, the process ends when the power is turned off or an interrupt occurs to end the process.

[0193] Next, a first example of the process of inspection etc. in step S410 will be described with reference to the flowchart of FIG.

[0194] (Step S501) The inspection unit 133 assigns 1 to a counter i.

[0195] (Step S502) The inspection unit 133 determines whether the i-th accounting document information exists among the one or more pieces of accounting document information acquired or received. If the i-th accounting document information exists, the process proceeds to step S503; if not, the process returns to the upper processing.

[0196] (Step S503) The inspection unit 133 assigns 1 to a counter j.

[0197] (Step S504) The inspection unit 133 determines whether the jth inspection item, which is an inspection item to be performed on the i-th accounting document information, exists. If the jth inspection item exists, the process proceeds to step S505; if not, the process proceeds to step S509. It is preferable that one or more inspection item identifiers are stored in the storage unit 11 in association with the information acquisition unit.

[0198] The inspection item to be performed on the i-th accounting document information is, for example, the inspection item corresponding to the j-th information acquisition unit in step S406.

[0199] The inspection items are, for example, the above-mentioned inspection of the "image conditions," the inspection of the "input period conditions," the inspection of the "consistency conditions," the inspection of the "duplication conditions," and the inspection of the "budget conditions." The inspection items may also differ depending on the target information acquisition unit.

[0200] (Step S505) The inspection unit 133 performs an inspection corresponding to the jth inspection item on the i-th accounting document information, obtains a judgment result, and temporarily stores it in a buffer (not shown). The judgment result includes, for example, information indicating "fraud" or information indicating "valid." If the judgment result includes information indicating "fraud," it is preferable that the judgment result includes information specifying the nature of the fraud.

[0201] (Step S506) The inspection unit 133 judges whether the judgment result of the inspection in step S505 is "illegal" or "valid." If it is "illegal," the process proceeds to step S507, and if it is "valid," the process proceeds to step S508.

[0202] (Step S507) The inspection unit 133 stores the determination result acquired in step S505 in a buffer (not shown) in association with the i-th book document information.

[0203] (Step S508) The inspection unit 133 increments the counter j by 1. The process returns to step S504.

[0204] (Step S509) The inspection unit 133 uses the judgment results accumulated in a buffer (not shown) or the judgment results in step S505 to form an inspection result corresponding to the i-th accounting document information.

[0205] (Step S510) The notification destination acquisition unit 134 acquires one or more pieces of notification destination information corresponding to the target information acquisition unit (the j-th information acquisition unit in step S406) from the storage unit 11. An example of such notification destination information acquisition processing will be described with reference to the flowchart in FIG.

[0206] (Step S511) The notification unit 141 notifies the notification destinations specified by the one or more pieces of notification destination information acquired in step S510 of the test results configured in step S509, using the notification destination information.

[0207] (Step S512) The inspection unit 133 increments the counter i by 1. The process returns to step S502.

[0208] Next, a second example of the process of inspection etc. in step S410 will be described using the flowchart of Fig. 6. In the flowchart of Fig. 6, the description of the same steps as those in the flowchart of Fig. 6 will be omitted.

[0209] (Step S601) The correspondence detection unit 132 performs correspondence determination processing. An example of the correspondence determination processing will be described using the flowchart in Fig. 8. Note that the correspondence determination processing is a determination as to whether or not the book document information to be inspected includes character string information and a document image, and the character string information and the document image correspond to each other.

[0210] (Step S602) The correspondence detection unit 132 determines whether the result of the correspondence determination process in step S601 is "correspondence" (determination result is "OK") or "no correspondence" (determination result is "NG"). If "correspondence" is found, the process proceeds to step S605, and if "no correspondence" is found, the process proceeds to step S603.

[0211] (Step S603) The correspondence detection unit 132 performs a correspondence information determination process. An example of the correspondence information determination process will be described with reference to the flowchart in Fig. 9. The correspondence information determination process is a process of determining one or more pieces of character string information and one or more document images that correspond to each other.

[0212] (Step S604) The correspondence detection unit 132 determines whether the corresponding character string information and the document image have been determined (corresponded) as a result of the correspondence information determination process in step S603. If determined, the process proceeds to step S605, and if not, the process proceeds to step S606.

[0213] (Step S605) The inspection unit 133 performs a consistency condition determination process. An example of the consistency condition determination process will be described with reference to the flowchart in Fig. 11. The consistency condition determination process is an inspection of the "consistency condition".

[0214] (Step S606) The inspection unit 133 performs image condition determination processing. An example of the image condition determination processing will be described with reference to the flowchart in Fig. 12. Note that the image condition determination processing is an inspection of "image conditions."

[0215] (Step S607) The inspection unit 133 performs input period condition determination processing. An example of the input period condition determination processing will be described with reference to the flowchart in FIG. 13. The process proceeds to step S509. The input period condition determination processing is an inspection of the "input period condition".

[0216] Next, an example of the notification destination information acquisition process in step S510 will be described with reference to the flowchart in FIG.

[0217] (Step S701) The notification destination acquisition unit 134 acquires a user identifier corresponding to the checked accounting document information and the accounting document information of interest.

[0218] (Step S702) The notification destination acquisition unit 134 judges whether the inspection result is “illegal” or “valid.” If it is “illegal,” the process proceeds to step S703, and if it is “valid,” the process proceeds to step S704.

[0219] (Step S703) The notification destination acquisition unit 134 acquires one or more pieces of notification destination information that correspond to the user identifier acquired in step S701 and that corresponds to the inspection result "fraudulent." Note that the notification destination acquisition unit 134 acquires the one or more pieces of notification destination information, for example, from the storage unit 11. Also, the notification destination acquisition unit 134 acquires, for example, the one or more pieces of notification destination information that have been received.

[0220] (Step S704) The notification destination acquisition unit 134 acquires one or more pieces of notification destination information that correspond to the user identifier acquired in step S701 and that corresponds to the inspection result "legitimate." Note that the notification destination acquisition unit 134 acquires one or more pieces of notification destination information, for example, from the storage unit 11. Also, the notification destination acquisition unit 134 acquires, for example, one or more pieces of received notification destination information.

[0221] (Step S705) The notification destination acquisition unit 134 determines whether the accounting document information of interest is data acquired from the accounting document management device 2. If the data is acquired from the accounting document management device 2, the process proceeds to step S706, and if the data is not acquired from the accounting document management device 2, the process returns to the upper processing.

[0222] (Step S706) The notification destination acquisition unit 134 acquires the device identifier for identifying the ledger document management device 2 in which the targeted ledger document information is stored.

[0223] (Step S707) The notification destination acquisition unit 134 acquires notification destination information paired with the device identifier from the storage unit 11. The process returns to the upper level process.

[0224] In the flowchart of FIG. 7, the notification destination acquisition unit 134 may acquire one or more pieces of notification destination information received from the ledger / document management device 2 in pairs with the inspected ledger / document information.

[0225] Next, an example of the response determination process in step S601 will be described with reference to the flowchart in FIG.

[0226] (Step S801) The correspondence detection unit 132 determines whether or not the book document information to be inspected contains character string information and a document image. If character string information and a document image are included, the process proceeds to step S802; if character string information and a document image are not included, the process proceeds to step S806.

[0227] (Step S802) The correspondence detection unit 132 acquires an amount from each of one or more document images in the ledger document information to be inspected. Note that, if there are two or more document images in the ledger document information, the correspondence detection unit 132 acquires an amount from each document image and calculates an amount that is the sum of the amounts. Note that the process of acquiring an amount from a document image has been described above.

[0228] (Step S803) The correspondence detection unit 132 acquires an amount from one or more pieces of character string information in the accounting document information to be inspected. Note that, if there are two or more pieces of character string information in the accounting document information, the correspondence detection unit 132 acquires the amount of each piece of character string information and calculates the amount that is the sum of the amounts.

[0229] (Step S804) The correspondence detection unit 132 determines whether the amount acquired in step S802 matches the amount acquired in step S803. If they match, the process proceeds to step S805, and if they do not match, the process proceeds to step S806.

[0230] (Step S805) The correspondence detection unit 132 assigns "OK" to the variable "determination result" and returns to the upper level processing.

[0231] (Step S806) The correspondence detection unit 132 assigns "NG" to the variable "determination result" and returns to the upper level process.

[0232] Next, an example of the corresponding information determination process in step S603 will be described with reference to the flowchart in FIG.

[0233] (Step S901) The correspondence detection unit 132 acquires a user identifier corresponding to the book document information to be inspected.

[0234] (Step S902) The correspondence detection unit 132 acquires the date and the like contained in the accounting document information to be inspected. The date and the like are, for example, the date and the business partner. Note that the accounting document information here usually includes one or more pieces of character string information and one or more document images.

[0235] (Step S903) The correspondence detection unit 132 determines whether the amount obtained from the document image contained in the ledger document information is greater or the amount obtained from the character string information contained in the ledger document information is greater. If the amount obtained from the document image is greater, the process proceeds to step S904; if the amount obtained from the character string information is greater, the process proceeds to step S912.

[0236] (Step S904) The correspondence detection unit 132 acquires one or more pieces of character string information corresponding to the date, etc. acquired in step S902 from the accounting document storage unit 113. Note that the character string information corresponding to the date, etc. is usually character string information including the date, etc. that matches the date, etc. acquired in step S902. It is also preferable that the accounting document storage unit 113 stores accounting document information received from the terminal device 3, as well as accounting document information acquired from the accounting document management device 2.

[0237] (Step S905) The correspondence detecting unit 132 assigns 1 to a counter i.

[0238] (Step S906) The correspondence detection unit 132 determines whether or not an i-th set of one or more pieces of character string information exists among the one or more pieces of character string information acquired in step S904. If the i-th set of piece of character string information exists, the process proceeds to step S907; if not, the process proceeds to step S911. The i-th set may be one piece of character string information or two or more pieces of character string information. It is also preferable that the i-th set acquired by the correspondence detection unit 132 starts with one piece of character string information and gradually increases the number of pieces of character string information. This is because using fewer pieces of character string information increases the possibility of a match in step S908, and this process ends earlier.

[0239] (Step S907) The correspondence detection unit 132 calculates the sum of the amount in the character string information contained in the accounting document information to be inspected and the amount in each piece of character string information constituting the i-th set of character string information. Note that here, if the accounting document information to be inspected does not have character string information, the correspondence detection unit 132 obtains the sum of the amount in each piece of character string information constituting the i-th set of character string information.

[0240] (Step S908) The correspondence detection unit 132 determines whether the amount acquired in step S907 matches the amount acquired from the document image included in the accounting document information to be inspected. If they match, the process proceeds to step S909, and if they do not match, the process proceeds to step S910.

[0241] (Step S909) The correspondence detection unit 132 associates the i-th set of one or more pieces of character string information with a document image contained in the ledger document information to be inspected. This step associates one document image with two or more pieces of character string information. This step also allows one document image and two or more pieces of character string information that make up one piece of ledger document information to be acquired.

[0242] (Step S910) The correspondence detecting unit 132 increments the counter i by 1. The process returns to step S906.

[0243] (Step S911) The correspondence detection unit 132 performs a many-to-many determination process. An example of the many-to-many determination process will be described with reference to the flowchart in Fig. 10. The many-to-many determination process is a process for determining correspondence between two or more pieces of character string information included in one piece of ledger document information and two or more document images.

[0244] (Step S912) The correspondence detection unit 132 acquires one or more document images corresponding to the date, etc. acquired in step S902 from the ledger document storage unit 113. Note that the document image corresponding to the date, etc. is usually a document image in which the date, etc. acquired from the document image matches the date, etc. acquired in step S902.

[0245] It is preferable that each document image in the ledger document storage unit 113 is associated with a date, etc., obtained from the document image. The correspondence detection unit 132 may also obtain a character string, such as a date, from each document image in the ledger document storage unit 113.

[0246] (Step S913) The correspondence detecting unit 132 assigns 1 to a counter j.

[0247] (Step S914) The correspondence detection unit 132 determines whether or not a jth set of one or more document images exists among the one or more document images acquired in step S904. If the jth set of document images exists, the process proceeds to step S915; if not, the process proceeds to step S911. The jth set may be one document image or two or more document images. It is also preferable that the jth set acquired by the correspondence detection unit 132 be adopted from one document image and the number of document images is gradually increased. This is because using fewer document images increases the possibility of a match in step S916, and this process ends earlier.

[0248] (Step S915) The correspondence detection unit 132 calculates the sum of the amount obtained from the document image included in the accounting document information to be inspected and the amount obtained from each document image constituting the j-th document image set. Note that here, if the accounting document information to be inspected does not have a document image, the correspondence detection unit 132 obtains the sum of the amounts obtained from each document image constituting the j-th document image set.

[0249] (Step S916) The correspondence detection unit 132 determines whether the amount acquired in step S915 matches the amount included in the character string information of the accounting document information to be inspected. If they match, the process proceeds to step S917, and if they do not match, the process proceeds to step S918.

[0250] (Step S9179) The correspondence detection unit 132 associates the i-th set of one or more document images with character string information contained in the ledger document information to be inspected. This step associates one piece of character string information with two or more document images. This step also allows one piece of character string information and two or more document images that make up one piece of ledger document information to be acquired.

[0251] (Step S918) The correspondence detecting unit 132 increments the counter j by 1. The process returns to step S914.

[0252] In the flowchart of FIG. 9, steps S904 to S910 are an example of many-to-one determination processing between character string information and document images, and steps S912 to S918 are an example of one-to-many determination processing.

[0253] Next, an example of the many-to-many determination process in step S911 will be described with reference to the flowchart in FIG.

[0254] (Step S1001) The correspondence detecting unit 132 assigns 1 to a counter i.

[0255] (Step S1002) The correspondence detection unit 132 acquires one or more pieces of character string information corresponding to the date, etc. acquired in step S902 from the accounting document storage unit 113. Next, the correspondence detection unit 132 determines whether or not an i-th set of one or more pieces of character string information exists among the one or more pieces of character string information. If the i-th set of character string information exists, the process proceeds to step S1003; if not, the process proceeds to step S1011. Note that the i-th set may be one piece of character string information, or two or more pieces of character string information. Furthermore, it is preferable that the i-th set acquired by the correspondence detection unit 132 starts with one piece of character string information and gradually increases the number of pieces of character string information. This is because using fewer pieces of character string information increases the possibility of a match in step S1007, and this process terminates earlier.

[0256] (Step S1003) The correspondence detection unit 132 calculates the sum of the amount in the character string information contained in the accounting document information to be inspected and the amount in each piece of character string information constituting the i-th set of character string information. Note that here, if the accounting document information to be inspected does not have character string information, the correspondence detection unit 132 obtains the sum of the amount in each piece of character string information constituting the i-th set of character string information.

[0257] (Step S1004) The correspondence detecting unit 132 assigns 1 to a counter j.

[0258] (Step S1005) The correspondence detection unit 132 acquires one or more document images corresponding to the date, etc. acquired in step S902 from the ledger document storage unit 113. Next, the correspondence detection unit 132 determines whether or not a jth set of one or more document images exists among the one or more document images. If a jth set of document images exists, the process proceeds to step S1006; if not, the process proceeds to step S1010. Note that the jth set may be one document image or two or more document images. Furthermore, it is preferable that the jth set acquired by the correspondence detection unit 132 be adopted from one document image, and the number of document images is gradually increased. This is because using fewer document images increases the possibility of a match in step S916, and this process terminates earlier.

[0259] (Step S1006) The correspondence detection unit 132 calculates the sum of the amount obtained from the document image included in the accounting document information to be inspected and the amount obtained from each document image constituting the j-th document image set. Note that here, if the accounting document information to be inspected does not have a document image, the correspondence detection unit 132 obtains the sum of the amounts obtained from each document image constituting the j-th document image set.

[0260] (Step S1007) The correspondence detection unit 132 determines whether the total amount acquired in step S1003 matches the total amount acquired in step S1006. If they match, the process proceeds to step S1008, and if they do not match, the process proceeds to step S1009.

[0261] (Step S1008) The correspondence detection unit 132 associates the i-th set of one or more pieces of character string information with the ledger document information to be inspected. Also, the correspondence detection unit 132 associates the j-th set of one or more document images with the ledger document information to be inspected. The process returns to the upper level process. Note that associating a set of character string information or a set of document images with ledger document information may also be achieved by including a set of character string information or a set of document images in the ledger document information.

[0262] In addition, this step associates two or more pieces of character string information with two or more document images. Also, this step can obtain two or more pieces of character string information and two or more document images that constitute one piece of ledger document information.

[0263] (Step S1009) The correspondence detecting unit 132 increments the counter j by 1. The process returns to step S1005.

[0264] (Step S1010) The correspondence detecting unit 132 increments the counter i by 1. The process returns to step S1002.

[0265] (Step S1011) The correspondence detection unit 132 assigns "NG" to the variable "correspondence result." The process returns to the upper level process.

[0266] Next, an example of the consistency condition determination process in step S605 will be described with reference to the flowchart in FIG.

[0267] (Step S1101) The inspection unit 133 acquires the total amount of each of one or more pieces of character string information contained in the accounting document information to be inspected. Note that, if the accounting document information has only one piece of character string information, the inspection unit 133 acquires the amount of the character string information.

[0268] (Step S1102) The inspection unit 133 assigns 1 to the counter i.

[0269] (Step S1103) The inspection unit 133 determines whether or not the i-th document image included in the book document information to be inspected exists. If the i-th document image exists, the process proceeds to step S1104; if not, the process proceeds to step S1107.

[0270] (Step S1104) The inspection unit 133 acquires one or more character strings from the ith document image included in the ledger document information to be inspected.

[0271] (Step S1105) The checking unit 133 obtains the amount from one or more character strings.

[0272] (Step S1106) The inspection unit 133 increments the counter i by 1. The process returns to step S1103.

[0273] (Step S1107) The inspection unit 133 acquires the total amount acquired in step S1105. Note that, if the accounting document information to be inspected has one document image, the inspection unit 133 may acquire one amount from the document image.

[0274] (Step S1108) The verification unit 133 determines whether the total amount acquired in step S1101 matches the total amount acquired in step S1107. If they match, the process proceeds to step S1110, and if they do not match, the process proceeds to step S1109.

[0275] (Step S1109) The inspection unit 133 adds "Invalid (Consistency: Amount)" to the variable "Inspection Result". Note that "Invalid (Consistency: Amount)" is information indicating that the amount in the character string information and the document image does not match. "Invalid (Consistency: Amount)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0276] (Step S1110) The inspection unit 133 acquires the date (transaction date) included in each of one or more pieces of character string information included in the accounting document information to be inspected.

[0277] (Step S1111) The inspection unit 133 acquires dates (transaction dates) from one or more document images included in the book document information to be inspected.

[0278] (Step S1112) The inspection unit 133 determines whether or not all of the one or more dates acquired in step S1110 match the one or more dates acquired in step S1111. If all match, the process proceeds to step S1114, and if there are any dates that do not match, the process proceeds to step S1113.

[0279] (Step S1113) The inspection unit 133 adds "Invalid (Integrity: Date)" to the variable "Inspection Result". Note that "Invalid (Integrity: Date)" is information indicating that the date in the character string information does not match the date in the document image. "Invalid (Integrity: Date)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0280] (Step S1114) The inspection unit 133 acquires business partners included in one or more pieces of character string information included in the accounting document information to be inspected.

[0281] (Step S1115) The inspection unit 133 acquires business partners from one or more document images included in the accounting document information to be inspected.

[0282] (Step S1116) The inspection unit 133 determines whether or not all of the one or more business partners acquired in step S1113 match the one or more business partners acquired in step S1115. If all match, the process returns to the upper level process, and if there are any business partners that do not match, the process proceeds to step S1117.

[0283] (Step S1117) The inspection unit 133 adds "Invalid (Inconsistency: Customer)" to the variable "Inspection Result". The process returns to the upper level process. Note that "Invalid (Inconsistency: Customer)" is information indicating that the customer in the character string information does not match the customer in the document image. "Invalid (Inconsistency: Customer)" is, for example, an error code, but it could also be a character string or the like, and its data structure is not important.

[0284] In the flowchart of Figure 11, the consistency of three elements, namely, amount, date, and business partner, is checked, but the consistency of other elements contained in the accounting document information may also be checked, or the consistency of only one or two elements among amount, date, and business partner may also be checked.

[0285] Next, an example of the image condition determination process in step S606 will be described with reference to the flowchart in FIG.

[0286] (Step S1201) The inspection unit 133 assigns 1 to a counter i.

[0287] (Step S1202) The inspection unit 133 determines whether or not the i-th document image included in the book document information to be inspected exists. If the i-th document image exists, the process proceeds to step S1203, and if the i-th document image does not exist, the process returns to the upper process.

[0288] (Step S1203) The inspection unit 133 acquires one or more character strings from the i-th document image.

[0289] (Step S1204) The inspection unit 133 acquires the element name (e.g., amount, date, business partner) of each of the one or more character strings acquired in step S1203. Note that this processing is a processing for classifying character strings, etc., and can be realized by publicly known technology, so detailed explanation will be omitted.

[0290] (Step S1205) The inspection unit 133 assigns 1 to the counter j.

[0291] (Step S1206) The inspection unit 133 determines whether or not the jth inspection-compatible element exists. If the jth inspection-compatible element exists, the process proceeds to step S1207; if not, the process proceeds to step S1209. It is assumed here that the elements to be inspected for reading are predetermined. The elements to be inspected are, for example, the amount, date, and business partner. The inspection of reading is an inspection of whether or not it is possible to read the element from the document image.

[0292] (Step S1207) Inspection unit 133 determines whether or not the j-th element was acquired in steps S1203 and S1204. If the j-th element was acquired, the process proceeds to step S1208, and if the j-th element was not acquired, the process proceeds to step S1209.

[0293] (Step S1208) The inspection unit 133 adds "Invalid (reading condition: j-th element)" to the variable "inspection result." Note that "Invalid (reading condition: j-th element)" is information indicating that the j-th element could not be read from the document image. "Invalid (reading condition: j-th element)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0294] (Step S1209) The inspection unit 133 increments the counter j by 1. The process returns to step S1206.

[0295] (Step S1210) The inspection unit 133 acquires the file format (for example, PDF, JPEG) of the i-th document image.

[0296] (Step S1211) The inspection unit 133 determines whether the file format acquired in step S1210 matches the file format conditions. If the file format matches the file format conditions, the process proceeds to step S1213, and if the file format does not match the file format conditions, the process proceeds to step S1212.

[0297] (Step S1212) The inspection unit 133 adds "Invalid (file format condition)" to the variable "Inspection result." Note that "Invalid (file format condition)" is information indicating that the file format of the document image is invalid. "Invalid (file format condition)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0298] (Step S1213) The inspection unit 133 acquires the resolution of the i-th document image.

[0299] (Step S1214) The inspection unit 133 determines whether the resolution acquired in step S1213 matches the resolution condition. If the resolution condition is met, the process proceeds to step S1216, and if the resolution condition is not met, the process proceeds to step S1215.

[0300] (Step S1215) The inspection unit 133 adds "invalid (resolution condition)" to the variable "inspection result." Note that "invalid (resolution condition)" is information indicating that the resolution of the document image is invalid. "invalid (resolution)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0301] (Step S1216) The inspection unit 133 acquires the paper size of the i-th document image.

[0302] (Step S1217) The inspection unit 133 determines whether the paper size acquired in step S1216 matches the paper size conditions. If the paper size conditions are met, the process proceeds to step S1219, and if the paper size conditions are not met, the process proceeds to step S1218.

[0303] (Step S1218) The inspection unit 133 adds "Invalid (paper size condition)" to the variable "Inspection result." Note that "Invalid (paper size condition)" is information indicating that the paper size of the document image is invalid. "Invalid (paper size)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0304] (Step S1219) The inspection unit 133 acquires the gradation of the i-th document image.

[0305] (Step S1220) Inspection unit 133 determines whether the gradation acquired in step S1216 matches the gradation condition. If the gradation condition is met, the process proceeds to step S1222, and if the gradation condition is not met, the process proceeds to step S1221.

[0306] (Step S1221) The inspection unit 133 adds "Invalid (Gradation Condition)" to the variable "Inspection Result". Note that "Invalid (Gradation Condition)" is information indicating that the gradation of the document image is invalid. "Invalid (Gradation)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0307] (Step S1222) The inspection unit 133 increments the counter i by 1. The process returns to step S1202.

[0308] Next, an example of the input period condition determination process in step S607 will be described with reference to the flowchart of FIG.

[0309] (Step S1301) The inspection unit 133 assigns 1 to a counter i.

[0310] (Step S1302) The inspection unit 133 determines whether the i-th character string information or document image in the book document information to be inspected exists. If the i-th character string information or document image exists, the process proceeds to step S1303; if not, the process returns to the upper process.

[0311] (Step S1303) The inspection unit 133 acquires the receipt date corresponding to the ith character string information or document image contained in the ledger document information to be inspected. The corresponding receipt date is, for example, the date on which the character string information or document image was transmitted from the terminal device 3 to the inspection device 1 or the ledger document management device 2.

[0312] (Step S1304) The inspection unit 133 acquires the transaction date of the ith character string information or document image contained in the ledger document information to be inspected.

[0313] (Step S1305) The checking unit 133 obtains the difference between the acceptance date obtained in step S1303 and the transaction date obtained in step S1304.

[0314] (Step S1306) The inspection unit 133 determines whether or not the difference acquired in step S1305 satisfies the input period condition. If the input period condition is satisfied, the process proceeds to step S1308, and if the input period condition is not satisfied, the process proceeds to step S1307.

[0315] (Step S1307) The inspection unit 133 adds "Invalid (input period condition)" to the variable "inspection result." Note that "Invalid (input period condition)" is information indicating that the input period condition is not met. "Invalid (input period condition)" is, for example, an error code, but it may also be a character string or the like, and its data structure does not matter.

[0316] (Step S1308) The inspection unit 133 increments the counter i by 1. The process returns to step S1302.

[0317] Next, an example of the operation of the accounting document management device 2 will be described. The accounting document management device 2 receives one or more pieces of accounting document information from one or more terminal devices 3, each associated with a user identifier. Next, the management processing unit 23 stores the one or more pieces of accounting document information in the management storage unit 21, associated with the user identifier. The management receiving unit 25 receives inspection results associated with the accounting document information from the inspection device 1, and the management processing unit 23 stores the inspection results in association with the accounting document information. The management processing unit 23 acquires one or more pieces of accounting document information from the management storage unit 21 based on a search instruction from the inspection device 1. Next, the management transmitting unit 24 transmits the one or more pieces of accounting document information to the inspection device 1. The management processing unit 23 may acquire one or more pieces of notification information, user identifiers, and organization identifiers, paired with each of the one or more pieces of accounting document information. The management transmission unit 24 may then transmit one or more pieces of notification destination information, a user identifier, and an organization identifier together with the one or more pieces of accounting document information to the inspection device 1. The management transmission unit 24 may also transmit the inspection results received from the inspection device 1 to the notification destination indicated in the notification destination information associated with the accounting document information on which the inspection results are based.

[0318] Next, we will explain an example of the operation of the terminal device 3. The terminal reception unit 32 of the terminal device 3 receives one or more pieces of accounting document information. Next, the terminal transmission unit 34 transmits the one or more pieces of accounting document information to the accounting document management device 2 or the inspection device 1. In addition, the terminal reception unit 35 receives the inspection results from the inspection device 1, and the terminal output unit 36 ​​outputs the inspection results.

[0319] A specific example of the operation of the information system A in this embodiment will be described below.

[0320] Currently, the access information management table shown in FIG. 14 is stored in the access information storage unit 111 of the inspection device 1. The access information management table manages one or more records each having an "ID," "device identifier," and "access information." The "ID" is information that identifies a record. The "device identifier" here is the device name of the ledger document management device 2, but it can also be an IP address, etc. The "access information" here is the identifier of an API or the name of an execution module for acquiring expense information, but it can be any information for acquiring expense information from the ledger document management device 2.

[0321] The storage unit 11 of the inspection device 1 also stores an information acquisition unit management table shown in FIG. 15. The information acquisition unit management table stores one or more pieces of information about the information acquisition unit. The information acquisition unit information includes various pieces of information corresponding to the information acquisition unit. Here, the information acquisition unit information includes an "equipment identifier," an "information acquisition unit identifier," "timing information," "period information," and an "inspection item." The "information acquisition unit identifier" includes an "organization identifier" and a "user identifier." The "inspection item" includes an "inspection item identifier," "illegal conditions," and "inspection period information." If the "information acquisition unit identifier" is "-" (NULL), it indicates that the information acquisition unit is the ledger document management device 2. The "information acquisition unit identifier" may be NULL, may include only an "organization identifier," or may include both an "organization identifier" and a "user identifier." The "inspection item identifier" is information that identifies the inspection item. The inspection item identifier "image condition" indicates that the image condition is to be inspected. The inspection item identifier "consistency condition" indicates that the consistency condition is to be inspected. The inspection item identifier "budget condition" indicates that the budget condition is to be inspected. The inspection item identifier "input period condition" indicates that the input period condition is to be inspected. The inspection item identifier "duplicate condition" indicates that duplicate conditions are to be inspected. "Invalid condition" is a condition for determining that something is invalid. "Inspection period information" is information that specifies the period of expense information used for inspection, although it is not the subject of inspection. Note that "invalid condition" is information that takes into account that the conditions for invalidity differ depending on the information acquisition unit. "Inspection period information" is information that takes into account that the period of expense information used during inspection differs depending on the information acquisition unit. Note that "inspection period information" can also be considered to be included in "invalid conditions".

[0322] Furthermore, the storage unit 11 of the inspection device 1 stores a notification destination management table shown in FIG. 16. The notification destination management table is a table for managing notification destinations. The notification destination management table has "ID," "notification destination conditions," and "notification destination information." The "notification destination information" has "legitimate" and "illegal." The "notification destination conditions" are conditions for determining the notification destination. The "notification destination information" may differ depending on the inspection result, or may remain the same regardless of the inspection result.

[0323] In the above situation, the following five specific examples will be described. Specific Example 1 is a case where the information acquisition unit is for each ledger document management device 2, and the inspection result is sent to different notification destinations depending on whether the inspection result is "invalid" or "valid." Specific Example 2 is a case where the inspection device 1 acquires notification destination information corresponding to the ledger document information from the ledger document management device 2. Specific Example 2 is also a case where other ledger document information for a predetermined period is used during the inspection process. Specific Example 3 is a case where the information acquisition unit is for each user. Specific Example 4 is a case where the "search period information" differs for each information acquisition unit. Specific Example 5 is a case where the inspection device 1 inspects the ledger document information received, and inspects all inspection items. Here, the ledger document information is, for example, expense information. Here, the document image is, for example, a receipt image.

[0324] (Example 1) Assume that today is "August 31, 2020." Assume that the expense information in FIG. 17 is transmitted from the terminal device 3 of a user identified by "user identification = U101" to the ledger document management device 2 identified by the device identifier "device A," and that the expense information is stored in the ledger document management device 2. Assume also that on "August 31, 2020," one or more pieces of expense information other than that in FIG. 17 are transmitted by another user to the ledger document management device 2 identified by "device A," and that the expense information is stored in the ledger document management device 2.

[0325] Then, the current time becomes "August 31, 2020, 24:00 (0:00)", and the processing unit 13 of the inspection device 1 determines that it is time for the inspection device 1 to operate.

[0326] Next, the ledger document acquisition unit 131 of the inspection device 1 acquires the record with "ID=1" in the information acquisition unit management table (FIG. 15). Then, the ledger document acquisition unit 131 determines that the current time matches the timing information "everyday at 0:00" of the record.

[0327] Next, the ledger document acquisition unit 131 acquires the access information "get_record(expense DB, $information acquisition unit identifier, $period information)" that is paired with the device identifier "device A" of the record from the access information management table (FIG. 14). Note that this access information is expense information that is paired with "$information acquisition unit identifier" from the expense DB of "device A", and is an API of a function that acquires expense information for the period specified by "$period information".

[0328] Then, the ledger document acquisition unit 131 assigns "-1" (information indicating that the information acquisition unit is device-by-device) corresponding to the "-" in the record with "ID=1" to the parameter (variable) "$information acquisition unit identifier" of the API. The ledger document acquisition unit 131 also assigns the period information "1 day" of the record with "ID=1" to the parameter (variable) "$period information" of the API. The ledger document acquisition unit 131 then executes "get_record(expense DB, -1, 1 day)." The ledger document acquisition unit 131 then acquires all expense information accumulated as of August 31, 2020, from the ledger document management device 2 "device A." The ledger document acquisition unit 131 also acquires a user identifier and an organization identifier paired with each of the acquired one or more pieces of expense information. The acquired user identifier is the identifier of the user who input the expense information. The acquired organization identifier is the identifier of the organization to which the user who input the expense information belongs.

[0329] Next, the inspection unit 133 inspects each of the two or more pieces of acquired expense information as follows: That is, the inspection unit 133 acquires the inspection item identifiers "image condition" and "consistency condition" of the record with "ID=1" in the information acquisition unit management table (FIG. 15).

[0330] Then, the inspection unit 133 first inspects the "image conditions" for the expense information in FIG. 17. That is, first, the inspection unit 133 inspects, for example, the reading conditions. The inspection unit 133 performs character recognition processing on the document image included in the expense information in FIG. 17, and obtains each element (for example, "Date: August 27, 2020," "Amount: 940 yen," "Destination: Tsubame Taxi Co., Ltd.") and a clarity score of "80." The inspection unit 133 then determines that the required elements ("Date," "Amount," and "Customer") have been acquired and that the clarity score of "80" satisfies the conditions, resulting in a judgment result of "legitimate (reading conditions)." Note that, here, the condition for the clarity score is "score >= 70." Note that, here, it is not essential for the inspection unit 133 to use the clarity score.

[0331] The inspection unit 133 also inspects the file format condition. That is, it is assumed that the inspection unit 133 acquires the file format (JPEG) of the document image included in the expense information in Fig. 17. Next, the inspection unit 133 determines that the file format (JPEG) meets the file format condition "the file format is one of PDF, JPEG, PNG, and GIF," and obtains a judgment result of "legitimate (file format condition)."

[0332] The inspection unit 133 also inspects the resolution condition. That is, it is assumed that the inspection unit 133 acquires the resolution "400 dpi" of the document image included in the expense information in Fig. 17. Next, the inspection unit 133 determines that the resolution "400 dpi" matches the resolution condition "resolution >= 200 dpi", and obtains the judgment result "valid (resolution condition)".

[0333] The inspection unit 133 also inspects the paper size condition. That is, the inspection unit 133 acquires the size (for example, X dots x Y dots) of the document image contained in the expense information in FIG. 17. The inspection unit 133 also acquires the paper size "a x b" using the size (X dots x Y dots) and the resolution "400 dpi." Next, the inspection unit 133 determines that the paper size "a x b" meets the paper size condition "paper size is A3 or smaller," and obtains the judgment result "valid (paper size condition)."

[0334] The inspection unit 133 also inspects the gradation conditions. That is, it is assumed that the inspection unit 133 acquires the gradation "full color 512 colors" of the document image contained in the expense information of Fig. 17. Next, the inspection unit 133 determines that the gradation "full color 512 colors" matches the resolution condition "full color 256 colors or more", and obtains the judgment result "valid (gradation condition)".

[0335] Next, the inspection unit 133 inspects the "consistency condition" for the expense information in Fig. 17. Then, since "<amount> 980" in the character string information does not match "amount: 940 yen" acquired from the document image, the inspection unit 133 obtains the judgment result of the inspection of the "consistency condition" as "invalid (consistency condition)."

[0336] Next, the inspection unit 133 acquires information including "There is an irregularity in the 'Consistency condition'." and the expense information of FIG. 17 as the inspection result for the expense information of FIG.

[0337] Next, the notification destination acquisition unit 134 acquires the notification destination information "U101@z.com," "kreiri@z.com," and "U101bucho@z.com" paired with the user identifier "U101" and "unauthorized" from the notification destination management table (FIG. 16).

[0338] Next, the notification unit 141 notifies the configured test results to the notification destinations specified by the acquired three pieces of notification destination information.

[0339] Next, the three terminal devices 3 that have received the test results output the test results. An example of the test result output is shown in FIG.

[0340] The inspection device 1 also inspects the second and subsequent received expense information in the same manner and notifies the inspection results.

[0341] (Example 2) Assume that on "August 31, 2020," an employee of company α sent the expense information in FIG. 17 from a terminal device 3 to a ledger document management device 2 identified by a device identifier "device B." Then, the ledger document management device 2 received and stored the expense information. Also, assume that on "August 31, 2020," one or more pieces of expense information other than that in FIG. 17 were sent by another user to the ledger document management device 2 identified by "device B," and stored in the ledger document management device 2.

[0342] Then, after processing the record with "ID=1" in the information acquisition unit management table (FIG. 15) in specific example 1, the inspection device 1 performs the following processing on the record with "ID=2" in the information acquisition unit management table (FIG. 15). That is, the ledger document acquisition unit 131 acquires the record with "ID=2" in the information acquisition unit management table (FIG. 15). Then, the ledger document acquisition unit 131 determines that the timing information of that record matches "24:00 on the last day of each month."

[0343] Next, the ledger document acquisition unit 131 acquires the name of the execution module, "RetrieveRecord.exe," as access information paired with the device identifier "Device B" of the record, from the access information management table (FIG. 14). Then, the ledger document acquisition unit 131 provides the execution module with the information acquisition unit identifier "Company α" and the period information "1 month," and executes the execution module. Then, the ledger document acquisition unit 131 acquires one or more pieces of expense information paired with the organization identifier "Company α," which includes date information including "August 2020," from the ledger document management device 2, "Device B." Note that by executing "RetrieveRecord.exe," the ledger document acquisition unit 131 also acquires user notification information (here, each user's email address) associated with each of the one or more pieces of expense information. It is also assumed that the ledger document acquisition unit 131 acquires the email address of the accounting department of "Company α."

[0344] Next, the inspection unit 133 inspects each of the one or more pieces of acquired expense information as follows: That is, the inspection unit 133 acquires the inspection item identifiers "consistency condition" and "budget condition" of the record with "ID=2".

[0345] Then, the checking unit 133 first checks the "consistency condition" for the expense information in FIG. 17, and obtains the determination result of the "consistency condition" check as "incorrect (consistency condition)".

[0346] The inspection unit 133 also inspects the expense information in FIG. 17 for the "budget condition" as follows. That is, the inspection unit 133 acquires the fraudulent condition "cumulative expenses <= 500,000 yen" and the inspection period information "6 months" that are paired with the inspection item identifier "budget condition" from the table in FIG. 15. Next, the inspection unit 133 instructs the ledger document acquisition unit 131 to acquire, from "device B," all expense information for the period indicated by the inspection period information "6 months" that is paired with "company α." Then, the ledger document acquisition unit 131 acquires the expense information from "device B." Next, the inspection unit 133 acquires the total amount of all the acquired expense information (including the expense information in FIG. 17) and determines whether or not "cumulative expenses <= 500,000 yen" is satisfied. Here, it is assumed that the inspection unit 133 determines that "cumulative expenses <= 500,000 yen" is satisfied.

[0347] Next, the inspection unit 133 acquires information including "There is an irregularity in the 'Consistency condition'." and the expense information of FIG. 17 as the inspection result for the expense information of FIG.

[0348] Next, the notification destination acquisition unit 134 acquires the email address of the user and the email address of the accounting department of "company α" that were acquired together with the expense information in FIG.

[0349] Next, the notification unit 141 notifies the configured test results to the notification destinations specified by the two pieces of acquired notification destination information.

[0350] Next, the two terminal devices 3 that received the inspection results receive and output the inspection results. An example of the inspection result output is shown in Figure 18. The two terminal devices 3 are the terminal device 3 of the applicant who entered the expense information in Figure 17 and the terminal device 3 of the accounting department of "Company α."

[0351] The inspection device 1 also inspects other received expense information in the same manner and notifies the inspection results.

[0352] (Example 3) Assume that on August 31, 2020, an employee of the "Y Department" of Company Beta, identified by "user identifier = U001", sent the expense information shown in Figure 17 from a terminal device 3 to an accounting document management device 2, identified by a device identifier "Device B".

[0353] Then, after processing the record with "ID=2" in the information acquisition unit management table (FIG. 15) in specific example 2, the inspection device 1 performs the following processing using the record with "ID=3" in the information acquisition unit management table (FIG. 15). That is, the ledger document acquisition unit 131 acquires the record with "ID=3" in the information acquisition unit management table (FIG. 15). Then, the ledger document acquisition unit 131 determines that the timing information of that record matches "everyday at 0:00".

[0354] Next, the ledger document acquisition unit 131 acquires the name of the execution module, "RetrieveRecord.exe," as access information paired with the device identifier "Device B" of the record, from the access information management table (FIG. 14). Then, the ledger document acquisition unit 131 provides the execution module with the information acquisition unit identifier "Company β.X Department" and the period information "1 day," and executes the execution module. Then, the ledger document acquisition unit 131 acquires, from the ledger document management device 2 "Device B," one or more pieces of expense information paired with the organization identifier "Company α.X Department" and the user identifier "U001," and including the date information of "August 31, 2020." Note that by executing "RetrieveRecord.exe," the ledger document acquisition unit 131 also acquires the notification destination information of the user associated with each of the one or more pieces of expense information (here, the email address of the user identified by the user identifier "U001").

[0355] Next, the checking unit 133 checks each of the one or more pieces of acquired expense information as follows: That is, the checking unit 133 obtains the check item "consistency condition" of the record with "ID=3".

[0356] Then, the checking unit 133 first checks the "consistency condition" for the expense information in FIG. 17, and obtains the determination result of the "consistency condition" check: "Incorrect (consistency condition)."

[0357] Next, the inspection unit 133 acquires information including "There is an irregularity in the 'Consistency condition'." and the expense information of FIG. 17 as the inspection result for the expense information of FIG.

[0358] Next, the notification destination acquisition unit 134 acquires the notification destination information "$user email address" "X@β.co.jp" corresponding to "Fraud" of "ID=2" from the table in Fig. 16. Then, the notification destination acquisition unit 134 replaces the variable "$user email address" with the email address of the user acquired together with the expense information.

[0359] Next, the notification unit 141 notifies the configured test results to the notification destinations specified by the two pieces of notification destination information thus acquired. The two pieces of notification destination information are the email address of the user who sent the expense information in FIG. 17 and the notification destination information.

[0360] Next, the two terminal devices 3 that have received the test results receive and output the test results. An example of the test results output is shown in FIG.

[0361] The inspection device 1 also inspects other received expense information in the same manner and notifies the inspection results.

[0362] (Example 4) Assume that on "August 31, 2020," an employee of "Department Y" of company β, identified by "user identifier = U002," sent the expense information shown in Fig. 17 from a terminal device 3 to an accounting document management device 2 identified by a device identifier "device B." Then, assume that the accounting document management device 2 received and stored the expense information.

[0363] Then, after processing the record with "ID=3" in the information acquisition unit management table (FIG. 15) in specific example 3, the inspection device 1 performs the following processing using the record with "ID=4" in the information acquisition unit management table (FIG. 15). That is, the ledger document acquisition unit 131 acquires the record with "ID=4" in the information acquisition unit management table (FIG. 15). Then, the ledger document acquisition unit 131 determines that the timing information of that record matches "every day at 0:00".

[0364] Next, the ledger document acquisition unit 131 acquires the name of the execution module, "RetrieveRecord.exe," as access information paired with the device identifier "Device B" of the record, from the access information management table (FIG. 14). Then, the ledger document acquisition unit 131 provides the execution module with the information acquisition unit identifier "Company β.Y Department" and the period information "1 day," and executes the execution module. Then, the ledger document acquisition unit 131 acquires, from the ledger document management device 2 "Device B," one or more pieces of expense information paired with the organization identifier "Company α.Y Department" and the user identifier "U002," and including the date information of "August 31, 2020." Note that by executing "RetrieveRecord.exe," the ledger document acquisition unit 131 also acquires the notification destination information of the user associated with each of the one or more pieces of expense information (here, the email address of the user identified by the user identifier "U002").

[0365] Next, the inspection unit 133 inspects each of the one or more pieces of acquired expense information as follows: That is, the inspection unit 133 acquires the inspection items "consistency condition" and "overlapping condition" of the record with "ID=3".

[0366] Then, the checking unit 133 first checks the "consistency condition" for the expense information in FIG. 17, and obtains the determination result of the "consistency condition" check as "incorrect (consistency condition)".

[0367] The inspection unit 133 also inspects the expense information in FIG. 17 for the "overlapping condition" as follows. That is, the inspection unit 133 acquires the inspection period information "1 month" that is paired with the inspection item identifier "overlapping condition." Next, the inspection unit 133 instructs the accounting document acquisition unit 131 to acquire, from "device B," all expense information for the period indicated by the inspection period information "1 month" that is paired with "Company β.Y Department" and user identifier "U002." Then, the accounting document acquisition unit 131 acquires the expense information from "device B." Next, the inspection unit 133 determines whether or not the same expense information as the expense information to be inspected (FIG. 17) exists among all the acquired expense information. Here, it is assumed that the inspection unit 133 determines that the same expense information exists. Then, the inspection unit 133 acquires the judgment result "incorrect (overlapping condition)" for the inspection of the "overlapping condition."

[0368] Next, the inspection unit 133 acquires information including "There is an irregularity in the 'Consistency condition'. There is an irregularity in the 'Overlapping condition'." and the expense information in FIG. 17 as the inspection result for the expense information in FIG.

[0369] Next, the notification destination acquisition unit 134 acquires, from FIG. 16, the notification destination information "U002@β.com" and "keiri@β.com" that are paired with the organization identifier "Company α.Y Department" and the user identifier "U002".

[0370] Next, the notification unit 141 notifies the configured test results to the notification destinations specified by the two pieces of acquired notification destination information.

[0371] Next, the two terminal devices 3 that have received the test results receive and output the test results.

[0372] (Example 5) It is assumed that on August 31, 2020, a user registered in the inspection device 1 transmitted the expense information shown in FIG. 17 to the inspection device 1 from the terminal device 3.

[0373] Next, the receiving unit 12 of the inspection device 1 receives the expense information of Fig. 17 from the terminal device 3. Next, the inspection unit 133 performs each inspection using the above-mentioned image conditions (including "reading conditions," "file format conditions," "resolution conditions," "paper size conditions," and "gradation conditions"), "input period conditions," "consistency conditions," "overlap conditions," and "budget conditions."

[0374] In addition, when inspecting the "input period condition," it is assumed that the inspection unit 133 obtains the receipt date "August 31, 2020" from a clock (not shown). The inspection unit 133 also obtains the transaction date "August 27, 2020" contained in the expense information of FIG. 17. Next, the inspection unit 133 obtains the input period condition "within two months + seven business days" from the storage unit 11. Next, the inspection unit 133 calculates the difference "four days" between the receipt date "August 31, 2020" and the transaction date "August 27, 2020." Next, the inspection unit 133 determines that the difference "four days" satisfies the input period condition "within two months + seven business days." Then, the inspection unit 133 obtains the determination result "legitimate (input period condition)."

[0375] In addition, the inspection unit 133 also obtains the judgment results "valid (reading conditions)", "valid (file format conditions)", "valid (resolution conditions)", "valid (paper size conditions)", "valid (gradation conditions)", "invalid (consistency conditions)", "valid (duplication conditions)", and "valid (budget conditions)".

[0376] Next, the inspection unit 133 acquires information including "There is an irregularity in the 'Consistency condition'." and the expense information of FIG. 17 as the inspection result for the expense information of FIG.

[0377] Next, the notification destination acquisition unit 134 acquires from the storage unit 11 the notification destination information "Address A (e.g., the boss's email address)" and "Address B (e.g., the accounting department's email address)" that are paired with the user identifier that is paired with the expense information in Figure 17.

[0378] Next, the notification unit 141 notifies the terminal device 3 that has transmitted the expense information in Fig. 17 of the inspection result. The notification unit 141 also notifies "Address A" and "Address B" of the inspection result.

[0379] Next, the terminal device 3 that sent the expense information receives and outputs the inspection results. The superior and the accounting department receive and check the inspection results by email.

[0380] As described above, according to this embodiment, it is possible to inspect book documents in accordance with the Electronic Book Preservation Act, etc. Furthermore, according to this embodiment, it is possible to inspect document images in accordance with the Electronic Book Preservation Act, etc. Furthermore, according to this embodiment, it is possible to inspect consistency in accordance with the Electronic Book Preservation Act, etc.

[0381] Furthermore, according to this embodiment, accounting document inspections that comply with the Electronic Bookkeeping Act and the like can be performed appropriately using accounting document information acquired from one or more accounting document management devices 2. As a result, the inspection device 1 functions as a platform that provides accounting document inspection functions, particularly for accounting document management devices 2 that do not have inspection functions. In other words, an environment can be provided for adding accounting document information inspection functions without adding functions to one or more accounting document management devices.

[0382] Moreover, according to this embodiment, inspection can be performed using character string information and document images acquired from different ledger document management devices 2. Furthermore, according to this embodiment, inspection of one ledger document information can be performed using character string information or document images from the inspection device 1 and character string information or document images acquired from the ledger document management device 2.

[0383] Furthermore, according to this embodiment, the inspection results of the book and document information acquired from the external book and document management device 2 can be notified to an appropriate notification destination.

[0384] Furthermore, according to this embodiment, the test results can be notified to different notification destinations depending on the test results.

[0385] Furthermore, according to this embodiment, inspection can be performed using two or more pieces of book and document information for a predetermined period (predetermined period) for each book and document management device 2, for each organization, or for each user.

[0386] Furthermore, according to this embodiment, the inspection results can be notified at an appropriate timing for each accounting document management device 2, each organization, or each user.

[0387] Furthermore, according to this embodiment, it is possible to inspect the book and document information for an appropriate period for each book and document management device 2, each organization, or each user.

[0388] Furthermore, according to this embodiment, billing can be performed according to the frequency of inspection of accounting document information (timing information or period information), the items to be inspected, the period of accounting document information used for inspection (inspection period information), etc.

[0389] The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to the other embodiments in this specification. The software that realizes the inspection device 1 in this embodiment is the following program. In other words, this program causes a computer to function as a ledger document acquisition unit that acquires ledger document information having one or more types of information selected from character string information and document images, an inspection unit that determines whether the ledger document information meets inspection conditions and acquires inspection results, and an output unit that outputs the inspection results.

[0390] (Embodiment 2) In this embodiment, the inspection device operates passively, which is different from the inspection device 1 in embodiment 1, which operates actively. In other words, in this embodiment, the inspection device inspects expense information passively received from the ledger document management device 2 and notifies the inspection result.

[0391] In this embodiment, the inspection device may also receive notification destination information in combination with the accounting document information.

[0392] The conceptual diagram of information system B in this embodiment is the same as that in Fig. 1 except for the different reference numerals. Information system B has inspection device 4 instead of inspection device 1. Information system B includes inspection device 4, one or more ledger document management devices 2, and one or more terminal devices 3.

[0393] The inspection device 4 is usually a so-called server, such as a cloud server, an ASP server, etc. The type of the inspection device 4 is not important.

[0394] It is preferable that the management transmitting unit 24 in the accounting document management device 2 transmits accounting document information to the inspection device 4 every time the management receiving unit 25 receives the accounting document information. It is also preferable that the management transmitting unit 24 transmits one or more pieces of notification destination information to the inspection device 4 in pairs with the accounting document information. Note that each of the one or more pieces of notification destination information is information that specifies the destination to which the inspection results of the accounting document information should be notified.

[0395] 19 is a block diagram of an information system B according to this embodiment. The inspection device 4 constituting the information system B includes a storage unit 11, a receiving unit 42, a processing unit 43, and a transmitting unit 14. The receiving unit 42 includes an accounting document acquisition unit 421. The processing unit 43 includes an inspection unit 133 and a notification destination acquisition unit 134.

[0396] The receiving unit 42 included in the inspection device 4 receives various types of information from the accounting document management device 2. The various types of information include, for example, accounting document information and notification destination information.

[0397] The ledger document acquisition unit 421 receives one or more pieces of ledger document information from one or more ledger document management devices 2. For example, the ledger document acquisition unit 421 receives two or more pieces of ledger document information for a predetermined period for each user from the ledger document management device 2. The ledger document acquisition unit 421 may also receive one or more pieces of notification destination information associated with the ledger document information from the ledger document management device 2.

[0398] The processing unit 43 performs various types of processing, such as processing performed by the inspection unit 133 and the notification destination acquisition unit 134.

[0399] The notification unit 141 notifies the inspection result to the notification destination specified by one or more pieces of notification destination information corresponding to the accounting document information on which the inspection result is based. Note that the one or more pieces of notification destination information are usually information received by the accounting document acquisition unit 421.

[0400] The receiving unit 42 and the accounting document acquiring unit 421 are usually realized by wireless or wired communication means.

[0401] The processing unit 43 can usually be realized by a processor, memory, etc. The processing procedure of the processing unit 43 is usually realized by software, and the software is recorded on a recording medium such as a ROM. However, it may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and its type does not matter.

[0402] Next, an example of the operation of the inspection device 4 constituting the information system B will be described using the flowchart of Fig. 20. In the flowchart of Fig. 20, the description of the same steps as in the flowchart of Fig. 5 will be omitted.

[0403] (Step S2001) The ledger document acquisition unit 421 determines whether or not ledger document information, etc. has been received from any of the ledger document management devices 2. If ledger document information, etc. has been received, the process proceeds to step S503, and if not, the process returns to step S2001. Note that ledger document information, etc. is, for example, ledger document information and one or more notification destination information, but it may also be just ledger document information.

[0404] (Step S2002) The notification destination acquisition unit 134 acquires one or more pieces of notification destination information. Proceed to step S511. Note that the notification destination acquisition unit 134 acquires, for example, one or more pieces of notification destination information received in step S2001. The notification destination acquisition unit 134 acquires, for example, one or more pieces of notification destination information corresponding to the ledger document management device 2 that has transmitted the ledger document information.

[0405] In step S511 in the flowchart of FIG. 20, it is preferable to transmit the inspection results to the ledger document management device 2 that has transmitted the ledger document information and the like.

[0406] In the flowchart of FIG. 20, the process ends when the power is turned off or an interrupt occurs to end the process.

[0407] As described above, according to this embodiment, by simply adding a function for transmitting accounting document information and the like in one or more accounting document management devices 2, an environment for adding an inspection function for accounting document information can be provided.

[0408] The software that realizes the inspection device 4 in this embodiment is the following program. In other words, this program causes a computer to function as a ledger document acquisition unit that receives ledger document information from one or more ledger document management devices having a ledger document information storage unit in which one or more pieces of ledger document information are stored, an inspection unit that inspects the ledger document information acquired by the ledger document acquisition unit and acquires the inspection results, and a notification unit that notifies the inspection results to notification destinations specified by one or more notification destination information that corresponds to the ledger document information on which the inspection results are based.

[0409] 21 shows the appearance of a computer that executes the programs described herein to realize the inspection device 1 and the like according to the various embodiments described above. The above-described embodiments can be realized by computer hardware and a computer program executed thereon. FIG. 21 is an overview of this computer system 300, and FIG. 22 is a block diagram of the system 300.

[0410] In FIG. 21, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

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

[0412] A program that causes the computer system 300 to execute the functions of the inspection device 1 and the like of the above-described embodiment may be stored on a 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 when executed. The program may also be loaded directly from the CD-ROM 3101 or the network.

[0413] The program does not necessarily include an operating system (OS) or a third-party program that causes the computer 301 to execute the functions of the inspection device 1 of the above-described embodiment. The program only needs to include instructions that call appropriate functions (modules) in a controlled manner to achieve the desired results. How the computer system 300 operates is well known, and a detailed description thereof will be omitted.

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

[0415] The computer that executes the program may be a single computer or a plurality of computers, that is, it may perform centralized processing or distributed processing.

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

[0417] Furthermore, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

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

[0419] As described above, the inspection device according to the present invention has the effect of being able to inspect book documents that comply with the Electronic Bookkeeping Act and the like, and is useful as an inspection device, etc. [Explanation of symbols]

[0420] 1, 4 Inspection equipment 2. Ledger document management device 3 Terminal Devices 11 Storage area 12, 42 Receiver 13, 43 Processing section 14 Output section 14 Transmitter 21 Management Storage Unit 22 Management Reception Department 23 Management Department 24 Management and Transmission Unit 25 Management Receiving Unit 26 Management output section 31 Terminal storage section 32 Terminal Reception 33 Terminal processing section 34 Terminal transmitter 35 Terminal receiving unit 36 Terminal Output Unit 111 Access information storage unit 112 Identifier conversion information storage unit 113 Ledger Document Storage Section 131, 421 Book and Document Acquisition Department 132 Corresponding detection unit 133 Inspection Department 134 Notification destination acquisition unit 141 Notification Department

Claims

1. an accounting document acquisition unit that acquires accounting document information having one or more types of information selected from character string information and document images from one or more accounting document management devices; an inspection unit that determines whether the book and document information meets inspection conditions and obtains inspection results; and an output unit that outputs the inspection results.

2. The accounting document acquisition unit The inspection device according to claim 1 acquires access information from an access information storage unit in which access information for accessing each of the one or more accounting document management devices is stored, and uses the access information to acquire the accounting document information from the accounting document management device.

3. The accounting document acquisition unit acquiring the book document information having a document image from the one or more book document management devices; The inspection unit The inspection device according to claim 1 , further comprising: a determination unit that determines whether or not the document image satisfies an image condition, and obtains an inspection result.

4. The inspection unit The inspection device according to claim 3, further comprising: acquiring one or more character strings from the document image; determining whether the one or more character strings satisfy a reading condition that predetermined information, including one or more of the following information: amount, date, and business partner, can be acquired from the document image; and obtaining an inspection result.

5. The accounting document acquisition unit Acquiring the book document information having character string information and a document image from the one or more book document management devices; The inspection unit 2. The inspection device according to claim 1, further comprising: an inspection unit that acquires one or more character strings from the document image acquired by the accounting document acquisition unit; a determination unit that determines whether a consistency condition is satisfied between the one or more character strings and the character string information acquired by the accounting document acquisition unit; and an inspection result is obtained.

6. The accounting document acquisition unit Acquire one piece of character string information and two or more document images from the one or more ledger document management devices; The inspection unit The inspection device according to claim 5 , further comprising: a determination unit that determines whether the one piece of character string information and the two or more document images satisfy the consistency condition, and acquires an inspection result.

7. The accounting document acquisition unit acquiring two or more pieces of character string information and one document image from the one or more ledger document management devices; The inspection unit The inspection device according to claim 5 , further comprising: a determination unit that determines whether the two or more pieces of character string information and the one document image satisfy the consistency condition, and obtains an inspection result.

8. The accounting document acquisition unit two or more pieces of character string information and two or more document images are acquired; The inspection unit The inspection device according to claim 5 , further comprising: a determination unit that determines whether or not the two or more pieces of character string information and the two or more document images satisfy the consistency condition, and obtains an inspection result.

9. There are at least two accounting document management devices used by one user, an identifier conversion information storage unit that stores one or more pieces of identifier conversion information indicating a correspondence between a first user identifier in a first accounting document management device used by a user and a second user identifier in a second accounting document management device used by the user; a correspondence detection unit that refers to the identifier conversion information storage unit and detects that a user identifier corresponding to the character string information and a user identifier corresponding to the document image correspond to each other by using the identifier conversion information, even if the user identifiers corresponding to the character string information and the document image are different; The accounting document acquisition unit 7. The inspection device according to claim 6, wherein the character string information and the document image associated with each other by the user identifier are acquired.

10. The accounting document acquisition unit Acquiring the character string information from one ledger document management device and acquiring the document image from another ledger document management device; The inspection unit 2. The inspection device according to claim 1, wherein the inspection device uses the character string information and the document image acquired from different ledger document management devices to determine whether the inspection conditions are met and acquires the inspection results.

11. 2. The inspection device according to claim 1, further comprising a notification unit that notifies the inspection result to a notification destination specified by one or more notification destination information corresponding to the book document information on which the inspection result is based.

12. The notification unit The inspection device according to claim 11, wherein the inspection result is notified to different notification destinations depending on the inspection result.

13. a notification destination acquisition unit that acquires one or more pieces of notification destination information corresponding to the accounting document information acquired by the accounting document acquisition unit from the accounting document management device in which the accounting document information is stored; The notification unit The inspection device according to claim 11 , wherein the inspection result is notified to a destination specified by the one or more pieces of destination information acquired by the destination acquisition unit.

14. The accounting document acquisition unit Acquire two or more pieces of book and document information for a predetermined period for each user from the book and document management device; The inspection unit 2. The inspection device according to claim 1, wherein the inspection device inspects one or more pieces of book or document information using the two or more pieces of book or document information, and obtains inspection results.

15. The accounting document acquisition unit 2. The inspection device according to claim 1, wherein the accounting document information is acquired at different times for each accounting document management device, for each organization using the accounting document management device, or for each user using the accounting document management device.

16. The accounting document acquisition unit 2. The inspection device according to claim 1, wherein one or more pieces of book and document information for different periods are acquired for each book and document management device, for each organization using the book and document management device, or for each user using the book and document management device.

17. The notification unit The inspection device according to claim 11, wherein the inspection result is transmitted to the book and document management device.

18. An inspection method in which all processes performed by the inspection device according to any one of claims 1 to 17 are performed by a controller.

19. Computer, A program for causing the inspection device according to any one of claims 1 to 17 to function as the inspection device.

Images