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

Abstract

To solve a problem that it was previously difficult to perform appropriate processing on purchase statements.SOLUTION: Appropriate processing on purchase statements can be performed by an invoice processing device 1, which includes: an invoice reception unit 121 configured to receive two or more types of invoice information including purchase statement information which is invoice information issued by a buyer, and regular invoice information which is invoice information issued by a seller; a type determination unit 131 configured to determine which type of invoice information received by the invoice reception unit 121 is among the two or more types including the purchase statement information and the regular invoice information; and an invoice accumulation unit 132 configured to accumulate the invoice information received by the invoice reception unit 121 in an invoice management unit 111 which stores one or more pieces of management information including invoice identifier and invoice information so as to distinguish the type determined by the type determination unit 131.SELECTED DRAWING: Figure 3

Description

The present invention relates to a bill processing device and the like that manage bill information.

BACKGROUND ART Conventionally, there has been a bill data management device that aims to shorten the time required for accounting processing (for example, see Patent Document 1). Such a bill data management device includes an image data acquisition unit 231 that acquires bill image data using e-mail, and a first character string specifying unit 232 that specifies a plurality of first character strings included in the bill image data. a second character string identifying unit 233 that identifies one or more second character strings other than the bill image data associated with the email; and one or more first character strings among the plurality of first character strings; a data registration unit 234 that associates the one or more third character strings corresponding to the one or more second character strings identified by the second character string identification unit 233 and registers them in the bill database in which the bill data is registered; has.

Japanese Patent Application Publication No. 2021-182389

However, in the prior art, it has not been possible to perform appropriate processing on purchase statements.

The invoice processing device of the first invention processes two or more types of invoice information including purchase statement information, which is invoice information issued by a buyer, and regular invoice information, which is invoice information issued by a seller. an invoice receiving unit that receives the invoice, and a type determining unit that determines which type of invoice information received by the invoice receiving unit is out of two or more types including purchase statement information and normal invoice information. , a bill storage unit that stores the bill information received by the bill reception unit in a bill management unit that stores one or more pieces of management information having bill information so as to be able to distinguish the type determined by the type determination unit; This is a bill processing device equipped with.

With this configuration, by storing purchase statements and regular invoices in a distinguishable manner, appropriate processing can be performed on purchase statements.

Further, in the bill processing device of the second invention, in contrast to the first invention, the type determining unit determines that the type of bill information received by the bill receiving unit is purchase statement information. In this case, the invoice processing apparatus further includes a support unit that performs support processing to assist a seller of the invoice information in confirming the purchase statement information.

With this configuration, it is possible to support the seller's confirmation of the purchase statement.

Further, in the bill processing device of the third invention, in contrast to the second invention, the support unit is a bill processing device comprising two or more different means for supporting confirmation of purchase statement information. It is.

With this configuration, confirmation of the purchase statement by the seller can be appropriately supported by a plurality of means.

Furthermore, in contrast to the second invention, the invoice processing device of the fourth invention is an e-mail corresponding to an invoice identifier, and the invoice processing device of the fourth invention is an e-mail that corresponds to an invoice identifier, and a seller confirms purchase statement information identified by the invoice identifier. The support unit further includes an e-mail receiving unit that receives an e-mail sent from the seller terminal, and the support unit is configured to receive a confirmation e-mail when the e-mail received by the e-mail receiving unit is a confirmation e-mail. , an invoice processing device comprising a first support means for performing an e-mail confirmation process of accumulating confirmation information indicating that the purchase statement information has been confirmed by the seller in pairs with an invoice identifier corresponding to the confirmation e-mail; be.

With this configuration, confirmation by the seller of the purchase statement can be appropriately supported by a plurality of means including e-mail.

Moreover, the bill processing device of the fifth invention, in contrast to the second invention, further includes a bill acquisition unit that acquires purchase statement information identified by one bill identifier from the bill management unit; The support unit further includes an invoice transmission unit that transmits the purchase statement information acquired by the invoice acquisition unit to the seller terminal, and the support unit, in response to the invoice transmission unit transmitting the purchase statement information, The first step is to receive a confirmation flag indicating that the seller corresponding to the seller terminal has confirmed the purchase statement information, and perform online confirmation processing to store the confirmation information corresponding to the confirmation flag in pairs with one invoice identifier. The bill processing device is equipped with two supporting means.

With this configuration, confirmation by the seller of the purchase statement can be appropriately supported by the confirmation function in the online system.

In addition, in the bill processing device of the sixth invention, in contrast to the second invention, the support section responds to the purchase statement information in response to the receipt of the purchase statement information by the bill receiving section. The bill processing device includes a third support means that performs confirmation support processing to support confirmation of purchase statement information by the time corresponding to the confirmation deadline indicated by the deadline information.

With this configuration, by setting a deadline for checking the contents of the purchase statement, it is possible to appropriately support the seller's confirmation of the purchase statement.

In addition, in the bill processing device of the seventh invention, in contrast to the sixth invention, the third support means receives the purchase statement information in response to the receipt of the purchase statement information by the bill receiving section. This is a bill processing device that performs automatic confirmation processing to accumulate confirmation information in pairs with purchase statement information by the time corresponding to the confirmation deadline indicated by deadline information for information.

With this configuration, if the seller has not confirmed the purchase statement by the time corresponding to the deadline for confirming the contents of the purchase statement, it will be automatically assumed that the purchase statement has been confirmed. It can accelerate the progress of transactions.

In addition, in the bill processing device of the eighth invention, in contrast to the sixth invention, the purchase statement information is associated with seller contact information that specifies the contact information for the seller, and The support means identifies the purchase statement information by the time corresponding to the confirmation deadline indicated by the deadline information for the purchase statement information in response to the receipt of the purchase statement information by the invoice receiving unit. Determine whether confirmation information paired with the invoice identifier has been accumulated, and if not, send the purchase statement information to the seller using the seller contact information corresponding to the purchase statement information. This is a bill processing device that performs a reminder process that sends reminder information to encourage confirmation.

With this configuration, it is possible to remind the seller to confirm the contents of the purchase statement when the deadline for confirming the contents of the purchase statement is met.

Further, in the bill processing device of the ninth invention, in contrast to the sixth invention, the third support means is configured to process the purchase statement information in response to the receipt of the purchase statement information by the bill receiving section. Determine whether confirmation information paired with the invoice identifier that identifies purchase statement information has been accumulated by the time corresponding to the confirmation deadline indicated by the deadline information for the information, and if it has not been accumulated, Automatic confirmation processing that stores confirmation information in pairs with purchase statement information, and confirmation processing indicated by deadline information for purchase statement information in response to receipt of purchase statement information by the invoice receiving unit. Determine whether confirmation information paired with the invoice identifier that identifies the purchase statement information has been accumulated by the time corresponding to the deadline, and if not, respond to the purchase statement information. If the seller contact information can be used to perform a reminder process to send reminder information to the seller to confirm the purchase statement information, and if the related information regarding the purchase statement information satisfies the first condition, The invoice processing device performs an automatic confirmation process and performs a reminder process when related information regarding purchase statement information satisfies the second condition.

With this configuration, if the seller has not confirmed the purchase statement by the deadline for confirming the contents of the purchase statement, it is possible to appropriately control whether to perform automatic confirmation processing or reminder processing. can.

Further, in addition to the first invention, the bill processing device of the tenth invention further includes a bill acquisition section that acquires bill information from the bill management section, and a bill processing device that acquires the bill information acquired by the bill acquisition section. The bill transmitting unit is a bill processing device that transmits bill information to the seller terminal so that the type of bill information can be specified.

With this configuration, the type of bill can be clearly indicated on the terminal device.

According to the bill processing device according to the present invention, it is possible to appropriately process purchase statements.

Conceptual diagram of information system A in Embodiment 1 Block diagram of the information system A Block diagram of the bill processing device 1 Flowchart explaining an example of the operation of the bill processing device 1 Flowchart explaining an example of the operation of the bill processing device 1 Flowchart explaining an example of the confirmation support process Flowchart explaining an example of the operation of the terminal device 2 Flowchart explaining an example of the operation of the terminal device 2 Diagram showing the same user management table Diagram showing the invoice management table Diagram showing an example of the same list Diagram showing an example of the same email Diagram showing an example of the same output Overview of the computer system Block diagram of the computer system

Embodiments of a bill processing device and the like will be described below with reference to the drawings. Note that in the embodiments, constituent elements with the same reference numerals perform similar operations, and therefore, repeated explanation may be omitted.

(Embodiment 1)
In this embodiment, a bill processing device that accumulates purchase statements and regular bills in a distinguishable manner will be described.

Further, in this embodiment, when the object to be managed is a purchase statement, a bill processing device that provides a support function for the seller to confirm the purchase statement will be described. Note that it is preferable that the support function is realized by two or more different means (eg, email, online, etc.). The processing for the support function is, for example, a mail confirmation process described later, an online confirmation process described later, a confirmation support process described later, and a signature confirmation process described later. The confirmation support process is, for example, an automatic confirmation process or a reminder process.

Furthermore, in this embodiment, a bill processing device that transmits bill information so that it is possible to clearly indicate whether it is a purchase statement or a regular bill using a terminal device will be described.

Note that in this embodiment, the fact that information X is associated with information Y means that information Y can be acquired from information X, or information X can be acquired from information Y, and the method of association is not limited. . Information X and information Y may be linked, exist in the same buffer, information X may be included in information Y, or information Y may be included in information X. etc. is also fine.

FIG. 1 is a conceptual diagram of an information system A in this embodiment. The information system A includes a bill processing device 1 and one or more terminal devices 2.

The bill processing device 1 is a device that receives and manages bill information. The bill information to be managed here is information on two or more types of bills including purchase statement information and normal bill information.

The bill processing device 1 is usually a so-called server. The bill processing device 1 is, for example, a cloud server or an ASP server, but the type thereof does not matter. Note that the bill processing device 1 may operate stand-alone.

The terminal device 2 is a terminal used by a user related to bill information. The terminal device 2 is usually a terminal used by a seller or a buyer. A seller is a person who sells the goods or services that are the subject of an invoice. A buyer is a person who buys the goods or services that are the subject of an invoice. The terminal device 2 is, for example, a terminal that transmits bill information to the bill processing device 1. The terminal device 2 is, for example, a terminal that receives bill information from the bill processing device 1 and outputs it.

The terminal device 2 is appropriately referred to as a seller terminal when used by a seller, and a buyer terminal when used by a buyer. Note that one user may be both a seller and a buyer.

The terminal device 2 is a so-called personal computer, a smartphone, or a tablet terminal, but the type thereof does not matter.

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

FIG. 2 is a block diagram of information system A in this embodiment. FIG. 3 is a block diagram of the bill processing device 1.

The bill processing device 1 includes a storage section 11 , a reception section 12 , a processing section 13 , and a transmission section 14 . The storage unit 11 includes a bill management unit 111. The receiving section 12 includes a bill receiving section 121, an instruction receiving section 122, and a mail receiving section 123. The processing unit 13 includes a type determination unit 131, a bill storage unit 132, a bill acquisition unit 133, and a support unit 134. The support unit 134 includes a first support means 1341, a second support means 1342, a third support means 1343, and a fourth support means 1344. The transmitter 14 includes a bill transmitter 141.

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 .

A storage unit 11 that constitutes the bill processing device 1 stores various types of information. The various types of information include, for example, bill information to be described later, various conditions to be described later, and a collection of one or more pieces of user information. The various conditions include, for example, a first condition described later and a second condition described later.

The user information is information about the user who uses the terminal device 2. The user is, for example, a seller or a buyer. The user information includes, for example, a user identifier and an organization identifier. An organization identifier is information that identifies an organization. The organization identifier is, for example, an organization name such as a company name or organization name, or an ID.

The bill management unit 111 stores one or more pieces of management information. The management information includes bill information. The management information includes, for example, a bill identifier. The management information includes, for example, a seller identifier and a buyer identifier. The management information includes, for example, seller contact information and buyer contact information. Seller contact information is information that specifies contact information for the seller. Buyer contact information is information that specifies contact information for the buyer. The seller contact information and the buyer contact information are information used for contacting the seller terminal 2 or the buyer terminal 2. The seller contact information and the buyer contact information are, for example, an email address, a phone number, an ID, an IP address,

Bill information is bill information. The bill information is, for example, a bill image and a collection of information on each item (for example, addressee, biller, amount, date, etc.) constituting the bill. The bill image is an image of a bill, and is, for example, an image of a photographed bill or an image of a scanned bill. The bill image is, for example, a png, a jpeg, etc., and its data structure does not matter. Information on each item making up the bill is a character string.

The bill management unit 111 stores two or more types of bill information. The two or more types of bill information include purchase statement information and normal bill information.

Purchase statement information is information on a purchase statement. A purchase statement is an invoice issued by a buyer.

Normal bill information is information about a normal bill. A regular invoice is an invoice issued by the seller.

A bill identifier is information that identifies a bill. The bill identifier is, for example, an ID.

A seller identifier is information that identifies a seller. The seller identifier is, for example, an ID or a seller name. The seller name is usually an organization name such as a company name or an organization name, but may also be the individual name of a sole proprietor, for example.

A buyer identifier is information that identifies a buyer. The buyer identifier is, for example, an ID or a buyer name. The buyer name is usually an organization name such as a company name or an organization name, but may also be the individual name of a sole proprietor, for example.

The receiving unit 12 receives various instructions and information. Various instructions and information include, for example, invoice information, invoice transmission instructions, e-mails such as confirmation e-mails to be described later, and signatures to be described later.

The bill transmission instruction is an instruction to transmit bill information. A bill sending instruction is associated with a bill identifier. Information other than bill information may be transmitted based on the bill transmission instruction.

The bill receiving unit 121 receives one or more pieces of bill information from the terminal device 2 . The bill information is, for example, purchase statement information or normal bill information. The bill receiving unit 121 receives purchase statement information from the buyer terminal 2, for example. The bill receiving unit 121 receives normal bill information from the seller terminal 2, for example.

The bill information received by the bill receiving unit 121 is associated with a type identifier, for example. The invoice information received by the invoice receiving unit 121 is configured such that, for example, a type identifier (for example, "purchase statement" or "regular statement") can be obtained from the title included in the bill information. . Note that the title may be obtained by performing character recognition processing on a bill image included in the bill information, or may be a character string included in the bill information.

The instruction receiving unit 122 receives various instructions. The various instructions include, for example, a bill transmission instruction. The instruction receiving unit 122 receives a bill transmission instruction from the terminal device 2 . The bill transmission instruction includes, for example, a bill identifier.

The mail receiving unit 123 receives e-mails. The email receiving unit 123 receives, for example, a confirmation email sent from the seller terminal 2. The confirmation email is an example of an email. The confirmation email is an email corresponding to the invoice identifier, and is an email indicating that the seller has confirmed the purchase statement information identified by the invoice identifier. The mail receiving unit 123 may receive e-mail for communication with the seller from the buyer terminal. Note that confirmation of purchase statement information is confirmation that the purchase statement information issued by the buyer is appropriate.

The mail receiving unit 123 may receive the e-mail from the terminal device 2, or may receive the e-mail from a device (for example, a mail server), not shown, which has received the e-mail from the terminal device 2.

It is preferable that the e-mail received by the e-mail receiving unit 123 be associated with a bill identifier. Being associated with a bill identifier may mean including the bill identifier in the title or body of the e-mail.

The processing unit 13 performs various processes. Various types of processing are, for example, processing performed by the type determining section 131, the bill storage section 132, the bill acquiring section 133, and the support section 134.

The type determining unit 131 determines the type of bill information received by the bill receiving unit 121. The type determining unit 131 determines which type of bill information received by the bill receiving unit 121 is among two or more types including purchase statement information and regular bill information. Determining the type is, for example, obtaining a type identifier. The type identifier is information that identifies the type of bill information. The type identifier is, for example, "Purchase Statement" or "Regular Bill."

For example, the type determining unit 131 acquires a type identifier associated with the bill information received by the bill receiving unit 121.

For example, the type determining unit 131 acquires the destination (bill destination) in the bill information received by the bill receiving unit 121, and selects the destination (organization name) and the user of the terminal device 2 that transmitted the bill information. If the identifier and the paired organization name are the same, the type identifier "Purchase Statement" of the bill information is acquired.

