Evidence attachment business support device, evidence attachment business support method, and evidence attachment business support program

Abstract

To provide an evidence attachment work support apparatus, an evidence attachment work support method, and an evidence attachment work support program that can support work of attaching evidences to journal entries.SOLUTION: According to an embodiment, (1) a journal entry detail table including a journal entry slip number is generated, (2) an evidence file corresponding to a file name of an evidence in a specified attachment information file is obtained from a specified storage folder, (3) an evidence association table including the journal entry slip number in the journal entry detail table and a Guid corresponding to the obtained evidence file is generated, and (4) an evidence information table including the Guid in the evidence association table and detailed information about the evidence in the specified attachment information file and an evidence image table including the Guid in the evidence association table and the obtained evidence file are generated.SELECTED DRAWING: Figure 48

Description

[Technical Field]

[0001] The present invention relates to a document attachment business support device, a document attachment business support method, and a document attachment business support program. [Background technology]

[0002] Patent document 1 discloses an information processing program, an information processing device, and an information processing method that can increase the versatility of calculating the number of days that have passed while making users aware that it is necessary to keep original supporting documents such as receipts (see paragraphs 0005 and 0008 of Patent document 1). [Prior art documents] [Patent documents]

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

[0004] In the field of managing such supporting documents, it is important to link and manage the journal entries and supporting documents (invoices, receipts, etc.) by attaching them to the journal entries. However, this attachment work has traditionally been done manually by accounting staff, which has been a huge time-consuming and costly process, and has also been prone to errors in attachment.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a document attachment work support device, a document attachment work support method, and a document attachment work support program that can support the work of attaching document attachments to journal entries. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the supporting device for attaching supporting documents according to the present invention is a supporting device for attaching supporting documents to journal entries when generating the journal entries, the supporting device comprising a control unit and a storage unit, wherein the storage unit stores an attachment information file including the file name of the supporting document and detailed information about the supporting document, and a storage folder in which the file of the supporting document is stored, and the control unit has a journal entry detail generating means for generating a journal entry detail table including the slip number of the journal entry, and a storage folder in which the file of the supporting document is stored. a voucher file acquisition means for acquiring a voucher file corresponding to the file name of the voucher; a voucher linking table generation means for generating a voucher linking table including the slip number of the journal entry in the journal entry detail table and voucher identification data corresponding to the voucher file acquired by the voucher file acquisition means; and a voucher table generation means for generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired by the voucher file acquisition means.

[0007] Furthermore, the supporting device for attaching supporting documents according to the present invention is a supporting device for attaching supporting documents to generated journal entries, and is equipped with a control unit and a storage unit, wherein the storage unit stores an attachment information file including the voucher number of the generated journal entry, the file name of the supporting document, detailed information on the supporting document, and an update category indicating how to update it, a storage folder in which the file of the supporting document is stored, and a journal entry detail table including the voucher number of the generated journal entry, and the control unit performs a specified The system is characterized by comprising: a document file acquisition means for acquiring, from a storage folder, a document file of the document corresponding to the file name of the document in a specified attached information file; a document linking table generation means for generating a document linking table including the slip number of the journal entry in the journal entry details table and document identification data corresponding to the document file acquired by the document file acquisition means; and a document table generation means for generating a document table including the document identification data in the document linking table, detailed information on the document in the specified attached information file, and the document file acquired by the document file acquisition means.

[0008] In addition, in the supporting device for attaching supporting documents according to the present invention, the control unit, when the update category is a category indicating that supporting documents attached to the generated journal entry will be edited or deleted, acquires supporting document identification data linked to the slip number of the generated journal entry in the attached information file from the supporting document linking table generated by the supporting document linking table generation means, and is further characterized by being provided with a supporting document editing means for editing or deleting information in the supporting document table generated by the supporting document table generation means that is linked to the acquired supporting document identification data.

[0009] Furthermore, in the method for supporting work to attach supporting documents according to the present invention, the method is executed by an information processing device having a control unit and a storage unit, and is capable of supporting work to attach supporting documents to journal entries when the journal entries are generated. The storage unit stores an attachment information file containing the file name of the supporting document and detailed information about the supporting document, and a storage folder in which the file of the supporting document is stored. The control unit executes a journal entry detail generation step of generating a journal entry detail table containing the slip number of the journal entry, and a step of reading the supporting document from the specified storage folder. The method is characterized by including a voucher file acquisition step of acquiring a voucher file corresponding to a file name; a voucher linking table generation step of generating a voucher linking table including the slip number of the journal entry in the journal entry details table and voucher identification data corresponding to the voucher file acquired in the voucher file acquisition step; and a voucher table generation step of generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquisition step.

[0010] Furthermore, in the method for supporting work to attach supporting documents according to the present invention, the method is executed by an information processing device having a control unit and a storage unit, capable of supporting work to attach supporting documents to generated journal entries, wherein the storage unit stores an attachment information file including the voucher number of the generated journal entry, the file name of the supporting document, detailed information on the supporting document, and an update category which is a category indicating how to update, a storage folder in which the file of the supporting document is stored, and a journal entry detail table including the voucher number of the generated journal entry, and when the update category in the attachment information file executed by the control unit is a category indicating that supporting documents are to be attached to the generated journal entry, a voucher file acquisition step of acquiring, from a specified storage folder, a voucher file corresponding to the file name of the voucher in the specified attached information file; a voucher linking table generation step of generating a voucher linking table including the slip number of the journal entry in the journal entry details table and voucher identification data corresponding to the voucher file acquired in the voucher file acquisition step; and a voucher table generation step of generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquisition step.

[0011] Furthermore, the supporting program for attaching supporting documents according to the present invention is a supporting program for attaching supporting documents to journal entries when generating the journal entries, the supporting program being executed by an information processing device having a control unit and a storage unit, the storage unit storing an attachment information file including the file name of the supporting document and detailed information about the supporting document, and a storage folder in which the file of the supporting document is stored, the supporting program being executed by the control unit includes a journal entry detail generating step for generating a journal entry detail table including the slip number of the journal entry, and a step for reading a specified attachment information file from a specified storage folder. a voucher file acquisition step of acquiring a voucher file corresponding to the file name of the voucher in the journal entry details table; a voucher linking table generation step of generating a voucher linking table including the voucher slip number of the journal entry in the journal entry details table and voucher identification data corresponding to the voucher file acquired in the voucher file acquisition step; and a voucher table generation step of generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquisition step.

[0012] Furthermore, the supporting program for attaching supporting documents according to the present invention is a supporting program for attaching supporting documents to generated journal entries, which is executed by an information processing device having a control unit and a storage unit, and which can support the work of attaching supporting documents to generated journal entries, wherein the storage unit stores an attachment information file including the voucher number of the generated journal entry, the file name of the supporting document, detailed information on the supporting document, and an update category which is a category indicating how to update, a storage folder in which the file of the supporting document is stored, and a journal entry detail table including the voucher number of the generated journal entry, and wherein the update category in the attachment information file, which is executed by the control unit, is a category indicating that supporting documents are to be attached to the generated journal entry. In some cases, the method is characterized by including a voucher file acquisition step of acquiring, from a specified storage folder, a voucher file corresponding to the file name of the voucher in the specified attached information file; a voucher linking table generation step of generating a voucher linking table including the slip number of the journal entry in the journal entry details table and voucher identification data corresponding to the voucher file acquired in the voucher file acquisition step; and a voucher table generation step of generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquisition step. [Effects of the Invention]

[0013] The present invention has the effect of supporting the task of attaching supporting documents to journal entries. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a voucher attachment business support device. [Figure 2] FIG. 2 is a diagram showing an example of a list of systems and databases related to this embodiment. [Figure 3] FIG. 3 is a diagram showing an example of a conventional business flow when journal entries are linked from other upstream business systems to an accounting ERP. [Figure 4]FIG. 4 is a diagram showing an example of a conventional business flow when migrating from another company's accounting ERP system. [Figure 5] FIG. 5 is a diagram showing an example of a business flow in this embodiment when journal entries are linked from other upstream business systems to the accounting ERP. [Figure 6] FIG. 6 shows a table summarizing the correspondence between a list of conventional tasks and the risks and disadvantages associated with the tasks. [Figure 7] FIG. 7 is a diagram showing a table summarizing the correspondence between a list of tasks and the effects of performing the tasks in this embodiment. [Figure 8] FIG. 8 is a diagram showing a table summarizing the explanations for each item in the attached information file. [Figure 9] FIG. 9 is a diagram showing an example of an attachment information file when the update category is 0. As shown in FIG. [Figure 10] FIG. 10 is a diagram showing an example of an attachment information file when the update category is 1. As shown in FIG. [Figure 11] FIG. 11 is a diagram showing an example of an attachment information file when the update category is 2. As shown in FIG. [Figure 12] FIG. 12 is a diagram showing an example of an attachment information file when the update category is 3. In FIG. [Figure 13] FIG. 13 is a diagram showing an example of an attachment information file when the update category is 4. In FIG. [Figure 14] FIG. 14 is a diagram showing an example of the external journal entry data reception screen. [Figure 15] FIG. 15 is a diagram showing an example of the file batch attachment screen. [Figure 16] FIG. 16 is a diagram showing an example of an attachment file. [Figure 17] FIG. 17 is a diagram showing an example of the external journal entry data reception screen. [Figure 18] FIG. 18 is a diagram showing an example of the file batch attachment screen. [Figure 19] FIG. 19 is a diagram showing an example of an attachment file. [Figure 20]FIG. 20 is a diagram showing the premise for attaching supporting documents after journal entry acceptance. [Figure 21] FIG. 21 is a diagram showing the premise for attaching supporting documents after journal entry acceptance. [Figure 22] FIG. 22 is a diagram showing the premise for attaching supporting documents after journal entry acceptance. [Figure 23] FIG. 23 is a diagram showing the premise for attaching supporting documents after journal entry acceptance. [Figure 24] FIG. 24 is a diagram showing the premise for attaching supporting documents after journal entry acceptance. [Figure 25] FIG. 25 is a diagram showing the premise for attaching supporting documents after journal entry acceptance. [Figure 26] FIG. 26 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 27] FIG. 27 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 28] FIG. 28 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 29] FIG. 29 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 30] FIG. 30 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 31] FIG. 31 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 32] FIG. 32 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 33] FIG. 33 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 34] FIG. 34 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 35] FIG. 35 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 36] FIG. 36 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 37] FIG. 37 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 38] FIG. 38 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 39] FIG. 39 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 40] FIG. 40 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 41] FIG. 41 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 42] FIG. 42 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 43] FIG. 43 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 44] FIG. 44 is a diagram for explaining a specific example of attaching supporting documents after journalization acceptance. [Figure 45] FIG. 45 shows the premise for attaching supporting documents simultaneously with journal entry acceptance. [Figure 46] FIG. 46 shows the premise for attaching supporting documents simultaneously with journal entry acceptance. [Figure 47] FIG. 47 is a diagram for explaining a specific example of attaching supporting documents simultaneously with journal entry acceptance. [Figure 48] FIG. 48 is a diagram for explaining a specific example of attaching supporting documents simultaneously with journal entry acceptance. [Figure 49] FIG. 49 is a diagram for explaining a specific example of attaching supporting documents simultaneously with journal entry acceptance. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of a document attachment business support device, a document attachment business support method, and a document attachment business support program according to the present invention will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[0016] [1. Overview] The supporting documents (invoices, receipts, etc.) attached to business systems often involve financial figures. For this reason, storing journal entries and supporting documents together in an accounting system (core ERP) can reduce the workload of accounting work. ERP stands for Enterprise Resource Planning. There are two possible patterns for original supporting documents: those that are managed in business systems, and those that are not managed in the system at all.

[0017] However, in the past, in order to link vouchers and supporting documents and store them in the system, accounting staff had to individually access the vouchers from the input screen and attach them. The more transactions a company has, the more costly and time-consuming this attachment process becomes. In other words, in the past, it was not possible to attach supporting documents to vouchers and manage them within the system.

[0018] Therefore, in this embodiment, it is possible to attach supporting documents to journal entries in bulk, for example, when integrating data from other upstream systems or migrating accounting systems. This successfully reduces the workload associated with the attachment process and the risk of human error. Furthermore, by reducing the workload associated with the attachment process, it is now possible to attach supporting documents from the accounting system, thereby successfully streamlining accounting confirmation work. Furthermore, with requirements such as the Electronic Bookkeeping Act and paperless systems becoming almost mandatory, it is now possible to collectively manage supporting document files among the large number of business document registrations that occur during monthly operations or system migration, thereby improving work efficiency. Significant improvements in work efficiency can be expected, particularly for large companies with a high volume of transactions that import large volumes of documents.

[0019] Furthermore, in this embodiment, not only can the supporting documents be attached in bulk at the same time as data import, but also operations such as adding, updating, and deleting supporting documents can be performed after data import.

[0020] For reference, a list of systems and databases related to this embodiment is shown in Fig. 2. The specific configuration and operation will be described below.

[0021] [2. Configuration] An example of the configuration of the voucher attachment work support device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the voucher attachment work support device 100.

[0022] The voucher attachment work support device 100 is a commercially available desktop personal computer. Note that the voucher attachment work support device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0023] The voucher attachment work support device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit of the voucher attachment work support device 100 is connected to each other so that they can communicate with each other via any communication path.

[0024] The communication interface unit 104 communicably connects the evidence attachment work support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the evidence attachment work support device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described below may be stored in the server 200, for example.

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to achieve a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0026] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0027] The storage unit 106 includes, for example, an attachment information file 106a, a storage folder 106b, a journal entry detail table 106c, a voucher linking table 106d, a voucher information table 106e, a voucher image table 106f, a file information table 106g, a file image table 106h, an accepted information work table 106i, and an existing information work table 106j. The voucher information table 106e and the voucher image table 106f can be collectively referred to as the voucher table. The file information table 106g and the file image table 106h can be collectively referred to as the file table.

[0028] The attached information file 106a is a key table in this application. The attached information file 106a is used to set detailed settings for attaching supporting documents to journal entries. As shown in Figures 8 and 25, the attached information file 106a includes fields such as the journal entry voucher number, the voucher type, the file name of the supporting document, the system classification (which defines how supporting documents and files are managed), the document type, the transaction date, the amount, the client name, the item name, the receipt date, the size, notes, the reason for delay, the update classification (which defines how the document is updated), and the original voucher number. The fields from the document type to the reason for delay can be considered detailed information about the supporting document. The format of the attached information file 106a, which includes an explanation of each field, is shown in Figure 8. The system classification and update classification are key fields in this application, so they will be explained below.

