Information processing device, information processing method, and program

Abstract

To provide an information processing apparatus, an information processing method, and a program for generating new benefits in an accounting field.SOLUTION: In a bill management system 10, a bill management device 1 has: a bill data storage unit 12 that, when receiving bill data transmitted from a terminal device to a specific recipient through a network, stores the received bill data in association with identification information on the recipient and identification information on an issuer of the bill data; and a data processing unit 11 that, in response to the reception of the bill data, generates BI tokens that can be exchanged with currencies in the future and are individually unique to the issuer and the recipient, and stores the generated BI tokens in a given token management table in association with the received bill data.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] One method for protecting business document information from tampering is known as blockchain, which performs a so-called mining process at regular intervals to reach a consensus. Furthermore, there is known a technology that enables viewing of business documents (for example, invoices) of an entire company or an entire corporate group and centralized management of the information.

[0003] For example, an information processing device is known that includes: a memory unit that, when business document data sent from a terminal device to a specific recipient is received over a network, stores the received business document data in association with the recipient's identification information and the identification information of the issuer of the business document data; a judgment unit that determines whether at least one of the number of status changes indicating the progress of processing related to the business document data between the issuer and the recipient or the number of changes to the data accompanying the business document data has reached a predetermined number; and a transmission unit that, when the predetermined number of changes has been reached, collects the business document data and the data accompanying the business document data and transmits it to multiple consensus building devices that form consensus. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2020 / 009118 Summary of the Invention [Problem to be solved by the invention]

[0005] It is known that using blockchain technology, tokens with some value can be issued, and it is conceivable that these tokens could be applied to the field of business document data. In particular, applying tokens to the accounting field, which has not been considered profitable until now, is expected to generate new profits. In one aspect, the present invention aims to create new benefits in the field of accounting. [Means for solving the problem]

[0006] To achieve the above object, an information processing device is disclosed that includes a storage unit that, upon receiving document data relating to a business document sent from a terminal device to a specific recipient via a network, stores the received document data in association with identification information of the recipient and identification information of an issuer of the document data, and a processing unit that, in response to the receipt of the document data, generates unique tokens for the issuer and recipient that can be exchanged for currency in the future, and stores the generated tokens in association with the received document data in the storage unit. [Effects of the Invention]

[0007] In one aspect, new benefits can be generated in the accounting field. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 illustrates an invoice management system according to a first embodiment. [Figure 2] FIG. 10 is a diagram illustrating an example of a screen displayed on a terminal device after login. [Figure 3] 1 is a diagram illustrating a hardware configuration of an invoice management apparatus according to an embodiment. [Figure 4] 2 is a block diagram showing the functions of the invoice management device according to the embodiment. FIG. [Figure 5] FIG. 10 is a diagram illustrating an example of invoice data. [Figure 6]10 is an example of information stored in a token storage unit. [Figure 7] 10 is an example of information stored in a token storage unit. [Figure 8] FIG. 10 is a diagram illustrating information displayed in a summary display section. [Figure 9] FIG. 10 is a diagram illustrating information displayed in a summary display section. [Figure 10] FIG. 2 is a block diagram illustrating functions of a database according to an embodiment. [Figure 11] FIG. 10 is a diagram illustrating an example of information included in a blockchain according to an embodiment. [Figure 12] 10 is a flowchart illustrating the processing of the data processing unit involved in sending and receiving invoice data. [Figure 13] 10 is a flowchart illustrating a deposit process. [Figure 14] 10 is a flowchart illustrating a process for managing the amount of generated tokens. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, the bill management system according to the embodiment will be described in detail with reference to the drawings. First Embodiment FIG. 1 illustrates an invoice management system according to the first embodiment.

[0010] In the invoice management system 10 of the first embodiment, an invoice management device 1 is connected to terminal devices 2a, 2b, and 2c via a network such as the Internet or a dedicated line.

[0011] Terminal device 2a is located in the accounting department of company A, terminal device 2b is located in company B, terminal device 2c is located in company C, etc. Terminal devices 2a, 2b, and 2c are devices located in the accounting department of each of different companies. Examples of terminal devices 2a, 2b, and 2c include desktop PCs, notebook PCs, tablet devices, and smartphones.

[0012] The invoice management device 1 and terminal devices 2a, 2b, and 2c implement web programs. Terminal devices 2a, 2b, and 2c exchange invoice data related to invoices with the invoice management device 1 via a web browser. Note that while the exchange of invoice data is illustrated in this embodiment, an invoice is an example of a business document, and the present invention is not limited to the exchange of invoices. Other examples of business documents include estimates and order forms.

[0013] The invoice management device 1 transmits information (such as a hash of a file) to be written to the blockchain onto the network. In this embodiment, the information to be written is invoice data and data accompanying the invoice data. The databases 3a, 3b, and 3c are connected to each other via a blockchain network 20. The databases 3a, 3b, and 3c generate hash functions that are uniquely determined based on some data and are irreversible and random. The following description will be given assuming that the invoice management system 10 is used by accounting staff at companies A, B, and C.

[0014] Each accounting staff member at Company A, Company B, and Company C registers as a user in the invoice management device 1 using their assigned email address, etc., thereby creating an environment for accessing the invoice processing system built by the invoice management device 1.

[0015] Thereafter, for example, an accounting clerk at Company A operates terminal device 2a, causing the invoice management device 1 to display a login screen on the monitor connected to terminal device 2a. The accounting clerk can log in to the service provided by the invoice management device 1 by entering an email address and password on the login screen. The email address is an example of identification information that identifies the accounting clerk.

[0016] After logging in, the terminal devices 2a, 2b, and 2c can execute processes related to invoice data, which is the digitized version of the original invoice, via the invoice management device 1. Types of processes include, for example, creating, sending, receiving, viewing, and editing invoice data.

