Invoice processing apparatus, invoice processing method, and computer-readable recording medium

Abstract

To solve the problem that a bill cannot be properly processed by using a payee master database.SOLUTION: A biller acquisition unit 131 that acquires a biller identifier from a received bill image, a determination unit 132 that determines whether or not the biller identifier acquired by the biller acquisition unit 131 is present in a payee master database 31 in which two or more pieces of payee information having the biller identifier are stored, and a bill processing unit 133 that performs different processing related to the bill image according to a determination result of the determination unit 132, when the determination unit 132 determines that the biller identifier is present, the bill processing unit 133 can perform appropriate bill processing using the payee master database by the bill processing apparatus 1 including the bill information acquisition unit 1331 that acquires bill information necessary for performing bill processing and the bill processing unit 1336 that performs bill processing using the bill information and related to a bill image.SELECTED DRAWING: Figure 3

Description

[Technical Field]

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

[0002] Conventionally, there has been an invoice reading and settlement system that is characterized by comprising an invoice image acquisition means for acquiring invoice image data of an invoice, an invoice detail acquisition means for identifying invoice items contained in an invoice based on an invoice master and invoice image data using a machine learning technique and acquiring invoice detail data for each invoice item, and an invoice detail confirmation screen display control means for controlling the display of a invoice detail confirmation screen on which the invoice detail data is arranged on the input / output section of a terminal device based on an output format (see Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] However, in the prior art, it was not possible to process bills appropriately using a payee master database. [Means for solving the problem]

[0005] The invoice processing device of the first invention comprises an invoice receiving unit that receives an invoice image, a invoice acquisition unit that acquires a invoice identifier that identifies the invoice source from the invoice image, a judgment unit that determines whether the invoice identifier acquired by the invoice acquisition unit exists in a payee master database in which two or more payee information items having the invoice identifier are stored, and an invoice processing unit that performs different processing on the invoice image depending on the judgment result of the judgment unit, and the invoice processing device comprises: a invoice information acquisition means that acquires invoice information, which is information corresponding to the invoice identifier and is necessary for invoice processing when the judgment unit determines that the invoice identifier exists in the payee master database, and an invoice processing means that performs invoice processing using the invoice information acquired by the invoice information acquisition means, which is processing related to the invoice image.

[0006] This configuration allows appropriate processing of invoices using the payee master database.

[0007] In addition, in the invoice processing device of the second invention, compared to the first invention, the invoice processing unit is an invoice processing device that stores payee information including the invoice identifier in the master database only when the judgment unit determines that the invoice identifier does not exist in the payee master database.

[0008] With this configuration, the payee master database can be updated appropriately.

[0009] In addition, the invoice processing device of the third invention is different from the second invention in that the invoice processing unit queries whether or not to register payee information including the invoice identifier in the payee master database when the judgment unit determines that the invoice identifier does not exist in the payee master database, and is equipped with an inquiry means for sending an inquiry including the invoice identifier to the terminal device that sent the invoice image, an answer receiving means for receiving an answer to the inquiry, and a storage means for storing payee information including the invoice identifier in the payee master database only if the response is to store the information in the payee master database.

[0010] This configuration allows the payee master database to be updated more appropriately.

[0011] Furthermore, the invoice processing device of the fourth invention is an invoice processing device in which, compared to the third invention, the response receiving means receives a response including payee information having a billing source identifier, and the storage means stores the payee information received by the response receiving means in a payee master database.

[0012] This configuration allows the payee master database to be updated more appropriately.

[0013] In addition, the invoice processing device of the fifth invention is an invoice processing device that, compared to the first invention, the invoice processing unit acquires a default invoice code only when the judgment unit determines that the invoice identifier does not exist in the payee master database, acquires invoice information including the invoice code, and performs invoice processing, which is processing using the invoice information and processing related to invoice images.

[0014] This configuration allows appropriate processing of invoices using the payee master database.

[0015] In addition, the invoice processing device of the sixth invention is an invoice processing device in which, compared to any one of the first to fifth inventions, a processing identifier that identifies the processing to be performed when the billing source identifier does not exist in the payee master database is stored in correspondence with the billing destination identifier, and the invoice processing unit is an invoice processing device that performs processing identified by the processing identifier that pairs with the billing destination identifier corresponding to the invoice image when the judgment unit determines that the billing source identifier does not exist in the payee master database.

[0016] This configuration allows appropriate processing of invoices using the payee master database.

[0017] Furthermore, in the invoice processing device of the seventh invention, compared to the first invention, the invoice processing unit further includes an account information acquisition means for acquiring payee account information from the invoice image when the judgment unit determines that two or more of the invoice identifiers acquired by the invoice acquisition unit exist in the payee master database, and the invoice information acquisition means determines whether payee information having the invoice identifier and account information exists in the payee master database, and if so, acquires the invoice information having the invoice identifier and account information.

[0018] With this configuration, invoices can be processed appropriately using the payee master database.

[0019] In addition, the invoice processing device of the eighth invention is an invoice processing device that, compared to any one of the first to seventh inventions, further comprises an invoice storage unit that stores invoice information, which is an invoice image or information obtained using an invoice image, in association with a billing source identifier or a billing recipient identifier.

[0020] This configuration allows for appropriate management of bill information.

[0021] In addition, the invoice processing device of the ninth invention is an invoice processing device in which, compared to any one of the first to eighth inventions, the invoice processing unit performs invoice processing by sending a billing source identifier and invoice information, which is an invoice image or information obtained from the invoice image.

[0022] This configuration allows appropriate processing of invoices using the payee master database. [Effects of the Invention]

