Additional attachment support device, additional attachment support method, and additional attachment support program

Abstract

The objective is to provide an additional attachment support device, an additional attachment support method, and an additional attachment support program that can support the process of adding additional supporting documents to a linked document after it has been generated by linking a linked source document with attached supporting documents from the linked source database to the linked destination database. [Solution] In this embodiment, (1) an approval classification is obtained from the journal entry data stored in the linked database, linked to the linked document number specified on the journal entry input screen; (2) if the obtained approval classification is "in approval", electronic document linking data including the linked document number and document identification data for the additionally attached document is generated and stored in the linked database; and (3) if the obtained approval classification is "approved", an error message is displayed on the journal entry input screen indicating that additional documents cannot be attached to the linked document identified by the specified linked document number.

Description

Technical Field

[0001] The present invention relates to an additional attachment work support device, an additional attachment work support method, and an additional attachment work support program.

Background Art

[0002] Patent Document 1 discloses an output support system including a distributed computing system configured by bundling some resources in a plurality of monitored systems, a history acquisition driver provided for each housing unit of each monitored system, and an output driver provided in the distributed computing system and a format storage unit that records the output format of forms (see Claim 1 of Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Here, conventionally, including the above Patent Document 1, after linking a linked source slip with an attached certificate (for example, a delivery note) from a linked source database (for example, a sales database) to a linked destination database (for example, an accounting database) to generate a linked destination slip, it was not possible to additionally attach another certificate (for example, a delivery note, a petition, etc.) to the linked destination slip.

[0005] For this reason, the accounting staff had to newly create a debit and credit slip and reattach the other certificate (for example, a delivery note, a petition, etc.), which caused problems such as cost and labor, and the work became complicated.

[0006] The present invention has been made in view of the above-mentioned problems, and aims to provide an additional attachment support device, an additional attachment support method, and an additional attachment support program that can support the process of adding another document to a linked document after linking a linked source document with attached supporting documents from a linked source database to a linked destination database to generate a linked destination document. [Means for solving the problem]

[0007] To solve the above-mentioned problems and achieve the objective, the present invention provides an additional attachment business support device that supports the business of adding another document to a linked document after linking a linked source document with attached documents from a linked source database to a linked destination database to generate a linked destination document, wherein the storage device includes a linked source database which stores document number linking data including a linked source document number which is the document number of the linked source document and a linked document number which is the document number of the linked document, and a linked destination database which stores document number linking data including a linked destination document number which is the document number of the linked destination document and the linked document number, and journal entry data including the linked destination document number and approval classification, and the control unit controls the linked destination database The system is characterized by comprising: approval classification acquisition means for acquiring an approval classification associated with a linked document number specified on a screen for modifying the linked document from the journal entry data stored in the system; additional attachment storage means for generating electronic document linking data including the linked document number and document identification data for the additionally attached document, and storing it in the linked database, if the approval classification acquired by the approval classification acquisition means is a classification indicating that the final approval of the linked document has not yet been completed; and error message display means for displaying an error message on the screen indicating that additional attachments to the linked document identified by the specified linked document number are not possible, if the approval classification acquired by the approval classification acquisition means is a classification indicating that the final approval of the linked document has already been completed.

[0008] Furthermore, the additional attachment support device according to the present invention can support the task of verifying the documents attached to the source document linked to the linked document, and the storage unit stores a source database in which electronic document linking data including document identification data for identifying the document number and the document and a classification of the method for storing the data, document number linking data including the source document number which is the document number of the source document and the linked document number which is the document number of the linked document, and the linked document number, and a linked destination database in which document number linking data including the linked destination document number which is the document number of the linked document and the linked document number, and a document storage database in which document data including document identification data, the file name of the document and the binary data of the document, and the control unit uses the linked document number to verify the source document number and the linked destination document based on the document number linking data stored in the source database and the document number linking data stored in the linked destination database The system further comprises: temporary table generation means for generating a temporary table for identifying a voucher number, which is a table containing details that are associated with and stored with numbers; confirmation candidate display means for displaying the details included in the temporary table for identifying voucher numbers as confirmation candidates; when a specific detail is selected from the details displayed by the confirmation candidate display means, the system obtains the source voucher number corresponding to the linked voucher number held by the selected specific detail from the temporary table for identifying voucher numbers, and further obtains the voucher identification data, etc. acquisition means for obtaining voucher identification data and classification associated with the obtained source voucher number from the electronic voucher linking data stored in the source database; and if the classification obtained by the voucher identification data, etc. acquisition means is a classification that means storing a file as a voucher, the system further obtains the file name and binary data of the voucher associated with the voucher identification data obtained by the voucher identification data, etc. acquisition means from the voucher data stored in the voucher storage database.

[0009] Furthermore, the additional attachment support device according to the present invention is characterized in that the control unit further comprises a document display means that displays the file name and binary data of the document acquired by the document acquisition means when a specific item is selected from the items displayed by the confirmation candidate display means.

[0010] Furthermore, the additional attachment support device according to the present invention is characterized in that the control unit further comprises: a file name list display means that displays a list of file names of documents acquired by the document acquisition means when a specific item is selected from the items displayed by the confirmation candidate display means; and a document display means that displays the file name and binary data of a document selected from the file names of documents displayed by the file name list display means, among the file names and binary data of documents acquired by the document acquisition means.

[0011] Furthermore, the method for supporting additional attachment operations according to the present invention is an information processing device that supports the operation of adding another document to a linked document after linking a linked source document with attached documents from a linked source database to a linked destination database to generate a linked destination document, wherein the storage device is equipped with a control unit and a storage unit, and the storage unit stores a linked source database which stores document number linking data including a linked source document number which is the document number of the linked source document and a linked document number which is the document number of the linked document, and a linked destination database which stores document number linking data including a linked destination document number which is the document number of the linked destination document and the linked document number, and journal entry data including the linked destination document number and approval classification, and the control unit executes the operation of linking a linked source database which stores documents in the linked destination database The system is characterized by including: an approval classification acquisition step that acquires an approval classification associated with a linked document number specified on a screen for modifying the linked document from the aforementioned journal entry data; an additional attachment storage step that, if the approval classification acquired in the approval classification acquisition step is a classification indicating that the linked document has not yet been finalized, generates electronic document linking data including the linked document number and document identification data for the additionally attached document and stores it in the linked database; and an error message display step that, if the approval classification acquired in the approval classification acquisition step is a classification indicating that the linked document has already been finalized, displays an error message on the screen indicating that additional attachments for the linked document identified by the specified linked document number cannot be made.

[0012] Furthermore, the method for supporting additional attachment operations according to the present invention can support the operation of verifying the documents attached to the source document linked to the linked document, and the storage unit stores a source database in which electronic document linking data including document identification data for identifying the document number and the document and a classification of the method for storing the data, document number linking data including the source document number which is the document number of the source document and the linked document number which is the document number of the linked document, and the linked document number, and a linked destination database in which document number linking data including the linked destination document number which is the document number of the linked document and the linked document number, and a document storage database in which document data including document identification data, the file name of the document and the binary data of the document, and the control unit executes the operation to match the source document number and the linked destination document number using the linked document number based on the document number linking data stored in the source database and the document number linking data stored in the linked destination database, and The method further includes: a temporary table generation step of generating a temporary table for identifying a voucher number, which is a table containing details to be held in correspondence; a confirmation candidate display step of displaying the details included in the temporary table for identifying a voucher number as confirmation candidates; a document identification data acquisition step of obtaining, when a specific detail is selected from the details displayed in the confirmation candidate display step, the source voucher number corresponding to the linked voucher number held by the selected specific detail is obtained from the temporary table for identifying a voucher, and further obtaining document identification data and classification associated with the obtained source voucher number from the electronic document linking data stored in the source database; and, if the classification obtained in the document identification data acquisition step is a classification that means the file is stored as a document, a document acquisition step of obtaining the file name and binary data of the document associated with the document identification data obtained in the document identification data acquisition step from the document storage database.

[0013] Furthermore, the present invention provides an additional attachment support program for an information processing device equipped with a control unit and a storage unit, which supports the process of adding another document to a linked document after linking a linked source document with attached documents from a linked source database to a linked destination database to generate a linked destination document, wherein the storage unit stores a linked source database containing document number linking data including a linked source document number which is the document number of the linked source document and a linked document number which is the document number of the linked document, and a linked destination database containing document number linking data including a linked destination document number which is the document number of the linked destination document and the linked document number, and journal entry data including the linked destination document number and approval classification, and the storage unit provides an additional attachment support program for an information processing device equipped with a control unit and a storage unit, which supports the process of adding another document to the linked destination document. The system is characterized by including: an approval classification acquisition step that acquires an approval classification associated with a linked document number specified on a screen for modifying the linked document from the journal entry data stored in the system; an additional attachment storage step that, if the approval classification acquired in the approval classification acquisition step is a classification indicating that the linked document has not yet been finalized, generates electronic document linking data including the linked document number and document identification data for the additionally attached document and stores it in the linked database; and an error message display step that, if the approval classification acquired in the approval classification acquisition step is a classification indicating that the linked document has already been finalized, displays an error message on the screen indicating that additional attachments for the linked document identified by the specified linked document number cannot be made.

[0014] Furthermore, the additional attachment support program according to the present invention can support the task of verifying the documents attached to the source document linked to the linked document, and the storage unit stores a source database in which electronic document linking data including document identification data for identifying the document number and the document and a classification of the method for storing the data, and document number linking data including the source document number which is the document number of the source document and the linked document number which is the document number of the linked document, and the linked document number, and a linked destination database in which document number linking data including the linked destination document number which is the document number of the linked document and the linked document number, and a document storage database in which document data including document identification data, the file name of the document and the binary data of the document, and to cause the control unit to execute the following: the source database in which electronic document linking data including the document number linking data stored in the source database and the document number linking data stored in the linked destination database, using the linked document number, and the linked destination document number The method further includes: a temporary table generation step of generating a temporary table for identifying voucher numbers, which is a table containing details that are associated with voucher numbers; a confirmation candidate display step of displaying the details included in the temporary table for identifying voucher numbers as confirmation candidates; a document identification data acquisition step of obtaining, when a specific detail is selected from the details displayed in the confirmation candidate display step, the source voucher number corresponding to the linked voucher number held by the selected specific detail is obtained from the temporary table for identifying voucher numbers, and further obtaining document identification data and classification associated with the obtained source voucher number from the electronic document linking data stored in the source database; and, if the classification obtained in the document identification data acquisition step is a classification that means storing a file as a document, a document acquisition step of obtaining the file name and binary data of the document associated with the document identification data obtained in the document identification data acquisition step from the document storage database. [Effects of the Invention]

[0015] According to the present invention, after linking a linked source slip with an attached certificate from a linked source database to a linked destination database to generate a linked destination slip, it is possible to support the operation of additionally attaching another certificate to the linked destination slip.

Brief Description of the Drawings

[0016] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of an additional attachment operation support device. [Figure 2] FIG. 2 is a diagram showing an example of a list of systems and databases related to the present embodiment. [Figure 3] FIG. 3 is a diagram showing an example of a conventional business flow when there is a delivery in April. [Figure 4] FIG. 4 is a diagram showing an example of a conventional business flow when an invoice for the delivery in April is sent in May. [Figure 5] FIG. 5 is a diagram showing an example of a business flow in the present embodiment when there is a delivery in April. [Figure 6] FIG. 6 is a diagram showing an example of a business flow in the present embodiment when an invoice for the delivery in April is sent in May. [Figure 7] FIG. 7 is a diagram showing an example of a business flow for issuing a red - black slip. [Figure 8] FIG. 8 is a diagram showing an example of a processing flow according to the present embodiment. [Figure 9] FIG. 9 is a diagram showing an example of the registration of a purchase slip. [Figure 10] FIG. 10 is a diagram showing an example of the link from sales to finance. [Figure 11] FIG. 11 is a diagram showing an example of additional attachment by journal entry input. [Figure 12] FIG. 12 is a diagram showing an example when attempting to perform additional attachment to a slip that has been finally approved. [Figure 13] FIG. 13 is a diagram showing an example of a record finally generated in the sales DB. [Figure 14]FIG. 14 is a diagram showing an example of a record finally generated in the accounting DB. [Figure 15] FIG. 15 is a diagram showing an example of a record finally generated in the voucher storage DB. [Figure 16] FIG. 16 is a diagram showing an example of a general ledger screen. [Figure 17] FIG. 17 is a diagram showing an example of the generation of a temporary table for specifying voucher numbers. [Figure 18] FIG. 18 is a diagram showing an example of the generated temporary table for specifying voucher numbers. [Figure 19] FIG. 19 is a diagram showing an example of a temporary table for specifying voucher numbers generated when aggregating multiple vouchers and linking them to the accounting DB. [Figure 20] FIG. 20 is a diagram showing an example of a general ledger detail inquiry screen. [Figure 21] FIG. 21 is a diagram showing an example of data acquisition from electronic voucher linking data. [Figure 22] FIG. 22 is a diagram showing an example of voucher acquisition. [Figure 23] FIG. 23 is a diagram showing an example of voucher acquisition. [Figure 24] FIG. 24 is a diagram showing an example of an attached file list screen. [Figure 25] FIG. 25 is a diagram showing an example of an attached file details screen. [Embodiments of the Invention]

[0017] Hereinafter, embodiments of the additional attachment business support device, additional attachment business support method, and additional attachment business support program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by this embodiment.

[0018] [1. Overview] In recent years, the obligation to store electronic transaction data has been increasing in order to comply with laws such as the Electronic Bookkeeping Law. In this context, there is a demand to be able to view invoices and regulatory documents linked to accounting records. Specifically, there is a demand to be able to verify the data flow from sales management systems and expense reimbursement systems to accounting while comparing it with supporting documents.

[0019] For example, there is a request to check which financial vouchers (such as liability or travel expense vouchers) a particular financial voucher originated from and what supporting documents it is linked to. There is also a request to attach supporting documents when they become available after voucher entry from sales management systems and expense reimbursement systems (for example, when an invoice for an October voucher arrives in November).

[0020] However, traditionally, while it was possible to link vouchers and supporting documents, it was not possible to attach supporting documents midway through the process. As a result, after the linking process, the accounting department had no choice but to issue red / black vouchers, which placed a heavy burden on them. Furthermore, issuing red / black vouchers made it difficult to trace the linkage with sales management systems and expense reimbursement systems, which was undesirable from a control standpoint. In addition, because different people were in charge of each task, managing supporting documents became complicated, and it was difficult to know at what stage of the linking process the supporting documents were attached.

[0021] In other words, traditionally, it was impossible to attach supporting documents during the process of linking to accounting, so the accounting department had to create new red / black vouchers and reattach the supporting documents. This resulted in not only increased costs, but also the problem that the vouchers to be attached were not linked vouchers, making it difficult to trace the linking process and delaying the collection of information for management decisions.

[0022] Therefore, in this embodiment, for example, it is possible to attach supporting documents from multiple systems. This eliminates the need to create unnecessary red / black slips, thus distributing the workload that was concentrated in the accounting department. However, slips that have already received final approval will continue to be subject to red / black slip creation as before.

[0023] Furthermore, in this embodiment, for example, the management of files attached to multiple systems is completed entirely on the same ERP (Enterprise Resource Planning) system. This makes it possible to drill down from financial vouchers and confirm which system and which voucher the attached document was for. As a result, there are no unnecessary red / black vouchers, and the integration process can be verified without interruption.

[0024] In this embodiment, for example, the accounting system can now attach supporting documents to vouchers linked from the sales management system and expense reimbursement system. This allows for the attachment of additional supporting documents without creating unnecessary red / black vouchers when processing requires additional documents or when supporting documents are missing. This ability to attach additional documents has successfully reduced the costs associated with creating and verifying red / black vouchers, and has also made the linking process easier to follow, resulting in faster business decision-making.

[0025] For reference, Figure 2 shows a list of systems and databases related to this embodiment. The specific configuration and operation will be described below.

[0026] [2. Structure] An example of the configuration of the additional attachment business support device 100 according to this embodiment will be described with reference to Figure 1. Figure 1 is a block diagram showing an example of the configuration of the additional attachment business support device 100.

[0027] The additional business support device 100 is a commercially available desktop personal computer. However, the additional business support device 100 is not limited to stationary information processing devices such as desktop personal computers; it 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.

[0028] The additional business support device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each component of the additional business support device 100 is connected to communicate via any communication path.

[0029] The communication interface unit 104 connects the additional attached business support device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines. The communication interface unit 104 has the function of communicating data with other devices via communication lines. Here, the network 300 has the function of connecting the additional attached business 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). Data such as various masters, which will be described later, may be stored in the server 200, for example.

[0030] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with a mouse to provide pointing device functionality. 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 mouse 112.

[0031] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0032] The memory unit 106 includes, for example, a sales DB 106a as the source database, an accounting DB 106b as the destination database, and a document storage DB 106c as the document storage database.

[0033] As shown in Figure 13, etc., the sales DB106a includes, for example, purchase information data, electronic receipt linking data (sales), invoice number linking data, etc.

[0034] The aforementioned purchase information data includes, for example, a voucher number, as shown in Figure 13, etc. The aforementioned electronic document linking data (sales) includes, for example, a voucher number, document identification data (electronic document GUID) for identifying the document, a classification of the database where the data is stored that indicates the sales database (sales management), a classification of the method of storing the data (system classification), etc. The aforementioned classification (system classification) is either a classification that means the file is stored as a document ("electronic transaction" or "scanner storage" system classification), or a classification that means the file is stored as another file rather than a document ("other" system classification).

[0035] As shown in Figure 13, the aforementioned voucher number-linking data includes, for example, the voucher number of the source voucher (purchase voucher A and purchase voucher B), the voucher number of the voucher used for linking (linking voucher Z and linking voucher X), and so on.

[0036] As shown in Figure 14, etc., accounting DB106b includes, for example, journal entry data, electronic document linking data (financial), file data, voucher number linking data, etc.

[0037] The aforementioned journal entry data includes, for example, a voucher number, an approval category, etc., as shown in Figures 11, 12, and 14. The approval category is either an approval category indicating that the linked voucher has not yet been finalized (the "Approving" category in Figure 11), or an approval category indicating that the linked voucher has already been finalized (the "Approved" category in Figure 12).

[0038] As shown in Figure 14, the aforementioned electronic document linking data (finance) includes, for example, the voucher number, the document identification data (electronic document GUID), a classification of the database where the data is stored that indicates the accounting database (financial accounting), the classification (system classification), and so on.

[0039] As shown in Figure 14, the aforementioned voucher number-linked data includes, for example, the linked voucher number (Journal Voucher C and Journal Voucher D), which is the voucher number of the linked voucher, and the linked voucher number (Linked Voucher Z and Linked Voucher X), etc.

[0040] As shown in Figure 14, the file data consists of file image data and file information data. As shown in Figure 14, the file image data includes, for example, the document identification data (electronic document GUID), the binary data of the document (data), etc. As shown in Figure 14, the file information data includes, for example, the document identification data (electronic document GUID), a memo, the file name of the document, etc.

[0041] As shown in Figure 15, etc., the document storage DB106c includes, for example, document data. As shown in Figure 15, etc., the document data consists of document image data and document information data. As shown in Figure 15, etc., the document image data includes, for example, the document identification data (electronic document GUID), the binary data of the document (data), etc. As shown in Figure 15, etc., the document information data includes, for example, the document identification data (electronic document GUID), the file name of the document, the file type of the document (file type), the transaction date, the amount, the name of the trading partner, the item name, the receipt date, the size, the reason for the delay, the classification (system classification), the deletion flag, etc.

[0042] The control unit 102 is a CPU or similar component that comprehensively controls the additional attached business support device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0043] Functionally, the control unit 102 includes, for example, (1) an approval classification acquisition unit 102a as an approval classification acquisition means that acquires an approval classification associated with the linked document number specified on the screen for modifying the linked document from the journal entry data stored in the linked database; (2) an additional attachment storage unit 102b as an additional attachment storage means that, if the approval classification acquired by the approval classification acquisition means is a classification indicating that the final approval of the linked document has not yet been completed, generates electronic document linking data including the linked document number and document identification data for the additionally attached document and stores it in the linked database; (3) an error message display unit 102c as an error message display means that, if the approval classification acquired by the approval classification acquisition means is a classification indicating that the final approval of the linked document has already been completed, displays an error message on the screen indicating that additional attachment of a document to the linked document identified by the specified linked document number is not possible; and (4) the document number linking data stored in the linked source database and the data stored in the linked database (5) A temporary table generation unit 102d, which is a temporary table generation means that generates a temporary table for identifying a voucher number, which is a table containing details that associate the source voucher number and the destination voucher number with the linked voucher number, based on the voucher number linkage data that has been generated, (6) a confirmation candidate display unit 102e, which is a confirmation candidate display means that displays the details included in the temporary table for identifying a voucher number as confirmation candidates, and (7) when a specific detail is selected from the details displayed by the confirmation candidate display means, the temporary table for identifying a voucher number (7) If the classification obtained by the document identification data acquisition means is a classification that means the file is to be stored as a document, then from the document storage database, the document identification data acquisition unit 102f obtains the source document number corresponding to the linked document number held by the selected specific item from the table, and further obtains the document identification data and classification associated with the obtained source document number from the electronic document linking data stored in the source database,The system includes: (8) a document acquisition unit 102g which acquires the file name and binary data of a document associated with the document identification data acquired by the document identification data acquisition means; (8) a file name list display unit 102h which displays a list of document file names acquired by the document acquisition means when a specific item is selected from the items displayed by the confirmation candidate display means; and (9) a document display unit 102i which displays the file name and binary data of a document selected from the file names of documents displayed by the file name list display means among the file names and binary data of documents acquired by the document acquisition means (a document display unit which displays the file name and binary data of a document acquired by the document acquisition means when a specific item is selected from the items displayed by the confirmation candidate display means). Specific examples of the processing performed by each unit are described in [4. Specific Examples of Processing] below.

[0044] [3. Overview of the Business Flow] This section will compare and explain the outline of the conventional business process flow with the outline of the business process flow in this embodiment.

[0045] [3-1. Overview of the conventional business workflow] Figure 3 illustrates the conventional workflow for deliveries made in April. First, the supplier's representative sends the delivery slip to the purchasing manager. Next, the purchasing manager generates purchase data from the sales management system, attaching the delivery slip. Finally, the purchasing manager transfers the generated purchase data from the sales management system to the accounting system, thereby forwarding the delivery slip to the accounting manager.

[0046] Figure 4 illustrates the conventional workflow when invoices for April deliveries are sent in May. Since journal entries have already been linked from the sales management system to the accounting system, the purchasing staff cannot attach the invoices. This is also the case in this embodiment, but the problem in the past was that the accounting staff could not attach invoices and approval documents from the accounting system midway through the process. This inability to attach documents midway through the process increased the burden on the accounting staff, and they had to create extra red / black slips, as shown on the far right of Figure 4.

[0047] [3-2. Overview of the business flow in this embodiment] Figure 5 shows the workflow in this embodiment when a delivery occurs in April. Since it is the same as the content in Figure 3, the explanation is omitted.

[0048] The workflow in this embodiment, where an invoice for April deliveries is sent in May, will be explained using Figure 6. As mentioned above, since journal entries have already been linked from the sales management system to the accounting system, purchasing staff cannot attach invoices, which remains unchanged from the conventional method. However, in this embodiment, accounting staff can attach invoices and approval documents from the accounting system midway through the process. Note that, both in the conventional method and in this embodiment, as shown on the far right of Figure 6, documents cannot be attached midway through the process to a voucher that has already received final approval. If you want to attach documents to a voucher that has already received final approval, you need to create a new red / black entry, as shown in Figure 7.

[0049] Thus, in this embodiment, by enabling accounting staff to attach documents from the accounting system midway through the process, we succeeded in reducing the burden on the accounting department and strengthening its control. Furthermore, in this embodiment, the following became possible, for example: • Documents can now be attached from multiple systems. • It eliminated the need to create unnecessary red / black slips. • It is now possible to drill down from financial vouchers and see a list of which system and which voucher the attached document was for. • Managing files attached across multiple systems can now be handled entirely within a single ERP system.

[0050] [4. Specific examples of processing] This section describes a specific example of the process according to this embodiment. In this section, as shown in Figure 8, we will explain using the example of a scenario in which the purchasing staff registers file A (delivery note), and then the accounting staff registers file B (invoice) and file C (approval document).

[0051] Section [4-1] below will explain specific examples of attaching additional supporting documents, and Section [4-2] will explain specific examples of verifying supporting documents.

[0052] [4-1. Specific examples of attaching additional supporting documents] This section explains specific examples of attaching additional supporting documents.

[0053] (1) Registration of purchase slips First, the purchasing manager enters information about purchase slip A from the purchase input screen shown in Figure 9 and attaches the delivery slip. As a result, purchase information data, slip number linking data, and electronic document linking data (sales) are generated in the sales DB, as shown in Figure 9. Also, as shown in Figure 9, document image data and document information data, including records for the delivery slip, are generated in the document storage DB.

[0054] (2) Integration from sales to finance Next, as shown in Figure 10, purchase slip A is linked from the sales database to the accounting database. At this time, as shown in Figure 10, a new record is added to the slip number linkage data in the sales database. Also, as shown in Figure 10, journal entry data and slip number linkage data are generated in the accounting database. As shown in Figure 10, the slip number linkage data in the sales database and the slip number linkage data in the accounting database contain the same linkage slip, "Linkage Slip Z," so it is possible to trace the linkage between the databases by using this linkage slip.

[0055] (3) Additional attachments via journal entry Next, the accounting staff member enters information related to journal entry C by calling up the editing mode from the journal entry input screen shown in Figure 11, and also adds an invoice and approval document. The details of the additional attachments are explained below.

[0056] The approval classification acquisition unit 102a acquires the approval classification associated with the linked document number specified on the screen for modifying the linked document (journal entry screen) from the journal entry data stored in the linked database (accounting DB).

[0057] Specifically, when "Journal Entry C" is specified as the voucher number on the journal entry input screen shown in Figure 11, the approval status acquisition unit 102a retrieves "Approved" as the approval status associated with Journal Entry C from the journal entry data shown again in the accounting DB in Figure 11. In contrast, although it differs from this example, if the journal entry data in the accounting DB is as shown in Figure 12, the approval status acquisition unit 102a retrieves "Approved" as the approval status associated with Journal Entry C.

[0058] If the approval category acquired by the approval category acquisition unit 102a is an approval category indicating that the final approval of the linked document has not yet been completed ("approved" approval category), the additional attachment storage unit 102b generates electronic document linking data including the linked document number and document identification data (electronic document Guid) for the additionally attached document and stores it in the linked database (accounting DB).

[0059] Specifically, if the approval classification acquired by the approval classification acquisition unit 102a is "in approval," the additional attachment storage unit 102b generates electronic document linkage data (finance) including a record having the voucher number "Journal Entry C" and the electronic document Guid "GuidB" for the invoice, etc., and a record having the voucher number "Journal Entry C" and the electronic document Guid "GuidC" for the approval document, etc., and stores it in the accounting DB.

[0060] This creates a link between the invoice or approval document and the delivery note, following this sequence: Invoice or approval document → Journal entry C → Linking document Z → Purchase slip A → Delivery note. In other words, it was possible to link the delivery note generated in April with the invoice and approval document generated in May.

[0061] Furthermore, as shown in Figure 11, file image data and file information data containing records for approval documents are generated and stored in the accounting DB. Then, as shown in Figure 11, records for invoices are generated and stored in the document image data and document information data in the document storage DB.

[0062] If the approval category obtained by the approval category acquisition unit 102a is a category indicating that the final approval of the linked document has already been completed (the "approved" approval category), the error message display unit 102c displays an error message on the screen (journal entry screen) indicating that it is not possible to attach additional supporting documents for the linked document identified by the specified linked document number.

[0063] Specifically, if the approval category obtained by the approval category acquisition unit 102a is "approved," the error message display unit 102c displays an error message on the journal entry input screen indicating that additional supporting documents cannot be attached to journal entry voucher C, as shown in Figure 12.

[0064] (4) The final generated record Assuming that purchase slip B, linking slip X, and journal entry slip D are also registered using the same method as described in (1) to (3), the records ultimately generated in the sales DB, accounting DB, and document storage DB will be as shown in Figures 13 to 15, respectively.

[0065] As described above in section [4-1], the additional attachment support device 100 according to this embodiment can support the process of linking a source document (in this example, purchase slip A) with attached supporting documents (in this example, delivery slip) from the source database (in this example, sales DB) to the destination database (in this example, accounting DB) to generate a destination document (in this example, journal entry slip C), and then adding other supporting documents (in this example, invoice and approval document) to the destination document. As a result, when processing requiring the attachment of additional supporting documents occurs or when supporting documents are not attached, accounting staff no longer need to create new red / black slips as in the past, thus reducing costs and labor and eliminating work errors.

[0066] [4-2. Specific Examples of Document Verification] This section will explain specific examples of how to verify supporting documents.

[0067] (1) Generation of a temporary table for identifying invoice numbers (acquisition of linked information) When the "Details Inquiry" button is pressed on the general ledger screen shown in Figure 16, a temporary table for identifying the voucher number is generated as follows.

[0068] The temporary table generation unit 102d generates a temporary table for identifying voucher numbers, which is a table containing details that associate the source voucher number and the destination voucher number, based on the voucher number association data stored in the source database (sales DB) and the voucher number association data stored in the destination database (accounting DB), using the linked voucher number. Specifically, it is as follows:

[0069] (A) First, as shown in (A) of Figure 17, the temporary table generation unit 102d adds records where both the financial voucher number and voucher number are "Journal Voucher C" and records where both the financial voucher number and voucher number are "Journal Voucher D" to the voucher number linkage data in the accounting DB, and generates a temporary table for voucher number identification (interim version).

[0070] (B) Next, the temporary table generation unit 102d copies the temporary table for identifying voucher numbers (intermediate version) generated in the accounting DB into the sales DB, as shown in Figure 17(B).

[0071] (C) Next, the temporary table generation unit 102d refers to the invoice number linkage data in the sales DB and traces back from the linked invoice to the purchase invoice. Specifically, as shown in (C) of Figure 17, the temporary table generation unit 102d refers to the invoice number linkage data in the sales DB and traces back from the linked invoice Z to the purchase invoice A. In addition, although not shown in the figure, the temporary table generation unit 102d also refers to the invoice number linkage data in the sales DB and traces back from the linked invoice X to the purchase invoice B. This traceback continues until a record is reached in the invoice number linkage data in the sales DB where "linked invoice number = linked invoice number".

[0072] (D) Next, the temporary table generation unit 102d updates the temporary table for identifying the voucher number (interim version) generated in (B) with the purchase voucher traced back in (C). Specifically, as shown in (D) of Figure 17, the temporary table generation unit 102d adds the record for financial voucher number "Journal Entry Voucher C" and the traced voucher number "Purchase Voucher A", and the record for financial voucher number "Journal Entry Voucher D" and the traced voucher number "Purchase Voucher B", to the temporary table for identifying the voucher number (interim version) in the sales DB, thereby generating the temporary table for identifying the voucher number (final version) in the sales DB.

[0073] (E) Finally, the temporary table generation unit 102d copies the temporary table for identifying transaction numbers (final version) generated in the sales DB in (D) into the accounting DB, as shown in (E) of Figure 18. In this way, the temporary table for identifying transaction numbers, tracing back from the journal entry to the source, is completed.

[0074] Figure 19 shows a temporary table for identifying voucher numbers that is generated when multiple vouchers are consolidated and linked to the accounting database. The temporary table for identifying voucher numbers shown in Figure 19 is an example where purchase vouchers A, B, and C are consolidated into linked voucher Z to become journal voucher C.

[0075] (2) Display of the ledger details inquiry screen (acquisition of attached information) When the "Details Inquiry" button is pressed on the general ledger screen shown in Figure 16, a temporary table for identifying the voucher number is generated as explained in (1), and then, as explained below, the ledger details inquiry screen shown in Figure 20 is displayed.

[0076] The confirmation candidate display unit 102e displays the details included in the temporary table for identifying the voucher number as confirmation candidates. In other words, the confirmation candidate display unit 102e displays the linking process for all vouchers displayed on the general ledger screen on the ledger details inquiry screen.

[0077] Specifically, as shown in Figure 21, the confirmation candidate display unit 102e retrieves data from the electronic document linking data (sales) if the voucher number in the temporary table for voucher number identification corresponds to the system classification "sales management" in the system classification information, and retrieves data from the electronic document linking data (finance) if it corresponds to the system classification "financial accounting" in the system classification information. The confirmation candidate display unit 102e then displays the retrieved data on the ledger details inquiry screen.

[0078] (3) Obtaining evidence There are two ways to check the documents: one is to display the supporting documents via the attached file list screen from the ledger details inquiry screen, and the other is to display the supporting documents directly from the ledger details inquiry screen. In either case, prior acquisition of the supporting documents is required. Therefore, in this section (3), we will explain in detail how to acquire the supporting documents.