[0017] For example, when an accounting clerk at Company A issues an invoice to Company B, the accounting clerk at Company A operates the terminal device 2a to create an invoice with Company B as the billing destination on the management screen that is displayed after logging in. Then, the accounting clerk sends invoice data specifying the email address of the accounting clerk (recipient) at Company B as the destination of the created invoice. The sent invoice data is stored in the invoice management device 1.

[0018] That is, instead of directly exchanging invoice data between terminal devices 2a, 2b, and 2c, all invoice data created on terminal devices 2a, 2b, and 2c and sent to the invoice destination is stored in the invoice management device 1 and treated as shared data.The invoice management device 1 then grants the terminal devices 2a, 2b, and 2c the authority to view and edit the invoice data as necessary. In this way, the original invoice itself can be digitized and processed electronically, eliminating the need to manage and store paper or PDF invoices.

[0019] As mentioned above, invoice data is not directly exchanged between the terminal devices 2a, 2b, and 2c, but is stored in the invoice management device 1. However, in the following explanation, for ease of understanding, for example, if an accountant at company A sends invoice data addressed to the email address of an accountant at company B, As with the general exchange of invoice data, the expression "the accounting staff receives the invoice data" is sometimes used. It is preferable that the bill data exchanged between the bill management apparatus 1 and each of the terminal devices 2a, 2b, and 2c is encrypted. FIG. 2 is a diagram illustrating an example of a screen displayed on the terminal device after login. The management screen 110 shown in FIG. 2 is an example of a screen displayed on the terminal device 2a. As shown in Figure 2, accounting staff can create, issue, view, edit, etc. invoice data in a manner similar to that of email software.

[0020] In the above example, the accounting staff of Company A cannot rewrite invoice data once it has been sent. Likewise, the accounting staff of Company B cannot rewrite the invoice data. If there is a defect in the invoice data, a different version of the invoice data will be reissued. Furthermore, the old version of the invoice data is not discarded but is stored in the invoice management device 1 and can be viewed at any time. Furthermore, the invoice management device 1 also manages the version number of invoice data, making it easy to search for new version of invoice data from old version of invoice data and search for old version of invoice data from new version of invoice data. The management screen 110 will be described in detail later.

[0021] When a new invoice data exchange (transaction) occurs, the invoice management device 1 notifies the databases 3a, 3b, and 3c of the transaction details. The administrators of the databases 3a, 3b, and 3c refer to their own databases to check whether there is any fraud in the exchange of the new invoice data.

[0022] Then, a consensus is formed to decide who has the authority to update the database. Consensus formation methods include, for example, Proof of Work and Proof of Stake.

[0023] For example, if the administrator of database 3a discovers the answer first, the administrator of database 3a will notify the participants of other databases 3b and 3c that the answer has been discovered. At this time, some compensation may be paid to the administrator of the database 3a. The administrators of the databases 3a, 3b, and 3c add the transaction data notified by the invoice management device 1 to their own databases. The disclosed bill management system will be described in more detail below. FIG. 3 is a diagram illustrating a hardware configuration of the invoice management apparatus according to the embodiment.

[0024] The invoice management apparatus 1 is entirely controlled by a CPU (Central Processing Unit) 101. A RAM (Random Access Memory) 102 and a plurality of peripheral devices are connected to the CPU 101 via a bus 108.

[0025] The RAM 102 is used as the main storage device of the invoice management device 1. The RAM 102 temporarily stores at least a portion of the OS (Operating System) programs and application programs executed by the CPU 101. The RAM 102 also stores various data used in processing by the CPU 101.

[0026] A hard disk drive (HDD) 103, a graphics processing unit 104, an input interface 105, a drive unit 106, and a communication interface 107 are connected to the bus 108.

[0027] The hard disk drive 103 magnetically writes and reads data to and from the built-in disk. The hard disk drive 103 is used as a secondary storage device for the invoice management device 1. The hard disk drive 103 stores the OS program, application programs, and various data. Note that a semiconductor storage device such as a flash memory can also be used as the secondary storage device.

[0028] A monitor 104a is connected to the graphics processing unit 104. The graphics processing unit 104 displays an image on the screen of the monitor 104a in accordance with an instruction from the CPU 101. Examples of the monitor 104a include a display device using a CRT (Cathode Ray Tube) and a liquid crystal display device.

[0029] A keyboard 105a and a mouse 105b are connected to the input interface 105. The input interface 105 transmits signals sent from the keyboard 105a and the mouse 105b to the CPU 101. Note that the mouse 105b is an example of a pointing device, and other pointing devices can also be used. Examples of other pointing devices include a touch panel, a tablet, a touch pad, and a trackball.

[0030] The drive device 106 reads data recorded on a portable recording medium such as an optical disc on which data is recorded so that it can be read by reflected light, or a USB (Universal Serial Bus) memory. For example, if the drive device 106 is an optical drive device, it reads data recorded on an optical disc 200 using laser light or the like. Examples of the optical disc 200 include Blu-ray (registered trademark), DVD (Digital Versatile Disc), DVD-RAM, CD-ROM (Compact Disc Read Only Memory), and CD-R (Recordable) / RW (Rewritable).

[0031] The communication interface 107 is connected to the network 50. The communication interface 107 transmits and receives data to and from other computers or communication devices via the network 50.

[0032] The processing functions of this embodiment can be realized with the hardware configuration described above. Note that while Figure 3 shows the hardware configuration of the invoice management device 1, other computers such as the terminal device 2a can also be realized with a similar hardware configuration. The invoice management device 1 having the hardware configuration shown in FIG. 3 has the following functions. FIG. 4 is a block diagram showing the functions of the invoice management device according to the embodiment.

[0033] The invoice management device 1 has a data processing unit 11, an invoice data storage unit 12, an external contact data storage unit 13, an attachment data storage unit 14, a history data storage unit 15, a memo data storage unit 16, a block data generation unit 17, and a token storage unit 18.

[0034] The data processing unit 11 displays the management screen 110 shown in Fig. 2 on the terminal device 2a or the like in response to the operation of the accounting staff. The data processing unit 11 executes processing in response to the exchange of invoice data carried out via the management screen 110. For example, the data processing unit 11 distributes and stores in each storage unit the invoice data received by the invoice management device 1, external communications (described later) and memos created by the accounting staff, etc.

[0035] Furthermore, for example, when an accounting staff member of Company A creates invoice data addressed to Company B and the invoice management device 1 receives the invoice data, the data processing unit 11 assigns a unique token (hereinafter referred to as a BI token) to each of Company A and Company B. In this embodiment, every time each company transmits or receives invoice data, the data processing unit 11 assigns a BI token to each of the invoice source and invoice destination of the invoice data.

[0036] This BI token can be generated, for example, by the transaction data generation unit 17 managing the invoice data using blockchain technology (preventing tampering with the invoice data). The BI token contains information that can identify the invoice data. In other words, the data processing unit 11 assigns the BI token generated by the transaction data generation unit 17 using blockchain technology to the billing source and billing destination of the invoice data at the timing of sending and receiving the invoice data. The data processing unit 11 stores in the token storage unit 18 the amount of BI tokens issued that the transaction data generation unit 17 has generated and the amount of BI tokens that have already been granted.

[0037] This BI token can be treated as a claim having value that can be converted into virtual currency or legal currency, for example, by having the administrator of the invoice management device 1 guarantee the value of the BI token.

[0038] In addition, BI tokens can be entrusted to a virtual currency exchange (cryptocurrency exchange business) after passing an examination. In that case, BI tokens will be listed and made public, and the rate of the BI tokens themselves will also fluctuate. This rate will also be applied when redeeming.

[0039] The data processing unit 11 also monitors the amount of BI tokens issued. When the amount of BI tokens issued reaches a certain number or more, the administrator of the invoice management device 1 may purchase the BI tokens at a set rate. If the BI tokens are not listed, the set rate is, for example, a rate predetermined by the administrator of the invoice management device 1. If the BI tokens are listed, the set rate is determined, for example, based on the listed price on an exchange.

[0040] In this way, the use of unique tokens creates an incentive for accounting staff to use the service, thereby encouraging active use of the invoice management device 1 by users compared to the use of conventional systems such as EDI (Electronic Data Interchange).

[0041] The granted BI tokens can be managed individually for each predetermined unit. This unit can be, for example, an individual, a corporation, a department (division, section), etc. In this embodiment, the corporation is used as the unit.

[0042] The invoice data storage unit 12 stores invoice data received by the invoice management device 1 for each accountant (specifically, for each email address of the accountant). The invoice data received by the invoice management device 1 includes invoice data sent by the invoice source accountant to the invoice destination accountant, and invoice data created as a draft by the invoice source accountant (issuer). FIG. 5 is a diagram illustrating an example of invoice data. In this embodiment, the data is stored in the form of a table.

[0043] The invoice data management table T1 has columns for invoice ID, transmission / reception, transmission / reception date and time, person in charge status, other party status, person in charge address, person in charge name, other party address, and other party person in charge name. The information listed horizontally is related to each other.

[0044] The invoice ID field stores an ID unique to the invoice data for managing the invoice data. This invoice ID is assigned to the invoice data by the data processing unit 11 when the invoice management device 1 receives the invoice data.

[0045] In the "Sent / Received" column, a classification is set to indicate whether the invoice data is received or sent from the accounting staff's perspective. Specifically, "Received" is set for received invoice data, and "Sent" is set for sent invoice data. The transmission / reception date / time field stores the most recent date / time when the bill data was transmitted / received. The status of the invoice data (progress in processing) from the perspective of the accounting staff is set in the staff status column. The status of the invoice data as seen by the accounting staff of the other party exchanging the invoice data is set in the partner status column.

[0046] The statuses that can be set in the column for the person in charge status and the column for the other party status include "Unopened", "Returning", "Discarded by the other party", "Confirmed", "Paid", "Storage box", "Sent", "Returned", "Discarded", and "Payment completed". The contents of each status will be explained in detail later. The person in charge address field stores the email address of the person in charge of accounting. The name of the person in charge is stored in the person in charge column. The recipient address field stores the email address of the person in charge of accounting who will be exchanging the invoice data. The name of the person in charge of the other party field stores the name of the person with whom the bill data is exchanged.

[0047] In addition to the information shown in the figure, the information stored in the invoice data management table includes the company name and department name of the accounting staff member, the company name and department name of the accounting staff member with whom the invoice data is exchanged, each company's postal code, address, billing items, billing amount, and other invoice-related data.

[0048] Next, we will explain the information stored in the token storage unit 18. The token storage unit 18 stores information about the amount of generated BI tokens and information about the amount of granted BI tokens. FIG. 6 is an example of information stored in the token storage unit.

[0049] The wallet management table T2 shown in Fig. 6 has columns for the address of the person in charge and the wallet number. The information arranged horizontally is associated with each other.

[0050] The wallet number field stores a number that identifies the destination of the currency obtained by converting BI tokens into cash. There may be one wallet or multiple wallets. The currency may be virtual currency or legal tender. The type of wallet is not particularly limited, and can be specified by an accounting staff member when creating the invoice data. The timing of conversion into cash is also optional. The wallet may also store information indicating when and at what rate the BI tokens were redeemed.

[0051] 6 shows an example in which the grant amount and wallet size are set for each person in charge, but the grant amount and wallet size may be set for any unit (for example, for each department or company). The grant amount may also be set on a daily, weekly, or monthly basis. FIG. 7 is an example of information stored in the token storage unit.

