Invoice processing device, invoice processing method, and program

Abstract

To provide an invoice processing device capable of collectively managing invoice information received by multiple routes, which cannot do in the conventional technology.SOLUTION: An invoice processing device 1 capable of collectively managing invoice information received by multiple routes, comprises first reception means 121 for receiving invoice information from a terminal device 2, second reception means 122 for receiving the invoice information by an E-mail, a reception unit 12 equipped with two or more means of third reception means 123 for accepting the invoice information based on the mailed invoice form, a route acquisition unit 133 for acquiring a route identifier that identifies the route from which the reception unit 12 accepts the invoice information, and a storage unit 137 pairing the invoice information accepted by the reception unit 12 with the route identifier acquired by the route acquisition unit 133 and storing them in an invoice storage unit 111 with the invoice information stored.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to an invoice processing device that receives and stores invoice information. [Background technology]

[0002] Conventionally, there have been invoice processing devices that process invoice information and that can easily check whether any invoices have been missed when invoices that have already been issued are consolidated or divided and reissued (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-114122 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the prior art, it was not possible to centrally manage invoice information received through multiple routes. [Means for solving the problem]

[0005] The invoice processing device of the first invention is an invoice processing device comprising a reception unit having two or more means of a first reception means for receiving invoice information from a terminal device, a second reception means for receiving invoice information by email, and a third reception means for receiving invoice information based on an invoice form mailed, a route acquisition unit for acquiring a route identifier that identifies the route by which the reception unit accepted the invoice information, and a storage unit for pairing the invoice information accepted by the reception unit with the route identifier acquired by the route acquisition unit and storing it in an invoice storage unit in which the invoice information is stored.

[0006] With this configuration, invoice information received through multiple routes can be managed collectively.

[0007] The invoice processing device of the second invention is a invoice processing device according to the first invention, in which the reception section comprises first reception means, second reception means and third reception means.

[0008] With this configuration, invoice information received through at least three routes can be managed in a centralized manner.

[0009] In addition, the invoice processing device of the third invention is an invoice processing device in which, compared to the first or second invention, the reception unit further includes an output instruction reception means for receiving an instruction to output invoice information, and further includes an invoice output unit for obtaining invoice information corresponding to the output instruction from the invoice storage unit, and outputting the invoice information together with a route identifier paired with the invoice information.

[0010] With this configuration, in a situation where invoice information can be received through a plurality of routes, the route through which each piece of invoice information is received can be managed.

[0011] In addition, the invoice processing device of the fourth invention is an invoice processing device in which the reception unit includes a management information reception means for receiving management information which is a pair of a sender identifier identifying the sender of the invoice and a destination identifier identifying the destination of the invoice, and further includes an output information acquisition unit for acquiring output information paired with the management information accepted by the management information reception means from an output information storage unit in which the output information is stored, in correspondence with one or more pieces of management information, and an output information output unit for outputting the output information.

[0012] With this configuration, it is possible to easily output the output information that is managed in association with the sender identifier and the destination identifier.

[0013] In addition, the invoice processing device of the fifth invention is an invoice processing device in which, compared to the fourth invention, the output information is a subject, and the output information output unit transmits the output information to the terminal device that transmitted the invoice information when the reception unit receives management information together with the invoice information.

[0014] With this configuration, it is possible to easily obtain the subject that corresponds to the pair of sender and recipient of the invoice.

[0015] In addition, the invoice processing device of the sixth invention is an invoice processing device in which the reception unit is equipped with a third reception means, and further includes an address information composition unit that obtains mailing information from a mailing address storage unit in which mailing address information regarding the mailing address of the invoice paper is stored, and composes address information for mailing the invoice paper, and an address information output unit that outputs the address information.

[0016] This configuration makes it possible to assist in the management of invoice forms received by mail. Specifically, address information for mailing the invoice form to a destination that manages the invoice form can be output.

[0017] In addition, the invoice processing device of the seventh invention is an invoice processing device according to any one of the first to sixth inventions, wherein the invoice storage unit stores one or more pieces of invoice information in association with management information which is a pair of a sender identifier and a destination identifier, the reception unit has a second reception means, and further has a management information acquisition unit which, when the second reception means receives invoice information by email, acquires the email address of the destination of the email address and acquires the management information paired with the email address from a management mail information storage unit which stores one or more pieces of management mail information having management information and an email address, and the accumulation unit accumulates the invoice information received by the second reception means in association with the management information acquired by the management information acquisition unit.

[0018] This configuration can assist in managing invoice information received by email. Specifically, the email address of the email destination is obtained, and the sender identifier and destination identifier of the invoice are automatically obtained using the email address, and the sender identifier and destination identifier can be managed together with the invoice information.

[0019] The eighth invention is an invoice processing device according to any one of the first to seventh inventions, wherein the reception unit is equipped with a second reception means, and the content acquisition unit acquires content information which is the body information or title of an e-mail, and the storage unit stores the content information in pairs with the invoice information received by the reception unit.

[0020] This configuration can assist in managing invoice information received by e-mail. Specifically, the subject or text of the e-mail can be managed in association with the invoice information.

[0021] In addition, the invoice processing device of the ninth invention is an invoice processing device in which the reception unit is equipped with a management information reception means for receiving management information which is a pair of a sender identifier and a destination identifier, and further includes a unique address acquisition unit for acquiring a unique email address in response to the reception of the management information, and a management mail information registration unit for storing the management mail information having the management information received by the management information reception means and the unique email address in a management mail information storage unit which stores one or more management mail information.

[0022] This configuration can assist in managing invoice information received by email. Specifically, a sender identifier, a recipient identifier, and a unique email address can be registered in association with each other. Effect of the Invention

[0023] The invoice processing device according to the present invention can collectively manage invoice information received through a plurality of routes. [Brief description of the drawings]

[0024] [Figure 1] Conceptual diagram of invoice processing system A according to the first embodiment [Diagram 2] Block diagram of the invoice processing system A [Diagram 3] Block diagram of the invoice processing device 1 [Figure 4]A flowchart explaining an example of the operation of the invoice processing device 1. [Diagram 5] A flowchart explaining an example of the operation of the invoice processing device 1. [Figure 6] A flowchart for explaining an example of the operation of the terminal device 2 of the user who is the sender or recipient of the bill. [Figure 7] A flowchart for explaining an example of the operation of the terminal device 2 of the same worker. [Figure 8] A diagram showing the invoice management table [Figure 9] FIG. 13 shows the output information management table. [Figure 10] The figure shows the management table for email information. [Figure 11] A diagram showing an example of the input screen [Figure 12] A screenshot of the email [Figure 13] A diagram showing an example of the input screen [Figure 14] An example of the output screen [Figure 15] An example of the output screen [Figure 16] Overview of the computer system [Figure 17] Block diagram of the computer system DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

[0026] (Embodiment 1) In this embodiment, an invoice processing device that can accept invoice information via at least two of the three routes of uploading invoice information, receiving invoice information by email, and accepting input of invoice information based on a mailed invoice form will be described. Note that invoice information accepted via each of the two or more routes is usually accumulated and can be managed collectively.

[0027] In this embodiment, an invoice processing device that can store and manage invoice information in pairs with a route identifier that identifies a receiving route for the invoice information will be described.

[0028] In this embodiment, one or more pieces of output information that are paired with a sender / destination pair are managed, and an invoice processing device that can output the output information in association with the invoice information corresponding to the pair is described. The output information is, for example, a subject.

[0029] In this embodiment, an invoice processing device will be described that supports the mailing of invoice forms for the purpose of managing the forms. Note that support for mailing includes, for example, outputting address information.

[0030] In this embodiment, an invoice processing device will be described which stores invoice information received by e-mail in pairs with sender and recipient information which is paired with the e-mail address of the sender of the e-mail.

[0031] In this embodiment, an invoice processing device will be described which stores invoice information received by e-mail in association with the body information or title of the e-mail.

[0032] Furthermore, in this embodiment, we will describe an invoice processing device that can perform registration processing to accept management information having a sender and a recipient, obtain a unique email address, and register management email information having the email address, the sender, and the recipient.

[0033] 1 is a conceptual diagram of an 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.

[0034] The invoice processing device 1 may be, for example, a cloud server or an ASP server, but the type is not important. The invoice processing device 1 is usually a device that accepts and manages invoice information. The terminal device 2 may be a so-called personal computer, smartphone, or tablet terminal, but the type is not important. The terminal device 2 is a terminal used by a user who sends the invoice information. The terminal device 2 is a terminal (which may be called a first terminal) used by a user who is the sender or destination of the invoice information, or a terminal (which may be called a second terminal) used by a worker who inputs the invoice information based on the transported invoice paper.

[0035] The invoice processing device 1 and one or more terminal devices 2 are capable of communicating with each other via a network such as the Internet.

[0036] FIG 2 is a block diagram of the invoice processing system A in this embodiment. FIG 3 is a block diagram of the invoice processing device 1.

[0037] The invoice processing device 1 comprises a storage unit 11, a reception unit 12, a processing unit 13, and an output unit 14. The storage unit 11 comprises an invoice storage unit 111, a mailing address storage unit 112, an output information storage unit 113, and a management mail information storage unit 114. The reception unit 12 comprises a first reception means 121, a second reception means 122, a third reception means 123, an output instruction reception means 124, and a management information reception means 125. The processing unit 13 comprises a unique address acquisition unit 131, a management mail information registration unit 132, a route acquisition unit 133, a management information acquisition unit 134, a content acquisition unit 135, an output information acquisition unit 136, a storage unit 137, an address information composition unit 138, and an invoice acquisition unit 139. The output unit 14 comprises an output information output unit 141, an address information output unit 142, and an invoice output unit 143.

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

[0039] Various types of information are stored in the storage unit 11 constituting the invoice processing device 1. The various types of information include, for example, invoice information (to be described later) and mailing address information (to be described later).

[0040] One or more pieces of invoice information are stored in the invoice storage unit 111. Each piece of invoice information is usually stored in association with management information. The management information is a set of a sender identifier and a destination identifier.

[0041] The sender identifier is information that identifies the sender of the invoice. The sender of the invoice can be said to be the party that issues the invoice. The sender identifier can be thought of as information that specifies the issuer of the invoice. The sender identifier is, for example, the company name and person in charge of the invoice issuer, the company name and department name of the invoice issuer, the company identifier and person in charge identifier of the invoice issuer, or the company identifier and department identifier of the invoice issuer.

[0042] The delivery destination identifier is information that identifies the delivery destination of the invoice. The delivery destination of the invoice can be said to be the invoice destination. The delivery destination identifier can be thought of as information that identifies the party being invoiced. The sender identifier is, for example, the company name and person in charge of the party being invoiced, the company name and department name of the party being invoiced, the company identifier and person in charge identifier of the party being invoiced, or the company identifier and department identifier of the party being invoiced.

[0043] The invoice information may be associated with other information such as a route identifier (described later), a date, and output information (described later).

[0044] The invoice storage unit 111 is usually provided in the invoice processing device 1, but may be provided in an external device.

[0045] The mailing address storage unit 112 stores mailing address information regarding the mailing address of the invoice paper. Mailing address information is usually information about the location where the invoice paper is stored and managed. The mailing address information has a mailing address. The mailing address information has, for example, a postal code and a destination. The invoice paper is a paper invoice. The mailing address storage unit 112 is usually provided in the invoice processing device 1, but may be provided in an external device.

[0046] The output information storage unit 113 stores output information in association with one or more pieces of management information. The output information is information corresponding to the sender and sender of an invoice, and is information to be output. The output information is, for example, a subject. The output information is, for example, information regarding the payment deadline (for example, "within 30 days after the invoice is issued"). However, the output information is not restrictive. It is preferable that the output information is information in which the sender and destination of the invoice are fixed.

[0047] The management mail information storage unit 114 stores one or more pieces of management mail information. The management mail information is information on an email address for each piece of management information. The management mail information is information having management information and an email address. It is preferable that the email address is unique for each piece of management information. The email address is an address specified as the email destination when sending receipt information by email.

[0048] The reception unit 12 receives various types of information, instructions, etc. The various types of information, instructions, etc. include, for example, invoice information, output instructions, and management information.

[0049] Here, "acceptance" usually means receipt of information transmitted via a wired or wireless communication line, but the concept of "acceptance" may also include receipt of information input from an input device such as a keyboard, mouse, or touch panel, or receipt of information read from a recording medium such as an optical disk, magnetic disk, or semiconductor memory.

[0050] The first reception means 121 receives invoice information from the terminal device 2. The first reception means 121 usually receives invoice information via the Internet. The first reception means 121 usually receives invoice information uploaded from the terminal device 2. The person who inputs the invoice information is usually the issuer of the invoice (the person in charge of the organization that issued the invoice). The first reception means 121 may also receive management information along with the invoice information. The invoice information here is, for example, information input from the screen of the terminal device 2. The invoice information is, for example, a file uploaded from the terminal device 2. The first reception means 121 may receive a sender identifier and a destination identifier in addition to the invoice information. Also, when the invoice information is a file, the first reception means 121 may also receive, for example, a character string of information in the invoice information (for example, the invoice destination, the invoice amount, the sender of the invoice, etc.) in addition to the invoice information. Note that while PDF is preferable for the invoice file, the file format and structure are not important.

[0051] The second receiving means 122 receives invoice information by email. The person who inputs the invoice information is usually the issuer of the invoice. The invoice information is usually an attachment, but may be information written in the body of the email. An email usually has a title and body information in addition to the invoice information. The second receiving means 122, for example, checks a predetermined mailbox storage area (not shown) for each email address, determines whether or not an email exists, and if an email exists, retrieves the email from the mailbox.

[0052] It is preferable that the web page or app for inputting the invoice information, etc. of the worker's terminal device 2 is different from the web page or app for inputting the invoice information, etc. of the sender's terminal device 2, but they may be the same. If they are the same, it may be possible to distinguish whether the user is the sender or the worker based on the user identifier of the user who inputs the information, or the received information may include a route identifier. In other words, it is sufficient if the first receiving means 121 and the second receiving means 122 can obtain the correct route identifier by some method.

[0053] The third reception means 123 receives invoice information based on the invoice form that has been mailed. The person who inputs such invoice information is usually not the issuer of the invoice, but the worker to whom the invoice form has been mailed. There is no restriction on the method by which the worker inputs the invoice information. The invoice information may be a file or a collection of character strings, and the structure is not restricted. The worker uploads a file that is the invoice information created from the invoice form to the invoice processing device 1, for example, using the terminal device 2. The third reception means 123 may also receive, for example, character strings of information in the invoice information (for example, the invoice destination, the invoice amount, the sender of the invoice, etc.) in addition to the invoice information.

[0054] The output instruction receiving means 124 receives an instruction to output invoice information. The output instruction preferably has information for identifying the invoice information. The output instruction has, for example, one or more pieces of information among an invoice information identifier, a sender identifier, and a destination identifier. The output instruction has, for example, period information for identifying a period. The output instruction includes, for example, a search formula for searching the invoice information from the invoice storage unit 111.

[0055] The management information receiving means 125 receives management information. The management information is a set of a sender identifier that identifies the sender of the invoice and a destination identifier that identifies the destination of the invoice. The purpose of receiving the management information is to register management mail information.

[0056] The processing unit 13 performs various types of processing, such as processing performed by a unique address acquisition unit 131, a management mail information registration unit 132, a route acquisition unit 133, and the like.

[0057] The processing unit 13, for example, calculates the ratio of invoice information for each route identifier and outputs the usage ratio for each route. As a result, the usage status of each route can be grasped, which makes it possible to improve the invoice processing device 1, change the hiring of workers, and otherwise review the business.

[0058] The processor 13, for example, calculates the ratio of billing information for each sender identifier and outputs the usage ratio for each sender identifier and each route. This makes it possible to take measures such as instructing senders who use a large proportion of mail to increase the number of senders using the web or e-mail.

[0059] The processing unit 13 acquires information on the contents of the invoice, for example, from the invoice information, which is a received file. The information on the contents of the invoice is, for example, a sender identifier, a recipient identifier, an amount, a payment deadline, etc. The processing unit 13 acquires information on the contents of the invoice, for example, from the invoice information, which is a PDF file. The processing unit 13 acquires information on the contents of the invoice, for example, by performing character recognition processing on the invoice information, which is an image. In this case, for example, information on the format of the invoice (for example, coordinate information on which the name of the recipient company is written, coordinate information on which the name of the sender company is written, coordinate information on which the name of the recipient person in charge is written, coordinate information on which the name of the sender person in charge is written, and coordinate information on which the amount is written) is stored in the storage unit 11, and the processing unit 13 acquires information on the contents of the invoice from the invoice information using such information.

[0060] The processing unit 13, for example, retrieves from the storage unit 11 the destination person in charge email address that pairs with the destination identifier corresponding to the received email, and notifies the address corresponding to the destination person in charge identifier (for example, email address) that the invoice information has been accepted. The means of notification is not important. The processing unit 13 notifies by email, for example. The processing unit 13 forwards the received email, for example, to the destination person in charge identifier. The content of the notification is not important.

[0061] The unique address acquisition unit 131 acquires a unique email address in response to receipt of management information. There is no limit to the method for acquiring a unique email address. For example, the unique address acquisition unit 131 increments the numerical portion of a most recently generated email address, which is a numerical portion of an email address, to generate a replacement email address. For example, the unique address acquisition unit 131 reads out an unused email address from a set of two or more email addresses.

[0062] The management mail information registration unit 132 accumulates the management mail information, which includes the management information accepted by the management information accepting unit 125 and the unique email address acquired by the unique address acquisition unit 131, in the management mail information storage unit 114. Through this process, the management mail information is registered.

[0063] The route acquisition unit 133 acquires a route identifier that identifies the route by which the receiving unit 12 received the invoice information. A route may also be called a means. In other words, the route identifier is information that identifies, for example, whether the invoice information was received by the first receiving means 121, the second receiving means 122, or the third receiving means 123. When the invoice information was received by the first receiving means 121, for example, the route identifier is "web." When the invoice information was received by the second receiving means 122, for example, the route identifier is "email." When the invoice information was received by the third receiving means 123, for example, the route identifier is "mail."

[0064] The route acquisition unit 133 acquires a route identifier that specifies which of the first reception means 121, the second reception means 122, and the third reception means 123 the invoice information has been received by. The route acquisition unit 133 detects which of the first reception means 121, the second reception means 122, and the third reception means 123 the invoice information has been received by, and acquires a route identifier based on the detection result. The route acquisition unit 133 may acquire a route identifier received by the first reception means 121, the second reception means 122, or the third reception means 123, for example. Such a route identifier is, for example, information input by a user who inputs the invoice information.

[0065] When the second receiving means 122 receives invoice information by email, the management information acquisition unit 134 acquires the email address of the destination of the email, and acquires the management information paired with that email address from the management email information storage unit 114. Note that the technology for acquiring the email address of the destination of a received email is publicly known, and therefore a detailed description thereof will be omitted.

[0066] The content acquisition unit 135 acquires content information, which is the body information or title of the email, from the received email. The content information may be the email itself.

[0067] The output information acquisition unit 136 acquires output information paired with the management information accepted by the management information acceptance unit 125 from the output information storage unit 113. The output information is, for example, an item and a payment due date.

[0068] The accumulation unit 137 accumulates the invoice information accepted by the acceptance unit 12 in the invoice storage unit 111. It is preferable that the accumulation unit 137 accumulates the invoice information in the invoice storage unit 111 regardless of the route by which the invoice information was accepted. In this way, invoice information accepted via two or more routes can be collectively managed.

[0069] It is preferable that the accumulation unit 137 accumulates the invoice information accepted by the acceptance unit 12 in the invoice storage unit 111 in a pair with the route identifier acquired by the route acquisition unit 133 .

[0070] It is preferable that the storage unit 137 stores the invoice information received by the second accepting unit 122 in association with the management information acquired by the management information acquisition unit 134 .

[0071] The storage unit 137 also stores the content information of the received e-mail in a pair with the invoice information received by the second receiving means 122. In this way, for example, background information at the time of sending the invoice information can be obtained later.

[0072] The address information constructing unit 138 acquires mailing address information from the mailing address storage unit 112, and constructs address information for mailing the invoice form using the mailing address information. It is preferable that the address information constructing unit 138 automatically acquires the address information in response to the acceptance of the invoice information by the third accepting means 123.

[0073] The invoice acquisition unit 139 acquires one or more pieces of invoice information corresponding to the received output instruction from the invoice storage unit 111. It is preferable that the invoice acquisition unit 139 acquires from the invoice storage unit 111 one or more pairs of invoice information etc. corresponding to the received output instruction and a route identifier.

[0074] The output unit 14 outputs various types of information, such as invoice information, output information, and address information.

[0075] Here, output typically means transmission to terminal device 2, but it may also be a concept that includes display on a display, projection using a projector, printing on a printer, storage on a recording medium, and handing over the processing results to other processing devices or other programs.

[0076] The output information output unit 141 outputs one or more pieces of output information acquired by the output information acquisition unit 136. When the reception unit 12 receives management information together with invoice information, it is preferable that the output information output unit 141 transmits one or more pieces of output information to the terminal device 2 that has transmitted the invoice information. When the reception unit 12 receives invoice information that is a file, the output information output unit 141 may output a delivery destination identifier and a delivery source identifier acquired from the invoice information by the processing unit 13 together with the invoice information.

[0077] The address information output unit 142 outputs the address information acquired by the address information configuration unit 138. The address information output unit 142 usually transmits the address information to the terminal device 2 of the worker.

[0078] The invoice output unit 143 outputs the invoice information acquired by the invoice acquisition unit 139. It is preferable that the invoice output unit 143 outputs the invoice information and the route identifier acquired by the invoice acquisition unit 139. The invoice output unit 143 usually transmits the invoice information to the terminal device 2.

[0079] Various types of information are stored in the terminal storage unit 21 constituting the terminal device 2. The various types of information are, for example, a sender identifier and a destination identifier.

[0080] The terminal reception unit 22 receives various information, instructions, etc. Examples of the various information, instructions, etc. include a URI or URL for accessing a website for inputting a bill, an instruction to start a bill input application, an instruction to start an email application, bill information, management information, An output instruction. An invoice input application is an application for inputting invoice information. An email application is an application for sending emails.

[0081] Here, reception is a concept that includes reception of information input from input devices such as a keyboard, mouse, or touch panel, reception of information transmitted via a wired or wireless communication line, and reception of information read from recording media such as an optical disk, magnetic disk, or semiconductor memory.

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

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

[0084] The terminal transmission unit 24 transmits various types of information, instructions, etc. to the invoice processing device 1. The various types of information, instructions, etc. are, for example, invoice information, e-mail, output instructions, and management information.

[0085] The terminal receiving unit 25 receives various types of information from the invoice processing device 1. The various types of information include, for example, invoice information, output information, and address information.

[0086] The terminal output unit 26 outputs various types of information, such as invoice information, output information, and address information.

[0087] Here, output is a concept that includes display on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and handing over the processing results to other processing devices or other programs, etc.

[0088] The storage unit 11, invoice storage unit 111, mailing address storage unit 112, output information storage unit 113, management mail information storage unit 114, and terminal storage unit 21 are preferably non-volatile recording media, but can also be realized with volatile recording media.

[0089] There is no restriction on the process by which information is stored in the storage unit 11, etc. For example, information may be stored in the storage unit 11, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the storage unit 11, etc., or information inputted via an input device may be stored in the storage unit 11, etc.

[0090] The reception unit 12, the first reception means 121, the second reception means 122, the third reception means 123, the output instruction reception means 124, the management information reception means 125, and the terminal reception unit 25 are typically realized by wireless or wired communication means, but may also be realized by means for receiving broadcasts.

[0091] The processing unit 13, the unique address acquisition unit 131, the management mail information registration unit 132, the route acquisition unit 133, the management information acquisition unit 134, the content acquisition unit 135, the output information acquisition unit 136, the storage unit 137, the address information composition unit 138, and the terminal processing unit 23 can usually be realized by a processor, a memory, etc. The processing procedure of the processing unit 13, etc. is usually realized by software, and the software is recorded in a recording medium such as a ROM. However, it may also be realized by hardware (dedicated circuit). The processor is, for example, a CPU, an MPU, a GPU, etc., and the type is not important.

[0092] The output unit 14, the output information output unit 141, the address information output unit 142, the invoice output unit 143, the terminal transmission unit 24, and the terminal output unit 26 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

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

[0094] The terminal output unit 26 may be considered to include, or may not include, an output device such as a display, a speaker, etc. The terminal output unit 26 may be realized by driver software for an output device, or a combination of driver software for an output device and an output device, etc.

[0095] Next, an example of the operation of the invoice processing system A will be described. First, an example of the operation of the invoice processing device 1 will be described with reference to the flowcharts of FIGS.

[0096] (Step S401) The first reception means 121 judges whether or not invoice information, etc. has been received from the terminal device 2 of the sender of the invoice information. If invoice information, etc. has been received, the process proceeds to step S402, and if invoice information, etc. has not been received, the process proceeds to step S407.

[0097] The invoice information etc. here may be just the invoice information, but it is preferable that the invoice information etc. include the invoice information, a sender identifier, and a destination identifier.

[0098] (Step S402) The route acquisition unit 133 acquires the route identifier "web".

[0099] (Step S403) The management information acquisition unit 134 acquires management information that is a pair of the sender identifier and the destination identifier received in step S401. Alternatively, the management information acquisition unit 134 may acquire the sender identifier and the destination identifier from the invoice information and configure the management information.

[0100] (Step S404) The output information acquiring unit 136 acquires, from the output information storage unit 113, output information paired with the management information acquired in step S403.

[0101] (Step S405) The storage unit 137 constructs information having the invoice information received in step S401, the route identifier "web" obtained in step S402, and the output information obtained in step S404.

[0102] (Step S406) The storage unit 137 stores the information configured in step S405 in the invoice storage unit 111. The process returns to step S401.

[0103] (Step S407) The second reception means 122 judges whether or not invoice information, etc. has been received by email. If invoice information, etc. has been received, the process proceeds to step S408, and if invoice information, etc. has not been received, the process proceeds to step S415.

[0104] The invoice information etc. here may be just the invoice information, but it is preferable that the invoice information etc. include the invoice information, a sender identifier, and a destination identifier.

[0105] (Step S408) The route acquisition unit 133 acquires the route identifier "email".

[0106] (Step S409) The management information acquiring unit 134 acquires the email address of the destination of the email.

[0107] (Step S410) The management information acquisition unit 134 acquires, from the management mail information storage unit 114, management information paired with the mail address acquired in step S409.

[0108] (Step S411) The output information acquisition unit 136 acquires, from the output information storage unit 113, output information paired with the management information acquired in step S410.

[0109] (Step S412) The content acquiring unit 135 acquires content information from the e-mail received in step S407.

[0110] (Step S413) The storage unit 137 configures information having the invoice information received in step S407, the route identifier “email” acquired in step S408, the output information acquired in step S411, and the content information acquired in step S412.

[0111] (Step S414) The storage unit 137 stores the information configured in step S413 in the invoice storage unit 111. The process returns to step S401.

[0112] (Step S415) The third reception means 123 judges whether or not invoice information, etc. has been received from the worker's terminal device 2. If invoice information, etc. has been received, the process proceeds to step S416, and if invoice information, etc. has not been received, the process proceeds to step S424. Note that the invoice information, etc. here may be only invoice information.

[0113] (Step S416) The route acquisition unit 133 acquires the route identifier "mail".

[0114] (Step S417) The management information acquisition unit 134 acquires management information that is a pair of the sender identifier and the destination identifier received in step S415. The management information acquisition unit 134 may acquire the sender identifier and the destination identifier from the invoice information and configure the management information.

[0115] (Step S418) The output information acquisition unit 136 acquires, from the output information storage unit 113, output information paired with the management information acquired in step S417.

[0116] (Step S419) The storage unit 137 configures information having the invoice information received in step S415, the route identifier "mail" obtained in step S416, and the output information obtained in step S418.

[0117] (Step S420) The storage unit 137 stores the information configured in step S419 in the invoice storage unit 111.

[0118] (Step S421) The address information constructing unit 138 acquires mailing destination information from the mailing destination storage unit 112.

[0119] (Step S422) The address information constructing unit 138 constructs address information using the mailing address information acquired in step S421.

[0120] (Step S423) The address information output unit 142 transmits the address information constructed in step S422 to the terminal device 2 of the worker who transmitted the invoice information, etc. Return to step S401.

[0121] (Step S424) The management information receiving means 125 judges whether or not management information has been received from the terminal device 2. If management information has been received, the process proceeds to step S425, and if management information has not been received, the process proceeds to step S429.

[0122] (Step S425) The unique address acquiring unit 131 acquires a unique email address.

[0123] (Step S426) The administration mail information registration unit 132 composes administration mail information having the administration information received in step S424 and the email address acquired in step S425.

[0124] (Step S427) The management mail information registration section 132 accumulates the management mail information configured in step S426 in the management mail information storage section 114.

[0125] (Step S428) The output unit 14 transmits the management mail information constructed in step S426 to the terminal device 2 that transmitted the management information. Through this process, the user of the terminal device 2 can know the email address to use when sending the invoice information by email.

[0126] (Step S429) The output instruction receiving means 124 judges whether or not an output instruction has been received from the terminal device 2. If an output instruction has been received, the process proceeds to step S430, and if an output instruction has not been received, the process returns to step S401.

[0127] (Step S430) The invoice obtaining unit 139 obtains from the invoice storage unit 111 the invoice information and the like corresponding to the output instruction received in step S429 and the route identifier.

[0128] (Step S431) The invoice output unit 143 transmits the invoice information etc. acquired in step S430 and the route identifier to the terminal device 2 that transmitted the output instruction. Then, the process returns to step S401.

[0129] In the flowcharts of FIG. 4 and FIG. 5, the process ends when the power is turned off or an interrupt is issued to end the process.

[0130] Next, an example of the operation of the terminal device 2 (so-called first terminal) used by the sender of the invoice information will be described with reference to the flowchart in Fig. 6. Note that the sender of the invoice information (the person making the request) may also be the recipient of the invoice information (the person being requested).

[0131] (Step S601) The terminal reception unit 22 determines whether or not an instruction to launch the invoice input app has been received. If the instruction to launch has been received, the process proceeds to step S602; if the instruction to launch has not been received, the process proceeds to step S605. The invoice input app is an app that inputs invoice information and sends it to the invoice processing device 1. Also, here, instead of the invoice input app, a website for inputting invoice information may be used. In other words, instead of an instruction to launch the invoice input app, the URL of a website for inputting invoice information may be used.

[0132] (Step S602) The device processing unit 23 launches the bill input application in the terminal storage unit 21. Note that instead of launching the bill input application, access to a website for inputting bill information may be performed.

[0133] (Step S603) The terminal reception unit 22 judges whether or not it has received input of invoice information, etc. If it has received input of invoice information, etc., it proceeds to step S604, and if it has not received input of invoice information, etc., it returns to step S603.

[0134] (Step S604) The terminal processing unit 23 uses the invoice information etc. accepted in step S603 to compose invoice information etc. to be transmitted. The terminal transmitting unit 24 transmits the invoice information etc. to the invoice processing device 1. Return to step S601.

[0135] (Step S605) Terminal reception unit 22 judges whether or not an instruction to start an e-mail application has been received. If an instruction to start an e-mail application has been received, the process proceeds to step S606. If an instruction to start an e-mail application has not been received, the process proceeds to step S610. The e-mail application is an application for sending e-mail.

[0136] (Step S606) The terminal processing unit 23 starts up the email application in the terminal storage unit 21.

[0137] (Step S607) Terminal reception unit 22 determines whether input of invoice information, content information, destination email address, etc. has been accepted for the email application. If input of invoice information, etc. has been accepted, the process proceeds to step S608, and if input of invoice information, etc. has not been accepted, the process returns to step S607. Note that invoice information is usually a file (e.g., a PDF file) and is input to the email application as an attachment to an email.

[0138] (Step S608) The terminal reception unit 22 judges whether or not an instruction to send mail has been received. If an instruction to send mail has been received, the process proceeds to step S609, and if an instruction to send mail has not been received, the process returns to step S608.

[0139] (Step S609) The terminal processing unit 23 composes an e-mail including bill information, content information, etc. The terminal transmitting unit 24 transmits the composed e-mail to the destination indicated by the input e-mail address. Return to step S601.

[0140] (Step S610) The terminal reception unit 22 judges whether or not the management information has been received. If the management information has been received, the process proceeds to step S611, and if the management information has not been received, the process proceeds to step S614.

[0141] (Step S611) The terminal processing unit 23 composes management information to be transmitted using the management information accepted in step S610. The terminal transmitting unit 24 transmits the management information to the invoice processing device 1.

[0142] (Step S612) The terminal receiving unit 25 judges whether or not management mail information has been received from the invoice processing device 1. If management mail information has been received, the process proceeds to step S613, and if management mail information has not been received, the process returns to step S612. Note that here, the terminal receiving unit 25 may receive only the disciple mail address contained in the management mail information.

[0143] (Step S613) The terminal processing unit 23 uses the management mail information received in step S612 to compose management mail information to be output. The terminal output unit 26 outputs the management mail information. Return to step S601. Here, the terminal output unit 26 may output only the disciple's mail address.

[0144] (Step S614) The terminal reception unit 22 judges whether or not an output instruction has been received. If an output instruction has been received, the process proceeds to step S615, and if an output instruction has not been received, the process returns to step S601.

[0145] (Step S615) The terminal processing unit 23 composes an output instruction to be transmitted. The terminal transmitting unit 24 transmits the output instruction to the invoice processing device 1.

[0146] (Step S616) The terminal receiving unit 25 judges whether or not one or more pieces of invoice information, etc. have been received. If invoice information, etc. have been received, the process proceeds to step S617, and if invoice information, etc. have not been received, the process returns to step S616.

[0147] (Step S617) The terminal processing unit 23 uses the invoice information, etc. received in step S616 to compose invoice information, etc. to be output. The terminal output unit 26 outputs the invoice information, etc. Return to step S601. Note that it is preferable that the invoice information, etc. include the invoice information and the route identifier.

[0148] In the flowchart of FIG. 6, steps S601 to S604 are for sending the invoice information via a first route (route identifier=web). Steps S605 to S609 are for sending the invoice information via a second route (route identifier=email). Furthermore, the sender of the invoice information may send the invoice paper via a third route (route identifier=mail). In such a case, the sender prints out the invoice paper and takes steps to mail it to a predetermined mailing address.

[0149] In the flow chart of FIG. 6, the invoice processing device 1 may be compatible with only two of the three routes.

[0150] Furthermore, in the flowchart of FIG. 6, the process ends when the power is turned off or an interrupt for ending the process occurs.

[0151] Next, an example of the operation of the terminal device 2 (so-called second terminal) used by an operator who receives an invoice form by mail and then works on the invoice information based on the invoice form will be described with reference to the flowchart in Fig. 7. The operator may be, for example, an operator of the company that operates the invoice processing device 1.

[0152] (Step S701) The terminal reception unit 22 judges whether or not invoice information, etc. has been received from the worker. If invoice information, etc. has been received, the process proceeds to step S702, and if invoice information, etc. has not been received, the process returns to step S701. Note that the invoice information, etc. is, for example, invoice information, a sender identifier, and a destination identifier. It is also preferable that the invoice information is a file (for example, a PDF file). It is also assumed that, prior to step S701, the worker is creating invoice information from an invoice form, for example by converting the invoice form to PDF.

[0153] (Step S702) The terminal processing unit 23 composes invoice information to be transmitted using the invoice information etc. accepted in step S701. The terminal transmitting unit 24 transmits the invoice information etc. to the invoice processing device 1.

[0154] (Step S703) The terminal receiving unit 25 determines whether or not address information has been received from the invoice processing device 1. If address information has been received, the process proceeds to step S704, and if address information has not been received, the process returns to step S703.

[0155] (Step S704) The terminal processing unit 23 uses the address information received in step S703 to compose address information to be printed. The terminal output unit 26 outputs the address information.

[0156] (Step S705) The terminal reception unit 22 judges whether or not a print instruction has been received. If a print instruction has been received, the process proceeds to step S706, and if a print instruction has not been received, the process returns to step S705.

[0157] (Step S706) The terminal output unit 26 prints the output address information. The printed address information is affixed to an envelope, the invoice form is placed in the envelope, and the envelope is mailed to the destination indicated by the address information.

[0158] In the flowchart of FIG. 7, the process ends when the power is turned off or an interrupt is issued to end the process.

[0159] The specific operation of the invoice processing system A in this embodiment will now be described. A conceptual diagram of invoice processing system A is shown in Figure 1.

[0160] Now, the invoice storage unit 111 of the invoice processing device 1 stores an invoice management table having the structure shown in FIG. 8. The invoice management table is a table for managing invoice information and the like. The invoice management table manages records having an "ID", "invoice information", "sender identifier", "destination identifier", "route identifier", "date", "subject", and "payment due date". "ID" is information for identifying a record. "Invoice information" is assumed to be a PDF file of an invoice here. The "sender identifier" has "company" and "person in charge". "Company" is information for identifying an organization (company, sole proprietor, government office, etc.) that has sent the invoice information, and is the company name here. "Person in charge" is information for identifying a person in charge of the organization that has sent the invoice information, and is the person in charge name here. The "destination identifier" has "company" and "person in charge". "Company" is information for identifying an organization (company, sole proprietor, government office, etc.) to which the invoice information is to be sent, and is the company name here. "Person in charge" is information for identifying a person in charge of the organization to which the invoice information is to be sent, and is the person in charge name here. Here, the "route identifier" can be any one of "web", "email", or "mail". The "date" is the date on which the invoice information was received. The "date" can also be the date on which the invoice was issued.

[0161] Also, mailing address information "<Address> Toranomon, Minato-ku, Tokyo 105-0001...<Destination> XXXX Co., Ltd., Bill Management Center <Sender identifier>$sender identifier <destination identifier>$destination identifier" is stored in mailing address storage unit 112. Note that "$sender identifier" and "$destination identifier" are variables into which information on the corresponding sender identifier and destination identifier is substituted.

[0162] Furthermore, the output information storage unit 113 stores an output information management table having the structure shown in FIG. 9. The output information management table has "ID", "source identifier", "destination identifier", and "output information". "ID", "source identifier", and "destination identifier" are the same as "ID", "source identifier", and "destination identifier" in FIG. 8. "Output information" here has "subject" and "payment due date". "Subject" is the subject that corresponds to the invoice information. "Payment due date" is information that specifies the due date for payment of the invoice information.

[0163] Furthermore, the management mail information storage unit 114 stores a management mail information management table having the structure shown in FIG. 10. The management mail information management table has "ID", "sender identifier", "destination identifier", "destination email address", and "destination person in charge email address". The "ID", "sender identifier", and "destination identifier" are the same as the "ID", "sender identifier", and "destination identifier" in FIG. 8. The "destination email address" and "destination person in charge email address" are email addresses to use when sending invoice information by email. The "destination person in charge email address" is the email address of the person in charge who is used to notify the destination person in charge when the invoice information has been accepted.

[0164] In the above situation, the following five specific examples will be described. Specific Example 1 is a process for automatically configuring management information. Specific Example 2 is a case where invoice information, etc. is sent via a website. Specific Example 3 is a case where invoice information, etc. is sent by email. Specific Example 4 is a case where a worker inputs invoice information, etc. based on an invoice form that has been mailed. Specific Example 5 is a case where invoice information and a route identifier are output to terminal device 2 based on an output instruction.

[0165] (Example 1) Assume now that the user “Yamada A” has entered management information into the terminal device 2, including “sender identifier “<company> Company A <person in charge> Yamada A” and destination identifier “<company> Company X <person in charge> Tanaka E”.

[0166] Next, the terminal reception unit 22 of the terminal device 2 receives the management information. Next, the terminal processing unit 23 uses the received management information to configure management information to be transmitted. Next, the terminal transmission unit 24 transmits the management information to the invoice processing device 1.

[0167] Next, the management information receiving means 125 of the invoice processing device 1 receives the management information. Next, it is assumed that the unique address acquisition unit 131 acquires the unique email address "a001@b.jp". Note that here, the unique address acquisition unit 131 generates a unique email address by incrementing the <number> (here, three digits) in the email address template "a<number>@b.jp" in the storage unit 11. In other words, after acquiring "a001@b.jp", the unique address acquisition unit 131 acquires "a002@b.jp".

[0168] Next, the management mail information registration unit 132 constructs management mail information having the received management information "sender identifier "<company> Company A <person in charge> Yamada A", destination identifier "<company> Company X <person in charge> Tanaka E"" and the acquired email address "a001@b.jp". Next, the management mail information registration unit 132 accumulates the constructed management mail information in the management mail information management table (Figure 10). The accumulated management mail information is the record of "ID=1" in Figure 10. It is assumed that the "destination person in charge address" of the record of "ID=1" in Figure 10 was entered separately.

[0169] With the above process, the registration of the administrative email information is completed.

[0170] (Example 2) Next, assume that the user "Yamada Ako" (hereinafter, the "user") accesses a website to input billing information. This access is based on inputting the URL of the website.

[0171] 11 is displayed on the terminal device 2 of the user. The user also imports a PDF file of the invoice that he or she wishes to send. This imported invoice file is 1101. The user also inputs an invoice sender identifier 1102 and a delivery destination identifier 1103 on the screen of FIG. 11. The terminal reception unit 22 then receives the input of the invoice information 1101 (PDF file of the invoice), sender identifier 1102, and delivery destination identifier 1103.

[0172] Next, the user presses the send button 1104 in Fig. 11. The terminal processing unit 23 then uses the received invoice information, etc. to compose invoice information, etc. to be sent. Next, the terminal sending unit 24 sends the invoice information, etc. to the invoice processing device 1.

[0173] Next, the first receiving means 121 of the invoice processing device 1 receives the invoice information 1101, sender identifier 1102, and destination identifier 1103 from the sender's terminal device 2.

[0174] Next, the route acquisition unit 133 acquires the route identifier "web" of the route via the website. The route acquisition unit 133 acquires the route identifier "web" based on, for example, the URL.

[0175] Next, the management information acquisition unit 134 acquires from the received information management information which is a pair of a sender identifier and a destination identifier: sender identifier "<Company> Company A <Person in Charge> Yamada A", destination identifier "<Company> Company X <Person in Charge> Tanaka E"

[0176] Next, the output information acquisition unit 136 acquires the output information “<subcontract cost, <payment due date> end of current month, . . . ” that is paired with the acquired management information from the output information management table (FIG. 9).

[0177] Next, the storage unit 137 stores the received invoice information, the acquired management information "sender identifier "<company> Company A <person in charge> Yamada A", destination identifier "<company> Company X <person in charge> Tanaka E", the acquired route identifier "web", date, and the acquired output information "<subject> Outsourcing expenses, <payment due date> End of current month, ..." in the invoice management table (Figure 8). The stored record is the record with "ID=58" in Figure 8. It is assumed that the storage unit 137 has acquired the date from a clock (not shown).

[0178] Through the above process, billing information was sent and stored via the web. Output information such as subjects was also automatically stored.

[0179] (Example 3) Next, it is assumed that the user "Inoue B" (hereinafter, the user) starts up an email application on the terminal device 2 in order to send invoice information.

[0180] Then, the email application is started on the terminal device 2. Then, the user performs an operation to attach a separately prepared PDF file of an invoice as an attachment to the email. As a result, as shown in 1201 of FIG. 12, invoice information (PDF file) is attached (see 1201).

[0181] Also, assume that the user enters the email address "a002@b.jp" given by the operator of the invoice processing device 1 as the destination of the invoice for "Kinoshita F of Company Y" in the email address field (see 1202). Also assume that the user enters the title (1203) and body (1204) of the email and presses the send button 1205.

[0182] Then, the email in Figure 12 will be sent to the address "a002@b.jp".

[0183] Next, the second receiving means 122 of the invoice processing device 1 receives the invoice information, the title of the email, the body of the email, and the like by email.

[0184] Next, the route acquisition unit 133 detects that an e-mail has been received, and acquires the route identifier "e-mail".

[0185] Next, the management information acquisition unit 134 acquires the email address "a002@b.jp" of the email destination. Then, the management information acquisition unit 134 acquires the management information "sender identifier "<company> Company B <person in charge> Inoue B", destination identifier "<company> Company Y <person in charge> Kinoshita F"" that is paired with the acquired email address "a002@b.jp" from the management email information management table (FIG. 10).

[0186] Next, the output information acquisition unit 136 acquires the output information “<item> communication expenses, <payment due date> within 30 days, . . . ” that is paired with the acquired management information from the output information management table (FIG. 9).

[0187] Next, the content acquisition unit 135 acquires content information from the received e-mail. The content information includes a title "Sending an invoice for Internet line usage" and text information "To Mr. Kinoshita F of Company Y, This is Mr. Inoue B of Company B...".

[0188] Next, the storage unit 137 stores information including the received invoice information, the acquired management information, the acquired route identifier "email", the date, the acquired output information "<Subject> Communication Expenses, <Payment Due Date> Within 30 Days,...", the acquired content information (title "Sending invoice for Internet line usage", etc.) in the invoice management table (FIG. 8). The stored record is the record with "ID=59" in FIG. 8. This record also includes content information, but it is omitted in FIG. 8.

[0189] Through the above process, invoice information was sent and stored by email. In addition, management information and output information such as subjects were automatically stored.

[0190] (Example 4) Now, let us say that a user, "Aoki C of Company C," places the invoice paper in an envelope and mails the envelope to a specified mailing address (here, the operating company of invoice processing device 1) in order to send an invoice to "Fukuda G of Company Z." Then, let us say that the operating company of invoice processing device 1 receives the mailing from Aoki C.

[0191] Next, it is assumed that a worker at the operating company converts the invoice paper in the envelope into a PDF file, and then the worker starts an application for inputting invoice information, etc., in order to send the invoice information, etc., to the invoice processing device 1.

[0192] Then, it is assumed that the worker provides the PDF file of the invoice to the launched application and inputs the sender identifier and the destination identifier. It is also assumed that the worker selects the route "mail". An example of such a screen is shown in FIG. 13. In FIG. 13, 1301 is the PDF file of the invoice, 1302 is the sender identifier, 1303 is the destination identifier, and 1304 is the selected route. It is also assumed that the worker presses the send button 1305.

[0193] Next, the PDF file of the invoice, the sender identifier, the destination identifier, and the route identifier “mail” are transmitted from the terminal device 2 to the invoice processing device 1 .

[0194] Next, the third receiving means 123 of the invoice processing device 1 receives the invoice information, etc. Next, the route acquisition unit 133 acquires the route identifier "mail". In addition, the management information acquisition unit 134 acquires management information that is a pair of the received sender identifier and destination identifier.

[0195] Next, the output information acquisition unit 136 acquires the output information “<Subject> Advertising Expenses, . . . ” that is paired with the acquired management information from the output information management table (FIG. 9).

[0196] Next, the storage unit 137 stores a record having the received invoice information (Welsh file), management information, route identifier "mailing", date, and output information "<subject> advertising expenses,..." in the invoice management table (FIG. 8). This record is "ID=60" in FIG. 8.

[0197] Next, the address information composition unit 138 acquires the mailing address information "<Address> Toranomon, Minato-ku, Tokyo 105-0001...<Destination> XXXX Corporation, Invoice Management Center <Sender Identifier> $Sender Identifier <Destination Identifier> $Destination Identifier" from the mailing address storage unit 112. The address information composition unit 138 also uses the acquired mailing address information, sender identifier, and destination identifier to compose the address information "<Address> Toranomon, Minato-ku, Tokyo 105-0001...<Destination> XXXX Corporation, Invoice Management Center <Sender Identifier> C Company, Aoki Cko <Destination Identifier> Z Company, Fukuda Gko." Next, the address information output unit 142 transmits the constructed address information to the terminal device 2 of the worker who has transmitted the invoice information, etc. It is preferable that the address information output unit 142 substitutes the constructed address information into a template stored in the storage unit 11, constructs the address information in a format to be printed, and then transmits the address information.

[0198] Next, the terminal receiving unit 25 receives the address information from the invoice processing device 1. Next, the terminal processing unit 23 uses the received address information to compose address information to be printed. The terminal output unit 26 outputs the address information. An example of such output is shown in FIG. 14.

[0199] Next, the worker instructs the print button 1401. Then, the address for mailing the invoice paper (original) is printed. The worker attaches the printed address to an envelope, places the invoice paper (original) in the envelope, and mails the envelope to the "invoice management center" that manages the invoice paper (original).

[0200] In this way, the sending and storing of invoice information when the route is by mail was completed. In addition, support was provided for mailing the invoice form (original).

[0201] (Example 5) It is assumed that a user "Aoki C-ko" inputs an output instruction to the terminal device 2 to check whether the invoice form she sent by mail has been digitized and the invoice information, etc. has been stored in the invoice processing device 1. The output instruction has "<Sender Identifier> Company C, Aoki C-ko <Destination Identifier> Company Z, Fukuda G-ko".

[0202] Next, the terminal reception unit 22 receives an output instruction having the sender identifier and the destination identifier. Next, the terminal processing unit 23 composes an output instruction to be transmitted. The terminal transmission unit 24 transmits the output instruction to the invoice processing device 1.

[0203] Next, the output instruction receiving means 124 of the invoice processing device 1 receives the output instruction. Next, the invoice obtaining unit 139 obtains the invoice information etc. and the route identifier corresponding to the received output instruction from the invoice management table (FIG. 8). Here, it is assumed that the invoice obtaining unit 139 obtains the record with "ID=60" from FIG. 8.

[0204] Next, the invoice output unit 143 transmits the acquired invoice information and the route identifier "mail" to the terminal device 2 of Aoki C child.

[0205] Next, the terminal receiving unit 25 of the terminal device 2 receives the invoice information, etc. The terminal processing unit 23 uses the received invoice information, etc. to compose the invoice information, etc. to be output. The terminal output unit 26 outputs the invoice information, etc. An example of such output is shown in FIG. 15. In FIG. 15, invoice information (file) 1501, route identifier "mail" 1502, and item "advertising and promotion expenses" 1503 are output. Note that one of the route identifiers "web", "email", or "mail" is output to the field 1503.

[0206] By the above processing of this specific example, the invoice information is output on the same screen as the route identifier, subject, etc.

[0207] As described above, according to this embodiment, invoice information received through a plurality of routes can be collectively managed.

[0208] Furthermore, according to this embodiment, the route through which the invoice information was received can be ascertained.

[0209] Furthermore, according to this embodiment, it is possible to easily output the output information that is managed in association with the sender identifier and the destination identifier.

[0210] Furthermore, according to this embodiment, the subject can be easily obtained in response to the transmission of the invoice information.

[0211] Furthermore, according to this embodiment, it is possible to assist in the management of invoice forms received by mail.

[0212] Furthermore, according to this embodiment, it is possible to assist in the management of invoice information received by email.

[0213] In this embodiment, the invoice information can be sent via three routes: web, e-mail, and mail. However, in this embodiment, it is also possible to use only two of the three routes: web, e-mail, and mail.

[0214] The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. 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 for realizing the invoice processing device 1 in this embodiment is the following program. That is, this program is a program for making a computer function as a reception unit having two or more means among a first reception means for receiving invoice information from a terminal device, a second reception means for receiving invoice information by e-mail, and a third reception means for receiving invoice information based on a mailed invoice form, a route acquisition unit for acquiring a route identifier for identifying the route by which the reception unit accepted the invoice information, and a storage unit for pairing the invoice information accepted by the reception unit with the route identifier acquired by the route acquisition unit and storing it in an invoice storage unit in which the invoice information is stored.

[0215] Fig. 16 shows the external appearance of a computer that executes the programs described in this specification to realize the bill processing device 1 or terminal device 2 of the various embodiments described above. The above-mentioned embodiments can be realized by computer hardware and a computer program executed thereon. Fig. 16 is an overview of this computer system 300, and Fig. 17 is a block diagram of the system 300.

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

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

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

[0219] The program does not necessarily include an operating system (OS) or a third party program that causes the computer 301 to execute the functions of the invoice processing device 1 of the above-mentioned embodiment. The program only needs to include an instruction portion that calls appropriate functions (modules) in a controlled manner to achieve a desired result. How the computer system 300 operates is well known, and a detailed description will be omitted.

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

[0221] Furthermore, the computer that executes the above program may be a single computer or multiple computers. In other words, centralized processing or distributed processing may be performed. In other words, the invoice processing device 1, etc. may be a standalone device or may be composed of two or more devices.

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

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

[0224] INDUSTRIAL APPLICABILITY As described above, the invoice processing device according to the present invention has the effect of being able to collectively manage invoice information received through a plurality of routes, and is useful as an invoice processing server or the like. [Explanation of symbols]

[0225] A. Invoice processing system 1. Invoice Processing Device 2 Terminal Equipment 11 Storage area 12 Reception 13 Processing section 14 Output section 21 Terminal storage section 22 Terminal Reception 23 Terminal Processing Section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Section 111 Bill storage section 112 Mailing address storage section 113 Output information storage section 114 Management mail information storage section 121 First reception method 122 Secondary reception method 123 Third Reception Method 124 Output instruction receiving means 125 Management information reception means 131 Unique Address Acquisition Unit 132 Management Email Information Registration Section 133 Route Acquisition Department 134 Management information acquisition department 135 Content acquisition part 136 Output information acquisition unit 137 Storage Unit 138 Address information component 139 Bill Acquisition Department 141 Output information output section 142 Address information output section 143 Invoice Printing Section

Claims

1. a reception unit including a second reception means for receiving bill information by e-mail, and including at least one of a first reception means for receiving bill information from a terminal device and a third reception means for receiving bill information based on a bill form sent by mail; a route acquisition unit that acquires a route identifier that identifies a route through which the invoice information was received by the reception unit; a management information acquisition unit that, when the second reception unit receives invoice information by email, acquires an email address of a destination of the email and acquires management information paired with the email address from a management email information storage unit that stores one or more pieces of management email information having management information, which is a pair of a sender identifier and a destination identifier, and an email address; an invoice processing device comprising: a storage unit that stores the invoice information accepted by the acceptance unit in an invoice storage unit in which invoice information is stored, pairing the invoice information accepted by the acceptance unit with a route identifier acquired by the route acquisition unit and the management information acquired by the management information acquisition unit.

2. a reception unit including a second reception means for receiving bill information by e-mail, and including at least one of a first reception means for receiving bill information from a terminal device and a third reception means for receiving bill information based on a bill form sent by mail; a route acquisition unit that acquires a route identifier that identifies a route through which the invoice information was received by the reception unit; a content acquisition unit for acquiring content information, which is body information or a title of the e-mail; an invoice processing device comprising: a storage unit that pairs the invoice information and content information accepted by the acceptance unit with the route identifier acquired by the route acquisition unit and stores them in an invoice storage unit in which invoice information is stored.

3. The reception unit is 3. The invoice processing device according to claim 1, further comprising: said first receiving means, said second receiving means and said third receiving means.

4. The reception unit is The device further includes an output instruction receiving means for receiving an instruction to output the invoice information, 4. The invoice processing device according to claim 1, further comprising an invoice output unit that obtains invoice information corresponding to the output instruction from the invoice storage unit and outputs the invoice information together with a route identifier that pairs with the invoice information.

5. The reception unit is a management information receiving means for receiving management information which is a pair of a sender identifier for identifying a sender of the invoice and a destination identifier for identifying a destination of the invoice; an output information acquisition unit that acquires output information paired with the management information accepted by the management information acceptance unit from an output information storage unit in which the output information is stored, in association with one or more pieces of management information; The invoice processing device according to claim 1 , further comprising an output information output unit that outputs the output information.

6. The output information is a subject, The output information output unit 6. The invoice processing device according to claim 5, wherein when the reception section receives the management information together with the invoice information, the reception section transmits the output information to the terminal device that transmitted the invoice information.

7. The reception unit includes the third reception means, an address information configuration unit that acquires mailing address information from a mailing address storage unit in which mailing address information relating to the mailing address of the invoice form is stored, and configures address information for mailing the invoice form; 7. The invoice processing device according to claim 1, further comprising an address information output unit for outputting the address information.

8. The reception unit is a management information receiving means for receiving management information which is a set of a sender identifier and a destination identifier; a unique address acquisition unit that acquires a unique email address in response to receipt of the management information; An invoice processing device as described in claims 1 to 7, further comprising a management mail information registration unit that accumulates the management information accepted by the management information accepting means and management mail information having the unique email address in a management mail information storage unit that stores one or more pieces of management mail information.

9. A bill processing method comprising all of the processes performed by the bill processing device according to any one of claims 1 to 8.

10. Computer, A program for causing the invoice processing device according to any one of claims 1 to 8 to function as such an invoice processing device.

Images