[0029] The three classifications of the system are "1: Electronic Transactions," "2: Scanner Storage," and "3: Other Attachments." Of the classifications of the system, "1: Electronic Transactions" and "2: Scanner Storage" fall under the category of "system files." "3: Other Attachments" is a classification for internal management.

[0030] The update categories include five categories: "0: Add a new file," "1: Delete an attached file," "2: Change the supporting information of an attached file (change only the document type and reason for delay)," "3: Replace an attached file with the same name," and "4: Replace an attached file with a different document." "0: Add a new file" is a category that indicates attaching a supporting document to the generated journal entry. In contrast, "1: Delete an attached file," "2: Change the supporting information of an attached file (change only the document type and reason for delay)," "3: Replace an attached file with the same name," and "4: Replace an attached file with a different document" are categories that indicate editing or deleting supporting documents attached to the generated journal entry.

[0031] An example of attachment information file 106a when the update category is "0: Add new file" is shown in Figure 9, an example of attachment information file 106a when the update category is "1: Delete attached file" is shown in Figure 10, an example of attachment information file 106a when the update category is "2: Change supporting information of attached file (only change document type to reason for delay)" is shown in Figure 11, an example of attachment information file 106a when the update category is "3: Replace attached file with same name" is shown in Figure 12, and an example of attachment information file 106a when the update category is "4: Transfer attached file to another voucher" is shown in Figure 13.

[0032] The storage folder 106b stores files of evidence. The format of the files is not particularly limited.

[0033] The journal entry details table 106c is a table for managing information on generated journal entries. As shown in Fig. 21, the journal entry details table 106c includes, for example, the journal entry voucher number, the receipt voucher number which is assigned when the journal entry is received from another system, the debit account title, the debit amount, and the like.

[0034] The voucher linking table 106d is a table for linking vouchers with generated journal entries. As shown in Fig. 22, the voucher linking table 106d includes, for example, the slip number of the journal entry, the system classification, the voucher identification data (Guid) for identifying the voucher, the system classification, and the like.

[0035] The evidence information table 106e is a table for managing detailed information about the evidence. As shown in Fig. 23 etc., the evidence information table 106e includes, for example, the evidence identification data (Guid), the file name of the evidence, the document type, the transaction date, the amount, the customer name, the product name, the receipt date, the size, the reason for delay, the system classification, a deletion flag, etc.

[0036] The voucher image table 106f is a table for managing the voucher file itself (binary data, etc.) As shown in Fig. 23 etc., the voucher image table 106f includes, for example, the voucher identification data (Guid) and the binary data (binary) of the voucher.

[0037] The file information table 106g is a table for managing detailed information about files. As shown in Fig. 24, the file information table 106g includes, for example, the document identification data (Guid), the journal entry slip number, the system classification, the memo, and the like.

[0038] The file image table 106h is a table for managing the file itself (binary data, etc.) As shown in Fig. 24, the file image table 106h includes, for example, the voucher identification data (Guid), the file name, and the binary data (binary) of the file.

[0039] Details of the contents of the incoming information work table 106i and the existing information work table 106j will be explained in [5. Specific example of processing] below.

[0040] The control unit 102 is a CPU or the like that comprehensively controls the document attachment business support device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0041] The control unit 102 functionally conceptually includes, for example, (1) a journal entry detail generating unit 102a as a journal entry detail generating means for generating a journal entry detail table including a journal entry voucher number; (2) a voucher file acquiring unit 102b as a voucher file acquiring means for acquiring, from a specified storage folder, a file of the voucher corresponding to the file name of the voucher in the specified attached information file (when the update classification in the attached information file is a classification indicating that a voucher is attached to the generated journal entry, the voucher file acquiring means acquires, from a specified storage folder, a file of the voucher corresponding to the file name of the voucher in the specified attached information file); and (3) a voucher linking table generating means for generating a voucher linking table including the journal entry voucher number in the journal entry detail table and voucher identification data corresponding to the file of the voucher acquired by the voucher file acquiring means. (4) a voucher linking table generating unit 102d as a voucher table generating means for generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the vouchers in the specified attached information file, and the voucher file acquired by the voucher file acquiring means; and (5) a voucher editing unit 102e as a voucher editing means for acquiring, when the update category indicates editing or deleting the vouchers attached to the generated journal entry, from the voucher linking table generated by the voucher linking table generating means, voucher identification data linked to the slip number of the generated journal entry in the attached information file, and further editing or deleting information in the voucher table generated by the voucher table generating means that is linked to the acquired voucher identification data.

[0042] Below, [2-1] explains the process for attaching supporting documents in bulk after accepting journal entries, [2-2] explains the process for editing the supporting documents that have been attached in bulk, and [2-3] explains the process for attaching supporting documents in bulk at the same time as accepting journal entries.

[0043] [2-1. When attaching supporting documents all at once after accepting journal entries] This section explains the process for attaching supporting documents in bulk after journal entry acceptance. This process is the process executed in (7) of [5-1] (When adding supporting documents) and (When adding files) in [5. Specific examples of processing] below.

[0044] If the update category in the attachment information file 106a (see Figure 25) is a category indicating that a voucher is to be attached to the generated journal entry (category "0: Add new file"), the voucher file acquisition unit 102b acquires the voucher file corresponding to the file name of the voucher in the specified attachment information file 106a (see Figure 25) from the specified storage folder 106b (see Figure 25).

[0045] In the example of (7) (when adding a document) in [5-1] (see Figure 36), the document file acquisition unit 102b acquires the document file "File A.pdf" corresponding to the document file name "File A.pdf" in the record on the first line (record with document number "Zaimu100") in the specified attachment file 106a (see Figure 25) from the specified storage folder 106b (see Figure 25) because the update category in the record on the first line (record with document number "Zaimu100") in the specified attachment file 106a (see Figure 25) is "0: Add new file".

[0046] The voucher linking table generation unit 102c generates a voucher linking table 106d that includes the voucher number of the journal entry in the journal entry details table 106c (see Figure 21) and the voucher identification data (Guid) corresponding to the voucher file acquired by the voucher file acquisition unit 102b.

[0047] In the example of (7) (when supporting evidence is added) in [5-1] (see Figure 36), the supporting evidence linking table generation unit 102c generates a supporting evidence linking table 106d that includes the voucher number "Zaimu100" of the generated journal entry in the journal entry details table 106c (see Figure 21) and the Guid "Guid1" corresponding to the supporting evidence file "File A.pdf" acquired by the supporting evidence file acquisition unit 102b.

[0048] The evidence table generation unit 102d generates a evidence table that includes the evidence identification data (Guid) in the evidence linking table 106d, detailed information regarding the evidence in the specified attached information file 106a, and the evidence file acquired by the evidence file acquisition unit 102b.

[0049] In the example of (7) (when adding evidence) in [5-1] (see Figure 36), the evidence table generation unit 102d generates a evidence information table 106e that includes the Guid "Guid1" in the evidence linking table 106d and the document type to the reason for delay in the first row record (record for voucher number "Zaimu100") in the attached information file 106a (see Figure 25), and a evidence image table 106f that includes the Guid "Guid1" in the evidence linking table 106d and the binary data of the evidence file "File A.pdf" acquired by the evidence file acquisition unit 102b.

[0050] [2-2. Editing all attached vouchers] This section explains the process for editing the vouchers that have been attached all at once. In terms of [5. Specific examples of processing] below, this process is the process that is executed in (7) of [5-1] (When deleting vouchers), (When changing voucher information), (When deleting files), (When correcting files), (When replacing attached files), and (When transferring to another document).

[0051] If the update category is a category indicating editing or deletion of the voucher attached to the generated journal entry (categories of "1: Delete attached file," "2: Change voucher information of attached file (change only document type to delay reason)," "3: Replace attached file with same-named file," or "4: Replace attached file with different voucher"), the voucher editing unit 102e obtains the voucher identification data (Guid) linked to the voucher number of the generated journal entry in the attachment information file 106a (see FIG. 25) from the voucher linking table 106d (see FIG. 22) generated by the voucher linking table generation unit 102c. The voucher editing unit 102e further edits or deletes information in the voucher table generated by the voucher table generation unit 102d that is linked to the obtained voucher identification data (Guid).

[0052] In the example of (7) (when deleting a supporting document) in [5-1] (see Figure 37), since the update category in the record on the second line (record with document number "Zaimu200") in the attachment information file 106a (see Figure 25) is "1: Delete attached file", the supporting document editing unit 102e obtains the Guid "Guid2" linked to the document number "Zaimu200" of the generated journal entry in the record on the second line (record with document number "Zaimu200") from the supporting document linking table 106d (see Figure 22) generated by the supporting document linking table generation unit 102c. The voucher editing unit 102e further updates the deletion flag, which is information linked to the acquired "Guid2", from "False" to "True" among the information in the voucher information table 106e (see Figure 37) and the voucher image table 106f (see Figure 37) generated by the voucher table generation unit 102d.

[0053] [2-3. When attaching supporting documents at the same time as accepting journal entries] This section explains the process for attaching supporting documents at the same time as journal entry acceptance. This process is executed in (7) of [5-2] (When adding supporting documents) and (When adding files) in [5. Specific examples of processing] below.

[0054] The journal entry detail generating unit 102a generates a journal entry detail table 106c including the slip number of the journal entry.

[0055] In the example of (7) of [5-2] (when vouchers are added) (see FIG. 48), the journal entry details generating unit 102a generates a journal entry details table 106c including the journal entry slip number "Zaimu001" and the like.

[0056] The evidence file acquisition unit 102b acquires the evidence file corresponding to the file name of the evidence in the specified attachment information file 106a (see FIG. 46) from the specified storage folder 106b (see FIG. 46).

[0057] In the example of (7) (when adding evidence) in [5-2] (see Figure 48), the evidence file acquisition unit 102b acquires the evidence file "File A.pdf" corresponding to the evidence file name "File A.pdf" in the first line record (record with voucher number "Uke001") in the specified attachment information file 106a (see Figure 46) from the specified storage folder 106b (see Figure 46).

[0058] The voucher linking table generation unit 102c generates a voucher linking table 106d that includes the voucher number of the journal entry in the journal entry details table 106c (see Figure 48) and the voucher identification data (Guid) corresponding to the voucher file acquired by the voucher file acquisition unit 102b.

[0059] In the example of (7) (when adding supporting evidence) in [5-2] (see Figure 48), the supporting evidence linking table generation unit 102c generates a supporting evidence linking table 106d that includes the voucher number "Zaimu001" of the journal entry in the journal entry details table 106c (see Figure 48) and the Guid "Guid001" corresponding to the supporting evidence file "File A.pdf" acquired by the supporting evidence file acquisition unit 102b.

[0060] The evidence table generation unit 102d generates a evidence table that includes the evidence identification data (Guid) in the evidence linking table 106d, detailed information about the evidence in the specified attached information file 106a, and the evidence file acquired by the evidence file acquisition unit 102b.

[0061] In the example of (7) (when adding evidence) in [5-2] (see Figure 48), the evidence table generation unit 102d generates a evidence information table 106e that includes the Guid "Guid001" in the evidence linking table 106d and the document type to the reason for delay in the first row record (record for voucher number "Uke001") in the attachment information file 106a (see Figure 46), and a evidence image table 106f that includes the Guid "Guid001" in the evidence linking table 106d and the binary data of the evidence file "File A.pdf" acquired by the evidence file acquisition unit 102b.

[0062] [3. Overview of Workflow] In this section, an outline of a conventional business flow and an outline of a business flow in this embodiment will be compared and explained.

[0063] [3-1. Overview of conventional business flow] An example of a conventional business flow when linking journal entries from other upstream business systems to an accounting ERP is shown in Figure 3. If the upstream business system and the accounting system (core ERP) have different mechanisms for storing supporting documents, as indicated by the phrase "Attachments required for journal entries" in Figure 3, accounting personnel had to manually attach supporting documents after accepting the journal entry file.

[0064] An example of the conventional workflow when migrating from another company's accounting ERP system is shown in Figure 4. When migrating accounting systems, as indicated by the phrase "Attachments required for journal entries" in Figure 4, accounting staff had to manually attach supporting documents to accepted journal entries along with the migration of journal entries.

[0065] A table summarizing the correspondence between the list of conventional tasks and the risks and disadvantages associated with those tasks is shown in Figure 6. As can be seen from Figure 6, simply put, in the past, attaching supporting documents was time-consuming.

[0066] [3-2. Overview of the Workflow in This Embodiment] Therefore, in this embodiment, by preparing in advance an attachment information file for bulk attachment and a file of all attached supporting documents in one folder, separate from the journal entry file, it is possible to easily attach supporting documents to journal entries in bulk, either at the same time as or after the journal entry is accepted.

[0067] An example of the workflow in this embodiment when journal entries are linked from other upstream business systems to the accounting ERP is shown in Figure 5. As indicated by the phrase "accept attachment files" in Figure 5, the presence of the bulk attachment function in this embodiment has succeeded in significantly reducing the effort and risk required to attach supporting documents to journal entries.

[0068] The batch attachment function according to this embodiment is also capable of flexible responses such as those shown in (1) to (3) below. (1) The timing of attachment can now be flexibly selected. In other words, it is now possible to accommodate both patterns of attachment at the same time as journal entry acceptance and attachment only after journal entry acceptance. (2) The system can now flexibly accommodate the system classifications of "electronic transactions," "scanner storage," and "other attachments." This allows mixed data to be accepted in bulk. The system classification of "other attachments" is a classification for attachments for internal management purposes. (3) It is now possible to consolidate multiple operations (addition, deletion, changing only supporting information, replacing files with the same name, and changing the attached document) into a single attachment operation.

[0069] FIG. 7 shows a table summarizing the correspondence between a list of tasks and the effects of performing the tasks in this embodiment.

[0070] [4. Screen and operation images] In this section, an image of the screen and operations in this embodiment will be described.

[0071] (1) When attaching supporting documents at the same time as receiving journal data The person in charge first launches the external journal entry data acceptance screen shown in Fig. 14 from the menu screen, and then clicks the "Bulk Attachment" button on that screen. This click launches the bulk file attachment screen shown in Fig. 15.

[0072] Next, the person in charge designates the attachment file 106a and the destination folder 106b on the launched file batch attachment screen shown in Fig. 15, and then clicks the "Execute" button at the bottom right of the screen. Note that the attachment file 106a is assumed to have been created in advance with the contents shown in Fig. 16. This click returns the user to the external journal entry data acceptance screen shown in Fig. 17.

[0073] Finally, the person in charge clicks the "Execute" button at the bottom right of the external journal data acceptance screen shown in Figure 17. By clicking this, the journal data is accepted and the supporting documents are attached at the same time, and the journal data is accepted in a state linked to the supporting documents.

[0074] (2) When attaching supporting documents in bulk after accepting journal data (when attaching supporting documents in bulk to journal data registered in Finance) First, as a preliminary step, the person in charge launches the external journal data reception screen from the menu screen and registers the journal data by clicking the "Execute" button on that screen. In other words, the person in charge registers the journal data first.

[0075] The person in charge then launches the file batch attachment screen shown in Fig. 18 from the menu screen, specifies the attachment information file 106a and the destination folder 106b on that screen, and clicks the "Execute" button at the bottom right of the screen. It is assumed that the attachment information file 106a has been generated in advance with the contents shown in Fig. 19. By clicking this button, the supporting documents are subsequently attached to the previously registered journal data.

[0076] [5. Specific examples of processing] This section explains a specific example of the process according to this embodiment. Below, [5-1] explains a specific example of attaching supporting documents all at once after accepting journal entries, and [5-2] explains a specific example of attaching supporting documents all at once at the same time as accepting journal entries.

[0077] [5-1. Example of attaching supporting documents in bulk after journal entry acceptance] This section explains a specific example of attaching supporting documents all at once after accepting the journal entry (attaching documents later after accepting the journal entry).

[0078] (1) Premise The information mainly used in this section [5-1] is the attached information file 106a and the storage folder 106b, as shown in Figure 20. In addition, as a premise for the explanation in this section [5-1], As shown in the journal entry detail table 106c in FIG. 21, it is assumed that nine vouchers, 100-900 (acceptance voucher numbers: Uke100-Uke900), have already been accepted. As shown in the voucher linking table 106d in Figure 22, vouchers (Guid2 and Guid3) corresponding to "regulatory files" are attached to slips 200 and 300, and files (Guid5, Guid6, Guid7, and Guid8) corresponding to "other files" are attached to slips 500, 600, 700, and 800. The information on the evidence (Guid2 and Guid3) corresponding to the "regulatory file" is stored in the evidence information table 106e and the evidence image table 106f shown in FIG. 23. Information on files (Guid5, Guid6, Guid7, and Guid8) that fall under "other files" is stored in the file information table 106g and file image table 106h shown in FIG. 24. The attachment file 106a and the storage folder 106b are set as shown in FIG. 25. It shall be.

[0079] (2) Generation of the receiving information work table 106i First, as shown in Fig. 26, the attachment information file 106a shown in Fig. 25 is read and the system classification in the attachment information file 106a is checked. As shown in Fig. 26, if the system classification is "1: electronic transaction" or "2: scanner storage", a check is made to see if the system requirement items have been entered, whereas if the system classification is "3: other attachments", a check is made to see if the system requirement items cannot be entered.

[0080] Next, as shown in Fig. 26, basic checks at the time of acceptance are performed, including an input item type digit check, a file existence check, and a check for the attachment of the same file. Through the above processing, the attachment information file 106a can be saved in the acceptance information work table 106i, as shown in Fig. 26. In other words, through the above processing, the acceptance information work table 106i can be generated based on the attachment information file 106a.

[0081] The generated accepted information worktable 106i is shown in Fig. 27. In addition to the items included in the attached information file 106a, the accepted information worktable 106i includes, as shown in Fig. 27, for example, the business slip number, the voucher identification data (Guid), the binary data, the voucher identification data for the voucher before replacement (pre-replacement Guid), etc.

[0082] The business voucher number is the existing voucher number of the existing voucher to be attached. The initial value of the business voucher number is NULL, and the value is updated as follows after the receipt information worktable 106i is created. That is, if the "registered voucher number" is specified as the voucher number in the receipt information worktable 106i, the value of the business voucher number in the receipt information worktable 106i will be the same as the "voucher number" in the attached information file 106a. On the other hand, if the "acceptance voucher number" is specified as the voucher number in the receipt information worktable 106i, the value of the business voucher number in the receipt information worktable 106i is identified using the receipt voucher number as a key. Note that the updating of the value of the business voucher number will be explained in detail in (3) below.

[0083] The Guid is used to identify the file within the system and is assigned a unique number within the system. If the update category in the receipt information work table 106i is "1: Delete attached file," "2: Change supporting information of attached file," or "4: Reassign attached file to another slip," the value of the Guid is updated as explained in (6) below.

[0084] The initial value of the pre-replacement Guid is NULL. If the update category in the acceptance information work table 106i is "3: Replace an attached file with the same name," the value of the pre-replacement Guid is updated as described in (6) below.

[0085] (3) Update the value of the transaction slip number in the receipt information work table 106i Next, the value of the business voucher number in the receipt information worktable 106i is updated as follows. That is, if the voucher type in the receipt information worktable 106i is "1: Financial document number" as shown in Figure 28, a record in the journal entry detail table 106c having the same voucher number (financial document number) as the voucher number (financial document number) in the receipt information worktable 106i is identified, and the voucher number (financial document number) in the identified record becomes the business voucher number in the receipt information worktable 106i. That is, in the receipt information worktable 106i, the value of the voucher number (financial document number) and the value of the business voucher number become the same. On the other hand, if the voucher type in the acceptance information worktable 106i is "0: acceptance voucher number", a record in the journal entry details table 106c having the same acceptance voucher number as the voucher number (acceptance voucher number) in the acceptance information worktable 106i is identified, and the voucher number (financial voucher number) in the identified record becomes the business voucher number in the acceptance information worktable 106i.

[0086] (4) Creation of existing information work table 106j Next, if the update category in the received information work table 106i is other than "0: Add new file", the existing information work table 106j is generated as follows.

[0087] As shown in Figure 29, if the update category in the receipt information worktable 106i updated in (3) is "1: Delete attached file," "2: Change voucher information of attached file," or "3: Replace attached file with same-named file," a record in the voucher linking table 106d that has "the business voucher number" in the receipt information worktable 106i as its voucher number is identified. On the other hand, as shown in Figure 29, if the update category in the receipt information worktable 106i updated in (3) is "4: Replace attached file with another voucher," a record in the voucher linking table 106d that has "the voucher number before change" in the receipt information worktable 106i as its voucher number is identified.

[0088] Then, as shown in Figure 29, the slip number, the voucher identification data (Guid), and the system classification of the record identified from the voucher linking table 106d are stored in the existing information work table 106j, thereby generating the existing information work table 106j. Note that the file name in the existing information work table 106j is updated by the following process (5).

[0089] (5) Update the file name in the existing information work table 106j Next, as shown in Fig. 30, a file name associated with the same voucher identification data (Guid) in the existing information work table 106j generated in (4) is identified from the voucher information table 106e and the file image table 106h. Then, as shown in Fig. 30, the identified file name is updated in the existing information work table 106j.

[0090] Next, as shown in FIG. 31, an existing attachment check, a duplicate attachment check, and a system classification change check are performed as attachment content correction checks.

[0091] (6) Update the Guid and pre-replacement Guid in the receiving information work table 106i Next, the Guid and pre-replacement Guid in the acceptance information work table 106i are updated as follows.

[0092] As shown in Figure 32, if the update category in the receipt information worktable 106i is "1: Delete attached file" or "2: Change supporting information of attached file," a record in the existing information worktable 106j that has the same business slip number and file name as those in the receipt information worktable 106i is identified. Then, as shown in Figure 32, the Guid of the identified record (= the Guid assigned when the file was attached) is updated as the Guid of the receipt information worktable 106i.