[0052] 7 has columns for company ID, contact person address, transaction date and time, amount granted at time of sending, amount granted at time of receiving, total amount granted, remaining amount, total amount issued, and buyback. The information arranged horizontally is associated with each other. In the company name ID, information for identifying the company name is set. The person in charge address field stores the email address of the rights manager. The amount of BI tokens granted at the time of transmission field stores the amount of BI tokens granted by the data processing unit 11 when the accounting staff member sends the invoice data. The amount of BI tokens granted at time of reception field stores the amount of BI tokens granted by the data processing unit 11 when the accounting staff member transmits the invoice data. The total amount of BI tokens granted when exchanging invoice data is stored in the Total Amount column. The remaining amount field stores the amount obtained by subtracting the total amount given from the total amount produced. The total amount generated column stores the amount of BI tokens generated so far. The buyback column stores the amount of BI tokens that the data management device 1 has bought back. The data processing unit 11 confirms that the total amount of generated BI tokens matches (1000 in this embodiment) every time BI tokens are granted.

[0053] As shown in FIG. 7, in this embodiment, the data processing unit 11 assigns a predetermined amount of BI tokens to each sender and receiver, with each set consisting of transmission and reception of bill data.

[0054] Then, when a buyback request is received from the accounting staff at any time, the data processing unit 11 will buy back the received amount of BI tokens. Set Rate The amount is converted into cash and deposited into the wallet of the accounting officer in question. Next, the management screen will be described. <Management screen> The data processing unit 11 displays the management screen 110 shown in FIG. 2 on the terminal device 2a or the like in response to an operation by the accounting clerk.

[0055] The management screen 110 displays a user information display section 111, a status display section 112, a summary display section 113, an invoice display section 114, an external contact button 115, an attachment button 116, a history button 117, a memo button 118, an external contact list button 119, a memo list button 120, an information display section 121, an information input section 122, and a token redemption button 123.

[0056] Information (user information) about the accountant who is logged in to the invoice management system is displayed in the user information display section 111. In Fig. 2, as an example, the name of the company to which the accountant belongs, the name of the department, the last name, and the email address of the accountant are displayed. The status display section 112 displays the number of invoice data handled by the accounting staff logged in to the invoice management system for each status. The status display section 112 is roughly divided into columns for the received box, drafts, sent box, and sent / received box. The data processing unit 11 allocates the invoice data addressed to the email address of the accounting staff to the inbox.

[0057] When the accounting staff member selects the inbox, the data processing unit 11 refers to the invoice data management table T1 and displays in the summary display unit 113 a summary of the invoice data whose accountant address matches "bbb@xxmail.co.jp" and whose transmission / reception column is set to "received."

[0058] As shown in Figure 2, the status of invoice data assigned to the inbox can be broken down into "unopened," "in return," "discarded by recipient," "confirmed," "paid," and "storage box."

[0059] The status "unopened" is a status that the data processing unit 11 assigns to invoice data that has been assigned to the inbox and that has not yet been confirmed by the accounting staff.

[0060] The status "Returning" is a status that the data processing unit 11 assigns to invoice data that has been assigned to the inbox and that has been returned by the accounting staff to the accounting staff who made the invoice.

[0061] The status "Discarded by the other party" is a status that the data processing unit 11 assigns to invoice data that has been assigned to the inbox and that has been discarded by the accounting staff of the billing entity after the accounting staff has returned the received invoice data to the billing entity.

[0062] The status "Confirmed" is a status that the data processing unit 11 assigns to invoice data that has been assigned to the inbox and that has been viewed by an accounting staff member and for which the confirmation button (described later) has been selected.

[0063] The status "paid" is assigned by the data processing unit 11 to invoice data allocated to the inbox for which the accounting staff has made a deposit and selected a payment button (not shown). Accounting staff can keep track of payment details by aggregating invoice data with a paid status.

[0064] The status "storage box" is a status that the data processing unit 11 assigns to invoice data that has the status "paid" and that has been moved to the storage box by the accounting staff at any time. The numbers displayed in the status display section 112 indicate the number of assigned statuses. For example, the unopened column of the status display section 112 displays the number of invoice data items that have not yet been checked by the accounting staff out of the received invoice data items. It should be noted that no particular numbers are displayed in the storage box column of the status display section 112.

[0065] When an accounting staff member wants to view the contents of the invoice data assigned to each of the following boxes, "Unopened," "In Return," "Discarded by Recipient," "Confirmed," "Paid," and "Storage Box," he or she simply selects the appropriate section in the status display section 112.

[0066] For example, when an accounting clerk selects the inbox, the data processing unit 11 refers to the invoice data management table T1. Then, the data processing unit 11 displays, in the summary display unit 113, a summary of the invoice data whose accountant status is unopened, among the invoice data whose accountant address matches "bbb@xxmail.co.jp". The data processing unit 11 assigns the invoice data that has been created and saved by the accounting staff but has not yet been sent to the accounting staff of the destination to the draft. The data processing unit 11 allocates the invoice data sent by the accounting staff to the transmission box.

[0067] When the accounting staff member selects the Send BOX, the data processing unit 11 refers to the invoice data management table T1 and displays in the summary display unit 113 a summary of the invoice data whose accountant address matches "bbb@xxmail.co.jp" and whose sending / receiving column is set to "Sent."

[0068] As shown in Figure 2, the status of invoice data allocated to the Outbox can be broken down into "Sent," "Returned," "Discarded," "Payment," and "Storage box."

[0069] The status "Sent" is a status that the data processing unit 11 assigns to invoice data that has been assigned to the Outbox and for which the accounting staff of the invoice recipient has not yet carried out payment processing.

[0070] The "returned" status is a status that the data processing unit 11 assigns to invoice data that has been assigned to the Outbox and that has been returned from the accounting staff of the invoice destination. The accounting staff can then process the invoice data that has been returned from the invoice destination.

[0071] The status "destroyed" is a status that the data processing unit 11 assigns to invoice data that has been returned from the invoice recipient's accountant and that has been destroyed by the invoice source's accountant.

