JP2022110630A - Invoice processing device, invoice processing method, and program - Google Patents

Abstract

Problem: In the prior art, it was not possible to collectively manage invoice information received via multiple routes.Solution: An invoice processing device 1 including a reception unit 12 equipped with two or more means of a first reception means 121 for receiving invoice information from a terminal device 2, a second reception means 122 for receiving invoice information by e-mail, and a third reception means 123 for receiving invoice information based on a mailed invoice form, a route acquisition unit 133 for acquiring a route identifier specifying the route by which the reception unit 12 received the invoice information, and a storage unit 137 for pairing the invoice information received by the reception unit 12 with the route identifier acquired by the route acquisition unit 133 and storing it in an invoice storage unit 111 in which invoice information is stored, can collectively manage invoice information received via multiple routes. [Selected Figure] Figure 3

Description

Patent Act Article 30, Paragraph 2 application filed April 26, 2020, April 27, 2020, April 28, 2020, April 30, 2020, Reiwa 2 May 1, 2020, May 6, 2020, May 7, 2020, May 8, 2020, May 11, 2020, May 12, 2020 , May 13, 2020, May 14, 2020, May 15, 2020, May 18, 2020, May 19, 2020, 2020 May 20, May 21, 2020, May 22, 2020, May 26, 2020, May 27, 2020, May 28, 2020, May 31, 2020, June 1, 2020, June 2, 2020, June 3, 2020, June 8, 2020, June 2020 June 9, 2020, June 10, 2020, June 11, 2020, June 12, 2020, June 15, 2020, June 16, 2020, Reiwa June 17, 2020, June 18, 2020, June 19, 2020, June 20, 2020, June 21, 2020, June 2020 22nd, June 23, 2020, June 24, 2020, June 25, 2020, June 26, 2020, June 27, 2020, Reiwa June 28, 2020, June 29, 2020, June 30, 2020, July 1, 2020, July 2, 2020, July 3, 2020 July 5, 2020, July 6, 2020, July 7, 2020, July 8, 2020, July 9, 2020, Reiwa 2 July 10, 2020, July 12, 2020, July 13, 2020, July 14, 2020, July 15, 2020, July 16, 2020 , July 17, 2020, July 19, 2020, July 20, 2020, July 21, 2020, July 22, 2020, 2020 July 23, July 24, 2020, July 27, 2020, July 28, 2020, July 29, 2020, July 30, 2020, July 31, 2020, August 1, 2020, August 3, 2020, August 4, 2020, August 5, 2020, August 2020 August 6, 2020, August 7, 2020, August 11, 2020, August 12, 2020, August 13, 2020, August 14, 2020, Reiwa August 17, 2020, August 18, 2020, August 19, 2020, August 20, 2020, August 21, 2020, August 2020 24th, August 25, 2020, August 26, 2020, August 27, 2020, August 28, 2020, August 29, 2020, Reiwa August 31, 2nd year,

Patent Law Article 30, Paragraph 2 applied September 1, 2020, September 2, 2020, September 3, 2020, September 4, 2020, Reiwa 2 September 7, 2020, September 8, 2020, September 9, 2020, September 10, 2020, September 11, 2020, September 12, 2020 , September 13, 2020, September 14, 2020, September 15, 2020, September 16, 2020, September 17, 2020, 2020 September 18, September 19, 2020, September 20, 2020, September 21, 2020, September 22, 2020, September 23, 2020, September 24, 2020, September 25, 2020, September 26, 2020, September 27, 2020, September 28, 2020, September 2020 29th of the month, September 30, 2020, October 1, 2020, October 2, 2020, October 5, 2020, October 6, 2020, Reiwa October 7, 2020, October 8, 2020, October 9, 2020, October 10, 2020, October 12, 2020, October 2020 13th, October 14, 2020, October 15, 2020, October 16, 2020, October 17, 2020, October 18, 2020, Reiwa October 19, 2020, October 20, 2020, October 21, 2020, October 22, 2020, October 23, 2020, October 25, 2020 October 26, 2020, October 27, 2020, October 28, 2020, October 29, 2020, October 30, 2020, Reiwa 2 October 31, 2020, November 2, 2020, November 4, 2020, November 5, 2020, November 6, 2020, November 7, 2020 , November 9, 2020, November 10, 2020, November 11, 2020, November 12, 2020, November 13, 2020, 2020 November 14, November 16, 2020, November 17, 2020, November 18, 2020, November 19, 2020, November 20, 2020, November 21, 2020, November 22, 2020, November 23, 2020, November 24, 2020, November 25, 2020, November 2020 26th of the month, November 27, 2020, November 28, 2020, November 29, 2020, November 30, 2020,

Patent Act Article 30, Paragraph 2 application filed December 1, 2020, December 2, 2020, December 3, 2020, December 4, 2020, Reiwa 2 December 5, 2020, December 7, 2020, December 8, 2020, December 9, 2020, December 10, 2020, December 11, 2020 , December 12, 2020, December 13, 2020, December 14, 2020, December 15, 2020, December 16, 2020, 2020 December 17, December 18, 2020, December 19, 2020, December 20, 2020, December 21, 2020, December 22, 2020, December 23, 2020, December 24, 2020, December 25, 2020, December 26, 2020, December 27, 2020, December 2020 December 28, 2020, December 29, 2020, December 30, 2020, January 3, 2021, January 4, 2021, January 5, 2021, Reiwa January 6, 3rd year of Reiwa, January 7th, 3rd year of Reiwa, January 8th, 1st year of Reiwa, January 9th, 1st year of Reiwa, January 10th, 1st year of Reiwa, January 3rd year of Reiwa 11th, January 12, 2021, January 13, 2021, January 14, 2021, January 15, 2021, January 16, 2021, Reiwa Announced through individual sales on January 17, 3,

Patent Law Article 30, Paragraph 2 application filed April 24, 2020 https://jp. corp-sansan. com/news/2020/bill-one_launch. html, https://bill-one. com/, https://bill-one. com/#feature, https://bill-one. com/#works, https://bill-one. com/#step, https://bill-one. com/#qa, https://www. business insider. jp/post-211835, https://www. nikkei. com/article/DGXMZO58439050U0A420C2X30000/, https://www. business insider. jp/post-211835, https://www. nikkei. com/article/DGXMZO58439050U0A420C2X30000/, https://www. nikkei. com/article/DGXLASFL24HD0_U0A420C2000000/, https://www. watch. impress. co. jp/docs/news/1249320. html, https://saleszine. jp/news/detail/1441, https://news. my navi. jp/article/20200424-1023377/, https://japan. cnet. com/article/35152934/, https://japan. zdnet. com/article/35152942/, https://bizzine. Announced via jp/article/detail/4579, May 11, 2020 https://app. bill-one. com/sender/invoices, June 24, 2020 https://active. nikkeibp. co. jp/atcl/act/19/00005/061600232/? Announced through i_cid=nbpnxta_top, July 13, 2020 https://www. nikkei. com/article/DGXMZO61383660Q0A710C2TJ1000/,

Applied for application of Article 30, Paragraph 2 of the Patent Act July 14, 2020 Announced in "Nihon Keizai Shimbun July 14, 2020 morning edition page 12" published by Nikkei Inc., Reiwa 2 September 9, https://jp. corp-sansan. com/news/2020/billone_happo-en. html, https://www. it media. co. jp/business/articles/2009/09/news040. Announced through html, September 11, 2020 https://saleszine. Announced via jp/news/detail/1847, November 4, 2020 https://cloud. watch. impress. co. jp/docs/news/1286973. html, https://news. my navi. jp/article/20201104-1452316/, https://www. nikkei. com/article/DGXMZO65818260U0A101C2X30000/, November 5, 2020 https://saleszine. jp/news/detail/1995, https://www. weekly bcn. com/journal/news/detail/20201105_178080. Announced through html, November 14, 2020 https://jp. corp-sansan. com/news/2020/billone_obc. Announced through html, November 16, 2nd year of Reiwa Announced on page 5 of Nikkei Sangyo Shimbun dated November 16, 2nd year of Reiwa, published by Nikkei Inc., November 30, 2nd year of Reiwa, BCN Co., Ltd. Published in “Weekly BCN November 30, 2020 Vol.1852 p13”, November 30, 2020 https://www. weekly bcn. com/journal/news/detail/20201203_178643. announced through html,