For example, the type determining unit 131 acquires the destination (bill destination) in the bill information received by the bill receiving unit 121, and selects the destination (organization name) and the user of the terminal device 2 that transmitted the bill information. If the identifier and the paired organization name are different, the type identifier "regular bill" of the bill information is acquired.

For example, the type determining unit 131 acquires information on the issuer (billing side, product or service provider side) in the bill information received by the bill receiving unit 121, and acquires information on the issuer (organizational If the organization name paired with the user identifier of the terminal device 2 that sent the bill information is the same, the type identifier "regular bill" of the bill information is acquired.

For example, the type determination unit 131 acquires a title (for example, “invoice” or “purchase statement”) that is a character string included in the invoice information received by the invoice reception unit 121, and determines the type indicated by the title. Obtain the identifier (for example, "regular invoice", "purchase statement").

For example, the type determining unit 131 performs character recognition processing on the invoice image included in the invoice information received by the invoice receiving unit 121, and determines the title (for example, “invoice” or “purchase statement”). and the type identifier indicated by the title (for example, "regular bill", "purchase statement").

Note that there may be various methods for the type determining unit 131 to determine the type of bill information, and there are no limitations.

Further, the timing at which the type determining unit 131 determines the type of bill information does not matter. The type determination unit 131 may determine the type of bill information when the bill receiving unit 121 receives the bill information, or may determine the type of bill information when the bill information is transmitted to the terminal device 2. You may also decide the type of.

The bill storage section 132 stores the bill information received by the bill reception section 121 in the bill management section 111 so that the type determined by the type determination section 131 can be distinguished.

For example, the bill storage section 132 stores the bill information received by the bill reception section 121 in the bill management section 111 in association with the type identifier acquired by the type determination section 131.

For example, the bill storage section 132 stores the bill information received by the bill reception section 121 in the bill management section 111 in association with the type identifier acquired by the type determination section 131.

Note that if the bill information received by the bill receiving unit 121 is information that can determine the type of bill information, the bill storage unit 132 simply stores the bill information received by the bill receiving unit 121. Accumulating can be thought of as accumulating so that the types can be distinguished.

When the bill receiving section 121 receives bill information, the bill storage section 132 acquires a unique bill identifier and matches the bill identifier with the bill information received by the bill receiving section 121. It is preferable to store the information in the bill management section 111. Note that acquiring a unique bill identifier includes, for example, generating a unique bill identifier, reading a unique bill identifier, etc., and the method of acquiring the unique bill identifier does not matter.

The bill acquisition unit 133 acquires bill information identified by one bill identifier from the bill management unit 111. The invoice acquisition unit 133 acquires, for example, purchase statement information identified by one invoice identifier from the invoice management unit 111.

The bill acquisition unit 133 acquires, from the bill management unit 111, bill information identified by the bill identifier associated with the bill transmission instruction received by the reception unit 12, for example. The invoice acquisition unit 133 acquires, for example, purchase statement information identified by the invoice identifier associated with the invoice transmission instruction received by the reception unit 12 from the invoice management unit 111. The bill acquisition unit 133 acquires, for example, regular bill information identified by the bill identifier associated with the bill transmission instruction received by the reception unit 12 from the bill management unit 111.

Note that the trigger and timing for the bill acquisition unit 133 to acquire bill information do not matter.

When the type determining unit 131 determines that the type of invoice information received by the invoice receiving unit 121 is purchase statement information, the support unit 134 performs support processing.

The support process is a process that assists the seller of the invoice information in checking the purchase statement information. The support processing is, for example, email confirmation processing, online confirmation processing, confirmation support processing, and signature confirmation processing. The confirmation support process is, for example, an automatic confirmation process or a reminder process.

For example, when purchase statement information is received, the support unit 134 acquires contact information that is information indicating that the purchase statement information has been received, and uses the contact information indicated by the seller contact information. You can also send it to your contacts. Note that the contact information may be, for example, a fixed phrase such as "A purchase statement has been sent to your company. Please confirm it." or may be information including invoice information or the like. The contact information is information for facilitating the seller to confirm the purchase statement.

The support unit 134 includes two or more different means for supporting confirmation of purchase statement information. The two or more different means include, for example, e-mail and online means. The means can be called the route.

Each support process performed by the support unit 134 will be described below. Each support process is performed by, for example, one of the first support means 1341, the second support means 1342, the third support means 1343, and the fourth support means 1344.
(1) Email confirmation process

When the e-mail received by the e-mail receiving unit 123 is a confirmation e-mail, the first support means 1341 performs e-mail confirmation processing to store confirmation information in pairs with the invoice identifier corresponding to the confirmation e-mail. Note that the confirmation information is information indicating that the purchase statement information has been confirmed by the seller. The confirmation information is, for example, a flag, confirmation date, and confirmation date and time. Note that the bill identifier may be included in the title or body of the e-mail, or may be received as a pair with the e-mail.

For example, the first support means 1341 acquires the title of the e-mail received by the e-mail receiving unit 123, and when the title includes a character string indicating that it is a “confirmation e-mail”, the e-mail receiving unit 123 determines that the email received is a confirmation email.

For example, when the text of the e-mail received by the e-mail receiving section 123 includes a character string indicating that the e-mail is a "confirmation e-mail," the first support means 1341 may detect the e-mail received by the e-mail receiving section 123. It is determined that it is a confirmation email.

Note that the method of determining whether the first support means 1341 is a confirmation email does not matter.
(2) Online confirmation process

The second support means 1342 receives a confirmation flag from the seller terminal 2 in response to the invoice transmitting unit 141 transmitting the purchase statement information to the seller terminal 2, and sends confirmation information corresponding to the confirmation flag. , performs online confirmation processing to store the information in pairs with one invoice identifier.

Note that the confirmation flag is information indicating that the seller corresponding to the seller terminal 2 has confirmed the purchase statement information. The confirmation information may be a confirmation flag, or may be time information that specifies when the confirmation flag is received. The time information may be, for example, the date, date and time, but its granularity does not matter.

Further, the purchase statement information may be transmitted to the seller terminal 2, for example, in response to receiving an invoice transmission instruction, or in response to receipt of purchase statement information. Alternatively, it may be a URL included in an e-mail sent to the seller terminal 2, and may be performed in response to a click on a URL for accessing purchase statement information. The trigger for sending the purchase statement information to the seller terminal 2 does not matter.
(3) Confirmation support processing

In response to the receipt of the purchase statement information by the invoice receiving unit 121, the third support means 1343 sends the purchase statement information by the time corresponding to the confirmation deadline indicated by the deadline information for the purchase statement information. Perform confirmation support processing to assist in confirming statement information.

The third support means 1343 can perform, for example, an automatic confirmation process described later and a reminder process described later.

The third support means 1343 performs automatic confirmation processing when the related information regarding the purchase statement information satisfies the first condition, and performs the reminder processing when the related information regarding the purchase statement information satisfies the second condition. It is suitable to do so. The third support means 1343 may always perform either automatic confirmation processing or reminder processing.

The related information regarding the purchase statement information is, for example, a flag that is paired with a seller identifier that is paired with the purchase statement information. The related information regarding the purchase statement information is, for example, the amount included in the purchase statement information. The flag is, for example, an automatic confirmation flag indicating that automatic confirmation processing is to be performed, or a reminder flag indicating that reminder processing is to be performed.

The first condition is, for example, "the automatic confirmation flag is ON", "the automatic confirmation flag is ON AND the amount is less than or equal to the threshold", "the reminder flag is OFF", "the reminder flag is OFF AND The amount is less than or equal to the threshold.” Note that the first condition may not satisfy the second condition. The first condition may include a condition regarding time limit information. The condition regarding the deadline information is, for example, that today is the deadline that the deadline information satisfies.

The second condition is, for example, "the reminder flag is ON", "the reminder flag is ON AND the amount is greater than or equal to the threshold value", "the automatic confirmation flag is OFF", "the automatic confirmation flag is OFF AND the amount is greater than or equal to the threshold value." Note that the second condition may not satisfy the first condition. The second condition may include a condition regarding time limit information.
(3-1) Automatic confirmation process

The third support means 1343 receives the purchase statement information by the time corresponding to the confirmation deadline indicated by the deadline information for the purchase statement information in response to the receipt of the purchase statement information by the invoice receiving unit 121. An automatic confirmation process is performed in which confirmation information indicating that the information has been confirmed is stored in pairs with the bill identifier.

For example, in response to the receipt of the purchase statement information by the invoice receiving unit 121, the third support means 1343 completes the purchase order by the time corresponding to the confirmation deadline indicated by the deadline information for the purchase statement information. Determine whether or not confirmation information paired with an invoice identifier that identifies statement information has been accumulated, and if confirmation information has not been accumulated, select the confirmation information that indicates that the purchase statement information has been confirmed. Performs automatic confirmation processing that is stored in pairs with invoice identifiers.

The deadline information for the purchase statement information is, for example, a certain period of time after receiving the purchase statement information, a certain period of time after the date in the purchase statement information, or the like.

The time corresponding to the confirmation deadline indicated by the deadline information is, for example, the confirmation deadline indicated by the deadline information, but it may also be a time after the deadline has passed.
(3-2) Reminder processing

The third support means 1343 receives the purchase statement information by the time corresponding to the confirmation deadline indicated by the deadline information for the purchase statement information in response to the receipt of the purchase statement information by the invoice receiving unit 121. Determine whether or not confirmation information paired with the invoice identifier that identifies the information has been accumulated, and if not, make a purchase to the seller using the seller contact information corresponding to the purchase statement information. Performs a reminder process that sends reminder information to encourage checking statement information.

The time corresponding to the deadline is, for example, at the time of the deadline, slightly before the deadline, immediately after the deadline, etc.
(4) Signature confirmation process

The fourth support means 1344 receives signature information from the seller terminal 2 in response to the invoice transmitting unit 141 transmitting the purchase statement information to the seller terminal 2, and sends confirmation information corresponding to the signature information. , performs signature verification processing to be stored in pairs with one invoice identifier. Note that the signature information is information on the user's signature, but may also be information on an electronic seal stamp, for example.

The purchase statement information may be transmitted to the seller terminal 2, for example, in response to receiving an invoice transmission instruction, or in response to receipt of the purchase statement information. However, the URL is included in the e-mail sent to the seller terminal 2, and may be performed in response to the URL for accessing the purchase statement information being clicked. The trigger for sending the purchase statement information to the seller terminal 2 does not matter.

The transmitter 14 transmits various types of information to the terminal device 2 . The various types of information include, for example, bill information, confirmation information, and a list of bills including two or more pieces of bill information.

The bill transmitting unit 141 transmits the bill information acquired by the bill acquiring unit 133 to the seller terminal 2.

The invoice transmitting unit 141 transmits, for example, the purchase statement information acquired by the invoice acquiring unit 133 to the seller terminal 2.

The bill transmitting unit 141 transmits bill information to the terminal device 2 so that the type of bill information can be specified. Note that such bill information is, for example, purchase statement information or regular bill information.

A terminal storage unit 21 that constitutes the terminal device 2 stores various types of information. The various types of information include, for example, bill information and user identifiers.

The terminal reception unit 22 receives various information, instructions, and the like. The various information and instructions include, for example, bill information, bill output instructions, e-mails, confirmation flags, and confirmation information.

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

The terminal processing unit 23 performs various processes. 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 for converting received information into information with a structure to be output.

The terminal transmitter 24 transmits various information, instructions, etc. to the bill processing device 1. Various types of information and instructions include, for example, bill information, bill output instructions, e-mails, confirmation flags, and confirmation information.

The terminal receiving unit 25 receives various information from the bill processing device 1. The various types of information include, for example, bill information, confirmation flag, and confirmation information.

The terminal output unit 26 outputs various information. The various types of information include, for example, bill information, confirmation flag, and confirmation information. The terminal output unit 26 outputs the bill information so that the type of bill information can be specified.

Here, output means displaying on a display, projecting using a projector, printing on a printer, outputting sound, sending to an external device, storing on a recording medium, sending to other processing devices or other programs, etc. This is a concept that includes the delivery of processing results.

The storage unit 11, the bill management unit 111, and the terminal storage unit 21 are preferably non-volatile recording media, but can also be implemented using volatile recording media.

The process by which information is stored in the storage unit 11 or the like does not matter. 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 receiving unit 12, bill receiving unit 121, instruction receiving unit 122, mail receiving unit 123, and terminal receiving unit 25 are usually realized by wireless or wired communication means, but are not realized by means for receiving broadcasts. Also good.

Processing section 13, type determination section 131, bill storage section 132, bill acquisition section 133, support section 134, first support means 1341, second support means 1342, third support means 1343, fourth support means 1344, and The terminal processing unit 23 can usually be realized by a processor, a memory, or the like. The processing procedures of the processing unit 13 and the like are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, it may be realized by hardware (dedicated circuit). Note that the processor may be a CPU, MPU, GPU, etc., and its type does not matter.

The transmitting unit 14, bill transmitting unit 141, and terminal transmitting unit 24 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

The terminal reception unit 22 may 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 output devices such as a display and a speaker. The terminal output unit 26 can be realized by output device driver software, output device driver software and the output device, or the like.

Next, an example of the operation of the information system A will be described. First, an example of the operation of the bill processing device 1 will be explained using the flowcharts of FIGS. 4 and 5.

(Step S401) The bill receiving unit 121 determines whether bill information etc. have been received from the terminal device 2. If bill information etc. have been received, the process goes to step S402; if not, the process goes to step S410.

Note that the bill information and the like are, for example, bill information and the user identifier of the user who transmitted the bill information. Bill information and the like are, for example, bill information, user identifier, and type identifier.

(Step S402) The bill storage unit 132 acquires the bill information etc. received in step S401.

(Step S403) The type determination unit 131 acquires a type identifier that identifies the type of bill information acquired in step S402.

(Step S404) The bill storage unit 132 acquires a bill identifier that identifies the bill information received in step S401. Next, the bill storage unit 132 stores information including the bill identifier, the bill information received in step S401, and the type identifier acquired in step S403.

(Step S405) The bill storage unit 132 stores the information configured in step S404 in the bill management unit 111 in association with the user identifier.

(Step S406) The support unit 134 determines whether the type identifier acquired in step S403 is "purchase statement". If it is a "purchase statement", the process goes to step S407; if it is not a "purchase statement", the process returns to step S401.

(Step S407) The support unit 134 acquires the seller identifier in the received bill information or the seller identifier paired with the bill information. The support unit 134 acquires seller contact information paired with the seller identifier from the collection of user information in the storage unit 11 . Note that the seller identifier is also a user identifier. The support unit 134 may acquire seller contact information paired with the seller identifier from the received bill information. The method of obtaining seller contact information does not matter.

(Step S408) The support unit 134 acquires contact information that is information indicating that the purchase statement information has been received.

(Step S409) The transmitter 14 transmits the contact information acquired in step S408 to the contact indicated by the seller contact information. Return to step S401. Note that such transmission may be performed by the support unit 134.

(Step S410) The instruction receiving unit 122 determines whether a bill transmission instruction has been received from the terminal device 2. If a bill sending instruction is received, the process goes to step S411; if not, the process goes to step S413.

(Step S411) The bill acquisition unit 133 acquires one or more bill identifiers corresponding to the bill transmission instruction received in step S410. Next, the bill acquisition unit 133 acquires information including bill information identified by the one or more bill identifiers from the bill management unit 111. Note that the information including invoice information may be only invoice information, or may include one or more of the following: type identifier, confirmation information, seller identifier, and buyer identifier in addition to invoice information. good.

(Step S412) The bill transmitting unit 141 transmits the one or more pieces of bill information etc. acquired in step S411 to the terminal device 2 that has transmitted the bill transmitting instruction. Return to step S401.

(Step S413) The mail receiving unit 123 determines whether or not the e-mail sent from the terminal device 2 has been received. If the e-mail is received, the process goes to step S414; if the e-mail is not received, the process goes to step S420.

(Step S414) The processing unit 13 acquires the email received in step S413.

(Step S415) The processing unit 13 acquires the bill identifier corresponding to the email acquired in step S414.

(Step S416) The processing unit 13 stores the e-mail acquired in step S414 in the storage unit 11 in pairs with the invoice identifier acquired in step S415.

(Step S417) The first support means 1341 determines whether the e-mail acquired in step S414 is a confirmation e-mail. If it is a confirmation email, the process goes to step S418, and if it is not a confirmation email, the process returns to step S401.

(Step S418) The first support means 1341 acquires confirmation information for the purchase statement identified by the invoice identifier acquired in step S415. Note that the confirmation information is, for example, a confirmation flag (for example, "ON"), time information that specifies the time, such as the current day or date and time.

(Step S419) The first support means 1341 stores the confirmation information acquired in step S418 in the bill management unit 111 in pairs with the bill identifier acquired in step S415. Return to step S401.

(Step S420) The receiving unit 12 determines whether a confirmation flag or the like has been received. If a confirmation flag or the like is received, the process goes to step S421; if not, the process goes to step S424.

Note that the confirmation flag and the like are, for example, a confirmation flag and a bill identifier. The confirmation flag and the like are, for example, a confirmation flag, an invoice identifier, and a seller identifier.

(Step S421) The second support means 1342 acquires confirmation information corresponding to the received confirmation flag.

(Step S422) The second support means 1342 acquires the bill identifier corresponding to the received confirmation flag.

(Step S423) The second support means 1342 stores the confirmation information acquired in step S421 in pairs with the bill identifier acquired in step S422. Return to step S401.

(Step S424) The receiving unit 12 determines whether a signature or the like has been received. If a signature or the like is received, the process goes to step S425; if not, the process goes to step S428.

Note that the signature etc. is, for example, a signature and a bill identifier. The signature is, for example, a signature, an invoice identifier, and a seller identifier.

(Step S425) The fourth support means 1344 acquires confirmation information corresponding to the received signature.

(Step S426) The fourth support means 1344 obtains the bill identifier corresponding to the received signature.

(Step S427) The confirmation information acquired in step S425 is stored in pairs with the bill identifier acquired in step S426. Return to step S401.

(Step S428) The third support means 1343 determines whether it is the timing for confirmation support processing. If it is the timing for confirmation support processing, the process goes to step S429, and if it is not the timing for confirmation support processing, the process returns to step S401.
Note that the timing of the confirmation support process is, for example, when a predetermined time has arrived or when the reception unit 12 receives an instruction for the confirmation support process from the terminal device 2, but it does not matter.

(Step S429) The third support means 1343 performs confirmation support processing. Return to step S401. An example of the confirmation support process will be explained using the flowchart of FIG. 6.

In addition, in the flowchart of FIG. 4, it is not necessary to send the contact information using receipt of the purchase statement information as a trigger.

Further, in the flowcharts of FIGS. 4 and 5, the processing is terminated by turning off the power or by an interrupt to terminate the processing.

Next, an example of the confirmation support process in step S429 will be explained using the flowchart of FIG.

(Step S601) The third support means 1343 assigns 1 to the counter i.

(Step S602) The third support means 1343 determines whether or not the i-th bill information exists in the bill management section 111. If the i-th bill information exists, the process goes to step S603; if it does not exist, the process returns to the upper level process.

(Step S603) The third support means 1343 acquires the type identifier corresponding to the i-th bill information. The third support means 1343 acquires the type identifier from the bill management section 111, for example. The third support means 1343, for example, analyzes the i-th bill information and acquires the type identifier. Note that the type determination unit 131 may perform the process of acquiring the type identifier.

(Step S604) The third support means 1343 determines whether the type identifier acquired in step S603 is "purchase statement". If it is a "purchase statement", the process goes to step S605, and if it is not a "purchase statement", the process goes to step S611.

(Step S605) The third support means 1343 acquires confirmation information corresponding to the i-th bill information from the bill management unit 111. Note that here, the third support means 1343 may not be able to acquire the confirmation information.

(Step S606) As a result of the process in step S605, the third support means 1343 determines whether the purchase statement information, which is the i-th bill information, has been confirmed by the seller. If it has been confirmed, the process goes to step S611, and if it has not been confirmed, the process goes to step S607.

(Step S607) The third support means 1343 acquires deadline information corresponding to the i-th bill information. Note that the deadline information is, for example, the period after a predetermined number of days (for example, 10 days) have passed from the reception date paired with the i-th bill information or the date indicated by the date included in the i-th bill information. It is day.

(Step S608) The third support means 1343 acquires today's date from a clock (not shown), and if today's date is the deadline day for the deadline information acquired in step S607, And it is determined whether the i-th bill information satisfies the first condition. If the first condition etc. are satisfied, the process goes to step S609, and if the first condition etc. are not satisfied, the process goes to step S612.

(Step S609) The third support means 1343 acquires confirmation information for the i-th bill information.

(Step S610) The third support means 1343 stores the confirmation information acquired in step S609 in the bill management unit 111 in association with the i-th bill information.

(Step S611) The third support means 1343 increments the counter i by 1. Return to step S602.

(Step S612) The third support means 1343 acquires today's date from a clock (not shown), and if today's date is the deadline day for the deadline information acquired in step S607, And it is determined whether the i-th bill information satisfies the second condition. If the second condition etc. are satisfied, the process goes to step S613, and if the second condition etc. are not satisfied, the process goes to step S611.

(Step S613) The third support means 1343 acquires the seller identifier paired with the i-th bill information. The third support means 1343 acquires seller contact information paired with the seller identifier from the storage unit 11.

(Step S614) The third support means 1343 acquires reminder information to confirm the i-th bill information. Note that the reminder information may be the same as the contact information described above.

(Step S615) The third support means 1343 transmits the reminder information acquired in step S614 to the contact indicated by the seller contact information acquired in step S613. Go to step S611.

Next, an example of the operation of the terminal device 2 will be explained using the flowcharts of FIGS. 7 and 8.

(Step S701) The terminal reception unit 22 determines whether bill information has been received. If the bill information is accepted, the process goes to step S702; if the bill information is not accepted, the process goes to step S704.

(Step S702) The terminal processing unit 23 configures information to be transmitted. Note that the information to be transmitted includes the bill information accepted in step S701. The information to be sent includes, for example, the user identifier or type identifier of the user sending the bill information.

(Step S703) The terminal transmitter 24 transmits the bill information etc. configured in step S702 as bill information. Return to step S701.

(Step S704) The terminal reception unit 22 determines whether the bill transmission instruction has been received. If the bill sending instruction is accepted, the process goes to step S705, and if the bill sending instruction is not accepted, the process goes to step S710.

(Step S705) The terminal processing unit 23 composes a bill transmission instruction to be transmitted. Note that the bill transmission instruction to be transmitted includes information specifying bill information. The information specifying bill information is, for example, a bill identifier and a search condition for bill information.

(Step S706) The terminal transmission unit 24 transmits the bill transmission instruction configured in step S705 to the bill processing device 1.

(Step S707) The terminal receiving unit 25 determines whether one or more pieces of bill information, etc. have been received from the bill processing device 1. If bill information etc. have been received, the process goes to step S708; if not, the process returns to step S707.

(Step S708) The terminal processing unit 23 configures one or more pieces of bill information, etc. to be output, using the one or more pieces of bill information, etc. received in step S707.

Note that it is preferable that the terminal processing unit 23 configures information in a manner that clearly indicates one or more types of each bill information.

(Step S709) The terminal output unit 26 outputs the one or more bill information etc. configured in step S708. Return to step S701.

Note that it is preferable that the terminal output unit 26 outputs one or more pieces of bill information, etc. in a manner that clearly indicates the type of each piece of bill information.

(Step S710) The terminal reception unit 22 determines whether or not the e-mail has been received. If the e-mail is accepted, the process goes to step S711; if the e-mail is not accepted, the process goes to step S712.

(Step S711) The terminal processing unit 23 acquires an e-mail to be sent. The terminal transmitter 24 transmits the e-mail. Return to step S701. Note that the destination of the e-mail is, for example, the bill processing device 1.

(Step S712) The terminal reception unit 22 determines whether or not the confirmation flag has been accepted. If the confirmation flag is accepted, the process goes to step S713, and if the confirmation flag is not accepted, the process goes to step S715.

(Step S713) The terminal processing unit 23 configures a confirmation flag and the like to be transmitted. Note that the confirmation flag to be transmitted includes, for example, a confirmation flag to be transmitted and a bill identifier. The confirmation flag etc. includes, for example, a confirmation flag to be transmitted, an invoice identifier, and a seller identifier.

(Step S714) The terminal transmitter 24 transmits the confirmation flag configured in step S713 to the bill processing device 1. Return to step S701.

(Step S715) The terminal accepting unit 22 determines whether the signature has been accepted. If the signature is accepted, the process goes to step S716; if the signature is not accepted, the process goes to step S718.

(Step S716) The terminal processing unit 23 configures signature information and the like to be transmitted. Note that the signature information to be transmitted includes, for example, the signature information to be transmitted and a bill identifier. The signature information includes, for example, signature information to be transmitted, an invoice identifier, and a seller identifier. The signature information includes, for example, signed bill information. Note that the signature information is simply referred to as a signature as appropriate.

(Step S717) The terminal transmitter 24 transmits the signature information configured in step S716 to the bill processing device 1. Return to step S701.

(Step S718) The terminal receiving unit 25 determines whether or not reminder information has been received from the bill processing device 1. If the reminder information has been received, the process advances to step S719; if the reminder information has not been received, the process returns to step S701.

(Step S719) The terminal processing unit 23 configures the reminder information to be output.

(Step S720) The terminal output unit 26 outputs the reminder information configured in step S719. Return to step S701.

Note that in the flowcharts of FIGS. 7 and 8, the process is terminated by turning off the power or by an interrupt to terminate the process.

A specific example of the operation of the information system A in this embodiment will be described below.

It is now assumed that the storage unit 11 of the bill processing device 1 stores a user management table having the structure shown in FIG. The user management table is a table that manages user information. The user management table here manages one or more records having "ID", "user identifier", and "user attribute value". Here, the "user attribute value" includes "name", "company name", "department name", and "email address". "ID" is information that identifies a record. “Company name” is an example of an organization identifier that identifies the organization to which the user belongs. “Department name” is an example of a department identifier.

It is assumed that the bill management unit 111 stores a bill management table having the structure shown in FIG. The bill management table is a table that manages one or more pieces of bill information. The bill management table here manages one or more records having "ID", "bill identifier", and "bill information". Here, the "bill information" includes a "type identifier," "seller identifier," "buyer identifier," "amount," "date," "bill image," and "confirmation information." The "type identifier" here can be either "regular bill" or "purchase statement." "Confirmation information" is an attribute that is required only when the type identifier is "Purchase statement." The "confirmation information" can be "OFF" or "ON" here. The confirmation information "OFF" indicates that confirmation of the purchase statement by the seller has not been completed. Confirmation information "ON" indicates that confirmation of the purchase statement by the seller has been completed.

In this situation, the following four specific examples will be explained. Specific example 1 is a case where a list of invoices is outputted, and a list is outputted so that normal invoices and purchase statements can be visually distinguished. In specific example 2, when purchase statement information is received, the type identifier "purchase statement" of the purchase statement information is stored, and a message is sent to prompt the seller to confirm the purchase statement information. This is a case of transmitting information. In specific example 2, a process of receiving a confirmation flag from the seller and accumulating confirmation information will also be described. In specific example 3, automatic confirmation processing for purchase statement information for which confirmation has not been completed will be described. In specific example 4, a reminder process for purchase statement information for which confirmation has not been completed will be described.

(Specific example 1)
Hanako, the accounting manager in the accounting department of Tsuyoshi Shoji Co., Ltd., inputs an invoice sending instruction "Buyer identifier = "Syuri Shoji Co., Ltd."" into her terminal device 2 to send the invoice information for which her company is to pay. , and so on. Then, the terminal device 2 receives the bill transmission instruction and transmits it to the bill processing device 1.

Next, the instruction receiving unit 122 of the invoice processing device 1 receives the invoice transmission instruction "buyer identifier="Shikoku Shoji Co., Ltd."".

Next, it is assumed that the invoice acquisition unit 133 acquires invoice information that matches the invoice transmission instruction "buyer identifier="Receipt Shoji Co., Ltd."" from the invoice management table (FIG. 10). It is assumed that the bill information is three pieces of bill information with bill identifiers "R001, R002, and R068."

Next, the invoice acquisition unit 133 obtains the seller identifier, the name of the person in charge on the seller's side, the type identifier, the amount, the name of the person in charge on the buyer's side, confirmation information, and the file name of the invoice image ( Assume that you have acquired the URL (URL) and created a list.

Next, the invoice transmitting unit 141 transmits the configured list to the terminal device 2 of Keiri Hanako who has transmitted the invoice transmission instruction.

Next, the terminal device 2 of Keiri Hanako receives and outputs a list of invoice information for which the company is to pay. An example of such a list is shown in FIG. In FIG. 11, the type of bill information is specified in "Type". Furthermore, in "Confirmation", it is clearly specified whether the seller has confirmed (agreed to) or not confirmed the invoice information whose type identifier is "Purchase Statement." Note that 1101 in FIG. 11 is an icon (button) for outputting details of bill information (here, a bill image).

As described above, in this specific example, the types of bill information are clearly specified so that they can be visually distinguished. Note that when the icon 1101 is specified, for example, a corresponding invoice image is output, but the invoice image clearly indicates that it is a "purchase statement", etc., and invoice information is output. When doing so, it is preferable that the type be clearly specified.

(Specific example 2)
Suppose that a person in charge at yonyon Co., Ltd. (Heizo Tanaka) inputs bill information (purchase statement information) for a service requested from Issu Bussan Co., Ltd. into his terminal device 2.

Next, Heizo Tanaka's terminal device 2 receives the bill information and transmits information including the bill information to the bill processing device 1. It is assumed that the information including invoice information includes, for example, an invoice image, Heizo Tanaka's user identifier "U289", a seller identifier "Issu Bussan Co., Ltd.", and a buyer identifier "Yonyon Co., Ltd.".

Next, the bill receiving unit 121 of the bill processing device 1 receives the bill information and the like. Next, the bill storage unit 132 acquires the received bill information and the like. Further, the type determining unit 131 performs image recognition on the invoice image and acquires the destination company name "Yonyon Co., Ltd." in the invoice image. Further, the type determination unit 131 acquires the organization identifier "yonyon Inc." that is paired with the received user identifier of Heizo Tanaka from the user management table (FIG. 9). Next, the type determining unit 131 determines that the destination of the invoice image matches the organization identifier of the user who sent the invoice information, etc., and assigns the type identifier "Purchase Statement" to the received invoice information, etc. get.

Next, the bill storage unit 132 obtains the unique bill identifier "R101". The bill storage unit 132 also acquires the amount “105,900” and the date “September 24, 2021” from the bill image. The invoice storage unit 132 also acquires the uploader ID "U289", the seller identifier "Shuppan Bussan Co., Ltd.", and the buyer identifier "Yonyon Co., Ltd.". The bill storage unit 132 also acquires the file name "img4.png" of the bill image. Furthermore, since the received purchase statement information is unconfirmed, the invoice storage unit 132 acquires the confirmation information "OFF". Next, the bill storage unit 132 uses the acquired information to configure bill information to be stored, and stores the information in the bill management table (FIG. 10). Such bill information is the record “ID=101” in FIG.

Next, the support unit 134 determines that the type identifier corresponding to the accumulated bill information is "Purchase Statement."

Next, the support unit 134 obtains the seller identifier "Shushu Bussan Co., Ltd." from the received bill information. Next, the support unit 134 acquires seller contact information (here, an e-mail address) paired with the seller identifier. Although the seller contact information paired with the seller identifier is stored in the user management table, for example, it may be associated with the received bill information. Next, the support unit 134 obtains contact information (here, e-mail) that is information indicating that the purchase statement information has been received. Note that the support unit 134, for example, reads a template of contact information from the storage unit 11, substitutes information specific to the received bill information (for example, address, URL of the bill image) into the template, and sends the contact information. Configure information.

Next, the transmitter 14 transmits the acquired contact information to the contact indicated by the seller contact information (for example, "Issu Taro of Issu Bussan Co., Ltd.").

Next, the terminal device 2 of the contact point indicated by the seller contact information receives and outputs the e-mail which is the contact information. An example of such an output is shown in FIG.

Here, it is assumed that "Issuing Taro" has instructed the URL (1201) of FIG. 12 displayed on the terminal device 2.

Then, the terminal device 2 composes a bill transmission instruction for the bill information corresponding to the URL and transmits it to the bill processing device 1.

Next, the instruction receiving unit 122 of the bill processing device 1 receives a bill transmission instruction from the terminal device 2.

Next, the bill acquisition unit 133 acquires the bill image "img4.png" corresponding to the URL (1201). In addition, the bill acquisition unit 133 configures screen information including the bill image and a "agree to terms" button, which is a user interface that prompts confirmation of the bill image. Note that the "agree to terms" button is a button for inputting a confirmation flag indicating that the purchase statement has been confirmed.

Next, the bill transmitting unit 141 transmits the screen information to the terminal device 2 of the issuer Taro who has transmitted the bill transmitting instruction. Note that the screen information includes the bill identifier "R101".

Next, Issu Taro's terminal device 2 receives the screen information and outputs the screen. An example of such a screen is shown in FIG.

It is assumed that Issuing Taro looks at the invoice image 1301 in FIG. 13, confirms the contents of the invoice, and instructs the "agree to terms" button 1302.

Next, Issuing Taro's terminal device 2 receives the confirmation flag. Next, the terminal processing unit 23 configures a confirmation flag and the like to be transmitted. Note that the confirmation flag and the like include a bill identifier "R101" that identifies the bill image. Next, the terminal transmitter 24 transmits the configured confirmation flag and the like to the bill processing device 1.

Next, the receiving unit 12 of the bill processing device 1 receives the confirmation flag and the like. Next, the second support means 1342 obtains confirmation information "ON" corresponding to the received confirmation flag. Next, the second support means 1342 obtains the bill identifier "R101" corresponding to the received confirmation flag. Next, the second support means 1342 stores the confirmation information "ON" in pairs with the acquired bill identification "R101" child. Through this process, the confirmation information of the record "ID=101" in the bill management table (FIG. 10) is updated from "OFF" to "ON".

As described above, according to this specific example, when purchase statement information is received, the type identifier "purchase statement" of the purchase statement information is stored, and the seller receives the purchase statement information. We have sent you contact information asking for confirmation. Further, in this specific example, a confirmation flag is received from the seller side, and confirmation information is accumulated.

(Specific example 3)
It is now assumed that the storage unit 11 of the bill processing device 1 stores a first condition: "The date indicated by the deadline information has arrived. AND Amount < 100,000 yen." It is assumed that the third support means 1343 of the bill processing device 1 has determined that it is time for confirmation support processing.

Then, the third support means 1343 refers to the invoice management table (FIG. 10) and detects invoice information whose type identifier is "purchase statement" and whose confirmation information is "OFF" (unconfirmed). do. Here, it is assumed that the third support means 1343 has detected bill information with "ID=2".

Next, the third support means 1343 acquires the date "June 14, 2020" of the bill information of "ID=2". It is assumed that the third support means 1343 has acquired deadline information "June 21, 2020," which is one week later from the date "June 14, 2020." It is also assumed that the third support means 1343 has acquired today's date "June 21, 2020" from a clock (not shown). Further, the third support means 1343 acquires the amount "30,000" in the bill information of "ID=2". The third support means 1343 then determines that the first condition is satisfied.

Next, the third support means 1343 obtains confirmation information "ON" for the bill information of "ID=2". Next, the third support means 1343 updates the confirmation information included in the bill information of "ID=2" to "ON".

As described above, according to this specific example, the confirmation information of bill information that satisfies the first condition is automatically changed to "ON".

(Specific example 4)
Now, in the storage unit 11 of the bill processing device 1, the first condition "The date indicated by the deadline information has arrived AND the amount < 20,000 yen" and the second condition "The date indicated by the deadline information has arrived AND It is assumed that the amount of money <= 20,000 yen is stored. It is assumed that the third support means 1343 of the bill processing device 1 has determined that it is time for confirmation support processing.

Then, the third support means 1343 refers to the invoice management table (FIG. 10) and detects invoice information whose type identifier is "Purchase Statement" and whose confirmation information is "OFF" (unconfirmed). do. Here, it is assumed that the third support means 1343 has detected bill information with "ID=2".

Next, the third support means 1343 acquires the date "June 14, 2020" of the bill information of "ID=2". It is assumed that the third support means 1343 has acquired deadline information "June 21, 2020," which is one week later from the date "June 14, 2020." It is also assumed that the third support means 1343 has acquired today's date "June 21, 2020" from a clock (not shown). Further, the third support means 1343 acquires the amount "30,000" in the bill information of "ID=2". Then, the third support means 1343 determines, based on the acquired information, that the first condition is not satisfied but the second condition is satisfied.

Next, the third support means 1343 acquires the seller identifier "Issu Bussan Co., Ltd." that is paired with the bill information of "ID=2". Next, it is assumed that the third support means 1343 has acquired seller contact information (for example, the e-mail address of the person in charge of Issu Bussan Co., Ltd.) paired with the seller identifier from the storage unit 11.

Next, the third support means 1343 obtains the reminder information "Please check the following purchase statement. URL1" to confirm the invoice information of "ID=2". Note that URL1 is information about a link to the bill information of “ID=2”. Further, the third support means 1343 acquires a template of reminder information to confirm the bill information of "ID=2" from the storage unit 11, and stores the template in the URL area of the template. Suppose that you have written a link to the invoice information.

Next, the third support means 1343 transmits the acquired reminder information to the contact indicated by the acquired seller contact information. Note that the transmitted reminder information is associated with a bill identifier "R002".

Next, the terminal device 2 of the person in charge at Issu Bussan Co., Ltd. receives and outputs the reminder information in the form of an e-mail. Such output includes "Please check the following purchase statement. URL1."

Then, in response to the reminder information, the person in charge at Issu Bussan Co., Ltd. confirms the purchase statement information and sends an e-mail containing the confirmation information (for example, an e-mail containing "Confirmed.") as a reply. To do, to do. Note that this e-mail is associated with a bill identifier "R002".

Then, the e-mail receiving unit 123 of the bill processing device 1 receives an e-mail that includes "Confirmed." and is associated with the bill identifier "R002."

Next, the processing unit 13 acquires the received email. Next, the processing unit 13 obtains the bill identifier "R002" corresponding to the obtained e-mail. Next, the processing unit 13 stores the obtained e-mail as a pair with the bill identifier "R002".

Next, the first support means 1341 analyzes the obtained e-mail and determines that the e-mail contains information indicating confirmation from "Confirmed.", and determines that the e-mail is a confirmation e-mail. . Next, the first support means 1341 obtains confirmation information "ON" for the purchase statement identified by the invoice identifier "R002". Then, the first support means 1341 stores the confirmation information "ON" in the bill management table in pairs with the bill identifier "R002." Through this process, the confirmation information paired with the bill identifier "R002" is updated to "ON".

As described above, in this specific example, reminder processing can be performed for purchase statement information for which confirmation has not been completed.

As described above, according to the present embodiment, by storing purchase statements and regular invoices in a distinguishable manner, appropriate processing can be performed on purchase statements.

Further, according to the present embodiment, it is possible to support the seller's confirmation of the purchase statement.

Further, according to the present embodiment, confirmation by the seller of the purchase statement can be appropriately supported by a plurality of means. Note that the plurality of means include, for example, means using e-mail and means using an online system.

Further, according to the present embodiment, by setting a deadline for checking the contents of the purchase statement, it is possible to appropriately support the seller's confirmation of the purchase statement.

Further, according to the present embodiment, if the seller has not confirmed the purchase statement by the time corresponding to the deadline for confirming the contents of the purchase statement, the purchase statement is automatically confirmed. By doing so, it is possible to accelerate the progress of transactions.

Further, according to the present embodiment, when the deadline for checking the contents of the purchase statement is met, the seller can be reminded to check the contents of the purchase statement.

Further, according to the present embodiment, if the seller has not confirmed the purchase statement by the deadline for confirming the contents of the purchase statement, automatic confirmation processing or reminder processing is performed. You can appropriately control what you do.

Furthermore, according to the present embodiment, the type of bill can be specified on the terminal device 2.

Note that the processing in this embodiment may be realized by software. Then, this software may be distributed by software download or the like. Furthermore, 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. Note that the software that implements the bill processing device 1 in this embodiment is the following program. In other words, this program allows the computer to receive two or more types of bill information, including purchase statement information, which is bill information issued by the buyer, and regular bill information, which is bill information issued by the seller. a type determining unit that determines which type the invoice information received by the invoice receiving unit is among two or more types including purchase statement information and normal invoice information; A bill that stores the bill information received by the bill receiving unit in a bill management unit that stores one or more pieces of management information having bill information such that the type determined by the type determination unit can be distinguished. This is a program for functioning as a storage section.

Further, FIG. 14 shows the external appearance of a computer that executes the programs described in this specification to realize the bill processing apparatus 1 and the like of the various embodiments described above. The embodiments described above may be implemented in computer hardware and computer programs executed thereon. FIG. 14 is an overview diagram of this computer system 300, and FIG. 15 is a block diagram of the system 300.

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

In FIG. 15, the computer 301 includes, in addition to 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, and an MPU 3013. It is connected and includes a RAM 3016 for temporarily storing application program instructions and providing temporary storage space, and a hard disk 3017 for storing application programs, system programs, and data. Although not shown here, the computer 301 may further include a network card that provides connection to a LAN.

A program that causes the computer system 300 to execute the functions of the bill processing device 1 of the embodiment described above is stored in the CD-ROM 3101, inserted into the CD-ROM drive 3012, and further transferred to the hard disk 3017. good. 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 during execution. The program may be loaded directly from CD-ROM 3101 or the 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 bill processing device 1 of the above-described embodiment. The program need only contain those parts of the instructions that call the appropriate functions (modules) in a controlled manner to achieve the desired results. How computer system 300 operates is well known and will not be described in detail.

In addition, in the above program, in the step of transmitting information and the step of receiving information, processing is performed by hardware. processing) is not included.

Further, the number of computers that execute the above program may be one or more. That is, centralized processing or distributed processing may be performed.

Furthermore, 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 embodiments described above, each process may be realized by being centrally processed by a single device, or may be realized by being distributedly processed by a plurality of devices.

It goes without saying that the present invention is not limited to the above-described embodiments, and that various modifications can be made, and these are also included within the scope of the present invention.

As described above, the bill processing device 1 according to the present invention has the effect of appropriately processing purchase statements, and is useful as a server or the like that manages bill information.

A Information System 1 Bill Processing Device 2 Terminal Device 11 Storage Unit 12 Receiving Unit 13 Processing Unit 14 Transmitting Unit 21 Terminal Storage Unit 22 Terminal Receiving Unit 23 Terminal Processing Unit 24 Terminal Transmitting Unit 25 Terminal Receiving Unit 26 Terminal Output Unit 111 Bill Management section 121 Bill receiving section 122 Instruction receiving section 123 Mail receiving section 131 Type determining section 132 Bill storage section 133 Bill acquisition section 134 Support section 141 Bill transmission section 1341 First support means 1342 Second support means 1343 Third Support means 1344 Fourth support means

Claims (12)

an invoice receiving unit that receives two or more types of invoice information including purchase statement information, which is invoice information issued by the buyer, and regular invoice information, which is invoice information issued by the seller;
a type determining unit that determines which type the bill information received by the bill receiving unit is among two or more types including purchase statement information and regular bill information;
A bill that stores the bill information received by the bill receiving unit in a bill management unit that stores one or more pieces of management information having bill information such that the type determined by the type determination unit can be distinguished. A bill processing device comprising: a storage section; When the type determining unit determines that the type of the bill information received by the bill receiving unit is purchase statement information, the seller of the bill information confirms the purchase statement information. The bill processing device according to claim 1, further comprising a support unit that performs support processing to support the bill processing. The support department is
3. The bill processing device according to claim 2, further comprising two or more different means for supporting confirmation of purchase statement information. This is an email that corresponds to the invoice identifier and is a confirmation email that indicates that the seller has confirmed the purchase statement information identified by the invoice identifier. It further includes an e-mail receiving section for receiving e-mails,
The support department is
If the e-mail received by the e-mail reception unit is a confirmation e-mail, send confirmation information indicating that the purchase statement information has been confirmed by the seller, paired with the invoice identifier corresponding to the confirmation e-mail. 3. The bill processing apparatus according to claim 2, further comprising a first support means for performing confirmation processing of accumulated mail. an invoice acquisition unit that acquires purchase statement information identified by one invoice identifier from the invoice management unit;
further comprising an invoice transmission unit that transmits the purchase statement information acquired by the invoice acquisition unit to the seller terminal,
The support department is
In response to the invoice transmitting unit transmitting the purchase statement information, a confirmation flag indicating that the seller corresponding to the seller terminal has confirmed the purchase statement information is received, and the processing unit responds to the confirmation flag. 3. The bill processing apparatus according to claim 2, further comprising second support means for performing an online confirmation process of storing confirmation information in pairs with said one bill identifier. The support department is
In response to the receipt of the purchase statement information by the invoice receiving unit, the purchase statement information is confirmed by a time corresponding to a confirmation deadline indicated by deadline information for the purchase statement information. 3. The bill processing apparatus according to claim 2, further comprising third support means for performing confirmation support processing to support the confirmation. The third support means is
In response to the receipt of the purchase statement information by the invoice receiving unit, the invoice receiving unit may pair the purchase statement information with the purchase statement information by the time corresponding to the confirmation deadline indicated by the deadline information for the purchase statement information. 7. The bill processing apparatus according to claim 6, wherein automatic confirmation processing is performed to accumulate confirmation information. The purchase statement information is associated with seller contact information that specifies the contact information for the seller.
The third support means is
In response to the receipt of the purchase statement information by the invoice receiving unit, identify the purchase statement information by a time corresponding to a confirmation deadline indicated by deadline information for the purchase statement information. It is determined whether confirmation information paired with the invoice identifier has been accumulated, and if it has not been accumulated, the purchase statement information is sent to the seller using the seller contact information corresponding to the purchase statement information. 7. The bill processing apparatus according to claim 6, wherein the bill processing apparatus performs a reminder process of transmitting reminder information prompting the user to confirm the information. The third support means is
In response to the receipt of the purchase statement information by the invoice receiving unit, the purchase statement information is identified by a time corresponding to a confirmation deadline indicated by deadline information for the purchase statement information. automatic confirmation processing that determines whether confirmation information paired with the invoice identifier has been accumulated, and if not accumulated, stores confirmation information in pairs with the purchase statement information;
In response to the receipt of the purchase statement information by the invoice receiving unit, the purchase statement information is identified by a time corresponding to a confirmation deadline indicated by deadline information for the purchase statement information. It is determined whether confirmation information paired with the invoice identifier has been accumulated, and if it has not been accumulated, the purchase statement information is sent to the seller using the seller contact information corresponding to the purchase statement information. If the relevant information regarding the purchase statement information satisfies the first condition, the automatic confirmation process is performed to send reminder information to encourage the purchase statement information to be confirmed. 7. The bill processing device according to claim 6, wherein the reminder process is performed when the related information satisfies the second condition. a bill acquisition unit that acquires bill information from the bill management unit;
further comprising a bill transmitting unit that transmits the bill information acquired by the bill acquiring unit to the seller terminal,
The bill transmitter includes:
The bill processing device according to claim 1, wherein the bill information is transmitted to the seller terminal so that the type of the bill information can be specified. A bill processing method realized by a bill receiving section, a type determining section, and a bill storage section, the method comprising:
Invoice reception, in which the invoice receiving unit receives two or more types of invoice information including purchase statement information, which is invoice information issued by a buyer, and regular invoice information, which is invoice information issued by a seller. step and
a type determining step in which the type determining unit determines which type the invoice information received in the invoice receiving step is among two or more types including purchase statement information and normal invoice information; and,
The bill storage unit stores the bill information received by the bill receiving unit, and one or more pieces of management information including the bill information, such that the type determined in the type determination step can be distinguished. A bill processing method comprising: a step of accumulating bills in a bill management section. computer,
an invoice receiving unit that receives two or more types of invoice information including purchase statement information, which is invoice information issued by the buyer, and regular invoice information, which is invoice information issued by the seller;
a type determining unit that determines which type the bill information received by the bill receiving unit is among two or more types including purchase statement information and regular bill information;
A bill that stores the bill information received by the bill receiving unit in a bill management unit that stores one or more pieces of management information having bill information such that the type determined by the type determination unit can be distinguished. A program to function as a storage section.

Images