[0072] The status "paid" is assigned by the data processing unit 11 to invoice data allocated to the outbox for which the billing accountant has confirmed the payment and selected the payment button (not shown).

[0073] The status "storage box" is a status that the data processing unit 11 assigns to invoice data that has the status "paid" and that has been moved to the storage box by the accounting staff at any time. In the storage box column of the status display section 112, no particular number is displayed.

[0074] To view the contents of the invoice data stored in the "Sent," "Returned," "Discarded," "Payed," or "Storage Box" boxes, simply select the box.

[0075] As described above, the summary display section 113 displays a summary of the invoice data corresponding to the status selected by the accounting staff in the status display section 112. For received invoice data, the summary displays the name of the company that made the invoice, the subject, the payment due date, and the statuses of the sender and receiver. These statuses are displayed identically on the management screens of both accounting staff who sent and received the invoice data. 8 and 9 are diagrams for explaining information displayed in the summary display section.

[0076] Figure 8 shows an invoice data summary 113a displayed in the summary display section 113 of the management screen 110 viewed by the accounting staff of the billing recipient, and an summary 113b displayed in the summary display section 113 of the management screen 110 viewed by the accounting staff of the billing source.

[0077] 8, the invoice data D1 whose biller is ABC Co., Ltd. and whose subject is XX work is displayed as "Sent" in the status display section on the management screen of the terminal device operated by the biller's accounting clerk. When the biller's accounting clerk selects "Sent" in the status display section, the summary display section 113 displays that the billing destination is XX Co., Ltd., the subject is XX work, the billing destination's accounting clerk's status is "Sent", and the billing destination's accounting clerk's status is "Unopened".

[0078] In addition, by checking the status transition, the invoicer's accountant can easily check the progress of the invoice recipient's processing, allowing both accountants to check the current status of each invoice data in real time. The summaries 113c, 113d, and 113e shown in FIG. 9(a) all show summaries of the invoice data D2.

[0079] When the billing recipient's accounting staff views the invoice data D2 and selects the confirmation button (described below), the data processing unit 11 changes the information displayed in the summary display section 113 of the management screen 110 of the terminal device operated by the billing source's accounting staff from summary 113c to summary 113d.

[0080] Thereafter, when the billing recipient's accounting staff performs the payment process for the invoice data D2 and selects the Paid button (not shown), the data processing unit 11 changes the information displayed in the summary display section 113 of the management screen 110 of the terminal device operated by the billing source's accounting staff from summary 113d to summary 113e. As another example, summaries 113f and 113g shown in FIG. 9(b) each indicate a summary of the invoice data D3.

[0081] When the billing recipient's accounting staff views the invoice data D3 and selects the return button (described later), the data processing unit 11 changes the information displayed in the summary display section 113 of the management screen of the terminal device operated by the billing recipient's accounting staff from summary 113f to summary 113g. Returning to FIG. 2 for further explanation.

[0082] When the accounting staff selects the summary of the invoice data displayed in the summary display section 113, the data processing section 11 displays the details of the invoice data in the invoice display section 114. The content of the invoice displayed in the invoice display section 114 is the same as an existing (paper or PDF-based) invoice, except that it has an address display section 114a and various buttons described later.

[0083] When the accounting staff member views the invoice data allocated to the inbox, the data processing unit 11 displays the email address of the accounting staff member who sent the invoice data (from) in the address display unit 114a.

[0084] Furthermore, when the accounting staff member views the invoice data allocated to the draft or transmission box, the data processing unit 11 displays the email address of the accounting staff member (to) who is the transmission destination. The data processing unit 11 may display the invoice ID of the invoice data on the invoice display unit 114. The accounting staff can process the invoice displayed in the invoice display section 114 on the management screen 110. Specifically, buttons for processing the invoice are displayed in the invoice display section 114 depending on the status of the invoice data. Figure 2 shows the buttons that are displayed when invoice data with a status of Unopened is selected. The bill display section 114 is provided with a confirmation button 114b, a return button 114c, and a copy button 114d.

[0085] When the accounting staff member selects the Confirm button 114b, the data processing unit 11 refers to the invoice data management table T1. Then, it changes the staff member status of the invoice data displayed in the invoice display unit 114 to "Confirmed." The data processing unit 11 also decreases the number for "Unopened" in the status display unit 112 by one and increases the number for "Confirmed" by one.

[0086] When the accounting staff selects the return button 114c, the data processing unit 11 refers to the invoice data management table T1. Then, it changes the staff status of the invoice data displayed in the invoice display unit 114 to "Returning" and the recipient status to "Returned." The data processing unit 11 also decreases the number for "Unopened" in the status display unit 112 by one and increases the number for "Returning" by one. On the management screen of the accounting staff member who receives the returned invoice data, the returned number in the status display section will be increased by one.

[0087] When the accounting staff selects the copy button 114d, the data processing unit 11 creates new invoice data in which the company names and addresses of the billing source and billing recipient of the invoice data have been swapped. The data processing unit 11 then stores information about the created invoice data in the invoice data management table T1. At this time, the staff status of the invoice data becomes "draft" and the recipient status becomes blank. Returning to FIG. 2 for further explanation.

[0088] The sending / receiving box is allocated with all the invoice data stored in the receiving box and sending box, excluding the discarded invoice data, the invoice data allocated to the storage box, and the invoice data allocated to the draft box. <External contact button>

[0089] When the accounting staff member selects the external contact button 115, the data processing unit 11 switches the management screen 110 to the external contact input mode. In this external contact input mode, the data processing unit 11 stores a document (text data) that has been entered into the information input unit 122 and confirmed by pressing the Enter key on the keyboard, etc., as an external contact in the external contact data storage unit 13 in association with the accounting staff member's email address and the invoice data displayed in the invoice display unit 114. <Attachment button>