Patent Law Article 30, Paragraph 2 application filed December 14, 2020 https://jp. corp-sansan. com/news/2020/billone_yayoi. html, https://jp. corp-sansan. com/news/2020/billone-peppol. html, https://news. my navi. jp/article/20201214-1590111/, https://digital-shift. jp/flash_news/FN201214_3, https://aiocr. news/%E5%BC%A5%E7%94%9F%E4%BC%9A%E8%A8%88%E3%83%A9%E3%82%A4%E3%83%B3%E3%82%A2 %E3%83%83%E3%83%97%E3%81%A8sansan%E3%81%8C%E6%89%8B%E6%8E%9B%E3%81%91%E3%82%8B%E8 Announced through %AB%8B%E6%B1%82%E6%9B%B8%E3%81%AE%E3%82%AA/, December 15, 2020 https://sogyotecho. Announced through jp/news/20201215yayoi-sansan/, December 22, 2020 https://internet. watch. impress. co. jp/docs/news/1296655. html, January 14, 2021 https://jp. corp-sansan. com/news/2021/bill-one_kintone. html, https://enterprisezine.com. Announced via jp/news/detail/13819, January 15, 2021 https://saleszine. Announced via jp/news/detail/2191

TECHNICAL FIELD The present invention relates to a bill processing apparatus or the like that receives and stores bill information.

Conventionally, this is an invoice processing device that performs processing related to invoice information, and it is an invoice processing that can easily check whether there are any billing omissions when reissuing invoices that have been issued once by integrating or dividing them. There was a device (see, for example, Patent Document 1).

JP 2019-114122 A

However, in the prior art, bill information received through multiple routes could not be collectively managed.

The bill processing device of the first invention comprises first reception means for receiving bill information from a terminal device, second reception means for receiving bill information by electronic mail, and a receiving unit including two or more means of third receiving means for receiving invoice information, a route obtaining unit for obtaining a route identifier specifying a route through which the receiving unit receives bill information, and a receiving unit receiving an accumulation unit for pairing the obtained bill information with the route identifier obtained by the route acquisition unit and accumulating the bill information in a bill storage unit in which the bill information is stored.

With such a configuration, it is possible to collectively manage invoice information received through a plurality of routes.

Further, the bill processing device of the second aspect of the invention is the bill processing device in which the receiving unit comprises first receiving means, second receiving means, and third receiving means, in contrast to the first invention. be.

With this configuration, invoice information received through at least three routes can be collectively managed.

Further, in the bill processing apparatus of the third invention, in contrast to the first or second invention, the receiving unit further comprises output instruction receiving means for receiving an instruction to output the bill information, and responds to the output instruction. The invoice processing apparatus further comprises an invoice output unit that acquires invoice information from an invoice storage unit and outputs the invoice information together with a route identifier paired with the invoice information.

With such a configuration, it is possible to manage the route through which each piece of bill information is received in a situation where bill information can be received through a plurality of routes.

In addition, in the bill processing device of the fourth invention, for any one of the first to third inventions, the reception unit stores a sender identifier for identifying the sender of the invoice and the recipient of the invoice. a management information receiving means for receiving management information paired with a destination identifier for identification, and output information paired with the management information received by the management information receiving means is associated with each of the one or more pieces of management information, The invoice processing apparatus further includes an output information acquisition unit that acquires output information from an output information storage unit, and an output information output unit that outputs the output information.

With this configuration, it is possible to easily output the output information managed in association with the source identifier and the destination identifier.

In addition, in the bill processing device of the fifth invention, in contrast to the fourth invention, the output information is the subject, and the output information output unit is the receiving unit when the management information is received together with the bill information Second, the bill processing device transmits output information to the terminal device that has transmitted the bill information.

With such a configuration, it is possible to easily acquire the subject corresponding to the set of the sender and the receiver of the invoice.

In addition, in the bill processing device of the sixth invention, the reception unit comprises third reception means for any one of the first to fifth inventions, and the mailing address information regarding the mailing address of the billing form further comprising an address information construction unit that acquires the mailing address information from the mailing address storage unit in which is stored and configures the address information for mailing the billing form, and an address information output unit that outputs the address information. It is an invoice processor.

Such a configuration can assist in managing billing forms received by mail. Specifically, the address information for mailing the billing form can be output to the destination that manages the billing form.

Further, in the bill processing device of the seventh invention, for any one of the first to sixth inventions, the bill storage unit stores one or more pieces of bill information as sender identifiers and receiver identifiers. The reception unit includes a second reception means, and when the second reception means receives the invoice information by email, the destination of the email is stored in association with the management information that is a pair of and a management information acquisition unit that 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 the management information and the email address. The storage unit is a bill processing device that stores the bill information received by the second reception means in association with the management information acquired by the management information acquisition unit.

With such a configuration, it is possible to support the management of invoice information received by e-mail. Specifically, the e-mail address of the destination of the e-mail is acquired, and using the e-mail address, the invoice sender identifier and recipient identifier are automatically acquired, and the invoice information and the sender identifier are automatically acquired. Destination identifiers can be managed.

In addition, in the bill processing device of the eighth invention, in any one of the first to seventh inventions, the reception unit comprises second reception means, and the content which is text information or title of the e-mail The content acquisition unit for acquiring information and the storage unit are a bill processing device that also stores the content information in a pair with the bill information received by the reception unit.

With such a configuration, it is possible to support the management of invoice information received by e-mail. Specifically, the title or text of the mail can also be managed in pairs with the invoice information.

Further, in the invoice processing apparatus of the ninth invention, in contrast to the seventh or eighth invention, the reception unit includes management information reception means for receiving management information that is a set of a sender identifier and a recipient identifier. a unique address obtaining unit for obtaining a unique mail address in response to reception of management information; management information received by the management information receiving means; and management mail information having a unique mail address. The invoice processing apparatus further comprises a management mail information registration unit for storing management mail information in a management mail information storage unit.

With such a configuration, it is possible to support the management of invoice information received by e-mail. Specifically, a source identifier, a destination identifier, and a unique e-mail address can be associated and registered.

According to the invoice processing apparatus of the present invention, invoice information received through a plurality of routes can be collectively managed.

Conceptual diagram of invoice processing system A in Embodiment 1 Block diagram of the invoice processing system A Block diagram of the invoice processing device 1 Flowchart explaining an operation example of the bill processing device 1 Flowchart explaining an operation example of the bill processing device 1 Flowchart for explaining an operation example of the terminal device 2 of the user who is the sender or receiver of the invoice Flowchart explaining an operation example of the same worker's terminal device 2 Diagram showing the invoice management table Diagram showing the same output information management table Diagram showing the same management mail information management table Diagram showing an example of the same input screen Diagram showing a screen example of the same email Diagram showing an example of the same input screen Diagram showing an example of the same output screen Diagram showing an example of the same output screen Overview of the computer system Block diagram of the same computer system

Embodiments of an invoice processing device and the like will be described below with reference to the drawings. It should be noted that, since components denoted by the same reference numerals in the embodiments perform similar operations, repetitive description may be omitted.

(Embodiment 1)
In this embodiment, at least two of the three routes of uploading invoice information, receiving invoice information by e-mail, and accepting input of invoice information based on mailed invoice forms , describes a bill processing device capable of accepting bill information. Invoice information received through two or more routes is normally accumulated and can be collectively managed.

In addition, in the present embodiment, a bill processing apparatus that can store and manage bill information in pairs with a route identifier that identifies a receipt route for bill information will be described.