[0079] When a specific item is selected from the items displayed by the confirmation candidate display unit 102e, the document identification data acquisition unit 102f acquires the source document number corresponding to the linked document number held by the selected specific item from the temporary table for document number identification.

[0080] Specifically, in the ledger details inquiry screen shown in Figure 20, when the details on the first to third lines (the details with financial voucher number "Journal Voucher C") are selected, the document identification data acquisition unit 102f acquires "Purchase Voucher A", "Linking Voucher Z", and "Journal Voucher C" from the temporary table for voucher number identification shown in Figure 22 as voucher numbers corresponding to the selected financial voucher number "Journal Voucher C".

[0081] Next, the document identification data acquisition unit 102f acquires the document identification data (electronic document Guid) and classification (system classification) associated with the acquired source voucher number from the electronic document linkage data stored in the source database (sales DB) or the linked database (accounting DB).

[0082] Specifically, the acquired slip number "Purchase Slip A" corresponds to the system classification "Sales Management" when referring to the system classification information in Figure 22. In this case, the document identification data acquisition unit 102f acquires a record from the electronic document linking data (sales) in Figure 22 that has the slip number "Purchase Slip A" and the classification "Sales Management". The document identification data acquisition unit 102f then acquires the electronic document Guid "GuidA" and the system classification "Electronic Transaction" from the acquired record. The acquisition flow described in this paragraph is also shown in Figure 23 for reference.

[0083] Furthermore, as shown in Figure 22, the acquired voucher number "Linking Voucher Z" does not exist in either the electronic voucher linking data (sales) or the electronic voucher linking data (finance). Therefore, processing for "Linking Voucher Z" ends here.

[0084] Then, referring to the system classification information in Figure 22, the acquired "Journal Entry C" corresponds to the system classification "Financial Accounting". In this case, the document identification data acquisition unit 102f acquires two records from the electronic document linking data (finance) in Figure 22 that have "Journal Entry C" and the classification "Financial Accounting". The document identification data acquisition unit 102f then acquires the electronic document Guid "GuidB" and system classification "Scanner Storage" and the electronic document Guid "GuidC" and system classification "Other" from the acquired records.

[0085] The following is a summary of the data obtained from the temporary table for identifying the voucher number, the obtained electronic document GUID, and the obtained system classification, based on the processing up to this point. • "Purchase Invoice A, Guide A, Electronic Transaction" • "Journal entry voucher C, Guide B, saved via scanner" • "Journal entry voucher C, GuidC, others"

[0086] If the classification obtained by the document identification data acquisition unit 102f is a classification that means the file will be stored as a document (a system classification of "electronic transaction" or "scanner storage"), the document acquisition unit 102g obtains the file name and binary data of the document linked to the document identification data (electronic document Guid) obtained by the document identification data acquisition unit 102f from the document data (document information data and document image data) stored in the document storage DB.

[0087] Specifically, for "Purchase Invoice A, GuidA, Electronic Transaction," the document acquisition unit 102g acquires the file name "Delivery Note.pdf" etc., associated with GuidA, from the document information data, as shown in Figure 22, and acquires the data "File A Binary Data" associated with GuidA from the document image data. The acquisition flow described in this paragraph is also shown in Figure 23 for reference.

[0088] Furthermore, the document acquisition unit 102g, for "Journal entry voucher C, GuidB, Scanner storage," acquires the file name "Invoice.pdf" etc. associated with GuidB from the document information data, as shown in Figure 22, and acquires the data "File B binary data" associated with GuidB from the document image data.

[0089] In response, if the classification obtained by the document identification data acquisition unit 102f is a classification that means the file will be stored as an other file rather than a document (the "other" system classification), the document acquisition unit 102g obtains the file name and the binary data of the file associated with the document identification data (electronic document Guid) obtained by the document identification data acquisition unit 102f from the file data (file information data and file image data) stored in the accounting DB.

[0090] Specifically, for "Journal Entry Voucher C, GuidC, and Others," the document acquisition unit 102g retrieves the file name "Approval Document.xlsx" associated with GuidC from the file information data, as shown in Figure 22, and retrieves the data "File C Binary Data" associated with GuidC from the file image data.

[0091] The following is a summary of the process so far, including the voucher number obtained from the temporary table for voucher number identification, the obtained system classification, the obtained file name, and the obtained binary data. • "Purchase Invoice A, Electronic Transaction, Delivery Note.pdf, File A Binary Data" • "Journal entry voucher C, scanned and saved, invoice.pdf, file B binary data" • "Journal entry voucher C, Others, Approval document.xlsx, File C Binary data"

[0092] (4) Method of displaying supporting documents via the attachment list screen from the ledger details inquiry screen. The file name list display unit 102h displays a list of file names of the documents obtained by the document acquisition unit 102g when a specific detail is selected from the details displayed by the confirmation candidate display unit 102e. In other words, the file name list display unit 102h allows users to check a list of attached files associated with the financial voucher number of the selected line by matching them with the source voucher number of the attached file in the detail inquiry.

[0093] Specifically, in the ledger details inquiry screen shown in Figure 20, when any of the details in the first to third rows (the details with financial voucher number "Journal Voucher C") are selected and the "Attached Documents" button is pressed, the file name list display unit 102h displays the file name obtained by the document acquisition unit 102g, the voucher number obtained from the temporary table for voucher number identification by the document identification data acquisition unit 102f, and the system classification obtained by the document identification data acquisition unit 102f, all together on the attached file list screen, as shown in Figure 24.

[0094] Next, the document display unit 102i displays the file names and binary data of the documents selected from the file names of the documents displayed by the file name list display unit 102h, from among the file names and binary data of the documents acquired by the document acquisition unit 102g.

