Receipt processing apparatus, receipt processing method, and program

Abstract

To provide a receipt processing apparatus, a receipt processing method, and a program that enable flexible processing for duplicate registration of receipt information.SOLUTION: In a receipt system unit, a receipt processing apparatus 1 includes: a receipt receiving unit 121 which receives a receipt image from a first terminal used by an applicant who makes an application for a receipt; a receipt configuration unit 131 which acquires receipt information based on the receipt image; an inspection unit 132 which determines whether or not the receipt information is to be registered redundantly; an accumulation unit 134 which accumulates the receipt information acquired by the receipt configuration unit and an inspection result of the inspection unit, on a receipt management unit that stores receipt information regarding receipts; an instruction receiving unit 122 which receives an instruction to acquire the receipt information, from a second terminal used by an approver who approves the receipt; a receipt acquisition unit 135 which acquires the receipt information corresponding to the acquisition instruction and the inspection result from the receipt management unit; and a receipt transmission unit 142 which transmits the receipt information acquired by the receipt acquisition unit and the inspection result to the second terminal.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to a receipt processing device that receives and processes receipt images. [Background technology]

[0002] Previously, there was technology relating to a method for processing expense receipts, which includes the steps of receiving an electronic image of the expense receipt on a computer processor, processing the electronic image to obtain expense data, entering the expense data into an electronic expense report, and displaying the electronic expense report (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Special Publication No. 2006-511896 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the prior art has not been able to flexibly handle duplicate registration of receipt information. [Means for solving the problem]

[0005] The receipt processing device of the first invention is a receipt processing device that includes a receipt receiving unit that receives a receipt image from a first terminal used by an applicant who applies for a receipt, a receipt composition unit that acquires receipt information based on the receipt image, an inspection unit that determines whether the receipt information is a duplicate registration, a storage unit that accumulates the receipt information acquired by the receipt composition unit and the inspection results acquired by the inspection unit in a receipt management unit where receipt information related to receipts is stored, an instruction receiving unit that receives an instruction to acquire receipt information from a second terminal used by an approver who approves the receipt, a receipt acquisition unit that acquires receipt information and inspection results corresponding to the acquisition instruction from the receipt management unit, and a receipt sending unit that transmits the receipt information and inspection results acquired by the receipt acquisition unit to the second terminal.

[0006] This configuration allows flexible processing of duplicate registration of receipt information.

[0007] In addition, compared to the first invention, the receipt processing device of the second invention further includes a route management unit that stores route information that identifies the receipt approval route and two or more route information corresponding to the inspection results, and the receipt sending unit is a receipt processing device that sends receipt information and inspection results to the second terminal only when the instruction receiving unit receives an acquisition instruction from the second terminal of the approver corresponding to the route information corresponding to the inspection results.

[0008] This configuration allows flexible processing of duplicate registration of receipt information.

[0009] Furthermore, in the receipt processing device of the third invention, compared to the first or second invention, the inspection unit is equipped with a first inspection means that performs a first inspection as to whether receipt information will be registered twice, and a second inspection means that performs a second inspection of receipt information other than the first inspection, which is an inspection as to the legitimacy of the receipt information, and the storage unit is a receipt processing device that stores the inspection results, including type information that identifies the type of judgment that was inappropriate in the first inspection and second inspection, and the receipt information in the receipt management unit.

[0010] This configuration allows flexible processing for duplicate registration of receipt information, etc.

[0011] Furthermore, the receipt processing device of the fourth invention is a receipt processing device in which, compared to any one of the first to third inventions, the receipt sending unit may or may not send receipt information to the second terminal depending on the inspection results if the inspection results include information indicating that the inspection results are invalid.

[0012] This configuration allows flexible processing of duplicate registration of receipt information.

[0013] In addition, the receipt processing device of the fifth invention is a receipt processing device in which, compared to any one of the first to fourth inventions, the receipt composition unit performs character recognition processing on the receipt image, obtains two or more element information that is a character string, and obtains receipt information having two or more element information.

[0014] This configuration allows flexible processing of duplicate registration of receipt information. [Effects of the Invention]

[0015] The receipt processing device according to the present invention can flexibly handle duplicate registration of receipt information. [Brief explanation of the drawings]

[0016] [Figure 1] Conceptual diagram of receipt system A in embodiment 1 [Figure 2] Block diagram of the receipt system A [Figure 3] A flowchart illustrating an example of the operation of the receipt processing device 1 [Figure 4] A flowchart illustrating an example of the inspection process [Figure 5] A flowchart illustrating an example of the determination process [Figure 6] A flowchart illustrating an example of the destination determination process. [Figure 7]A flowchart illustrating an example of the receipt information acquisition process [Figure 8] A flowchart illustrating an example of the operation of the terminal device 2 [Figure 9] A diagram showing the user management table [Figure 10] A diagram showing the route management table [Figure 11] A diagram showing the receipt management table [Figure 12] FIG. 10 shows an example of the receipt image. [Figure 13] A diagram showing an example of the receipt screen [Figure 14] FIG. 10 shows an example of the receipt image. [Figure 15] FIG. 10 shows an example of the receipt image. [Figure 16] Overview of the computer system [Figure 17] Block diagram of the computer system DETAILED DESCRIPTION OF THE INVENTION

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

[0018] (Embodiment 1) In this embodiment, a receipt processing device is described that accepts a receipt image, checks whether receipt information based on the receipt image is a duplicate registration, and, even if a duplicate registration is found, stores the receipt information along with the check result, allowing the receipt approver to view the receipt information along with the check result. Note that in the receipt processing device, for example, receipt information is generated by character recognition of the receipt image. Also, duplicate registration of receipt information means that receipt information for the accepted receipt image has already been registered.

[0019] In this embodiment, we will explain a receipt processing device that accepts a receipt image, checks whether receipt information based on the receipt image is a duplicate registration, and determines the approval route for the receipt depending on the check result. Note that even if the check result is "NG," we will explain a receipt processing device that may or may not send the receipt information to an approver.

[0020] In this embodiment, a receipt processing device is described that performs inspections from two or more perspectives, including whether receipt information is a duplicate registration, and obtains inspection results that allow the type of inspection to be determined when the inspection result is "NG." The inspection result may be, for example, "NG" or "OK." "NG" may also be referred to as "invalid" or "fraudulent." "OK" may also be referred to as "valid" or "normal."

[0021] In this specification, 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.

[0022] Furthermore, in this specification, selecting or determining information Z means obtaining information Z, obtaining a pointer to information Z, obtaining the ID of information Z, setting a flag on information Z, etc., and it is sufficient if information Z can be accessed.

[0023] 1 is a conceptual diagram of a receipt system A according to this embodiment. The receipt system A comprises a receipt processing device 1 and one or more terminal devices 2.

[0024] The receipt processing device 1 is a server that receives and processes receipt images. The receipt processing device 1 may be, for example, a cloud server or an ASP server, but the type is not important.

[0025] The terminal device 2 is a terminal that transmits receipt images to the receipt processing device 1. The terminal device 2 is a terminal used by an applicant who applies for a receipt. The terminal device 2 may be, for example, a smartphone, a personal computer, or a tablet terminal, but the type is not important.

[0026] The terminal device 2 is, for example, a first terminal 2(1) or a second terminal 2(2). The first terminal 2(1) is a terminal used by an applicant who applies for a receipt. The second terminal 2(2) is a terminal used by an approver who approves a receipt. The same terminal device 2 may be both the first terminal 2(1) and the second terminal 2(2). In other words, one user may be both the applicant and the approver.

[0027] The receipt processing device 1 and one or more terminal devices 2 can communicate with each other via a network such as the Internet.

[0028] FIG. 2 is a block diagram of a receipt system A according to this embodiment.

[0029] The receipt processing device 1 includes a storage unit 11, a receiving unit 12, a processing unit 13, and a transmission unit 14. The storage unit 11 includes a user management unit 111, a route management unit 112, and a receipt management unit 113. The receiving unit 12 includes a receipt receiving unit 121 and an instruction receiving unit 122. The processing unit 13 includes a receipt configuration unit 131, an inspection unit 132, a judgment unit 133, a storage unit 134, and a receipt acquisition unit 135. The inspection unit 132 includes a first inspection means 1321 and a second inspection means 1322. The transmission unit 14 includes an inspection result transmission unit 141 and a receipt transmission unit 142.

[0030] The terminal device 2 includes a terminal storage unit 21, a terminal reception unit 22, a terminal processing unit 23, a terminal transmission unit 24, a terminal reception unit 25, and a terminal output unit 26.

[0031] Various types of information are stored in the storage unit 11 that constitutes the receipt processing device 1. The various types of information include, for example, user information (to be described later), route information (to be described later), and receipt information (to be described later).

[0032] The user management unit 111 stores one or more pieces of user information. User information is information about users who use the receipt processing device 1. The user information has a user identifier. The user information has, for example, one or more user attribute values. The user identifier is information that identifies a user. The user identifier is, for example, a user ID, email address, telephone number, or name. The user attribute value is, for example, the name of the organization (e.g., company) to which the user belongs, the name of the department to which the user belongs, the user's job title, name, and age.

[0033] The route management unit 112 stores two or more pieces of route information. Route information is information that specifies the approval route of a receipt. Route information is information that specifies one or more approvers. Route information includes, for example, information that specifies the order of approval by two or more approvers. However, route information may be information that only specifies one or more approvers. For example, each of two or more pieces of route information is associated with a condition. Here, the condition is, for example, a condition related to an inspection result. The condition may be, for example, a condition related to one or more user attribute values. The condition may be, for example, a condition related to one or more element information. The condition may be, for example, a condition related to two or more types of information selected from the inspection result, user attribute value, and element information. For example, each of two or more pieces of route information is associated with a condition related to the inspection result. In other words, the approval route of a receipt differs depending on, for example, the inspection result. Note that element information is information that constitutes receipt information, which will be described later. Element information is a character string. Element information is, for example, an amount, a payee, a destination, and a date.

[0034] It is preferable that route information be associated with storage conditions and destination information. Storage conditions are conditions for determining whether or not to store receipt information. The storage conditions may be storage flags. Destination information is information for identifying the destination. Destination information is, for example, an email address, a user identifier, or information for identifying the user (e.g., "applicant" or "supervisor").

[0035] The receipt management unit 113 stores one or more pieces of receipt information. Receipt information is information related to receipts. Receipt information may or may not include a receipt image. Receipt information may consist of only a receipt image. Receipt information includes, for example, one or more pieces of element information written on a receipt. Receipt information includes, for example, one or more pieces of element information obtained by performing character recognition processing on a receipt image. Receipt information corresponds, for example, to one or more inspection results. The inspection results are the results of inspection processing performed by the inspection unit 132, which will be described later. Receipt information corresponds, for example, to one or more approval flags. The approval flag is information indicating whether the receipt has been approved by the approver.

[0036] The receiving unit 12 receives various instructions and information from the terminal device 2. The various instructions and information include, for example, a receipt image (to be described later), a receipt application instruction (to be described later), and an acquisition instruction (to be described later).

[0037] The receipt receiving unit 121 receives a receipt image from the first terminal 2(1). A receipt image is an image of a receipt. A receipt image is, for example, an image of a photograph of a receipt or an image of a receipt converted into PDF. The receipt image may be, for example, PDF, GIF, or JPEG, but the data format is not important.

[0038] The receipt receiving unit 121 may receive a receipt request instruction. The receipt request instruction is an instruction to request a receipt. The receipt request instruction includes a receipt image. The receipt request instruction preferably includes a user identifier.

[0039] The instruction receiving unit 122 receives an instruction to acquire receipt information from the second terminal 2(1). The instruction to acquire receipt information is an instruction to acquire receipt information. The acquisition instruction is, for example, an instruction for the approver to acquire receipt information in order to carry out the receipt approval procedure.

[0040] The processing unit 13 performs various types of processing. The various types of processing are, for example, processing performed by a receipt configuration unit 131, an inspection unit 132, a determination unit 133, a storage unit 134, and a receipt acquisition unit 135.

[0041] The processing unit 13 performs, for example, receipt processing. Receipt processing is processing for receipt information. Receipt processing is processing, for example, when approval is obtained from one or more approvers for a requested receipt. Receipt processing is processing, for example, when a requested receipt is legitimate.

[0042] Receipt processing is, for example, processing for depositing the amount contained in the receipt information of a receipt into an account specified by the account information paired with the user identifier of the user who applied for the receipt. Receipt processing is, for example, processing for adding the amount contained in the receipt information of a receipt to the salary of the applicant, into an account specified by the account information paired with the user identifier of the user who applied for the receipt.

[0043] The receipt composition unit 131 acquires receipt information based on the receipt image received by the receipt receiving unit 121. For example, the receipt composition unit 131 performs character recognition processing on the receipt image to acquire two or more pieces of element information, and acquires receipt information having the two or more pieces of element information. Note that the receipt information based on the receipt image may include the receipt image. The receipt information may also include element information input by the applicant.

[0044] The inspection unit 132 inspects the receipt information acquired by the receipt composition unit 131 and outputs the inspection result. For example, the inspection unit 132 determines whether the receipt information is a duplicate registration. The inspection result includes, for example, type information that identifies the type of inspection that is NG. The type information is, for example, "duplicate registration," "taxi use," or "over budget."

[0045] The first inspection means 1321 performs a first inspection to determine whether the receipt information is a duplicate registration. The first inspection means 1321 determines whether receipt information identical to the receipt information acquired by the receipt composition unit 131 exists in the receipt management unit 113, and acquires a first inspection result, which is the result of the determination. The first inspection result is, for example, "duplicate registration" or "not duplicate registration." The first inspection result is, for example, "invalid" or "valid."

[0046] The second inspection means 1322 performs a second inspection other than the first inspection on the receipt information. Like the first inspection, the second inspection is an inspection of the legitimacy of the receipt information. For example, the second inspection means 1322 detects that the recipient name in the receipt information contains the character string "taxi" and determines that the receipt information is invalid. In such a case, an unusable taxi was used. For example, the second inspection means 1322 detects that when the amount contained in the receipt information is added to the amount used up to that point, it exceeds the budget corresponding to the applicant, and determines that the receipt information is invalid. In such a case, it is determined that the budget has been exceeded.

[0047] The determination unit 133 determines whether to store receipt information according to the inspection result acquired by the inspection unit 132. The determination unit 133 may determine whether to store receipt information according to, for example, the inspection result and a user attribute value. The determination unit 133 may determine whether to store receipt information according to, for example, the inspection result and element information.

[0048] The determination unit 133 may determine whether or not to transmit the inspection result to the terminal device 2, depending on the inspection result acquired by the inspection unit 132. The determination unit 133 may determine whether or not to transmit the inspection result to the terminal device 2, depending on, for example, the inspection result and a user attribute value. The determination unit 133 may determine whether or not to transmit the inspection result to the terminal device 2, depending on, for example, the inspection result and element information.

[0049] The storage unit 134 stores the receipt information acquired by the receipt composition unit 131 and the inspection results acquired by the inspection unit 132 in the receipt management unit 113. Even if it is determined that the receipt information is a duplicate registration, it is preferable that the storage unit 134 stores the receipt information and the inspection results in the receipt management unit 113. When it is determined that the receipt information is a duplicate registration, it is preferable that the storage unit 134 stores or does not store the receipt information and the inspection results in the receipt management unit 113 depending on the user attribute value or element information.

[0050] The storage unit 134 may store in the receipt management unit 113 the inspection results including type information that identifies the type of judgment that was inappropriate in the first inspection and the second inspection, and the receipt information.

[0051] The receipt acquisition unit 135 acquires receipt information and inspection results corresponding to the acquisition instruction received by the instruction receiving unit 122 from the receipt management unit 113. It goes without saying that the receipt acquisition unit 135 may acquire two or more sets of receipt information and inspection results.

[0052] The transmission unit 14 transmits various types of information to the terminal device 2. The various types of information include, for example, test results, receipt information, and screen information.

[0053] The inspection result transmitting unit 141 transmits the inspection result to the terminal device 2. It is preferable that the inspection result transmitting unit 141 transmits the inspection result when the determining unit 133 determines that the inspection result should be transmitted, and does not transmit the inspection result when the determining unit 133 determines that the inspection result should not be transmitted.

[0054] The receipt sending unit 142 sends to the second terminal 2(2) the receipt information and the inspection results acquired by the receipt acquisition unit 135. This transmission is for approval by the approver.

[0055] It is preferable that the receipt sending unit 142 sends the receipt information and the inspection results to the second terminal 2(2) of the approver only when the instruction receiving unit 122 receives an acquisition instruction from the second terminal 2(2) of the approver corresponding to the route information according to the inspection results. The receipt sending unit 142 may send the receipt information and the inspection results to the first terminal 2(1) of the applicant. The receipt sending unit 142 does not normally send the receipt information and the inspection results to the terminal device 2 of a user who is neither the approver nor the applicant.

[0056] It is preferable that the receipt sending unit 142 may or may not send receipt information to the second terminal 2(2) depending on the inspection result if the inspection result includes information indicating that the inspection result is invalid.

[0057] Various types of information are stored in the terminal storage unit 21 included in the terminal device 2. The various types of information include, for example, a user identifier and a receipt image.

[0058] The terminal reception unit 22 receives various types of information, instructions, etc. Examples of the various types of information, instructions, etc. include a receipt image, a receipt application instruction, an acquisition instruction, or an approval instruction.

[0059] The approval instruction is an instruction to approve the receipt information or an instruction not to approve the receipt information. The approval instruction usually has approval information. The approval information is information indicating that the receipt information is approved or information indicating that the receipt information is not approved.

[0060] The means for inputting various information and instructions may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0061] The terminal processing unit 23 performs various types of processing. For example, the various types of processing are processing to convert received information, instructions, etc. into information, instructions, etc. with a structure to be transmitted. For example, the various types of processing are processing to convert received information into information with a structure to be output.

[0062] The terminal transmission unit 24 transmits various information, instructions, etc. to the receipt processing device 1. The various information, instructions, etc. are, for example, a receipt image, a receipt application instruction, an acquisition instruction, or an approval instruction.

[0063] The terminal receiving unit 25 receives various types of information from the receipt processing device 1. The various types of information include, for example, receipt information, inspection results, and receipt screen information. Receipt screen information is information for configuring a screen containing receipt information. Screen information such as receipt screen information is written in, for example, HTML, XML, or the like, but the actual format is not important.

[0064] The terminal output unit 26 outputs various types of information, such as receipt information, inspection results, and a receipt screen.

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

[0066] The storage unit 11, user management unit 111, route management unit 112, receipt management unit 113, and terminal storage unit 21 are preferably non-volatile recording media, but can also be realized by volatile recording media.

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

[0068] The receiving unit 12, receipt receiving unit 121, instruction receiving unit 122, and terminal receiving unit 25 are usually realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0069] The processing unit 13, receipt construction unit 131, inspection unit 132, judgment unit 133, storage unit 134, receipt acquisition unit 135, first inspection means 1321, second inspection means 1322, and terminal processing unit 23 can typically be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are typically 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 is not important.

[0070] The transmitting unit 14, the inspection result transmitting unit 141, the receipt transmitting unit 142, and the terminal transmitting unit 24 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

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

[0072] The terminal output unit 26 may or may not include an output device such as a display, a speaker, etc. The terminal output unit 26 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.

[0073] Next, an example of the operation of the receipt processing device 1 will be described with reference to the flowchart of FIG.

[0074] (Step S301) The receipt receiving unit 121 determines whether or not a receipt application instruction including a receipt image has been received from the terminal device 2. If a receipt application instruction has been received, the process proceeds to step S302; if not, the process proceeds to step S313. Note that the receipt application instruction here is associated with a user identifier.

[0075] (Step S302) The receipt composition unit 131 acquires the receipt image included in the receipt application instruction received in step S301.

[0076] (Step S303) The receipt composition unit 131 performs character recognition processing on the receipt image acquired in step S302 to acquire two or more pieces of element information.

[0077] (Step S304) The receipt composition unit 131 composes receipt information having two or more pieces of element information and a receipt image.

[0078] (Step S305) The checking unit 132 acquires the user identifier associated with the receipt application instruction. The checking unit 132 acquires user information paired with the user identifier from the user management unit 111.

[0079] (Step S306) The inspection unit 132 inspects the receipt information using the receipt information constructed in step S304 and the user information acquired in step S305, and acquires the inspection result. An example of such inspection processing will be described with reference to the flowchart in FIG. 4.

[0080] (Step S307) The determination unit 133 determines what process (normal, storage process, transmission process) to perform in accordance with the inspection result. An example of such determination process will be described with reference to the flowchart of FIG.

[0081] (Step S308) If the determination result in step S307 includes information indicating "accumulate", the process proceeds to step S309, and if the determination result does not include information indicating "accumulate", the process proceeds to step S310.

[0082] (Step S309) The storage unit 134 acquires a unique receipt identifier. Next, the storage unit 134 stores the receipt information acquired in step S304 and the inspection results acquired in step S306 in the receipt management unit 113 in association with the receipt identifier.

[0083] (Step S310) If the result of the determination in step S307 includes information indicating "send", the process proceeds to step S311, and if the result does not include information indicating "send", the process returns to step S301.

[0084] (Step S311) The processing unit 13 determines one or more destinations. An example of the destination determination process will be described with reference to the flowchart of FIG.

[0085] (Step S312) The test result transmitting unit 141 transmits the test result acquired in step S306 to one or more destinations determined in step S311. Return to step S301.

[0086] Here, the receipt sending unit 142 may send all or part of the receipt information to one or more destinations determined in step S311.

[0087] (Step S313) The instruction receiving unit 122 determines whether or not an instruction to acquire receipt information has been received from the terminal device 2. If an instruction to acquire receipt information has been received, the process proceeds to step S314; if not, the process proceeds to step S317. Note that the instruction to acquire receipt information here is associated with the user identifier.

[0088] (Step S314) The receipt acquisition unit 135 acquires one or more pairs of receipt information and inspection results that are subject to approval by the user identified by the user identifier associated with the acquisition instruction received in step S313. An example of such receipt information acquisition processing will be described using the flowchart in FIG.

[0089] (Step S315) The receipt acquisition unit 135 uses the set of receipt information and inspection results acquired in step S314 to compose receipt screen information to be sent to the terminal device 2.

[0090] (Step S316) The receipt sending unit 142 sends the receipt screen information created in step S315 to the terminal device 2. Return to step S301.

[0091] (Step S317) The receiving unit 12 determines whether or not approval information has been received from the terminal device 2. If approval information has been received, the process proceeds to step S318; if not, the process returns to step S301. The approval information here corresponds to the user identifier and the receipt identifier. The approval information is, for example, either "approved" or "not approved."

[0092] (Step S318) The storage unit 134 sets the attribute value of the attribute "approval information" of the receipt management unit 113, which is the approval information corresponding to the user identifier and the receipt identifier, to the approval information received in step S317. That is, the storage unit 134 stores the approval information received in step S317 in the receipt management unit 113.

[0093] (Step S319) If the approval information received in step S317 is "OK (approved)", the process proceeds to step S320, and if it is "NG (not approved)", the process proceeds to step S325.

[0094] (Step S320) The processing unit 13 determines whether or not approval of one or more receipt information identified by the receipt identifier paired with the approval information received in step S317 has been completed. If approval has been completed, the process proceeds to step S321, and if approval has not been completed, the process proceeds to step S322. Note that approval is determined to be completed when the user identified by the user identifier paired with the approval information is the last approver.

[0095] (Step S321) The processing unit 13 performs receipt processing, which is processing on receipt information identified by the receipt identifier paired with the approval information received in step S317.

[0096] (Step S322) It is determined whether or not to send information to the next approver to prompt them to approve. If the information is to be sent, the process proceeds to step S323, and if not, the process returns to step S301.

[0097] (Step S323) The processing unit 13 acquires the destination of the next approver.

[0098] (Step S324) The receipt sending unit 142 sends the receipt information to the destination of the next approver. Return to step S301. Note that here, the receipt sending unit 142 may send information that simply prompts the next approver to approve.

[0099] (Step S325) The processing unit 13 acquires a user identifier paired with the receipt identifier paired with the approval information. The processing unit 13 acquires a destination paired with the user identifier from the user management unit 111.

[0100] (Step S326) The transmission unit 14 transmits to the destination acquired in step S325 a message indicating that the requested receipt has not been approved. The process returns to step S301.

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

[0102] Next, an example of the inspection process in step S306 will be described with reference to the flowchart in FIG.

[0103] (Step S401) The first checking means 1321 assigns 1 to a counter i.

[0104] (Step S402) The first inspection means 1321 determines whether or not the i-th receipt information exists in the receipt management unit 113. If the i-th receipt information exists, the process proceeds to step S403; if not, the process proceeds to step S407.

[0105] (Step S403) The first checking means 1321 acquires the i-th receipt information from the receipt management unit 113.

[0106] (Step S404) The first inspection means 1321 determines whether the receipt information acquired in step S403 is the same as the receipt information configured in step S304. If they are the same, the process proceeds to step S405, and if they are not the same, the process proceeds to step S406.

[0107] (Step S405) The first inspection means 1321 assigns "NG" to the variable "first inspection result." Then, the process proceeds to step S408.

[0108] (Step S406) The first checking means 1321 increments the counter i by 1. The process returns to step S402.

[0109] (Step S407) The first inspection means 1321 assigns "OK" to the variable "first inspection result".

[0110] (Step S408) The second checking means 1322 assigns 2 to the counter j.

[0111] (Step S409) The second checking means 1322 judges whether or not the j-th check condition exists. If the j-th check condition exists, the process proceeds to step S410, and if not, the process returns to the upper process.

[0112] (Step S410) The second inspection means 1322 determines whether the receipt information constructed in step S304 satisfies the j-th inspection condition. If the j-th inspection condition is satisfied, the process proceeds to step S411; if not, the process proceeds to step S412.

[0113] (Step S411) The second inspection means 1322 assigns "OK" to the variable "jth inspection result." Then, the process proceeds to step S413.

[0114] (Step S412) The second inspection means 1322 assigns "NG" to the variable "jth inspection result".

[0115] (Step S413) The second checking means 1322 increments the counter j by 1. The process returns to step S409.

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

[0117] (Step S501) The determination unit 133 acquires the accumulation condition from the storage unit 11.

[0118] (Step S502) The judgment unit 133 judges whether the acquired test results, etc., match the accumulation conditions. If the test results, etc., match the accumulation conditions, the process proceeds to step S503; if not, the process proceeds to step S504.

[0119] The test results etc. here may be just the test results, or the test results and user attribute values, or the test results and element information, or the test results, user attribute values ​​and element information. In other words, the accumulation conditions may be conditions related to the test results, or conditions related to the test results and user attribute values, or conditions related to the test results and element information, or conditions related to the test results, user attribute values ​​and element information.

[0120] (Step S503) The determination unit 133 assigns "accumulate" to the variable "result." The process proceeds to step S505.

[0121] (Step S504) The determination unit 133 assigns "do not store" to the variable "result".

[0122] (Step S505) The determination unit 133 acquires the transmission conditions from the storage unit 11.

[0123] (Step S506) The determination unit 133 determines whether the acquired test results, etc., match the transmission conditions. If they match the transmission conditions, the process proceeds to step S507, and if they do not match, the process proceeds to step S508.

[0124] The test results etc. here may be just the test results, or the test results and user attribute values, or the test results and element information, or the test results, user attribute values ​​and element information. In other words, the transmission conditions may be conditions related to the test results, or conditions related to the test results and user attribute values, or conditions related to the test results and element information, or conditions related to the test results, user attribute values ​​and element information.

[0125] (Step S507) The determination unit 133 assigns "send" to the variable "result." The process returns to the upper level process.

[0126] (Step S508) The determination unit 133 assigns "not to send" to the variable "result", and returns to the upper-level process.

[0127] Next, an example of the destination determination process in step S311 will be described with reference to the flowchart in FIG.

[0128] (Step S601) The processing unit 13 acquires the test results.

[0129] (Step S602) The processing unit 13 acquires a user identifier.

[0130] (Step S603) The processing unit 13 acquires one or more pieces of destination information corresponding to the test result and the user identifier from the route management unit 112. The process returns to the upper processing.

[0131] Next, an example of the receipt information acquisition process in step S314 will be described with reference to the flowchart in FIG.

[0132] (Step S701) The receipt acquisition unit 135 acquires a user identifier paired with the acquisition instruction. Note that the user identifier is information for identifying the user who transmitted the acquisition instruction.

[0133] (Step S702) The receipt acquisition unit 135 assigns 1 to the counter i.

[0134] (Step S703) The receipt acquisition unit 135 determines whether the i-th receipt information exists in the receipt management unit 113. If the i-th receipt information exists, the process proceeds to step S704; if not, the process returns to the upper level process.

[0135] (Step S704) The receipt acquisition unit 135 acquires the i-th receipt information from the receipt management unit 113.

[0136] (Step S705) The receipt acquisition unit 135 determines whether or not there is a next approver corresponding to the i-th receipt information. If there is a next approver, the process proceeds to step S706; if there is not, the process proceeds to step S710. Note that the next approver is, for example, the case where the approver flag value in FIG. 11 is NULL (-). Note that the method for determining whether or not there is a next approver depends on the method for managing approval information.

[0137] (Step S706) The receipt acquisition unit 135 acquires the user identifier paired with the i-th receipt information from the receipt management unit 113. This user identifier is the identifier of the person who applied for the i-th receipt.

[0138] (Step S707) The receipt acquisition unit 135 acquires the information of the approver (e.g., "Supervisor," "Accounting Department Employee," user identifier) ​​identified by the ranking information (e.g., approval flag 1, approval flag 2, or approval flag 3 in Figure 11) corresponding to the next approver, which is contained in the route information paired with the route condition satisfied by the inspection results, etc. paired with the i-th receipt information.

[0139] (Step S708) The receipt acquisition unit 135 determines whether the user identifier etc. acquired in step S701 matches the approver conditions. If the approver conditions are met, the process proceeds to step S709; if not, the process proceeds to step S710. The approver conditions are that the information matches the approver information acquired in step S707.

[0140] (Step S709) The receipt acquisition unit 135 acquires the i-th receipt information and inspection results, and temporarily stores them in a buffer (not shown).

[0141] (Step S710) The receipt acquisition unit 135 increments the counter i by 1. The process returns to step S703.

[0142] Next, an example of the operation of the terminal device 2 will be described with reference to the flowchart of FIG.

[0143] (Step S801) The terminal reception unit 22 determines whether or not a receipt application instruction including a receipt image has been received. If a receipt application instruction has been received, the process proceeds to step S802, and if not, the process proceeds to step S803.

[0144] (Step S802) The terminal processing unit 23 acquires the user identifier from the terminal storage unit 21 and composes a receipt application instruction having the user identifier. The terminal transmission unit 24 transmits the receipt application instruction to the receipt processing device 1. Return to step S801.

[0145] (Step S803) The terminal reception unit 22 determines whether or not an instruction to acquire receipt information has been accepted. If an instruction to acquire receipt information has been accepted, the process proceeds to step S804, and if not, the process proceeds to step S807.

[0146] (Step S804) The terminal processing unit 23 acquires the user identifier from the terminal storage unit 21 and creates an acquisition instruction having the user identifier. The terminal transmission unit 24 transmits the acquisition instruction to the receipt processing device 1.

[0147] (Step S805) In response to the transmission of the acquisition instruction, the terminal receiving unit 25 determines whether or not receipt screen information has been received from the receipt processing device 1. If receipt screen information has been received, the process proceeds to step S806; if not, the process returns to step S805.

[0148] (Step S806) The terminal processing unit 23 uses the received receipt screen information to create a receipt screen. The terminal output unit 26 outputs the receipt screen. Return to step S801.

[0149] (Step S807) The terminal reception unit 22 determines whether or not an approval instruction for the receipt information has been received. If an approval instruction has been received, the process proceeds to step S808, and if not, the process proceeds to step S809.

[0150] (Step S808) The terminal processing unit 23 acquires the user identifier from the terminal storage unit 21 and constructs an approval instruction having the user identifier and a receipt identifier that identifies the receipt information. The terminal transmission unit 24 transmits the approval instruction to the receipt processing device 1. Return to step S801.

[0151] (Step S809) The terminal receiving unit 25 determines whether or not information has been received from the receipt processing device 1. If information has been received, the process proceeds to step S810, and if information has not been received, the process returns to step S801.

[0152] (Step S810) The terminal processing unit 23 composes information to be output. The terminal output unit 26 outputs the information. The process returns to step S801.

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

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

[0155] Currently, the user management table shown in Figure 9 is stored in the user management unit 111 of the receipt processing device 1. The user management table is a table for managing user information. A user management table may exist for each organization (e.g., company). The user management table manages one or more records having an "ID," "user identifier," and "user attribute value." The "user attribute value" is "name," "company," "department," "job title," "destination," and "supervisor." The "ID" is information that identifies the record. The "destination" here is an email address, but it can also be an ID for an SNS such as Slack (registered trademark). The "supervisor" here is the user identifier of the superior of the user identified by the user identifier.

[0156] The route management unit 112 stores a route management table shown in FIG. 10. The route management table is a table that manages information related to receipt approval routes. The route management table includes "ID," "company," "route conditions," "route information," "accumulation flag," and "destination information." The "route information" includes "first approver," "second approver," and "third approver."

[0157] A "root condition" is a condition to which root information is applied. A root condition is a condition based on test results, a condition based on user attribute values ​​(e.g., job title, years of service), a condition based on element information, or a condition based on two or more types of information from test results, user attribute values, and element information. "First approver" is information that identifies the first approver. "Second approver" is information that identifies the second approver. "Third approver" is information that identifies the third approver. Information that identifies an approver can be any information that can identify a person, such as a department and job title, user identifier, job title, or relationship with the user (e.g., "supervisor"). An accumulation flag of "1" indicates that receipt information and test results are accumulated. An accumulation flag of "0" indicates that receipt information, etc., is not accumulated. "Destination information" here is an email address, but it can also be an SNS ID such as Slack.

[0158] The receipt management unit 113 stores the receipt management table shown in Figure 11. The receipt management table is a table for managing receipt information. The receipt management table has "ID," "user identifier," "receipt information," "approval information," and "inspection results." "Receipt information" has "date," "amount," "payee," and "receipt image." "Approval information" has "approval flag 1," "approval flag 2," and "approval flag 3." "Approval flag 1" indicates whether the first approver has approved. "Approval flag 2" indicates whether the second approver has approved. "Approval flag 3" indicates whether the third approver has approved. An approval flag of "1" indicates approval, and "0" indicates no approval. An approval flag of "-" indicates "NULL," which means no data has been entered.

[0159] It is assumed that the storage unit 11 stores a first inspection condition "duplicate registration = NG" and a second inspection condition "taxi use by a person with the job title "employee" is NG."

[0160] In the above situation, the following two specific examples will be explained.

[0161] (Example 1) Let us assume that user A "Yamada A" inputs a receipt application instruction including the receipt image shown in Figure 12 into the terminal device 2. The terminal device 2 then accepts the receipt application instruction and sends a receipt application instruction paired with the user identifier "U001" to the receipt processing device 1.

[0162] Next, the receipt receiving unit 121 of the receipt processing device 1 receives the receipt application instruction from the terminal device 2.

[0163] Next, the receipt composition unit 131 acquires the receipt image included in the receipt application instruction. Next, the receipt composition unit 131 performs character recognition processing on the receipt image (FIG. 12) and acquires, for example, three pieces of element information (1201, 1202, 1203). Next, the receipt composition unit 131 composes receipt information including "<Date> 2024 / 3 / 27 <Amount> 940 <Payee> Tsubame Taxi Co., Ltd." and the receipt image.

[0164] Next, the inspection unit 132 acquires the user identifier "U001" associated with the receipt application instruction. The inspection unit 132 acquires the user information "<Name>Yamada A <Company>Company X <Department>Sales Department <Position>Employee <Destination>ya@x.com <Supervisor>U002..." that is paired with the user identifier "U001" from the user management table (FIG. 8).

[0165] Next, the inspection unit 132 uses the receipt information and the user information to perform the inspection process described using the flowchart in Figure 4, and obtains the inspection result "<First inspection result> OK <Second inspection result> NG".

[0166] Next, the judgment unit 133 uses the inspection result and the user attribute value to refer to the route management table of FIG. 10, and acquires the accumulation flag "1" and the destination information "applicant" and "supervisor" that are paired with "second inspection result=NG" in the last record of "ID=1" in FIG. 10 through the judgment process described using the flowchart of FIG. 5.

[0167] Next, the storage unit 134 acquires the unique receipt identifier "268." Next, the storage unit 134 stores the acquired receipt information in the receipt management table (FIG. 11) in association with the receipt identifier "268." Here, the stored record is the record with "ID=268" in FIG. 11.

[0168] Furthermore, the processing unit 13 obtains, from the user management table (FIG. 9), the destination information "ya@x.com" paired with the user identifier "U001" and the destination information "ib@x.com" paired with the superior's user identifier "U002" based on the obtained destination information "applicant" and "supervisor." Next, the inspection result sending unit 141 sends an email containing the inspection results to each of the two destinations. Note that here, the receipt sending unit 142 may also send an email containing all or part of the receipt information.

[0169] Then, the terminal devices 2 corresponding to the two destinations (Yamada A and Inoue B) receive and output the emails containing the test results.

[0170] Next, suppose that Inoue B, Yamada A's boss, acquires the receipt information to be approved and inputs an instruction to acquire the receipt information into the terminal device 2 in order to approve it. Next, the terminal reception unit 22 accepts the instruction to acquire the receipt information. Next, the terminal processing unit 23 acquires the user identifier "U002" from the terminal storage unit 21 and constructs an acquisition instruction having the user identifier "U002". Next, the terminal transmission unit 24 transmits the acquisition instruction to the receipt processing device 1.

[0171] Next, the instruction receiving unit 122 of the receipt processing device 1 receives the instruction to acquire the receipt information from the terminal device 2.

[0172] Next, the receipt acquisition unit 135 acquires the user identifier "U002." Next, the receipt acquisition unit 135 acquires the user identifiers "U001" and "U102" of subordinates who have the user identifier as their superior from the user management table (FIG. 8). Next, the receipt acquisition unit 135 acquires the receipt information and inspection results of the receipt that is paired with the user identifier "U001" or "U102" and that Inoue B should approve from the receipt management table (FIG. 11) by the process described using the flowchart in FIG. 7. Next, the receipt acquisition unit 135 uses the acquired pair of receipt information and inspection results to construct receipt screen information to be sent to the terminal device 2. Next, the receipt sending unit 142 sends the receipt screen information to the terminal device 2.

[0173] Next, the terminal device 2 receives the receipt screen information and outputs the receipt screen shown in FIG.

[0174] Next, it is assumed that Inoue B checks the approval box 1301 in FIG.

[0175] Next, the terminal reception unit 22 of the terminal device 2 receives an approval instruction for the receipt information (receipt identifier "268"). The terminal processing unit 23 acquires the user identifier "U002" from the terminal storage unit 21 and creates approval information having the user identifier: "<Approver Identifier>U002 <User Identifier>U001 <Receipt Identifier>268 <Approval Information>1". Next, the terminal transmission unit 24 transmits the approval instruction to the receipt processing device 1.

[0176] Next, the receiving unit 12 of the receipt processing device 1 receives the approval information from the terminal device 2. Next, the storage unit 134 changes the attribute value of the attribute "approval flag 1" (the first NULL attribute value of the three approval flags) in the receipt management table (FIG. 11) for the approval information corresponding to receipt identifier "268" from "NULL (-)" to "1."

[0177] (Example 2) Let us assume that user B "Inoue B" inputs a receipt application instruction including the receipt image shown in Figure 14 into the terminal device 2. The terminal device 2 then accepts the receipt application instruction and sends a receipt application instruction paired with the user identifier "U002" to the receipt processing device 1.

[0178] Next, the receipt processing device 1 receives the receipt application instruction from the terminal device 2, inspects it using the above-mentioned process, determines that it is valid, and registers the receipt information. The registered receipt information is the record with "ID=351" in Figure 11.

[0179] Furthermore, suppose that user B "Inoue B" then again inputs a receipt application instruction including the receipt image shown in Figure 14 into the terminal device 2. The terminal device 2 then accepts the receipt application instruction and sends a receipt application instruction paired with the user identifier "U002" to the receipt processing device 1.

[0180] Next, the receipt receiving unit 121 of the receipt processing device 1 receives the receipt application instruction from the terminal device 2.

[0181] Next, the receipt composition unit 131 acquires the receipt image (FIG. 14) included in the receipt application instruction. Next, the receipt composition unit 131 performs character recognition processing on the receipt image to acquire, for example, three pieces of element information. Next, the receipt composition unit 131 composes receipt information including "<Date> 2024 / 3 / 28 <Amount> 660 <Payee> Aomori Prefectural Road Public Corporation" and the receipt image.

[0182] Next, the inspection unit 132 acquires the user identifier "U002" associated with the receipt application instruction. The inspection unit 132 acquires the user information "<Name> Inoue B <Company> Company X <Department> Sales Department <Title> Section Chief <Destination> ib@x.com <Supervisor> U003..." that is paired with the user identifier "U002" from the user management table (FIG. 8).

[0183] Next, the inspection unit 132 uses the receipt information and the user information to perform the inspection process described using the flowchart in Figure 4, and obtains the inspection result "<First inspection result> NG <Second inspection result> OK".

[0184] Next, the judgment unit 133 uses the inspection result and the user attribute value to refer to the route management table of Figure 9, and through the judgment process described using the flowchart of Figure 5, obtains the accumulation flag "1" and the destination information "applicant" and "supervisor" that are paired with "First inspection result = NG AND Second inspection result = OK AND Position >= Section Chief" in the second record from the bottom of "ID = 1" in Figure 9.

[0185] Next, the storage unit 134 acquires the storage flag "1". The storage unit 134 acquires the unique receipt identifier "352". Next, the storage unit 134 stores the acquired receipt information in the receipt management table (FIG. 11) in association with the receipt identifier. This record is the record with "ID=352" in FIG. 11.

[0186] Next, the processing unit 13 acquires the destination information "applicant" and "supervisor." The processing unit 13 also acquires the destination "ib@x.com" that pairs with the user identifier "U002" corresponding to the destination information "applicant" from the user management table (FIG. 8). The processing unit 13 also acquires the user identifier "U003" of the supervisor that pairs with the user identifier "U002" based on the destination information "supervisor" from the user management table (FIG. 8). Next, the processing unit 13 acquires the destination "tc@x.com" that pairs with the user identifier "U003" from the user management table (FIG. 8).

[0187] Next, the inspection result transmitting unit 141 transmits the inspection result ("duplicate registration") and receipt information to the destinations "ib@x.com" and "tc@x.com".

[0188] Next, the terminal devices 2 of Inoue B and Tanaka C receive the inspection result ("duplicate registration") and receipt information by email and output them.

[0189] Also, suppose that Tanaka C, Inoue B's boss, acquires receipt information to be approved and inputs an instruction to acquire receipt information into the terminal device 2 to approve it. Next, the terminal reception unit 22 accepts the instruction to acquire receipt information. Next, the terminal processing unit 23 acquires the user identifier "U003" from the terminal storage unit 21 and constructs an acquisition instruction having the user identifier "U003". Next, the terminal transmission unit 24 transmits the acquisition instruction to the receipt processing device 1.

[0190] Next, the instruction receiving unit 122 of the receipt processing device 1 receives the instruction to acquire the receipt information from the terminal device 2.

[0191] Next, the receipt acquisition unit 135 acquires the user identifier "U003." Next, the receipt acquisition unit 135 acquires the user identifiers "U002" and "U082" of subordinates who have the user identifier as their superior from the user management table (FIG. 8). Next, the receipt acquisition unit 135 acquires the receipt information paired with the user identifier "U002" or "U082" and that Tanaka C should approve next, and the inspection results, from the receipt management table (FIG. 11). Next, the receipt acquisition unit 135 uses the acquired pair of receipt information and inspection results to construct receipt screen information to be sent to the terminal device 2. Next, the receipt transmission unit 142 sends the receipt screen information to the terminal device 2.

[0192] Next, the terminal device 2 receives the receipt screen information and outputs the receipt screen shown in Fig. 15. In Fig. 15, there is one receipt information to be approved.

[0193] Next, Tanaka C checks the approval box 1501 in FIG. 15 and presses the "send" button 1502.

[0194] Next, the terminal reception unit 22 of the terminal device 2 receives an approval instruction for the receipt information (receipt identifier "352"). The terminal processing unit 23 acquires the user identifier "U003" from the terminal storage unit 21 and creates approval information having the user identifier: "<Approver identifier>U003 <Applicant identifier>U002 <Receipt identifier>352 <Approval information>1". Next, the terminal transmission unit 24 transmits the approval instruction to the receipt processing device 1.

[0195] Next, the receiving unit 12 of the receipt processing device 1 receives the approval instruction including the approval information "1" from the terminal device 2. Next, the storage unit 134 changes the attribute value of the attribute "approval flag 1" in the receipt management table (FIG. 11), which is the approval information corresponding to the approver identifier "U002" and the receipt identifier "352", from "NULL (-)" to "1."

[0196] As described above, according to this embodiment, it is possible to flexibly handle duplicate registration of receipt information.

[0197] The processing in this embodiment may be realized by software. This software may be distributed by software download, etc. 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 receipt processing device 1 in this embodiment is the following program. In other words, this program causes a computer to function as a receipt receiving unit that receives a receipt image from a first terminal used by an applicant who applies for a receipt, a receipt composition unit that acquires receipt information based on the receipt image, an inspection unit that determines whether the receipt information is a duplicate registration, a storage unit that accumulates the receipt information acquired by the receipt composition unit and the inspection results acquired by the inspection unit in a receipt management unit where receipt information related to receipts is stored, an instruction receiving unit that receives an instruction to acquire receipt information from a second terminal used by an approver who approves the receipt, a receipt acquisition unit that acquires the receipt information and the inspection results corresponding to the acquisition instruction from the receipt management unit, and a receipt sending unit that transmits the receipt information and the inspection results acquired by the receipt acquisition unit to the second terminal.

[0198] 16 shows the appearance of a computer that executes the programs described herein to realize the receipt processing device 1 and other devices of the various embodiments described above. The above-described embodiments can be realized by computer hardware and a computer program executed thereon. FIG. 16 is an overview of this computer system 300, and FIG. 17 is a block diagram of the system 300.

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

[0200] 17, 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.

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

[0202] The program does not necessarily include an operating system (OS) or third-party programs that cause the computer 301 to execute the functions of the receipt processing device 1 of the above-described embodiment. The program need only 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 will be omitted.

[0203] 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).

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

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

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

[0207] 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]

[0208] As described above, the receipt processing device 1 according to the present invention has the effect of being able to flexibly process duplicate registration of receipt information, and is useful as a server or the like that processes receipt information. [Explanation of symbols]

[0209] A Receipt System 1. Receipt processing device 2. Terminal Device 11 Storage area 12 Receiving unit 13 Processing section 14 Transmitter 21 Terminal storage section 22 Terminal Reception 23 Terminal processing section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Unit 111 User Management Department 112 Route Management Department 113 Receipt Management Department 121 Receipt Receiving Department 122 Instruction receiving unit 131 Receipt component 132 Inspection Department 133 Judgment Department 134 Storage Unit 135 Receipt Acquisition Department 141 Test result transmission unit 142 Receipt Transmission Department 1321 First Inspection Method 1322 Secondary Inspection Method

Claims

1. an acquisition unit that acquires receipt information related to a receipt; an inspection unit that determines whether the receipt information is a duplicate registration; a receipt management unit that stores one or more receipt information items and a storage unit that stores the receipt information items acquired by the acquisition unit and the inspection results acquired by the inspection unit; The inspection unit a first inspection means for performing a first inspection as to whether the receipt information is a duplicate registration; a second inspection means for performing a second inspection on the receipt information other than the first inspection, the second inspection being an inspection on the validity of the receipt information; The storage unit is The receipt processing device stores the receipt information and the inspection results including type information that specifies the type of judgment that was inappropriate in the first inspection and the second inspection in the receipt management unit.

2. a route management unit that stores two or more pieces of route information corresponding to inspection results, the route information being route information that specifies the route for receipt approval; an instruction receiving unit that receives an instruction to acquire the receipt information from a second terminal used by an approver who approves the receipt; a receipt acquisition unit that acquires the receipt information and the inspection results corresponding to the acquisition instruction from the receipt management unit; a receipt transmitting unit that transmits the receipt information and the inspection result acquired by the receipt acquiring unit to the second terminal; The receipt sending unit 2. A receipt processing device as described in claim 1, wherein the receipt information and the inspection results are sent to the second terminal only when the instruction receiving unit receives the acquisition instruction from the second terminal of the approver corresponding to the route information according to the inspection results.

3. The receipt sending unit 2. A receipt processing device according to claim 1, wherein, when the inspection result includes information indicating invalidity, the receipt information may or may not be sent to the second terminal depending on the inspection result.

4. A receipt processing method comprising all of the processes performed by the receipt processing device according to any one of claims 1 to 3.

5. Computer, A program for causing the receipt processing device according to any one of claims 1 to 3 to function as the receipt processing device.

Images