In addition, in the present embodiment, one or more pieces of output information paired with a pair of a sender and a recipient are managed, and the output information can be output in association with the invoice information corresponding to the pair. A document processing device will be described. Note that the output information is, for example, subjects.

In addition, in the present embodiment, a bill processing apparatus for supporting mailing of mailed bill sheets for management of the bill sheets will be described. Note that the support for mailing is, for example, the output of address information.

In addition, in the present embodiment, regarding an invoice processing apparatus that stores invoice information received by e-mail in a pair with sender and destination information paired with the e-mail address of the sender of the e-mail. explain.

Further, in the present embodiment, an invoice processing apparatus for storing invoice information received by e-mail in association with text information or a title of the e-mail will be described.

Furthermore, in the present embodiment, a registration process of receiving management information having a sender and a destination, obtaining a unique mail address, and registering management mail information having the mail address, the sender, and the destination is performed. A bill processing device that can be performed will be described.

FIG. 1 is a conceptual diagram of an invoice processing system A according to this embodiment. An invoice processing system A includes an invoice processing device 1 and one or more terminal devices 2 . The bill processing device 1 is a so-called server.

The bill processing device 1 is, for example, a cloud server or an ASP server, but the type is not limited. The bill processing device 1 is a device that normally receives and manages bill information. The terminal device 2 is a so-called personal computer, a smart phone, or a tablet terminal, but the type is not limited. The terminal device 2 is a terminal used by a user who transmits bill information. The terminal device 2 is a terminal used by a user who is the source or destination of bill information (it can be called a first terminal), or a worker who inputs bill information based on a transported bill sheet. It is a terminal to be used (which may be called a second terminal).

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

FIG. 2 is a block diagram of invoice processing system A according to this embodiment. FIG. 3 is a block diagram of the invoice processing device 1.

The invoice processing device 1 includes a storage unit 11 , a reception unit 12 , a processing unit 13 and an output unit 14 . Storage unit 11 includes bill storage unit 111 , mailing address storage unit 112 , output information storage unit 113 , and management mail information storage unit 114 . The reception unit 12 includes first reception means 121 , second reception means 122 , third reception means 123 , output instruction reception means 124 , and management information reception means 125 . The processing unit 13 includes 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, an accumulation unit 137, an address information configuration unit 138, and an invoice acquisition unit 139 . The output unit 14 includes an output information output unit 141 , an address information output unit 142 and an invoice output unit 143 .

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

Various types of information are stored in the storage unit 11 that constitutes the invoice processing apparatus 1 . Various types of information are, for example, billing information, which will be described later, and mailing address information, which will be described later.

The bill storage unit 111 stores one or more pieces of bill information. Each piece of billing information is usually stored in association with management information. The management information is a set of a source identifier and a destination identifier.

The sender identifier is information that identifies the sender of the invoice. It can be said that the sender of the invoice is the issuer of the invoice. It may be considered that the sender identifier is information that identifies the sender 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, the invoice issuer company identifier and department identifier.

The delivery destination identifier is information for identifying the delivery destination of the invoice. It can be said that the billing address is the billing address. The destination identifier may be thought of as information identifying the party being requested. The sender identifier is, for example, the company name and the person in charge of the requesting party, the company name and department name of the requesting party, the company identifier and the person in charge of the requesting party, the company identifier and the person in charge of the requesting party. This is the department identifier.

The invoice information may be associated with other information such as a route identifier, date, and output information, which will be described later.

The invoice storage unit 111 is normally provided in the invoice processing apparatus 1, but may be provided in an external device.

The mailing address storage unit 112 stores mailing address information regarding the mailing address of the billing form. The mailing address information is usually the information of the place where the invoice form is stored and managed. The mailing address information has a mailing address. The mailing address information includes, for example, postal code and address. A billing form is a paper bill. The mailing address storage unit 112 is normally provided in the invoice processing device 1, but may be provided in an external device.

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 invoice sender and sender, and is information to be output. The output information is, for example, subjects. The output information is, for example, information on the payment deadline (for example, "within 30 days after issuing the bill"). However, output information does not matter. It is preferable that the output information is determined information in which the billing source and destination are determined.

The management mail information storage unit 114 stores one or more pieces of management mail information. The management email information is email address information for each piece of management information. The management mail information is information having management information and mail addresses. It is preferable that the mail address is unique for each piece of management information. The mail address is the address specified as the destination of the e-mail when the receipt information is sent by e-mail.

The reception unit 12 receives various information, instructions, and the like. Various types of information and instructions are, for example, invoice information, output instructions, and management information.

Here, acceptance generally means reception of information transmitted via a wired or wireless communication line. However, reception is a concept that includes reception of information input from input devices such as keyboards, mice, and touch panels, and reception of information read from recording media such as optical disks, magnetic disks, and semiconductor memories. good.

The first receiving means 121 receives bill information from the terminal device 2 . The first receiving means 121 normally receives bill information via the Internet. The first receiving means 121 normally receives invoice information uploaded from the terminal device 2 . The person who enters such invoice information is usually the issuer of the invoice (person in charge of the issuing organization). The first receiving unit 121 may receive management information as well as invoice information. The invoice information here is information input from the screen of the terminal device 2, for example. The invoice information is a file uploaded from the terminal device 2, for example. The first receiving means 121 may receive the sender identifier and the receiver identifier in addition to the invoice information. Further, when the invoice information is a file, the first receiving unit 121, for example, retrieves a character string of information in the invoice information (for example, the address of the invoice, the amount charged, the sender of the invoice, etc.). , may be received in addition to billing information. The invoice file is preferably in PDF format, but the format and structure of the file do not matter.

The second reception means 122 receives bill information by e-mail. The person who enters such billing information is typically the billing issuer. Also, such invoice information is usually an attached file, but may be information described in the text of the email. E-mail usually has title and body information in addition to billing information. The second receiving means 122, for example, inspects a predetermined mailbox storage area (not shown) for each email address, determines whether or not the email exists, and determines whether the email exists. If so, retrieve the email from the mailbox.

It is preferable that the web page or application for inputting the bill information of the terminal device 2 of the worker and the web page or application for inputting the bill information etc. of the terminal device 2 of the sender are different. , can be the same. If they are the same, the user identifier of the input user may distinguish whether the user is the sender or the worker, and the received information may include the route identifier. In other words, it is only necessary for the first reception unit 121 and the second reception unit 122 to acquire the correct route identifier by some method.

The third reception means 123 receives bill information based on the mailed bill form. The person who enters such billing information is usually not the billing issuer, but the worker to whom the billing form is mailed. It does not matter how the worker enters the invoice information. The invoice information may be a file or a collection of character strings, and its structure does not matter. For example, the worker uses the terminal device 2 to upload a file, which is invoice information created from invoice sheets, to the invoice processing apparatus 1 . The third receiving means 123 receives, for example, character strings of information in the invoice information (eg, invoice address, invoice amount, invoice sender, etc.) in addition to the invoice information. Also good.

The output instruction accepting means 124 accepts an instruction to output invoice information. The output instructions preferably have information specifying billing information. The output instruction includes, for example, one or more information among an identifier of invoice information, a sender identifier, and a sender identifier. The output instruction has, for example, period information specifying a period. The output instruction includes, for example, a search formula for searching bill information from the bill storage unit 111 .

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 recipient identifier that identifies the recipient of the invoice. The acceptance of management information is for registration of management mail information.

The processing unit 13 performs various types of processing. The various processes are, for example, processes performed by the unique address acquisition unit 131, the management mail information registration unit 132, the route acquisition unit 133, and the like.

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 of being able to grasp the usage status of each route, it becomes possible to review the business such as improvement of the invoice processing apparatus 1 and change in hiring of workers.

The processing unit 13, for example, calculates the ratio of invoice information for each sender identifier, and outputs the usage ratio for each sender identifier and for each route. As a result, for example, it is possible to take measures such as giving guidance to senders, who often send by mail, to increase the number of sending by web or e-mail.

For example, the processing unit 13 acquires information about the content of the invoice from the invoice information, which is a received file. Information related to the contents of the invoice includes, for example, a sender identifier, a receiver identifier, an amount, a payment deadline, and the like. The processing unit 13 acquires information about the contents of the invoice from the invoice information, which is a PDF file, for example. For example, the processing unit 13 performs character recognition processing on the invoice information, which is an image, to acquire information about the contents of the invoice. In such a case, for example, the storage unit 11 stores information about the format of the invoice (for example, coordinate information describing the company name of the sender, coordinate information describing the company name of the sender, coordinate information containing the name of the person in charge, coordinate information containing the name of the person in charge of the sender, and coordinate information containing the amount of money). , to obtain information about the contents of the invoice from the invoice information.

For example, the processing unit 13 acquires from the storage unit 11 the e-mail address of the person in charge of the destination that is paired with the identifier of the destination corresponding to the received e-mail, and stores the e-mail address corresponding to the identifier of the person in charge of the destination (e.g., e-mail address). Notify the recipient that the billing information has been received. Any means of notification may be used. The processing unit 13 notifies, for example, by e-mail. For example, the processing unit 13 forwards the received e-mail to the destination person in charge identifier. Note that the content of the notification does not matter.

The unique address acquisition unit 131 acquires a unique e-mail address in response to receiving the management information. It doesn't matter how you get the unique email address. The unique address acquisition unit 131 increments, for example, the numeric part of the e-mail address, and increments the numeric part of the recently generated e-mail address to generate a replacement e-mail address. The unique address acquisition unit 131 reads, for example, unused e-mail addresses from two or more e-mail address sets.

The management mail information registration unit 132 stores management mail information having the management information received by the management information reception unit 125 and the unique mail address acquired by the unique address acquisition unit 131 in the management mail information storage unit 114 . Through such processing, the registration of the management mail information is performed.

The route acquisition unit 133 acquires a route identifier that identifies the route from which the reception unit 12 received the invoice information. A route can be called a means. In other words, the route identifier is, for example, information specifying whether the bill information is received by the first receiving means 121, the second receiving means 122, or the third receiving means 123. FIG. In the case of the first receiving means 121, for example, the route identifier is "web". In the case of the second receiving means 122, for example, the route identifier is "e-mail". In the case of the third receiving means 123, for example, the route identifier is "mail".

The route acquisition unit 133 acquires, for example, a route identifier specifying which of the first reception unit 121, the second reception unit 122, and the third reception unit 123 received the invoice information. The route acquisition unit 133 detects, for example, which means among the first receiving means 121, the second receiving means 122, and the third receiving means 123 has received the invoice information, and obtains a route identifier based on the detection result. get. The route acquisition unit 133 may acquire the route identifier received by the first reception unit 121, the second reception unit 122, or the third reception unit 123, for example. Such route identifiers are, for example, information entered by a user entering billing information.

When the second receiving means 122 receives the invoice information by e-mail, the management information acquisition unit 134 acquires the e-mail address of the destination of the e-mail, and stores the management information paired with the e-mail address as the management mail information. Acquired from the storage unit 114 . The technology for acquiring the destination mail address of the received e-mail is a well-known technology, and detailed description thereof will be omitted.

The content acquisition unit 135 acquires the content information, which is the text information or the title of the e-mail, from the received e-mail. The content information may be the e-mail itself.

The output information acquisition unit 136 acquires output information paired with the management information received by the management information reception unit 125 from the output information storage unit 113 . Note that the output information is, for example, the item and the payment due date.

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 bill information in the bill storage unit 111 regardless of the route through which the bill information was received. In this way, invoice information received through two or more routes can be collectively managed.

The storage unit 137 preferably stores the invoice information received by the reception unit 12 in the invoice storage unit 111 in a pair with the route identifier acquired by the route acquisition unit 133 .

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

The accumulation unit 137 also accumulates the content information of the received e-mail in a pair with the invoice information received by the second reception unit 122 . By doing so, for example, background information at the time of sending billing information can be obtained later.

The address information constructing unit 138 acquires the mailing address information from the mailing address storage unit 112, and uses the mailing address information to construct the address information for mailing the billing form. It is preferable that the address information construction unit 138 automatically acquires the address information in response to the receipt of the bill information by the third receiving means 123 .

The invoice acquisition unit 139 acquires one or more items 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 the invoice information and the like corresponding to the received output instruction and the route identifier.

The output unit 14 outputs various information. Various types of information are, for example, invoice information, output information, and address information.

Here, the output usually means transmission to the terminal device 2, but display on a display, projection using a projector, printing on a printer, storage on a recording medium, other processing devices, other programs, etc. It may be a concept including delivery of processing results to.

The output information output unit 141 outputs one or more pieces of output information acquired by the output information acquisition unit 136 . 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 has received the management information together with the invoice information. . The output information output unit 141 outputs the destination identifier and the sender identifier obtained from the bill information by the processing unit 13 together with the bill information when the reception unit 12 receives bill information in the form of a file. can be

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

Invoice output unit 143 outputs the invoice information acquired by 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 bill output unit 143 normally transmits bill information to the terminal device 2 .

Various types of information are stored in the terminal storage unit 21 that constitutes the terminal device 2 . Various types of information are, for example, a source identifier and a destination identifier.

The terminal reception unit 22 receives various information, instructions, and the like. Various types of information and instructions include, for example, URI or URL for accessing a website for entering invoices, instructions to launch an invoice entry application, instructions to launch an e-mail application, invoice information, management information,
This is an output instruction. A bill input application is an application for inputting bill information. An e-mail application is an application for sending e-mails.

Here, reception means reception of information input from input devices such as keyboards, mice, and touch panels, reception of information transmitted via wired or wireless communication lines, and recording on optical discs, magnetic discs, semiconductor memories, etc. This is a concept that includes acceptance of information read from a medium.

Any means such as a touch panel, a keyboard, a mouse, or a menu screen may be used as input means for various information and instructions.

The terminal processing unit 23 performs various types of processing. The various types of processing are, for example, processing for converting received information, instructions, etc. into information, instructions, etc. of a structure to be transmitted. The various types of processing are, for example, processing of converting received information into information having a structure to be output.

The terminal transmission unit 24 transmits various information, instructions, etc. to the invoice processing apparatus 1 . Various information and instructions are, for example, invoice information, e-mail, output instructions, and management information.

The terminal reception unit 25 receives various information from the bill processing device 1 . Various types of information are, for example, invoice information, output information, and address information.

The terminal output unit 26 outputs various information. Various types of information are, for example, invoice information, output information, and address information.

Here, output means 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 transmission to another processing device or other program. This is a concept that includes delivery of processing results.

The storage unit 11, the bill storage unit 111, the mailing address storage unit 112, the output information storage unit 113, the management mail information storage unit 114, and the terminal storage unit 21 are preferably non-volatile recording media. A recording medium can also be used.

It does not matter how the information is stored in the storage unit 11 or the like. For example, information may be stored in the storage unit 11 or the like via a recording medium, or information transmitted via a communication line or the like may be stored in the storage unit 11 or the like. Alternatively, information input via an input device may be stored in the storage unit 11 or the like.

The reception unit 12, the first reception unit 121, the second reception unit 122, the third reception unit 123, the output instruction reception unit 124, the management information reception unit 125, and the terminal reception unit 25 are usually wireless or wired communication means. Although implemented, it may be implemented by means of receiving broadcasts.

a processing unit 13, 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, an accumulation unit 137, an address information configuration unit 138, and The terminal processing unit 23 can usually be implemented by a processor, memory, or the like. The processing procedure of the processing unit 13 and the like is normally realized by software, and the software is recorded in a recording medium such as a ROM. However, it may be realized by hardware (dedicated circuit). Note that the processor is, for example, a CPU, MPU, GPU, or the like, and any type of processor does not matter.

