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

Abstract

To provide a file registration support device or the like for supporting a voucher file and a non-voucher file to be registered from the same screen.SOLUTION: The control unit includes an attached file list screen display unit that displays an attached file list screen for attaching a file, an attached file control unit that refers to the job master, the system-based precision control master, and the file attachment control master from a job used by a user and determines a precision category of an attachable file, and an attached file detail screen display unit that displays an attached file detail screen. The attached file detail screen display means displays only the scope category of the file determined to be attachable by the attached file control means in a user-selectable manner.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] When creating a voucher, it is possible to attach supporting documents, which are electronic transaction files classified as electronic transactions under the Electronic Bookkeeping Act, supporting documents, which are scanner-saved files classified as scanner-saved under the Electronic Bookkeeping Act, and other files for internal management. This is because, for example, when approving a voucher, there is a desire to check not only supporting documents such as receipts corresponding to the voucher, but also other files such as approval documents corresponding to the voucher.

[0003] As a technology for improving the efficiency of accounting processing based on supporting documents, a supporting document processing system has been proposed, which includes an account information registration unit that receives account information for accessing a trading partner system that provides supporting document data related to a transaction from a user terminal and registers the account information in an account information storage unit, a transaction information acquisition unit that acquires the supporting document data from the trading partner system based on the account information and stores the supporting document data in the transaction information storage unit, and an accounting information generation unit that generates accounting data for performing accounting processing related to the transaction based on the supporting document data stored in the transaction information storage unit, and associates the supporting document data with the accounting data and stores them in the accounting information storage unit. [Prior art documents] [Patent documents]

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

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

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

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

[0008] In order to solve the above-mentioned problems and achieve the object, the file registration support device according to the present invention is a file registration support device that supports the registration of supporting documents and non-supporting documents from the same screen and includes a control unit, and is capable of accessing a job master that associates and stores the system used by the user with the job, a system-specific system correspondence control master that associates and stores the system with the supporting documents that can be attached, and a file attachment control master that associates and stores the job with the file attachment unit and the files that can be attached, and when a button to attach a file is selected on a slip input screen where the contents of the slip are input, the control unit accesses an attachment field to attach the file. The system comprises an attachment file list screen display means for displaying a file list screen, an attachment file control means for referencing the job master, the system-specific system correspondence control master, and the file attachment control master from the job used by the user and determining the system classification of files that can be attached on an attachment unit basis, and an attachment file detail screen display means for displaying an attachment file detail screen for inputting detailed information about the file to be attached to the slip when a file is attached on the attachment file list screen, wherein the attachment file detail screen display means displays only the system classification of files that the attachment file control means has determined can be attached on an attachment unit basis in a format that the user can select.

[0009] In addition, the file registration support device of the present invention is equipped with an attachment button display control means that refers to the job master, the system-specific institutional control master, the file attachment control master, and the job-specific attachable document type master from the job used by the user, determines whether or not to display an attachment button for each attachment unit, and displays it on the slip input screen.

[0010] In addition, the file registration support device of the present invention is capable of accessing a job-specific attachable evidence type master that stores the job, the file attachment unit, and the type of evidence that can be attached in association with each other, and the attachment file control means references the job master, the system-specific institutional correspondence control master, and the file attachment control master from the job used by the user to obtain the type of evidence that can be attached in the attachment unit, and the attachment file details screen display means lists only the type of evidence that can be attached in the attachment unit obtained by the attachment file control means.

[0011] Further, a file registration support method according to the present invention is a file registration support method executed by a file registration support device having a control unit that supports the registration of evidential files and non-evidential files from the same screen, and is capable of accessing a job master that associates and stores a system used by a user with a job, a system-specific system correspondence control master that associates and stores the system with the evidential files that can be attached, and a file attachment control master that associates and stores the job with a file attachment unit and the files that can be attached, and when a button to attach a file is selected on a slip input screen for inputting the contents of a slip executed by the control unit, an attachment list screen to which the file can be attached is displayed. an attachment control step in which the user references the job master, the system-specific system control master, and the file attachment control master from the job used and determines the system classification of files that can be attached in the attachment unit; and an attachment detail screen display step in which, when a file is attached in the attachment list screen display step, an attachment detail screen is displayed in which detailed information about the file to be attached to the slip is entered, and the attachment detail screen display step displays only the system classification of files that can be attached in the attachment unit obtained in the attachment control step in a format that the user can select.

[0012] In addition, the file registration support program of the present invention is a file registration support program executed by a file registration support device equipped with a control unit that supports the registration of supporting documents files and non-supporting documents files from the same screen, and is capable of accessing a job master that associates and stores the system used by the user with the job, a system-specific system control master that associates and stores the system with the supporting documents files that can be attached, and a file attachment control master that associates and stores the job, file attachment units, and attachable files, and includes an attachment list screen display step that displays an attachment list screen to which files are attached when a button to attach a file is selected on a slip input screen on which the contents of a slip are entered, an attachment control step that references the job master, the system-specific system control master, and the file attachment control master from the job used by the user and determines the system classification of files that can be attached in the attachment unit, and an attachment detail screen display step that enters detailed information about the file to be attached to the slip when a file is attached in the attachment list screen display step, and is characterized in that the attachment detail screen display step displays only the system classification of files that can be attached in the attachment unit obtained in the attachment control step in a format that the user can select. [Effects of the Invention]

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

