JP7704807B2 - File registration support device, file registration support method and file registration support program - Google Patents

Description

The present invention relates to a file registration support device, a file registration support method, and a file registration support program.

Patent document 1, paragraph 0006, states, "However, in order to digitize and store a large number of supporting documents using a scanner, and to make journal entries or prepare expense reimbursement application documents based on these supporting documents, the work of matching the journal entries or expense reimbursement application documents with the supporting documents is necessary, which is cumbersome." Furthermore, patent document 1, paragraph 0007, states, "Therefore, the present invention aims to provide a supporting document processing system and method that enable the efficiency of accounting processing based on supporting documents."

JP 2018-116602 A

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 that corresponds to the voucher but also the approval document that corresponds to the voucher.

However, conventionally, evidential files and non-evidential files 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 the user would launch the wrong screen and register the file in the wrong registration destination (for example, registering a evidential file in the registration destination for a non-evidential file).

In addition, if users wanted to register both supporting and non-supporting files, they had to register them from separate screens, which placed a heavy workload on the user.

The present invention has been made in consideration of the above 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.

In order to solve the above-mentioned problems and achieve the object, the file registration support device according to the present invention is a file registration support device having a control unit capable of supporting the registration of evidential files and non-evidence files from the same screen, the control unit being provided with an attachment list screen display means for displaying an attachment list screen, which is a screen for attaching a file, when a button for attaching a file is selected on a voucher input screen, which is a screen for inputting the contents of a voucher, and an attachment detail screen display means for displaying an attachment detail screen, which is a screen for inputting detailed information about a file to be attached to a voucher, including an area for inputting an image of the attached file and detailed information about the attached file, when a file is attached on the attachment list screen, the attachment detail screen display means displays on the attachment detail screen a list of items according 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 input on the voucher input screen before the attachment list screen is displayed, the contents of the voucher input on the voucher input screen are displayed with the item values set to the contents of the voucher.

The file registration support device according to the present invention is also 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 that includes a list of items to be displayed on the attachment details screen for each file type.

The file registration support device according to the present invention further includes a storage unit, and the storage 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 document type table including the document type identification data, the document name, and an item name related to the date, and the attachment details screen display means acquires, from the screen control table, 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 input belongs, then acquires from the document type table the document name and item name related to the date linked to the acquired document type identification data, and finally displays the acquired document name and item name related to the date.

The file registration support device according to 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, redisplays the attachment list screen including a list of attached files and the corresponding file types, and the control unit further comprises a work table generation means, when a button for registering an attached file is selected on the redisplayed attachment list screen, generates a work table including file identification data for the attached file, a file type identification category for the type of the attached file, detailed information about the attached file input on the attachment details screen, and binary information about the attached file.

In addition, in the file registration support device according to the present invention, when a button for registering an attached file is selected on the redisplayed attachment list screen, the control unit redisplays the voucher input screen, and when a button for registering a voucher is selected on the redisplayed voucher input screen, (i) a linking table that links a voucher number for identifying the registered voucher 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 voucher 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 system further comprises a linking table generating means for generating a voucher image table including the data and binary information about the attached file, (iii) a workflow case table including the voucher number and case identification data for identifying each case on the workflow when the file type identification category in the work table is a category indicating the non-voucher file, 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 (iv) a voucher detail table including the voucher number and the contents of the voucher entered on the voucher input screen.

In addition, in the file registration support device according to the present invention, when a voucher approval screen, which is a screen for a person in charge to approve the voucher, is launched, the control unit obtains from the voucher details 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, obtains from the linking table the file identification data linked to the voucher number in the workflow case table, and further obtains detailed information and binary information linked to the obtained file identification data from the evidence information table and the evidence 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 when the file selected on the voucher approval screen is the evidence file, the contents of the obtained voucher, detailed information obtained from the evidence information table, and binary information obtained from the evidence image table are displayed on the voucher approval screen, and when the file selected on the voucher approval screen is the non-evidence file, the contents of the obtained voucher and the binary information obtained from the file image table are displayed on the voucher approval screen.

The file registration support device according to the present invention is further characterized in that it includes a document search result display means for, when search conditions are inputted on a document search screen, which is a screen for searching for the document files, searching the document information table for information on the document files that match the inputted search conditions and displaying the search results on the document search screen.

The file registration support device according to the present invention is also characterized in that the supporting document is a delivery note, receipt, invoice, or estimate, and the non-supporting document is a request for approval.

The file registration support method according to the present invention is a file registration support method executed by an information processing device having a control unit, which can support the registration of evidential files and non-evidence files from the same screen, and includes an attachment list screen display step executed by the control unit, which displays an attachment list screen, which is a screen for attaching a file, when a button for attaching a file is selected on a voucher input screen, which is a screen for inputting the contents of a voucher, and an attachment detail screen display step, which displays an attachment detail screen, which is a screen for inputting detailed information about a file to be attached to a voucher, including an area for inputting an image of the attached file and detailed information about the attached file, when a file is attached on the attachment list screen, and in the attachment detail screen display step, a list of items according 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 input on the voucher input screen before the attachment list screen was displayed, the contents of the voucher input on the voucher input screen are displayed as item values.