[0023] The invoice processing device according to the present invention can process invoices appropriately using a payee master database. [Brief explanation of the drawings]

[0024] [Figure 1] Conceptual diagram of invoice processing system A according to the first embodiment [Figure 2] Block diagram of the invoice processing system A [Figure 3] Block diagram of the invoice processing device 1 [Figure 4] A flowchart illustrating an example of the operation of the invoice processing device 1. [Figure 5] Flowchart for explaining an example of processing when the same item exists [Figure 6] A flowchart illustrating an example of processing when the same is not present. [Figure 7] A flowchart illustrating an example of the operation of the terminal device 2 [Figure 8] FIG. 10 is a diagram showing an example of the payee master database 31. [Figure 9] FIG. 10 is a diagram showing an example of the processing management table. [Figure 10] Figure showing an example of the invoice image [Figure 11] Figure showing an example of the invoice image [Figure 12] A diagram showing an example of the inquiry information [Figure 13] Figure showing an example of the screen on which the answer is entered [Figure 14] Block diagram of the computer system DETAILED DESCRIPTION OF THE INVENTION

[0025] Hereinafter, embodiments of a bill processing device and the like will be described with reference to the drawings. Note that components with the same reference numerals in the embodiments operate in the same manner, and therefore repeated description may be omitted.

[0026] (Embodiment 1) In this embodiment, we will explain an invoice processing device that receives an invoice image from the invoice recipient's terminal device, obtains payee information, which is a string of characters, from the invoice image, determines whether the payee information is registered in the payee master, and if it is present in the payee master, performs invoice processing, which is processing using the invoice information.

[0027] In this embodiment, an invoice processing device will be described that, if the payee information is not registered in the payee master, registers the payee information including information acquired from the invoice image in the payee master.

[0028] In this embodiment, a bill processing device that registers payee information in a payee master based on a user instruction will be described.

[0029] In this embodiment, an invoice processing device will be described that presents payee information obtained from an invoice image to a user, and after the user adds or modifies the payee information, registers the payee information in a payee master.

[0030] In this embodiment, an invoice processing device will be described that processes invoice information using a default code when payment destination information is not registered in the payment destination master.

[0031] In this embodiment, an invoice processing device will be described that performs processing according to a processing identifier stored for each invoice destination when the invoice destination information is not registered in the invoice destination master.

[0032] In this embodiment, we will describe an invoice processing device that, when there are two or more pieces of payee information with a billing identifier in the payee master, obtains the payee account information of the invoice image and determines whether payee information with the payee account information and the billing identifier exists in the payee master.

[0033] In this embodiment, a bill processing device that stores and manages bill images or bill information acquired from bill images in association with billing source identifiers will be described.

[0034] In this embodiment, an invoice processing device that performs invoice processing by sending an invoice identifier and an invoice image or invoice information acquired from the invoice image to a server or the like where a payee master is stored will be described.

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

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

[0037] 1 is a conceptual diagram of a bill processing system A according to this embodiment. The bill processing system A comprises a bill processing device 1, one or more terminal devices 2, and a server 3.

[0038] The invoice processing device 1 is a device that performs invoice processing (described later) using received invoice images. The invoice processing device 1 is, for example, a cloud server or an ASP server, but the type is not important.

[0039] The terminal device 2 is a terminal used by a user who sends an invoice image. The user is usually the user to whom the invoice is sent. The terminal device 2 is, for example, a smartphone, a personal computer, or a tablet terminal, but the type is not important.

[0040] The server 3 is a device that manages a payee master database (hereinafter referred to as "payee master" as appropriate), which will be described later. The server 3 is, for example, a cloud server or an ASP server, but the type is not important.

[0041] The invoice processing device 1 and one or more terminal devices 2, and the invoice processing device 1 and server 3, can communicate with each other via a network such as the Internet.

[0042] Fig. 2 is a block diagram of the invoice processing system A according to this embodiment. Fig. 3 is a block diagram of the invoice processing device 1.

[0043] The invoice processing device 1 comprises a storage unit 11, a receiving unit 12, a processing unit 13, and a transmitting unit 14. The receiving unit 12 comprises an invoice receiving unit 121. The processing unit 13 comprises a billing source acquisition unit 131, a determination unit 132, an invoice processing unit 133, and an invoice storage unit 134. The invoice processing unit 133 comprises a billing information acquisition means 1331, an account information acquisition means 1332, an inquiry means 1333, a response receiving means 1334, a storage means 1335, and an invoice processing means 1336.

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

[0045] The server 3 includes a payee master database 31 .

[0046] Various types of information are stored in the storage unit 11 that constitutes the invoice processing device 1. The various types of information include, for example, an invoice image, invoice information, one or more default invoice source codes, and a processing identifier.

[0047] The storage unit 11 may have a payee master database 31. In such a case, the server 3 may not exist.

[0048] An invoice image is an image of an invoice. The invoice image may be, for example, a PDF file, JPEG, GIF, HTML, XML, or other format, but the data format is not important. An invoice image typically includes a billing source identifier, a billing recipient identifier, and payee account information.

[0049] A requesting party identifier is information that identifies a requesting party. A requesting party is the party making a request. A requesting party identifier is, for example, the name of the requesting party's organization or the name of the requesting party. An organization name is, for example, a company name or an organization name. A requesting party identifier may also be the requesting party's ID. A requesting party is usually an organization, but may also be an individual.

[0050] A billing destination identifier is information that identifies a billing destination. A billing destination is the party being billed. A billing destination identifier is, for example, the name of the billing destination organization or the name of the billing destination individual. A billing destination identifier may also be the billing destination ID. A billing destination is usually an organization, but may also be an individual.