The output unit 14, the output information output unit 141, the address information output unit 142, the bill output unit 143, the terminal transmission unit 24, and the terminal output unit 26 are usually realized by wireless or wired communication means, but broadcasting means It may be realized by

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

The terminal output unit 26 may or may not include an output device such as a display or speaker. The terminal output unit 26 can be realized by output device driver software, or by output device driver software and an output device.

Next, an operation example of the invoice processing system A will be described. First, an operation example of the invoice processing apparatus 1 will be described with reference to the flow charts of FIGS. 4 and 5. FIG.

(Step S401) The first receiving means 121 determines whether or not the invoice information or the like has been received from the terminal device 2 of the sender of the invoice information. If bill information etc. have been received, the process goes to step S402, and if bill information etc. have not been received, the process goes to step S407.

Note that the invoice information and the like here may be invoice information only. The billing information and the like preferably includes billing information, a sender identifier, and a sender identifier.

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

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

(Step S404) The output information acquisition unit 136 acquires from the output information storage unit 113 the output information paired with the management information acquired in step S403.

(Step S405) The accumulation unit 137 configures information having the invoice information received in step S401, the route identifier "web" acquired in step S402, and the output information acquired in step S404.

(Step S406) The accumulation unit 137 accumulates the information configured in step S405 in the invoice storage unit 111. FIG. Return to step S401.

(Step S407) The second reception unit 122 determines whether or not the invoice information or the like has been received by e-mail. If bill information etc. have been received, the process goes to step S408, and if bill information etc. have not been received, the process goes to step S415.

Note that the invoice information and the like here may be invoice information only. The billing information and the like preferably includes billing information, a sender identifier, and a sender identifier.

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

(Step S409) The management information acquisition unit 134 acquires the e-mail address of the destination of the e-mail.

(Step S410) The management information acquisition unit 134 acquires from the management email information storage unit 114 management information paired with the email address acquired in step S409.

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

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

(Step S413) The storage unit 137 stores the invoice information received in step S407, the route identifier "E-mail" acquired in step S408, the output information acquired in step S411, and the content information acquired in step S412. Configure the information you have.

(Step S414) The accumulation unit 137 accumulates the information configured in step S413 in the invoice storage unit 111. FIG. Return to step S401.

(Step S415) The third receiving means 123 determines whether or not the invoice information or the like has been received from the terminal device 2 of the worker. If bill information etc. have been received, the process goes to step S416, and if bill information etc. have not been received, the process goes to step S424. Note that the invoice information and the like here may be invoice information only.

(Step S416) The route acquisition unit 133 acquires the route identifier “mail”.

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

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

(Step S419) The accumulation unit 137 composes information having the invoice information received in step S415, the route identifier "mail" acquired in step S416, and the output information acquired in step S418.

(Step S420) The accumulation unit 137 accumulates the information configured in step S419 in the invoice storage unit 111. FIG.

(Step S<b>421 ) The address information configuration unit 138 acquires mailing address information from the mailing address storage unit 112 .

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

(Step S423) The address information output unit 142 transmits the address information configured in step S422 to the terminal device 2 of the worker who has transmitted the invoice information and the like. Return to step S401.

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

(Step S425) The unique address acquisition unit 131 acquires a unique e-mail address.

(Step S426) The management mail information registration unit 132 configures management mail information having the management information received in step S424 and the mail address acquired in step S425.

(Step S427) The management mail information registration unit 132 stores the management mail information configured in step S426 in the management mail information storage unit 114. FIG.

(Step S428) The output unit 14 transmits the management mail information configured in step S426 to the terminal device 2 that transmitted the management information. Through such processing, the user of the terminal device 2 can know the mail address when sending the invoice information by e-mail.

(Step S429) The output instruction receiving means 124 determines whether an output instruction has been received from the terminal device 2 or not. When the output instruction is received, the process goes to step S430, and when the output instruction is not received, the process returns to step S401.

(Step S430) The invoice acquisition unit 139 acquires 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.

(Step S431) The bill output unit 143 transmits the bill information and the like acquired in step S430 and the route identifier to the terminal device 2 that transmitted the output instruction. Return to step S401.

In the flow charts of FIGS. 4 and 5, the processing ends when the power is turned off or when the processing ends.

Next, an operation example of the terminal device 2 (so-called first terminal) used by the sender of billing information will be described with reference to the flowchart of FIG. It should be noted that the sender of the invoice information (person on the billing side) may be the recipient of the invoice information (person on the billing side).

(Step S601) The terminal reception unit 22 determines whether or not it has received an instruction to activate the bill input application. If the activation instruction is received, the process goes to step S602, and if the activation instruction is not received, the process goes to step S605. The bill input application is an application for inputting bill information and transmitting it to the bill processing apparatus 1 . Also, here, instead of the bill input application, a website for inputting bill information may be used. In other words, the URL of the website for inputting the bill information may be used instead of the bill input application activation instruction.

(Step S<b>602 ) The terminal processing unit 23 activates the bill input application in the terminal storage unit 21 . It should be noted that, instead of starting the bill input application, access to a website for inputting bill information may be performed.

(Step S603) The terminal reception unit 22 determines whether or not input of invoice information and the like has been received. If the input of the invoice information or the like is received, the process goes to step S604, and if the input of the invoice information or the like is not received, the process returns to step S603.

(Step S604) The terminal processing unit 23 uses the bill information and the like accepted in step S603 to compose the bill information and the like to be transmitted. The terminal transmission unit 24 transmits the invoice information and the like to the invoice processing apparatus 1 . Return to step S601.

(Step S605) The terminal reception unit 22 determines whether or not it has received an instruction to activate the e-mail application. If the activation instruction is received, the process goes to step S606, and if the activation instruction is not received, the process goes to step S610. The e-mail application is an application for sending e-mails.

(Step S<b>606 ) The terminal processing unit 23 activates the e-mail application of the terminal storage unit 21 .

(Step S607) The terminal reception unit 22 determines whether or not input of invoice information, content information, destination mail address, etc. has been received for the e-mail application. If the input of the invoice information or the like is accepted, the process goes to step S608, and if the input of the invoice information or the like is not accepted, the process returns to step S607. The invoice information is usually a file (for example, a PDF file) and is input to an e-mail application as an e-mail attachment.

(Step S608) The terminal reception unit 22 determines whether or not it has received a mail transmission instruction. If the mail transmission instruction is received, the process goes to step S609, and if the mail transmission instruction is not received, the process returns to step S608.

(Step S609) The terminal processing unit 23 composes an e-mail including invoice information, content information, and the like. The terminal transmission unit 24 transmits the configured e-mail to the destination indicated by the input e-mail address. Return to step S601.

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

(Step S611) The terminal processing unit 23 uses the management information accepted in step S610 to construct management information to be transmitted. The terminal transmission unit 24 transmits the management information to the invoice processing device 1 .

(Step S612) The terminal receiving section 25 determines whether or not the management mail information has been received from the invoice processing apparatus 1. If the management mail information has been received, the process goes to step S613, and if the management mail information has not been received, the process returns to step S612. Here, the terminal receiving section 25 may receive only the disciple's e-mail address included in the management e-mail information.

(Step S613) The terminal processing unit 23 uses the management mail information received in step S612 to construct 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 e-mail address.

(Step S614) Terminal reception unit 22 determines whether or not an output instruction has been received. If the output instruction is accepted, the process goes to step S615, and if the output instruction is not accepted, the process returns to step S601.

(Step S615) The terminal processing unit 23 composes an output instruction to be transmitted. The terminal transmission unit 24 transmits the output instruction to the bill processing device 1 .

(Step S616) The terminal reception unit 25 determines whether or not one or more items of invoice information or the like have been received. If bill information or the like has been received, the process proceeds to step S617, and if bill information or the like has not been received, the process returns to step S616.

(Step S617) The terminal processing unit 23 uses the bill information and the like received in step S616 to configure the bill information and the like to be output. The terminal output unit 26 outputs the invoice information and the like. Return to step S601. It is preferable that the invoice information and the like include the invoice information and the route identifier.