The file registration support program according to the present invention is a file registration support program for an information processing device having a control unit, which can support the registration of evidential files and non-evidence files from the same screen, and includes an attachment list screen display step for causing the control unit to execute the program, which displays an attachment list screen, which is a screen for attaching a file, when a button for attaching a file is selected on a voucher input screen, which is a screen for inputting the contents of a voucher, and an attachment detail screen display step for displaying an attachment detail screen, which is a screen for inputting detailed information about a file to be attached to a voucher, including an area for inputting an image of the attached file and detailed information about the attached file, when a file is attached on the attachment list screen, and in the attachment detail screen display step, a list of items according to the type of the 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 input on the voucher input screen before the attachment list screen was displayed, the contents of the voucher input on the voucher input screen are displayed as item values.

The present invention has the effect of helping users to register evidence files and non-evidence files from the same screen.

FIG. 1 is a block diagram showing an example of the configuration of a file registration support device. FIG. 2 is a diagram showing an example of an outline of a processing flow according to the present embodiment. FIG. 3 is a diagram showing an example of an outline of the process flow when the system classification is "electronic transaction" or "scanner storage." FIG. 4 is a diagram showing an example of an outline of a process flow when the system classification is "other attachments" and a workflow is used. FIG. 5 is a diagram showing an example of the screen control table and the voucher type table. FIG. 6 is a diagram showing an example of a voucher work. FIG. 7 is a diagram showing an example of the evidence information table and the evidence image table. FIG. 8 is a diagram showing an example of a table in which an explanation of each item included in the evidence information table is given. FIG. 9 is a diagram showing an example of the journal entry details table and the voucher linking table. FIG. 10 is a diagram showing an example of a workflow case table, a file information table, and a file image table. FIG. 11 is a diagram showing an example of the invoice input screen at the stage when the contents of the invoice have been input. FIG. 12 is a diagram showing an example of arguments for a dialog call. FIG. 13 is a diagram showing an example of the attached file list screen. 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). 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). 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 files). FIG. 17 is a diagram illustrating an example of a display item setting table. FIG. 18 is a diagram showing an example of the attached file list screen that is displayed again. FIG. 19 is a diagram showing an example of the generated evidence slip work. FIG. 20 is a diagram showing an example of the slip input screen that is displayed again. FIG. 21 is a flow chart showing an example of the processing executed within the business system after the "Register" button on the redisplayed slip entry screen is pressed. FIG. 22 is a diagram showing an example of obtaining a list of generated voucher work and voucher slips. FIG. 23 is a diagram illustrating an example of the generated evidence linking table. 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." FIG. 25 is a diagram showing an example of the generated voucher work. FIG. 26 is a diagram showing 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. FIG. 27 is a diagram showing 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. FIG. 28 is a diagram showing an example of the generated journal entry detail table. FIG. 29 is a diagram showing an example of advance acquisition of information necessary for displaying the slip approval screen. FIG. 30 shows an example of the voucher approval screen when file A, which is a system requirements file, is selected. FIG. 31 shows an example of the slip approval screen when file C, which is an additional attached file, is selected. 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. FIG. 33 is a diagram showing an example of the evidence information table to be searched. FIG. 34 is a diagram showing an example of items that can be used as search conditions. FIG. 35 is a diagram showing an example of items displayed as search results. FIG. 36 is a diagram showing an example of the evidence search screen. FIG. 37 shows buttons and the like arranged in the footer section of the evidence search screen. 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/time have been updated.

Below, an embodiment 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 drawings. Note that the present invention is not limited to the present embodiment.

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

Here, a supporting document file is document data that proves the contents of a transaction. Examples of supporting documents include delivery notes, receipts, invoices, and estimates. Support files generated by electronic transactions (electronic transaction files) and support files generated by scanner storage (scanner-saved files) must meet the system requirements of the Electronic Bookkeeping Act, and therefore belong to the category of "system requirement files."

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 system requirements of the Electronic Bookkeeping Act, and belong to the category of "other attached files."

There are rules for storing system requirement files, so they need to be stored in a way that is different from the way other attachments are stored. Previously, in order to meet these rules, ports were created for uploading system requirement files and other attachments to their respective storage locations from different screens.

However, when registering files from different screens, the following problems (1) and (2) arise.
(1) The user must determine which entry to attach depending on the type of file to be uploaded, which may result in errors.
(2) The amount of work increases when uploading both the system requirements file and other attachments.

There was also a request to be able to approve invoices by reviewing the file of the approval document that is the basis for the invoice, and travel expense schedule files for business trip settlements. There was also a request to store a set of related documents linked to accounting entries.

Therefore, in this embodiment, for example, the following (1) to (4) are possible.
(1) It is now possible to register system requirement files (evidence files) that need to 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 uploaded, the system can now automatically determine the items that need to be entered for each system requirement and display them on the screen, helping to reduce errors made by applicants.
(3) It is now possible to search electronic transaction files and scanned files, which will reduce the costs of responding to tax investigations, 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 users and also reduces the risk of misjudgment.

For details on how to view and delete uploaded files, please see below.

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 way other attached files are viewed varies depending on the method of calling up each business, and can also be controlled by each business.

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

The specific configuration and operation are explained below.

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.

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 be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The file registration support device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the file registration support device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 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.

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 works with a mouse to provide 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

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

The screen control table 106a, the evidence type table 106b, the evidence voucher work 106c, the evidence information table 106d, and the evidence image table 106e are tables stored in the electronic bookkeeping system. In contrast, the evidence linking table 106f, the workflow case table 106g, the file information table 106h, the file image table 106i, and the journal entry details table 106j are tables stored in each business system.

As shown in FIG. 5, the screen control table 106a includes, for example, system identification data (system name) for identifying the system to which the invoice input screen described below belongs, and document type identification data (initial display document code) for identifying the document type. In other words, the screen control table 106a includes the name of the screen from which the attachment dialog was called, and the document code that is initially set when the attachment dialog is called from that screen.

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

The voucher voucher work 106c is a work table for temporarily storing information about files. As shown in FIG. 6, the voucher voucher work 106c includes, for example, a WK key (work key) for uniquely identifying a record in the voucher voucher work 106c, file identification data (voucher Guid) for the attached file, a file type identification category (regulation category) for the type of the attached file, detailed information about the attached file entered on the attachment file details screen described below (file name, extension, document code, receipt date, transaction date, amount, client name, product name, resolution, gradation, TS presence/absence, TS attachment date and time, and originating system), and binary information (file image) about the attached file. In reality, only the code is stored in the document code column. TS is an abbreviation for "time stamp".

The file type identification category (regulatory category) is broadly divided into a category indicating the evidential file (the "electronic transaction" or "scanner-saved" regulatory category) and a category indicating the non-evidence file (the "other attachment" regulatory category). The category indicating the evidential file is further divided into a category indicating the electronic transaction file (the "electronic transaction" regulatory category) and a category indicating the scanner-saved file (the "scanner-saved" regulatory category).

The binary information is information that represents the attached file itself, and may be image information or information other than an image. Examples of the binary information include PDF files with embedded images, e-mail data, Excel format data, and Word format data.

The evidence information table 106d is a table that manages 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 category (regulation category), and detailed information about the attached file (file name, extension, document code, receipt date, transaction date, amount, client name, product name, resolution, gradation, TS presence/absence, TS attachment date/time, originating system, and deleted flag). FIG. 8 shows a table that provides an explanation of each item included in the evidence information table 106d.

The evidence image table 106e is a table that manages binary information about the evidence file, and is generated from the evidence voucher work 106c. As shown in FIG. 7, the evidence image table 106e includes, for example, the file identification data (evidence Guid) and binary information (file image) about the attached file.

The 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 evidence linking table 106f includes, for example, a voucher number for identifying a registered voucher, the file identification data (electronic evidence Guid) in the evidence voucher work 106c, and the file type identification category (system category) in the evidence voucher work 106c, which are linked together.

As shown in FIG. 10, the workflow case table 106g includes, for example, case identification data (case Guid) for identifying each case in the workflow, the approval status, the name of the employee who applied, the document number (business document number), and the like.

The file information table 106h is a table that manages detailed information about the non-voucher files, and is generated from the voucher work 106c. As shown in FIG. 10, the file information table 106h includes, for example, the case identification data (CaseGuid) and detailed information about the attached files (attached file names and notes).

The file image table 106i is a table that manages binary information about the non-voucher files, and is generated from the voucher voucher 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.

As shown in FIG. 9, the journal entry details table 106j includes, for example, the voucher number, the case identification data (case Guid), the contents of the voucher (debit account title and debit amount) entered on the voucher input screen described below, and so on.

As shown in FIG. 17, 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. In the example of FIG. 17, items marked with "◯" are items that are displayed on the attachment details screen, and items marked with "X" are items that are not displayed on the attachment details screen.

The control unit 102 is a CPU or the like that provides 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.

The control unit 102 has, in terms of its functional concept, for example: (1) an attachment list screen display unit 102a as an attachment list screen display means for displaying an attachment 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 detail screen display unit 102b as an attachment detail screen display means for displaying an attachment detail screen, which is a screen for inputting detailed information about a file to be attached to a slip, including an area for inputting an image of the attached file and detailed information about the attached file, when a file is attached on the attachment list screen; and (3) an attachment list screen that is displayed again, which displays, when a button for registering an attached file is selected, file identification data for the attached file, file type identification classification for the type of the attached file, detailed information about the attached file entered on the attachment detail screen, and binary information about the attached file. and (4) when a button for registering an attached file is selected on the attached file list screen that is displayed again, the voucher input screen is displayed again, and when a button for registering a voucher is selected on the re-displayed voucher input screen, (i) a linking table that links a voucher number for identifying the registered voucher with the file identification data in the worktable, (ii) when the file type identification category in the worktable is a category indicating the evidence file, a voucher information table that includes the file identification data in the worktable, the file type identification category, and detailed information about the attached file, and a voucher image table that includes the file identification data in the worktable and binary information about the attached file, and (iii) when the file type identification category in the worktable is a category indicating the non-evidence file, a linking table that links the voucher number with each case on the workflow and includes the file identification data in the worktable and the file type identification category. a linking table etc. generating unit 102d as linking table etc. generating means for generating (i) a workflow case table including case identification data for identifying the attached file in the work table, 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 voucher detail table including the voucher number and the content of the voucher entered on the voucher input screen; and (5) when a voucher approval screen which is a screen for a person in charge to approve the voucher is launched, the unit 102d obtains the content of the voucher linked to the voucher number in the workflow case table from the voucher 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. The system includes an approval information display unit 102e as an approval information display means for displaying the acquired voucher contents, detailed information acquired from the evidence information table, and binary information acquired from the evidence image table on the voucher approval screen when other files associated with the case are registered in the file information table, and for displaying the acquired voucher contents and binary information acquired from the evidence image table on the voucher approval screen when the file selected on the voucher approval screen is the evidence file, and for displaying the acquired voucher contents and binary information acquired from the file image table on the voucher approval screen when the file selected on the voucher approval screen is the non-evidence file, and (6) an evidence search result display unit 102f as an evidence search result display means for searching the evidence information table for information on the evidence file that matches the search conditions entered on the evidence search screen, when search conditions are entered on the evidence search screen, which is a screen for searching the evidence file, and displaying the search results on the evidence search screen. The contents of the processing executed by each unit will be described in detail in [4. Specific examples of processing] below.

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

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

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

Figure 4 shows an overview of the process flow when the system classification is "other attachments" and a workflow is used. 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.

The key point here is that in this embodiment, even if the file classification is different, files can be registered in the same flow from journal entry screen → attachment list screen and attachment details screen → journal entry screen, as shown in Figures 3 and 4.

Note that in Figures 3 and 4, the characters marked with * indicate the corresponding relationship with [4-1. Operational image] below. 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].

[3-3. Electronic bookkeeping systems and business systems]
In this embodiment, the evidence files can be stored in an electronic bookkeeping system, which is a dedicated DB separate from the normal business DB, to meet the requirements of the Electronic Bookkeeping Act. This allows complete separation of processing between the electronic bookkeeping system that stores evidence files and the normal business system that stores non-evidence files. The features of this system are that they can be collectively processed in the same DB, and that they are stored in a single DB to unify the handling of logical deletion within the same DB. The features of the processing or management performed in each system are shown below.

(Electronic bookkeeping system)
- It is possible to add a time stamp, which makes it possible to prevent unauthorized persons from falsifying evidence data and to detect whether or not such falsification has occurred.
・The evidence cannot be physically deleted. In addition, time stamp attachments can be consolidated into one database (not distributed across business databases).
- Because it is a separate database, it is possible to encrypt it in the database settings. Also, the database can be backed up separately (this is not a requirement that includes security as an access right to the database).
As explained in [4-3] below, it is possible to search supporting documents that meet the search requirements of the Electronic Bookkeeping Act.

(Normal business system)
・No time stamp is added.
- Attached files can be physically deleted. Also, the DB can be initialized.
- The search method differs depending on the business system. There are also business systems that do not allow file search. In the case of a workflow system, you can refer to files from "File Attachment Specification. Inquiry", but you cannot search for individual files.

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

[4-1. Operation image]
This section explains how to start 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.

(1) Calling of Attachment Dialog from Business System First, when the button for attaching a file ("Attach" button) is selected on the slip input screen (see FIG. 11) for inputting the contents of a slip, the attachment list screen display unit 102a displays the attachment list screen (see FIG. 13) for attaching a file. The display of the attachment list screen is, in other words, the start of the attachment dialog.

Here, the attachment file list screen display unit 102a displays the attachment file list screen in accordance with arguments of the dialogue call shown in Fig. 12. Note the following points regarding the arguments of the dialogue call.
When you call a dialog at the source of the 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 is a flag that prevents the amount, etc. from being changed after final approval or when viewing in reference mode from a job.
The originating system is used to set an upper limit on the number of files that can be uploaded, and to uniquely identify the evidence in [4-3]. The originating system is preset as an argument when the dialog is called.

(2) Starting and registering the attachment dialog (2-1) Step 1: Selecting the file you want to attach on the attachment list screen Next, select the file you want to attach from the attachment list screen (see FIG. 13). There are four ways to attach a file:

The first method is to press the "Select from Explorer" button in Figure 13 and select the file you want to attach. 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.

The third method is to press the "Select from photo of evidence file" button in Figure 13 and upload a file taken with a mobile phone. With this method, it is possible not only to apply directly from the mobile phone using an image taken with a mobile phone, but also to import the image from an in-house PC.

The fourth method is to press the "Select from previously uploaded files" button in Figure 13 and reattach a file that was deleted after being registered in the electronic bookkeeping system. This method makes it possible to relink a voucher that has been logically deleted from the voucher information table 106d to a slip and upload it.

Once the file has been attached, you will be redirected to the attachment details screen.

(2-2) Step 2: Entering detailed information about the attached file 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.

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

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 (see Figures 14 to 16), 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 value.