[0090] When the accounting clerk selects the attachment button 116, the data processing unit 11 switches the management screen 110 to attachment mode. In this attachment mode, the data processing unit 11 stores the attachment data, which has been clicked and dragged to the information input unit 122 and confirmed by pressing the Enter key on the keyboard, in the attachment data storage unit 14 in association with the accounting clerk's email address and the invoice data displayed in the invoice display unit 114. <History button> The data processing unit 11 stores the operation history (history data) of both accounting staff members in the history data storage unit 15. <Memo button>

[0091] When the accounting clerk selects the memo button 118, the data processing unit 11 switches the management screen 110 to memo input mode. In this memo input mode, the data processing unit 11 stores characters and the like entered into the information input unit 122 and confirmed by pressing the Enter key on the keyboard, as a memo, in the memo data storage unit 16 in association with the accounting clerk's email address and the invoice data displayed in the invoice display unit 114. This memo can only be viewed by the person who created it. <External Contact List Button>

[0092] When the accounting staff member selects the external contact list button 119, the data processing unit 11 refers to the external contact data storage unit 13 in which data related to external contacts is stored, and displays a list screen of external contacts (external contact list screen) related to invoices handled by the accounting staff member in chronological order on the management screen 110. <Memo list button>

[0093] When the accounting staff member selects the memo list button 120, the data processing unit 11 refers to the memo data storage unit 16 in which data related to external contacts is stored, and displays a list screen (memo list screen) of memos related to invoices handled by the accounting staff member in chronological order on the management screen 110. <Token redemption button>

[0094] When the accounting clerk selects the token exchange button 123, the data processing unit 11 executes a process (deposit process) to exchange the amount of the invoice currently displayed in the invoice display unit 114 for cash using BI tokens. This process will be described in detail later. Returning to FIG. 4, the explanation will be given again.

[0095] When the transaction data has been updated a predetermined number of times, transaction data generation unit 17 collects the transaction data stored in each storage unit 12-16, encrypts and signs it, and transmits it to databases 3a, 3b, and 3c where consensus is built. Additionally, transaction data includes at least one of invoice data, invoice data status, external contact data, attachment data, history data, and memo data.

[0096] A BI token is generated at the timing of block generation. The transaction data generation unit 17 stores the generated BI token in the token storage unit 18. After that, the transaction data generation unit 17 resets the value of the counter that has reached a predetermined number of times. Next, the functions of the databases 3a, 3b, and 3c will be described. FIG. 10 is a block diagram illustrating the functions of the database according to the embodiment. The database 3a includes a storage unit 31, a transmitter / receiver unit 32, a block header generator unit 33, and a consensus building unit .

[0097] The storage unit 31 stores a block 311 and a database list 312. It goes without saying that the information stored in the storage unit 31 is not limited to these.

[0098] Block 311 is a collection of information (transaction) to be registered in the blockchain, such as an individual transaction history or a collection of computer processes, with the information necessary to configure the blockchain added. FIG. 11 is a diagram illustrating an example of information included in the blockchain according to the embodiment. The block 311 includes a block number 311a, a timestamp 311b, and a transaction list 311c. The block number 311 a is information for identifying the block 311 . The timestamp 311b is the timestamp of the newly created block.

[0099] The transaction list 311c refers to a collection of transaction history and computer processing. Here, it refers to a list of collections of information to be registered in the blockchain. Specifically, it includes invoice data, external contact data, attachment data, history data, memo data, the wallet number of the billing source for the invoice data, and the wallet number of the billing recipient.

[0100] The database list 312 is a list that stores identification information (e.g., IP addresses) that identify other databases connected to the blockchain network 20. The transmitter / receiver 32 receives data to be recorded in the block 311 (data to be recorded) from the invoice management apparatus 1. The block header generating unit 33 generates a hash value by using a hash function on the data to be recorded. Furthermore, the block header generation unit 33 generates a block header using the generated hash value, the hash value of the immediately preceding block, and the timestamp 311b. The consensus building unit 34 calculates the hash value of the block header by inputting an appropriate value into the nonce "Nonce" generated by the block header generation unit 33.

[0101] Of databases 3a, 3b, and 3c, the database that finds the answer first (here, database 3a) notifies databases 3b and 3c of this (approval process). Once approved, each database 3b and 3c adds the block notified to its own database to its existing block. This maintains the consistency of the transaction data held by databases 3a, 3b, and 3c. Next, the processing of the data processing unit 11 accompanying the transmission and reception of bill data will be described using a flowchart. FIG. 12 is a flowchart illustrating the processing of the data processing unit involved in sending and receiving bill data. [Step S1] The data processing unit 11 receives bill data, and then proceeds to step S2.

[0102] [Step S2] The data processing unit 11 updates the invoice data management table T1. The data processing unit 11 also refers to the grant token management table T3 and increases the grant amount at the time of sending of the accounting clerk who sent the invoice data by a predetermined amount. The data processing unit 11 then sets the amount obtained by subtracting the grant amount at the time of sending from the remaining amount of the record one level above in the remaining amount field. The grant amount at the time of sending is added to the total grant amount. The data processing unit 11 also increases the grant amount at the time of receiving of the accounting clerk who received the invoice data by a predetermined amount. The data processing unit 11 then sets the amount obtained by subtracting the grant amount at the time of sending from the remaining amount of the record one level above in the remaining amount field. The grant amount at the time of receiving is added to the total grant amount. This completes the processing in FIG. Next, the deposit process of this embodiment will be described. FIG. 13 is a flowchart illustrating the deposit process. [Step S11] When the data processing unit 11 receives the selection of the token redemption button 123, the process proceeds to step S12.