[0051] The account information is information about the payee of a bill. The account information is, for example, information about a bank account. The account information includes, for example, the name of the payee's bank, the name or ID of the bank branch, and the account number. The account information is, for example, an electronic money ID.

[0052] The default billing code is a billing code that is used when the billing identifier obtained from the bill image does not exist in the payee master database 31. The default billing code corresponds to the billing recipient identifier. The billing code is usually the billing source's ID, but it may be the same as the billing source identifier. The billing code may also be the name of the billing source (for example, the company name).

[0053] A processing identifier is information that identifies a process. A processing identifier is usually information that identifies a process to be performed when the billing source identifier does not exist in the payee master database 31. A processing identifier is, for example, the ID of the process or the name of the function that performs the process. A processing identifier is, for example, one of "automatic accumulation process," "inquiry process," or "default code process." Each of the one or more processing identifiers in the storage unit 11 is usually associated with a different billing destination identifier. In other words, a processing identifier is usually information registered by the billing destination.

[0054] The process identifier "automatic accumulation process" is a process that automatically accumulates payee information that does not exist in the payee master database 31. The process identifier "automatic accumulation process" is a process that automatically accumulates, for example, part or all of the payee information obtained from an invoice image in the payee master database 31.

[0055] The process identifier "inquiry process" is a process in which an inquiry is made as to whether or not to store payee information that does not exist in the payee master database 31, and then the information is stored as necessary.

[0056] The transaction identifier "default code transaction" is a payment transaction that uses a default billing code. When the transaction identifier is "default code transaction," payee information is not normally stored in the payee master database 31.

[0057] The receiving unit 12 receives various instructions and information from the terminal device 2. The various instructions and information are, for example, an invoice image and an invoice processing instruction.

[0058] Invoice processing instructions are instructions for processing an invoice. Invoice processing instructions include an invoice image. Invoice processing instructions include, for example, a billing identifier.

[0059] The invoice receiving unit 121 receives an invoice image. The invoice receiving unit 121 usually receives the invoice image from the terminal device 2 of the invoice recipient. Note that such an invoice image is, for example, an invoice image received by the user of the invoice recipient from the invoice source, or an invoice image obtained by the invoice recipient by imaging (e.g., converting to PDF) an invoice mailed from the invoice source to the invoice recipient. The invoice receiving unit 121 may also receive an invoice processing instruction.

[0060] The processing unit 13 performs various types of processing, such as processing performed by the billing source acquisition unit 131, the determination unit 132, the bill processing unit 133, or the bill storage unit .

[0061] The billing source acquisition unit 131 acquires a billing source identifier indicating the billing source from the invoice image received by the invoice receiving unit 121. The billing source acquisition unit 131, for example, performs character recognition processing on the invoice image to acquire the billing source identifier. For example, the billing source acquisition unit 131 provides the generation AI with the invoice image and a prompt to acquire the billing source identifier, and acquires the billing source identifier from the generation AI. The prompt is, for example, "Please tell me the name of the organization that is the billing source listed in the invoice image below!" The method for acquiring the billing source identifier is not important.

[0062] The billing source acquisition unit 131 acquires, for example, one or more bill attribute values ​​from the bill image received by the bill receiving unit 121. The one or more bill attribute values ​​typically include a billing source identifier and a billing recipient identifier. The one or more bill attribute values ​​include, for example, the bill amount, the billing source's address, telephone number, the name of the billing source's representative, and the billing source's telephone number.

[0063] The judgment unit 132 judges whether the billing source identifier acquired by the billing source acquisition unit 131 exists in the payee master database 31, which will be described later. The judgment unit 132 searches the payee master database 31 using the billing source identifier acquired by the billing source acquisition unit 131 as a key, and judges whether the billing source identifier exists in the payee master database 31.

[0064] The invoice processing unit 133 performs different processing on the invoice image depending on the determination result of the determination unit 132. In other words, the invoice processing unit 133 performs different processing depending on whether the invoice source identifier exists in the payee master database 31 or not.

[0065] The invoice processing unit 133 stores the payee information including the invoice identifier in the payee master database 31 only when the determination unit 132 determines that the invoice identifier does not exist in the payee master database 31. The payee information stored by the invoice processing unit 133 may be part of the payee information stored in the payee master database 31. The payee information stored by the invoice processing unit 133 may be only the invoice identifier.

[0066] The invoice processing unit 133 acquires a default invoice code, acquires invoice information including the invoice code, and performs invoice processing for the invoice image using the invoice information, only when the judgment unit 132 determines that the invoice identifier does not exist in the payee master database 31, for example.

[0067] The invoice processing unit 133, for example, obtains a default invoice code from the storage unit 11, obtains invoice information including the invoice code from the payee master database 31, and performs invoice processing using the invoice information, only when the judgment unit 132 determines that the invoice identifier does not exist in the payee master database 31.

[0068] Invoice processing is processing of an invoice using an invoice image, such as processing for payment of an invoice specified by the invoice image, or processing for managing invoice information.

[0069] The invoice processing unit 133 performs processing identified by the processing identifier. When the determination unit 132 determines that the billing identifier does not exist in the payee master database 31, the invoice processing unit 133 acquires the billing destination identifier corresponding to the received invoice image, acquires the processing identifier paired with the billing destination identifier from the storage unit 11, and performs processing identified by the processing identifier. The processing identifier is, for example, "automatic storage processing," "inquiry processing," or "default code processing."

[0070] The process identified by the process identifier “automatic accumulation process” is a process for automatically accumulating the acquired payee information in the payee master database 31 .

