JP2023087855A - Business information data file management system, business information data file management method, and program - Google Patents

Abstract

To enable electronic data storage of transaction documents mainly by paperless FAX that satisfies electronic data storage requirements without using time stamps, and to improve convenience by various cooperation systems.SOLUTION: A business information data file management system 100 classifies and registers business information data files mainly into national tax-related transaction documents for paperless FAX and other business information. A transaction information data file or a normal business information data file is extracted in response to an output instruction input and is output in a predetermined format. When the transaction information data file is stored, a transaction date, a transaction destination name, an amount of money, a file name, a registration date, and a hash value of the file, which are required for visibility as required by law, are recorded as metadata, and when the transaction information data file is extracted in response to the output instruction input, the registration date is set to prohibit rewriting, and the metadata is output as a read-only file.SELECTED DRAWING: Figure 5

Description

The present invention relates to a business information data file management system, a business information data file management method, and a program.

Relevant laws and regulations stipulate the storage period and storage method for documents created or received in relation to transactions, such as bills and receipts, and business operators are required to comply with those rules. In recent years, electronic commerce has become commonplace, and the documents mentioned above are now exchanged between business operators as electronic data. Preservation requirements are specified. Electronically recorded transaction information is considered to be easier to falsify than data recorded on paper. Therefore, in order to prevent falsification of records, it is required to satisfy authenticity such as adding time stamps to electronic data. A time stamp is a combination of information indicating the time when electronic data was recorded and a hash value calculated from the recorded electronic data. A hash value is fixed value data that is irreversibly calculated from electronic data, and if electronic data is tampered with, the hash value always changes, so the fact of tampering remains. Using this property, the authenticity of electronic data is ensured by a combination of time information and a hash value obtained at that time. Timestamps can only be issued by time stamping business operators, and a business operator that wishes to receive a time stamp issuing service concludes a contract with one of the authorized business operators to receive the service. Therefore, cost reduction associated with the use of the time stamp service is one of the challenges for business operators.

In this respect, for example, Japanese Patent Laid-Open No. 2002-200001 proposes a technique for reducing the chances of using a time stamping service to reduce the cost related to time stamps. Patent Document 1 discloses a file management device for managing registered files, which selects a plurality of files from the registered files, combines the stored data of the selected files, and combines the combined stored data into one file. Store in a file. Then, a hash value of the file storing the combined stored data is calculated, a time stamp based on the hash value is obtained, and the time stamp is added to the file storing the combined stored data.

JP 2008-129857 A

However, as electronic transactions have become more and more widespread, electronic data storage related to electromagnetic records of transaction information in electronic transactions has become obligatory. Electronic storage requirements have been relaxed. In other words, the amended Electronic Book Storage Act, which will come into force on January 1, 2022 (Reiwa 4), requires time stamps to be added under certain conditions for storage in cloud services provided by third parties. Electronic data storage of transaction information is now permitted.

One of the objects of the present invention is to enable electronic data storage of transaction documents that satisfies requirements for authenticity in electronic data storage without using a time stamp service in storing input data from various linked systems. An object of the present invention is to provide a business information data file management system, a business information data file management method, and a program that can improve convenience.

According to one aspect of the present invention, business information data files input from the outside are classified into transaction information data files and normal business information data files according to the type of the business information data file and registered. a registration unit, a transaction information storage area for storing the transaction information data files classified by the business information data file registration unit, and a normal business information data file for storing the normal business information data files classified by the business information data file registration unit a business information data file storage unit having a business information storage area; and the transaction information data file from the transaction information storage area of the business information data file storage unit or from the normal business information storage area in response to an output instruction input. a business information data file providing unit for extracting the normal business information data file and outputting it in a predetermined format, wherein the business information data file registration unit stores the transaction information data file in the transaction information storage area; , the transaction date, counterparty name, amount, file name, and date on which the transaction information data file was stored, which are required for visibility as stipulated by law, recorded in the transaction information data file. The registration date shown and the hash value calculated for the transaction information data file are recorded as metadata of the transaction information data file, and the business information data file providing unit creates the transaction information data file in response to the output instruction input is set to prohibit rewriting of the registration date of the transaction information data file, and the metadata is output as a read-only format file when extracting the business information data file.

According to the present invention, in saving input data from various linked systems, etc., it is possible to save transaction documents as electronic data that satisfies the authenticity requirements for electronic data saving without using a time stamp service, thereby improving convenience. can be improved.