[0103] [Step S12] The data processing unit 11 issues a payment ID for the invoice data for which the selection has been accepted. This payment ID is a hashed number representing information about the transaction of the block, such as who sent the payment to whom, at what time, and for how much. The process then proceeds to step S13. The data processing unit 11 stores the issued payment ID in the payment ID column for the corresponding invoice data in the invoice data management table T1. For example, in the example shown in Figure 5, invoice IDs "001" and "002" each store a different payment ID. Therefore, these are invoice data recorded in different blocks. Furthermore, invoice IDs "003" and "004" each store the same payment ID. Therefore, these are invoice data recorded in the same block. [Step S13] The data processing unit 11 determines whether the above-mentioned approval process has been executed. If the approval process has been executed, the process proceeds to step S14.

[0104] [Step S14] The data processing unit 11 uses the payment ID to check whether the data stored in the block 311 has been approved. Notifications may be received from the databases 3a to 3c.

[0105] [Step S15] If the data stored in block 311 is approved for addition to an existing block, the data processing unit 11 changes the person in charge status and the other party status of the corresponding invoice in the invoice data management table T1 to statuses indicating that payment has been completed. Specifically, the person in charge status is changed from "Sent" to "Payed." The other party status is changed from "Unopened" or "Confirmed" to "Paid." The process shown in FIG. 13 makes it possible to automate the process of depositing the amount of the invoice stated in the invoice data. Next, the process of managing the amount of generated tokens will be described with reference to a flowchart. FIG. 14 is a flowchart illustrating a process for managing the amount of generated tokens. [Step S21] The data processing unit 11 refers to the column of the total generation amount in the token granting management table T3, and then proceeds to step S22.

[0106] [Step S22] The data processing unit 11 determines whether the total production amount is equal to or greater than a predetermined amount. This predetermined amount is, for example, an amount set in advance by an administrator of the data management device 1. If the total production amount is equal to or greater than the predetermined amount (Yes in step S22), the process proceeds to step S23. If the total production amount is less than the predetermined amount (No in step S22), the process of FIG. 14 ends.

[0107] [Step S23] The data processing unit 11 determines whether the BI token is listed. If the BI token is listed (Yes in step S23), the process proceeds to step S24. If the BI token is not listed (No in step S23), the process proceeds to step S25. [Step S24] The data processing unit 11 deposits the currency obtained by converting the BI tokens into the listed value into the wallet, and then proceeds to step S25.

[0108] [Step S25] The data processing unit 11 deposits the currency converted from the BI tokens at a pre-assigned rate into the wallet, and then proceeds to step S26.

[0109] [Step S26] The data processing unit 11 refers to the granted token management table T3 and updates the remaining amount and total granted amount columns. Specifically, the data processing unit 11 increases the remaining amount by the amount repurchased. Also, it decreases the total amount generated by the amount repurchased. Then, the process of FIG. 14 ends.

[0110] In addition, repurchased BI tokens may be made permanently unusable (introduction of a burn system). Repurchased BI tokens may also be made temporarily unusable (introduction of a lock-up system). This makes it possible to control the scarcity of BI tokens by reducing the amount of BI tokens in circulation on the market.

[0111] As described above, according to the invoice management system 10, the invoice management device 1 has an invoice data storage unit 12 that, when it receives invoice data sent from terminal devices 2a, 2b, and 2c to a specific recipient via a network, stores the received invoice data in association with the recipient's identification information and the identification information of the issuer of the invoice data, and a data processing unit 11 that, in response to the reception of the invoice data, generates unique BI tokens for the issuer and recipient that can be exchanged for currency in the future, and stores the generated BI tokens in association with the received invoice data in the granted token management table T3. Therefore, new profits can be generated in the accounting field.

[0112] As mentioned above, the use of a unique token creates an incentive for accounting staff who use the service, so that work that was previously inconspicuous and not subject to evaluation can now be made visible by monetizing it, and fair evaluation of labor can be expected.

[0113] Invoice payments can also be made with BI tokens. This reduces remittance fees incurred when going through a bank to nearly zero, and allows for one payment to be made for one piece of billing data (by breaking down hundreds of pieces of billing data into individual pieces when paying with virtual currency). In addition, remittances and deposits can be made immediately on the day the billing data is sent to the bill management device 1. Trust from a third party (a bank) is not required for settlement.

[0114] In addition, the BI token used for payment can have information that can identify the billing data, and when the recipient selects the deposit amount (token), the billing data corresponding to that BI token can be displayed on the screen, and the breakdown of the bill can also be seen. This makes it possible to automate the deposit process on the recipient side.

[0115] Furthermore, the more BI tokens a person holds, the more incentive they will have to increase the value of the BI tokens, which will lead to them introducing the services provided by the invoice management system 10 to their business partners and contributing to the growth of the service. An economic sphere will be born and expand, mainly in the BtoB world, centered around BI tokens.

[0116] If BI tokens can be converted into cash, for example, accounting departments will be transformed from cost centers into profit centers, which will promote the digitalization of invoices (DX) on a global scale.

[0117] Note that the generation of BI tokens is not limited to when invoice data is sent or received. For example, BI tokens may be generated when the recipient of the invoice data selects the "Confirm" button or when the issuer of the invoice data selects the "Payed" button. Furthermore, the invoice management device 1 may also have the functions of the databases 3a, 3b, and 3c.

[0118] Furthermore, instead of directly exchanging invoice data between terminal devices 2a, 2b, and 2c, all invoice data created on terminal devices 2a, 2b, and 2c and sent to the invoice recipient is stored in the invoice management device 1 and treated as shared data. Therefore, the accounting staff at the invoice recipient can obtain the original invoice by printing out the invoice data. In addition, since there is no need to perform electronic signature processing or timestamp processing, the hassle of converting paper invoices into PDFs for tax audits can be reduced.

[0119] External contact information entered by the accounting staff at both the sender and receiver of the invoice data is displayed on the information display section 121. Therefore, by using this external contact input mode, the accounting staff at both parties can communicate in a chat-like manner.