[0071] The "inquiry process" is a process in which the user is asked whether or not to store the acquired payee information in the payee master database 31, and if the answer is "yes," the payee information is stored in the payee master database 31. Note that the payee information stored here may include information that the user has added or modified.

[0072] "Default code processing" refers to processing an invoice image by acquiring a default billing code corresponding to a billing identifier, acquiring billing information including the billing code, and using the billing information. The invoice processing here is usually processing the payment of the amount contained in the billing information.

[0073] The invoice processing unit 133 performs invoice processing, for example, by transmitting to the server 3 a billing source code corresponding to the invoice source identifier and an invoice image or invoice information acquired from the invoice image.

[0074] When the determining unit 132 determines that the billing source identifier exists in the payee master database 31, the billing information obtaining means 1331 obtains the billing information corresponding to the billing source identifier.

[0075] The billing information is information necessary for processing bills. The billing information includes, for example, a billing source identifier, billing source account information, a billing destination identifier, and an amount. The billing information includes, for example, an invoice image.

[0076] The billing information acquisition means 1331 acquires the payee information having a billing source identifier and account information, which is payee information existing in the payee master database 31. In other words, the billing information may be the same information as the payee information.

[0077] If the judgment unit 132 determines that the billing source identifier acquired by the billing source acquisition unit 131 exists in the payee master database 31 twice or more, the account information acquisition means 1332 acquires the payee's account information from the invoice image.

[0078] When the judgment unit 132 judges that the billing source identifier does not exist in the payee master database 31, the inquiry means 1333 inquires whether or not to register the payee information including the billing source identifier in the payee master database 31, and sends an inquiry including the billing source identifier to the terminal device 2.

[0079] The response receiving means 1334 receives a response to the inquiry made by the inquiry means 1333. The response includes, for example, a flag specifying whether to "store" or "not store." The response includes, for example, all or part of the payee information.

[0080] The reply receiving means 1334 receives a reply including, for example, payee information having a billing source identifier.

[0081] The storage means 1335 stores the payee information including the billing source identifier in the payee master database 31 only if the response indicates that the information should be stored in the payee master database 31 .

[0082] The storage means 1335 stores, for example, the payee information received by the response receiving means 1334 in the payee master database 31. The payee information received by the response receiving means 1334 includes, for example, information that has been added or changed by the user.

[0083] The bill processing means 1336 performs bill processing relating to the bill image using the billing information acquired by the billing information acquisition means 1331 .

[0084] The invoice storage unit 134 stores invoice information in association with a billing source identifier or a billing recipient identifier. The invoice information includes an invoice image or information acquired using the invoice image. The invoice information preferably includes an invoice image and information acquired using the invoice image. The invoice information preferably includes an invoice image. Note that the information acquired using the invoice image is one or more invoice attribute values. The invoice storage unit 134 typically stores invoice information for the purpose of managing invoice information.

[0085] The transmission unit 14 transmits various types of information. For example, the transmission unit 14 transmits to the terminal device 2 the results of processing the received receipt image.

[0086] Various types of information are stored in the terminal storage unit 21 that constitutes the terminal device 2. The various types of information include, for example, a user identifier and an invoice image.

[0087] The terminal reception unit 22 receives various types of information, instructions, etc. Examples of the various types of information, instructions, etc. include invoice images and invoice processing instructions.

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

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

[0090] The terminal transmission unit 24 transmits various information, instructions, etc. to the invoice processing device 1. The various information, instructions, etc. are, for example, an invoice image and invoice processing instructions.

[0091] The terminal receiving unit 25 receives various types of information from the invoice processing device 1. The various types of information are, for example, the transmission results of the receipt image.

[0092] The terminal output unit 26 outputs various information, such as the result of sending a receipt image.

[0093] Output is a concept that includes displaying on a display, projecting using a projector, printing on a printer, outputting sound, transmitting to an external device, storing on a recording medium, and handing over processing results to other processing devices or other programs.

[0094] The payee master database 31 constituting the server 3 stores one or more payee information items. Payee information is information about the biller from whom the bill payment is made. The payee information includes one or more payee information items. Each payee information item is associated with a billing identifier. The payee information includes a billing source identifier. The payee information includes, for example, the biller's address, telephone number, name of the person in charge, and account information. The payee master database 31 is, for example, an RDB, but it could also be a spreadsheet file or the like, and the data structure is not important.

[0095] The storage unit 11, the terminal storage unit 21, and the payee master database 31 are preferably non-volatile recording media, but may also be realized as volatile recording media.

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

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

[0098] The processing unit 13, billing source acquisition unit 131, judgment unit 132, invoice processing unit 133, invoice storage unit 134, billing information acquisition means 1331, account information acquisition means 1332, inquiry means 1333, response receiving means 1334, storage means 1335, invoice processing means 1336, and terminal processing unit 23 can typically be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are typically realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuitry). The processor may be a CPU, MPU, GPU, etc., and the type is not important.

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

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

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

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

[0103] (Step S401) The bill receiving unit 121 determines whether or not a bill processing instruction including a bill image has been received. If a bill processing instruction has been received, the process proceeds to step S402, and if the patient has not been examined, the process returns to step S401.

[0104] (Step S402) The billing source acquisition unit 131 acquires the bill image included in the bill processing instruction received in step S401.

[0105] (Step S403) The billing source acquisition unit 131 acquires one or more bill attribute values ​​from the bill image. For example, the billing source acquisition unit 131 performs character recognition processing on the bill image to acquire one or more bill attribute values.