1 is a system configuration diagram illustrating the overall configuration of a business information processing system including a business information data file management system according to one embodiment of the present invention; FIG. 2 is an explanatory diagram of a business information processing function of the business information processing system of FIG. 1; FIG. 2 is a sequence diagram illustrating an outline of data processing in the business information processing system of FIG. 1; FIG. 1 is a block diagram illustrating the hardware configuration of a business information data file management system according to one embodiment of the present invention; FIG. 1 is a functional block diagram illustrating functions of a business information data file management system according to one embodiment of the present invention; FIG. 4 is a block diagram showing a configuration example of a file storage area; FIG. 6 is a flowchart illustrating business information registration processing in one embodiment of the present invention. It is a flow chart which illustrates business information offer processing in one embodiment of the present invention. 6 is a flow chart illustrating a configuration example of an input support screen for business information registration in one embodiment of the present invention. FIG. 10 is a diagram showing an example of a service selection screen in the business information data file management system; It is a figure which shows the example of a compressed file decompression screen in a business information data file management system. FIG. 10 is a diagram showing an example of a detailed information list screen in the business information data file management system;

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in line with its embodiments with reference to the accompanying drawings.
[Electronic storage of transaction information]
As mentioned above, the amended Electronic Book Preservation Act, which will come into effect on January 1, 2022, requires that transaction information electronically sent and received through e-mail, etc. must be stored as Transaction information that must be stored as electronic data includes transaction-related documents such as invoices, contracts, receipts, purchase orders, quotations, and receipts attached to emails, which are electronically stored in PDF format. In addition to data created as data, when facsimile electronic data of transaction documents received by facsimile is saved as electronic data as it is, or transaction documents generated as electronic data are converted into facsimile electronic data and sent to the other party Electronic data for transmission to a facsimile machine is also included. It is not permitted to print out the electronic data to be sent and received by facsimile and then save it on paper or save it by scanning. Therefore, even when conducting paper-based transactions using facsimiles with small and medium-sized enterprises that are difficult to fully support electronic transactions, business operators that transfer and electronically store electronic data sent and received by facsimile equipment , it is necessary to store electronic data that satisfies the storage requirements of the revised Electronic Book Storage Law. In this regard, business operators using various electronic facsimile data storage services that are currently being provided will be obliged to store electronic data in accordance with legal storage requirements.

As electronic storage requirements for transaction data, "ensuring authenticity" and "ensuring visibility" are stipulated. The requirement of "assurance of authenticity" seeks to guarantee that the stored electronic data is genuine and has not been subjected to illegal processing such as falsification. In this regard, the amended Electronic Book Storage Act, which came into force on January 1, 2022, prohibits the recording time from being changed in cloud services provided by third parties, In addition, transaction information is transferred and stored in a system that can confirm these facts and contents, or a system that cannot correct or delete recorded items. It has been made clear that this can be guaranteed. In addition, the requirement for "ensuring visibility" is that "the computer (personal computer, etc.), program, display, printer, and operation manual for these must be installed in the storage location, and the screens and documents will be displayed promptly in an orderly format and in a clear state. In addition to the administrative requirements such as "to be able to output to ," and "to provide an overview of the electronic computer processing system," there is also a technical requirement to "secure a search function" for the stored transaction data. is imposed. The requirements for this search function are the search requirements for books and transaction documents: "the ability to search by transaction date, account title, transaction amount, and other major record items according to the type of book or document"; It corresponds to "searchable by specifying a range of amounts" and "searchable by conditions combining two or more arbitrary record items", but the person responsible for storage requests the download of electromagnetic records based on the right to question and inspect by tax officials. If you are ready to meet the requirements, you only need to meet the first requirement. In that case, the items to be recorded are limited to the transaction date, transaction amount, and transaction partner.