[0014] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a file registration support device according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a transaction flow for product sales in which file registration can be performed by the file registration support device according to this embodiment. [Figure 3]FIG. 3 is a diagram illustrating a screen that is displayed when a user selects a job for registering slips using an available system. [Figure 4] FIG. 4 is a diagram illustrating an example of a job master. [Figure 5] FIG. 5 is a diagram illustrating an example of the system-specific regulation-compliant control master. [Figure 6] FIG. 6 is a diagram illustrating an example of the file attachment control master. [Figure 7] FIG. 7 is a diagram showing an example of the job-specific attachable evidence type master. [Figure 8] FIG. 8 is a flowchart showing an example of processing by the attachment button display control unit to determine whether or not the attachment button can be displayed for each attachment unit. [Figure 9] FIG. 9 is a diagram showing an example of the slip input screen. [Figure 10] FIG. 10 is a diagram showing an example of the attachment file list screen. [Figure 11] FIG. 11 is a flowchart showing an example of a process performed by the attachment file control unit to determine the system classification of files that can be attached on an attachment basis. [Figure 12] FIG. 12 is a diagram showing an example of the attachment file details screen. [Figure 13] FIG. 13 shows an example of the screen control table and the voucher type table. [Figure 14] FIG. 14 is a diagram showing an example of the supporting slip work. [Figure 15] FIG. 15 shows an example of the evidence information table and the evidence image table. [Figure 16] FIG. 16 is a diagram illustrating an example of the journal entry detail table and the voucher linking table. [Figure 17] FIG. 17 shows an example of a workflow case table, a file information table, and a file image table. [Figure 18] FIG. 18 is a diagram illustrating an example of a display item setting table. [Figure 19] FIG. 19 is a diagram showing an example of the slip approval screen. [Figure 20] FIG. 20 is a diagram showing an example of the document search screen. [Figure 21] FIG. 21 is a diagram illustrating the flow of registration in the file registration support device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0017] Here, a supporting document file is document data that certifies the content of a transaction. Examples of supporting documents include purchase orders, contracts, shipping instructions, delivery notes, receipts, invoices, and estimates. Support files generated through electronic transactions (electronic transaction files) and support files generated through scanner storage (scanner-saved files) must meet the system requirements of the Electronic Books Preservation Act, and are therefore categorized as "system-required files."

[0018] 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." In addition, in this specification, the classification that distinguishes between electronic transaction files, scanner-saved files, and other files is referred to as the "system classification."

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

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

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

[0022] Therefore, in this embodiment, for example, the following (1) to (6) are made possible. (1) It is now possible to register system requirement files (evidence files) that must be kept in accordance with system requirements and other attachment files (non-evidence files) that do not need to be kept in accordance with system requirements from the same screen. This reduces the amount of work required by the user. (2) The system classification (electronic transaction files, scanner-saved files, other attachments) and supporting document type (invoice, receipt) that can be attached for each business system, job, and attachment unit are set by the administrator as a master. This prevents employees with little knowledge of the system and its operation from registering files using the wrong combination of registration screen / system classification / support document type. (3) The administrator sets up a master of the system classification (electronic transaction files, scanner-saved files, other attachments) and supporting document type (invoice, receipt) that can be attached for each business system, job, and attachment unit, and determines whether or not the attachment button can be displayed for each attachment unit. If attachment is not possible, the attachment button is not displayed, thereby preventing incorrect file registration. (4) Depending on the type of file being uploaded, the system will determine the fields that need to be entered for each system requirement and automatically display them on the screen, reducing the chance of errors by applicants. (5) It is now possible to search electronic transaction files and scanned files, which will reduce the cost of responding to tax audits, etc. (6) When approving a document, all supporting documents and other attachments linked to the document can be viewed from the same screen. This reduces the amount of work required by the user and also reduces the risk of misjudgment.

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

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

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

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

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

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

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

[0030] The memory unit 106 includes, for example, a job master 106a, a system-specific compliance control master 106b, a file attachment control master 106c, a job-specific attachable voucher type master 106d, a screen control table 106e, a voucher type table 106f, a voucher slip work table 106g as a work table, a voucher information table 106h, a voucher image table 106i, a voucher linking table 106j, a workflow case table 106k, a file information table 106l, a file image table 106m, a journal entry details table 106n, and a display item setting table 106o.

[0031] The job master 106a stores the system used by the user in association with the job. The job master 106a indicates the relationship between the job used by the user for slip registration and the system that has been started. As shown in an example in Fig. 4, if the job is order entry, the system is the sales system, if the job is journal entry, the system is the financial accounting system, etc., which are registered in advance in the system settings at the time of installation.

[0032] The system-specific regulatory control master 106b stores the system used by the user in association with the voucher file that can be attached. In the system-specific regulatory control master 106b, the business system and the usable classification (attachable classification), that is, the voucher file that can be attached, are set, as shown in an example in Fig. 5.

[0033] The file attachment control master 106c stores the jobs used by the user, the file attachment units, and the files that can be attached, in association with each other. As shown in FIG. 6, the file attachment control master 106c includes the job, the attachment unit, and the available attachment classification (attachment classification), i.e., the attachment classification. In this specification, the attachment unit refers to the unit in which a file is attached. The attachment unit may be determined by the job or may be selected by the user. To select the attachment unit, the user can select the attachment unit by placing "Attach" buttons in multiple locations on the slip entry screen (described later), such as the header and details, and selecting and pressing one of the multiple "Attach" buttons. For example, pressing the "Attach" button in the header allows files to be attached on a slip-by-slip basis, whereas pressing the "Attach" button in the details allows files to be attached on a detail-by-detail basis.

[0034] The job-specific attachable voucher type master 106d stores the job used by the user, the file attachment unit, and the attachable voucher type in association with each other. As shown in an example in Fig. 7, the job-specific attachable voucher type master 106d sets the job, the attachment unit, and the attachable voucher type, such as a purchase order, contract, shipping instruction, etc.

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

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

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

[0038] The file type identification classification (regulatory classification) is broadly divided into classifications that indicate supporting documents files (regulatory classifications of "electronic transaction" or "scanner storage") and classifications that indicate non-supporting documents files (regulatory classifications of "other attachments"). The classifications that indicate supporting documents files further include classifications that indicate electronic transaction files (regulatory classifications of "electronic transaction") and classifications that indicate scanner storage files (regulatory classifications of "scanner storage").

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

[0040] The evidence information table 106h is a table for managing detailed information about evidence files, and is generated from the evidence slip work table 106g. As shown in Fig. 15, the evidence information table 106h includes, for example, file identification data (evidence Guid), file type identification classification (regulation classification), and detailed information about attached files (file name, extension, document code, receipt date, transaction date, amount, customer name, product name, resolution, gradation, presence or absence of TS, TS attachment date and time, originating system, and deleted flag).

[0041] The evidence image table 106i is a table for managing binary information about evidence files, and is generated from the evidence slip work table 106g. As shown in Fig. 15, the evidence image table 106i includes, for example, file identification data (evidence Guid) and binary information about attached files (file image).

[0042] The supporting evidence linking table 106j is a table for linking vouchers with attached files. In the case of a financial accounting system, "attached files" include both system requirement files and other attached files. As shown in FIG. 16, the supporting evidence linking table 106j includes, for example, a voucher number for identifying a registered voucher, file identification data (electronic supporting evidence Guid) in the supporting evidence voucher worktable 106g, and file type identification classification (system classification) in the supporting evidence voucher worktable 106g, all linked together.

[0043] As shown in FIG. 17, the workflow case table 106k includes, for example, case identification data (case Guid) for identifying each case on the workflow, the approval status, the name of the employee who applied, the slip number (business slip number), and the like.

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

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

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

[0047] The display item setting table 106o includes a list of items to be displayed on the attachment details screen (described later) for each file type, as shown in Fig. 18. In the example of Fig. 18, 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.

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

[0049] In terms of functional concept, the control unit 102 includes an attachment button display control unit 102a, an attachment list screen display unit 102b, an attachment control unit 102c, an attachment detail display control unit 102d, a work table generation unit 102e, a linking table etc. generation unit 102f, an approval information display unit 102g, and a voucher search result display unit 102h.

[0050] The attachment button display control unit 102a refers to the job master 106a, system-specific system correspondence control master 106b, file attachment control master 106c, and job-specific attachable evidence type master 106d from the job used by the user, obtains the system classification of files that can be attached on an attachment unit basis, determines whether or not to display the "attachment button" on an attachment unit basis, and displays it on the slip input screen MA (see Figure 9).

[0051] When the button to attach a file is selected on the slip entry screen MA for entering the contents of the slip, the attachment file list screen display unit 102b displays the attachment file list screen MB (see FIG. 10) for attaching a file.

[0052] The attachment file control unit 102c refers to the job master 106a, the system-specific system correspondence control master 106b, the file attachment control master 106c, and the job-specific attachable evidence type master 106d from the job used by the user, and determines the system classification of files that can be attached on an attachment basis.

[0053] When a file is attached on the attachment list screen MB, the attachment details screen display unit 102d displays an attachment details screen MC (see FIG. 12) for inputting detailed information about the file to be attached to the slip. In addition, the attachment details screen display unit 102d displays only the system classifications of files that the attachment control unit 102c has determined can be attached on an attachment unit basis in a format that the user can select, and also displays a list of only the types of vouchers that the user can attach.

[0054] When a button for registering an attached file is selected on the attachment list screen MB, the work table generation unit 102e generates a supporting document work table 106g that includes 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 entered on the attachment details screen MC, and binary information about the attached file.

[0055] The linking table etc. generating unit 102f generates a voucher linking table 106j that includes a voucher number for identifying a registered voucher and the file identification data in the work table in a linked manner, a voucher information table 106h that includes, when the file type identification category in the voucher voucher work table 106g is a category that indicates a voucher file, the file identification data in the voucher work table 106g, the file type identification category, and detailed information about the attached file, and a file identification data in the voucher voucher work table 106g that includes binary information about the attached file. If the file type identification category in the supporting document image table 106i and the supporting document voucher work table 106g is a category indicating a non-support file, a workflow case table 106k containing the voucher number and case identification data for identifying each case in the workflow, a file information table 106l containing the case identification data and detailed information about the attached files in the supporting document voucher work table 106g, and a file image table 106m containing the case identification data and binary information about the attached files in the supporting document voucher work table 106g are created.

[0056] When the voucher approval screen MD (see FIG. 19) is launched, the approval information display unit 102g acquires the contents of the voucher linked to the voucher number in the workflow case table 106k from the journal entry detail table 106n, and if a voucher linked to the case is registered in the evidence linking table 106j, acquires file identification data linked to the voucher number in the workflow case table 106k from the evidence linking table 106j, and further acquires detailed information and binary information linked to the acquired file identification data from the evidence information table 106h and the evidence image table 106i, respectively, and registers other files linked to the case in the file information table. If the file is registered, binary information linked to the case identification data in the workflow case table 106k is obtained from the file image table 106l, and if the file selected on the invoice approval screen MD is a voucher file, the contents of the obtained invoice, detailed information obtained from the voucher information table 106h, and binary information obtained from the voucher image table 106i are displayed on the invoice approval screen MD, and if the file selected on the invoice approval screen MD is a non-voucher file, the contents of the obtained invoice and binary information obtained from the file image table 106m are displayed on the invoice approval screen MD.

[0057] When search conditions are entered on the evidence search screen ME (see Figure 20), which is a screen for searching evidence files, the evidence search result display unit 102h searches the evidence information table 106h for information about evidence files that match the entered search conditions and displays the search results on the evidence search screen ME.

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

[0059] Here, a specific example of the processing executed by the file registration support device 100 will be described with reference to FIGS.

[0060] FIG. 2 is a diagram illustrating an example of a transaction flow for product sales in which files can be registered using the file registration support device 100 according to this embodiment. FIG. 2 illustrates transaction flow A, in which product orders and receipts are processed via email or the Internet; transaction flow B, in which orders from business partners are sent on paper; and transaction flow C, in which orders are placed by phone and the accounting department collectively prepares the documents required for the transaction. In the file registration support device 100 according to this embodiment, an administrator can set a system-specific system correspondence control master 106b, a file attachment control master 106c, and a job-specific attachable voucher type master 106d that correspond to the transaction flow with customers, thereby preventing file registration using an incorrect combination of registration screen / system classification / voucher type.

[0061] 3 is a diagram illustrating a screen when a user selects a job for registering a slip using a system that the user can use. In this specification, a case will be described in which a user (a person in charge, an accounting department) who uses the financial accounting system in a client that uses a sales system and a financial accounting system attaches a file when registering a slip using the file registration support device 100 according to this embodiment.

[0062] When a user (accountant B) selects a job (journal entry input) using the financial accounting system shown in Fig. 3, the attachment button display control unit 102a performs processing to determine whether or not the "attachment button" can be displayed on the slip input screen MA. Fig. 8 is a flowchart showing an example of processing to determine whether or not the attachment button can be displayed for each attachment unit, performed by the attachment button display control unit 102a.

[0063] As shown in Fig. 8, when a user starts a job, the attachment button display control unit 102a refers to the job master 106a and acquires the "system" used by the user using the "job" as a key (step S1). Fig. 4 is a diagram showing an example of the job master 106a. In the job master 106a in Fig. 4, the "system" corresponding to the "job" and "journal entry input" is the "financial accounting system."

[0064] Next, the attachment button display control unit 102a refers to the system-specific regulatory control master 106b and acquires the "usable category" using "system" as a key (step S2). FIG. 5 is a diagram showing an example of the system-specific regulatory control master 106b. FIG. 5 shows three system-specific regulatory control masters 106b-1, 106b-2, and 106b-3 corresponding to transaction flows. The file registration support device 100 according to this embodiment stores the system-specific regulatory control master 106b corresponding to the client's transaction flow. Here, the case of transaction flow C will be explained as an example. In the system-specific regulatory control master 106b-3 in FIG. 5, for the "system" financial accounting system, the "usable category (category where supporting document file attachments are possible)" is "○ (attachment possible)" for electronic files and "○ (attachment possible)" for scanner save.

[0065] Next, the attachment button display control unit 102a refers to the file attachment control master 106c and acquires the usable classification for each "attachment unit" using "job" as a key (step S3). FIG. 6 is a diagram showing an example of the file attachment control master 106c. FIG. 6 shows three file attachment control masters 106c-1, 106c-2, and 106c-3 corresponding to transaction flows. As described above, in order to explain the case of transaction flow C, the file attachment control master 106c-3 in FIG. 6 will be referred to. In the file attachment control master 106c-3 in FIG. 6, for "job" and "financial accounting system," for "attachment unit" and "slip unit," electronic transaction is "○ (attachment allowed)," scanner storage is "× (attachment not allowed)," and other attachments is "○ (attachment allowed)." For "attachment unit" and "detail unit," electronic transaction is "× (attachment not allowed)," scanner storage is "○ (attachment allowed)," and other attachments is "× (attachment not allowed)."

[0066] Furthermore, the attachment button display control unit 102a determines whether or not to display the "Attachment button" for each "Attachment unit" based on the values ​​acquired in steps S2 and S3 (step S4). The determination in step S4 is made by looping the number of times equal to the number of attachment units stored in the system-specific regulation control master 106b (step S5). In the system-specific regulation control master 106b-3 in transaction flow C described here, two attachment units, "voucher unit" and "detail unit," are stored, so a determination is made for each "voucher unit" and "detail unit." It is determined whether or not the "Attachment button" can be displayed for the corresponding attachment unit (step S6), and if it is determined that it cannot be displayed (step S6: Yes), the "Attachment button" for the corresponding attachment unit is hidden on the voucher input screen MA (step S7). If it is determined that display is possible (Step S6: No), proceed to Step S8 and determine whether the next attachment unit exists (Step S8). If the next attachment unit exists (Step S8: Yes), repeat from Step S6. If the next attachment unit does not exist (Step S8: No), display the slip input screen MA reflecting the above determination result and end the process.

[0067] The determination of whether to display the "Attachment button" is made for supporting documents files, i.e., electronic transaction files and scanner-saved files. If either the system-specific regime control master 106b or the file attachment control master 106c indicates that attachments are not permitted, then it is determined that attachments are not permitted; if both allow attachments, then it is determined that attachments are permitted. For other files, the value of the file attachment control master 106c is used. If all regime classifications determine that attachments are not permitted, then the "Attachment button" for that attachment unit is hidden. For the system-specific regime control master 106b-3 and the file attachment control master 106c-3, if the attachment unit is a slip, then both electronic transaction files are permitted, so it is determined that attachments are permitted; for scanner-saved files, it is determined that attachments are not permitted, so it is determined that attachments are permitted; and for other files, it is determined that attachments are permitted, so it is determined that attachments are permitted, and the "Attachment button" is displayed because attachments are permitted in both regime classifications. In addition, when the slip unit is a detail unit, the electronic transaction unit is judged as "Attachment not possible" because the file attachment control master 106c-3 does not allow attachments, both scanner saved files are judged as "Attachment possible" because they can be attached, other files are judged as "Attachment not possible" because the file attachment control master 106c-3 does not allow attachments, and attachments are possible in one system classification, so the "Attach button" is displayed.

[0068] FIG. 9 is a diagram showing an example of a slip input screen MA. On the slip input screen MA in FIG. 9, an "Attach button" for attaching a file on a slip-by-slip basis is located in the header, and an "Attach button" for attaching a file on a detail-by-detail basis is located in the detail. According to the flowchart in FIG. 8, if a file cannot be attached on a slip-by-slip basis, the "Attach button" in the header is hidden, and if a file cannot be attached on a detail-by-detail basis, the "Attach button" in the detail is hidden. In this embodiment, the administrator sets the master data for the system classification (electronic transaction file, scanner-saved file, other attachment file) and supporting document type (invoice, receipt) that can be attached for each business system, job, and attachment unit, and determines whether or not to display the attachment button for each attachment unit. If attachment is not possible, the attachment button is hidden, thereby preventing erroneous file registration.

[0069] When the user presses the "Attach button" for each attachment on the slip entry screen MA in Fig. 9, the attachment list screen display unit 102b displays an attachment list screen MB for attaching files. Fig. 10 is a diagram showing an example of the attachment list screen MB. There are several ways to attach a file on the attachment list screen MB: press the "Select from Explorer" button to select the file you want to attach; drag and drop the file you want to attach to the "You can drag and drop files here" section; press the "Select from files photographed on a document" button to upload a file photographed with a mobile device; or press the "Select from previously uploaded files" button to reattach a file that was deleted after being registered in the electronic bookkeeping system.

[0070] When a file is attached on the attachment list screen MB of Fig. 10, the attachment control unit 102c performs a process of acquiring the system classification of the file that can be attached on an attachment basis. Fig. 11 is a flowchart showing an example of a process of acquiring the system classification of the file that can be attached on an attachment basis by the attachment control unit 102c.

[0071] When a user attaches a file on the attachment list screen MB shown in Fig. 10, the attachment detail process is started. The attachment control unit 102c refers to the job master 106a and acquires the "system" used by the user using the "job" as a key (step S11). In the job master 106a shown in Fig. 4, the "system" corresponding to the "job" and "journal entry" is the "financial accounting system."

[0072] Next, the attachment file control unit 102c refers to the system-specific regulatory control master 106b and acquires the "usable category" using "system" as a key (step S12). In the system-specific regulatory control master 106b-3 in Fig. 5, for "system" and "financial accounting system," the "usable category (category where evidence file attachments can be made)" is "○ (attachment allowed)" for electronic files and "○ (attachment allowed)" for scanner storage.

[0073] Next, the attachment control unit 102c refers to the file attachment control master 106c and acquires the usable classification for each "attachment unit" using "job" as a key (step S13). The acquired usable classification for each "attachment unit" is the "attachment unit" of the "attachment button" that uploaded the file. On the slip input screen MA of Figure 9, if the file was uploaded using the "attachment button" in the header section, the "attachment unit" is the slip unit, and if the file was uploaded using the "attachment button" in the details section, the "attachment unit" is the detail unit.

[0074] Furthermore, the attachment control unit 102c determines whether or not the file can be attached in the uploaded "attachment unit" based on the values ​​acquired in steps S12 and S13 (step S14).

[0075] The determination of whether or not a file can be attached on an "attachment unit" is made for evidence files, i.e., electronic transaction files and scanner-saved files. If either the system-specific system correspondence control master 106b or the file attachment control master 106c indicates that attachment is not permitted, it is determined that attachment is permitted if both are permitted. For other files, the value of the file attachment control master 106c is used.

[0076] For example, if a file is uploaded with the "attachment unit" set to detail unit, the electronic transaction unit is determined to be "attachment not allowed" because the file attachment control master 106c-3 does not allow attachments, both scanner-saved files are "attachment allowed" because they can be attached, and other files are determined to be "attachment not allowed" because the file attachment control master 106c-3 does not allow attachments.

[0077] The attachment details screen display unit 102d locks the selection of files of the system classification that the attachment control unit 102c has determined cannot be attached on the attachment details screen MC (step S15). Figure 12 is a diagram showing an example of the attachment details screen MC. In the file type selection area C-1 on the attachment details screen MC, electronic transactions and other transactions of the system classification that the attachment control unit 102c has determined cannot be attached are displayed in gray out and cannot be selected. As in the attachment details screen of Figure 12, in addition to locking the selection of files of the system classification that has been determined to be unable to be attached, only selectable classifications may be displayed.

[0078] The attachment file control unit 102c also references the job-specific attachable voucher type master 106d using "job" and "attachment unit" as keys to acquire the voucher type (step S16). FIG. 7 is a diagram showing an example of the job-specific attachable voucher type 106d. FIG. 7 illustrates three file attachment control masters 106d-1, 106d-2, and 106d-3 corresponding to transaction flows. As described above, since the case of transaction flow C is explained here, the job-specific attachable voucher type master 106d-3 in FIG. 7 is referenced. In the job-specific attachable voucher type master 106d-3 in FIG. 7, the attachable voucher types for "job," "financial accounting system," "attachment unit," and "detail unit" are "delivery note," "invoice," and "receipt."

[0079] The attachment details screen display unit 102d displays a list of only the types of evidence that the user can attach, which have been acquired by the attachment control unit 102c, on the attachment details screen MC (step S17). As shown in Fig. 12, the attachment details screen display unit 102d displays a list of only the types of evidence that the user can attach in the selection area C-2 for the type of evidence on the attachment details screen MC.

[0080] In the file registration support device 100 of this embodiment, the system classification (electronic transaction files, scanner-saved files, other attachment files) and supporting document type (invoice, receipt) that can be attached for each business system, job, and attachment unit are master-set by the administrator, thereby preventing employees with little knowledge of the system and operations from registering files using an incorrect combination of registration screen / system classification / support document type. In addition, in the file registration support device 100 according to this embodiment, as shown in Fig. 21, any file can be registered from the same screen, and evidence files such as electronic transaction files and scanner-saved files can be stored in the electronic bookkeeping system, which is a dedicated DB separate from the normal business DB, to meet the requirements of the Electronic Bookkeeping Act, while other non-evidence files can be stored in the normal business files. 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.

[0081] In addition, the attachment details screen display unit 102d displays a list of items according to the type of attached file on the attachment details screen MC, and if the contents of the invoice have been entered on the invoice input screen MA for some of the displayed items, the contents of the invoice entered on the invoice input screen MA (see Figure 9) are displayed as the item value.

[0082] The attachment details screen display unit 102d may acquire a list of items according to the type of attached file according to a fixed rule, or may acquire the list by referring to the display item setting table 106o (see FIG. 18), as will be described below. That is, the attachment details screen display unit 102b may acquire a list of items according to the type of attached file from the display item setting table 106o, which includes a list of items to be displayed on the attachment details screen for each file type.

[0083] Specifically, when a file type (=regulation classification) is selected in the file type selection area C-1 of the attachment details screen MC, the attachment details screen display unit 102d switches the display / hide of the input items by retrieving items corresponding to the selected regulation classification from the display item setting table 106o.

[0084] Here, the attachment details screen display unit 102d acquires document type identification data (initial display document code) linked to the system identification data (system name) for the system from the screen control table 106e (see FIG. 13). Next, the attachment details screen display unit 102d acquires the document name and date-related item name (transaction date label name) linked to the acquired document type identification data (document code) from the evidence type table 106f (see FIG. 13). Finally, the attachment details screen display unit 102b displays the acquired document name and date-related item name (transaction date label name).

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

[0086] When the "Register" button for the last file is pressed on the attachment details screen MC, the attachment list screen display unit 102b displays the attachment list screen again, which includes a list of the attached files and their corresponding file types. On the attachment list screen, the attached files and their corresponding file types (=registry classification) can be confirmed.

[0087] When the button for registering the attached file (the "Register" button) is selected on the attached file list screen that is displayed again, the work table generation unit 102e generates a supporting document slip work table 106g (see FIG. 14) that includes file identification data (support document Guid) for the attached file, file type identification classification (registry classification) for the attached file, detailed information about the file entered on the attached file details screen (file name, extension, document code, receipt date, transaction date, business partner name, amount, product name, resolution, gradation, TS presence / absence, TS assignment date and time, and originating system), and binary information (file image) about the attached file. The work table generation unit 102e also stores the same WK key (work key) in the supporting document slip work table 106g.

[0088] Specifically, detailed information and file images of the attached supporting documents are stored in the supporting document work table 106g. Once storage is complete, the screen returns to the business system screen from which the transition originated. The items stored differ depending on the radio button selected on the attachment details screen MB. In other words, the columns in the supporting document work table 106g that are updated differ depending on the system classification selected on the attachment details screen MB. For example, if a scanner-saved file is selected, information is stored in the resolution and gradation columns.

[0089] When the button for registering the attached file (the "Register" button) is selected on the re-displayed attachment file list screen, the linking table etc. generation unit 102f re-displays the slip input screen MA. Then, when the button for registering the slip (the "Register" button) is selected on the re-displayed slip input screen, the linking table etc. generation unit 102h generates each data.

[0090] The type of data generated differs depending on the system classification selected on the attachment details screen MC (the storage location of the information in the supporting document work table 106g differs).

[0091] The linking table etc. generation unit 102f acquires file identification data (evidence Guid) and file type identification classification (regulation classification) from the evidence voucher worktable 106g as information necessary for generating the evidence linking table 106j. Furthermore, the linking table etc. generation unit 102f generates the evidence linking table 106j that includes, in association with each other, the voucher number for identifying the registered voucher and the file identification data (evidence Guid) in the evidence voucher worktable 106g (see FIG. 16). Note that the linking table etc. generation unit 102f may further include the file type identification classification (regulation classification) in the evidence voucher worktable 106g in the evidence linking table 106j.

[0092] In addition, the linking table etc. generation unit 102f checks the type of file type identification category (regulation category) in the supporting document slip worktable 106g. In the supporting document slip worktable 106g (see FIG. 14), the first record (regulation category: electronic transaction) and the second record (regulation category: scanner storage) correspond to records of the regulation requirement file. In this case, the linking table etc. generation unit 102h generates the supporting document information table 106h and the supporting document image table 106i (see FIG. 15) based on the first and second records in the supporting document slip worktable 106g.

[0093] On the other hand, the record in the third row (regulation classification: other attachments) of the supporting document worktable 106g corresponds to the record of other attachment files. In this case, the linking table etc. generation unit 102f generates the workflow case table 106k, the file information table 106l, and the file image table 106m, or generates the file information table 106l and the file image table 106m (see zu17), based on the record in the third row in the supporting document worktable 106g.

[0094] When the file type identification category (regulation category) in the supporting document voucher worktable 106g is a category indicating a supporting document file (electronic transaction or scanner storage), the linking table etc. generation unit 102f generates a supporting document information table 106h (see Figure 15) containing the file identification data (support document Guid) in the supporting document voucher worktable 106g, the file type identification category (regulation category) in the supporting document voucher worktable 106g, and detailed information about the attached file in the supporting document voucher worktable 106g (file name, extension, document code, receipt date, transaction date, amount, product name, business partner name, resolution, gradation, TS presence / absence, TS assignment date and time, originating system, and deleted flag), and a supporting document image table 106i (see Figure 15) containing the file identification data (support document Guid) in the supporting document voucher worktable 106g and binary information (file image) about the attached file in the supporting document voucher worktable 106g.

[0095] If the file type identification category (regulation category) in the supporting document work table 106g is a category indicating a non-supporting document file (other attachments), the linking table etc. generation unit 102f further checks whether or not a workflow system is used. This is because the storage location and storage method for other files differ depending on whether or not each business system uses a workflow system. All updates to other files are delegated to the business system. Each business system saves file images obtained by common processing in the electronic bookkeeping system.

[0096] When the file type identification category (regulatory category) in the supporting document voucher worktable 106g is a category indicating a non-supporting document file (other attachments) and a workflow system is being used, the linking table etc. generation unit 102f generates a workflow case table 106k including the document number (business document number), case identification data (case Guid), etc., a file information table 106l including the case identification data (case Guid) and detailed information about the attached files in the supporting document voucher worktable 106g (attachment file names and notes), and a file image table 106m (see Figure 17) including the case identification data (case Guid) and binary information (file images) about the attached files in the supporting document voucher worktable 106g.

[0097] In addition, when the file type identification category (regulatory category) in the supporting document voucher worktable 106g is a category indicating a non-supporting document file (other attachments) and a workflow system is not being used, the linking table etc. generation unit 102f generates a file information table 106l containing the document number and detailed information about the attached file in the supporting document voucher worktable 106g (attachment file name and memo), and a file image table 106m containing the document number and binary information (file image) about the attached file in the supporting document voucher worktable 106g.

[0098] Furthermore, the linking table etc. generating unit 102f generates a journal entry detail table 106n (see FIG. 16) that includes the voucher number and the contents of the voucher entered on the voucher input screen MA. By generating the journal entry detail table 106n, the voucher is confirmed by the voucher registration process of each business system.

[0099] According to the file registration support device 100 of this embodiment, voucher files and non-voucher files can be stored in different locations. That is, information on voucher files can be stored in the voucher information table 106h and the voucher image table 106i, while information on non-voucher files can be stored in the workflow case table 106k, the file information table 106l, and the file image table 106m. Storing voucher files and non-voucher files in different locations in this way has the effect of facilitating the approval of slips and the search for vouchers, as described below.

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

[0101] In order to display information when approving a slip, 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 slip approval screen MD, which is the screen for the person in charge to approve the slip, is launched, the approval information display unit 102g acquires information in advance as follows. Figure 19 is a diagram showing an example of the slip approval screen MD.

[0102] The approval information display unit 102g acquires the contents of the voucher (debit account title, debit amount, etc.) linked to the voucher number in the workflow case table 106k from the journalization detail table 106n.

[0103] In addition, if a voucher linked to the case is registered in the voucher linking table 106j, the approval information display unit 102g obtains from the voucher linking table 106j the file identification data (voucher Guid) linked to the slip number in the workflow case table 106k, and further obtains from the voucher information table 106h and the voucher image table 106i, respectively, detailed information (file name, extension, document code, receipt date, etc.) and binary information (file image) linked to the obtained file identification data (voucher Guid).

[0104] Then, if other files linked to the case are registered in the file information table 106l, the approval information display unit 102g obtains binary information (file image) linked to the case identification data (voucher Guid) in the workflow case table 106k from the file image table 106m.

[0105] The approval information display unit 102g then displays the acquired information on the slip approval screen MD in the following manner.

[0106] If the file selected on the voucher approval screen MD is a voucher file (regulatory requirements file), the approval information display unit 102g displays the contents of the acquired voucher, detailed information acquired from the voucher information table 106h, and binary information acquired from the voucher image table 106i on the voucher approval screen MD.

[0107] Fig. 19 is a diagram showing the slip approval screen MD when the cursor is placed on the "File A.pdf" button. As shown in Fig. 19, when File A, which is a system requirements file, is selected, the approval information display unit 102g displays the "Journal Entry Slip Confirmation" area on the left side of the screen as the slip content, displays an area on the right side of the screen containing the document name etc. as detailed information, and displays an image of the delivery note in the center of the screen as binary information.

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

[0109] According to the file registration support device 100 of this embodiment, when approving a voucher, the contents of the voucher (in this example, the contents of the "Journal Entry Voucher Confirmation"), an image of the supporting document linked to the voucher (in this example, an image of the delivery note), detailed information on the supporting document linked to the voucher (in this example, detailed information on the delivery note), and an image of the non-supporting document linked to the voucher can be displayed on a single screen (in this example, the voucher approval screen MD). This allows the person in charge of approval to approve the voucher after accurately and immediately checking a series of information related to the voucher, thereby reducing the burden on the person in charge of approval and eliminating mistakes in the approval process.

[0110] Next, we will explain how to search for supporting documents (displaying a list of electronic supporting documents). By searching for supporting documents, you can view all supporting documents stored in the electronic bookkeeping system. The list of electronic supporting documents has two jobs: one for the person in question and one for the accounting staff.

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

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

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

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

[0115] Below, a specific description will be given of a search for evidence performed from the evidence search screen ME (see FIG. 20), which is a screen for searching for the evidence file, under the following assumptions. It is assumed that the evidence information table 106h shown in Fig. 15 exists as a search target. The evidence information table 106h is a table to which files are uploaded not only from the financial accounting system but also from the sales system. Search conditions can be entered in the area on the left side of the document search screen. The items displayed as search results are, for example, as shown in Figure 35. The search results are displayed in the area on the right side of the document search screen.

[0116] When search conditions are entered on the evidence search screen ME, the evidence search result display unit 102h searches the evidence information table 106h for information about evidence files that match the entered search conditions, and displays the search results on the evidence search screen ME.

[0117] We will explain the buttons located in the footer section (bottom part) of the Evidence Search Screen ME. The "Add Evidence" button e1 is a button for directly uploading electronic transaction files to the electronic bookkeeping system without linking them to a slip. When the "Add Evidence" button e1 is pressed, the screen transitions to the Attachment List Screen MB and the Attachment Details Screen MC.

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

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

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

[0121] Furthermore, according to the file registration support device 100 of this embodiment, it is possible to search for the desired voucher from the voucher information table 106h, which aggregates vouchers registered from multiple systems (in this example, including not only the financial accounting system but also the sales system), thereby enabling a comprehensive and thorough search of all registered vouchers.

[0122] Finally, we will explain how to assign a timestamp. When a timestamp is assigned, the presence or absence of a timestamp (TS presence or absence) and the timestamp assignment date and time (TS assignment date and time) in the evidence information table 106h are updated. By collecting evidence in the electronic bookkeeping system, it is possible to use a predetermined authenticated timestamp service.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0138] 100 File registration support device 102 Control section 102a Attachment button control section 102b Attachment list screen display section 102c Attachment control section 102d Attachment details screen display section 102e Work table generation unit 102f Linking table generation unit 102g Approval information display section 102h Evidence search results display section 104 Communication interface unit 106 Storage section 106a Job Master 106b System-specific control master 106c File Attachment Control Master 106d Master of types of vouchers that can be attached by job 106e Screen Control Table 106f Evidence type table 106g Voucher Work Table 106h Evidence information table 106i Evidence Image Table 106j Evidence linking table 106k workflow matter table 106l File Information Table 106m File Image Table 106m Journal Entry Detail Table 106o Display Item Setting Table 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A file registration support device that supports the registration of evidence files and non-evidence files from the same screen, and that includes a control unit, a job master that stores a system used by a user and a job in association with each other; a system-specific system-based control master that stores the system and the attachable evidence file in association with each other; a file attachment control master that stores the job, a file attachment unit, and an attachable file in association with each other; is accessible to The control unit an attachment file list screen display means for displaying an attachment file list screen for attaching files when a button for attaching a file is selected on a slip input screen for inputting the contents of the slip; an attachment file control means for determining a system classification of a file that can be attached in units of attachments by referring to the job master, the system-specific system correspondence control master, and the file attachment control master from a job used by a user; an attachment file details screen display means for displaying an attachment file details screen for inputting detailed information about the file to be attached to the slip when a file is attached on the attachment file list screen; Equipped with The file registration support device is characterized in that the attachment file detail screen display means displays only the system classification of files that the attachment file control means has determined can be attached on an attachment unit basis in a format that can be selected by the user.

2. an attachment button display control means for referencing the job master, the system-specific system correspondence control master, the file attachment control master, and the job-specific attachable document type master from the job used by the user, determining whether or not to display an attachment button for each attachment unit, and displaying it on the slip input screen; The file registration support device according to claim 1 , comprising:

3. a job-specific attachable evidence type master that stores the job, the file attachment unit, and the attachable evidence type in association with each other; is accessible to The attachment file control means refers to the job master, the system-specific system correspondence control master, the file attachment control master, and the job-specific attachable evidence type master from the job used by the user, and acquires the evidence type that can be attached in the attachment unit; 2. The file registration support device according to claim 1, wherein said attachment file detail screen display means displays a list of only the types of evidence that can be attached by the user and that are acquired by said attachment file control means.

4. A file registration support method executed by a file registration support device having a control unit, which supports the registration of evidence files and non-evidence files from the same screen, a job master that stores a system used by a user and a job in association with each other; a system-specific system-based control master that stores the system and the attachable evidence file in association with each other; a file attachment control master that stores the job, a file attachment unit, and an attachable file in association with each other; is accessible to Executed by the control unit, an attachment list screen display step of displaying an attachment list screen for attaching files when a button for attaching a file is selected on a slip input screen for inputting the contents of the slip; an attachment file control step of referring to the job master, the system-specific regulation control master, and the file attachment control master from the job used by the user, and determining the regulation classification of the file that can be attached in the attachment unit; an attachment details screen display step that displays an attachment details screen for inputting detailed information about the file to be attached to the slip when a file is attached on the attachment list screen; Including, The file registration support method is characterized in that the attachment file detail screen display step displays only the system classification of files that can be attached in the attachment unit determined in the attachment file control step in a format that can be selected by the user.

5. A file registration support program executed by a file registration support device having a control unit, which supports the registration of evidence files and non-evidence files from the same screen, a job master that stores a system used by a user and a job in association with each other; a system-specific system-based control master that stores the system and the attachable evidence file in association with each other; a file attachment control master that stores the job, a file attachment unit, and an attachable file in association with each other; is accessible to To be executed by the control unit, an attachment list screen display step of displaying an attachment list screen for attaching files when a button for attaching a file is selected on a slip input screen for inputting the contents of the slip; an attachment file control step of referring to the job master, the system-specific regulation control master, and the file attachment control master from the job used by the user, and determining the regulation classification of the file that can be attached in the attachment unit; an attachment details screen display step that displays an attachment details screen for inputting detailed information about the file to be attached to the slip when a file is attached on the attachment list screen; Including, The file registration support program is characterized in that the attachment file detail screen display step displays only the system classification of files that can be attached in the attachment unit determined in the attachment file control step in a format that can be selected by the user.

Images