[0095] Specifically, when the "Details" button (Details button) for the third row (Attachment source slip number "Purchase slip A") on the attachment list screen shown in Figure 24 is pressed, the document display unit 102i displays the file name of the document for that third row (Delivery note.pdf) and the binary data of the document (Image of the Delivery Note) on the attachment details screen, as shown in Figure 25.

[0096] Although not shown in the illustration, when the "Details" button (Details button) for the first row (Attachment source voucher number "Journal entry voucher C") is pressed on the attachment list screen shown in Figure 24, the document display unit 102i displays the file name (Approval document.xlsx) and binary data of the file (Image of approval document) for the first row on the attachment details screen. Similarly, when the Details button for the second row (Attachment source voucher number "Journal entry voucher C") is pressed, the document display unit 102i displays the file name (Invoice.pdf) and binary data of the document (Image of invoice) for the second row on the attachment details screen.

[0097] (5) Method of directly displaying supporting documents from the ledger details inquiry screen When a specific item is selected from the items displayed by the confirmation candidate display unit 102e, the document display unit 102i displays the file name and binary data of the document obtained by the document display unit 102i. In other words, if the attachment information of the source purchase slip is selected and "Attached Document" is pressed, the document display unit 102i displays the slip number of the purchase slip. On the other hand, if the attachment information of the linked financial slip is selected and "Attached Document" is pressed, the financial slip number is displayed.

[0098] Specifically, in the ledger details inquiry screen shown in Figure 20, when the third line item (the item with the attached source slip number "Purchase Slip A") is selected and the "Attached Documents" button is pressed, the document display unit 102i displays the file name of the document for that third line (Delivery Note.pdf) and the binary data of the document (image of the delivery note), etc., on the attachment details screen, as shown in Figure 25.

[0099] Although not shown in the diagram, in the ledger details inquiry screen of Figure 20, when the "Attached Documents" button is pressed while the first line of details (the details of the attached source voucher number "Journal Voucher C") is selected, the document display unit 102i displays the file name (approval document.xlsx) and binary data of the file (image of the approval document) for the first line of details on the attached file details screen. Similarly, when the "Attached Documents" button is pressed while the second line of details (the details of the attached source voucher number "Journal Voucher C") is selected, the document display unit 102i displays the file name (invoice.pdf) and binary data of the document (image of the invoice) for the second line of details on the attached file details screen.

[0100] As described above in section [4-2], the additional attached business support device 100 according to this embodiment can support the task of verifying the supporting documents (in this example, delivery slips) attached to the linked source document (in this example, purchase slip A) linked to the linked destination document (in this example, journal entry slip C). As a result, the person in charge (in this example, accounting staff) can easily verify the supporting documents (in this example, delivery slips) linked to the document (in this example, purchase slip A) linked from the linked source database (in this example, sales DB) to the linked destination database (in this example, accounting DB) on the linked destination database (in this example, accounting DB) side, thereby reducing costs and labor and eliminating verification errors.

[0101] The additional attached business support device 100 according to this embodiment can be rephrased as a document verification business support device 100, focusing on its function of supporting the business of verifying documents as described in section [4-2].

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

[0103] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0104] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0105] [6. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0106] 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 by known methods.

[0107] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0108] Furthermore, with respect to the additional attached business support device 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[0109] For example, the processing functions of the additional business support device 100, particularly those performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the additional business support device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) contains a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0110] Furthermore, this computer program may be stored on an application program server connected to the additional business support device 100 via any network, and it is possible to download all or part of it as needed.

[0111] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, 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 Blu-ray (Registered Trademark) Discs.

[0112] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

[0113] The various databases stored in the memory unit are 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.

[0114] Furthermore, the additional attached business support device 100 may be configured as an information processing device such as a known personal computer or workstation, or as an information processing device to which any peripheral devices are connected. Alternatively, the additional attached business support device 100 may be implemented by installing software (including programs or data, etc.) that enables the processing described in this embodiment onto the device.

[0115] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0116] This invention is useful in any industry and sector where document management is required. [Explanation of symbols]

[0117] 100 Additional Attachment Business Support Device 102 Control Unit 102a Approval classification acquisition department 102b Additional attachment storage section 102c Error message display section 102d Temporary Table Generation Unit 102e Confirmation Candidate Display Section 102f Document Identification Data Acquisition Unit 102g Document Acquisition Department 102h File name list display section 102i Proof Display Unit 104 Communication Interface Section 106 Storage section 106a Sales Database 106b Accounting DB 106c Document Storage Database 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

[Claim 1] An additional attachment support device comprising a control unit and a storage unit supports the process of adding another document to a linked document after linking a linked document with attached supporting documents from a linked database to a linked database to generate a linked document, The aforementioned storage unit includes: A source database storing data that links voucher numbers, including the voucher number of the source voucher and the voucher number of the voucher used for linking, A linked database containing: a linked voucher number linkage data including the linked voucher number which is the voucher number of the linked voucher and the linked voucher number; and journal entry data including the linked voucher number and approval classification. It is remembered, The control unit, An approval classification acquisition means that acquires an approval classification associated with the linked document number specified on the screen for modifying the linked document from the journal entry data stored in the linked database, If the approval classification obtained by the approval classification acquisition means is a classification indicating that the final approval of the linked document has not yet been completed, the additional attachment storage means generates electronic document linking data including the linked document number and document identification data for the additionally attached document and stores it in the linked database. If the approval category obtained by the approval category acquisition means is a category indicating that the final approval of the linked document has already been completed, the error message display means displays an error message on the screen indicating that it is not possible to attach additional supporting documents to the linked document identified by the specified linked document number, To be equipped, An additional attachment for business support, characterized by the following.

Images