File registration support apparatus, file registration support method, and file registration support program

Abstract

To provide a file registration support apparatus, and the like, for supporting registration of a voucher file and a non-voucher file through the same screen.SOLUTION: A file registration support apparatus is configured to: (1) when a button to attach a file is selected on a slip input screen, which is a screen for inputting the content of a slip, display an attachment file list screen; and (2) when a file is attached on the attachment file list screen, display an attachment file detail screen including a region for inputting an image of the attached file and detail information on the attached file, while displaying a list of items according to the type of the attached file selected on the attachment file detail screen on the attachment file detail screen. Regarding some of the items to be displayed, in the case where the content of the slip has already been input on the slip input screen before displaying the attachment file list screen, the content of the slip input on the slip input screen are set, as item values, and displayed.SELECTED DRAWING: Figure 14

Description

[Technical Field]

[0001] The present invention relates to a file registration support device, a file registration support method, and a file registration support program. [Background technology]

[0002] Paragraph 0006 of Patent Document 1 states, "However, in order to digitize and store a large number of supporting documents using a scanner, and to issue journal entries or prepare expense reimbursement application documents based on these supporting documents, the work of associating the journal entries or expense reimbursement application documents with the supporting documents is necessary, which is cumbersome." Furthermore, paragraph 0007 of Patent Document 1 states, "Therefore, an object of the present invention is to provide a supporting document processing system and a supporting document processing method that enable the efficiency of accounting processing based on supporting documents." [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2018-116602 Summary of the Invention [Problem to be solved by the invention]

[0004] When creating a voucher, not only supporting documents such as receipts but also non-supporting documents such as approval documents may be attached to the voucher. This is because, for example, when approving a voucher, there is a desire to check not only the receipt corresponding to the voucher but also the approval document corresponding to the voucher.

[0005] However, in the past, supporting documents and non-supporting documents were registered from different screens, so the user had to decide which screen to launch depending on the type of file they wanted to register, and there was a risk that they would launch the wrong screen and register the file in the wrong destination (for example, registering a supporting document file in the destination for a non-supporting document).

[0006] Furthermore, if users wanted to register both supporting documents and non-supporting documents, they had to register them from separate screens, which placed a heavy workload on the user.

[0007] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a file registration support device, a file registration support method, and a file registration support program that can support the registration of evidence files and non-evidence files from the same screen. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the object, the file registration support device of the present invention is a file registration support device that has a control unit that can support the registration of supporting documents files and non-supporting documents files from the same screen, and the control unit is equipped with: an attachment list screen display means that, when a button for attaching a file is selected on a voucher input screen that is a screen for entering the contents of a voucher, displays an attachment list screen that is a screen for attaching a file; and an attachment detail screen display means that, when a file is attached on the attachment list screen, displays an attachment detail screen that is a screen for entering detailed information about the file to be attached to the voucher, including an area for entering an image of the attached file and detailed information about the attached file, and the attachment detail screen display means displays on the attachment detail screen a list of items corresponding to the type of attached file selected on the attachment detail screen, and for some of the displayed items, if the contents of the voucher were entered on the voucher input screen before the attachment list screen was displayed, displays the contents of the voucher entered on the voucher input screen as the item value.

[0009] In addition, the file registration support device of the present invention is characterized in that the attachment details screen display means obtains a list of items corresponding to the type of attached file selected on the attachment details screen from a display item setting table which contains a list of items to be displayed on the attachment details screen for each file type.

[0010] In addition, the file registration support device of the present invention further comprises a memory unit, and the memory unit stores a screen control table including system identification data for identifying the system to which the voucher input screen belongs and document type identification data for identifying the type of document, and a supporting document type table including the document type identification data, document name, and date-related item name, and the attachment details screen display means acquires from the screen control table the document type identification data linked to the system identification data for the system to which the voucher input screen to which the voucher contents are entered belongs, then acquires from the supporting document type table the document name and date-related item name linked to the acquired document type identification data, and finally displays the acquired document name and date-related item name.

[0011] The file registration support device of the present invention is further characterized in that the attachment list screen display means, when information is input on the attachment details screen and a button for registering an attached file is selected on the attachment details screen, re-displays the attachment list screen including a list of attached files and the corresponding file types, and the control unit further comprises work table generation means, when a button for registering an attached file is selected on the re-displayed attachment list screen, generates a work table including file identification data for the attached file, file type identification classification for the type of attached file, detailed information about the attached file input on the attachment details screen, and binary information about the attached file.

[0012] Furthermore, in the file registration support device according to the present invention, when a button for registering an attached file is selected on the attached file list screen that is displayed again, the control unit redisplays the slip input screen, and when a button for registering a slip is selected on the redisplayed slip input screen, the control unit displays (i) a linking table that links a slip number for identifying the registered slip with the file identification data in the work table, and (ii) when the file type identification category in the work table is a category that indicates the evidence file, a evidence information table that includes the file identification data, the file type identification category, and detailed information about the attached file in the work table, and the file identification data in the work table. the file information table including the file identification data and detailed information about the attached file in the work table; and (iv) a voucher detail table including the voucher number and the contents of the attached file entered on the voucher input screen.

[0013] Furthermore, in the file registration support device according to the present invention, when a voucher approval screen is launched, which is a screen for a person in charge to approve the voucher, the control unit acquires from the voucher detail table the contents of the voucher linked to the voucher number in the workflow case table, and if a voucher linked to the case is registered in the linking table, acquires from the linking table the file identification data linked to the voucher number in the workflow case table, and further acquires detailed information and binary information linked to the acquired file identification data from the voucher information table and the voucher image table, respectively, and registers other files linked to the case in the file information table. is registered, binary information linked to the case identification data in the workflow case table is obtained from the file image table, and if the file selected on the voucher approval screen is the supporting document file, the content of the obtained voucher, detailed information obtained from the supporting document information table, and binary information obtained from the supporting document image table are displayed on the voucher approval screen, and if the file selected on the voucher approval screen is the non-support document file, the content of the obtained voucher and the binary information obtained from the file image table are displayed on the voucher approval screen.

[0014] In addition, the file registration support device of the present invention is characterized in that it further comprises a document search result display means for, when search conditions are input on a document search screen, which is a screen for searching for document files, searching the document information table for information about the document files that matches the input search conditions and displaying the search results on the document search screen.

[0015] Furthermore, the file registration support device according to the present invention is characterized in that the voucher is a delivery note, receipt, invoice or estimate, and the non-voucher is a request for approval.

[0016] Furthermore, the file registration support method of the present invention is a file registration support method executed by an information processing device having a control unit, which is capable of supporting the registration of supporting documents files and non-supporting documents files from the same screen, and includes: an attachment list screen display step executed by the control unit, which, when a button for attaching a file is selected on a voucher input screen, which is a screen for entering the contents of a voucher, displays an attachment list screen, which is a screen for attaching a file; and an attachment detail screen display step, which, when a file is attached on the attachment list screen, displays an attachment detail screen, which is a screen for entering detailed information about the file to be attached to the voucher, including an area for entering an image of the attached file and detailed information about the attached file, wherein in the attachment detail screen display step, a list of items corresponding to the type of attached file selected on the attachment detail screen is displayed on the attachment detail screen, and for some of the displayed items, if the contents of the voucher were entered on the voucher input screen before the attachment list screen was displayed, the contents of the voucher entered on the voucher input screen are displayed with the item values ​​set to the contents of the voucher entered on the voucher input screen.

[0017] Furthermore, the file registration assistance program of the present invention is a file registration assistance program to be executed by an information processing device having a control unit, which is capable of assisting in the registration of supporting documents files and non-supporting documents files from the same screen, and includes: an attachment list screen display step for causing the control unit to execute the program; when a button for attaching a file is selected on a slip input screen, which is a screen for entering the contents of a slip, it displays an attachment list screen, which is a screen for attaching a file; and an attachment detail screen display step for displaying, when a file is attached on the attachment list screen, an attachment detail screen, which is a screen for entering detailed information about the file to be attached to the slip, including an area for entering an image of the attached file and detailed information about the attached file. In the attachment detail screen display step, a list of items corresponding to the type of attached file selected on the attachment detail screen is displayed on the attachment detail screen, and for some of the displayed items, if the contents of the slip were entered on the slip input screen before the attachment list screen was displayed, the contents of the slip entered on the slip input screen are displayed as item values. [Effects of the Invention]

[0018] The present invention has the effect of being able to assist in registering voucher files and non-voucher files from the same screen. [Brief explanation of the drawings]

[0019] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a file registration support device. [Figure 2] FIG. 2 is a diagram showing an example of an outline of the processing flow according to this embodiment. [Figure 3] FIG. 3 is a diagram showing an example of an outline of the processing flow when the system classification is "electronic transaction" or "scanner storage." [Figure 4]FIG. 4 is a diagram showing an example of an outline of the processing flow when the system classification is "other attachments" and a workflow is used. [Figure 5] FIG. 5 is a diagram showing an example of the screen control table and the voucher type table. [Figure 6] FIG. 6 is a diagram showing an example of the supporting document slip work. [Figure 7] FIG. 7 shows an example of the evidence information table and the evidence image table. [Figure 8] FIG. 8 is a diagram showing an example of a table that describes each item included in the evidence information table. [Figure 9] FIG. 9 is a diagram illustrating an example of the journal entry details table and the supporting document linking table. [Figure 10] FIG. 10 shows an example of a workflow case table, a file information table, and a file image table. [Figure 11] FIG. 11 shows an example of the slip input screen at the stage when the slip contents have been entered. [Figure 12] FIG. 12 is a diagram illustrating an example of arguments for a dialog call. [Figure 13] FIG. 13 is a diagram showing an example of the attachment file list screen. [Figure 14] FIG. 14 is a diagram showing an example of an attachment file details screen for inputting detailed information about an invoice file (electronic transaction file). [Figure 15] FIG. 15 is a diagram showing an example of an attachment file details screen for inputting detailed information about a receipt file (scanner-saved file). [Figure 16] FIG. 16 is a diagram showing an example of an attachment file details screen for inputting detailed information about the approval request file (other attachment file). [Figure 17] FIG. 17 is a diagram illustrating an example of a display item setting table. [Figure 18] FIG. 18 is a diagram showing an example of the attached file list screen that is displayed again. [Figure 19] FIG. 19 is a diagram showing an example of the generated supporting slip work. [Figure 20] FIG. 20 is a diagram showing an example of the slip entry screen that is displayed again. [Figure 21] FIG. 21 is a flowchart showing an example of the processing executed within the business system after the "Register" button on the re-displayed slip entry screen is pressed. [Figure 22] FIG. 22 is a diagram showing an example of obtaining a list of generated supporting voucher works and supporting vouchers. [Figure 23] FIG. 23 is a diagram showing an example of the generated voucher linking table. [Figure 24] FIG. 24 is a diagram showing an example of the evidence information table and the evidence image table generated when the system classification is "electronic transaction or scanner storage." [Figure 25] FIG. 25 is a diagram showing an example of the generated supporting slip work. [Figure 26] FIG. 26 shows an example of a workflow case table, a file information table, and a file image table that are generated when the system classification is "other attachments" and a workflow system is used. [Figure 27] FIG. 27 shows an example of a file information table and a file image table that are generated when the system classification is "other attachments" and the workflow system is not used. [Figure 28] FIG. 28 is a diagram illustrating an example of the generated journal entry detail table. [Figure 29] FIG. 29 shows an example of advance acquisition of information necessary for displaying the slip approval screen. [Figure 30] FIG. 30 shows an example of the slip approval screen when file A, which is a system requirements file, is selected. [Figure 31] FIG. 31 shows an example of the slip approval screen when file C, which is another attached file, is selected. [Figure 32]FIG. 32 is a diagram showing an example of items that can be displayed as detailed information of a voucher on the slip approval screen. [Figure 33] FIG. 33 is a diagram showing an example of a voucher information table to be searched. [Figure 34] FIG. 34 is a diagram showing an example of items that can be used as search conditions. [Figure 35] FIG. 35 is a diagram showing an example of items displayed as search results. [Figure 36] FIG. 36 is a diagram showing an example of the evidence search screen. [Figure 37] FIG. 37 is a diagram showing buttons and the like arranged in the footer section of the document search screen. [Figure 38] FIG. 38 is a diagram showing an example of the evidence information table in which the presence / absence of TS and the TS attachment date and time have been updated. DETAILED DESCRIPTION OF THE INVENTION

[0020] Hereinafter, embodiments of a file registration support device, a file registration support method, and a file registration support program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.

[0021] [1. Overview] When creating a voucher, it is sometimes necessary to attach supporting documents such as receipts or internal management files such as approval documents. In this case, supporting documents must be stored in accordance with the requirements of the Electronic Bookkeeping Act.

[0022] Here, a supporting document file is document data that certifies the content of a transaction. Examples of supporting documents include delivery notes, receipts, invoices, and estimates. Support files generated through electronic transactions (electronic transaction files) and support files generated through scanner storage (scanner-saved files) must meet the system requirements of the Electronic Books Preservation Act, and therefore belong to the category of "system requirement files."

[0023] In contrast, non-voucher files are document data for internal management. Examples of non-voucher files include approval documents. Non-voucher files do not need to meet the requirements of the Electronic Bookkeeping Act and are classified as "other attached files."

[0024] There are rules for storing system requirement files, so they must be stored in a different way from other attachments. In the past, to meet these rules, system requirement files and other attachments were uploaded to different storage locations from different screens.

[0025] However, when registering files from different screens, the following issues (1) and (2) occurred. (1) The user must determine which entry to attach depending on the type of file to upload, which may result in errors. (2) Uploading both the system requirements file and other attachments requires additional work.

[0026] There was also a request to be able to approve invoices by checking the file of the approval document that is the basis for the invoice, and the travel expense schedule file for business trip settlements. There was also a request to store all related documents linked to the journal entry.

[0027] Therefore, in this embodiment, for example, the following (1) to (4) are made possible. (1) It is now possible to register system requirement files (evidence files) that must be kept in accordance with system requirements and other attachment files (non-evidence files) that do not need to be kept in accordance with system requirements from the same screen. This reduces the amount of work required by the user. (2) Depending on the type of file being uploaded, the system will determine the fields that need to be entered for each system requirement and automatically display them on the screen, reducing the chance of errors by applicants. (3) It is now possible to search electronic transaction files and scanned files, which will reduce the cost of responding to tax audits, etc. (4) When approving a document, all supporting documents and other attachments linked to the document can be viewed from the same screen. This reduces the amount of work required by the user and also reduces the risk of misjudgment.

[0028] Please refer to the following for how to view and delete uploaded files.

[0029] This section explains how to view uploaded files. All uploaded files, including electronic transaction files, scanner-saved files, and other attached files, can be searched and viewed on the electronic evidence list, the slip screen for each business, and the workflow inquiry / approval screen. Note that the access method for other attached files differs depending on the business, and can also be controlled by each business.

[0030] This section explains how to delete files. Physical deletion of electronic transaction files and scanner-saved files is not permitted by law, and is therefore not possible. Other attachments can be physically deleted, or the database can be initialized. Deletion of other attachments can also be controlled by the respective business systems.

[0031] The specific configuration and operation will be described below.

[0032] [2. Configuration] An example of the configuration of a file registration 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 file registration support device 100.

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

[0034] The file registration support device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the file registration support device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0035] The communication interface unit 104 communicatively connects the file registration support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the file registration 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.

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

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