The present invention has a configuration that can prevent falsification of transaction data in order to meet the requirements of "ensuring authenticity" without using time stamps. We propose a configuration that can similarly prevent falsification of transaction data even when the transaction data is taken over due to the termination of the service contract. In addition, on the premise that electronic data will be downloaded and submitted, the revised electronic book storage will be possible by satisfying the requirements of "securing visibility" in giving file names by transaction date, transaction amount, and business partner's record items. It enables electronic data storage that complies with the provisions of the law. In addition, it is possible to seamlessly handle transaction information by importing facsimile transmission/reception data and scanning data by a multifunction machine, sending/receiving e-mails, API linkage, etc., thereby enhancing user convenience. In this specification, general information to be processed by the business information data file management system 100 is referred to as "business information". Of the business information, the business information subject to the amended Act on the Preservation of Electronic Books shall be referred to as "transaction information", and other business information not subject to the amended Act on the Preservation of Electronic Books shall be referred to as "ordinary business information". do.

[Business information data file management system according to the embodiment of the present application]
FIG. 1 is an overall configuration diagram of a business information processing system including a business information processing system provided with a business information data file management system according to an embodiment of the present application and one or more client devices functioning as user terminals of the system. is exemplified. The business information processing system is communicably connected to the business information data file management system 100 (hereinafter abbreviated as "business information management system 100") through the network 500, as described above. and one or more client devices 200 . The business information management system 100 is also connected to a facsimile transmission/reception system 300 (hereinafter abbreviated as "FAX system 300") and an order reception business management system 400 (hereinafter abbreviated as "order reception system 400") via a network 500 so as to be mutually communicable. be able to. Network 500 can include various communication networks such as the Internet, WAN, LAN, and mobile communication networks. Business information management system 100, FAX system 300 . The order receiving system 400 is preferably configured as a cloud computing system comprising a plurality of nodes distributed on the network 500 .

The business information management system 100 has a function of storing transaction information data that satisfies the requirements for storing transaction information data stipulated in the revised Electronic Ledger Storage Law and downloading that satisfies authenticity. Functions of the business information management system 100 will be described later together with flowcharts illustrating data processing flows.

The client device 200 is a terminal device owned by a business operator who uses the functions provided by the business information management system 100 , and is an information processing device such as a personal computer having a communication function with the network 500 . Each user who owns the client device 200 can also use the FAX system 300 to send and receive data to and from the facsimile devices of other business operators, and receive order data from other business operators through the order receiving system 400 as electronic data. You can use the service to receive as Electronic transaction data transmitted and received by a business operator who owns the client device 200 is stored in the business information management system 100 in accordance with storage requirements to be satisfied for electronic data storage.

The FAX system 300 can be connected to a facsimile machine (not shown) via a communication line, and stores facsimile data received from the facsimile machine as a data file (for example, a PDF file) in a format readable by a normal computer. , attached to an e-mail, and transferred to a user who uses the FAX transmission/reception service provided by the FAX system 300. FIG. The FAX system 300 also has a function of converting data received from a user in the form of e-mail or the like into facsimile data and transmitting the data to a destination facsimile machine. The functions of the FAX system 300 allow users to conduct electronic data transactions with business operators who exchange information using facsimile machines.

The order receiving system 400 has a function of transferring order information sent by e-mail or facsimile from other businesses to users using the order receiving system 400 . The functions of the order receiving system 400 allow the user to reduce complicated paperwork related to order processing.
When the user of the business information management system 100 uses the services provided by the FAX system 300 and the order receiving system 400, the electronic data related to the business information exchanged by the FAX system 300 and the order receiving system 400 can be sent and received using the functions of the business information management system 100. can be stored and managed using

[Functions of Business Information Processing System 1]
FIG. 2 schematically shows main functions around the business information management system 100 shown in FIG. The business information management system 100 has a business information registration function 110 , a business information storage function 120 , a business information provision function 130 and a business information management function 140 . The business information data manually uploaded from the client device 200 or automatically captured by the e-mail linkage function, the facsimile transmission/reception service by the FAX system 300, and the various business information data related to the order reception business alternative service by the order reception system 400 are business information. It is stored by the business information storage function 120 by the registration function 110 . The stored business information data file is managed by the business information management function 140 . Specifically, for example, a data file that has not been downloaded or browsed for a predetermined period of time can be automatically archived by the business information management function 140 . The data files stored in the business information storage function 120 are downloaded with authenticity by the business information provision function 130 based on the batch download command from the client device 200 . Data related to normal business information is used for viewing/editing, attachment to e-mail, transmission to other devices through API linkage, etc., and facsimile transmission service using the FAX system 300 .

[Outline of data processing by the business information management system 100]
FIG. 3 is a sequence diagram showing data processing by the business information management system 100, the client device 200, the FAX system 300, and the order receiving system 400. As shown in FIG. In the example of FIG. 3, it is assumed that the user who owns the client device 200 uses the cooperation service between the FAX system 300 and the order receiving system 400 and the business information management system 100 .

<Transaction Information Registration Processing from FAX System 300>
In step S1, FAX system 300 receives facsimile data from another facsimile machine. At step S2, the FAX system 300 converts the received facsimile data into a computer readable file such as PDF format. In step S3, the FAX system 300 sends the received data to the business information management system 100 by e-mail with the converted data file attached or through API cooperation. In step S5, the business information management system 100 saves the received transaction information data file.

<Transaction Information Registration Processing from Order Receiving System 400>
In step S4, the order receiving system 400 receives transaction information as data from another business operator by e-mail or facsimile. In step S5, the order receiving system 400 transmits the received data to the business information management system 100 through e-mail or API cooperation. In step S5, the business information management system 100 registers and saves the received transaction information data file.

<Business Information Registration Processing from Client Device 200>
In step S10, the client device 200 transmits data files relating to transaction information and normal business information to the business information management system 100 by manual upload or transmission as an e-mail attachment file. In step S11, the business information management system 100 registers and saves a data file related to the received transaction information. As will be described later, the client device 200 is provided with a transaction information input support function from the business information management system 100 in this business information registration process.

<Business information reading process>
In step S20, the client device 200 requests reading of data files stored in the business information management system 100 through a web browser or API linkage. In step S21, the business information management system 100 receives the file read request, and in step S22 reads the data file related to the request. In step S23, the business information management system 100 transmits the read data file to the client device 200 which is the source of the request. If the read target is transaction information, the read command becomes a batch download command, and the requested data file and its corresponding metadata are sent to the requesting client device 200 .

As described above, in this embodiment, electronic data can be seamlessly exchanged between the client device 200, the FAX system 300, and the order receiving system 400 using the business information management system 100 as one hub, thereby improving user convenience. enhances sexuality.

[Configuration of Business Information Management System 100]
Next, a configuration example of the business information management system 100 will be described. FIG. 4 shows a hardware configuration example of the business information management system 100 of this embodiment. In FIG. 4, a business information management system 100 includes a processor 101 such as a CPU and GPU, a memory 102 such as ROM and RAM, an auxiliary storage unit 103 such as HDD and SSD, an input/output unit 104 such as a keyboard and monitor display, hardware A data interface unit (data IF unit) 105 for transmitting and receiving data between units, and a communication unit 106 for communicating with the network 500 are provided.

The business information management system 100 is preferably configured as a cloud computing system in which a plurality of computers as shown in FIG. 4 are communicably connected via a network 500 . Also, the client device 200, the FAX system 300, and the order receiving system 400 can each basically be configured as a computer having the hardware configuration illustrated in FIG.

Next, functions of the business information management system 100 according to this embodiment will be described with reference to FIG. FIG. 5 is a block diagram illustrating the functional configuration of the business information management system 100. As shown in FIG. The business information management system 100 includes a business information registration unit 110 (business information data file registration unit), a business information storage unit 120 (business information data file storage unit), a business information provision unit 130 (business information data file provision unit), and It has a functional block of a business information management unit 140 (business information data file management unit), each of which is the business information registration function 110, the business information storage function 120, the business information provision function 130, and the business information management function 140 in FIG. corresponds to These functional units are realized by executing corresponding programs by the processor 101 of FIG. can be configured as

The business information registration unit 110 includes a business information recording unit 111 , a hash value calculation unit 112 and a metadata generation unit 113 . The business information registration unit 110 stores facsimile data received from the client device 200, the FAX system 300, and the order receiving system 400, various types of attached data to e-mails, and the like in accordance with the authenticity and visibility requirements related to electronic data storage under the revised Electronic Ledger Storage Act. It has a function of storing in the business information storage unit 120 in a form that satisfies the requirements.
The business information recording unit 111 stores the data files to be stored in the business information storage unit 120, including national tax-related transaction information (transaction information data file) to be stored in accordance with the requirements of the revised Electronic Book Storage Law, and other business information (usually It has an input operation support function that separates and saves business information data files). Specifically, the business information recording unit 111 separates transaction information from normal business information by providing a necessary input support function in accordance with the requirements according to the type of data file to be stored. can be stored and operated The business information recording unit 111 is provided with an optical character recognition (OCR) function, and if the data file is an image file, the OCR function can be used to recognize character strings.

The hash value calculator 112 has a function of calculating a hash value for each business information data file to be registered. Calculation of the hash value can be performed using the SHA-2 algorithm or the like with an appropriate output length. The calculated hash value is used to ensure that the saved data file has not been tampered with after registration.

The metadata generation unit 113 generates record items that are keys for searching, specifically, transaction date, transaction amount, and transaction partner, for each electronic data file of transaction information such as national tax-related transaction documents to be registered. , and hash values calculated for the data file as a series of metadata. The generated metadata is automatically generated as appropriate spreadsheet (for example, MS Excel (Microsoft Corporation)) format data.

The business information storage unit 120 is a data storage area for storing business information data files registered by the business information registration unit 110, and is a logical storage area set using the auxiliary storage unit 103 of the business information management system 100. . The business information storage unit 120 has a transaction information storage area 121 (transaction information storage area) that stores electronic data classified as transaction information, and a normal business information storage area 122 that stores other business information data files. (Normal business information storage area). The business information registration unit 110 uses the input operation support function of the business information recording unit 111 to store the data file in one of the storage areas.

FIG. 6 shows a configuration example of the business information storage unit 120. As shown in FIG. FIG. 6 is a block diagram schematically showing a configuration example of a file storage area 600 set in the business information storage unit 120. As shown in FIG. A file storage area 600 is provided in the business information storage area 120 for each user of the business information management system 100, and is shown in FIG. 6 as an area allocated to company X, the user. The file storage area 600 is divided into a transaction information storage area 610 and a normal business information storage area 620 . The transaction information storage area 610 is further partitioned by X company's business partners, etc. In the example of FIG. 6, an A company storage area 611, a B company storage area 612, etc. are provided. For example, in the A company storage area 611 of the transaction information storage area 610, electronic data DT, such as bills and receipts, which should be stored according to the provisions of the Electronic Ledger Storage Law is stored. On the other hand, the normal work information storage area 620 is similarly divided according to X company's business partners and the like, and in the example of FIG. The normal work information storage area 620 stores a normal work information data file DN that is not subject to the Electronic Ledger Storage Law.

The business information providing unit 130 has a function of extracting and providing a requested business information data file from the business information storage unit 120 based on a request from the client device 200 . The business information providing unit 130 has a business information extracting unit 131 and a compression processing unit 132 . The business information extraction unit 131 extracts from the business information storage unit 120 the business information data file related to the browsing request or download request from the client device 200 . The compression processing unit 132 generates a compressed file of the extracted relevant file for the read request of the business information data file. The compressed file from the transaction information data file also contains a spreadsheet format file containing metadata for each data file to be downloaded.

The business information management unit 140 has a function of managing the storage status of business information data files stored in the business information storage unit 120 . The business information management unit 140 includes a business information organizing unit 141 . The business information organizing unit 141 notifies, for example, data files that have not been used for a certain period of time in the past, or data files that have passed a predetermined retention period, to the client devices 200 belonging to the owners of those data files, or automatically data processing such as moving to a predetermined area (for example, a "trash can" area) or archiving.

[Data processing by business information management system 100]
As already explained, the business information management system 100 registers and saves electronic data of transaction information such as national tax-related transaction documents and other electronic data while complying with the storage requirements for transaction information data stipulated in the revised Electronic Book Storage Law. , it has a function to make it available for easy download, viewing, etc., as needed. The specific data processing will be described below.

<Business information data file registration process>
FIG. 7 is a flow chart showing an example of the business information registration process of the business information management system 100. As shown in FIG. The business information registration process is executed by the business information registration unit 110 of the business information management system 100 . The business information registration processing flow of FIG. 7 is started when the business information management system 100 receives a business information data file from the client device 200 , the FAX system 300 , or the order receiving system 400 .

In step S<b>701 , the business information registration unit 110 receives a business information data file from the client device 200 , the FAX system 300 or the order receiving system 400 .

In step S702, the hash value calculator 112 calculates the hash value of the data file using a predetermined algorithm.
In step S703, the business information recording unit 111 stores the file name of the business information data file, the registration date indicating the date when the business information data file was stored, and the hash value calculated for the business information data file in a predetermined area. Record. The processing up to this step is commonly executed regardless of whether the received data file is transaction information or normal business information.

In step S704, the business information recording unit 111 classifies and registers the received business information data file into transaction information, specifically, transaction information such as national tax-related documents and other ordinary business information data files. Assist. For classification, the business information recording unit 111 forces a saving method according to the requirements of the business information to be saved to support an appropriate saving method. Specifically, as will be described later, the selection of the user's transaction information or normal business information in the client device 200, or the file attached to the received mail described in the header information of the received mail according to a predetermined rule. are classified based on the information indicating the type of document (document name, partner identification information such as business partner). FIG. 9 shows a configuration example 900 of an input support screen displayed when registering a data file related to transaction information. In the example of FIG. 9, the file name obtained from the file selected for uploading is automatically entered on the input support screen. Input fields for amount and document type are provided labeled "required". A user who intends to register a file from the client device 200 can perform an upload operation after inputting the required input items according to this screen. If the object to be uploaded is a file related to normal business information other than transaction information, the business information recording unit 111 implements the function of a file browser that enables file movement by intuitive operation on the screen as a user interface (UI). ).

In step S705, the business information recording unit 111 provides in parallel an input support function that can separate and store whether the received business information data file is a document related to transaction information or other business information. If the document is related to transaction information ("1: transaction" in step S705), in step S706, the metadata generation unit 113 generates the date of transaction, name of the customer, Amount, document type, file name of the transaction information data file, registration date indicating the date when the transaction information data file was stored, and hash value calculated for the transaction information data file as metadata of the transaction information data file Record as In step S<b>707 , the business information registration unit 110 supports storing the corresponding data file in the transaction information storage area 121 of the business information storage unit 120 .

On the other hand, in step S705, if the received business information data file is a data file of normal business information that is not a document related to transaction information ("2: normal" in step S705), in step S708, the business information registration unit 110 The corresponding data file is stored in the normal work information storage area 122 of the work information storage unit 120 .

In step S709, the business information registration unit 110 determines whether there is a data file waiting for reception processing, and if it determines that there is a data file waiting to be received (Yes in step S709), the process returns to step S701. If it is determined that there is no reception waiting data file (No in step S709), the business information registration unit 110 ends the business information registration process.

According to the business information registration process described above, the electronic data of national tax-related transaction documents, which are transaction information, can be distinguished from other normal electronic data, and "ensuring authenticity" and "visibility" required by the Electronic Book Storage Law. The relevant electronic data can be stored in a form that satisfies the storage requirements of "ensuring of data integrity".

<Business information data file provision processing>
FIG. 8 is a flow chart showing an example of the business information provision processing of the business information management system 100. As shown in FIG. The business information providing process is executed by the business information providing unit 130 of the business information management system 100 . The business information provision processing flow of FIG. 8 is started when the business information management system 100 receives an instruction to download a business information data file from the client device 200 .

In step S<b>801 , the business information providing unit 130 receives an instruction to download a business information data file from the client device 200 . FIG. 9 shows an example of a service selection screen output and displayed by the business information management system 100. As shown in FIG. When the user operating the client device 200 intends to use the data stored in the business information management system 100, the target data file is electronic data related to transaction information or electronic data related to other normal business information. By selecting either the transaction information management button 1010 or the normal business information management button 1020 shown in FIG. .

In step S802, the business information providing unit 130 determines which business information data file the download command received from the client device 200 is intended for. If it is determined that the target data file is transaction information ("1: transaction" in step S802), the business information extraction unit 131 extracts the data file from the transaction information storage area 121 of the business information storage unit 120 in step S803. read out.

In step S804, the business information extraction unit 131 generates metadata in a read-only format for the read data file. Specifically, the business information extraction unit 131 extracts records corresponding to the read file from the spreadsheet format data in which the metadata generated in the business information registration process is recorded, and extracts the record corresponding to the read file. Generate new spreadsheet files in read-only format.

In step S805, the compression processing unit 132 generates a compressed file storing the read business information data file and the spreadsheet file including the metadata generated in step S804.

In step S806, the business information providing unit 130 transmits the compressed file generated in step S805 to the client device 200, which is the source of the request, and ends the process. In addition, it is also possible to read and output the data file of the transaction information for browsing. In that case, in the read data file, the registration date data is set to be uneditable from the viewpoint of storage requirements.

On the other hand, if it is determined in step S802 that the request from the client device 200 is for a file of normal work information ("2: normal" in step S802), in step S807, the work information extraction unit 131 , the corresponding data file is read from the normal work information storage area 122 of the work information storage unit 120 . In step S808, the compression processing unit 132 compresses the read normal task information data file to generate a compressed file. In step S809, the business information providing unit 130 transmits the compressed file generated in step S808 to the client device 200, which is the source of the request, and ends the process. As for the normal business information, the read file may be transferred as it is without generating a compressed file.

FIG. 10 shows an example screen 1000 displayed when the compressed file generated by the business information providing unit 130 is decompressed by the client device 200 that has received it. In the screen example 1000 of FIG. 10, the names, update dates, types, and file sizes of five transaction information data files and one metadata file included in the compressed file are recorded. FIG. 11 shows an example of a detailed information list screen 1100 displayed by opening the SpreadEat file, which is the metadata file of FIG. The detailed information list screen example 1100 records the metadata of each of the five transaction information data files included in the compressed file that stores the downloaded data files. , date of processing, ID of the person in charge of input, type of document, and hash value are recorded. Further, in addition to the recorded items related to each data file, data related to the business operator providing the business information management service by the business information management system 100 is also included.

As described above, even if you download data files related to transaction information such as national tax-related transaction documents, the authenticity of the downloaded data files is the data files whose registration dates are prohibited from being edited, and the data files are set to read-only. Secured by metadata and a record of hash values computed for each data file.

The embodiments of the present invention have been described above. According to the business information management system 100 according to the present embodiment, input information from various cooperation systems can be stored according to electronic data storage requirements without using a time stamp service. Convenience can be improved while enabling electronic data storage of transaction documents that satisfies the requirements.

As described above, by storing transaction information data files related to electronic transaction information stipulated in the Electronic Book Storage Law in the business information data file management system 100 of the present embodiment, the storage requirements of the Electronic Book Storage Law can be satisfied. It is possible to store electronic data that satisfies

again. The business information registration unit 110 can be configured to receive transaction information data files converted from e-mail attachments and facsimile data by an external device.
In this manner, smooth data transfer can be realized between the business information management system 100 and an external facsimile transmission/reception system.

Further, the business information registration unit 110 and the business information provision unit 130 can be configured to be operable from other external devices such as the client device 200 via application program interfaces (APIs).
In this way, the functions of the business information management system 100 can be easily used from an external device such as the client device 200, improving convenience for the user.

Also, the business information providing unit 130 can be connected to an external device that converts the output transaction information data file into facsimile data.
In this way, the transaction information data file extracted from the business information storage unit 120 by the business information providing unit 130 can be transmitted by facsimile.

Further, the business information registration unit 110 can be configured to acquire counterpart identification information included in a transaction information data file to be registered and classify the transaction information data file into the transaction information data file. .
In this way, the received transaction information file data is automatically sorted using the read counterparty identification information, making it possible to save labor and improve the efficiency of the business information sorting process.

The business information management system 100 further includes a business information management unit 140, and the business information data file management unit monitors the usage status of each business information data file stored in the business information data file storage unit, It is possible to organize business information data files that have been determined to remain unused for a period of time.
In this way, the data storage area of the business information storage unit 120 can be effectively used by organizing data files that are not used or used infrequently by archiving or the like.

The series of processes described above can be executed by hardware or by software. In other words, the functional configuration of FIG. 5 is merely an example and is not particularly limited. That is, it is sufficient that the business information management system 100 has a function capable of executing the above-described series of processes as a whole, and what kind of functional blocks are used to realize this function is particularly limited to the example in FIG. not. Also, one functional block may be composed of hardware alone, or may be composed of software alone.

When a series of processes is to be executed by software, a program constituting the software is installed in a computer or the like from a network or a recording medium. The computer may be a computer built into dedicated hardware. The computer may also be a computer capable of executing various functions by installing various programs, such as a general-purpose personal computer.

In this specification, the steps of writing a program recorded on a recording medium are not only processes that are performed chronologically in that order, but also processes that are not necessarily chronologically processed, and that are performed in parallel or individually. It also includes the processing to be executed.

Although several embodiments of the present invention have been described above, these embodiments are merely examples and do not limit the technical scope of the present invention. The present invention can take various other embodiments, and it is also possible to combine the configurations of the above-described embodiment and modifications. Furthermore, various modifications such as omissions and substitutions can be made without departing from the gist of the present invention. These embodiments and modifications thereof are included in the scope and gist of the invention described in this specification and the like, and are included in the scope of the invention described in the claims and equivalents thereof.

REFERENCE SIGNS LIST 100 business information data file management system 110 business information registration unit 120 business information storage unit 121 transaction information storage area 122 normal business information storage area 130 business information provision unit 140 business information management unit

Claims (9)

a business information data file registration unit that classifies and registers business information data files input from the outside into transaction information data files and normal business information data files according to the type of the business information data files;
A transaction information storage area for storing the transaction information data files classified by the business information data file registration section, and a normal business information storage area for storing the normal business information data files classified by the business information data file registration section. a business information data file storage unit having
The transaction information data file is extracted from the transaction information storage area of the business information data file storage unit or the normal business information data file is extracted from the ordinary business information storage area in response to an output instruction input, and output in a predetermined format. a business information data file providing unit that
with
When storing the transaction information data file in the transaction information storage area, the business information data file registration unit stores the transaction year required for visibility as stipulated by law, recorded in the transaction information data file. The month and day, the name of the customer, the amount, the file name, the registration date indicating the date the transaction information data file was stored, and the hash value calculated for the transaction information data file as metadata of the transaction information data file record and
When extracting the transaction information data file in response to the input of the output instruction, the business information data file providing unit sets the registration date of the transaction information data file to prohibit rewriting, and stores the metadata in a read-only format. output as a file of
Business information data file management system. 2. The business information data file management system according to claim 1, wherein said transaction information data file is a data file relating to electronic transaction information stipulated in the Electronic Ledger Storage Law. 3. The business information data file registration unit according to claim 1 or 2, wherein the transaction information data file is configured to receive the transaction information data file as an email attachment and a computer-readable data file converted from facsimile data. Business information data file management system. 3. The business information data file management according to claim 1, wherein said business information data file registration unit and said business information data file providing unit are configured to be operable from another external device via an application program interface. system. 3. The business information data file management system according to claim 1, wherein said business information data file providing unit is connected to an external device that converts an output transaction information data file into facsimile data. The business information data file registration unit is configured to acquire partner identification information included in a business information data file to be registered and classify the business information data file into the transaction information data file. The business information data file management system according to claim 1 or 2. A business information data file management unit is further provided, and the business information data file management unit monitors the usage status of each business information data file stored in the business information data file storage unit, and is in a state of not being used for a predetermined period of time. 3. The business information data file management system according to claim 1 or 2, wherein the business information data file determined to be continuing is organized. The information processing device
Business information data files input from the outside are classified into transaction information data files and normal business information data files according to the type of the business information data file, and registered;
storing the classified transaction information data file in a transaction information storage area, storing the classified normal business information data file in a normal business information storage area;
extracting the transaction information data file from the transaction information storage area or the ordinary business information data file from the ordinary business information storage area in response to an output instruction input, and outputting the file in a predetermined format;
When storing the transaction information data file in the transaction information storage area, the date of transaction, the name of the customer, the amount of money, and the file name necessary for the visibility of the transaction information data file as stipulated by law, Record the registration date indicating the date when the transaction information data file was stored and the hash value calculated for the transaction information data file as metadata of the transaction information data file;
When extracting the transaction information data file in response to the input of the output instruction, setting the registration date of the transaction information data file to prohibit rewriting, and outputting the metadata as a read-only file;
Business information data file management method. information processing equipment,
A process of classifying and registering business information data files input from the outside into transaction information data files and normal business information data files according to the type of the business information data file;
a process of storing the classified transaction information data file in the transaction information storage area, and storing the classified ordinary business information data file in the ordinary business information storage area;
a process of extracting the transaction information data file from the transaction information storage area or the ordinary business information data file from the ordinary business information storage area in response to an output instruction input, and outputting the file in a predetermined format;
When storing the transaction information data file in the transaction information storage area, the date of transaction, the name of the customer, the amount of money, and the file name necessary for the visibility of the transaction information data file as stipulated by law, A process of recording a registration date indicating the date on which the transaction information data file was stored and a hash value calculated for the transaction information data file as metadata of the transaction information data file;
a process of setting the registration date of the transaction information data file to prohibit rewrite when extracting the transaction information data file in response to the input of the output instruction, and outputting the metadata as a file in a read-only format;
program to run.

Images