JP7780469B2 - Evidence attachment business support device, evidence attachment business support method, and evidence attachment business support program - Google Patents

Description

The present invention relates to a document attachment support device, a document attachment support method, and a document attachment support program.

Patent Document 1 discloses an information processing program, information processing device, and information processing method that can increase the versatility of calculating the number of days elapsed while making users aware that it is necessary to keep original copies of receipts and other supporting documents (see paragraphs 0005 and 0008 of Patent Document 1).

Japanese Patent Application Laid-Open No. 2021-077143

In areas where such supporting documents are managed, it is important to link 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 attachment errors.

The present invention was made in consideration of the above-mentioned problems, and aims to provide a supporting device, a supporting method, and a supporting program for attaching supporting documents to journal entries.

In order to solve the above-mentioned problems and achieve the objectives, 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, and is equipped with a control unit and a memory unit. The memory 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 supporting document file is stored. The control unit controls a journal entry detail generation unit that generates a journal entry detail table containing the slip number of the journal entry, and a storage folder in which the file name of the supporting document is stored. The system is characterized by comprising: 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 about the voucher in the specified attached information file, and the voucher file acquired by the voucher file acquisition means.

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 memory unit. The memory unit stores an attachment information file containing the voucher number of the generated journal entry, the file name of the supporting document, detailed information about 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 containing the voucher number of the generated journal entry. When the update category in the attachment information file indicates that supporting documents are to be attached to the generated journal entry, the control unit The system is characterized by comprising: a voucher file acquisition means for acquiring, from the storage folder, a voucher file corresponding to the file name of the voucher in the specified attached information file; 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 about the voucher in the specified attached information file, and the voucher file acquired by the voucher file acquisition means.

In addition, in the supporting device for attaching supporting evidence according to the present invention, the control unit, when the update category indicates editing or deleting supporting evidence attached to the generated journal entry, acquires supporting evidence identification data linked to the slip number of the generated journal entry in the attached information file from the supporting evidence linking table generated by the supporting evidence linking table generation means, and further includes supporting evidence editing means for editing or deleting information linked to the acquired supporting evidence identification data from the information in the supporting evidence table generated by the supporting evidence table generation means.

In addition, the method for supporting the attachment of supporting documents according to the present invention is a method for supporting the attachment of supporting documents to journal entries when generating the journal entries, and is executed by an information processing device having a control unit and a memory unit. The memory 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 supporting document file 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 extracting the supporting document from the specified storage folder. The method includes a voucher file acquisition step for acquiring a voucher file corresponding to the file name; a voucher linking table generation step for generating a voucher linking table including the journal entry slip number in the journal entry detail table and voucher identification data corresponding to the voucher file acquired in the voucher file acquisition step; and a voucher table generation step for generating a voucher table including the voucher identification data in the voucher linking table, detailed information about the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquisition step.

Furthermore, the supporting method for attaching supporting documents according to the present invention is a supporting method for attaching supporting documents to generated journal entries, executed by an information processing device equipped with a control unit and a memory unit, which can support the task of attaching supporting documents to generated journal entries. The memory unit stores an attachment information file containing the voucher number of the generated journal entry, the file name of the supporting document, detailed information about the supporting document, and an update category indicating how to update it; a storage folder in which the supporting document file is stored; and a journal entry detail table containing the voucher number of the generated journal entry. When the update category in the attachment information file is a category indicating that supporting documents are to be attached to the generated journal entry, the control unit executes a The method includes 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 detail 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 about the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquisition step.

The supporting document attachment support program of the present invention is a supporting document attachment support program for execution by an information processing device having a control unit and a memory unit, which can support the task of attaching supporting documents to journal entries when generating the journal entries. The memory unit stores an attachment information file containing the file name of the supporting document, detailed information about the supporting document, and a storage folder in which the supporting document file is stored. The supporting document attachment support program is executed by the control unit and includes a journal entry detail generation step for generating a journal entry detail table containing the journal entry slip number, and a step for extracting the specified attachment information file from the specified storage folder. The method includes a voucher file acquisition step for acquiring a voucher file corresponding to the file name of the voucher in the specified attached information file; a voucher linking table generation step 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 in the voucher file acquisition step; and a voucher table generation step for generating a voucher table including the voucher identification data in the voucher linking table, detailed information about the voucher in the specified attached information file, and the voucher file acquired in the voucher file acquisition step.