In addition, in the flowchart of FIG. 6, steps S601 to S604 are transmission of invoice information by the first route (route identifier=web). Further, steps S605 to S609 are transmission of invoice information by the second route (route identifier=e-mail). Furthermore, the sender of the bill information may send the bill form by the third route (route identifier=mail). In such a case, the sender will print the billing form and carry out the procedures for mailing it to a predetermined mailing address.

In addition, in the flowchart of FIG. 6, the bill processing device 1 may correspond to only two of the three routes.

Further, in the flowchart of FIG. 6, the process is terminated by power off or an interruption of process termination.

Next, the operation example of the terminal device 2 (so-called second terminal) used by the worker who works on the bill information based on the bill form after receiving the bill form by mail is shown in the flowchart of FIG. will be used to explain. Note that the worker is, for example, a worker of a company that operates the invoice processing apparatus 1 .

(Step S701) The terminal reception unit 22 determines whether or not invoice information or the like has been received from the worker. If bill information etc. have been received, the process goes to step S702, and if bill information etc. have not been received, the process returns to step S701. Note that billing information and the like are, for example, billing information, a sender identifier, and a sender identifier. Also, the invoice information is preferably a file (for example, a PDF file). Also, before step S701, it is assumed that the worker is creating invoice information from the invoice sheet by, for example, converting the invoice sheet into PDF.

(Step S702) The terminal processing unit 23 uses the bill information and the like accepted in step S701 to compose the bill information and the like to be transmitted. The terminal transmission unit 24 transmits the invoice information and the like to the invoice processing apparatus 1 .

(Step S703) The terminal receiving section 25 determines whether or not the address information has been received from the invoice processing apparatus 1. If the address information has been received, the process goes to step S704, and if the address information has not been received, the process returns to step S703.

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

(Step S705) The terminal reception unit 22 determines whether or not a print instruction has been received. If the print instruction is accepted, the process goes to step S706, and if the print instruction is not accepted, the process returns to step S705.

(Step S706) The terminal output unit 26 prints the output address information. The printed address information is pasted on an envelope, the billing form is put in the envelope, and the envelope is mailed to the address indicated by the address information.

Note that in the flowchart of FIG. 7, the process ends when the power is turned off or an interrupt for ending the process occurs.

A specific operation of the invoice processing system A according to this embodiment will be described below.
A conceptual diagram of the invoice processing system A is shown in FIG.

At present, the bill storage unit 111 of the bill processing apparatus 1 stores the bill management table having the structure shown in FIG. The bill management table is a table for managing bill information and the like. The bill management table manages records having "ID", "bill information", "source identifier", "destination identifier", "route identifier", "date", "item", and "payment due date". “ID” is information for identifying a record. "Invoice information" is assumed here to be the PDF file of the invoice. The 'source identifier' has 'company' and 'person in charge'. "Company" is information that identifies an organization (company, sole proprietor, government office, etc.) from which the invoice information is sent, and is the company name here. "Person in charge" is information identifying the person in charge of the organization that sent the invoice information, and here, it is the name of the person in charge. The 'destination identifier' has 'company' and 'person in charge'. "Company" is information that identifies an organization (company, sole proprietor, government office, etc.) to which the invoice information is sent, and is the company name here. "Person in charge" is information for identifying the person in charge of the organization to which the invoice information is sent, and is the name of the person in charge here. The 'route identifier' can be any of 'web', 'e-mail', and 'mail'. "Date" is the date when the invoice information was received. "Date" may be the issue date of the invoice.

In addition, the mailing address storage unit 112 stores mailing address information "<Address> 〒 105-0001 Toranomon, Minato-ku, Tokyo ... <Destination> XXXX Co., Ltd. Invoice Management Center <Sender identifier> $ Sender identifier < Destination Identifier>$Destination Identifier” is stored. Note that "$ sender identifier" and "$ sender identifier" are variables into which the information of the corresponding sender identifier and receiver identifier is substituted.

The output information storage unit 113 also stores an output information management table having the structure shown in FIG. 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. The 'output information' has 'item' and 'payment due date' here. "Subject" is a subject corresponding to invoice information. “Payment due date” is information specifying the payment due date for bill information.

The management mail information storage unit 114 also stores a management mail information management table having the structure shown in FIG. The management mail information management table has "ID", "source identifier", "destination identifier", "destination e-mail address", and "destination person in charge e-mail address". "ID", "source identifier" and "destination identifier" are the same as "ID", "source identifier" and "destination identifier" in FIG. "Destination e-mail address" and "Destination e-mail address of person in charge" are e-mail addresses when the invoice information is sent by e-mail. The "e-mail address of the person in charge of the destination" is the e-mail address of the person in charge to notify the person in charge of the destination when the invoice information is accepted.

In the above situation, the following five specific examples will be described. A specific example 1 is processing for automatically configuring management information. A specific example 2 is a case of transmitting invoice information and the like via a website. A specific example 3 is a case of sending invoice information and the like by e-mail. Concrete example 4 is a case where the worker inputs billing information and the like based on the mailed billing form. Specific example 5 is a case where the invoice information and the route identifier are output to the terminal device 2 based on the output instruction.

(Specific example 1)
Now, the user "Ako Yamada" has a management Assume that information is input to the terminal device 2 .

Next, the terminal reception unit 22 of the terminal device 2 receives the management information. Next, the terminal processing unit 23 configures management information to be transmitted using the received management information. Next, the terminal transmission unit 24 transmits the management information to the invoice processing device 1 .

Next, the management information receiving means 125 of the invoice processing apparatus 1 receives the management information. Next, it is assumed that the unique address acquisition unit 131 acquires a unique e-mail address "a001@b.jp". Here, the unique address acquisition unit 131 increments the <numerical value> (three digits here) of the mail address template “a<numerical value>@b.jp” in the storage unit 11, Shall generate a unique email address. That is, after obtaining "a001@b.jp", the unique address obtaining unit 131 obtains "a002@b.jp".

Next, the management mail information registration unit 132 registers the received management information “sender identifier “<company>A company <person in charge>Ako Yamada”, destination identifier “<company>X company <person in charge>Tanaka E Child”” and configures the management mail information having the acquired mail address “a001@b.jp”. Next, the management mail information registration unit 132 accumulates the configured management mail information in the management mail information management table (FIG. 10). Note that the accumulated management mail information is the record of "ID=1" in FIG. It is assumed that the "delivery destination person in charge address" of the record of "ID=1" in FIG. 10 is input separately.

By the above processing, the registration of the management mail information is completed.

(Specific example 2)
Next, it is assumed that the user "Ako Yamada" (hereinafter referred to as the user) accesses a website for entering bill information. Such access is based on entering the URL of the website.

Assume that the screen of FIG. 11 is displayed on the terminal device 2 of the user. In addition, it is assumed that the user imports a PDF file of the bill to be sent. This imported invoice file is 1101 . It is also assumed that the user inputs a bill sender identifier 1102 and a sender identifier 1103 on the screen of FIG. Then, the terminal reception unit 22 receives the input of invoice information 1101 (invoice PDF file), sender identifier 1102 , and receiver identifier 1103 .

Next, it is assumed that the user instructs the send button 1104 in FIG. 11 . Then, the terminal processing unit 23 uses the received bill information and the like to compose the bill information and the like to be transmitted. Next, the terminal transmission unit 24 transmits the invoice information and the like to the invoice processing apparatus 1 .

Next, the first receiving means 121 of the invoice processing apparatus 1 receives the invoice information 1101, sender identifier 1102, and receiver identifier 1103 from the terminal device 2 of the sender.

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 the URL, for example.

Next, from the received information, the management information acquisition unit 134 retrieves the management information “sender identifier “<Company> Company A <Person in charge> Acquire the destination identifier “<Company> X Company <Person in charge> Tanaka Eko”.