[0038] The memory unit 106 includes, for example, a screen control table 106a, a voucher type table 106b, a voucher slip work 106c as a work table, a voucher information table 106d, a voucher image table 106e, a voucher linking table 106f as a linking table, a workflow case table 106g, a file information table 106h, a file image table 106i, a journal entry details table 106j as a slip details table, and a display item setting table 106k.

[0039] The screen control table 106a, the evidence type table 106b, the evidence slip work 106c, the evidence information table 106d, and the evidence image table 106e are tables stored in the electronic bookkeeping system, while the evidence linking table 106f, the workflow case table 106g, the file information table 106h, the file image table 106i, and the journal entry detail table 106j are tables stored in each business system.

[0040] 5, screen control table 106a includes, for example, system identification data (system name) for identifying the system to which the slip input screen (described later) belongs, document type identification data (initial display document code) for identifying the document type, etc. In other words, screen control table 106a includes, for example, the name of the screen from which the attachment dialog box is called, and the document code that is initially set when the attachment dialog box is called from that screen.

[0041] As shown in FIG. 5, the document type table 106b includes, for example, the document type identification data (document code), document name, and date-related item name (transaction date label name).

[0042] The supporting document slip work 106c is a work table for temporarily storing information about files. As shown in FIG. 6, the supporting document slip work 106c includes, for example, a WK key (work key) for uniquely identifying a record in the supporting document slip work 106c, file identification data (support document GUID) for the attached file, a file type identification classification (regulation classification) for the type of the attached file, detailed information about the attached file entered on the attached file details screen described below (file name, extension, document code, receipt date, transaction date, amount, client name, product name, resolution, gradation, presence or absence of TS, TS assignment date and time, and originating system), and binary information about the attached file (file image). The document code column actually stores only a code. TS is an abbreviation for "timestamp."