Furthermore, the supporting document attachment program of the present invention is a supporting document attachment program for execution by an information processing device having a control unit and a memory unit, which can support the task of attaching supporting documents to generated journal entries. The memory unit stores an attachment information file containing the voucher number of the generated journal entry, the file name of the supporting document, detailed information about the supporting document, and an update category indicating how to update it; a storage folder in which the supporting document file is stored; and a journal entry detail table containing the voucher number of the generated journal entry. The program is executed by the control unit, and the update category in the attachment information file is a category indicating that supporting documents are to be attached to the generated journal entry. In some cases, the method includes a document file acquisition step for acquiring, from a specified storage folder, a document file corresponding to the document file name in the specified attached information file; a document linking table generation step for generating a document linking table including the journal entry slip number in the journal entry detail table and document identification data corresponding to the document file acquired in the document file acquisition step; and a document table generation step for generating a document table including the document identification data in the document linking table, detailed information about the document in the specified attached information file, and the document file acquired in the document file acquisition step.

The present invention has the effect of supporting the task of attaching supporting documents to journal entries.

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

Embodiments of a document attachment support device, a document attachment support method, and a document attachment support program according to the present invention are described in detail below with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[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.

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

In this embodiment, therefore, 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 attachment work and the risk of human error, for example. Furthermore, as the workload associated with attachment work is reduced, it is now possible to attach supporting documents on the accounting system side, resulting in the efficiency of 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 migrations, which is expected to improve 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.

In addition, in this embodiment, not only can supporting documents be attached simultaneously with data import, but it is also possible to add, update, and delete supporting documents after data import.

For reference, a list of systems and databases related to this embodiment is shown in Figure 2. Specific configurations and operations are explained below.

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.

The evidential document attachment work support device 100 is a commercially available desktop personal computer. Note that the evidential document attachment work support device 100 is not limited to stationary information processing devices such as desktop personal computers, but may also be portable information processing devices such as commercially available notebook personal computers, PDAs (Personal Digital Assistants), smartphones, and tablet personal computers.

The document attachment 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 document attachment support device 100 is connected to each other so that they can communicate with each other via any communication path.

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 the function of communicating data with other devices via a communication line. Here, the network 300 has the 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.

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 functions as a pointing device in conjunction with a mouse. Note that, below, 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. 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, or an optical disk.

The memory unit 106 includes, for example, an attachment information file 106a, a storage folder 106b, a journal entry details 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 worktable 106i, and an existing information worktable 106j. The voucher information table 106e and the voucher image table 106f can be collectively referred to as the voucher table. Furthermore, the file information table 106g and the file image table 106h can be collectively referred to as the file table.

Attachment file 106a is a key table in this application. Attachment file 106a is used to set detailed settings for attaching supporting documents to journal entries all at once. As shown in Figures 8 and 25, attachment file 106a includes fields such as the journal entry voucher number, voucher type, supporting document file name, system classification, which defines how supporting documents and files are managed, document type, transaction date, amount, client name, product name, receipt date, size, memo, reason for delay, update classification, which defines how the document is updated, and pre-change voucher number. The items from document type to reason for delay can be considered detailed information about the supporting documents. Figure 8 shows the format of attachment file 106a, which includes an explanation of each item. Since the system classification and update classification are key items in this application, they will be explained below.

These system classifications include three categories: "1: Electronic Transactions," "2: Scanner Storage," and "3: Other Attachments." Of these system classifications, "1: Electronic Transactions" and "2: Scanner Storage" fall under the category of "system files." "3: Other Attachments" is a classification for internal management.

The update categories include five: "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 voucher." "0: Add a new file" is a category that indicates attaching supporting information 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 voucher" are categories that indicate editing or deleting supporting information attached to the generated journal entry.

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

The storage folder 106b stores files of supporting evidence. There are no particular restrictions on the format of these files.

The journal entry details table 106c is a table for managing information about 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 the voucher number assigned when the journal entry is accepted from another system, the debit account title, the debit amount, and so on.

The evidence linking table 106d is a table for linking evidence with generated journal entries. As shown in FIG. 22, the evidence linking table 106d includes, for example, the journal entry's slip number, system classification, evidence identification data (Guid) for identifying the evidence, and the system classification.

The supporting document information table 106e is a table for managing detailed information about the supporting document. As shown in FIG. 23, the supporting document information table 106e includes, for example, the supporting document identification data (Guid), the file name of the supporting document, the document type, the transaction date, the amount, the customer name, the item name, the receipt date, the size, the reason for the delay, the system classification, and a deletion flag.

The evidence image table 106f is a table for managing the evidence file itself (binary data, etc.). As shown in FIG. 23, the evidence image table 106f includes, for example, the evidence identification data (Guid) and the evidence binary data (binary).

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, etc.

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 document identification data (Guid), the file name, and the file's binary data (binary).

Details of the contents of the incoming information worktable 106i and existing information worktable 106j are explained in [5. Specific examples of processing] below.

The control unit 102 is a CPU or the like that provides overall control of the document attachment support device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

The control unit 102 functionally comprises, for example, (1) a journal entry detail generation unit 102a as a journal entry detail generation means for generating a journal entry detail table including a journal entry voucher number; (2) a voucher file acquisition unit 102b as a voucher file acquisition means for acquiring, from a specified storage folder, a file of a voucher corresponding to the file name of the voucher in a specified attachment information file (if the update category in the attachment information file is a category indicating that a voucher is to be attached to the generated journal entry, the voucher file acquisition means for acquiring, from a specified storage folder, a file of a voucher corresponding to the file name of the voucher in the specified attachment information file); and (3) a voucher linking table generation 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 acquisition means. (4) a voucher linking table generating unit 102d as a voucher table generating means that generates 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 that, when the update category indicates editing or deletion of the vouchers attached to the generated journal entry, acquires from the voucher linking table generated by the voucher linking table generating means voucher identification data linked to the voucher number of the generated journal entry in the attached information file, and further edits or deletes information in the voucher table generated by the voucher table generating means that is linked to the acquired voucher identification data.

In the following, [2-1] explains the process for attaching supporting documents in bulk after journal entry acceptance, [2-2] explains the process for editing the attached supporting documents in bulk, and [2-3] explains the process for attaching supporting documents in bulk at the same time as journal entry acceptance.

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

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 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 Figure 25) from the specified storage folder 106b (see Figure 25).

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

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