[0106] (Step S404) The judgment unit 132 acquires a billing source identifier contained in one or more invoice attribute values ​​acquired in step S403. The judgment unit 132 also acquires a billing destination identifier contained in one or more invoice attribute values ​​acquired in step S403, or a billing destination identifier corresponding to the invoice processing instruction received in step S401. Next, the judgment unit 132 searches the payee master database 31 using the acquired billing destination identifier and the acquired billing source identifier as keys, and determines whether or not payee information corresponding to the billing destination identifier and including the billing source identifier exists in the payee master database 31. If the payee information exists, the process proceeds to step S405; if not, the process proceeds to step S406. Note that if payee information exists, it means that a billing source corresponding to the invoice image exists.

[0107] (Step S405) The invoice processing unit 133 performs processing when payment destination information exists. The process returns to the upper level processing. An example of processing when payment destination information exists will be described using the flowchart in Figure 5. Processing when payment destination information exists is the processing performed when it is determined in step S404 that payment destination information exists.

[0108] (Step S406) The invoice processing unit 133 etc. performs non-existence processing and returns to the upper level processing. An example of non-existence processing will be explained using the flowchart in Figure 6. Non-existence processing is processing that is performed when it is determined in step S404 that payment destination information does not exist.

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

[0110] Next, an example of the process in the presence state in step S405 will be described with reference to the flowchart in FIG.

[0111] (Step S501) If the search results in step S504 indicate that there is only one payment destination information item that includes the billing identifier, proceed to step S502; if the search results indicate that there are two or more payment destination information items, proceed to step S504.

[0112] (Step S502) The billing information acquisition means 1331 acquires billing information using one or more types of information from the bill attribute values ​​acquired in step S403 or the payee information searched in step S404. The billing information includes, for example, a billing source identifier, billing source account information, a billing destination identifier, and an amount. The billing information includes, for example, an invoice image.

[0113] (Step S503) The invoice processing means 1336 performs invoice processing, which is processing related to the invoice image, using the invoice information acquired in step S502. The process returns to the upper level process. The invoice processing means 1336 performs invoice processing, which is processing for payment for the invoice image, for example. The invoice processing means 1336 transmits the invoice information to a settlement server (not shown), for example.

[0114] (Step S504) The account information obtaining means 1332 obtains the payee's account information included in the bill attribute value obtained in step S502.

[0115] (Step S505) The billing information acquisition means 1331 searches the payee master database 31 using the billing destination identifier, the billing source identifier, and the account information as keys.

[0116] (Step S506) If the search result in step S505 is that payee information that is paired with the billing identifier and has a billing source identifier and account information exists in the payee master database 31, the billing information acquisition means 1331 proceeds to step S502, and if the search result is that it does not exist, the billing information acquisition means 1331 proceeds to step S507.

[0117] (Step S507) The invoice processing unit 133 etc. performs non-existence processing and returns to the upper level processing. An example of non-existence processing will be described with reference to the flowchart in FIG.

[0118] Next, an example of the non-existence process in steps S406 and S507 will be described with reference to the flowchart in FIG.

[0119] (Step S601) The invoice processing unit 133 acquires a billing identifier. The invoice processing unit 133 determines whether a processing identifier paired with the billing identifier exists in the storage unit 11. If a processing identifier paired with the billing identifier exists, the process proceeds to step S602; if not, the process proceeds to step S608.

[0120] (Step S602) The invoice processing unit 133 determines whether the processing identifier is "automatic accumulation processing." If the processing identifier is "automatic accumulation processing," the process proceeds to step S603; if the processing identifier is not "automatic accumulation processing," the process proceeds to step S607.

[0121] (Step S603) The invoice processing unit 133 acquires payee information. The payee information is one or more invoice attribute values ​​acquired in step S403. The one or more invoice attribute values ​​include, for example, a billing source identifier and billing source account information.

[0122] (Step S604) The storage means 1335 stores the payee information in association with the billing identifier in the payee master database 31. Note that the payee information stored here may be a portion of the payee information in the payee master database 31 (for example, information excluding the address, telephone number, and name of the person in charge).

[0123] (Step S605) The billing information acquisition unit 1331 acquires billing information. The billing information is, for example, one or more bill attribute values ​​acquired in step S403, and includes, for example, a billing source identifier, billing source account information, and an amount.

[0124] (Step S606) The invoice processing means 1336 uses the invoice information to process the invoice, and returns to the upper level processing.

[0125] (Step S607) The invoice processing unit 133 determines whether the processing identifier is “inquiry processing.” If the processing identifier is “inquiry processing,” the process proceeds to step S608, and if the processing identifier is not “inquiry processing,” the process proceeds to step S615.

[0126] (Step S608) The inquiry means 1333 acquires inquiry information. The inquiry information includes, for example, one or more invoice attribute values ​​acquired in step S403 and a user interface component (for example, a button) for selecting "store" or "do not store."

[0127] (Step S609) The inquiry means 1333 transmits the inquiry information acquired in step S608 to the terminal device 2.

[0128] (Step S610) The response receiving means 1334 determines whether or not a response in response to the transmission of the inquiry information has been received from the terminal device 2. If a response has been received, the process proceeds to step S611, and if not, the process returns to step S610.

[0129] (Step S611) The storage means 1335 determines whether the answer is "storage" or "not storage." If the answer is "storage," the process proceeds to step S612, and if the answer is "not storage," the process proceeds to step S614.

[0130] (Step S612) The storage unit 1335 acquires the payment destination information and the billing destination identifier.

[0131] (Step S613) The storage means 1335 stores the acquired payee information in the payee master database 31 in association with the acquired billing destination identifier.