[0043] The file type identification classification (regulatory classification) is broadly divided into a classification indicating the supporting document file (regulatory classification of "electronic transaction" or "scanner storage") and a classification indicating the non-supporting document file (regulatory classification of "other attachments"). The classification indicating the supporting document file is further divided into a classification indicating the electronic transaction file (regulatory classification of "electronic transaction") and a classification indicating the scanner storage file (regulatory classification of "scanner storage").

[0044] The binary information represents the attached file itself, and may be image information or information other than images. Examples of the binary information include PDF files with embedded images, email data, Excel format data, and Word format data.

[0045] The evidence information table 106d is a table for managing detailed information about the evidence file, and is generated from the evidence slip work 106c. As shown in Fig. 7, the evidence information table 106d includes, for example, the file identification data (evidence Guid), the file type identification classification (regulation classification), and detailed information about the attached file (file name, extension, document code, receipt date, transaction date, amount, customer name, product name, resolution, gradation, presence or absence of TS, TS attachment date and time, originating system, and deleted flag). Fig. 8 shows a table with an explanation of each item included in the evidence information table 106d.

[0046] The evidence image table 106e is a table for managing binary information about the evidence file, and is generated from the evidence slip work 106c. As shown in Fig. 7, the evidence image table 106e includes, for example, the file identification data (evidence Guid) and binary information about the attached file (file image).

[0047] The supporting evidence linking table 106f is a table for linking vouchers with attached files. In the case of an accounting system, the "attached files" include both the system requirement file and the other attached files. As shown in FIG. 9, the supporting evidence linking table 106f includes, for example, a voucher number for identifying a registered voucher, the file identification data (electronic supporting evidence GUID) in the supporting evidence voucher work 106c, and the file type identification classification (system classification) in the supporting evidence voucher work 106c, all linked together.

[0048] As shown in FIG. 10, the workflow case table 106g includes, for example, case identification data (case Guid) for identifying each case on the workflow, the approval status, the name of the applying employee, the slip number (business slip number), and the like.

[0049] The file information table 106h is a table for managing detailed information about the non-voucher files, and is generated from the voucher slip work 106c. As shown in Fig. 10, the file information table 106h includes, for example, the case identification data (case Guid) and detailed information about the attached file (attached file name and memo).

[0050] The file image table 106i is a table for managing binary information about the non-voucher files, and is generated from the voucher slip work 106c. As shown in Fig. 10, the file image table 106i includes, for example, the case identification data (case Guid) and binary information (file image) about the attached file.

[0051] As shown in Figure 9, the journal details table 106j includes, for example, the voucher number, the case identification data (case Guid), and the contents of the voucher (debit account item and debit amount) entered on the voucher input screen described below.

[0052] The display item setting table 106k includes a list of items to be displayed on the attachment details screen (described later) for each file type, as shown in Fig. 17. In the example of Fig. 17, items marked with "◯" are items to be displayed on the attachment details screen, and items marked with "X" are items not to be displayed on the attachment details screen.

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