In the example of (7) of [5-1] (when adding evidence) (see Figure 36), the evidence linking table generation unit 102c generates the evidence linking table 106d, which 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 evidence file "File A.pdf" acquired by the evidence file acquisition unit 102b.

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.

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 of the record (the 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.

[2-2. When editing all attached documents]
This section explains the process for editing all attached vouchers. In terms of [5. Specific examples of processing] below, this process is the process 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 voucher).

If the update category is one indicating editing or deletion of the evidence attached to the generated journal entry (categories of "1: Delete attached file," "2: Change evidence 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 evidence editing unit 102e obtains evidence identification data (Guid) linked to the voucher number of the generated journal entry in the attachment information file 106a (see Figure 25) from the evidence linking table 106d (see Figure 22) generated by the evidence linking table generation unit 102c. The evidence editing unit 102e further edits or deletes information in the evidence table generated by the evidence table generation unit 102d that is linked to the obtained evidence identification data (Guid).

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 voucher 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 voucher number "Zaimu200" of the generated journal entry in the record on the second line (record with voucher 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.

[2-3. When attaching supporting documents at the same time as journal entry acceptance]
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.

The journal entry details generation unit 102a generates a journal entry details table 106c that includes the journal entry voucher number.

In the example of (7) of [5-2] (when adding supporting evidence) (see Figure 48), the journal entry details generation unit 102a generates a journal entry details table 106c that includes the journal entry voucher number "Zaimu001", etc.

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 Figure 46) from the specified storage folder 106b (see Figure 46).

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 record on the first line (record with slip number "Uke001") in the specified attachment information file 106a (see Figure 46) from the specified storage folder 106b (see Figure 46).

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

In the example of (7) (when adding evidence) in [5-2] (see Figure 48), the evidence linking table generation unit 102c generates the evidence linking table 106d, which 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 evidence file "File A.pdf" acquired by the evidence file acquisition unit 102b.

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.

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 record (record with voucher number "Uke001") in the attached 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.

[3. Business flow overview]
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.

[3-1. Overview of conventional business flow]
An example of a conventional workflow for 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.

Figure 4 shows an example of the conventional workflow when migrating from another company's accounting ERP system. 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.

Figure 6 shows a table summarizing the correspondence between the list of conventional tasks and the risks and disadvantages associated with those tasks. As can be seen from Figure 6, simply put, in the past, attaching supporting documents was a time-consuming process.

[3-2. Overview of the business flow in this embodiment]
Therefore, in this embodiment, by preparing in advance an attachment information file for bulk attachment and all attached supporting documents files in one folder in addition to the journal entry file, it is possible to easily attach supporting documents to the journal entry in bulk at the same time as or after the journal entry is accepted.

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

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 be flexibly selected. In other words, it is now possible to accommodate both a pattern in which attachment is made at the same time as journal entry acceptance, and a pattern in which attachment is made only after journal entry acceptance.
(2) The system can now flexibly accommodate the classifications of "electronic transactions,""scannerstorage," and "other attachments." This allows mixed data to be accepted in bulk. The classification of "other attachments" is 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.

Figure 7 shows a table summarizing the correspondence between the list of tasks in this embodiment and the effects of performing those tasks.

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

(1) When accepting journal data and simultaneously attaching supporting documents, the person in charge first launches the external journal data acceptance screen shown in Fig. 14 from the menu screen, and then clicks the "attach all" button on that screen. This launches the file attachment screen shown in Fig. 15.

The person in charge then specifies the attachment file 106a and destination folder 106b on the launched file batch attachment screen shown in Figure 15, and 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 Figure 16. This click returns the user to the external journal entry data acceptance screen shown in Figure 17.

Finally, the person in charge clicks the "Execute" button in the bottom right of the external journal data acceptance screen shown in Figure 17. This click simultaneously accepts the journal data and attaches supporting documents, and the journal data is accepted linked to the supporting documents.

(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.

The person in charge then launches the file batch attachment screen shown in Figure 18 from the menu screen, specifies the attachment information file 106a and destination folder 106b on that screen, and clicks the "Execute" button in the bottom right of the screen. Note that the attachment information file 106a is assumed to have been created in advance with the contents shown in Figure 19. By clicking this button, the supporting documents are retroactively attached to the previously registered journal data.

5. Specific examples of processing
This section describes a specific example of processing according to this embodiment. Below, [5-1] describes a specific example of attaching supporting documents collectively after journal entry acceptance, and [5-2] describes a specific example of attaching supporting documents collectively at the same time as journal entry acceptance.

[5-1. Example of attaching supporting documents all at once after journal entry acceptance]
This section explains a specific example of attaching supporting documents all at once after accepting the journal entry (when the attachment operation is performed later after accepting the journal entry).

(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 FIG. 22, vouchers (Guid2 and Guid3) corresponding to the "regulatory file" are attached to slips 200 and 300, and files (Guid5, Guid6, Guid7, and Guid8) corresponding to the "other file" 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 information file 106a and the storage folder 106b are set as shown in FIG. 25.
It shall be.

(2) Generation of Acceptance 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. On the other hand, if the system classification is "3: Other Attachments", a check is made to see if the system requirement items cannot be entered.

Next, as shown in Figure 26, basic checks at the time of acceptance are performed: an input item type digit check, a file existence check, and a check that the same file is attached. Through the above processing, the attachment information file 106a can be saved to the acceptance information work table 106i, as shown in Figure 26. In other words, through the above processing, the acceptance information work table 106i can be generated based on the attachment information file 106a.

The generated accepted information worktable 106i is shown in Figure 27. In addition to the items included in the attached information file 106a, the accepted information worktable 106i also includes, as shown in Figure 27, for example, the business voucher number, the voucher identification data (Guid), the binary data, and the voucher identification data for the pre-replacement voucher (pre-replacement Guid).

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 "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 "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 acceptance voucher number as a key. Note that updating the value of the business voucher number is explained in detail in (3) below.

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 receiving information worktable 106i is "1: Delete attached file," "2: Change supporting information for attached file," or "4: Reassign attached file to another voucher," the value of the Guid is updated as explained in (6) below.

The initial value of the pre-replacement Guid is NULL. If the update category in the incoming information worktable 106i is "3: Replace an already attached file with the same name," the value of the pre-replacement Guid is updated as explained in (6) below.

(3) Updating the Value of the Business Voucher Number in the Receipt Information Worktable 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 Voucher Number" as shown in Figure 28, a record in the journal entry detail table 106c that has the same voucher number (financial voucher number) as the voucher number (financial voucher number) in the receipt information worktable 106i is identified, and the voucher number (financial voucher 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 voucher 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.

(4) Generating the Existing Information Work Table 106j Next, if the update category in the incoming information work table 106i is other than "0: Add new file", the existing information work table 106j is generated as follows.

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 for 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 "pre-change voucher number" in the receipt information worktable 106i as its voucher number is identified.

Then, as shown in FIG. 29, the voucher 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 worktable 106j, thereby generating the existing information worktable 106j. Note that the file name in the existing information worktable 106j is updated in the process (5) below.

(5) Updating the file name in the existing information work table 106j Next, as shown in Figure 30, from the evidence information table 106e and the file image table 106h, a file name linked to the same evidence identification data (Guid) in the existing information work table 106j generated in (4) is identified. Then, as shown in Figure 30, the identified file name is updated in the existing information work table 106j.

Next, as shown in Figure 31, attachment content correction checks are performed, including an existing attachment check, a duplicate attachment check, and a system classification change check.

(6) Updating the Guid and the Pre-Replacement Guid in the Acceptance Information Work Table 106i Next, the Guid and the pre-replacement Guid in the acceptance information work table 106i are updated as follows.

As shown in Figure 32, if the update category in the receiving information worktable 106i is "1: Delete attached file" or "2: Change supporting information for attached file," a record in the existing information worktable 106j that has the same business voucher number and file name as those in the receiving 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 receiving information worktable 106i.

As shown in Figure 32, if the update category in the receiving 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 receiving 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 receiving information worktable 106i.

As shown in Figure 32, if the update category in the receiving information worktable 106i is "4: Reassign attached file to another voucher," a record in the existing information worktable 106j that has the same pre-change voucher number and file name as those in the receiving 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 receiving information worktable 106i.

Next, as shown in Figure 33, a voucher existence check, final approval check, and voucher closing date check are performed to check whether the voucher can be modified.

The above processing completes the receiving information worktable 106i shown in Figure 32.

(7) Attaching or Editing Vouchers 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).

In the following, (7-1) explains the processing when the system classification is "1: Electronic Transaction" or "2: Scanner Storage," and in (7-2) explains the processing when the system classification is "3: Other Attachments."

(7-1) When the system classification is "1: Electronic transaction" or "2: Scanner storage" When the system classification in the receipt information work table 106i generated in (6) is "1: Electronic transaction" or "2: Scanner storage", as shown in Figure 35, the journal 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.

(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 an addition of a voucher, a new record is also generated in the voucher linking table 106d.

(When evidence is deleted)
In the pattern identified by record No. 2 (a record with the system classification "2: Saved by scanner" and the update classification "1: Delete attached files") in the receiving information worktable 106i (see Figure 32) generated in (6), as shown in Figure 37, the record in the evidence linking table 106d is physically deleted, the record in the evidence information table 106e is logically deleted, and the record in the evidence image table 106f is not updated. This pattern involves the deletion of evidence, but because the system classification "2: Saved by scanner" corresponds to an evidence file (i.e., data must be retained and not completely deleted according to the system), 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 the hatching in Figure 37.

(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 evidence information of the attached file (change only the document type to the reason for delay)"), as shown in Figure 38, the hatched parts (document type to reason for delay) of the record in the evidence information table 106e are updated, while the records in the evidence linking table 106d and the evidence image table 106f are not updated. The key point is that since this pattern is a change in evidence information, only the evidence information table 106e is updated.

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

(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.

(When deleting a file)
In the pattern identified by record No. 5 (a record in which the system classification is "3: Other attachments" and the update classification is "1: Delete attached files") in the acceptance information work table 106i (see Figure 32) generated in (6), the records in the voucher linking 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, so there is no problem with completely deleting it).

(When modifying a file)
In the pattern identified by record No. 6 in the receiving information worktable 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 (only document type - delay reason changed)"), 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.

(When replacing an attached file)
In the pattern identified by record No. 7 (a record with the system classification "3: Other attachments" and the update classification "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 voucher 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 voucher 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).

(When transferring to another document)
In the pattern identified by record No. 8 (a record with the system classification "3: Other attachments" and the update classification "4: Reassign attached file to another voucher") in the receipt information worktable 106i (see Figure 32) generated in (6), as shown in Figure 44, the records for the originally attached "Zaimu800" and "File H.pdf" in the voucher linking table 106d and file information table 106g are deleted, while records for "Zaimu900" and "File H.pdf" are added to the voucher 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.

[5-2. Example of attaching supporting documents at the same time as journal entry acceptance]
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).

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

(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].

However, when supporting documents are attached in bulk at the same time as journal entry acceptance, as in item [5-2], the voucher number (financial voucher number) in the journal entry details table 106c is assigned, and then the business voucher number in the acceptance information worktable 106i is updated. Specifically, when supporting documents are attached in bulk at the same time as journal entry acceptance, as in item [5-2], the acceptance voucher number is set in the "Voucher Number" column in the attachment information file 106a, and since the voucher type is "0: Acceptance Voucher Number," a record in the journal entry details table 106c that has 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.

The above processing completes the receiving information worktable 106i shown in Figure 47.

(7) Attachment of Vouchers 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 simultaneously with 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.

In the following, (7-1) explains the processing when the system classification is "1: Electronic Transaction" or "2: Scanner Storage," and in (7-2) explains the processing when the system classification is "3: Other Attachments."

(7-1) When the system classification is "1: Electronic transaction" or "2: Scanner storage" When the system classification in the generated acceptance information work table 106i is "1: Electronic transaction" or "2: Scanner storage", as shown in Figure 35, the journal 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.

(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 FIG. 47), a new record is generated and added to the journal entry details table 106c, the voucher linking table 106d, the voucher information table 106e, and the voucher image table 106f, as shown in FIG. 48. Because this pattern involves the addition of a voucher, the key point is that a new record is also generated in the voucher linking table 106d. Also, when vouchers are attached en bloc 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.

(7-2) When the system classification is "3: Other attachments" When the system classification in the generated acceptance information work table 106i is "3: Other attachments", as shown in Figure 39, 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.
(When adding a file)
In the pattern identified by record No. 2 in the generated acceptance information worktable 106i (see FIG. 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 voucher linking table 106d, the file information table 106g, and the file image table 106h, as shown in FIG. 49. Because this pattern involves the addition of a file, it is important to note that a new record is also generated in the voucher linking table 106d. Also, when files are attached in bulk at the same time as journal entry acceptance, as in 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.

[6. Summary of this embodiment]
As described above, the voucher attachment support device 100 according to this embodiment can support the task of attaching vouchers 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 vouchers to be attached in advance, the accounting staff member who attaches the vouchers 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.

The evidential document attachment work support device 100 according to this embodiment can also support the work of attaching evidential documents to generated journal entries, and can also support the work of attaching evidential documents to journal entries when generating the journal entries. In other words, the evidential document attachment work support device 100 according to this embodiment supports both the case where evidential documents are attached in bulk after journal entries are accepted, as described in [5-1], and the case where evidential documents are attached in bulk at the same time as journal entries are accepted, as described in [5-2].

[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.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

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.

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.

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

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.

For example, all or any part of the processing functions of the evidential document 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 evidential document attachment support device 100 as needed. In other words, a computer program that works in conjunction with the OS to issue commands to the CPU and perform 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 works in conjunction with the CPU to form the control unit.

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

In addition, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure 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 structures and procedures.

The various databases stored in the memory unit are storage devices 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 website provision.

The evidential document attachment work support device 100 may be configured as a known information processing device such as a personal computer or workstation, or may be configured as such an information processing device to which any peripheral device is connected. The evidential document attachment work support device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments may be implemented in any combination, or embodiments may be implemented selectively.

This invention is useful in all industries and sectors where managing supporting documents is required, but is particularly useful for large companies that need to manage large volumes of supporting documents.

100 Voucher attachment business support device 102 Control unit
102a Journal entry details generation unit
102b Evidence file acquisition unit
102c Voucher linking table generation unit
102d Evidence table generation unit
102e Evidence editing unit 104 Communication interface unit 106 Storage unit
106a Attachment file
106b Storage folder
106c Journal entry details 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 work table 108 input/output interface unit 112 input device 114 output device 200 server 300 network

Claims (8)

A supporting device for attaching supporting documents, the supporting device being equipped with a control unit , capable of supporting a 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. The certain 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, 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. The control unit
When the update category indicates editing or deleting of a voucher attached to the generated journal entry, the system further comprises a voucher editing means for acquiring, 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 linked to the acquired voucher identification data from the information in the voucher table generated by the voucher table generating means;
4. The supporting device for supporting document attachment work according to claim 3 . A method for supporting a voucher attachment process executed by an information processing device having a control unit, which can support a process of attaching a voucher to a journal entry created and managed in a certain information processing system when the journal entry is 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) 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. 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 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,
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. A supporting program for attaching supporting documents to be executed by an information processing device having a control unit, which can support a 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: A supporting program for attaching supporting documents to a generated journal entry, 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: