Invoice processing device, invoice processing method, and program

Abstract

To provide a bill processing device, method and program capable of performing appropriate processing relating to a bill by using management information which associates a transmission source of the bill with the transmission destination.SOLUTION: A bill processing device 1 comprises: a management information storage unit 111 which stores one or more pieces of management information which associate a transmission source identifier identifying a transmission source of a bill with a transmission destination identifier identifying a transmission destination of the bill; a bill reception unit 121 which receives a new bill in which the transmission source identifier is associated with the transmission destination identifier; and a bill processing unit 131 which acquires the transmission source identifier and the transmission destination identifier that are associated with the bill received by the bill reception unit 121, and performs processing for the bill, by using the transmission source identifier and the transmission destination identifier. Thereby, appropriate processing relating to the bill can be performed.SELECTED DRAWING: Figure 2

Description

Technical Field

[0004] ,

[0006] , , , ,

[0005] , , , , ,

[0007] , , ,

[0001] The present invention relates to a claim processing apparatus that performs processing related to claims.

Background Art

[0002] Conventionally, there has been a claim data inspection support apparatus that reduces the operation cost of claim data management operations (see Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art, appropriate processing related to claims could not be performed using management information that associates the sender and recipient of a claim.

Means for Solving the Problems

[0005] The claim processing apparatus of the first invention includes a management information storage unit that stores one or more pieces of management information that associate a sender identifier for identifying the sender of a claim with a recipient identifier for identifying the recipient of the claim, a claim reception unit that receives a new claim in which the sender identifier and the recipient identifier are associated, and a claim processing unit that acquires the sender identifier and the recipient identifier associated with the claim received by the claim reception unit and performs processing on the claim using the sender identifier and the recipient identifier.

[0006] With such a configuration, appropriate processing related to claims can be performed using management information that associates the sender and recipient of a claim.

[0007] Furthermore, the invoice processing device of the second invention, compared to the first invention, is an invoice processing device that includes an accounting information output means which retrieves accounting information corresponding to an invoice that corresponds to a sender identifier and a recipient identifier associated with an invoice received by an invoice receiving unit from an accounting information storage unit which stores accounting information corresponding to one or more past invoices associated with one or more management information items, retrieves reusable information which is information of predetermined items from the accounting information, constructs accounting information using the reusable information, and outputs the accounting information.

[0008] This configuration allows for the efficient creation of accounting information corresponding to received invoices, using historical accounting information that corresponds to management information linking the sender and recipient of the received invoices.

[0009] Furthermore, the invoice processing device of this third invention is an invoice processing device in which the reusable information is accounting information, in contrast to the second invention.

[0010] This configuration allows for the acquisition of past journal entry information corresponding to management information that associates the sender and recipient of received invoices, and enables the efficient construction of accounting information that includes such journal entry information and corresponds to the received invoices.

[0011] Furthermore, the invoice processing device of this fourth invention is an invoice processing device that, compared to the first invention, associates deadline information that specifies the arrival deadline of the invoice with the management information stored in the management information storage unit.

[0012] This configuration allows for the management of invoice arrival deadlines based on invoice management information.

[0013] Furthermore, the invoice processing device of the fifth invention, compared to the fourth invention, is an invoice processing device that includes a deadline management means which determines whether or not the invoice receiving unit has received an invoice to which the sender identifier and recipient identifier corresponding to the deadline information have been associated by the arrival deadline specified by the deadline information, and performs processing according to the determination result.

[0014] With this configuration, it is possible to determine whether or not an invoice arrived by the due date by using deadline information that identifies the invoice's arrival date in the invoice management information.

[0015] Furthermore, the invoice processing device of the sixth invention, compared to the fifth invention, is an invoice processing device in which, when the invoice receiving unit receives an invoice with a sender identifier and a recipient identifier associated with the deadline information by the arrival deadline specified by the deadline information, performs a first notification process to inform the recipient identified by the recipient identifier that the invoice has been received.

[0016] With this configuration, if an invoice arrives by the due date for the invoice management information, the recipient of the invoice can be notified that the invoice has been received.

[0017] Furthermore, the invoice processing device of the seventh invention, compared to the fifth invention, is an invoice processing device in which, if the invoice receiving unit determines that it has not received an invoice with a sender identifier and recipient identifier associated with the deadline information by the arrival deadline specified by the deadline information, it performs a second notification process to inform the recipient identified by the recipient identifier that the invoice has not been received.

[0018] With this configuration, if an invoice does not arrive by the due date according to the invoice management information, the recipient of the invoice can be notified that the invoice has not been received.

[0019] Furthermore, the invoice processing device of the eighth invention, compared to the fifth invention, is an invoice processing device in which, if the invoice receiving unit determines that it has not received an invoice with a sender identifier and recipient identifier associated with the deadline information by the arrival deadline specified by the deadline information, it performs a third notification process to inform the sender identified by the sender identifier that the invoice has not been sent.

[0020] With such a configuration, when a bill does not arrive by the due date for the management information of the bill, information indicating that the bill has not been sent can be notified to the sender of the bill.

[0021] Further, in the bill processing apparatus of the ninth invention, with respect to the first invention, the bill processing unit uses the bill received by the bill reception unit, one or more past bills corresponding to the sender identifier and the recipient identifier corresponding to the bill, and performs an irregularity inspection on the bill received by the bill reception unit, and is a bill processing apparatus including irregularity inspection means for outputting inspection information regarding the result of the irregularity inspection.

[0022] With such a configuration, using the management information associating the sender and the recipient of the bill, an irregularity inspection of the received bill can be performed.

[0023] Further, in the bill processing apparatus of the tenth invention, with respect to the ninth invention, the irregularity inspection means compares one or more partial information constituting the bill received by the bill reception unit with one or more partial information constituting one or more past bills, determines whether the reception of the bill in the bill reception unit is a duplicate reception of a bill similar to the past bills, and outputs the determination result, and is a bill processing apparatus.

[0024] With such a configuration, using the management information associating the sender and the recipient of the bill, an irregularity inspection of duplicate registration of the received bill can be performed.

[0025] Further, in the bill processing apparatus of the eleventh invention, with respect to the ninth invention, the irregularity inspection means compares specific partial information constituting the bill received by the bill reception unit with specific partial information constituting one or more past bills, determines whether the bill received by the bill reception unit is an irregular bill, and outputs the determination result, and is a bill processing apparatus.

[0026] With such a configuration, using the management information associating the sender and the recipient of the bill, an irregularity inspection of transmission by an impersonator of the received bill can be performed.

[0027] Also, in the claim processing apparatus of the twelfth invention, with respect to the eleventh invention, the specific partial information is account information for specifying a transfer account, and the fraud detection means compares the account information constituting the claim received by the claim reception unit with the account information constituting one or more past claims, and when the account information is different, determines that the claim received by the claim reception unit is a fraudulent claim, and outputs a determination result. It is a claim processing apparatus.

[0028] With such a configuration, using the account information corresponding to the management information associating the sender and the recipient of the claim, it is possible to perform fraud detection of the transmission by the person who forged the received claim.

[0029] Also, in the claim processing apparatus of the thirteenth invention, with respect to the eleventh invention, the specific partial information is appearance information constituting the appearance of the claim, and the fraud detection means compares the appearance information constituting the claim received by the claim reception unit with the appearance information constituting one or more past claims, and when the appearance information is different, determines that the claim received by the claim reception unit is a fraudulent claim, and outputs a determination result. It is a claim processing apparatus.

[0030] With such a configuration, using the appearance information of the claim corresponding to the management information associating the sender and the recipient of the claim, it is possible to perform fraud detection of the transmission by the person who forged the received claim.

Effect of the Invention

[0033] The following describes embodiments of the invoice processing device and the like with reference to the drawings. Note that components denoted by the same reference numerals in the embodiments perform similar operations, and therefore, further explanation may be omitted.

[0034] (Embodiment 1) In this embodiment, we will describe an invoice processing system that includes an invoice processing device that performs predetermined processing related to invoices using management information that manages the correspondence between the sender and recipient of an invoice.

[0035] Furthermore, this embodiment describes an invoice processing system that includes an invoice processing device that acquires reusable information from past invoices paired with management information corresponding to received invoices, and promotes the accumulation of accounting information using such information. The reusable information is, for example, journal entry information.

[0036] Furthermore, in this embodiment, the invoice arrival deadline is managed in association with management information, and an invoice processing system is described that includes an invoice processing device that performs processing related to the invoice using the said arrival deadline. The processing related to the invoice is, for example, a process of notifying that the invoice has not arrived by the arrival deadline.

[0037] Furthermore, this embodiment describes an invoice processing system that includes an invoice processing device that performs fraud detection of invoices using management information corresponding to received invoices and information on past invoices paired with that information. Fraud detection includes, for example, detection of duplicate registrations and detection of the possibility of impersonation.

[0038] In this specification, information A being associated with information B means that information B can be obtained from information A, and / or information A can be obtained from information B. Information A being associated with information B may mean that information A contains information B, information B contains information A, information A and information B are linked, or information A and information B are contained in the same variable or the same array, etc. The structure of such information A and information B is irrelevant.

[0039] Figure 1 is a conceptual diagram of the invoice processing system A in this embodiment. The invoice processing system A comprises an invoice processing device 1 and one or more terminal devices 2. The invoice processing device 1 is a so-called server.

[0040] Invoice processing device 1 is a device that receives invoices and processes them. Invoice processing device 1 can be, for example, a cloud server or an ASP server, but the type is not limited.

[0041] Terminal device 2 is a device used by users who send or receive invoices. Terminal device 2 can be a personal computer, smartphone, or tablet, but the type is not limited.

[0042] Figure 2 is a block diagram of the invoice processing system A in this embodiment. The invoice processing device 1 comprises a storage unit 11, a receiving unit 12, a processing unit 13, and a transmission unit 14. The storage unit 11 comprises a management information storage unit 111 and an accounting information storage unit 112. The receiving unit 12 comprises an invoice receiving unit 121. The processing unit 13 comprises an invoice processing unit 131. The invoice processing unit 131 comprises an accounting information output means 1311, a deadline management means 1312, and a fraud detection means 1313.

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

[0044] The storage unit 11, which constitutes the invoice processing device 1, stores various types of information. These types of information include, for example, management information and accounting information, which will be described later.

[0045] The management information storage unit 111 stores one or more pieces of management information. Management information is information that manages the connection between the sender and recipient of an invoice. Management information can also be called connection information. Management information is information that associates a sender identifier with a recipient identifier. For example, management information includes a sender identifier and a recipient identifier.

[0046] The sender identifier is information that identifies the sender of the invoice. The sender of the invoice is the party that issues the invoice. It can also be thought of as information that identifies the issuer of the invoice. The sender identifier is preferably information that identifies the individual (person in charge) of the sender of the invoice, but it can also be information that identifies the organization of the sender. Examples of sender identifiers include the company name and person in charge of the issuer of the invoice, the company name and department name of the issuer of the invoice, the company identifier and person in charge identifier of the issuer of the invoice, and the company identifier and department identifier of the issuer of the invoice. The sender identifier is preferably the email address of the person in charge at the company that issued the invoice. However, the sender identifier can also be the phone number or ID of the person in charge at the company that issued the invoice.

[0047] The recipient identifier is information that identifies the recipient of the invoice. The recipient of the invoice is, in other words, the billing party. It can also be thought of as information that identifies the party being billed. While it is preferable for the recipient identifier to identify an individual (contact person) at the invoice recipient's address, it may also identify the organization at the invoice recipient's address. Examples of recipient identifiers include the company name and contact person's name, the company name and department name, the company identifier and contact person's identifier, and the company identifier and department identifier. Ideally, the recipient identifier should be the email address of the contact person at the company receiving the invoice. However, it may also be the phone number or ID of the contact person at the company receiving the invoice.

[0048] Each of the one or more management information entries in the management information storage unit 111 is associated with, for example, deadline information. The deadline information is information that specifies the arrival deadline for the invoice. The information that specifies the deadline may also be information that specifies the arrival time. The arrival time may be the arrival date or the arrival period. Examples of deadline information include "October 29, 2021", "the end of each month", and "the 1st of each month".

[0049] The accounting information storage unit 112 stores one or more accounting information. Each of the one or more accounting information in the accounting information storage unit 112 is associated with management information. This accounting information corresponds to accounting information for invoices issued in the past. The accounting information may consist only of invoice information.

[0050] Accounting information is information that corresponds to an invoice. It is preferable for accounting information to include an invoice. An invoice, for example, includes recipient information indicating the recipient of the invoice, amount information indicating the amount to be invoiced, date information indicating the invoice issuance date, and recipient information indicating the address to which the invoice will be sent.

[0051] Accounting information typically includes journal entries. Journal entries are information that identifies a journal entry. Journal entries are information that identifies an account. Examples of journal entries include "consumable supplies," "employee welfare expenses," "communication expenses," "advertising and promotion expenses," and "outsourcing expenses."

[0052] The reception unit 12 receives various types of information and instructions. These types of information and instructions include, for example, invoices, output instructions, and management information.

[0053] An output instruction is an instruction to output information. This information could be, for example, an invoice or accounting information. An output instruction might include, for example, conditions for searching for an invoice or accounting information.

[0054] The input methods for various types of information and instructions can be anything, such as a touch panel, keyboard, mouse, or menu screen. The reception unit 12 can be implemented using device drivers for input methods such as touch panels and keyboards, or control software for menu screens.

[0055] Here, "reception" usually refers to the reception of information transmitted via wired or wireless communication lines, but it may also be a concept that includes the reception of information input from input devices such as keyboards, mice, and touch panels, as well as the reception of information read from recording media such as optical discs, magnetic discs, and semiconductor memory.

[0056] The invoice receiving unit 121 receives invoices. The invoices received are usually new invoices. New invoices are newly issued invoices. The invoices received by the invoice receiving unit 121 have a sender identifier and a recipient identifier associated with them. Also, the invoice here is electronic invoice information. The invoice may be an image, for example, but it may also be a set of strings that make up the invoice, or an image and a set of strings that make up the invoice, etc. The image is an image of the invoice, for example, a PDF file, a JPEG file, etc. In other words, the data structure of the electronic invoice or image is not specified. Electronic invoices can also be called invoice information.

[0057] The processing unit 13 performs various processes. These processes include, for example, those performed by the invoice processing unit 131.

[0058] The invoice processing unit 131 obtains the sender identifier and recipient identifier associated with the invoice received by the invoice receiving unit 121, and processes the invoice using the sender identifier and recipient identifier.

[0059] More specifically, the invoice processing unit 131 obtains the sender identifier and recipient identifier associated with the invoice received by the invoice receiving unit 121. Next, for example, the invoice processing unit 131 obtains management information corresponding to the obtained sender identifier and recipient identifier from the management information storage unit 111. Next, for example, the invoice processing unit 131 processes the invoice using the information corresponding to the management information.

[0060] The information corresponding to the management information includes, for example, deadline information, invoices, and accounting information. The processing of invoices includes, for example, the accounting information output processing, the notification processing, and the fraud detection processing, which will be described later.

[0061] The accounting information output means 1311, which constitutes the invoice processing unit 131, performs accounting information output processing. Specifically, the accounting information output means 1311 obtains accounting information corresponding to the invoices corresponding to the sender identifier and recipient identifier attached to the invoices received by the invoice receiving unit 121 from the accounting information storage unit 112, obtains one or more reusable pieces of information from the accounting information, constructs accounting information using the reusable pieces of information, and outputs the accounting information.

[0062] More specifically, the accounting information output means 1311 obtains the sender identifier and recipient identifier associated with the invoice received by the invoice receiving unit 121. Next, for example, the accounting information output means 1311 obtains accounting information from the accounting information storage unit 112 that corresponds to the management information that associates the obtained sender identifier and recipient identifier. Next, for example, the accounting information output means 1311 obtains one or more reusable pieces of information from the accounting information. Next, for example, the accounting information output means 1311 obtains one or more original pieces of information from the invoice received by the invoice receiving unit 121. Next, for example, the accounting information output means 1311 constructs accounting information having the one or more reusable pieces of information obtained and the one or more original pieces of information obtained. Next, the accounting information output means 1311 outputs the constructed accounting information. In other words, such accounting information is information constructed using at least a portion of past accounting information that corresponds to the management information associated with the invoice received by the invoice receiving unit 121.

[0063] Furthermore, reusable information is information obtained from past accounting records and is therefore reusable. Reusable information is information within accounting records and consists of predetermined items.

[0064] Reusable information includes, for example, accounting entries. This type of reusable information utilizes the fact that if the sender and recipient of an invoice are the same, the corresponding accounting entries for that invoice are often the same.

[0065] Reusable information includes, for example, summary information. This reused information takes advantage of the fact that if the sender and recipient of an invoice are the same, the summary information of the corresponding accounting information is often the same.

[0066] Reusable information includes, for example, extended fields and expense allocation. Extended fields, in this context, are information that constitutes accounting information and can be freely entered by the user. Expense allocation refers to information regarding the allocation of billing expenses. For example, expense allocation refers to information regarding the allocation ratio when billing expenses are allocated among two or more departments.

[0067] The source information is the information contained in the invoice and forms the basis of the accounting information. Examples of source information include recipient information, delivery address information, amount information, and date information. Amount information is the information that identifies the invoiced amount.

[0068] Here, "output" refers to, for example, transmission to terminal device 2 or storage on a recording medium, but it may also be a concept that includes display on a screen, projection using a projector, printing with a printer, transmission to other external devices, and delivery of processing results to other processing devices or other programs. Note that transmission to terminal device 2 could be terminal device 2 that sent the invoice, or terminal device 2 that receives the invoice and is the recipient terminal device.

[0069] The deadline management means 1312 determines whether the invoice receiving unit 121 has received an invoice with the sender identifier and recipient identifier corresponding to the deadline information by the arrival deadline specified by the deadline information paired with the management information, and processes accordingly based on the result of that determination. The determination result may be, for example, "information indicating that the invoice did not arrive by the arrival deadline specified by the deadline information" or "information indicating that the invoice arrived by the arrival deadline specified by the deadline information."

[0070] The deadline management means 1312 performs a first notification process to inform the recipient identified by the recipient identifier that the invoice has been received, for example, when the invoice receiving unit 121 receives an invoice with a sender identifier and recipient identifier associated with the deadline information, by the arrival deadline specified by the deadline information paired with the management information.

[0071] The first notification process is, for example, sending an email to the email address indicated by the recipient identifier informing the recipient that the invoice has been received. The first notification process is, for example, writing the information that the invoice has been received to the recording area indicated by the recipient identifier. The recording area indicated by the recipient identifier is a recording area that can be viewed by the user (person in charge) identified by the recipient identifier. This recording area may reside in the storage unit 11 or in another device.

[0072] For example, if the deadline management means 1312 determines that the invoice receiving unit 121 has not received the invoice associated with the sender identifier and recipient identifier corresponding to the deadline information by the arrival deadline specified by the deadline information paired with the management information, it performs a second notification process to inform the recipient identified by the recipient identifier that the invoice has not been received.

[0073] The second notification process involves, for example, sending an email to the email address indicated by the recipient identifier stating that the invoice has not been received. The second notification process also involves, for example, writing information indicating that the invoice has not been received to the record area indicated by the recipient identifier.

[0074] For example, if the deadline management means 1312 determines that the invoice receiving unit 121 has not received an invoice with a sender identifier and recipient identifier associated with the deadline information by the arrival deadline specified by the deadline information paired with the management information, it performs a third notification process to inform the sender identified by the sender identifier that the invoice has not been sent.

[0075] The third notification process involves, for example, sending an email to the email address indicated by the sender identifier stating that the invoice has not been received. The third notification process also involves, for example, writing the information that the invoice has not been received to the recording area indicated by the sender identifier. The recording area indicated by the sender identifier is a recording area that can be viewed by the user (person in charge) identified by the sender identifier. This recording area may reside in the storage unit 11 or in another device.

[0076] Furthermore, the content and data structure of information regarding whether an invoice has been received or not are not relevant. Also, information regarding whether an invoice has been received or not can be considered notification information.

[0077] The fraud detection means 1313 performs fraud detection processing. Specifically, the fraud detection means 1313 uses, for example, the invoice received by the invoice receiving unit 121 and one or more past invoices corresponding to the sender identifier and recipient identifier corresponding to the invoice to perform fraud detection on the invoice received by the invoice receiving unit 121, and outputs inspection information regarding the results of the fraud detection. The inspection information includes, for example, information indicating that it is fraudulent, information indicating the nature of the fraud, and the invoice that was determined to be fraudulent. "Fraudulent" may also mean that there is a possibility of fraud.

[0078] The output of inspection information includes, for example, the transmission of inspection information to the terminal device 2 that sent the invoice received by the invoice receiving unit 121, the transmission of inspection information to the terminal device 2 of the recipient identified by the recipient identifier paired with the invoice received by the invoice receiving unit 121, and the storage of inspection information on a recording medium.

[0079] More specifically, the fraud detection means 1313 obtains, for example, an invoice received by the invoice receiving unit 121, along with the sender identifier and recipient identifier corresponding to that invoice. Next, the fraud detection means 1313 obtains, for example, one or more past invoices corresponding to the said sender identifier and recipient identifier. Normally, the fraud detection means 1313 obtains one or more past invoices from the accounting information storage unit 112, but it may also obtain them from other storage areas or other devices. Next, the fraud detection means 1313 compares, for example, at least a portion of the information from the one or more past invoices obtained with at least a portion of the information from the invoice received by the invoice receiving unit 121, and uses the comparison result to obtain inspection information regarding the results of the fraud detection and outputs the inspection information.

[0080] The fraud detection method 1313 performs, for example, (1) duplicate registration checks and (2) impersonation checks, as described below. In the case of impersonation checks, impersonation may only be as simple as the possibility of an improper invoice. (1) Duplicate registration check

[0081] The fraud detection means 1313 compares one or more partial pieces of information that constitute an invoice received by the invoice receiving unit 121 with one or more partial pieces of information that constitute one or more past invoices, determines whether the invoice received by the invoice receiving unit 121 is a duplicate invoice similar to a past invoice, and outputs the determination result.

[0082] More specifically, for example, the fraud detection means 1313 compares one or more partial pieces of information constituting an invoice received by the invoice receiving unit 121 with one or more partial pieces of information constituting one or more past invoices. If all the partial pieces of information are the same, it determines that the invoice has been received twice and outputs the result. Alternatively, for example, the fraud detection means 1313 compares one or more partial pieces of information constituting an invoice received by the invoice receiving unit 121 with one or more partial pieces of information constituting one or more past invoices, obtains the matching rate, and if the matching rate is above a threshold, it determines that the invoice has been received twice and outputs the result. Alternatively, for example, the fraud detection means 1313 compares one or more partial pieces of information constituting an invoice received by the invoice receiving unit 121 with one or more partial pieces of information constituting one or more past invoices received within a threshold time (or within a threshold number of days) from the date of receipt, obtains the matching rate, and if the matching rate is above a threshold, it determines that the invoice has been received twice and outputs the result. (2) Impersonation testing

[0083] The fraud detection means 1313 compares specific partial information constituting the invoice received by the invoice receiving unit 121 with specific partial information constituting one or more past invoices to determine whether the invoice received by the invoice receiving unit 121 is fraudulent and outputs the determination result. The specific partial information may include, for example, account information and appearance information.

[0084] The fraud detection means 1313, for example, compares the account information constituting the invoice received by the invoice receiving unit 121 with the account information constituting one or more past invoices. If the two sets of account information are different, the invoice receiving unit 121 determines that the invoice received is fraudulent and outputs the determination result.

[0085] The fraud detection means 1313 compares, for example, the appearance information of an invoice received by the invoice receiving unit 121 with the appearance information of one or more past invoices. If the two sets of appearance information differ, the invoice receiving unit 121 determines that the invoice received is fraudulent and outputs the result. The appearance information is the information that constitutes the appearance of the invoice. The appearance information includes, for example, the upper part of the claim image (for example, the part above the threshold at the top of the image (top 10%)), the lower part of the claim image (for example, the part above the threshold at the bottom of the image (bottom 20%)), and the entire invoice image (which may be a PDF file, etc.). The fraud detection means 1313 also calculates the similarity between the image of the invoice received by the invoice receiving unit 121 and the image of one or more past invoices. It determines whether the similarity is below or less than the threshold, and if the similarity is below or less than the threshold, the received invoice is deemed fraudulent and outputs the result.

[0086] The transmitting unit 14 transmits various types of information to the terminal device 2. For example, the transmitting unit 14 transmits information that an invoice has been received to the terminal device 2 that sent the invoice. The transmitting unit 14 also transmits information that an invoice has been received to the terminal device 2 identified by the recipient identifier corresponding to the invoice. Transmitting to the terminal device 2 can be done, for example, by sending an email, but it is also possible to write the information to a memory area corresponding to the terminal device 2 and transmit the information from the memory area to the terminal device 2 in response to access from the terminal device 2.

[0087] The terminal storage unit 21, which constitutes the terminal device 2, stores various types of information. These types of information include, for example, a sender identifier, a recipient identifier, and an invoice.

[0088] The terminal reception unit 22 receives various types of information and instructions. These include, for example, a URI or URL for accessing a website for invoice entry, instructions to launch an invoice entry application, instructions to launch an email application, invoice information, management information, and output instructions. The invoice entry application is an application for entering invoice information. The email application is an application for sending emails.

[0089] Here, "reception" is a concept that includes receiving information input from input devices such as keyboards, mice, and touch panels; receiving information transmitted via wired or wireless communication lines; and receiving information read from recording media such as optical discs, magnetic discs, and semiconductor memory.

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

[0091] The terminal processing unit 23 performs various processes. These processes include, for example, converting received information and instructions into information and instructions for transmission. Other processes include, for example, converting received information into information for output.

[0092] The terminal transmission unit 24 transmits various information and instructions to the invoice processing device 1. These various information and instructions include, for example, invoices, emails, output instructions, and management information.

[0093] The terminal receiving unit 25 receives various types of information from the invoice processing device 1. These types of information include, for example, invoices, accounting information, and notification information.

[0094] The terminal output unit 26 outputs various types of information. These types of information include, for example, invoices, accounting information, and notification information.

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

[0096] The storage unit 11, the management information storage unit 111, the accounting information storage unit 112, and the terminal storage unit 21 are preferably made of non-volatile recording media, but can also be made of volatile recording media.

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

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

[0099] The processing unit 13, invoice processing unit 131, accounting information output means 1311, deadline management means 1312, fraud detection means 1313, and terminal processing unit 23 can typically be implemented using a processor, memory, etc. The processing procedures of the processing unit 13, etc., are typically implemented in software, and this software is recorded on a recording medium such as ROM. However, it may also be implemented in hardware (dedicated circuitry). The processor can be a CPU, MPU, GPU, etc., and the type is not limited.

[0100] The transmitting unit 14 and the terminal transmitting unit 24 are usually implemented by wireless or wired communication means, but may also be implemented by broadcasting means.

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

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

[0103] Next, we will explain an example of the operation of the invoice processing system A. First, we will explain an example of the operation of the invoice processing device 1 using the flowchart in Figure 3.

[0104] (Step S301) The invoice receiving unit 121 determines whether or not it has received an invoice from the terminal device 2. If an invoice has been received, the process proceeds to step S302; otherwise, the process proceeds to step S303.

[0105] (Step S302) The invoice processing unit 131 processes the invoice using the invoice received in step S301. The process returns to step S301. An example of invoice processing will be explained using the flowchart in Figure 4.

[0106] (Step S303) The reception unit 12 determines whether or not it has received an output instruction from the terminal device 2. If an output instruction is received, the process proceeds to step S304; if no output instruction is received, the process proceeds to step S306.

[0107] (Step S304) The processing unit 13 obtains one or more accounting information items corresponding to the output instruction received in step S303 from the accounting information storage unit 112.

[0108] (Step S305) The transmission unit 14 transmits one or more accounting information obtained in step S304 to the terminal device 2 that sent the output instruction. The process returns to step S301.

[0109] (Step S306) The reception unit 12 determines whether or not it has received management information from the terminal device 2. If it has received management information, it proceeds to step S307; if it has not received management information, it proceeds to step S308. The terminal device 2 that transmits the management information is, for example, the terminal of the operator of the invoice processing device 1.

[0110] (Step S307) The processing unit 13 stores the management information received in step S306 in the management information storage unit 111. Return to step S301.

[0111] (Step S308) The reception unit 12 determines whether or not it has received deadline information from the terminal device 2, in association with the management information. If deadline information is received, the unit proceeds to step S309; ​​otherwise, the unit proceeds to step S310. The terminal device 2 that transmits the deadline information may be a terminal used by the user sending the invoice, a terminal used by the user receiving the invoice, or a terminal operated by the operator of the invoice processing device 1.

[0112] (Step S309) The processing unit 13 stores the expiration date information received in step S308 in the management information storage unit 111, paired with the management information corresponding to the expiration date information. The process returns to step S301.

[0113] (Step S310) The processing unit 13 determines whether or not it is time to perform an expiration check. If it is time to perform an expiration check, it proceeds to step S311; otherwise, it returns to step S301. Note that the timing for performing an expiration check is usually predetermined, for example, at 12:00 every day, or at 0:00 every Monday, and the exact timing is not considered.

[0114] (Step S311) The expiration date management means 1312 performs an expiration date inspection process. Return to step S301. An example of the expiration date inspection process will be explained using the flowchart in Figure 6.

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

[0116] Next, an example of invoice processing in step S302 will be explained using the flowchart in Figure 4.

[0117] (Step S401) The fraud detection means 1313 performs fraud detection processing on the received invoice. An example of fraud detection processing will be explained using the flowchart in Figure 5.

[0118] (Step S402) The invoice processing unit 131 determines whether the result of the fraud check process in step S401 was "fraudulent" or "legitimate". If it is "legitimate", proceed to step S403; if it is fraudulent, proceed to step S411.

[0119] (Step S403) The accounting information output means 1311 acquires management information corresponding to the received invoice. It does not matter how the management information is associated with the received invoice.

[0120] (Step S404) The accounting information output means 1311 obtains accounting information from the accounting information storage unit 112 that corresponds to the management information obtained in step S403. Preferably, such accounting information is representative accounting information among the accounting information that corresponds to the management information. Representative accounting information is, for example, the latest accounting information in the accounting information storage unit 112, or accounting information to which a flag indicating that it is representative accounting information is attached.

[0121] (Step S405) The accounting information output means 1311 retrieves one or more reusable pieces of information from the accounting information obtained in step S404. The one or more pieces of reusable information may be, for example, journal entry information or extended items.

[0122] (Step S406) The accounting information output means 1311 obtains one or more pieces of raw information that constitute accounting information from the received invoice. The one or more pieces of raw information are, for example, the date, account information, and invoice amount.

[0123] (Step S407) The accounting information output means 1311 constitutes accounting information having one or more reusable pieces of information obtained in step S405 and one or more original pieces of information obtained in step S406.

[0124] (Step S408) The accounting information output means 1311 transmits, for example, the accounting information configured in step S407 to the terminal device 2 that sent the invoice. The accounting information output means 1311 may also transmit, for example, the accounting information configured in step S407 to the destination terminal device 2 identified by the destination identifier paired with the invoice. Such transmission is for the purpose of confirming the stored accounting information. The accounting information output means 1311 may also store the received invoice and the configured accounting information in the accounting information storage unit 112.

[0125] (Step S409) The accounting information output means 1311 determines whether or not it has received accounting information to be stored from the terminal device 2. If accounting information has been received, the process proceeds to step S410; otherwise, it returns to step S409. The accounting information to be stored may be the same as the accounting information transmitted in step S408, or it may be information that has been partially corrected by the user.

[0126] (Step S410) The accounting information output means 1311 stores the accounting information received in step S409 in the accounting information storage unit 112, pairing it with the management information that corresponds to the received invoice. Then it returns to the higher-level processing.

[0127] (Step S411) The invoice processing unit 131 sends a message to the terminal device 2 that sent the invoice, indicating that the transmitted invoice is fraudulent. The invoice processing unit 131 may also send information to the recipient identified by the recipient identifier paired with the transmitted invoice, indicating that a fraudulent invoice has been sent. The process returns to the higher level.

[0128] Next, an example of the fraud detection process in step S401 will be explained using the flowchart in Figure 5.

[0129] (Step S501) The fraud detection means 1313 obtains the management information that is paired with the received invoice.

[0130] (Step S502) The fraud detection means 1313 retrieves an invoice from the accounting information storage unit 112 that corresponds to the management information obtained in step S501. Preferably, such an invoice is a representative invoice among the invoices that correspond to the management information. A representative invoice is, for example, a recent invoice among the invoices that correspond to the management information.

[0131] (Step S503) The fraud detection means 1313 retrieves one or more partial pieces of information from the invoice obtained in step S502. These one or more pieces of information may be, for example, account information and address.

[0132] (Step S504) The fraud detection means 1313 assigns 1 to counter i.

[0133] (Step S505) The fraud detection means 1313 determines whether or not the i-th partial information exists in the partial information obtained in step S503. If the i-th partial information exists, the process proceeds to step S506; otherwise, the process proceeds to step S510.

[0134] (Step S506) The fraud detection means 1313 obtains information (partial information) of the same item as the i-th partial information from the received invoice.

[0135] (Step S507) The fraud detection means 1313 determines whether the i-th partial information and the partial information obtained in step S505 have a predetermined relationship. If the two partial information items have a predetermined relationship, the process proceeds to step S508; otherwise, the process proceeds to step S509. The predetermined relationship is, for example, a match, a difference within a threshold, etc. The predetermined relationship may also differ for each item. For example, the predetermined relationship for account information may be "match," and the predetermined relationship for billing amount may be "a difference within a threshold," etc.

[0136] (Step S508) The fraud detection means 1313 increments counter i by 1. Return to step S505.

[0137] (Step S509) The fraud detection means 1313 assigns "fraudulent" to the result of the fraud detection. It returns to the higher-level process.

[0138] (Step S510) The fraud detection means 1313 obtains the appearance information of past invoices obtained in step S502.

[0139] (Step S511) The fraud detection means 1313 obtains the appearance information of the received invoice.

[0140] (Step S512) The fraud detection means 1313 compares the appearance information obtained in step S510 with the appearance information obtained in step S511.

[0141] (Step S513) The fraud detection means 1313 determines, based on the comparison in step S512, whether the appearance of the received invoice is the same as the appearance of past invoices. If they are the same, the process proceeds to step S514; otherwise, the process proceeds to step S515. Note that the appearance being the same means, for example, that the two appearance information items are identical or their similarity is within a threshold.

[0142] (Step S514) The fraud detection means 1313 substitutes "legitimate" for the result of the fraud detection. It returns to the higher-level process.

[0143] (Step S515) The fraud detection means 1313 assigns "fraudulent" to the result of the fraud detection. It returns to the higher-level process.

[0144] Next, an example of the expiration date check process in step S311 will be explained using the flowchart in Figure 6.

[0145] (Step S601) The expiration date management means 1312 assigns 1 to counter i.

[0146] (Step S602) The deadline management means 1312 determines whether or not the i-th management information exists in the management information storage unit 111. If the i-th management information exists, the process proceeds to step S603; otherwise, the process returns to the higher-level processing.

[0147] (Step S603) The deadline management means 1312 determines whether or not deadline information exists in association with the i-th management information. If deadline information exists, proceed to step S604; otherwise, proceed to step S609.

[0148] (Step S604) The deadline management means 1312 obtains the deadline information corresponding to the i-th management information from the management information storage unit 111.

[0149] (Step S605) The deadline management means 1312 obtains today's date from a clock or calendar (not shown). The deadline management means 1312 determines whether today is past the deadline indicated by the deadline information obtained in step S604. If it is past the deadline, proceed to step S606; otherwise, proceed to step S609.

[0150] (Step S606) The deadline management means 1312 determines whether an invoice corresponding to the i-th management information and the deadline indicated by the deadline information exists in the accounting information storage unit 112. If such an invoice exists, proceed to step S607; otherwise, proceed to step S607.

[0151] (Step S607) The deadline management means 1312 obtains notification information that the invoice has not been received. Preferably, such notification information includes, for example, the sender identifier and recipient identifier of the i-th management information. Preferably, such notification information includes information that can identify the invoice that should be received.

[0152] (Step S608) The deadline management means 1312 transmits the notification information acquired in step S607 to the user identified by the sender identifier in the i-th management information. The deadline management means 1312 also transmits the notification information acquired in step S607 to the user identified by the recipient identifier in the i-th management information. Note that the deadline management means 1312 may transmit the notification information to either the user identified by the sender identifier or the user identified by the recipient identifier.

[0153] (Step S609) The expiration management means 1312 increments the counter i by 1. Return to step S602.

[0154] Next, an example of the operation of terminal device 2 will be explained using the flowchart in Figure 7.

[0155] (Step S701) The terminal receiving unit 22 determines whether or not it has received the instruction to send the invoice. If it has received the instruction to send the invoice, it proceeds to step S702; otherwise, it proceeds to step S703. The instruction to send the invoice includes, for example, the invoice, a recipient identifier, and a sender identifier.

[0156] (Step S702) The terminal processing unit 23 configures the invoice to be sent by associating the recipient identifier with the sender identifier, in accordance with the transmission instruction received in step S701. The terminal transmission unit 24 transmits the invoice to the invoice processing unit 1 by associating the recipient identifier with the sender identifier. The process returns to step S701.

[0157] (Step S703) The terminal reception unit 22 determines whether or not it has received an output instruction. If it has received an output instruction, it proceeds to step S704; otherwise, it proceeds to step S707.

[0158] (Step S704) The terminal processing unit 23 configures the output instruction to be transmitted. The terminal transmission unit 24 transmits the output instruction to the invoice processing unit 1.

[0159] (Step S705) The terminal receiving unit 25 determines whether it has received one or more accounting information corresponding to the output instruction. If it has received one or more accounting information, it proceeds to step S706; otherwise, it returns to step S705.

[0160] (Step S706) The terminal processing unit 23 uses one or more accounting information received in step S705 to configure the accounting information to be output. The terminal output unit 26 outputs the configured one or more accounting information. The process returns to step S701.

[0161] (Step S707) The terminal receiving unit 25 determines whether or not it has received notification information. If it has received notification information, it proceeds to step S708; otherwise, it proceeds to step S709.

[0162] (Step S708) The terminal processing unit 23 uses the broadcast information received in step S707 to configure the broadcast information to be output. The terminal output unit 26 outputs the configured broadcast information. The process returns to step S701.

[0163] (Step S709) The terminal receiving unit 25 determines whether or not it has received accounting information for pre-registration verification. If accounting information has been received, the process proceeds to step S710; otherwise, the process returns to step S701.

[0164] (Step S710) The terminal processing unit 23 uses the received accounting information to configure the accounting information to be output. The terminal output unit 26 outputs the accounting information.

[0165] (Step S711) The terminal reception unit 22 determines whether or not it has accepted the request to edit the output accounting information. If the edit has been accepted, the process proceeds to step S712; otherwise, the process proceeds to step S713.

[0166] (Step S712) The terminal processing unit 23 modifies the output accounting information according to the edit. Return to step S711.

[0167] (Step S713) The terminal processing unit 23 determines whether or not to transmit accounting information. If accounting information is to be transmitted, the process proceeds to step S714; otherwise, it returns to step S711. Note that accounting information is to be transmitted if, for example, an instruction to transmit accounting information has been received.

[0168] (Step S714) The terminal transmission unit 24 associates the output accounting information with the management information and transmits it to the invoice processing device 1. Return to step S701.

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

[0170] The specific operation of the invoice processing system A in this embodiment will be described below.

[0171] Currently, the management information storage unit 111 of the invoice processing device 1 stores the management information management table shown in Figure 8. The management information management table contains "ID", "Sender Identifier", "Recipient Identifier", "Sender Email Address", "Recipient Email Address", "Recipient Contact Person Email Address", and "Due Date Information". The "Sender Email Address" is the email address of the person sending the invoice by email. The "Recipient Email Address" is the email address to which the invoice will be sent when sent by email. The "Recipient Contact Person Email Address" is the email address of the person in charge at the recipient to be notified when the invoice is accepted. Note that the "Sender Email Address" can also be considered as the sender identifier. Alternatively, the "Recipient Email Address" or "Recipient Contact Person Email Address" can be considered as the recipient identifier. In this case, the "Sender Identifier" includes "Company" and "Contact Person". In this case, the "Recipient Identifier" includes "Company" and "Contact Person". Furthermore, records with and without "Due Date Information" may be mixed.

[0172] The accounting information storage unit 112 stores the accounting information management table shown in Figure 9. The accounting information management table is a table that manages accounting information, including invoices. The accounting information management table manages records that have "ID", "Invoice", "Sender Identifier", "Recipient Identifier", "Date", "Account", "Account Information", "Invoice Amount", "Extended Items", and "Expense Allocation". "ID" is information that identifies the record. "Invoice" is assumed to be a PDF file of the invoice. "Sender Identifier" has "Company" and "Contact Person". "Company" is information that identifies the organization (company, sole proprietor, government office, etc.) that sent the invoice information, and in this case, it is the company name. "Contact Person" is information that identifies the contact person at the organization that sent the invoice information, and in this case, it is the contact person's name. "Recipient Identifier" has "Company" and "Contact Person". "Company" is information that identifies the organization (company, sole proprietor, government office, etc.) that received the invoice information, and in this case, it is the company name. "Contact Person" is information that identifies the contact person at the organization that received the invoice information, and in this case, it is the contact person's name. "Date" is the date the invoice was received. Note that "Date" can be the invoice issuance date. "Account Information" is the account information of the sender of the invoice. "Account Information" is the account information entered by the recipient for the amount of the invoice. "Account Information" here refers to bank account information and usually includes the bank name, account number, etc. "Invoiced Amount" is the amount to be invoiced.

[0173] In this context, the following four specific examples will be explained. Specific example 1 is the case where reusable information (in this case, journal entry information, etc.) is suggested from past accounting information. Specific example 2 is an example of how to handle the case where an invoice does not arrive after the due date. Specific example 3 is an example of how to check for duplicate invoice entries. Specific example 4 is an example of how to check for incorrect account information on an invoice.

[0174] (Specific example 1) Let's assume that user "Yamada Aiko" (hereinafter referred to as "the user") accessed a website to enter invoice information. Such access is based on entering the URL of the website. The server for the website is, for example, Invoice Processing Unit 1.

[0175] Then, the screen shown in Figure 10 is displayed on the user's terminal device 2. The user then imports a PDF file of the invoice they wish to send. This imported invoice file is named 1001. The user then enters the sender identifier 1002 and recipient identifier 1003 of the invoice on the screen shown in Figure 10. The terminal reception unit 22 then accepts the input of invoice information 1001 (PDF file of the invoice), sender identifier 1002, and recipient identifier 1003.

[0176] Next, suppose the user presses the send button 1004 in Figure 10. Then, the terminal processing unit 23 uses the received invoice to compose the invoice to be sent. Next, the terminal transmission unit 24 sends the invoice to the invoice processing device 1.

[0177] Furthermore, the invoice, etc., shall include, in addition to invoice 1001, the sender identifier "<Company> Company A <Contact Person> Yamada Aiko" and the recipient identifier "<Company> Company X <Contact Person> Tanaka Eiko".

[0178] Next, the invoice receiving unit 121 of the invoice processing device 1 receives invoice information 1101, sender identifier 1102, and recipient identifier 1103 from the user's terminal device 2.

[0179] Furthermore, the route by which terminal device 2 sends invoices, etc., is not limited to email; it may also be via the web. Also, the screen for sending invoices, etc., is not limited to the screen shown in Figure 10.

[0180] Next, the invoice processing unit 131 processes the received invoice as follows: The fraud detection means 1313 of the invoice processing unit 131 performs fraud detection processing and obtains the result "legitimate".

[0181] Next, the accounting information output means 1311 obtains management information corresponding to the received invoice (sender identifier "<Company> Company A <Contact Person> Yamada Aiko", recipient identifier "<Company> Company X <Contact Person> Tanaka Eiko").

[0182] Next, the accounting information output means 1311 retrieves the accounting information "ID=58", which is the accounting information that corresponds to the acquired management information, from the accounting information management table (Figure 9). Note that the accounting information retrieved here does not necessarily have to be all the attribute values ​​that make up the accounting information; it may be only some of the attribute values.

[0183] Next, the accounting information output means 1311 retrieves reusable information from the acquired accounting information, such as the account "Outsourcing Expenses," the extended item "Automatic Set, A1000," and the expense allocation "Department 1=1 Department 2=2 Department 3=1." In this case, expense allocation is information that shows the ratio when the billed expenses are allocated among two or more departments. The expense allocation "Department 1=1 Department 2=2 Department 3=1" indicates that Department 1, Department 2, and Department 3 will bear the billed amount in a ratio of "1:2:1."

[0184] Next, the accounting information output means 1311 obtains one or more pieces of source information (in this case, date, account information, etc.) that constitute the accounting information from the received invoice (PDF file).

[0185] Next, the accounting information output means 1311 constructs accounting information "<Date>2021 / 11 / 1 <Account>Outsourcing expenses <Account information>P Bank XXXXX <Extended item>Automatic set, A1000 <Expense allocation>Department 1=1 Department 2=2 Department 3=1 ..." which has one or more reusable pieces of information acquired and one or more original pieces of information acquired.

[0186] Next, the accounting information output means 1311 transmits, for example, the configured accounting information to the terminal device 2 that sent the invoice.

[0187] Next, the terminal receiving unit 25 of terminal device 2 receives accounting information. Then, the terminal processing unit 23 uses the received accounting information to construct the accounting information to be output. Next, the terminal output unit 26 outputs the constructed accounting information along with the transmitted invoice. An example of such output is shown in Figure 11.

[0188] Next, suppose the user presses the registration button 1101 in Figure 11. The terminal reception unit 22 then receives this instruction. Next, the terminal processing unit 23 decides to transmit the displayed accounting information. Next, the terminal transmission unit 24 associates the displayed accounting information with the management information and transmits it to the invoice processing unit 1. The management information is the sender identifier "<Company> Company A <Contact Person> Yamada Aiko" and the recipient identifier "<Company> Company X <Contact Person> Tanaka Eiko".

[0189] Next, the accounting information output means 1311 of the invoice processing device 1 receives the accounting information to be stored from the terminal device 2. The accounting information output means 1311 then stores the received accounting information in the accounting information storage unit 112, pairing it with the management information that corresponds to the received invoice. An example of such accounting information is "ID=61" in Figure 9.

[0190] As shown in this specific example, accounting information corresponding to received invoices can be efficiently constructed using historical accounting information that corresponds to management information linking the sender and recipient of the received invoices.

[0191] (Specific example 2) Let's assume the current time is November 1, 2021, 12:00 PM. And let's assume that a deadline check is scheduled to be performed every day at 12:00 PM.

[0192] In other words, the processing unit 13 of the invoice processing unit 1 obtains "November 1, 2021, 12:00 PM" from a clock (not shown) and determines that it is time to perform an expiration check because it matches the trigger condition for expiration checks, "Every day, 12:00 PM".

[0193] Next, the deadline management means 1312 obtains the deadline information "end of each month" from the management information management table (Figure 8) in conjunction with the first management information. Then, the deadline management means 1312 determines that the obtained "November 1, 2021, 12:00" is past "end of each month".

[0194] Next, the deadline management means 1312 obtains the first piece of management information, "Sender identifier: '<Company> Company A <Contact Person> Yamada Ako', Recipient identifier: '<Company> Company X <Contact Person> Tanaka Eko'", from the management information management table (Figure 8).

[0195] Next, the deadline management device 1312 retrieves the date "2021 / 9 / 30" corresponding to the invoice paired with the first management information from the accounting information management table (Figure 9). The deadline management device 1312 then determines that the most recent date paired with the first management information is "2021 / 9 / 30," and that there is no invoice paired with an October date. In other words, the deadline management device 1312 determines that there is no invoice in the accounting information management table that corresponds to the invoice associated with the first management information and the deadline indicated by the deadline information.

[0196] Next, the deadline management means 1312 obtains notification information that the invoice has not been received. The deadline management means 1312 constructs the notification information using template information that constitutes the notification information, information that constitutes the management information, or information that can be obtained from the management information, or deadline information. Here, the template information is: "Dear <Sender Identifier.Contact Person>, We hope this finds you well. This is <Recipient Identifier.Contact Person> from <Recipient Identifier.Company>. We are contacting you because we have not yet received the invoice for the month of <Month Corresponding to Deadline Information>. We sincerely apologize if this has been a misunderstanding. We appreciate your cooperation in checking the invoice."

[0197] Next, the deadline management means 1312 obtains the sender email address "ya@a.com" corresponding to the first management information from the management information management table (Figure 8).

[0198] Next, the deadline management means 1312 sends the configured notification information by email to the sender email address "ya@a.com".

[0199] Next, the terminal device 2 of user "Yamada Aiko" receives and outputs the notification information. An example of such output is shown in Figure 12. In Figure 12, the "Check Sending History" button 1201 is associated with information for accessing accounting information that is paired with the management information "Sender Identifier "<Company> Company A <Contact Person> Yamada Aiko", Recipient Identifier "<Company> Company X <Contact Person> Tanaka Eiko"" (for example, a URL for accessing the invoice processing device 1, a search expression for the invoice information management table using the management information as a condition, etc.).

[0200] Next, let's assume that user "Yamada A-ko" presses the "Check Sending History" button 1201. The terminal reception unit 22 then receives the output instruction. This output instruction includes a search expression in the invoice information management table that uses the management information as a condition. Next, the terminal processing unit 23 configures the output instruction to be sent. Then, the terminal transmission unit 24 sends the output instruction to the invoice processing device 1.

[0201] Next, the receiving unit 12 of the invoice processing device 1 receives the output instruction from the terminal device 2. The processing unit 13 then obtains the accounting information for "ID=58" corresponding to the received output instruction from the accounting information management table (Figure 9). Next, the transmitting unit 14 transmits the obtained accounting information to the terminal device 2 that sent the output instruction.

[0202] Next, terminal device 2 receives and outputs the accounting information for "ID=58". This allows us to know that Yamada A-ko of Company A sent her last invoice to Tanaka E-ko of Company X on 2021 / 9 / 30, and that she was unable to send the invoice for October.

[0203] Next, the deadline management means 1312 performs the same deadline check process on the second piece of management information as described above.

[0204] In summary, this specific example allows for managing the arrival deadline of invoices in the invoice management information. Furthermore, this example allows for notifying the invoice sender if an invoice does not arrive by the arrival deadline in the invoice management information.

[0205] (Specific example 3) Let's assume the current time is "2021 / 10 / 15 19:15". And let's assume that user "Inoue B-man" (hereinafter referred to as "the user") has launched the email application on terminal device 2 in order to send invoice information.

[0206] Then, the email application is launched on terminal device 2. The user then performs the operation to attach a separately prepared PDF file of the invoice as an email attachment. As a result, the invoice (PDF file) is attached as shown in 1301 of Figure 13 (see 1301).

[0207] Furthermore, the user entered the email address "a002@b.jp", which was provided by the operator of the invoice processing device 1, as the recipient of the invoice to "F. Kinoshita of Company Y" (see 1302). The user also entered the email title (1303) and body (1304) and instructed the user to press the send button 1305.

[0208] Then, the email shown in Figure 13 is sent to the address "a002@b.jp".

[0209] Next, the invoice receiving unit 121 of the invoice processing device 1 receives the invoice, email title, email body information, etc., via email.

[0210] Next, the fraud detection method 1313 obtains the recipient email address "a002@b.jp" and the sender email address "ib@b.jp". Then, the fraud detection method 1313 obtains the management information corresponding to the obtained email addresses "a002@b.jp" and "ib@b.jp" from the management information management table (Figure 8): "Sender identifier "<Company> Company B <Contact Person> Inoue B-o", Recipient identifier "<Company> Company Y <Contact Person> Kinoshita F-o".

[0211] Next, the fraud detection device 1313 retrieves the accounting information (ID=59) that corresponds to the acquired management information from the accounting information management table.

[0212] Furthermore, the fraud detection method 1313 obtains partial information from the accounting information (ID=59), such as the date "2021 / 10 / 15" and the billing amount "1,540".

[0213] Next, the fraud detection device 1313 obtains partial information from the received invoice that is the same as the partial information obtained from the accounting information (ID=59). Here, let's assume that the fraud detection device 1313 obtained partial information such as the date "2021 / 10 / 15" and the invoice amount "1,540" from the received invoice.

[0214] Next, the fraud detection device 1313 determines that all of the partial information from the two information sources matches. In other words, the fraud detection device 1313 determines that the received invoice is a duplicate registration that has already been registered. The fraud detection device 1313 then substitutes "fraudulent (duplicate registration)" into the fraud detection result.

[0215] Next, the invoice processing unit 131 sends a message to the terminal device 2 of Mr. Inoue B, who sent the invoice, indicating that the submitted invoice is fraudulent (in this case, "fraudulent (duplicate registration)").

[0216] Next, Inoue B's terminal device 2 receives and outputs a message indicating that the transmitted invoice is fraudulent (in this case, "fraudulent (duplicate registration)"). Needless to say, the format of this output is irrelevant.

[0217] As shown in this specific example, it is possible to perform fraud detection for duplicate registrations of received invoices using management information that associates the sender and recipient of the invoice.

[0218] (Specific example 4) Similar to Specific Example 3, let's assume that user "Inoue B-o" (hereinafter referred to as "the user") attached an invoice containing account information such as "R Bank UUUUUU..." and sent an invoice to "Kinoshita F-o of Y Company" via email, as shown in Figure 13.

[0219] Next, the invoice receiving unit 121 of the invoice processing device 1 receives the invoice, email title, email body information, etc., via email.

[0220] Next, the fraud detection method 1313 obtains the recipient email address "a002@b.jp" and the sender email address "ib@b.jp". Then, the fraud detection method 1313 obtains the management information corresponding to the obtained email addresses "a002@b.jp" and "ib@b.jp" from the management information management table (Figure 8): "Sender identifier "<Company> Company B <Contact Person> Inoue B-o", Recipient identifier "<Company> Company Y <Contact Person> Kinoshita F-o".

[0221] Next, the fraud detection tool 1313 retrieves the account information "Q Bank YYYYY...", which is partial information of the accounting information (ID=59) that is paired with the acquired management information, from the accounting information management table.

[0222] Furthermore, the fraud detection method 1313 obtains account information "R Bank UUUUUU..." from the received invoice.

[0223] Next, the fraud detection device 1313 determines that the account information from the two sources does not match. In other words, the fraud detection device 1313 determines that there is a possibility of identity theft because the account information on the received invoice is different. The fraud detection device 1313 then substitutes "fraud (possibility of identity theft)" into the fraud detection result.

[0224] Next, the invoice processing unit 131 sends a message to the terminal device 2 of Mr. Inoue B, who sent the invoice, indicating that the transmitted invoice is fraudulent (in this case, "fraudulent (possible impersonation)").

[0225] Next, Inoue B's terminal device 2 receives and outputs a message indicating that the transmitted invoice is fraudulent (in this case, "fraudulent (possible impersonation)"). Needless to say, the manner of this output is irrelevant.

[0226] As described above, this specific example demonstrates that by using account information corresponding to management information that links the sender and recipient of an invoice, it is possible to perform fraudulent checks on whether an accepted invoice was sent by someone impersonating another person.

[0227] As described above, according to this embodiment, appropriate processing of invoices can be performed using management information that associates the sender and recipient of the invoice.

[0228] Furthermore, according to this embodiment, accounting information corresponding to received invoices can be efficiently constructed using past accounting information corresponding to management information that associates the sender and recipient of the received invoices.

[0229] Furthermore, according to this embodiment, the invoice arrival deadline can be managed for the invoice management information.

[0230] Furthermore, according to this embodiment, by using deadline information that specifies the arrival date of the invoice in the invoice management information, it is possible to determine whether or not the invoice arrived by the arrival date, and to perform processing according to the determination result.

[0231] Furthermore, according to this embodiment, fraud checks can be performed on received invoices using management information that associates the sender and recipient of the invoice. Fraud checks include, for example, checking for duplicate registrations and checking for fraudulent transmissions by impersonators.

[0232] The processing in this embodiment may be implemented by software. This software may be distributed by software download or the like. Alternatively, this software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software that implements the invoice processing device 1 in this embodiment is the following program. In other words, this program causes a computer that can access a management information storage unit that stores one or more pieces of management information associating a sender identifier that identifies the sender of an invoice with a recipient identifier that identifies the recipient of the invoice, to function as an invoice receiving unit that receives a new invoice with a sender identifier and a recipient identifier associated with the invoice received by the invoice receiving unit, and to function as an invoice processing unit that processes the invoice using the sender identifier and recipient identifier.

[0233] Figure 14 also shows the external appearance of a computer that executes the program described herein to realize the various embodiments of the invoice processing device, etc. described above. The embodiments described above can be realized with computer hardware and computer programs executed thereon. Figure 14 is an overview of this computer system 300, and Figure 15 is a block diagram of the system 300.

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

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

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

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

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

[0239] Furthermore, the computer running the above program may be a single computer or multiple computers. In other words, it may perform centralized processing or distributed processing.

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

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

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

[0243] As described above, the invoice processing device according to the present invention has the effect of being able to perform appropriate processing using management information that associates the sender and recipient of an invoice, and is useful as an invoice processing device, etc. [Explanation of Symbols]

[0244] 1. Invoice Processing Device 2 Terminal devices 11 Storage Unit 12 Reception Department 13 Processing Unit 14. Transmitter 21 Terminal storage section 22 Terminal Reception Section 23 Terminal Processing Unit 24 Terminal transmission unit 25 Receiving part of the terminal 26 Terminal output section 111 Management Information Storage Unit 112 Accounting Information Storage Unit 121 Invoice Reception Department 131 Invoice Processing Department 1311 Accounting Information Output Method 1312 Deadline management means 1313 Methods of fraud detection

Claims

1. A management information storage unit stores one or more management information items that associate a sender identifier that identifies the sender of an invoice with a recipient identifier that identifies the recipient of the invoice, A billing reception unit that receives invoices, where the sender identifier and recipient identifier are associated, An invoice processing device comprising: an invoice receiving unit that, upon receiving an invoice, obtains the sender identifier and recipient identifier associated with the invoice; obtains management information corresponding to the sender identifier and recipient identifier from the management information storage unit; obtains accounting information corresponding to the management information from an accounting information storage unit which stores accounting information corresponding to one or more past invoices associated with one or more pieces of management information; obtains reusable information, which is information of predetermined items, from the accounting information; constructs accounting information using the reusable information; and outputs the accounting information.

2. The invoice processing unit is: The invoice processing device according to claim 1, wherein when the invoice receiving unit receives the invoice, it obtains the latest accounting information, which is paired with management information corresponding to the sender identifier and recipient identifier associated with the invoice, or accounting information to which a flag indicating that it is representative accounting information is attached, from the accounting information storage unit where the accounting information is stored, obtains reusable information which is information of predetermined items from the accounting information, constructs accounting information using the reusable information, and outputs the accounting information.

3. The reusable information is accounting information, as described in claim 1, invoice processing device.

4. The invoice processing device according to claim 1, wherein the management information stored in the management information storage unit is associated with deadline information that specifies the arrival deadline for the invoice.

5. The aforementioned invoice processing unit, The invoice processing apparatus according to claim 4, comprising a deadline management means that determines whether the invoice receiving unit has received an invoice to which a sender identifier and a recipient identifier corresponding to the deadline information have been associated by the arrival deadline specified by the deadline information, and performs processing according to the result of said determination.

6. The aforementioned deadline management means is The invoice processing device according to claim 5, wherein when the invoice receiving unit receives an invoice by the arrival deadline specified by the deadline information, and the sender identifier and recipient identifier corresponding to the deadline information are associated with the invoice, it performs a first notification process to inform the recipient identified by the recipient identifier that the invoice has been received.

7. The aforementioned deadline management means is The invoice processing device according to claim 5, which, if the invoice receiving unit determines that it has not received an invoice associated with a sender identifier and a recipient identifier corresponding to the deadline information by the arrival deadline specified by the deadline information, performs a second notification process to inform the recipient identified by the recipient identifier that the invoice has not been received.

8. The aforementioned deadline management means is The invoice processing device according to claim 5, which, if the invoice receiving unit determines that it has not received an invoice with a sender identifier and recipient identifier associated with the deadline information by the arrival deadline specified by the deadline information, performs a third notification process to inform the sender identified by the sender identifier that the invoice has not been sent.

9. The aforementioned invoice processing unit, The system includes a fraud detection means that uses the invoice received by the invoice receiving unit and one or more past invoices corresponding to the sender identifier and recipient identifier of the invoice to perform a fraud check on the invoice received by the invoice receiving unit and outputs inspection information regarding the results of the fraud check. The aforementioned fraud detection means is The invoice processing device according to claim 1, which compares one or more partial pieces of information constituting an invoice received by the invoice receiving unit with one or more partial pieces of information constituting one or more past invoices, obtains a matching rate, determines that the invoice is a duplicate receipt if the matching rate is above a threshold, and outputs the result of the determination.

10. The aforementioned fraud detection means is The invoice processing device according to claim 9, which compares one or more partial pieces of information constituting an invoice received by the invoice receiving unit with one or more partial pieces of information constituting one or more past invoices received within a threshold time or within a threshold date from the date of receipt, obtains a matching rate, determines that the invoice is a duplicate receipt if the matching rate is equal to or greater than a threshold, and outputs the result of the determination.

11. The aforementioned invoice processing unit, The system includes a fraud detection means that uses the invoice received by the invoice receiving unit and one or more past invoices corresponding to the sender identifier and recipient identifier of the invoice to perform a fraud check on the invoice received by the invoice receiving unit and outputs inspection information regarding the results of the fraud check. The aforementioned fraud detection means is The invoice processing device according to claim 1, which compares the account information constituting an invoice received by the invoice receiving unit with the account information constituting one or more past invoices, and if the account information is different, determines that the invoice received by the invoice receiving unit is an invalid invoice, and outputs the result of said determination.

12. The aforementioned invoice processing unit, The system includes a fraud detection means that uses the invoice received by the invoice receiving unit and one or more past invoices corresponding to the sender identifier and recipient identifier of the invoice to perform a fraud check on the invoice received by the invoice receiving unit and outputs inspection information regarding the results of the fraud check. The aforementioned fraud detection means is The invoice processing device according to claim 1, which compares the appearance information constituting an invoice received by the invoice receiving unit with the appearance information constituting one or more past invoices, and if the appearance information is different, determines that the invoice received by the invoice receiving unit is a fraudulent invoice and outputs the result of said determination.

13. An invoice processing method in which all processing performed by the invoice processing device described in any one of claims 1 to 12 is performed by a computer.

14. Computers, A program for functioning as an invoice processing device according to any one of claims 1 to 12.

Images