[0054] The control unit 102 has, in terms of functional concept, for example: (1) an attachment file list screen display unit 102a as attachment file list screen display means for displaying an attachment file list screen, which is a screen for attaching a file, when a button for attaching a file is selected on a slip input screen, which is a screen for inputting the contents of a slip; (2) an attachment file detail screen display unit 102b as attachment file detail screen display means for displaying an attachment file detail screen, which is a screen for inputting detailed information about a file to be attached to a slip, including an image of the attached file and an area for inputting detailed information about the attached file, when a file is attached on the attachment file list screen; and (3) a work table is generated that includes, when a button for registering an attached file is selected on the attachment file list screen that is displayed again, file identification data for the attached file, file type identification classification for the type of the attached file, detailed information about the attached file input on the attachment file detail screen, and binary information about the attached file. (4) when a button for registering an attached file is selected on the attached file list screen that is displayed again, the slip input screen is displayed again, and when a button for registering a slip is selected on the re-displayed slip input screen, (i) a linking table that links a slip number for identifying the registered slip with the file identification data in the work table, (ii) when the file type identification category in the work table is a category that indicates the evidence file, a evidence information table that includes the file identification data in the work table, the file type identification category, and detailed information about the attached file, and a evidence image table that includes the file identification data in the work table and binary information about the attached file, and (iii) when the file type identification category in the work table is a category that indicates the non-evidence file, a workflow case table that includes the slip number and case identification data for identifying each case on the workflow.a linking table etc. generating unit 102d as linking table etc. generating means for generating (i) a file information table including the case identification data and detailed information about the attached file in the work table, a file image table including the case identification data and binary information about the attached file in the work table, and (ii) a slip detail table including the slip number and the content of the slip entered on the slip input screen; and (5) when a slip approval screen which is a screen for a person in charge to approve the slip is launched, the unit 102d obtains the content of the slip linked to the slip number in the workflow case table from the slip detail table, and if a voucher linked to the case is registered in the linking table, the unit 102d obtains the file identification data linked to the voucher number in the workflow case table from the linking table, and further obtains detailed information and binary information linked to the obtained file identification data from the voucher information table and the voucher image table, respectively, and enters the file information table. (6) an approval information display unit 102e as approval information display means for displaying information for approval, which, when a search condition is entered on a voucher search screen, which is a screen for searching for voucher files, searches the voucher information table for information about the voucher file that matches the entered search condition, and displays the search result on the voucher search screen. The system also includes: (i) an approval information display unit 102f as evidence search result display means for displaying information for approval, which, when a search condition is entered on a voucher search screen, which is a screen for searching for voucher files, searches the voucher information table for information about the voucher file that matches the entered search condition, and displays the search result on the voucher search screen. The processing executed by each unit will be described in detail in [4. Specific Example of Processing] below.

[0055] [3. Processing Overview] In this section, an overview of the processing according to this embodiment will be described.

[0056] [3-1. Overall overview] An overview of the processing flow according to this embodiment is shown in Fig. 2. As shown in Fig. 2, the key point of this embodiment is that even if the file types are different, files can be registered from a common upload screen (attachment file list screen and attachment file details screen).

[0057] [3-2. Overview of each system category] An overview of the processing flow when the system classification is "electronic transaction" or "scanner storage" is shown in Figure 3. When the system classification is "electronic transaction" or "scanner storage", as shown in Figure 3, a voucher information table 106d and a voucher image table 106e are generated as tables for storing information on voucher files.

[0058] An overview of the processing flow when the system classification is "other attachments" and a workflow is used is shown in Figure 4. When the system classification is "other attachments" and a workflow is used, a file information table 106h and a file image table 106i are generated as tables for storing information on non-voucher files.

[0059] Here, in this embodiment, as shown in Figures 3 and 4, the key point is that even if the file's system classification is different, files can be registered using the same flow: journal entry input screen → attachment list screen and attachment details screen → journal entry input screen.

[0060] In Figures 3 and 4, the characters marked with * indicate the corresponding relationship with the following [4-1. Operational Image]. For example, a specific example of the processing at the point marked with "*Operational Image (3)-D" in Figure 3 is described in (3)-D of [4-1. Operational Image].

[0061] [3-3. Electronic bookkeeping systems and business systems] In this embodiment, supporting documents files can be stored in an electronic bookkeeping system, which is a dedicated database separate from the regular business database, to meet the requirements of the Electronic Bookkeeping Act. This allows for complete separation of processing between the electronic bookkeeping system that stores supporting documents files and the regular business system that stores non-supporting documents files. The system is characterized by the ability to process documents collectively in the same database and by using a single database to unify the handling of logical deletion within the same database. The following describes the characteristics of the processing or management performed by each system.

[0062] (Electronic bookkeeping system) - It is possible to add a timestamp, which prevents unauthorized persons from falsifying the data and also makes it possible to detect whether or not the data has been falsified. · Physical deletion of evidence is not possible. Also, timestamp attachments can be consolidated into one database (not distributed across business databases). Because it is a separate database, it can be encrypted in the database settings. Also, the database can be backed up separately (this does not include the requirement to secure the database access rights). As explained in [4-3] below, it is possible to search for supporting documents that meet the search requirements of the Electronic Bookkeeping Act.

[0063] (Normal business system) No timestamp is added. Attachments can be physically deleted and the database can be initialized. The search method differs depending on the business system. There are also business systems that do not allow file searches. In the case of a workflow system, you can refer to files using "File Attachment Specification.Query", but you cannot search for individual files.

[0064] [4. Specific examples of processing] In this section, a specific example of the processing according to this embodiment will be described.

[0065] [4-1. Operation image] This section explains how to launch the screen. Note that this section explains how to register a file using the accounting system's "journal entry input" as an example, but it is possible to register files in a similar way in other business systems.

[0066] (1) Calling the attachment dialog from the business system First, when the button for attaching a file (the "Attach" button) is selected on the slip entry screen (see FIG. 11), which is a screen for entering the contents of a slip, the attachment list screen display unit 102a displays the attachment list screen (see FIG. 13), which is a screen for attaching a file. Displaying the attachment list screen is, in other words, the launch of the attachment dialog box.

[0067] Here, the attachment file list screen display unit 102a displays the attachment file list screen in accordance with the argument of the dialog call shown in Fig. 12. Note the following points regarding the argument of the dialog call. When you call a dialog at the source of a transition, you can pass the items you want to initially set to the dialog as arguments. You can also make those items read-only. The read-only flag prevents changes to the amount, etc., after final approval or when viewing in reference mode from a job. The originating system is used to set the upper limit of files that can be uploaded and to uniquely identify the supporting document in [4-3]. The originating system is set in advance as an argument when the dialog is called.

[0068] (2) Launching and registering the attachment dialog (2-1) Step 1: Select the file you want to attach on the attachment list screen Next, the file to be attached is selected from the attachment file list screen (see FIG. 13). There are four methods for attaching a file:

[0069] The first method is to select the file you want to attach by pressing the "Select from Explorer" button in Figure 13. The second method is to drag and drop the file you want to attach onto the "You can drag and drop files here" section in Figure 13.

[0070] The third method is to upload a file taken with a mobile phone by pressing the "Select from a file taken with a document" button in Figure 13. With this method, you can not only apply directly from the mobile phone using an image taken with a mobile phone, but also import it from an in-house PC.

[0071] The fourth method is to click the "Select from previously uploaded files" button in Figure 13 and re-attach a file that was deleted after being registered in the electronic bookkeeping system. This method makes it possible to re-link a voucher that has been logically deleted from the voucher information table 106d to a slip and upload it.

[0072] Once the file attachment is complete, you will be taken to the attachment details screen.

[0073] (2-2) Step 2: Enter detailed information about the attachment on the attachment details screen When a file is attached on the attachment list screen (see Figure 13), the attachment details screen display unit 102b displays the attachment details screen (see Figures 14 to 16), which is a screen for entering detailed information about the file to be attached to the slip, including an image of the attached file and an area for entering detailed information about the attached file.

[0074] Fig. 14 shows the attachment details screen for inputting detailed information about an invoice file (electronic transaction file). Fig. 15 shows the attachment details screen for inputting detailed information about a receipt file (scanner-saved file). Fig. 16 shows the attachment details screen for inputting detailed information about a request for approval file (other attachment file).

[0075] Here, the attachment details screen display unit 102b displays a list of items on the attachment details screen (see Figures 14 to 16) according to the type of attached file selected on the attachment details screen, and for some of the displayed items, if the contents of the voucher were entered on the voucher input screen before the attachment list screen was displayed, the contents of the voucher entered on the voucher input screen (see Figure 11) are displayed as the item values.

[0076] As described in the previous paragraph, the attachment details screen display unit 102b may acquire a list of items corresponding to the type of attached file selected on the attachment details screen (see FIGS. 14 to 16) according to a fixed rule, or may acquire the list by referring to the display item setting table 106k (see FIG. 17), as will be described below. That is, the attachment details screen display unit 102b may acquire a list of items corresponding to the type of attached file selected on the attachment details screen from the display item setting table 106k (see FIG. 17), which includes a list of items to be displayed on the attachment details screen for each file type.

[0077] Specifically, when a file type (=regulation classification) is selected from the "Please select the file type" section in the upper right corner of the attachment details screen (see FIGS. 14 to 16), the attachment details screen display unit 102b acquires items corresponding to the selected regulation classification from the display item setting table 106k (see FIG. 17) to switch between displaying and hiding input items. If a value is set in the "dialog call argument" described in (1) in the business system, the attachment details screen display unit 102b launches the attachment details screen (see FIGS. 14 to 16) with the items set.

[0078] Note that the following points should be noted regarding the display of the attachment details screen performed by the attachment details screen display unit 102b. The attachment details screen (see Figures 14 to 16) is launched with the items passed from the slip input screen (see Figure 11) initially set. What is set can be set by the business system. For example, in the case of a travel expense settlement application in a travel expense system, if there is a requirement to attach supporting documents for each item, parameters can be set for each item. On the same screen, you can select whether to upload a system requirements file or other attachments and upload the file. The input items will automatically change depending on the selected system category. In other words, the system will guide you so that you can enter items that meet the system requirements. For information on displaying or hiding items for each system category, please refer to the display item setting table 106k (see Figure 17).

[0079] Here, the attachment details screen display unit 102b obtains, from the screen control table 106a (see FIG. 14), document type identification data (initial display document code) linked to system identification data (system name) for the system to which the slip input screen (see FIG. 11) on which the slip contents have been entered belongs. Next, the attachment details screen display unit 102b obtains, from the voucher type table 106b (see FIG. 14), the document name and date-related item name (transaction date label name) linked to the obtained document type identification data (document code). Finally, the attachment details screen display unit 102b displays the obtained document name and date-related item name (transaction date label name).

[0080] The display of the document name and the item name related to the date (transaction date label name) performed by the attachment details screen display unit 102b is specifically as follows. Document names are managed by the screen control table 106a (see FIG. 14). The document name that is initially displayed can be set for each screen that is called. For example, as shown in the screen control table 106a (see FIG. 14), when the application is started from journal entry input, the document code of the delivery note is obtained, and when the application is started from transportation expense settlement, the document code of the receipt is obtained. The "Date" label name can be set for each document code to be initially displayed in the Voucher Type Table 106b (see FIG. 14). This function is provided because the concept of "transaction date" differs for each document. For example, as shown in the Voucher Type Table 106b (see FIG. 14), if the document is a "delivery note," the transaction date label name will be "Date," and if the document is a "receipt," the transaction date label name will be "Receipt Date." When a specific document code is selected by the user on the attachment details screen, the selected document code is searched for in the evidence type table 106b (see Figure 14), and the document name corresponding to the document code found in the search can be displayed on the attachment details screen.

[0081] Once you have completed entering the information, click the "Register" button. If multiple files are selected, the screen will switch to the input screen for the next file.

[0082] As explained above in (2-1) and (2-2), the file registration support device 100 according to this embodiment can support the registration of evidence files and non-evidence files from the same screen. In this example, evidence files are invoice files (electronic transaction files) and receipt files (scanner-saved files). In this example, non-evidence files are approval request form files (other attachment files). In this example, the same screen is the attachment file list screen (see FIG. 13) and the attachment file details screen (see FIGS. 14 to 16).

[0083] (2-3) Step 3: Return to the attachment list screen and confirm that the attached file and its system classification are correct. After information is entered on the attachment details screen (see Figures 14 to 16), when the button for registering the attached file (the "Register" button) is selected on the attachment details screen (see Figures 14 to 16), the attachment list screen display unit 102a re-displays the attachment list screen (see Figure 18) including a list of the attached files and the corresponding file types.

[0084] Specifically, when the registration of all selected attachments is completed on the attachment details screen (see FIGS. 14 to 16), the screen returns to the attachment list screen. On the returned attachment list screen, the attached files and their corresponding file types (=system classification) can be confirmed. When the attachment list screen is closed, the screen returns to the screen of the business system from which the transition originated.

[0085] In this specification, the term "display again" can be broadly understood and includes any of the following cases. - When the original screen is temporarily hidden, transitioning to the next screen, and then returning to the original screen from the next screen, the original screen is redisplayed. When the next screen is displayed as a pop-up on top of the original screen, and the original screen becomes active when the next screen is closed. In this case, the information added to the next screen may be displayed on the original screen, or the original screen may simply be made active without displaying the information added to the next screen on the original screen.

[0086] When the button for registering the attached file ("Register" button) is selected on the redisplayed attachment file list screen (see FIG. 18), the work table generation unit 102c generates a voucher voucher work 106c (see FIG. 19) containing file identification data (evidence Guid) for the attached file, file type identification classification (regulation classification) for the attached file, detailed information about the attached file (file name, extension, document code, receipt date, transaction date, business partner name, amount, product name, resolution, gradation, TS presence / absence, TS attachment date and time, and originating system) entered on the attachment file details screen (see FIGS. 14 to 16), and binary information (file image) about the attached file. The work table generation unit 102c also stores the same WK key (work key) in the voucher voucher work 106c.

[0087] Specifically, when registration is performed in the attachment dialog, detailed information and a file image of the attached voucher are stored in the voucher slip work 106c. When storage is complete, the screen returns to the business system screen from which the transition originated. The items stored differ depending on the radio button selected on the attachment details screen (see Figures 14 to 16). In other words, the columns in the voucher slip work 106c that are updated differ depending on the system classification selected on the attachment details screen (see Figures 14 to 16). For example, if a scanner-saved file is selected, information is stored in the resolution and gradation columns.

[0088] (3) Voucher registration at the calling system (business system) When the button for registering the attached file (the "Register" button) is selected on the re-displayed attachment file list screen (see FIG. 18), the linking table etc. generation unit 102d re-displays the slip input screen (see FIG. 20). Then, when the button for registering the slip (the "Register" button) is selected on the re-displayed slip input screen (see FIG. 20), the linking table etc. generation unit 102d starts generating each piece of data (corresponding to "Start" in the flowchart in FIG. 21).

[0089] The type of data generated differs depending on the system classification selected on the attachment details screen (see Figs. 14 to 16) (= the storage location of the information in the supporting document voucher work 106c differs). Below, each piece of data generated by the linking table etc. generation unit 102d will be explained with reference to the flowchart in Fig. 21. Fig. 21 is a flowchart showing the processing executed within the business system after the "Register" button is pressed on the voucher input screen (see Fig. 20) that is displayed again.

[0090] (3)-A. Obtaining a list of supporting documents registered in the attachment dialog First, as shown in Figure 22, the linking table etc. generation unit 102d uses common processing of the electronic bookkeeping system to obtain the file identification data (evidence Guid) and the file type identification classification (regulation classification) as information necessary for generating the evidence linking table 106f from the evidence voucher work 106c, which is a temporary table registered in the attachment dialog (corresponding to the processing of "A" in the flowchart of Figure 21).

[0091] (3)-B. Creation of the evidence linking table 106f Next, the linking table etc. generating unit 102d generates a voucher linking table 106f (see FIG. 23) that includes a voucher number for identifying the registered voucher, the file identification data (voucher Guid) in the voucher voucher work 106c, etc., in a linked manner (corresponding to the process of "B" in the flowchart of FIG. 21). Note that the linking table etc. generating unit 102d may further include the file type identification classification (regulation classification) in the voucher voucher work 106c in the voucher linking table 106f (see FIG. 23).

[0092] In the voucher linking table 106f shown in Figure 23, three files are linked to one voucher identified by the voucher number "Zaimu100": a delivery note file (Voucher Guid: Guid_Evi01), a receipt file (Voucher Guid: Guid_Evi02), and a request form file (Voucher Guid: Guid_Evi03).

[0093] Note that the following points should be noted regarding the generation of the voucher linking table 106f performed by the linking table etc. generating unit 102d. On the business system side, the linking information is updated in the evidence linking table 106f of the business system DB (this update is delegated to the business side). Here, the slip in the business system and the electronic evidence are linked. · Using the electronic evidence Guid as a key, link the document number in the business system with the electronic evidence registered in the attachment dialog. Updating of the supporting documents linking table 106f is delegated to each business system. For this reason, the information held in the supporting documents linking table 106f may differ depending on each business system. For example, the accounting system may also update "other attached files", while the travel expense system may not update "other attached files". This is to allow for flexibility, as each business system differs in where and how it stores "other attached files" in the database.

[0094] (3)-C. Check the system classification Next, the linking table etc. generating unit 102d checks the type of the file type identification division (regulation division) in the supporting document slip work 106c (corresponding to the process of "C" in the flowchart of FIG. 21).

[0095] 19, the record on the first line (regime classification: electronic transaction) and the record on the second line (regime classification: scanner storage) correspond to the records in the regulatory requirements file. In this case, the linking table etc. generating unit 102d generates the voucher information table 106d and the voucher image table 106e based on the records on the first and second lines in the voucher voucher work 106c, as described in (3)-D below.

[0096] 19, the record on the third line (registry classification: other attachments) corresponds to the record of the other attachments. In this case, the linking table etc. generation unit 102d generates the workflow case table 106g, the file information table 106h, and the file image table 106i based on the record on the third line in the voucher voucher work 106c, as will be described in (3)-F below, or generates the file information table 106h and the file image table 106i, as will be described in (3)-G below.

[0097] (3)-D. System classification = Electronic transaction or scanner storage The linking table etc. generating unit 102d, when the file type identification category (regulation category) in the supporting document slip work 106c (see FIG. 19) is a category (electronic transaction or scanner storage) indicating the supporting document file (when proceeding to the regulatory requirement file (electronic transaction or scanner storage) at C in the flowchart of FIG. 21), a voucher information table 106d (see FIG. 24) including the file identification data (voucher Guid) in the voucher slip work 106c (see FIG. 19), the file type identification classification (regulation classification) in the voucher slip work 106c (see FIG. 19), and detailed information about the attached file in the voucher slip work 106c (see FIG. 19) (file name, extension, document code, receipt date, transaction date, amount, product name, business partner name, resolution, gradation, TS presence / absence, TS attachment date / time, originating system, and deleted flag); A voucher image table 106e (see FIG. 24) containing the file identification data (voucher Guid) in the voucher slip work 106c (see FIG. 19) and binary information (file image) about the attached file in the voucher slip work 106c (see FIG. 19); (corresponding to the process "D" in the flowchart of FIG. 21).

[0098] Note that the following points should be noted regarding the generation of the evidence information table 106d and the evidence image table 106e performed by the linking table etc. generating unit 102d. · Execute common processing for the electronic bookkeeping system (electronic document confirmation processing). The evidence information table 106d and the evidence image table 106e are updated. In addition, the data in the evidence slip work 106c is deleted. The relevant data is acquired using the "WK key" registered in the temporary table, the voucher slip work 106c, as a key, and the information is updated in each table (the voucher information table 106d and the voucher image table 106e). The columns in the evidence information table 106d that are updated vary depending on the system classification. For example, when a scanner-saved file is selected, information is stored in the columns for resolution and gradation.

[0099] (3)-E. Check whether to use a workflow system If the file type identification category (regulation category) in the supporting document voucher work 106c (see FIG. 19) is a category indicating the non-supporting document file (other attachments), the linking table etc. generation unit 102d further checks whether or not a workflow system is used (corresponding to the process of "E" in the flowchart of FIG. 21). This is because the storage location and storage method of other files differ depending on whether each business system uses a workflow system or not. All updates of other files are delegated to the business system. Each business system stores file images etc. obtained by common processing in the electronic bookkeeping system. FIG. 25 shows the supporting document voucher work 106c, which is the update source table.

[0100] (3)-F. System classification = Other attachments and when using a workflow system The linking table etc. generating unit 102d determines whether the file type identification category (regulation category) in the supporting document slip work 106c (see FIG. 19) is a category (other attachments) indicating the non-supporting document file (when proceeding to "other attachments" in C in the flowchart of FIG. 21), and when using a workflow system (when proceeding to "Use" in E in the flowchart of FIG. 21), ● A workflow case table 106g (see FIG. 26) including the slip number (business slip number), the case identification data (case Guid), etc.; A file information table 106h (see FIG. 26) containing the case identification data (case Guid) and detailed information (attached file name and memo) about the attached file in the supporting document slip work 106c (see FIG. 19); a file image table 106i (see FIG. 26) containing the case identification data (case Guid) and binary information (file image) about the attached file in the supporting document slip work 106c (see FIG. 19); (corresponding to the process "F" in the flowchart of FIG. 21).

[0101] Note that the following points should be noted regarding the generation of the workflow case table 106g, the file information table 106h, and the file image table 106i performed by the linking table etc. generating unit 102d. · By executing common processing of the workflow system, information linking other attachments and documents is saved. -By using the workflow system, it is possible to simultaneously view documents and other attachments during approval.

[0102] (3)-G. System classification = Other attachments and when the workflow system is not used (when attachments are saved independently for business purposes) The linking table etc. generating unit 102d determines whether the file type identification category (regulation category) in the supporting document slip work 106c (see FIG. 19) is a category (other attachments) indicating the non-supporting document file (when proceeding to "other attachments" in C in the flowchart of FIG. 21), and if the workflow system is not being used (when proceeding to "not used" in E in the flowchart of FIG. 21), a file information table 106h (see FIG. 27) containing the voucher number and detailed information (attached file name and memo) about the attached file in the supporting voucher work 106c (see FIG. 19); a file image table 106i (see FIG. 27) containing the slip number and binary information (file image) about the attached file in the supporting slip work 106c (see FIG. 19); (corresponding to the process "G" in the flowchart of FIG. 21).

[0103] Note that the following points should be noted regarding the generation of the file information table 106h and the file image table 106i performed by the linking table etc. generating unit 102d. Each business system stores file images and other data obtained through common processing in the electronic bookkeeping system. In this example, the values ​​for the accounting system used in the explanation so far are listed.

[0104] (3)-H.Generating journal entry details table Finally, the linking table etc. generating unit 102d generates a journal entry detail table 106j (see FIG. 28) that includes the voucher number and the contents of the voucher entered on the voucher input screen (see FIG. 20) (corresponding to the process of "H" in the flowchart of FIG. 21). In other words, the voucher is confirmed by the voucher registration process of each business system.

[0105] By performing the processing described in this section (3) above, the linking table etc. generating unit 102d completes the generation of each piece of data (corresponding to "end" in the flowchart of FIG. 21).

[0106] As explained in section (3), the file registration support device 100 according to this embodiment allows voucher files and non-voucher files to be stored in different locations. That is, information about voucher files is stored in the voucher information table 106d and the voucher image table 106e, while information about non-voucher files can be stored in the workflow case table 106g, the file information table 106h, and the file image table 106i. Storing voucher files and non-voucher files in different locations in this way has the effect of facilitating the approval of slips, as described in [4-2] below, and the search for vouchers, as described in [4-3] below.

[0107] [4-2. Approval of invoices] This section explains the approval of invoices. When using workflow, when approving an invoice, all supporting documents and other files linked to the invoice can be viewed from the same screen. The information that can be viewed is as follows: · Contents of the slip File image of supporting documents linked to the slip Detailed information related to the supporting document (the information entered on the attachment details screen when uploading the supporting document) File images of other attachments linked to the slip

[0108] Here, since the information to be displayed must be acquired in advance in order to display it when approving a slip, we will first explain how to acquire the information to be displayed. When the slip approval screen, which is the screen for the person in charge to approve the slip, is launched, the approval information display unit 102e acquires information in advance as follows.

[0109] As shown in FIG. 29, the approval information display unit 102e acquires the contents of the voucher (debit account title, debit amount, etc.) linked to the voucher number in the workflow case table 106g from the journalization details table 106j.

[0110] In addition, when a voucher linked to a case is registered in the voucher linking table 106f, the approval information display unit 102e obtains the file identification data (voucher Guid) linked to the slip number in the workflow case table 106g from the voucher linking table 106f, as shown in Figure 29, and further obtains detailed information (file name, extension, document code, receipt date, etc.) and binary information (file image) linked to the obtained file identification data (voucher Guid) from the voucher information table 106d and the voucher image table 106e, respectively.

[0111] Then, if other files linked to the case are registered in the file information table 106h, the approval information display unit 102e obtains binary information (file image) linked to the case identification data (voucher Guid) in the workflow case table 106g from the file image table 106i, as shown in Figure 29.

[0112] Note that the following points should be noted regarding the advance acquisition of information performed by the approval information display unit 102e. The journal entry details table 106j and the supporting document linking table 106f are referenced from the workflow case table 106g. The information on the supporting documents is obtained from the supporting document linking table 106f by the supporting document obtaining process of the electronic bookkeeping system, which is referenced in the common process of the workflow. - Other attachment information is obtained based on the workflow's case Guid.

[0113] The approval information display unit 102e then displays the acquired information on the slip approval screen in the following manner.

[0114] If the file selected on the voucher approval screen is the supporting document file (regulatory requirements file), the approval information display unit 102e displays the contents of the acquired voucher, detailed information acquired from the supporting document information table 106d, and binary information acquired from the supporting document image table 106e on the voucher approval screen.

[0115] This display will be explained in detail using Figure 30. Figure 30 is a diagram showing the voucher approval screen when the cursor is placed on the "File A.pdf" button. As shown in Figure 30, when File A, which is a system requirements file, is selected at the top of the screen, the approval information display unit 102e displays a "Journal Entry Voucher Confirmation" area on the left side of the screen as the contents of the voucher, an area including the document name, etc. on the right side of the screen as the detailed information, and an image of the delivery note in the center of the screen as the binary information. Note that items that can be displayed as the detailed information are summarized in Figure 32.

[0116] On the other hand, if the file selected on the invoice approval screen is the non-voucher file (other attached file), the approval information display unit 102e displays the contents of the acquired invoice and the binary information acquired from the file image table 106i on the invoice approval screen.

[0117] This display will be explained in detail using Figure 31. Figure 31 is a diagram showing the voucher approval screen when the cursor is placed on the "File C.pdf" button. As shown in Figure 31, when File C, which is an additional attachment, is selected at the top of the screen, the approval information display unit 102e displays the "Journal Entry Voucher Confirmation" area on the left side of the screen as the contents of the voucher, and displays an image of the approval request form on the right side of the screen as the binary information, as shown in Figure 31.

[0118] Note the following points regarding the display of the slip approval screen by the approval information display unit 102e. At the top of the invoice approval screen, all attached files (system requirements files and other attached files) linked to the invoice are displayed as a list of file buttons. By clicking the displayed file button, you can download the attached files. By hovering the cursor over one of the file buttons displayed at the top of the document approval screen, you can automatically switch the attachment to be previewed. Note that if you hover the cursor over the file button for the system requirements file, the detailed information will also change.

[0119] As explained above in section [4-2], the file registration support device 100 according to this embodiment can display, at the time of approving a voucher, the contents of the voucher (in this example, the contents of the "Journal Entry Voucher Confirmation"), an image of the supporting document linked to the voucher (in this example, an image of the delivery note), detailed information on the supporting document linked to the voucher (in this example, detailed information on the delivery note), and an image of the non-supporting document linked to the voucher (in this example, an image of the approval request form) on a single screen (in this example, the voucher approval screen). This allows the person in charge of approval to approve the voucher after accurately and immediately checking a series of information related to the voucher, thereby reducing the burden on the person in charge of approval and eliminating mistakes in the approval process.