[0132] (Step S614) The billing information acquisition means 1331 acquires the billing information. Proceed to step S606. The billing information acquisition means 1331, for example, acquires information that constitutes the billing information from the received response, and configures billing information including that information. The billing information acquisition means 1331, for example, acquires information that constitutes the billing information from one or more invoice attribute values ​​acquired in step S403, and configures billing information including that information.

[0133] (Step S615) The invoice processing unit 133 determines whether the processing identifier is "default code processing." If the processing identifier is "default code processing," the process proceeds to step S616; if the processing identifier is not "default code processing," the process proceeds to step S608.

[0134] (Step S616) The invoice processing unit 133 acquires the invoice identifier corresponding to the received invoice processing instruction. The invoice processing unit 133 acquires from the storage unit 11 the default invoice code that pairs with the invoice identifier.

[0135] (Step S617) The billing information acquisition means 1331 uses the default billing source code to construct billing information, and then proceeds to step S606.

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

[0137] (Step S701) The terminal reception unit 22 determines whether or not an invoice image has been received. If an invoice image has been received, the process proceeds to step S702, and if not, the process proceeds to step S704.

[0138] (Step S702) The terminal processing unit 23 acquires the billing destination identifier from the terminal storage unit 21. The terminal processing unit 23 composes a bill processing instruction having the bill image and the billing destination identifier.

[0139] (Step S703) The terminal transmitting unit 24 transmits the invoice processing instruction constructed in step S702 to the invoice processing device 1. The process returns to step S701.

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

[0141] (Step S705) The device processing unit 23 composes inquiry information to be output based on the received inquiry information. The terminal output unit 26 outputs the inquiry information.

[0142] (Step S706) The terminal reception unit 22 determines whether or not an answer has been received from the user. If an answer has been received, the process proceeds to step S707; if not, the process returns to step S706.

[0143] (Step S707) The terminal processing unit 23 composes a response to be output based on the received response. The terminal transmitting unit 24 transmits the response to the invoice processing device 1. The process returns to step S701.

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

[0145] A specific example of the operation of the bill processing system A in this embodiment will be described below.

[0146] The payee master database 31 is assumed to be the payee management table shown in Figure 8. The payee management table has one or more records each having an "ID," "billing identifier," and "payee information." The "billing identifier" has a "billing ID" and "billing name." The "payee information" has a "billing source identifier," "address," "telephone number," "contact name," and "account information." The "billing source identifier" has a "billing source ID" and "billing source name." The "account information" is assumed to have the bank name, branch name, account number, etc. "ID" is information that identifies the record. Here, the "billing destination ID" or "billing destination name" is used as the billing destination identifier.

[0147] The storage unit 11 of the invoice processing device 1 also stores the processing management table shown in Figure 9. The processing management table is a table that manages the processing that is performed when the acquired billing identifier does not exist in the payment recipient master database 31. The processing management table manages one or more records that have an "ID," "billing destination identifier," "processing identifier," and "billing source code." The "billing destination identifier" has a "billing source ID" and a "billing source name." Here, the "billing destination ID" or "billing destination name" is used as the billing destination identifier. Here, the billing source code is assumed to be the billing source ID.

[0148] In the above situation, the following two specific examples will be explained. Specific Example 1 is a case where the acquired billing source identifier exists in the payee master database 31. Specific Example 2 is a case where the acquired billing source identifier does not exist in the payee master database 31.

[0149] (Example 1) Let us assume that person P at Company D converts the invoice mailed from Company A into a PDF and inputs an invoice processing instruction including the PDF invoice image into terminal device 2. The PDF invoice image is shown in Figure 10.

[0150] The terminal device 2 then creates an invoice processing instruction that includes the invoice image (FIG. 10) and the invoice identifier "D01" of the terminal storage unit 21, and transmits the invoice processing instruction to the invoice processing device 1.

[0151] Next, the claim receiving unit 121 of the claim processing apparatus 1 receives a claim processing instruction including a claim image.

[0152] Next, the claimant acquisition unit 131 acquires the claim image (FIG. 10) included in the received claim processing instruction, performs character recognition processing on the claim image, and acquires one or more claim attribute values. Here, the claimant acquisition unit 131 acquires the set of claim attribute values "<claimee identifier> Company D <claimant identifier> Company A <claimant representative> Representative Director AAAA BBBB <postal code> 110-0008 <address> Tokyo ······ <amount> 132,000 <account information> XY Bank XXX Branch Regular: 1234567 Name: Company A < / account information>".

[0153] Next, the determination unit 132 acquires the claimant identifier "Company A" from the set of acquired claim attribute values. Further, the determination unit 132 acquires the claimee identifier "D01" included in the claim processing instruction. Next, the determination unit 132 searches the payee master database 31 using the acquired claimee identifier "D01" and the acquired claimant identifier "Company A" as keys, and determines that there is payee information having the claimee identifier "D01" and the acquired claimant identifier "Company A" in "ID=1" of the payee master database 31 (FIG. 8).

[0154] Next, the claim processing unit 133 performs processing when present as follows. That is, the claim information acquisition means 1331 uses one or more types of information among the acquired claim attribute values or the searched payee information to construct the claim information "<claimee identifier> Company D <claimant identifier> Company A <claimant representative> Representative Director AAAA BBBB <postal code> 110-0008 <address> Tokyo ······ <amount> 132,000 <account information> XY Bank XXX Branch Regular: 1234567 Name: Company A < / account information> <claim image> img1". Note that img1 is the file name of the claim image (FIG. 10).

[0155] Next, the claim form processing means 1336 transmits the claim information to a settlement server (not shown) or server 3, and completes the settlement of 132,000 yen. It is assumed that in the settlement server (not shown) or server 3, processing for transferring 132,000 yen from the bank account identified by the payee identifier "Company D" to the bank account identified by "<Account Information> XY Bank, XXX Branch, Regular: 1234567, Name: Company A < / Account Information>" is performed.

[0156] As described above, according to Specific Example 1, by effectively using the payee master database 31, the claim form can be processed accurately and reliably.

[0157] (Specific Example 2) It is assumed that the person in charge P of Company D input a claim form processing instruction including a claim form image transmitted from the person in charge of Company Y into the terminal device 2. It is assumed that such a claim form image is Figure 11.

[0158] Then, the terminal device 2 constructs a claim form processing instruction having the claim form image (Figure 11) and the payee identifier "D01" in the terminal storage unit 21, and transmits the claim form processing instruction to the claim form processing apparatus 1.

[0159] Next, the claim form receiving unit 121 of the claim form processing apparatus 1 receives a claim form processing instruction including a claim form image. [[ID=第十九]]

[0160] Next, the claimant acquisition unit 131 acquires the claim form image (Figure 11) included in the received claim form processing instruction, performs character recognition processing on the claim form image, and acquires a set of claim form attribute values. Here, it is assumed that the claimant acquisition unit 131 has acquired the set of claim form attribute values "<Payee Identifier> Company D <Claimer Identifier> Company Y <Zip Code> 110 - 0008 <Address> Tokyo ······ <Amount> 33,000 <Account Information> ZZ Bank, AB Branch, Regular: 7654321, Name: Company Y < / Account Information>".

[0161] Next, the determination unit 132 acquires the claimant identifier "Y Corporation" from the set of claim form attribute values obtained. Also, the determination unit 132 acquires the payee identifier "D01" included in the claim form processing instruction. Next, the determination unit 132 searches the payee master database 31 using the acquired payee identifier "D01" and the acquired claimant identifier "Y Corporation" as keys, and determines that there is no payee information having the payee identifier "D01" and the acquired claimant identifier "Y Corporation" in the payee master database 31 (FIG. 8).

[0162] Next, the claim form processing unit 133 acquires the payee identifier "D01". The claim form processing unit 133 acquires the processing identifier "inquiry processing" paired with the payee identifier "D01" from the processing management table (FIG. 9).

[0163] Next, the inquiry means 1333 acquires inquiry information using the set of claim form attribute values acquired. Next, the inquiry means 1333 transmits the inquiry information to the terminal device 2. Here, it is assumed that the inquiry information includes the set of claim form attribute values "<payee identifier> Corporation D <claimant identifier> Y Corporation <address> Tokyo ······ <account information> ZZ Bank AB Branch Regular: 7654321 Name: Y Corporation < / account information>" acquired by the claimant acquisition unit 131.

[0164] Next, the terminal reception unit 25 receives the inquiry information from the claim form processing apparatus 1. Next, the terminal processing unit 23 configures the inquiry information to be output based on the received inquiry information. Next, the terminal output unit 26 outputs the inquiry information. An example of such inquiry information is shown in FIG. 12.

[0165] Next, user P checks the screen of FIG. 12, and inputs the telephone number and the name of the person in charge of the new business partner "Y Corporation" into the "Telephone number" and "Name of the person in charge" fields of FIG. 12 respectively (1301), and instructs the "Store" button 1302 (see FIG. 13).

[0166] Next, the terminal reception unit 22 of the terminal device 2 receives the instruction of the "Store" button 1302. Next, based on the received response, the terminal processing unit 23 constructs the response to be transmitted: "<Process> Store <Claimee Identifier> Company D <Claimer Identifier> Company Y <Address> ······, Tokyo <Phone Number> 03 - 5555 - 6666 <Responsible Person Name> Kiko Inoue <Account Information> ZZ Bank, AB Branch, Regular: 7654321, Name: Company Y < / Account Information>". Next, the terminal transmission unit 24 transmits the response to the bill processing device 1.

[0167] Next, the response receiving means 1334 of the bill processing device 1 receives the response from the terminal device 2.

[0168] Next, based on "<Process> Store" in the response, the storage means 1335 obtains the payee information "<Claimer Identifier> Company Y <Address> ······, Tokyo <Phone Number> 03 - 5555 - 6666 <Responsible Person Name> Kiko Inoue <Account Information> ZZ Bank, AB Branch, Regular: 7654321, Name: Company Y < / Account Information>" from the information in the response. Next, the storage means 1335 obtains the claimee identifier "D01".

[0169] Next, the storage means 1335 stores the payee information "<Claimer Identifier> Company Y <Address> ······, Tokyo <Phone Number> 03 - 5555 - 6666 <Responsible Person Name> Kiko Inoue <Account Information> ZZ Bank, AB Branch, Regular: 7654321, Name: Company Y < / Account Information>" in the payee master database 31 in association with the claimee identifier "D01". As described above, one new payee information associated with the claimee identifier "D01" is added to the payee master database 31 (Figure 8).

[0170] <W As described above, according to the specific example 2, the payee master database 31 can be appropriately and automatically updated.

[0171] As described above, according to the present embodiment, appropriate processing of bills can be performed using the payee master database 31.

[0172] Furthermore, according to this embodiment, the payee master database can be updated appropriately.

[0173] The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to the other embodiments in this specification. The software that realizes the invoice processing device 1 in this embodiment is the following program. In other words, this program...

[0174] FIG. 14 is a block diagram of a computer system 300 that executes the programs described in this specification to realize the bill processing device 1 and the like according to the various embodiments described above.

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

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

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

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

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

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

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

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

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

[0184] As described above, the invoice processing device 1 according to the present invention has the effect of being able to process invoices appropriately using a payee master database, and is useful as a server or the like that supports invoice processing. [Explanation of symbols]

[0185] A. Invoice processing system 1. Invoice processing device 2. Terminal Device 3 Server 11 Storage area 12 Receiving unit 13 Processing section 14 Transmitter 21 Terminal storage section 22 Terminal Reception 23 Terminal processing section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Unit 31 Payment Master Database 121 Bill Receiving Department 131 Billing Source Acquisition Department 132 Judgment Department 133 Invoice Processing Unit 134 Bill Storage Unit 1331 Billing information acquisition means 1332 Account information acquisition means 1333 Inquiry Method 1334 Response receiving means 1335 Means of accumulation 1336 Invoice Processing Instruments

Claims

1. an invoice receiving unit for receiving an invoice image; a billing source acquisition unit that acquires a billing source identifier that identifies a billing source from the bill image; a determination unit that determines whether the billing source identifier acquired by the billing source acquisition unit exists in a payee master database that stores two or more pieces of payee information having the billing source identifier; an invoice processing unit that performs different processes on the invoice image depending on the determination result of the determination unit; The invoice processing unit a billing information acquisition means for acquiring, when the determination unit determines that the billing identifier exists in the payee master database, billing information that corresponds to the billing identifier and is information necessary for processing bills; and a bill processing means for performing bill processing, which is processing using the billing information acquired by the billing information acquisition means and is processing related to the bill image.

2. The invoice processing unit 2. The bill processing device according to claim 1, wherein payee information including said billing source identifier is stored in said master database only when said determining unit determines that said billing source identifier does not exist in said master database.

3. The invoice processing unit an inquiry means for inquiring whether or not to register payee information including the billing source identifier in the payee master database when the judgment unit judges that the billing source identifier does not exist in the payee master database, the inquiry including the billing source identifier being sent to the terminal device that sent the invoice image; a response receiving means for receiving a response to the inquiry; 3. The bill processing apparatus according to claim 2, further comprising: storage means for storing the payee information including the billing source identifier in the payee master database only when the response indicates that the information should be stored in the payee master database.

4. The response receiving means receiving a response including payment information having a billing identifier; The storage means 4. The invoice processing device according to claim 3, wherein the payee information received by the reply receiving means is stored in the payee master database.

5. The invoice processing unit An invoice processing device as described in claim 1, wherein only when the judgment unit determines that the billing source identifier does not exist in the payee master database, a default billing source code is obtained, billing information including the billing source code is obtained, and the invoice processing is processing using the billing information and is processing related to the invoice image.

6. a processing identifier for identifying a process to be performed when the billing source identifier does not exist in the payee master database is stored in association with the billing destination identifier; The invoice processing unit An invoice processing device as described in any one of claims 1 to 5, wherein when the judgment unit determines that the billing source identifier does not exist in the payment destination master database, processing identified by the processing identifier that pairs with the billing destination identifier corresponding to the invoice image is performed.

7. The invoice processing unit further comprising an account information acquisition means for acquiring account information of a payee from the invoice image when the determination unit determines that two or more of the billing source identifiers acquired by the billing source acquisition unit exist in the payee master database; The billing information acquisition means An invoice processing device as described in claim 1, which determines whether payment destination information having the billing source identifier and the account information exists in the payment destination master database, and if so, acquires the billing information having the billing source identifier and the account information.

8. 2. The invoice processing device according to claim 1, further comprising a invoice storage unit that stores the invoice image or invoice information obtained using the invoice image in association with the invoice source identifier or invoice recipient identifier.

9. The invoice processing unit The invoice processing device according to claim 1, wherein the invoice processing is performed by transmitting the invoice identifier and invoice information, which is the invoice image or information acquired from the invoice image.

10. A bill processing method realized by a bill receiving unit, a billing source acquisition unit, a determination unit, and a bill processing unit, a bill receiving step in which the bill receiving unit receives a bill image; a billing source acquisition step in which the billing source acquisition unit acquires a billing source identifier that identifies a billing source from the bill image; a determination step in which the determination unit determines whether the billing source identifier acquired by the billing source acquisition unit exists in a payee master database in which two or more pieces of payee information having the billing source identifier are stored; a bill processing step in which the bill processing unit performs different processing on the bill image depending on the determination result of the determination unit; The invoice processing step includes: a billing information acquisition substep, when the determination unit determines that the billing identifier exists in the payee master database, of acquiring billing information that corresponds to the billing identifier and is information necessary for processing an invoice; a bill processing substep of performing bill processing using the billing information acquired in the billing information acquisition substep, the bill processing being processing related to the bill image.

11. Computer, an invoice receiving unit for receiving an invoice image; a billing source acquisition unit that acquires a billing source identifier that identifies a billing source from the bill image; a determination unit that determines whether the billing source identifier acquired by the billing source acquisition unit exists in a payee master database that stores two or more pieces of payee information having the billing source identifier; A program for causing the program to function as an invoice processing unit that performs different processes on the invoice image depending on the determination result of the determination unit, The invoice processing unit a billing information acquisition means for acquiring, when the determination unit determines that the billing identifier exists in the payee master database, billing information that corresponds to the billing identifier and is information necessary for processing bills; A program for causing the computer to function as comprising an invoice processing means for performing invoice processing, which is processing using the invoice information acquired by the invoice information acquisition means and is processing related to the invoice image.

Images