As described in the previous paragraph, the attachment details screen display unit 102b may obtain a list of items corresponding to the type of attached file selected on the attachment details screen (see Figures 14 to 16) according to fixed rules, but as described below, it may also obtain the list by referring to the display item setting table 106k (see Figure 17). That is, the attachment details screen display unit 102b may obtain 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 Figure 17), which contains a list of items to be displayed on the attachment details screen for each file type.

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 Figures 14 to 16), the attachment details screen display unit 102b switches between displaying and hiding input items by retrieving items corresponding to the selected regulation classification from the display item setting table 106k (see Figure 17). 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 Figures 14 to 16) with the items set.

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 attached file details screen (see Figs. 14 to 16) is launched with the items passed from the slip input screen (see Fig. 11) initially set. The business system can set what to set. For example, in the case of a travel expense settlement application in a travel expense system, if there is a requirement to attach a voucher for each item, parameters can be set for each item.
- On the same screen, it is possible to select either a system requirements file or other attachment and upload the file.
Depending on the selected system classification, the input items are automatically switched. In other words, the system guides you so that you can input items that meet the system requirements. For information on displaying/hiding items according to each system classification, please refer to the display item setting table 106k (see FIG. 17).

Here, the attachment details screen display unit 102b obtains, from the screen control table 106a (see FIG. 14), the document type identification data (initial display document code) linked to the system identification data (system name) for the system to which the voucher input screen (see FIG. 11) on which the voucher contents have been entered belongs. Next, the attachment details screen display unit 102b obtains, from the evidence 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).

The display of the document name and the item name related to the date (transaction date label name) by the attachment details screen display unit 102b is specifically as follows.
The document name is 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 up. 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, whereas when the application is started from travel expense settlement, the document code of the receipt is obtained.
The label name of "Date" can be set for each document code to be initially displayed in the evidence 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 evidence type table 106b (see FIG. 14), if the document is a "delivery note," the label name of the transaction date will be "Date," and if the document is a "receipt," the label name of the transaction date 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 is displayed on the attachment details screen.

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

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 delivery note files (electronic transaction files) and receipt files (scanner-saved files). In this example, non-evidence files are approval request files (other attachments). In this example, the same screen is the attachment list screen (see FIG. 13) and the attachment details screen (see FIG. 14 to FIG. 16).

(2-3) Step 3: Return to the attachment list screen and check whether the attached file and its corresponding 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 their corresponding file types.

Specifically, when registration of all selected attachments has been completed on the attachment details screen (see Figures 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 (=regulation 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.

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 and you move to the next screen, and then return to the original screen from the next screen, the original screen is displayed again.
- When the next screen is displayed as a pop-up on 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.

When the button for registering the attached file (the "Register" button) is selected on the redisplayed attachment list screen (see FIG. 18), the work table generating unit 102c generates a voucher voucher work 106c (see FIG. 19) that includes the file identification data (evidence Guid) for the attached file, the file type identification category (regulation category) 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/time, and originating system) entered on the attachment details screen (see FIG. 14 to FIG. 16), and binary information (file image) about the attached file. The work table generating unit 102c also stores the same WK key (work key) in the voucher voucher work 106c.

Specifically, when registration is made in the attachment dialog, detailed information and a file image of the attached evidence are stored in the evidence voucher work 106c. When storage is complete, the screen returns to the business system 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 evidence voucher work 106c that are updated differ depending on the system classification selected on the attachment details screen (see Figures 14 to 16); for example, when a scanner-saved file is selected, information is stored in the resolution and gradation columns.

(3) Voucher registration at the caller (business system) When the button for registering the attached file (the "Register" button) is selected on the redisplayed attached file list screen (see FIG. 18), the linking table etc. generation unit 102d redisplays the voucher input screen (see FIG. 20). Then, when the button for registering the voucher (the "Register" button) is selected on the redisplayed voucher input screen (see FIG. 20), the linking table etc. generation unit 102d starts generating each data (corresponding to "Start" in the flowchart in FIG. 21).

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

(3)-A. Acquiring a list of supporting documents registered in the attachment dialog First, the linking table etc. generating unit 102d uses common processing of the electronic bookkeeping system as shown in FIG. 22 to acquire the file identification data (supporting document Guid) and the file type identification classification (regulation classification) as information required for generating the supporting document linking table 106f from the supporting document work 106c, which is a temporary table registered in the attachment dialog (corresponding to the processing of "A" in the flowchart in FIG. 21).

(3)-B. Generation of the evidence linking table 106f Next, the linking table etc. generating unit 102d generates the evidence linking table 106f (see FIG. 23) including the voucher number for identifying the registered voucher and the file identification data (evidence Guid) in the evidence voucher work 106c, etc., in a linked manner (corresponding to the process of "B" in the flowchart in FIG. 21). The linking table etc. generating unit 102d may further include the file type identification category (regulation category) in the evidence voucher work 106c in the evidence linking table 106f (see FIG. 23).

In the evidence linking table 106f shown in FIG. 23, three files are linked to one invoice identified by the invoice number "Zaimu100": a delivery note file (Evidence Guid: Guid_Evi01), a receipt file (Evidence Guid: Guid_Evi02), and a request for approval file (Evidence Guid: Guid_Evi03).

Please note the following points regarding the generation of the evidence linking table 106f performed by the linking table etc. generation unit 102d.
On the business system side, the linking information is updated in the voucher linking table 106f of the business system DB (this update is delegated to the business side). Here, the slip of the business system and the electronic voucher 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 evidence linking table 106f is delegated to each business system. Therefore, the information held in the evidence linking table 106f may differ depending on each business system. For example, the accounting system also updates "other attachments", while the travel expense system does not update "other attachments". This is to allow for flexibility in how and in which DB the "other attachments" are stored, as each business system differs.

(3)-C. Checking the System Classification Next, the linking table etc. generating unit 102d checks the type of the file type identification classification (system classification) in the evidence slip work 106c (corresponding to the process of "C" in the flowchart of FIG. 21).

Referring to the generated supporting document work 106c shown in FIG. 19, the record on the first line (regulation category: electronic transaction) and the record on the second line (regulation category: scanner storage) correspond to the records in the above-mentioned regulatory requirements file. In this case, the linking table etc. generating unit 102d generates the supporting document information table 106d and the supporting document image table 106e based on the records on the first and second lines in the supporting document work 106c, as described in (3)-D below.

In contrast, referring to the generated supporting document work 106c shown in FIG. 19, the record on the third line (regulation classification: other attachments) corresponds to the record for the other attachments. In this case, the linking table etc. generation unit 102d generates the workflow case table 106g, file information table 106h, and file image table 106i based on the record on the third line in the supporting document work 106c, as described in (3)-F below, or generates the file information table 106h and file image table 106i, as described in (3)-G below.

(3)-D. When the system classification = electronic transaction or scanner storage, the linking table etc. generating unit 102d determines that the file type identification classification (system classification) in the evidence slip work 106c (see FIG. 19) is a classification (electronic transaction or scanner storage) indicating the evidence file (when proceeding to the system requirement file (electronic transaction or scanner storage) in 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 voucher work 106c (see FIG. 19), the file type identification category (regulation category) in the voucher voucher work 106c (see FIG. 19), and detailed information about the attached file in the voucher voucher work 106c (see FIG. 19) (file name, extension, document code, receipt date, transaction date, amount, product name, customer name, resolution, gradation, TS presence/absence, TS attachment date/time, originating system, and deleted flag);
A voucher image table 106e (see FIG. 24) including the file identification data (voucher Guid) in the voucher voucher work 106c (see FIG. 19) and binary information (file image) about the attached file in the voucher voucher work 106c (see FIG. 19);
(corresponding to the process of "D" in the flowchart of FIG. 21).

Note that the following points should be noted regarding the generation of the evidence information table 106d and the evidence image table 106e 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 obtained using the "WK key" registered in the temporary table, voucher slip work 106c, as a key, and the information is updated in each table (voucher information table 106d and 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.

(3)-E. Checking whether or not to use a workflow system When the file type identification category (regulation category) in the evidence voucher work 106c (see FIG. 19) is a category indicating the non-evidence file (other attachments), the linking table etc. generating unit 102d further checks whether or not to use a workflow system (corresponding to the process of "E" in the flowchart in 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 saves file images obtained by the common processing of the electronic bookkeeping system. FIG. 25 shows the evidence voucher work 106c, which is the update source table.

(3)-F. In the case where the system classification = other attachments and the workflow system is used, the linking table etc. generating unit 102d judges that the file type identification classification (system classification) in the supporting document slip work 106c (see FIG. 19) is a classification (other attachments) indicating the non-supporting file (in the case where the process proceeds to "other attachments" in C in the flowchart of FIG. 21), and the workflow system is used (in the case where the process proceeds 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) including the case identification data (Case Guid) and detailed information (attached file name and memo) about the attached file in the supporting document work 106c (see FIG. 19);
A file image table 106i (see FIG. 26) including the case identification data (Case Guid) and binary information (file image) about the attached file in the supporting document work 106c (see FIG. 19);
(corresponding to the process of "F" in the flowchart of FIG. 21).

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 by the association 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 view the document and other attachments at the same time when approving.

(3)-G. System category = Other attachments and no workflow system is used (when attaching files to be saved by the business itself)
The linking table etc. generating unit 102d determines that the file type identification category (regulation category) in the supporting document voucher work 106c (see FIG. 19) is a category (other attachments) indicating the non-supporting file (when proceeding to "other attachments" in C in the flowchart of FIG. 21), and the workflow system is not being used (when proceeding to "not in use" 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 voucher number and binary information (file image) about the attached file in the supporting voucher work 106c (see FIG. 19);
(corresponding to the process of "G" in the flowchart of FIG. 21).

Note that the following points should be noted regarding the generation of the file information table 106h and the file image table 106i by the association table etc. generating unit 102d.
- Each business system stores file images, etc. obtained through common processing in the electronic bookkeeping system.
・In this example, the values listed are those of the accounting system used in the explanation so far.

(3)-H. Generation of Journal Detail Table Finally, the linking table etc. generating unit 102d generates a journal detail table 106j (see FIG. 28) including 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 finalized by the voucher registration process of each business system.

By carrying out the processing described in this section (3), the linking table etc. generation unit 102d completes the generation of each data (corresponding to "End" in the flowchart in Figure 21).

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

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

To display information when approving a voucher, the information to be displayed must be acquired in advance, so we will first explain how to acquire the information to be displayed. When the voucher approval screen, which is the screen for the person in charge to approve the voucher, is launched, the approval information display unit 102e acquires information in advance as follows.

As shown in FIG. 29, the approval information display unit 102e obtains the contents of the voucher (such as the debit account item and debit amount) linked to the voucher number in the workflow case table 106g from the journal entry details table 106j.

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

Then, when 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 (evidence Guid) in the workflow case table 106g from the file image table 106i, as shown in FIG. 29.

Note that the following points should be noted regarding the advance acquisition of information performed by the approval information display unit 102e.
From the workflow case table 106g, the journal entry details table 106j and the voucher linking table 106f are referenced.
The information on the evidence is obtained by the evidence acquisition process of the electronic bookkeeping system, which is referenced from the evidence linking table 106f within the common processing of the workflow.
- Other attachment information is obtained based on the Workflow CaseGuid.

Then, the approval information display unit 102e displays the acquired information on the invoice approval screen as follows:

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.

This display will be described in detail with reference to FIG. 30. FIG. 30 is a diagram showing the voucher approval screen when the cursor is placed on the "File A.pdf" button. As shown in FIG. 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 the "Journal Entry Voucher Confirmation" area on the left side of the screen as the contents of the voucher, displays an area on the right side of the screen containing the document name, etc. as the detailed information, and displays an image of the delivery note in the center of the screen as the binary information, as shown in FIG. 30. The items that can be displayed as the detailed information are summarized in FIG. 32.

In contrast, if the file selected on the invoice approval screen is the non-voucher file (other attachment 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.

This display will be described in detail with reference to FIG. 31. FIG. 31 is a diagram showing the voucher approval screen when the cursor is placed on the "File C.pdf" button. As shown in FIG. 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 document on the right side of the screen as the binary information, as shown in FIG. 31.

Note that the following points should be noted 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 requirement files and other attached files) linked to the invoice are displayed as a list of file buttons. By clicking on the displayed file button, you can download the attached files.
- By placing the cursor on one of the file buttons displayed at the top of the document approval screen, the preview of the attached file can be automatically switched. If the cursor is placed on the file button for the system requirements file, the content of the detailed information will also change.

As explained above in section [4-2], the file registration support device 100 according to this embodiment can display, when approving a voucher, the contents of the voucher (in this example, the contents of "Journal 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 request form) on a single screen (in this example, the voucher approval screen). This allows the approving officer to accurately and instantly check a series of information related to the voucher before approving the voucher, which reduces the burden on the approving officer and also eliminates mistakes during the approval process.

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

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

The accounting staff version is used for responding to tax audits, regular inspections, and daily checks. In addition, the accounting staff version allows them to search, view, and logically delete supporting documents uploaded by all users.

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

Here, the search requirements of the Electronic Bookkeeping Act include the following (1) to (3).
(1) The ability to search by "transaction date (or other date),""transactionamount," 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 a request for download is complied with, conditions (2) and (3) are not required.

The following will specifically explain the search for evidence from the evidence search screen (see FIG. 36), which is a screen for searching for the evidence file, assuming that the following conditions exist.
Assume that the evidence information table 106d shown in Fig. 33 exists as a search target. The evidence information table 106d shown in Fig. 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 Fig. 33, a scanner-saved file is uploaded from the travel expense system (record of evidence Guid: Guid_Evi03), and an electronic transaction file is uploaded from the sales system (record of 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 right-hand area of the evidence search screen (see Fig. 36).

When search conditions are entered on the evidence search screen (see FIG. 36), the evidence search result display unit 102f searches the evidence information table 106d for information about the evidence files that match the entered search conditions, and displays the search results on the evidence search screen (see FIG. 36).

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 FIG. 36), it is possible to search (extract) documents using the details registered at the time of application. By making it possible to search for 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 FIG. 36), the item details displayed as search results are controlled according to the selected system category. For control of the displayed item details, see FIG. 35.
In [4-1], an example of registering supporting documents from the core accounting system was explained, but as explained in this section [4-3], if supporting documents are registered from other systems (in this example, the travel expense system and the sales system), it is possible to search for and view the supporting documents registered from those other systems.

Here, we will explain the buttons located in the footer section (lower part) of the evidence search screen (see Figure 36). Figure 37 shows an enlarged view of the buttons located in the footer section (lower part).

The "Add Evidence" button is used to directly upload an electronic transaction file to the electronic bookkeeping system without linking it to a voucher. When the "Add Evidence" button is pressed, the screen transitions to the attachment list screen and the attachment details screen.

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 FIG. 37. Records whose "Deleted Flag" has been updated to "True" are treated as deleted, but the records themselves do not disappear.

The "Details" button is used to view 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.

As described above in 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 regular inspections and daily checks, and can also respond quickly to tax audits.

As explained in 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 consolidates vouchers registered from multiple systems (in this example, including not only the core accounting system but also the travel expense system and sales system), allowing a comprehensive and thorough search of all registered vouchers.

[4-4. Adding a time stamp]
In this section, the addition of a time stamp will be described. When a time stamp is added, the presence/absence of a time stamp (TS presence/absence) and the time stamp addition date/time (TS addition 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 time stamp service.

[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 making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

6. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

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

Furthermore, with regard to the file registration support device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the file registration support device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains 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 necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

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

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

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. 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.

The various databases stored in the memory unit are storage devices such as RAM, ROM, etc., 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.

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 implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

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

The present invention is useful, for example, in fields related to accounting and fields that use auxiliary ledgers.

100 File registration support device 102 Control unit
102a Attachment file list screen display section
102b Attachment file details screen display section
102c work table generating unit
102d Linking table etc. generating unit
102e Approval information display section
102f evidence search result display unit 104 communication interface unit 106 storage unit
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 details table
106k Display item setting table 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (10)

A file registration support device having a control unit capable of supporting the registration of evidence files and non-evidence files from a single screen,
The control unit is
an 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;
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
said attachment details screen display means displays on said attachment details screen a list of items corresponding to the type of the attached file selected on said attachment details screen, and for some of the displayed items, if the contents of a slip have been input on said slip input screen before said attachment list screen is displayed, the contents of the slip input on said slip input screen are displayed in a state where they are set as item values;
A file registration support device comprising: The attachment file detail screen display means
obtaining a list of items corresponding to the type of the attached file selected on the attachment details screen from a display item setting table including a list of items to be displayed on the attachment details screen for each file type;
2. The file registration support device according to claim 1, wherein: Further comprising a storage unit,
The storage unit includes:
a screen control table including system identification data for identifying a system to which the slip input screen belongs and document type identification data for identifying a document type;
a document type table including the document type identification data, the document name, and the item name related to the date;
is stored,
The attachment file detail screen display means
obtaining, from the screen control table, document type identification data linked to system identification data for the system to which the slip input screen in which the slip contents are input belongs, then obtaining, from the voucher type table, item names relating to the document name and date linked to the obtained document type identification data, and finally displaying the obtained item names relating to the document name and date;
2. The file registration support device according to claim 1, wherein: the attachment file list screen display means, when information is input on the attachment file details screen and a button for registering an attached file is selected on the attachment file details screen, displays again the attachment file list screen including a list of the attached files and the corresponding file types;
The control unit is
a work table generating means for generating a work table including, when a button for registering an attached file is selected on the re-displayed attachment file list screen, file identification data for the attached file, a file type identification category for the type of the attached file, detailed information for the attached file input on the attachment file details screen, and binary information for the attached file;
2. The file registration support device according to claim 1, wherein: The control unit is
When a button for registering an attached file is selected on the redisplayed attachment file list screen, the slip input screen is displayed again, and when a button for registering a slip is selected on the redisplayed slip input screen,
(i) a linking table including a slip number for identifying a registered slip and the file identification data in the work table in a linked manner;
(ii) when the file type identification category in the work table is a category indicating the evidence file, a evidence information table including 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 including the file identification data in the work table and binary information about the attached file;
(iii) when the file type identification category in the work table is a category indicating the non-voucher file, a workflow case table including the slip number and case identification data for identifying each case on the workflow, a file information table including the case identification data and detailed information about the attached file in the work table, and a file image table including the case identification data and binary information about the attached file in the work table;
(iv) a voucher detail table including the voucher number and the contents of the voucher entered on the voucher input screen;
Further comprising a linking table generating means for generating a linking table etc.
5. The file registration support device according to claim 4, The control unit is
When the invoice approval screen, which is a screen for the person in charge to approve the invoice, is launched,
Obtaining the contents of the voucher linked to the voucher number in the workflow case table from the voucher detail table;
When a voucher linked to a case is registered in the linking table, the file identification data linked to the slip number in the workflow case table is obtained from the linking table, and further, detailed information and binary information linked to the obtained file identification data are obtained from the evidence information table and the evidence image table, respectively;
When other files linked to the case are registered in the file information table, binary information linked to the case identification data in the workflow case table is obtained from the file image table;
When the file selected on the voucher approval screen is the evidence file, the acquired contents of the voucher, the detailed information acquired from the evidence information table, and the binary information acquired from the evidence image table are displayed on the voucher approval screen;
an approval information display means for displaying, on the voucher approval screen, the acquired contents of the voucher and the binary information acquired from the file image table when the file selected on the voucher approval screen is the non-voucher file;
6. The file registration support device according to claim 5, The control unit is
a document search result display means for, when a search condition is input on a document search screen which is a screen for searching the document files, searching the document information table for information on the document files which matches the input search condition and displaying the search result on the document search screen;
6. The file registration support device according to claim 5, The document is a delivery note, receipt, invoice or quotation,
The non-certificate is a request for approval,
8. A file registration support device according to claim 1, wherein: A file registration support method executed by an information processing device having a control unit, which can support the registration of evidence files and non-evidence files from a single screen, comprising:
Executed by the control unit,
an attachment list screen display step of displaying an attachment 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;
an attachment details screen display step of displaying an attachment details screen, which is a screen for inputting detailed information about the file to be attached to the 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 list screen;
Including,
In the attachment details screen display step, a list of items corresponding to the type of the attached file selected on the attachment details screen is displayed 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 method comprising the steps of: A file registration support program for an information processing device having a control unit, capable of supporting the registration of evidence files and non-evidence files from a single screen, the program comprising:
To cause the control unit to execute
an attachment list screen display step of displaying an attachment 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;
an attachment details screen display step of displaying an attachment details screen, which is a screen for inputting detailed information about the file to be attached to the 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 list screen;
Including,
In the attachment details screen display step, a list of items corresponding to the type of the attached file selected on the attachment details screen is displayed 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 program characterized by the above.

Images