Next, the output information acquisition unit 136 acquires the output information "<subject outsourcing fee, <payment date> the end of the current month, ..." paired with the acquired management information from the output information management table (Fig. 9). .

Next, the accumulation unit 137 collects the received invoice information, the acquired management information “sender identifier “<company>A company <person in charge> Yamada Ako”, destination identifier “<company>X company <person in charge Person > Tanaka Eko”, the acquired route identifier “web”, the date, and the acquired output information “<subject> subcontracting expenses, <payment date> the end of the current month, …” are stored in the invoice management table (Fig. 8). The accumulated record is the record of "ID=58" in FIG. Note that the accumulation unit 137 acquires the date from a clock (not shown).

Through the above processing, billing information was transmitted and stored via the web. In addition, output information such as subjects was automatically accumulated.

(Specific example 3)
Next, it is assumed that the user “B man Inoue” (hereafter referred to as the user) has activated the e-mail application of the terminal device 2 in order to send bill information.

Then, in the terminal device 2, an e-mail application is started. Then, it is assumed that the user performs an operation to attach a separately prepared PDF file of an invoice as an attachment file to the e-mail. As a result, invoice information (PDF file) was attached as shown in 1201 in FIG. 12 (see 1201).

In addition, the e-mail address "a002@b.jp" given by the administration side of the bill processing device 1 was entered in the e-mail address column as the address to send the bill to "Fo Kinoshita of Company Y". (see 1202). It is also assumed that the user has entered the title (1203) and text (1204) of the mail and instructed the send button 1205. FIG.

Then, the e-mail shown in FIG. 12 is sent to the address "a002@b.jp".

Next, the second receiving means 122 of the bill processing apparatus 1 receives the bill information, the title of the mail, the text information of the mail, and the like by e-mail.

Next, the route acquisition unit 133 detects that an e-mail has been received, and acquires the route identifier “e-mail”.

Next, the management information acquisition unit 134 acquires the e-mail address "a002@b.jp" of the destination of the e-mail. Then, the management information acquisition unit 134 acquires management information paired with the acquired mail address “a002@b.jp”, “sender identifier “<company>B company <person in charge>B man Inoue”, destination identifier “< Company> Company Y <person in charge> Mr. F Kinoshita”” is obtained from the management mail information management table (FIG. 10).

Next, the output information acquisition unit 136 acquires the output information "<subject> communication expenses, <payment date> within 30 days, ..." paired with the acquired management information from the output information management table (Fig. 9). get.

Next, the content acquisition unit 135 acquires content information from the received e-mail. The content information includes the title "Send invoice for Internet line usage" and text information "Mr. F Kinoshita, company Y. I am B Inoue of company B....".

Next, the storage unit 137 stores the received invoice information, the acquired management information, the acquired route identifier “e-mail”, the date, the acquired output information “<subject> communication expenses, <payment date> 30 Within days, . Note that the accumulated record is the record of "ID=59" in FIG. This record also includes content information, which is omitted in FIG.

By the above processing, the invoice information is transmitted and stored by e-mail. In addition, management information and output information such as subjects were automatically accumulated.

(Specific example 4)
Now, in order to send a bill to "G child Fukuda of company Z", the user "C child Aoki of company C" puts the billing form in an envelope and sends the envelope to a predetermined mailing address ( Here, it is assumed that the invoice is mailed to the operating company of the invoice processing apparatus 1). Assume that the operating company of the invoice processing apparatus 1 has received a mailing from Ciko Aoki.

Next, it is assumed that the operator of the operating company converts the invoice form in the envelope into PDF. Assume that the worker starts an application for inputting bill information and the like in order to transmit the bill information and the like to the bill processing apparatus 1 .

Then, it is assumed that the worker provides the PDF file of the bill to the activated application and inputs the sender identifier and the receiver identifier. It is also assumed that the worker has selected the route "mail". An example of such a screen is shown in FIG. In FIG. 13, 1301 is the PDF file of the invoice, 1302 is the sender identifier, 1303 is the recipient identifier, and 1304 is the selected route. Then, it is assumed that the worker instructs the send button 1305 .

Next, the PDF file of the bill, the source identifier, the destination identifier, and the route identifier “mail” are transmitted from the terminal device 2 to the bill processing device 1 .

Next, the third receiving means 123 of the bill processing apparatus 1 receives bill information and the like. Next, the route acquisition unit 133 acquires the route identifier “mail”. Also, the management information acquisition unit 134 acquires management information that is a set of the received sender identifier and recipient identifier.

Next, the output information acquisition unit 136 acquires the output information “<subject> advertising expenses, . . . ” paired with the acquired management information from the output information management table (FIG. 9).

Next, the accumulation unit 137 stores records having the received invoice information (Welsh file), management information, route identifier “mail”, date, and output information “<subject> advertising expenses, . . . ”. Store in a table (FIG. 8). This record is "ID=60" in FIG.

Next, the address information constructing unit 138 retrieves the mailing address information from the mailing address storage unit 112 "<Address> 〒 105-0001 Toranomon, Minato-ku, Tokyo ... <Address> XXXX Co., Ltd. Invoice management center <Sender identifier >$ sender identifier <sender identifier>$ sender identifier”. Also, the address information configuration unit 138 uses the acquired mailing address information, sender identifier, and receiver identifier to generate address information "<address> Toranomon, Minato-ku, Tokyo 105-0001 ... <address> XXXX Inc. Invoice Management Center <Sender Identifier> C Company Aoki C child <Destination Identifier> Z Company Fukuda G child". Next, the address information output unit 142 transmits the configured address information to the terminal device 2 of the worker who has transmitted the invoice information and the like. It is preferable that the address information output unit 142 substitutes the configured address information into the template stored in the storage unit 11, configures the address information in a form to be printed, and then transmits the address information. is.

Next, the terminal receiving section 25 receives the address information from the invoice processing apparatus 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 address information. An example of such an output is shown in FIG.

Next, assume that the operator has instructed the print button 1401 . Then, the mailing address of the billing form (original) is printed. The worker pastes the printed address on an envelope, puts the invoice form (original) in the envelope, and mails the envelope to the "invoice management center" that manages the invoice form (original).

As described above, processing such as transmission and storage of billing information when the route is mail has been performed. In addition, we were able to provide support for mailing the billing form (original).

(Specific example 5)
The user "Aoki Ciko" inputs an output instruction to the terminal device 2 in order to confirm whether or not the mailed billing form has been digitized and the billing information and the like are stored in the billing processing device 1. I did. It is assumed that the output instruction has "<sender identifier> C company Aoki C child <destination identifier> Z company G child Fukuda".

Next, the terminal accepting unit 22 accepts an output instruction having a source identifier and a 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 bill processing device 1 .

Next, the output instruction receiving means 124 of the invoice processing apparatus 1 receives the output instruction. Next, the invoice acquisition unit 139 acquires the invoice information and the like corresponding to the received output instruction and the route identifier from the invoice management table (FIG. 8). Here, it is assumed that the bill acquisition unit 139 has acquired the record of "ID=60" from FIG.

Next, the invoice output unit 143 transmits the acquired invoice information and the like and the route identifier “mail” to the terminal device 2 of Ciko Aoki.

Next, the terminal reception unit 25 of the terminal device 2 receives bill information and the like. The terminal processing unit 23 uses the received bill information and the like to compose the bill information and the like to be output. The terminal output unit 26 outputs the invoice information and the like. An example of such an output is shown in FIG. In FIG. 15, invoice information (file) 1501, route identifier "mail" 1502, and item "advertising expenses" 1503 are output. In the field 1503, one of the route identifiers "web", "e-mail", and "mail" is output.

By the above processing of this specific example, invoice information is output on the same screen as route identifiers, items, and the like.

As described above, according to the present embodiment, invoice information received through a plurality of routes can be collectively managed.

Further, according to the present embodiment, it is possible to grasp the route through which the invoice information was received.

Further, according to this embodiment, it is possible to easily output the output information managed in association with the source identifier and the destination identifier.

Also, according to the present embodiment, it is possible to easily acquire the subject in response to the transmission of the invoice information.

Further, according to the present embodiment, it is possible to support the management of bill forms received by mail.

Furthermore, according to this embodiment, it is possible to support the management of invoice information received by e-mail.

It should be noted that, in the present embodiment, billing information can be transmitted through three routes: web, e-mail, and mail. However, in the present embodiment, only any two of the three routes of web, e-mail, and mail may be used.

Also, the processing in the present embodiment may be realized by software. Then, this software may be distributed by software download or the like. Also, this software may be recorded on a recording medium such as a CD-ROM and distributed. Note that this also applies to other embodiments in this specification. The software that implements the invoice processing apparatus 1 in this embodiment is the following program. In other words, this program comprises a computer, first receiving means for receiving bill information from a terminal device, second receiving means for receiving bill information by e-mail, and bill information based on mailed bill paper. a receiving unit comprising two or more means of third receiving means for receiving; a route obtaining unit for obtaining a route identifier specifying a route from which the receiving unit receives the invoice information; and the route identifier acquired by the route acquisition unit, and stores the bill information in an invoice storage unit in which the invoice information is stored.

Also, FIG. 16 shows the appearance of a computer that executes the program described in this specification and realizes the invoice processing device 1 or the terminal device 2 of the various embodiments described above. The above-described embodiments can be implemented in computer hardware and computer programs running thereon. FIG. 16 is an overview diagram of this computer system 300, and FIG. 17 is a block diagram of the system 300. As shown in FIG.

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

In FIG. 17, a computer 301 includes a 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 a boot-up program, It includes a RAM 3016 connected and 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, computer 301 may also include a network card that provides connection to a LAN.

A program that causes computer system 300 to execute the functions of invoice processing apparatus 1 of the above-described embodiment is stored in CD-ROM 3101, inserted into CD-ROM drive 3012, and transferred to hard disk 3017. good. Alternatively, the program may be transmitted to computer 301 via a network (not shown) and stored in hard disk 3017 . Programs are loaded into RAM 3016 during execution. The program may be loaded directly from CD-ROM 3101 or network.

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 apparatus 1 of the above-described embodiment. A program need only contain those parts of instructions that call the appropriate functions (modules) in a controlled manner to produce the desired result. How the computer system 300 operates is well known and will not be described in detail.

In the above program, the step of transmitting information, the step of receiving information, etc. are performed by hardware. processing) are not included.

Also, the number of computers that execute the above programs may be singular or plural. That is, centralized processing may be performed, or distributed processing may be performed. In other words, the bill processing device 1 or the like may be a stand-alone device, or may be composed of two or more devices.

Further, in each of the above embodiments, it goes without saying that two or more communication means existing in one device may be physically realized by one medium.

Further, in each of the above embodiments, each process may be implemented by centralized processing by a single device, or may be implemented by distributed processing by a plurality of devices.

INDUSTRIAL APPLICABILITY As described above, the invoice processing apparatus 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.

A invoice processing system 1 invoice processing device 2 terminal device 11 storage unit 12 reception unit 13 processing unit 14 output unit 21 terminal storage unit 22 terminal reception unit 23 terminal processing unit 24 terminal transmission unit 25 terminal reception unit 26 terminal output unit 111 Invoice storage unit 112 Mailing address storage unit 113 Output information storage unit 114 Management mail information storage unit 121 First reception means 122 Second reception means 123 Third reception means 124 Output instruction reception means 125 Management information reception means 131 Unique address acquisition unit 132 Management mail information registration unit 133 Route acquisition unit 134 Management information acquisition unit 135 Content acquisition unit 136 Output information acquisition unit 137 Accumulation unit 138 Address information configuration unit 139 Invoice acquisition unit 141 Output information output unit 142 Address information output unit 143 Invoice Output part

Claims (11)

Of the first receiving means for receiving bill information from a terminal device, the second receiving means for receiving bill information by e-mail, and the third receiving means for receiving bill information based on mailed billing forms a reception unit comprising two or more means;
a route acquisition unit that acquires a route identifier that specifies a route from which the reception unit receives the invoice information;
an accumulation unit for pairing the bill information received by the reception unit with the route identifier obtained by the route acquisition unit and accumulating the bill information in a bill storage unit. . The reception unit
2. The invoice processing apparatus according to claim 1, comprising said first reception means, said second reception means, and said third reception means. The reception unit
further comprising output instruction receiving means for receiving an output instruction of invoice information;
2. A bill output unit that acquires bill information corresponding to the output instruction from the bill storage unit and outputs the bill information together with a route identifier paired with the bill information. 3. The bill processing device according to claim 2. The reception unit
comprising management information receiving means for receiving management information that is a set of a sender identifier that identifies the sender of the invoice and a recipient identifier that identifies the recipient of the invoice;
an output information acquisition unit that associates output information paired with the management information received by the management information reception unit with one or more pieces of management information, and acquires the output information from an output information storage unit in which the output information is stored;
4. The invoice processing apparatus according to any one of claims 1 to 3, further comprising an output information output unit that outputs the output information. the output information is a subject,
The output information output unit is
5. The bill processing apparatus according to claim 4, wherein, when receiving management information together with bill information, said reception unit transmits said output information to the terminal device that transmitted said bill information. The reception unit comprises the third reception means,
an address information configuration unit that acquires mailing address information from a mailing address storage unit that stores mailing address information related to the mailing address of the billing form, and configures address information for mailing the billing form;
6. The invoice processing apparatus according to any one of claims 1 to 5, further comprising an address information output unit that outputs the address information. The bill storage unit
One or more items of invoice information are stored in association with management information that is a set of a sender identifier and a recipient identifier,
The reception unit comprises the second reception means,
When the second reception means receives invoice information by e-mail, it acquires the e-mail address of the destination of the e-mail, and has management information and the e-mail address as management information paired with the e-mail address. further comprising a management information acquisition unit that acquires from the management mail information storage unit that stores one or more pieces of management mail information;
The storage unit is
7. The invoice processing apparatus according to any one of claims 1 to 6, wherein the invoice information received by said second reception means is stored in association with the management information acquired by said management information acquisition unit. The reception unit comprises the second reception means,
a content acquisition unit for acquiring content information, which is text information or a title of the e-mail;
The storage unit is
8. The invoice processing apparatus according to any one of claims 1 to 7, wherein the content information is also stored in a pair with the invoice information received by the reception unit. The reception unit
comprising management information reception means for receiving management information that is a set of a source identifier and a destination identifier;
a unique address obtaining unit that obtains a unique email address in response to receiving the management information;
A management mail information registration unit for storing the management information received by the management information receiving means and the management mail information having the unique mail address in a management mail information storage unit for storing one or more pieces of management mail information. The bill processing device according to claim 7 or 8, comprising: An invoice processing method implemented by an invoice storage unit for storing invoice information, a reception unit, a route acquisition unit, and an accumulation unit,
The receiving unit comprises first receiving means for receiving bill information from a terminal device, second receiving means for receiving bill information by e-mail, and third receiving means for receiving bill information based on a mailed bill form. a receiving step of receiving bill information by two or more of the receiving means;
a route acquisition step in which the route acquisition unit acquires a route identifier specifying a route from which the bill information is received in the reception step;
an accumulation step in which the accumulation unit stores the bill information received in the reception step in the bill storage unit in a pair with the route identifier obtained in the route acquisition step. Method. a computer having access to an invoice store where invoice information is stored;
Of the first receiving means for receiving bill information from a terminal device, the second receiving means for receiving bill information by e-mail, and the third receiving means for receiving bill information based on mailed billing forms a reception unit comprising two or more means;
a route acquisition unit that acquires a route identifier that specifies a route from which the reception unit receives the invoice information;
A program for functioning as an accumulation unit for accumulating the invoice information received by the reception unit and the route identifier acquired by the route acquisition unit as a pair in the invoice storage unit.

Images