[0120] [4-3. Search for evidence (display list of electronic evidence)] This section explains how to search for supporting documents (displaying a list of electronic supporting documents). By searching for supporting documents, you can view all supporting documents stored in the electronic bookkeeping system. The list of electronic supporting documents has two jobs: one for the person in question and one for the accounting staff.

[0121] In the personal section, users can search, view, and logically delete the vouchers they have uploaded. In addition, users can also register new electronic transaction files that are not linked to vouchers.

[0122] The accountant's account is used for responding to tax audits, periodic inspections, and daily checks. In addition, the accountant's account allows all users to search, view, and logically delete uploaded supporting documents.

[0123] The evidence data obtained from the electronic evidence list is obtained from the electronic ledger storage DB. While slip data is distributed across each business system, evidence data is consolidated in the electronic ledger storage DB. Therefore, by searching for evidence (displaying the electronic evidence list), it is possible to search and view evidence uploaded from all business systems.

[0124] Here, the search requirements of the Electronic Bookkeeping Act include the following (1) to (3). (1) You can search by "transaction date (or other date)," "transaction amount," and "transaction partner." (2) You can search by specifying a date or amount range. (3) The ability to search by combining two or more items. However, if you comply with a request for download, conditions (2) and (3) are not required.

[0125] Below, a specific description will be given of the search for evidence performed from the evidence search screen (see FIG. 36), which is a screen for searching for the evidence file, assuming the following conditions. Assume that the evidence information table 106d shown in Figure 33 exists as the search target. The evidence information table 106d shown in Figure 33 is a table to which files are uploaded not only from the core accounting system, but also from the travel expense system and the sales system. As shown in Figure 33, a scanned file is uploaded from the travel expense system (record with evidence Guid: Guid_Evi03), and an electronic transaction file is uploaded from the sales system (record with evidence Guid: Guid_Evi04). Items that can be used as search conditions are, for example, as shown in Fig. 34. Search conditions can be entered in the area on the left side of the document search screen (see Fig. 36). Items displayed as search results are, for example, as shown in Fig. 35. The search results are displayed in the area on the right side of the voucher search screen (see Fig. 36).

[0126] When search conditions are entered on the evidence search screen (see Figure 36), the evidence search result display unit 102f searches the evidence information table 106d for information about the evidence file that matches the entered search conditions and displays the search results on the evidence search screen (see Figure 36).

[0127] Note that the following points should be noted regarding the search for evidence performed by the evidence search result display unit 102f. By entering search conditions in the area on the left side of the document search screen (see Figure 36), it is possible to search (extract) document documents using the details registered at the time of application. By being able to search for document documents in this way, the search requirements of the Electronic Bookkeeping Act can be met. In the right area of ​​the document search screen (see Figure 36), the item details displayed as search results are controlled according to the selected system category. For details on controlling the displayed item details, see Figure 35. In [4-1], we explained an example of registering supporting documents from the core accounting system, but as explained in this section [4-3], if supporting documents are registered from other systems (in this example, the travel expense system and sales system), it is possible to search and view the supporting documents registered from those other systems.

[0128] Here, the buttons arranged in the footer section (lower section) of the voucher search screen (see Fig. 36) will be described. Fig. 37 shows an enlarged view of the buttons arranged in the footer section (lower section).

[0129] The "Add Evidence" button is a button for directly uploading an electronic transaction file to the electronic bookkeeping system without linking it to a slip. When the "Add Evidence" button is pressed, the screen transitions to the attachment list screen and the attachment details screen.

[0130] The "Delete" button is used to logically delete the evidence. Logical deletion means treating the data as deleted rather than physically deleting it. When logical deletion is performed, the "Deleted Flag" in the evidence information table 106d is updated from "False" to "True," as shown in Figure 37. A record whose "Deleted Flag" has been updated to "True" is treated as deleted, but the record itself does not disappear.

[0131] The "Details" button is a button for viewing detailed information about the selected evidence (the values ​​entered on the attachment details screen). When the "Details" button is pressed, the attachment details screen is launched in read-only mode.

[0132] As explained above in this section [4-3], the file registration support device 100 according to this embodiment can search for evidence and display the search results. This allows the person who registered the evidence to efficiently refer to the evidence they registered. The administrator can efficiently perform periodic inspections and daily checks, and can also respond quickly to tax audits.

[0133] Furthermore, as explained in this section [4-3], the file registration support device 100 according to this embodiment can search for the desired voucher from the voucher information table 106d, which aggregates vouchers registered from multiple systems (in this example, including not only the core accounting system but also the travel expense system and the sales system), thereby enabling a comprehensive and thorough search of all registered vouchers.

[0134] [4-4. Adding a timestamp] This section explains how to assign a timestamp. When a timestamp is assigned, the presence / absence of a timestamp (TS presence / absence) and the timestamp assignment date / time (TS assignment date / time) in the evidence information table 106d are updated as shown in Fig. 38. By collecting evidence in the electronic bookkeeping system, it is possible to use a predetermined authenticated timestamp service.

[0135] [5. 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.

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

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

[0138] 6. 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.

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

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

[0141] Furthermore, with regard to the file registration support device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0142] For example, all or any part of the processing functions of the file registration 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 file registration support device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0143] This computer program may also be stored in an application program server connected to file registration support device 100 via any network, and all or part of it may be downloaded as needed.

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

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

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

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

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

[0149] The present invention is useful, for example, in fields related to accounting and fields that use subsidiary ledgers. [Explanation of symbols]

[0150] 100 File registration support device 102 Control section 102a Attachment list screen display section 102b Attachment details screen display section 102c Worktable generation unit 102d Linking table generation unit 102e Approval information display section 102f Voucher search results display section 104 Communication interface unit 106 Storage section 106a Screen Control Table 106b Evidence type table 106c Voucher Work 106d Evidence Information Table 106e Evidence Image Table 106f Evidence linking table 106g Workflow Case Table 106h File Information Table 106i File Image Table 106j Journal Entry Detail Table 106k display item setting table 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

[Claim 1] A file registration support device having a control unit that can support the registration of evidence files and non-evidence files from the same screen, The control unit an attachment file list screen display means for displaying an attachment file list screen, which is a screen for attaching files, when a button for attaching a file is selected on a slip input screen, which is a screen for inputting the contents of a slip; an attachment file details screen display means for displaying an attachment file details screen, which is a screen for inputting detailed information about a file to be attached to a slip, including an image of the attached file and an area for inputting detailed information about the attached file, when a file is attached on the attachment file list screen; Equipped with the attachment details screen display means displays a list of items corresponding to the type of attached file selected on the attachment details screen on the attachment details screen, and for some of the displayed items, if the contents of a slip have been input on the slip input screen before the attachment list screen is displayed, the contents of the slip input on the slip input screen are displayed in a state where they are set as item values; A file registration support device characterized by the above.

Images