[0093] As shown in Figure 32, if the update category in the receipt information worktable 106i is "3: Replace an already attached file with the same name," a record in the existing information worktable 106j that has the same business slip number and file name as those in the receipt information worktable 106i is identified. Then, as shown in Figure 32, the Guid of the identified record (= the Guid assigned when the file was attached) is updated as the pre-replacement Guid in the receipt information worktable 106i.

[0094] As shown in Figure 32, if the update category in the receipt information worktable 106i is "4: Reattach attached file to another slip," a record in the existing information worktable 106j that has the same pre-change slip number and file name as those in the receipt information worktable 106i is identified. Then, as shown in Figure 32, the Guid of the identified record (= the Guid assigned when the file was attached) is updated as the Guid of the receipt information worktable 106i.

[0095] Next, as shown in FIG. 33, a check is made to see if the voucher can be modified by checking whether it exists, whether it has been approved, and whether it has been closed.

[0096] Through the above processing, the receiving information work table 106i shown in FIG. 32 is completed.

[0097] (7) Attaching or editing supporting documents Next, as shown in Figure 34, different DBs are updated depending on the system classification in the receiving information worktable 106i (see Figure 32) generated in (6). That is, as shown in Figure 34, if the system classification is "1: Electronic Transaction" or "2: Scanner Storage", the voucher storage DB is primarily updated, whereas if the system classification is "3: Other Attachments", the accounting DB is updated. Regarding how the DBs are updated, the processing branches depending on the value of the update classification in the receiving information worktable 106i (see Figure 32) generated in (6).

[0098] Below, in (7-1), we will explain the processing when the system classification is "1: Electronic Transaction" or "2: Scanner Storage", and in (7-2), we will explain the processing when the system classification is "3: Other Attachments".

[0099] (7-1) If the system classification is "1: Electronic Transaction" or "2: Scanner Storage" If the system classification in the receipt information worktable 106i generated in (6) is "1: Electronic transaction" or "2: Scanner storage," as shown in Figure 35, the journal entry details table 106c and the supporting document linking table 106d are stored in the accounting DB, while the supporting document information table 106e and the supporting document image table 106f are stored in the supporting document storage DB.

[0100] (When adding evidence) In the pattern identified by record No. 1 (a record in which the system classification is "1: electronic transaction" and the update classification is "0: new file added") in the receipt information work table 106i (see Figure 32) generated in (6), a new record is generated and added to the voucher linking table 106d, the voucher information table 106e, and the voucher image table 106f, as shown in Figure 36. The key point is that because this pattern is the addition of a voucher, a new record is also generated in the voucher linking table 106d.

[0101] (When deleting evidence) In the pattern identified by record No. 2 (a record whose system classification is "2: Saved by scanner" and whose update classification is "1: Delete attached files") in the receiving information work table 106i (see FIG. 32) generated in (6), as shown in FIG. 37, the record in the evidence linking table 106d is physically deleted, and the record in the evidence information table 106e is logically deleted, while the record in the evidence image table 106f is not updated. This pattern is a deletion of evidence, but because the system classification of "2: Saved by scanner" corresponds to a system file (= the system requires that data be retained rather than completely deleted), the record in the evidence information table 106e is not physically deleted, but is treated as a logical deletion. Note that this logical deletion is performed by updating the deletion flag from "False" to "True" in the evidence information table 106e, as shown by hatching in FIG. 37.

[0102] (When supporting information changes) In the pattern identified by record No. 3 in the receipt information worktable 106i (see Figure 32) generated in (6) (a record in which the system classification is "1: electronic transaction" and the update classification is "2: change the supporting information of the attached file (change only document type to reason for delay)"), the hatched parts (document type to reason for delay) of the record in the supporting information table 106e are updated, as shown in Figure 38, while the records in the supporting document linking table 106d and the supporting document image table 106f are not updated. The key point is that since this pattern is a change in supporting document information, only the supporting document information table 106e is updated.

[0103] (7-2) If the system classification is "3: Other attachments" If the system classification in the acceptance information worktable 106i generated in (6) is "3: Other attachments," all of the journal entry details table 106c, the supporting document linking table 106d, the file information table 106g, and the file image table 106h are stored in the accounting DB, as shown in Figure 39.

[0104] (When adding a file) In the pattern identified by record No. 4 (a record in which the system classification is "3: Other attachments" and the update classification is "0: New file added") in the receipt information work table 106i (see Figure 32) generated in (6), a new record is generated and added to the voucher linking table 106d, file information table 106g, and file image table 106h, as shown in Figure 40. Since this pattern is a file addition, the key point is that a new record is generated in the voucher linking table 106d.

[0105] (When deleting a file) In the pattern identified by record No. 5 (a record whose system classification is "3: Other attachments" and whose update classification is "1: Delete attached files") in the receipt information work table 106i (see Figure 32) generated in (6), the records in the evidence linkage table 106d, file information table 106g, and file image table 106h are physically deleted, as shown in Figure 41. This pattern is a file deletion, and the key point is that the record is physically deleted because the system classification of "3: Other attachments" does not apply to system files (= the data is only for internal management purposes, so there is no problem with completely deleting it).

[0106] (When modifying a file) In the pattern identified by record No. 6 in the receipt information work table 106i (see Figure 32) generated in (6) (a record in which the system classification is "3: Other attachments" and the update classification is "2: Change evidence information of attached file (change only document type - reason for delay)"), as shown in Figure 42, the records in the evidence linking table 106d and the file image table 106h are not updated, while only the notes of the records in the file information table 106g are updated. Since this pattern is a modification of file information, the key point is that only the file information table 106g is updated.

[0107] (When replacing an attached file) In the pattern identified by record No. 7 (a record whose system classification is "3: Other attachments" and whose update classification is "3: Replacing an already attached file with the same name") in the receipt information worktable 106i (see Figure 32) generated in (6), as shown in Figure 43, the records for the originally attached "File G.pdf" in the evidence linking table 106d, file information table 106g, and file image table 106h are deleted, while records for the newly attached "File G.pdf" are added to the evidence linking table 106d, file information table 106g, and file image table 106h. Because this pattern involves replacing an already attached file, the key point is that although the file name is the same for the file in the deleted record and the file in the added record, the file contents are different (see also Figure 25).

[0108] (When transferring to another document) In the pattern identified by record No. 8 in the receipt information worktable 106i (see Figure 32) generated in (6) (a record with the system classification "3: Other attachments" and the update classification "4: Reassign attached file to another voucher"), as shown in Figure 44, the records for the originally attached "Zaimu800" and "File H.pdf" in the evidence linking table 106d and file information table 106g are deleted, while records for "Zaimu900" and "File H.pdf" are added to the evidence linking table 106d and file information table 106g. Note that, as shown in Figure 44, the file image table 106h is not updated. Because this pattern involves a transfer to a different voucher, the key point is that a file with the same contents is transferred from the "Zaimu800" voucher to the "Zaimu900" voucher.

[0109] [5-2. Example of attaching supporting documents at the same time as accepting journal entries] This section explains a specific example of attaching supporting documents at the same time as accepting journal entries (attaching documents at the same time as accepting journal entries).

[0110] (1) Premise The information mainly used in this item [5-2] is the attachment information file 106a, the storage folder 106b, and the journal entry detail table 106c, as shown in Figure 45. Furthermore, as a premise for the explanation in this item [5-2], it is assumed that the attachment information file 106a and the storage folder 106b are set as shown in Figure 46.

[0111] (2) to (6) In this item [5-2], the processes from "(2) Generating the acceptance information work table 106i" to "(6) Updating the Guid and pre-replacement Guid in the acceptance information work table 106i" are the same as the processes described in [5-1].

[0112] However, when supporting documents are attached in bulk at the same time as journal entry acceptance as in this item [5-2], the business document number in the acceptance information worktable 106i is updated after the document number (financial document number) in the journal entry details table 106c is assigned. Specifically, when supporting documents are attached in bulk at the same time as journal entry acceptance as in this item [5-2], the acceptance document number is set in the "document number" column in the attachment information file 106a, and since the document type is "0: acceptance document number," a record in the journal entry details table 106c that has the same acceptance document number as the document number (acceptance document number) in the acceptance information worktable 106i is identified, and the document number (financial document number) in the identified record becomes the business document number in the acceptance information worktable 106i.

[0113] By the above processing, the receiving information work table 106i shown in FIG. 47 is completed.

[0114] (7) Attachment of supporting documents Next, different DBs are updated depending on the system classification in the generated acceptance information worktable 106i (see Figure 47). That is, if the system classification is "1: Electronic Transaction" or "2: Scanner Storage," the voucher storage DB is primarily updated, whereas if the system classification is "3: Other Attachments," the accounting DB is updated. Note that when attaching vouchers at the same time as journal acceptance as in this item [5-2], the only update classification available is "0: New File Added," so only processing branching based on the system classification is performed.

[0115] Below, in (7-1), we will explain the processing when the system classification is "1: Electronic Transaction" or "2: Scanner Storage", and in (7-2), we will explain the processing when the system classification is "3: Other Attachments".

[0116] (7-1) If the system classification is "1: Electronic Transaction" or "2: Scanner Storage" If the system classification in the generated acceptance information worktable 106i is "1: Electronic transaction" or "2: Scanner storage," as shown in Figure 35, the journal entry details table 106c and the supporting document linking table 106d are stored in the accounting DB, while the supporting document information table 106e and the supporting document image table 106f are stored in the supporting document storage DB.

[0117] (When adding evidence) In the pattern identified by record No. 1 (a record in which the system classification is "1: Electronic Transaction" and the update classification is "0: New File Added") in the generated acceptance information worktable 106i (see Figure 47), a new record is generated and added to the journal entry details table 106c, the supporting document linking table 106d, the supporting document information table 106e, and the supporting document image table 106f, as shown in Figure 48. Since this pattern is the addition of supporting documents, it is important to note that a new record is also generated in the supporting document linking table 106d. Also, when supporting documents are attached in bulk at the same time as journal entry acceptance, as in this item [5-2], the journal entry has not yet been generated at the time of the attachment operation, so a new record is generated in the journal entry details table 106c.

[0118] (7-2) If the system classification is "3: Other attachments" If the system classification in the generated acceptance information worktable 106i is "3: Other attachments," as shown in Figure 39, all of the journal entry details table 106c, voucher linking table 106d, file information table 106g, and file image table 106h are stored in the accounting DB. (When adding a file) In the pattern identified by record No. 2 in the generated acceptance information work table 106i (see Figure 47) (a record in which the system classification is "3: Other attachments" and the update classification is "0: New file added"), a new record is generated and added to the journal entry details table 106c, the supporting document linking table 106d, the file information table 106g, and the file image table 106h, as shown in Figure 49. Because this pattern involves the addition of a file, it is important to note that a new record is also generated in the supporting document linking table 106d. Also, when files are attached in bulk at the same time as journal entry acceptance, as in this item [5-2], the journal entry has not yet been generated at the time of the attachment operation, so a new record is generated in the journal entry details table 106c.

[0119] [6. Summary of this embodiment] As explained above, the supporting device 100 for attaching supporting documents to journal entries according to this embodiment can support the task of attaching supporting documents to journal entries. Specifically, as long as an accounting staff member or the like prepares the attachment information file 106a and the files of the supporting documents to be attached in advance, the accounting staff member who attaches supporting documents to journal entries can do so without any prior knowledge. This can, for example, reduce the time and cost required for the attachment task and prevent attachment errors.

[0120] Furthermore, the supporting device for attaching supporting documents 100 according to this embodiment can support the task of attaching supporting documents to generated journal entries, and can also support the task of attaching supporting documents to journal entries when generating the journal entries. In other words, the supporting device for attaching supporting documents 100 according to this embodiment can handle both the case where supporting documents are attached in bulk after journal entry acceptance as described in [5-1], and the case where supporting documents are attached in bulk at the same time as journal entry acceptance as described in [5-2].

[0121] [7. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to the achievement of SDGs Goals 8 and 9.

[0122] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0123] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0124] 8. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0125] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

[0126] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0127] Furthermore, with regard to the document attachment business support device 100, the components shown in the figure are functional concepts, and do not necessarily have to be physically configured as shown in the figure.

[0128] For example, all or any part of the processing functions of the documentary evidence attachment support device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the documentary evidence attachment support device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0129] In addition, this computer program may be stored in an application program server connected to the document attachment business support device 100 via any network, and all or part of it may be downloaded as needed.

[0130] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0131] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0132] The various databases stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and providing websites.

[0133] The supporting device for attaching evidence 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The supporting device for attaching evidence 100 may be realized by installing software (including programs or data) that causes the device to realize the processing described in this embodiment.

[0134] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0135] The present invention is useful in any industry or business that requires the management of supporting documents, but is particularly useful in large companies that require the management of large amounts of supporting documents. [Explanation of symbols]

[0136] 100 Voucher attachment business support device 102 Control section 102a Journal entry detail generation section 102b Evidence File Acquisition Department 102c Voucher linking table generation unit 102d Evidence table generation unit 102e Evidence Editorial Department 104 Communication interface unit 106 Storage section 106a Attachment file 106b Destination folder 106c Journal Entry Detail Table 106d Evidence linking table 106e Evidence Information Table 106f Evidence image table 106g File Information Table 106h File Image Table 106i Receipt Information Worktable 106j Existing Information Worktable 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A supporting device for attaching supporting documents, which is equipped with a control unit, and which can support the task of attaching supporting documents to journal entries created and managed in a certain information processing system when the journal entries are received in an information processing system other than the certain information processing system, The control unit When (A) a storage folder for a journal entry file that stores information on the multiple journal entries to be accepted, (B) the file name of the journal entry file, (C) a storage folder for an attachment information file that stores the slip number of each journal entry included in the journal entry file in association with the file name of the attached supporting document file and detailed information on the supporting document, (D) the file name of the attachment information file, and (E) a storage folder for the multiple supporting document files are specified, (1) accessing the storage destination folder of the specified journal file, and acquiring the journal file corresponding to the file name of the specified journal file; (2) accessing the storage destination folder of the specified attachment file, and acquiring the attachment file corresponding to the file name of the specified attachment file; (3) accessing the storage destination folder of the specified plurality of evidence files, and acquiring the plurality of evidence files based on the file names of the plurality of evidence files included in the acquired attachment information file; (4) assigning a new voucher number to each of the journal entries included in the acquired journal entry file, generating a plurality of journal entry detail records including the information of each of the journal entries included in the journal entry file and the assigned voucher number, and registering the generated plurality of journal entry detail records in a journal entry detail table; (5) based on the acquired attached information file, the acquired plurality of evidence files, and the generated plurality of journal entry detail records, generate a plurality of evidence linking records including each of the assigned slip numbers and evidence identification data corresponding to the evidence files, and register the generated plurality of evidence linking records in a evidence linking table; (6) generating a plurality of evidence records including the evidence identification data, the file name of the evidence file, the detailed information, and the evidence file based on the acquired attached information file, the acquired plurality of evidence files, and the generated plurality of evidence linking records, and registering the generated plurality of evidence records in a evidence table; A supporting device for attaching supporting documents, characterized by the above.

2. The information processing system corresponds to a business system, The other information processing system corresponds to an accounting system; 2. The supporting device for attaching supporting documents according to claim 1,

3. A supporting device for attaching supporting documents to generated journal entries, the supporting device comprising a control unit and a storage unit, The storage unit includes: An attached information file including the voucher number of the generated journal entry, the file name of the voucher, detailed information about the voucher, and an update category indicating how to update the voucher; A storage folder where the supporting documents are stored, a journal entry details table containing the voucher numbers of the generated journal entries; is stored, The control unit a voucher file acquisition means for acquiring, from a designated storage folder, a file of the voucher corresponding to the file name of the voucher in the designated attachment information file, when the update classification in the attachment information file indicates that the voucher is to be attached to the generated journal entry; a voucher linking table generating means for generating a voucher linking table including the slip number of the journal entry in the journal entry detail table and the voucher identification data corresponding to the voucher file acquired by the voucher file acquiring means; a voucher table generating means for generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired by the voucher file acquiring means; To have A supporting device for attaching supporting documents, characterized by the above.

4. The control unit When the update category indicates editing or deleting the voucher attached to the generated journal entry, a voucher identification data linked to the slip number of the generated journal entry in the attached information file is acquired from the voucher linking table generated by the voucher linking table generating means, and further, a voucher editing means for editing or deleting information in the voucher table generated by the voucher table generating means that is linked to the acquired voucher identification data. Further comprising:

4. The supporting device for supporting document attachment work according to claim 3.

5. A method for supporting a document attachment process executed by an information processing device having a control unit, which can support a process of attaching a document to a journal entry created and managed by a certain information processing system when the journal entry is received by another information processing system, the method comprising: The control unit When a destination folder for a journal entry file that stores information on the plurality of journal entries to be accepted, a destination folder for an attachment file that stores the file name of the journal entry file and the slip number of each journal entry included in the journal entry file in association with the file name of the attached supporting document file and detailed information on the supporting document, and the file name of the attached information file and the destination folder for the plurality of supporting document files are specified, (1) accessing the storage destination folder of the specified journal file, and acquiring the journal file corresponding to the file name of the specified journal file; (2) accessing the storage destination folder of the specified attachment file, and acquiring the attachment file corresponding to the file name of the specified attachment file; (3) accessing the storage destination folder of the specified plurality of evidence files, and acquiring the plurality of evidence files based on the file names of the plurality of evidence files included in the acquired attachment information file; (4) assigning a new voucher number to each of the journal entries included in the acquired journal entry file, generating a plurality of journal entry detail records including the information of each of the journal entries included in the journal entry file and the assigned voucher number, and registering the generated plurality of journal entry detail records in a journal entry detail table; (5) based on the acquired attached information file, the acquired plurality of evidence files, and the generated plurality of journal entry detail records, generate a plurality of evidence linking records including each of the assigned slip numbers and evidence identification data corresponding to the evidence files, and register the generated plurality of evidence linking records in a evidence linking table; (6) generating a plurality of evidence records including the evidence identification data, the file name of the evidence file, the detailed information, and the evidence file based on the acquired attached information file, the acquired plurality of evidence files, and the generated plurality of evidence linking records, and registering the generated plurality of evidence records in a evidence table; A supporting method for attaching supporting documents, characterized by the above.

6. A method for supporting a task of attaching supporting documents to generated journal entries, the method being executed by an information processing device having a control unit and a storage unit, The storage unit includes: An attached information file containing the voucher number of the generated journal entry, the file name of the voucher, detailed information about the voucher, and an update category that indicates how to update the voucher; A storage folder where the supporting documents are stored, a journal entry details table containing the voucher numbers of the generated journal entries; is stored, Executed by the control unit, a voucher file acquisition step of acquiring, from a specified storage folder, a file of the voucher corresponding to the file name of the voucher in the specified attachment information file, when the update classification in the attachment information file is a classification indicating that the voucher is attached to the generated journal entry; a voucher linking table generating step of generating a voucher linking table including the voucher number of the journal entry in the journal entry detail table and the voucher identification data corresponding to the voucher file acquired in the voucher file acquiring step; a voucher table generating step of generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquiring step; containing, A supporting method for attaching supporting documents, characterized by the above.

7. A supporting program for attaching supporting documents to be executed by an information processing device having a control unit, which can support the task of attaching supporting documents to journal entries created and managed in a certain information processing system when the journal entries are received in an information processing system other than the certain information processing system, The control unit When a destination folder for a journal entry file that stores information on the plurality of journal entries to be accepted, a destination folder for an attachment file that stores the file name of the journal entry file and the slip number of each journal entry included in the journal entry file in association with the file name of the attached supporting document file and detailed information on the supporting document, and the file name of the attached information file and the destination folder for the plurality of supporting document files are specified, (1) accessing the storage destination folder of the specified journal file, and acquiring the journal file corresponding to the file name of the specified journal file; (2) accessing the storage destination folder of the specified attachment file, and acquiring the attachment file corresponding to the file name of the specified attachment file; (3) accessing the storage destination folder of the specified plurality of evidence files, and acquiring the plurality of evidence files based on the file names of the plurality of evidence files included in the acquired attachment information file; (4) assigning a new voucher number to each of the journal entries included in the acquired journal entry file, generating a plurality of journal entry detail records including the information of each of the journal entries included in the journal entry file and the assigned voucher number, and registering the generated plurality of journal entry detail records in a journal entry detail table; (5) based on the acquired attached information file, the acquired plurality of evidence files, and the generated plurality of journal entry detail records, generate a plurality of evidence linking records including each of the assigned slip numbers and evidence identification data corresponding to the evidence files, and register the generated plurality of evidence linking records in a evidence linking table; (6) based on the acquired attached information file, the acquired plurality of evidence files, and the generated plurality of evidence linking records, generate a plurality of evidence records including the evidence identification data, the file name of the evidence file, the detailed information, and the evidence file, and register the generated plurality of evidence records in a evidence table; To execute the process, A supporting program for document attachment work that features:

8. A supporting program for attaching supporting documents to generated journal entries, the supporting program being executed by an information processing device having a control unit and a storage unit, The storage unit includes: An attached information file including the voucher number of the generated journal entry, the file name of the voucher, detailed information about the voucher, and an update category indicating how to update the voucher; A storage folder where the supporting documents are stored, a journal entry details table containing the voucher numbers of the generated journal entries; is stored, To cause the control unit to execute a voucher file acquisition step of acquiring, from a specified storage folder, a file of the voucher corresponding to the file name of the voucher in the specified attachment information file, when the update classification in the attachment information file is a classification indicating that the voucher is attached to the generated journal entry; a voucher linking table generating step of generating a voucher linking table including the voucher number of the journal entry in the journal entry detail table and the voucher identification data corresponding to the voucher file acquired in the voucher file acquiring step; a voucher table generating step of generating a voucher table including the voucher identification data in the voucher linking table, detailed information on the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquiring step; containing, A supporting program for document attachment work that features:

Images