[0120] When invoice data is sent, the information is stored in the invoice data management table T1, and the status of subsequent exchanges is managed in this invoice data management table T1. This frees accounting staff from the task of manually inputting invoices into data sheets. The processing performed by the invoice management device 1 may be distributed among multiple devices.

[0121] In addition, in this embodiment, the invoice management device 1 is configured to have various storage units such as the invoice data storage unit 12, but this is not limited to this, and each storage unit may be cloud-based and located in a separate location from the data processing unit 11.

[0122] While the information processing device, information processing method, and program of the present invention have been described above based on the illustrated embodiments, the present invention is not limited to these, and the configuration of each part can be replaced with any configuration having the same function. Furthermore, any other components or steps may be added to the present invention. Furthermore, the present invention may be a combination of any two or more configurations (features) of the above-described embodiments.

[0123] The above processing functions can be realized by a computer. In this case, a program is provided that describes the processing details of the functions possessed by the invoice management device 1. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing details can be recorded on a computer-readable recording medium. Examples of computer-readable recording media include magnetic storage devices, optical disks, magneto-optical recording media, and semiconductor memories. Examples of magnetic storage devices include hard disk drives, flexible disks (FDs), and magnetic tapes. Examples of optical disks include DVDs, DVD-RAMs, and CD-ROM / RWs. Examples of magneto-optical recording media include MOs (Magneto-Optical disks).

[0124] When distributing a program, for example, the program is recorded on a portable recording medium such as a DVD or CD-ROM and sold. Alternatively, the program can be stored in a storage device of a server computer and transferred from the server computer to other computers via a network.

[0125] A computer that executes a program stores, for example, a program recorded on a portable recording medium or a program transferred from a server computer in its own storage device. The computer then reads the program from its own storage device and executes processing in accordance with the program. Note that the computer can also read the program directly from a portable recording medium and execute processing in accordance with that program. The computer can also execute processing in accordance with the program received each time a program is transferred from a server computer connected via a network.

[0126] At least a part of the above processing functions can also be realized by electronic circuits such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), or a PLD (Programmable Logic Device). [Explanation of symbols]

[0127] 1 Bill management device 2a, 2b, 2c Terminal equipment 3a, 3b, 3c databases 10. Invoice Management System 11 Data processing section 12 Bill data storage unit 13 External Contact Data Storage Unit 14 Attachment data storage unit 15 History data storage unit 16 Memo data storage section 17 Transaction data generation unit 20 Blockchain Network 31 Storage section Block 311 312 Database List 32 Transmitter / Receiver 33 Block header generator 34 Consensus Building Department T1 Invoice data management table

Claims

1. a storage unit that, when receiving document data relating to a business document sent from a terminal device to a specific recipient via a network, stores the received document data in association with identification information of the recipient and identification information of an issuer of the document data; a processing unit that, in response to receiving the document data, generates unique tokens for the issuer and recipient that can be exchanged for currency in the future, and stores the generated tokens in a storage unit in association with the received document data; wherein the processing unit converts a token generated in response to reception of the document data into currency in response to a request from the issuer, and pays the converted currency to the issuer.

2. A storage unit that, when receiving document data relating to a business document sent from a terminal device to a specific recipient via a network, stores the received document data in association with identification information of the recipient and identification information of an issuer of the document data; a processing unit that, in response to receiving the document data, generates unique tokens for the issuer and recipient that can be exchanged for currency in the future, and stores the generated tokens in a storage unit in association with the received document data; and The information processing device is characterized in that the processing unit converts a token generated in response to reception of the document data into currency in response to a request from the recipient, and pays the converted currency to the recipient.

3. The processing unit stores in a storage unit progress statuses relating to the processing of each of the issuer and recipient of the document data, which change depending on whether the document data is viewed or edited; The document data is stored in a block; the processing unit issues an ID corresponding to the document data in response to a request from the issuer or the recipient, the ID being capable of referencing the document data stored in a block; 3. An information processing device according to claim 1, further comprising: a processor for executing a process for processing the document data; a processor for executing a process for processing the document data; a processor for executing a process for processing the document data;

4. The tokens are publicly traded and valued in the market, The information processing device according to claim 1 or 2, wherein the processing unit refers to a current value of the token and pays the converted currency to the issuer or recipient.

5. An information processing device as described in claim 1 or 2, wherein the memory unit stores a wallet based on the identification information of the recipient or the issuer, and the exchanged currency is paid into the specified wallet.

6. An information processing device as described in claim 1 or 2, wherein the processing unit stores the amount currently being supplied to the market for each token in the memory unit, and when the supply amount of tokens reaches a certain level, the tokens are converted into currency and paid out.

7. A computer comprising: When document data relating to a business document transmitted from a terminal device to a specific recipient is received via a network, the received document data is stored in association with identification information of the recipient and identification information of an issuer of the document data, and In response to receiving the document data, generating unique tokens for the issuer and recipient that can be exchanged for currency in the future, and storing the generated tokens in association with the received document data; converting the tokens generated in response to the receipt of the document data into currency in response to a request from the issuer, and paying the converted currency to the issuer; and converting the tokens generated in response to the receipt of the document data into currency in response to a request from the recipient, and paying the converted currency to the recipient.

1. An information processing method comprising:

8. A computer comprising: When document data relating to a business document transmitted from a terminal device to a specific recipient is received via a network, the received document data is stored in association with identification information of the recipient and identification information of an issuer of the document data, and In response to receiving the document data, generating unique tokens for the issuer and recipient that can be exchanged for currency in the future, and storing the generated tokens in association with the received document data; converting the tokens generated in response to the receipt of the document data into currency in response to a request from the issuer, and paying the converted currency to the issuer; and converting the tokens generated in response to the receipt of the document data into currency in response to a request from the recipient, and paying the converted currency to the recipient. A program characterized by executing a process.

Images