Business support device, business support method, and business support program
The business support device manages journal entry and supporting document data with approval status information, reducing approver workload by allowing separate review of final-approved documents, thus enhancing efficiency and accuracy in the approval process.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- OBIC CO LTD
- Filing Date
- 2024-12-27
- Publication Date
- 2026-07-09
AI Technical Summary
The burden on approvers increases due to the need to search for and approve changes in vouchers such as invoices and receipts, as they are unaware of the correction points, leading to inefficiencies in the approval process.
A business support device and method that includes an acquisition unit to manage journal entry and supporting document data with approval status information, an unapproved list display control unit to show pending approvals, and an inquiry screen to review application content, allowing approvers to focus on final-approved documents.
Reduces the workload on approvers by enabling separate review of supporting documents and managing approval status, ensuring accurate accounting information during audits.
Smart Images

Figure 2026115229000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a business support device, a business support method, and a business support program.
Background Art
[0002] Patent Document 1 (Japanese Unexamined Patent Application Publication No. 2024-155947) discloses an information processing device that facilitates the selection of settlement means including cashless settlement in transactions between businesses and enables the setting of settlement means for each trading partner.
[0003] In paragraph 0062 of this Patent Document 1, for invoices created in the billing process in a workflow, in the case of settlement by bank transfer, since the settlement has not been completed, the invoice data of the invoice is generated and the account information of the transfer destination is described, and in the case of credit card settlement, since the settlement has been completed, the technique of generating the invoice data of the receipt is disclosed.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0005] Here, since vouchers such as invoices and receipts are important accounting information, it is preferable to obtain the approval of an approver when storing them in the system. At this time, since the approver is not aware of the correction points, even when only vouchers are added by slip correction, it is necessary to start a slip check by searching for the changed points in the slip content, and there is a problem that the burden of the approver's approval work increases.
[0006] This invention has been made in view of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that can reduce the burden on approvers in the process of approving evidence. [Means for solving the problem]
[0007] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention acquires journal entry data stored in the journal entry data storage unit with approval status information of "pending" added, which indicates that final approval by the approver has been completed or that approval by the approver is pending, along with a unique voucher number, predetermined application content, and application type of journal entry voucher indicating that it is journal entry data. In addition, it acquires supporting document data for which an additional supporting document application is made for the journal entry data after final approval, which includes approval status information of either "final approval" indicating that final approval by the approver has been completed or that approval by the approver is pending, a unique voucher number, and supporting document for the journal entry voucher after final approval. The system includes: an acquisition unit that acquires evidence data stored in the evidence data storage unit with an additional attachment application type indicating that it is evidence data for an additional application, and to which approval status information of the application has been added; an unapproved list display control unit that displays a list of data including the application type, voucher number, and approval status information of the acquired journal entry data and evidence data to which approval status information of the application has been added via a display unit; and an inquiry screen display control unit that displays, via an application content additional evidence inquiry screen, the application content of the journal entry data corresponding to the list data selected by the operator from the displayed list data, or the application content of the journal entry data that has received final approval and was the source of the application for the evidence and evidence data indicated by the evidence data corresponding to the list data selected by the operator.
[0008] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the business support method according to the present invention is a method in which the acquisition unit acquires journal entry data that has been stored in the journal entry data storage unit with approval status information of "application in progress" attached, which indicates that final approval by the approver has been completed, or approval in progress, which indicates that approval by the approver is pending, along with a unique voucher number, predetermined application content, and application type of journal entry voucher indicating that it is journal entry data, and also provides supporting data for which an application for additional supporting documents is submitted for the journal entry data after final approval, which includes approval status information of "approved" indicating that final approval by the approver has been completed, or approval in progress, which indicates that approval by the approver is pending, along with a unique voucher number, and provides supporting data for which an application for additional supporting documents is submitted for the journal entry voucher after final approval. The system includes: an acquisition step to acquire document data stored in the document data storage unit with an additional attachment application type indicating that an application is pending, to which approval status information of the application is attached; an unapproved list display control step in which the unapproved list display control unit displays a list of data via the display unit, including the application type, voucher number, and approval status information of the journal entry data and document data to which approval status information of the application is attached, acquired in the acquisition step; and an inquiry screen display control step in which the inquiry screen display control unit displays, via the application content additional document inquiry screen, the application content of the journal entry data corresponding to the list data selected by the operator from the list data displayed by the operator, or the application content of the journal entry data that has received final approval and was the source of the application for the document and document data indicated by the document data corresponding to the list data selected by the operator.
[0009] Furthermore, in order to solve the above-mentioned problems and achieve the objective, the business support program according to the present invention retrieves journal entry data stored in the journal entry data storage unit, which has approval status information of "pending" added to it, from among the journal entry data that has approval status information of "pending" added to it, which is either "finally approved" indicating that the final approval by the approver has been completed, or "pending" indicating that the approval by the approver is pending, a unique voucher number, predetermined application content, and an application type of journal entry voucher indicating that it is journal entry data, and also retrieves supporting document data for which an application for additional supporting documents is submitted for the journal entry data after final approval, which has approval status information of either "finally approved" indicating that the final approval by the approver has been completed, or "pending" indicating that the approval by the approver is pending, a unique voucher number, and a journal entry voucher after final approval. The system functions as an acquisition unit that acquires evidence data stored in the evidence data storage unit with an additional attachment application type indicating that it is evidence data for which an additional application for evidence is being submitted, and which has approval status information of the application attached; an unapproved list display control unit that displays a list of data including the application type, voucher number, and approval status information of the acquired journal entry data and evidence data with approval status information attached via a display unit; and an inquiry screen display control unit that displays the application details of the journal entry data corresponding to the list data selected by the operator from the displayed list data, or the application details of the journal entry data that has received final approval and was the source of the application for the evidence and evidence data indicated by the evidence data corresponding to the list data selected by the operator, via an application content additional evidence inquiry screen. [Effects of the Invention]
[0010] This invention can reduce the burden on approvers in the process of approving supporting documents. [Brief explanation of the drawing]
[0011] [Figure 1] Figure 1 is a block diagram showing the hardware configuration of the business support device according to the embodiment. [Figure 2] Figure 2 is a functional block diagram showing the functions of the business support device according to the embodiment. [Figure 3]Figure 3 illustrates the process in the comparative example where, if supporting documents arrive after the final approval of the voucher, the previous black voucher is canceled out with a red voucher, and a new black voucher is created with the supporting documents attached. [Figure 4] Figure 4 is a diagram illustrating the operation of the business support device of the embodiment when supporting documents are added after the final approval of a document. [Figure 5] Figure 5 is a diagram illustrating the process of adding supporting documents before final approval of a document in a comparative example. [Figure 6] Figure 6 shows how an error occurs when a document prior to final approval is added in attachment mode to the business support device 1 of the embodiment. [Figure 7] Figure 7 shows the journal entry data displayed in the attachment mode after final approval, where the journal entry details cannot be modified. [Figure 8] Figure 8 shows the attachment details screen where additional supporting documents are attached. [Figure 9] Figure 9 shows the document data generated based on the image data and accompanying information of the additional documents to be attached, which are entered via the attachment details screen. [Figure 10] Figure 10 shows an example of the unapproved list screen. [Figure 11] Figure 11 shows an example of the application details additional support document inquiry screen. [Figure 12] Figure 12 shows how, in a general ledger details inquiry, only "Final Approval" supporting document data is displayed. [Figure 13] Figure 13 is a flowchart showing the operation flow in the modification mode of the business support device according to the embodiment. [Figure 14] Figure 14 shows an example of an error message indicating that the journal entry data specified in the modification mode cannot be modified, which is displayed when final approval has been completed. [Figure 15] Figure 15 shows an example of journal entry data that is displayed as editable when approval for the specified journal entry data is not yet complete (pending). [Figure 16] FIG. 16 is a flowchart showing the flow of operations in the attachment mode of the business support apparatus according to the embodiment. [Figure 17] FIG. 17 is a diagram showing an example of an error message that disables the additional attachment of supporting documents, which is displayed when the approval of the journal data specified in the attachment mode is under application. [Figure 18] FIG. 18 is a diagram showing an example of the journal data that is displayed on the journal input screen with the journal details being in a non-editable state during the attachment mode. [Figure 19] FIG. 19 is a diagram showing various data at the time of new registration of a slip. [Figure 20] FIG. 20 is a diagram showing various data at the time of slip approval. [Figure 21] FIG. 21 is a diagram showing various data when performing additional attachment of supporting documents in the correction mode. [Figure 22] FIG. 22 is a diagram showing various data at the time of additional attachment of supporting documents in the attachment mode. [Figure 23] FIG. 23 is a diagram showing various data when the supporting documents additionally attached in the attachment mode are approved. [Figure 24] FIG. 24 is a flowchart for explaining the data update process for the update destination corresponding to the processing mode. [Figure 25] FIG. 25 is a diagram showing the update destinations of data in the new mode and the correction mode. [Figure 26] FIG. 26 is a diagram showing the update destination of data in the attachment mode. [Figure 27] FIG. 27 is a diagram for explaining the control to display only the finally approved supporting documents when the detail inquiry button of the general ledger is operated.
Embodiments for Carrying Out the Invention
[0012] Hereinafter, a business support apparatus according to an embodiment to which the present invention is applied will be described in detail based on the drawings. Note that the present invention is not limited to the following embodiments.
[0013] (overview) In the document storage process, if the relevant voucher has been completed to the final approval stage, attaching it by modifying the voucher is prohibited from an internal control perspective, resulting in a workload due to the creation of red and black vouchers. Furthermore, generating black vouchers, red vouchers, and subsequent black vouchers increases the number of vouchers, making it difficult to verify the original transaction details.
[0014] Furthermore, since supporting documents contain important accounting information, it is preferable to obtain approval from an approver before storing them in the system. However, because approvers are unaware of the changes, even if only supporting documents are added due to a document modification, they must start the document check by searching for changes in the document content, which increases the burden on the approver's approval process.
[0015] Therefore, the business support device of this embodiment allows for the attachment of supporting documents while maintaining control over the documents by enabling "attachment mode," which locks the contents of the documents and only allows for the attachment of supporting documents. This reduces the workload on the person in charge due to the creation of red / black documents and prevents the inconvenience of an increase in the number of documents.
[0016] Furthermore, by presenting the additionally attached documents to the approver separately from the original document, it becomes possible to perform the approval process by reviewing only the supporting documents, thereby reducing the workload on the approver.
[0017] Furthermore, by managing the approval status for each document, only documents that have received final approval are displayed when referencing documents from the ledger. This ensures that accurate accounting information can be submitted during audits.
[0018] (Hardware configuration) The business support device 1 of this embodiment is operated by an accountant, and as shown in Figure 1, the business support device 1 of this embodiment comprises a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5.
[0019] Output device 7 may include a display unit of a monitor device (including a home television), a printing device, or a speaker device. Input device 6 may include a keyboard device, a mouse device, a microphone device, or a monitor device that works in conjunction with a mouse device to provide a pointing device function.
[0020] The communication interface unit 4 is connected to a network 50, such as a wide-area network like the Internet or a private network like a LAN (Local Area Network). The approver terminal device 51 of approvers, who perform the approval work of documents submitted for approval from the business support device 1 in a so-called workflow, is connected to the network 50.
[0021] For the memory unit 2, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used. The memory unit 2 stores a business support program that reduces the workload of attaching supporting documents to documents after final approval, as well as the workload of approvers handling documents.
[0022] Furthermore, this storage unit 2 is equipped with the following storage areas: a payment data storage unit 11, a document data storage unit 12, a document association data storage unit 13, an additional document data storage unit 14, a journal entry data storage unit 15, a list data storage unit 16, and a general ledger storage unit 17.
[0023] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the memory unit 2, and functions as a data generation unit 21, a discrimination unit 23, an error output control unit 24, a mode switching control unit 25, a display control unit 26, an acquisition unit 27, and an update processing unit 28, as shown in Figure 2.
[0024] The data generation unit 21 includes the functions of an additional document data generation unit 22, a document association data generation unit 29, a document data generation unit 30, and a journal entry data generation unit 31. The display control unit 26 also includes the functions of an unapproved list display control unit 32, an inquiry screen display control unit 33, and a general ledger display control unit 34.
[0025] In this example, the data generation unit 21 to the general ledger display control unit 34 are described as being implemented in software based on the business support program. However, all or part of the data generation unit 21 to the general ledger display control unit 34 may be implemented in hardware. In either case, the same effects as described later can be obtained.
[0026] In the business support device 1 of this embodiment, the acquisition unit 27 acquires journal entry data that has the approval status information of "application in progress" added to it, from among the journal entry data stored in the journal entry data storage unit 15, which is attached either approval status information of "final approval completed" indicating that final approval by the approver has been completed, or approval status information of "application in progress" indicating that approval by the approver is pending, along with an approval status information of "application in progress" indicating that it is journal entry data.
[0027] Furthermore, the acquisition unit 27 acquires the supporting document data stored in the supporting document data storage unit 12, which is supporting document data for which an application for additional supporting documents is made for journal entry data after final approval, and which has the approval status information of "approved" (indicating that final approval by the approver has been completed) or "in application" (indicating that approval by the approver is still being applied for), along with an approval status information of "in application" (indicating that an application for additional supporting documents is being made for journal entry data after final approval).
[0028] The unapproved list display control unit 32 displays a list of data, including the application type, voucher number, and approval status information of the journal entry data and supporting document data to which the acquired approval status information of pending applications has been attached, via the display unit (output device 7).
[0029] The inquiry screen display control unit 33 displays, via the application content additional supporting document inquiry screen, the application content of the journal entry data corresponding to the list data selected by the operator from the list data displayed in the list, or the supporting document data corresponding to the list data selected by the operator, and the supporting document data that was the source of the application and has received final approval (see Figure 11).
[0030] The document data includes additional attachment information indicating the number of additional documents to be added. The unapproved list display control unit 32 controls the display of the list data including the additional attachment information.
[0031] The update processing unit 28 updates the approval status information of the journal entry data that has been finally approved by the approver, and the approval status information of the supporting document data that has been finally approved by the approver, to the final approved approval status information (see Figure 20(a)).
[0032] The General Ledger Data Display Control Unit (General Ledger Display Control Unit 34) includes the date of occurrence, voucher number, debit amount, credit amount, and balance amount. When the display of general ledger data stored in the general ledger storage unit is specified, it refers to the journal entry data storage unit 15 and the supporting document data storage unit 12 based on the voucher number of the general ledger data, and displays the general ledger data corresponding to the journal entry data with final approval status information attached, and the general ledger data corresponding to the supporting document data with final approval status information attached, on the display unit (output device 7).
[0033] The document data generation unit 30 generates document data including the document body data and unique document number of the document to be added, and stores it in the document data storage unit 12, in the attachment mode selected when adding a document, after final approval by the approver of the journal entry data including the payment amount and unique voucher number, and the document body data of the document corresponding to the payment amount and the unique document number of the document to be added.
[0034] The additional document data generation unit 22 generates additional document data, including the voucher number of the final approved journal entry data, the document number of the final approved document data, and the approval status information attached to the journal entry data indicating whether the approval application by the approver is pending or final approved (see Figure 22(a)), and stores this additional document data in the additional document data storage unit 14 (see Figure 22(d)).
[0035] When a desired voucher number is entered and the attachment mode is specified, the discrimination unit 23 refers to the journal entry data and determines whether the approval status information attached to the journal entry data for the entered voucher number is pending or final approved.
[0036] The document data generation unit 30 generates document data for the added document and stores it in the document data storage unit 12 when the attachment mode is specified and the determination unit 23 determines that the approval status information of the entered slip number is final approved.
[0037] When the attachment mode is specified, the error output control unit 24 controls a predetermined output device to output an error indicating that the addition of supporting documents is not permitted if the discrimination unit 23 determines that the approval status information is pending (see Figure 17). In addition to a display unit, a printing device, a speaker device, etc., can be used as the predetermined output device.
[0038] The mode switching control unit 25 controls the switching operation by the operator to switch between a modification mode that enables modification and addition of supporting documents for journal entry data whose approval status is pending, and an attachment mode that enables the addition of supporting documents for journal entry data whose approval status is final approved (see the switch button 70 in Figure 7).
[0039] In modification mode, the display control unit 26 displays the journal entry data stored in the journal entry data storage unit 15 via the display unit (for example, the output device 7) in a state that allows for modification (see Figure 15). In attachment mode, the journal entry data is displayed via the display unit in a state where the contents of the voucher cannot be changed (see Figure 18).
[0040] In attachment mode, the document data generation unit 30 adds predetermined document supplementary information (file name, transaction date, amount, etc. shown in Figure 11) entered by the person in charge to the document data including the document body data (binary data) and unique document number of the document to be added, and stores it in the document data storage unit 12.
[0041] (Processing of supporting documents added after final approval of the voucher) Next, we will describe the processing operation of supporting documents added after the final approval of a document in the business support device 1 of this embodiment.
[0042] (If supporting documents arrive after the final approval of the voucher (a red / black voucher must be prepared and attached)) First, Figure 3 is a diagram illustrating a comparative example to the business support device 1 of the embodiment. This Figure 3 shows the operation of a comparative example in which, when supporting documents arrive after the final approval of a voucher, the previous black voucher is reconciled with a red voucher, and then a new black voucher is created and the supporting documents are attached.
[0043] In this case, when the person in charge performs the purchase input operation, the data generation unit generates payment data including the slip number (W001) and amount (100 yen) and stores it in the payment data storage unit. The document data generation unit also generates document data including the document code (Code A), document name (invoice), and binary data (image information of the document, etc.) and stores it in the document data storage unit. The data generation unit also generates document association data linking the slip number (W001) of the payment data and the document code (Code A) of the document data, and stores it in the document association data storage unit.
[0044] Furthermore, the binary data included in the main document data may include not only the image information of the document, but also other information such as text information of transaction data (including information other than image information).
[0045] Next, based on the journal entry input operation by the person in charge, the journal entry data generation unit generates journal entry data including the voucher number (M001) and amount (100 yen), and stores it in the journal entry data storage unit.
[0046] This journal entry data and supporting document data are transmitted to the approver terminal device 51, where the approver performs the approval process. The approver verifies the contents of the voucher indicated by the journal entry data and the supporting document (in this case, an invoice) indicated by the supporting document data, and then gives final approval. After this final approval, any changes to the data contents of the journal entry data (the contents of the voucher) are prohibited.
[0047] Now, suppose that after the approver's final approval, it becomes necessary to add a receipt corresponding to the invoice that was initially attached as supporting documentation. In this case, the person in charge generates a journal entry of "-100 yen" by entering a red slip corresponding to the previous invoice, thereby reconciling the amount of the previous invoice. Then, the person in charge generates a journal entry of "100 yen" again, along with supporting documentation data for the invoice and receipt.
[0048] As a result, document association data is generated that links the voucher number (M003) of the regenerated journal entry data, the document code (Code B) of the invoice document data, and the document code (Code C) of the receipt document data, and this data is stored in the document association data storage unit.
[0049] In this way, the approver performs the approval process again based on the newly generated journal entry data and supporting document data.
[0050] (If supporting documents arrive after the final approval of the voucher (only the supporting documents will be added to the approved voucher)) Next, we will describe the operation of the business support device 1 of the embodiment when supporting documents are added after the final approval of the voucher. In this case, the operation is the same as described above until the approver's final approval is made based on the journal entry data to which the supporting documents of the invoice are attached.
[0051] If a receipt needs to be added after the approver's final approval, the person in charge selects "Attachment Mode" on the journal entry input screen, which will be described later using Figure 7. This causes the mode switching control unit 25 to switch the operation mode of the control unit 3 to "Attachment Mode".
[0052] When this attachment mode is selected and the voucher number of the voucher to which the receipt will be added is entered, the discrimination unit 23 refers to the approval status information attached to the journal entry data of the entered voucher number. This approval status information includes either "Final Approval" approval status information, which indicates that the approver has completed final approval of the journal entry data, or "Application in Progress" approval status information, which indicates that the journal entry data is currently under approval by the approver.
[0053] In this case, since attachment mode is selected, the discrimination unit 23 determines whether or not the approval status information "Final Approved" is attached to the journal entry data of the entered voucher number. If the discrimination unit 23 determines that the approval status information "Final Approved" is not attached, it means that the journal entry data is "Pending Approval" and that it is possible to modify the voucher contents and add supporting documents in modification mode. Therefore, the error output control unit 24 displays a predetermined error message and prompts the user to make modifications (such as adding a receipt) in the "modification mode" described later.
[0054] In response to this, if the discrimination unit 23 determines that the approval status information "finally approved" has been added, the display control unit 26 displays the journal entry data corresponding to the slip number entered by the person in charge via the output device 7, with the contents of the journal entry data set to be unchangeable.
[0055] The display screen for this journal entry data is equipped with an attachment button (reference numeral 60 in Figure 7) which is used when adding supporting documents. The person in charge uses this attachment button to specify the storage location (e.g., an external storage device) where the data (binary data) of the supporting document to be added, such as a receipt, which has been digitized by reading it with an optical scanner, is stored.
[0056] The display control unit 26 retrieves the data of the document to be added from the designated storage location and displays it via the output device 7 along with the input fields for document supplementary information. The person in charge checks the displayed image of the document and enters the file name, transaction date, amount, and other document supplementary information such as memos into the input fields for document supplementary information, and instructs the attachment.
[0057] As a result, the document data generation unit 30 generates document data with attached image data (binary data) of the receipt and document-related information, as shown in Figure 4, and stores it in the document data storage unit 12.
[0058] Furthermore, as shown in Figure 4, the document association data generation unit 29 generates additional document data that associates the document code (code B) of the generated document data with the journal entry number (M001) of the journal entry data to which the document was to be added, and stores it in the additional document data storage unit 14.
[0059] The approver selects the approval list data from the approval list screen shown in Figure 4, where the application type is "Additional Attachment," the voucher number is the voucher number "M001" from the journal entry data, and the case details are "1 Additional Attachment."
[0060] As a result, the added document data and the journal entry data to which the document data has been added are transmitted from the business support device 1 to the approver terminal device 51 and displayed. The approver then performs the approval process again based on this document data and journal entry data.
[0061] Next, once final approval is given by the approver, the document association data generation unit 29 generates document association data, as shown in Figure 4, which associates the document code (code B) of the approved document data with the voucher number (M001) of the journal entry data to which the document was added, and stores it in the document association data storage unit 13.
[0062] (If supporting documents arrive before the final approval of the voucher (the original voucher must be amended and attached)) Next, we will describe the operation of adding supporting documents before final approval of a voucher in the modification mode of the business support device 1 of the embodiment. In this case, the operation is the same as described above until the journal entry data with supporting documents attached to the invoice is generated. Based on this journal entry data and supporting document data, final approval is made by the approver, but suppose that supporting documents such as receipts are added before this final approval.
[0063] The addition of supporting documents prior to final approval is performed in modification mode, and as shown in Figure 5, supporting document data for the added supporting document is generated and stored in the supporting document data storage unit 12. The supporting document data for the added supporting document is a document with the supporting document code "Code B", the supporting document name "Receipt", and binary data (such as image information of the supporting document) attached.
[0064] Furthermore, the document association data generation unit 29 generates document association data by associating the document code (code B) of the added document data with the voucher number (M001) of the journal entry data to which the document was added, and stores it in the document association data storage unit 13.
[0065] Since the voucher has not yet received final approval, the contents of the voucher and supporting documents can be freely added. The approver will then approve the added documents and the corresponding journal entry data.
[0066] (Error behavior when adding evidence before final approval in attachment mode) Next, Figure 6 shows how an error occurs when a document prior to final approval is added in attachment mode to the business support device 1 of the embodiment.
[0067] In other words, before final approval, journal entry data can be freely modified and supporting documents can be added in the modification mode described above. For this reason, adding supporting documents before final approval in attachment mode will result in an error.
[0068] In attachment mode, after final approval of the journal entry data, it is possible to add supporting documents, but without being able to modify the journal entry content. Further details will be provided later.
[0069] (Attachment of supporting documents to journal entry data after approval) Next, when adding and attaching supporting documents to the journal entry data after final approval, the person in charge specifies the display of the journal entry input screen. The display control unit 26 then displays the journal entry input screen, as illustrated in Figure 7, via the output device 7. This journal entry input screen is equipped with a switch button 70 for switching between the attachment mode and the modification mode. In this case, the person in charge selects the attachment mode by operating the switch button 70. At the same time, the operator also inputs the voucher number (M001) and the business location (Tokyo Head Office) of the journal entry data to which the supporting documents will be added.
[0070] In addition to the attachment mode and modification mode, the modes selectable via the toggle button 70 include a new mode, which is selected when entering new journal entry data; a delete mode, which is selected when deleting existing journal entry data; and a query mode, which is selected when specifying a query for existing journal entry data.
[0071] When attachment mode is selected, the display control unit 26 reads the journal entry data to which the entered slip number (M001) is attached from the journal entry data storage unit 15 and displays it on the journal entry input screen. At this time, the discrimination unit 23 determines whether the approval status information attached to the journal entry data is final approved or not.
[0072] If the display control unit 26 determines that the attachment mode has been selected by the person in charge and that final approval status information has been added to the specified journal entry data, it displays the journal entry data on the journal entry input screen in a state where the journal entry content cannot be modified, as shown in Figure 7. This makes it possible to attach supporting documents while protecting the final approved journal entry content.
[0073] Next, the person in charge operates the attachment button 60 on the journal entry input screen. As a result, the display control unit 26 displays the attachment details screen, as illustrated in Figure 8, via the output device 7. The person in charge obtains image data of supporting documents, such as receipts, which have been previously scanned using, for example, an optical scanner, from an external memory device or a storage device on the network, and performs the attachment operation. As a result, the display control unit 26 displays the image of the attached supporting document on the attachment details screen, as shown in Figure 8.
[0074] This attachment details screen includes an input field for supporting document information. The person in charge enters supporting document information such as the file name, transaction date, amount, and memo into this input field and operates the execute button. When the execute button is operated, the supporting document data generation unit 30 automatically assigns a new supporting document code (code B) as shown in Figure 9, and generates supporting document data including the supporting document name (file name), binary data (image information included in the supporting document data, etc.), transaction date, amount, and memo based on the entered supporting document information, and stores it in the supporting document data generation unit 30.
[0075] (Approval support action) Next, as shown in Figure 10, when generating evidence data, the evidence data generation unit 30 adds application type, corresponding journal entry number, case details, and approval status information to the evidence data. Similarly, when generating journal entry data, the journal entry data generation unit 31 adds application type, journal entry number, and approval status information to the journal entry data.
[0076] If the supporting document data is the supporting document data of the additional supporting document mentioned above, the application type will be "Additional Attachment". Similarly, if the journal entry data is from a journal entry voucher, the application type will be "Journal Entry Voucher".
[0077] The case details are added based on the "number of supporting documents to be added" entered by the person in charge in the input field for supporting document information on the attachment details screen shown in Figure 8. That is, if, for example, "1 document" is entered as the "number of supporting documents to be added" via the attachment details screen, the supporting document data generation unit 30 generates supporting document data with the case details "1 additional attachment" added, as shown in Figure 10.
[0078] The approval status information is updated from "Pending" to "Final Approval" by the update processing unit 28 when the approval by the approver is completed.
[0079] When approval is granted by the approver, the acquisition unit 27 refers to the document data storage unit 12 and the journal entry data storage unit 15 and acquires the document data and journal entry data with the approval status information "in progress". The unapproved list display control unit 32 then transmits the document data and journal entry data with the approval status information "in progress" acquired by the acquisition unit 27 to the approver terminal device 51 and displays them in a list on the approver terminal device 51 as shown in Figure 10.
[0080] Furthermore, the supporting document data and journal entry data with the "approved" status information attached may be displayed as an unapproved list via the output device 7 of the business support device 1, and the approver may perform the approval work via the output device 7 of the business support device 1.
[0081] The approver selects the supporting document or journal entry data to be approved from this list of unapproved items. The example in Figure 10 shows an example where additionally attached supporting document data is selected as the supporting document to be approved. Such selected data is transmitted from the approver terminal device 51 to the business support device 1.
[0082] Between the business support device 1 and the approver terminal device 51, such data is transmitted and received by the transmitting and receiving devices and transmitting and receiving control units provided in each device 1 and 51, respectively. However, the explanation of the transmission and receiving operation between these two devices 1 and 51 will be omitted in the following description.
[0083] If the additionally attached document data (application type = additional attachment) is selected from the list of unapproved documents as the document data to be approved, the inquiry screen display control unit 33 displays the application content additional document inquiry screen, as illustrated in Figure 11, to the approver terminal device 51.
[0084] This application details additional supporting document inquiry screen includes selection buttons 80a and 80b for the supporting documents attached to the journal entry data, a display field for the journal entry details, a display field for the supporting document image, and a display field for supporting document supplementary information.
[0085] The document selection buttons 80a and 80b are generated by the inquiry screen display control unit 33, which refers to the document data shown in Figure 9 and generates selection buttons corresponding to the document names of the document data for the specified slip number, and displays them on the application content additional document inquiry screen. The example in Figure 11 is an example in which the document data for a final approved invoice and the document data for a final approved additional receipt are associated with a specified slip number. In this case, the inquiry screen display control unit 33 generates the invoice selection button 80a and the receipt selection button 80b and displays them on the application content additional document inquiry screen.
[0086] In terms of journal entries, the inquiry screen display control unit 33 displays the voucher number, business name, debit and credit account titles, and amounts based on the journal entry data of the entered voucher number.
[0087] The document image is displayed by the inquiry screen display control unit 33 based on the binary data of the document data of the document selected by the selection button 80a or selection button 80b (see Figure 9).
[0088] In this example, we will explain how to display the image information of the document as binary data, but other information, such as textual information of transaction data, may also be displayed. Furthermore, the image information of the document and other information may be downloaded from a storage device on the network and displayed.
[0089] The document-related information is displayed by the inquiry screen display control unit 33 based on the document data (see Figure 9) of the document selected by the selection button 80a or selection button 80b.
[0090] By displaying this application details and supporting document inquiry screen, it becomes possible to select the desired documents and approve them individually.
[0091] (Display control of ledger) Next, the business support device 1 of the embodiment displays the supporting document data associated with the general ledger data stored in the general ledger storage unit 17 for which final approval by the approver has been completed, and does not display supporting document data for which final approval by the approver has not been completed.
[0092] Specifically, when the user specifies that the general ledger should be displayed, the general ledger display control unit 34 reads general ledger data from the general ledger storage unit 17 and displays it on the general ledger screen illustrated in Figure 12(a). This general ledger data includes the date of occurrence, voucher number, counter account, debit amount, credit amount, and balance amount. The data generation unit 21 generates such general ledger data based on the journal entry data and supporting document data described above.
[0093] The general ledger display control unit 34 displays a detail inquiry button 65 when displaying the general ledger screen. When this detail inquiry button 65 is operated, the discrimination unit 23 determines whether the approval status information of the supporting document data corresponding to the voucher number of the general ledger data displayed on the general ledger screen is "pending" or "finally approved".
[0094] Here, there are two types of supporting data associated with the same voucher number: invoice data and receipt data. Of these, the invoice data has received final approval from the approver (approval status information = final approved), while the receipt data has not received final approval from the approver (approval status information = pending).
[0095] If the discrimination unit 23 determines that the approval status information of the document data is "pending," the general ledger display control unit 34 hides the document data with the "pending" approval status information from the ledger details inquiry screen, as shown in Figure 12(b).
[0096] In response, if the discrimination unit 23 determines that the approval status information of the document data is "finally approved," the general ledger display control unit 34 displays the document data with the "finally approved" approval status information on the ledger details inquiry screen, as shown in Figure 12(c).
[0097] In other words, when the detail inquiry button 65 on the general ledger screen is operated, the general ledger display control unit 34 displays only the document data with the approval status information "Final Approval" attached on the ledger detail inquiry screen.
[0098] This makes it possible to view only the "finally approved" documentation data. In other words, it makes it possible to identify "pending" documentation and proceed with the approval process for "pending" documentation.
[0099] (Operation in correction mode) Next, the operation flow in correction mode will be explained using the flowchart in Figure 13. This flowchart in Figure 13 starts when correction mode is selected using the toggle button 70 on the journal entry input screen shown in Figure 7, and the processes are executed sequentially from step S1.
[0100] In step S1, the mode switching control unit 25 controls the operation mode of the control unit 3 to the modification mode. In this modification mode, the display control unit 26 refers to the journal entry data in the journal entry data storage unit 15 based on the slip number entered by the person in charge.
[0101] In step S2, the discrimination unit 23 determines whether the approval status information attached to the journal entry data of the voucher number entered by the person in charge is "pending" or "finally approved".
[0102] In step S3, the display control unit 26 determines from the discrimination unit 23 that approval status information of "application in progress" has been added, and therefore determines that it is possible to make corrections in correction mode and thus it is possible to retrieve the journal entry data (step S3: Yes).
[0103] When the display control unit 26 determines that the journal entry data can be retrieved, in step S4, it reads the journal entry data for the voucher number entered by the person in charge from the journal entry data storage unit 15 and displays it on the journal entry input screen as shown in Figure 15. The person in charge uses this journal entry input screen to make corrections to the journal entry data in correction mode and attach additional supporting documents, etc.
[0104] In contrast, in step S3, if the display control unit 26 obtains a determination result from the discrimination unit 23 indicating that the approval status information "finally approved" has been added, it is preferable to make the correction in correction mode impossible, and therefore it determines that the retrieval of the journal entry data is impossible (step S3: No).
[0105] If it is determined that the journal entry data cannot be retrieved, the error output control unit 24, in step S5, displays an error message via the output device 7, as shown in Figure 14, which prohibits modification of the final approved journal entry data during modification mode. For example, "The corresponding voucher number cannot be retrieved (the voucher cannot be changed because it has been approved)."
[0106] This ensures that the person in charge understands that the document they designated has already received final approval from the approver and therefore cannot be modified in modification mode. In this case, the person in charge can only add supporting documents in attachment mode, as described below.
[0107] (Operation in attachment mode) Next, the operation flow in attachment mode will be explained using the flowchart in Figure 16. This flowchart in Figure 16 starts when attachment mode is selected using the toggle button 70 on the journal entry input screen shown in Figure 7, and the processes are executed sequentially from step S11.
[0108] In step S11, the mode switching control unit 25 controls the operation mode of the control unit 3 to the attachment mode. In addition, the display control unit 26, in this attachment mode, refers to the journal entry data in the journal entry data storage unit 15 based on the slip number entered by the person in charge.
[0109] In step S12, the discrimination unit 23 determines whether the approval status information attached to the journal entry data of the voucher number entered by the person in charge is "pending" or "finally approved".
[0110] If the discrimination unit 23 determines that the approval status information "Final Approval" has been added, it becomes possible to attach additional supporting documents in attachment mode. For this reason, the display control unit 26 determines in step S13 that it is possible to retrieve the journal entry data (step S13: Yes).
[0111] When the display control unit 26 determines that the journal entry data can be retrieved, in step S15, it reads the journal entry data for the slip number entered by the person in charge from the journal entry data storage unit 15 and displays it on the journal entry input screen in a state where the journal entry content cannot be modified, as shown in Figure 18. The person in charge operates the attachment button 60 on this journal entry input screen and inputs a new document image and document supplementary information via the attachment file details screen shown in Figure 8. As a result, the document data generation unit 30 generates new document data corresponding to the newly attached document and stores it in the document data storage unit 12.
[0112] In response to this, if the discrimination unit 23 obtains a discrimination result indicating that "application in progress" approval status information has been added, the display control unit 26 determines in step S13 that the retrieval of the journal entry data is not possible because the addition and attachment of supporting documents to the journal entry data can be freely done in the modification mode described above (step S13: No).
[0113] If it is determined that the journal entry data cannot be retrieved, the error output control unit 24, in step S14, displays an error message via the output device 7, as shown in Figure 17, which prohibits the addition of new supporting documents to the journal entry data that is currently under approval in attachment mode, such as "The corresponding voucher number cannot be retrieved (approval application is pending. Please attach in modification mode)."
[0114] This allows the person in charge to recognize that the document they specified can have supporting documents added in modification mode. In this case, the person in charge will add new supporting documents using the aforementioned modification mode.
[0115] (Data update operation) Next, the data update operations in the business support device 1 of the embodiment will be described. As an example, the data update operations will be described in the case where a slip M001 with an invoice 001 attached is registered by new registration and a receipt 001 is added in modification mode, and in the case where a slip M002 with an invoice 002 attached is registered by new registration, approved by the approver (final approval), and a receipt 002 is added in attachment mode.
[0116] (When registering for a new account) First, Figure 19 shows the various data when vouchers M001 and M002 are newly registered. Of these, Figure 19(a) shows the journal entry data, Figure 19(b) shows the supporting document data, Figure 19(c) shows the supporting document association data, and Figure 19(d) shows the additional supporting document association data.
[0117] In this case, as shown in Figure 19(a), the journal entry data generation unit 31 generates journal entry data for vouchers M001 and M002, which include the debit account for "Purchases," the credit account for "Accounts Payable," the amount, and approval status information indicating "Application in Progress" that the approver's approval has not yet been completed, and stores it in the journal entry data storage unit 15.
[0118] Furthermore, as shown in Figure 19(b), the document data generation unit 30 generates document data with the document code "Code A" to be attached to the journal entry data of voucher M001, and generates document data with the document code "Code B" to be attached to the journal entry data of voucher M002, and stores each of them in the document data storage unit 12.
[0119] Each document data entry will include the document name, such as "Invoice 001" or "Invoice 002," image data (binary data) of the attached invoice, the transaction date, the amount, and a memo.
[0120] Furthermore, as shown in Figure 19(c), the data generation unit 21 generates document association data that links the document number "M001" of the journal entry data for document M001 with the document code "Code A", and document association data that links the document number "M002" of the journal entry data for document M002 with the document code "Code B", and stores these in the document association data storage unit 13. This document association data allows the person in charge to recognize the related journal entry data and document data.
[0121] Note that, during this new registration, since there are no additional supporting documents to add, no additional supporting document data is generated, as shown in Figure 19(d).
[0122] (When the voucher is approved) Next, Figures 20(a) to 20(d) show various data at the time of document approval. In the example shown in Figure 20, document M001 is under approval (application pending) by the approver, and document M002 has been finalized by the approver.
[0123] Once the approver completes the final approval of voucher M002, the update processing unit 28 updates the approval status of the approved voucher from "Pending" to "Final Approval" based on the information indicating that the approver has approved it, which is attached to the approved journal entry data or supporting document data and transmitted from the approver terminal device 51, as shown in Figure 20(a). The example in Figure 20(a) is an example where the journal entry data of voucher M002 has been approved by the approver.
[0124] (When adding supporting documents in editing mode) Next, Figures 21(a) to 21(d) show the various data when an additional receipt is attached to the journal entry data of voucher M001 in modification mode. As shown in Figure 21(a), since voucher M002 has already received final approval from the approver, it is necessary to select attachment mode when attaching additional supporting documents. In contrast, since the journal entry data of voucher M001 is "pending" approval from the approver, it is possible to attach supporting documents in modification mode.
[0125] The document data generation unit 30 generates document data for the added document (document data for document code C) as exemplified in Figure 21(b) based on the document and document-related information added via the attached file details screen explained with reference to Figure 8, and stores it in the document data storage unit 12.
[0126] Furthermore, the document association data generation unit 29 generates document association data by associating the voucher number entered when generating the additional document data (in this example, the voucher number for M001) with the document code (code C) of the added document data, and stores it in the document association data storage unit 13 as shown in Figure 21(c).
[0127] (When adding supporting documents in attachment mode) Next, Figures 22(a) to 22(d) show the various data when an additional receipt is attached to the journal entry data of voucher M002 in attachment mode. As shown in Figure 22(a), since voucher M001 is "pending" for approval by the approver, any additional supporting documents must be attached using the modification mode described above. In contrast, since the journal entry data of voucher M002 has been "finally approved" by the approver, changes to the journal entry content are not permitted, but supporting documents can be added.
[0128] The document data generation unit 30 generates document data (document data for document code D) for the added document (receipt 002) as exemplified in Figure 22(b) based on the document and document-related information added via the attached file details screen explained with reference to Figure 8, and stores it in the document data storage unit 12.
[0129] Furthermore, the additional document data generation unit 22 generates additional document data that includes the voucher number entered when generating the additional document data (in this example, the voucher number M002), the document code (code D) of the additional document data, and approval status information indicating that the approval application is pending by the approver, and stores it in the additional document data storage unit 14 as shown in Figure 22(d).
[0130] (When approving additional supporting documents attached in attachment mode) Next, Figure 23 shows various data when additional supporting documents attached in attachment mode are approved. When additional supporting documents attached in attachment mode are approved by the approver, the supporting document association data generation unit 29 generates supporting document association data by associating the voucher number entered when generating the additional supporting document data (in this example, the voucher number M002) with the supporting document code (code D) of the approved additional supporting document data, and stores it in the supporting document association data storage unit 13 as shown in Figure 23(c).
[0131] Furthermore, as shown in Figure 23(d), the additional document data generation unit 22 generates additional document data that includes the voucher number entered when generating the additional document data (in this example, the voucher number M002), the document code (code D) of the approved additional document data, and approval status information of "Final Approval" which indicates the approval status of the added document, and stores it in the additional document data storage unit 14.
[0132] (Data update destination according to processing mode) Next, the control unit 3 performs data update processing on the update destination corresponding to the processing mode, as shown in the flowchart in Figure 24.
[0133] In other words, when updating data, the control unit 3 determines in step S21 whether the current processing mode is attachment mode or not. If the current processing mode is not attachment mode (i.e., it is new mode or modification mode), the control unit 3 proceeds to step S22.
[0134] In step S22, the control unit 3 functions as a journal entry data generation unit 31, a document data generation unit 30, a document association data generation unit 29, and an application data generation unit, generating the journal entry data shown in Figure 25(a), the document data shown in Figure 25(b), the document association data shown in Figure 25(c), and the application data shown in Figure 25(e). The control unit 3 then stores the generated data in the journal entry data storage unit 15, the document data storage unit 12, the document association data storage unit 13, and the application data storage unit, respectively.
[0135] Note that no additional supporting data is generated in New Mode or Modification Mode.
[0136] In response to this, if step S21 determines that the current processing mode is attachment mode, the control unit 3 functions as a document data generation unit 30, an additional document data generation unit 22, and an application data generation unit, and generates the document data shown in Figure 26(a), the additional document data shown in Figure 26(c), and the application data shown in Figure 26(d). The control unit 3 then stores the generated data in the document data storage unit 12, the additional document data storage unit 14, and the application data storage unit.
[0137] (This function displays only the final approved documents.) Finally, as explained using Figure 12, we will once again describe the control that displays only the final approved documents when the general ledger details inquiry button 65 is operated.
[0138] As described above, if the added document is under approval by the approver, the approval status of the added document data is set to "Pending" as shown in Figure 27(a), and the document association data corresponding to the added document is not stored in the document association data storage unit 13 as shown in Figure 27(b).
[0139] When the general ledger details inquiry button 65 is operated, the general ledger display control unit 34 refers to the document association data based on the voucher number. If the added document has not been approved by the approver, the document association data storage unit 13 does not store the document association data corresponding to the added document. Therefore, as shown in Figure 12(b), the general ledger display control unit 34 hides the document data of the added document from the ledger details inquiry screen.
[0140] In response, once the added document is approved by the approver, the approval status of the added document data is updated to "Final Approval" by the update processing unit 28, as shown in Figure 27(c). Then, as shown in Figure 27(d), the document association data corresponding to the added document is stored in the document association data storage unit 13.
[0141] In this state, when the general ledger details inquiry button 65 is operated, the general ledger display control unit 34 displays the document data with the approval status information "Final Approval" attached, as shown in Figure 12(c), on the ledger details inquiry screen, based on the document association data stored in the document association data storage unit 13.
[0142] Furthermore, approvers can perform the approval process by referring only to the final approved documents in the general ledger.
[0143] (Effects of the embodiment) As is clear from the above description, the business support device 1 of the embodiment is equipped with an "attachment mode" that allows only the attachment of supporting documents while making it impossible to modify the contents of the voucher. Therefore, it is possible to attach supporting documents while maintaining control over the vouchers. In addition, it is possible to reduce the workload of the person in charge due to the creation of red / black vouchers and prevent the inconvenience of an increase in the number of vouchers.
[0144] Furthermore, the business support device 1 of this embodiment can present the additionally attached content to the approver separately from the prepared voucher, allowing the approver to perform the approval process by only checking the content of the supporting documents. This reduces the workload on the approver's approval process.
[0145] Furthermore, the business support device 1 of this embodiment manages the approval status for each document, so when referring to documents from the ledger, only those that have been finally approved are displayed. This makes it possible to submit accurate accounting information even during audits.
[0146] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving operational efficiency and promoting appropriate management decisions by companies, and therefore can contribute to SDGs Goals 8 and 9.
[0147] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic processes, thereby contributing to SDGs Goals 12, 13, and 15.
[0148] Furthermore, this invention can contribute to strengthening control and governance, and therefore can contribute to achieving the 16 goals of the SDGs.
[0149] [Other embodiments] The present invention can be implemented in various different forms within the scope of the technical idea described in the claims, even in embodiments other than those described above.
[0150] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually. Alternatively, all or part of the processes described as being performed manually may be performed automatically by known methods or the like.
[0151] Furthermore, unless otherwise specified, the processing procedures, control procedures, specific names, registration data for each process, information including parameters such as search conditions, screen examples, and database configuration shown in the specification or drawings can be arbitrarily changed.
[0152] Furthermore, with respect to the business support device 1, each component shown in the diagram is a functional concept and does not necessarily have to have the physical configuration shown. For example, the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be implemented in whole or in any part by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or by hardware using wired logic.
[0153] The program is recorded on a non-temporary, computer-readable recording medium containing programmed instructions for the information processing device to execute the processes described in the embodiment, and is mechanically read by the business support device 1 as needed. In other words, the storage unit 2, such as ROM or HDD, records a computer program that works in cooperation with the OS (Operating System) to give instructions to the control unit 3 (CPU) and perform various processes. This computer program is loaded into RAM, unpacked, and executed by the control unit 3 as appropriate.
[0154] Furthermore, the business support program for this business support device 1 may be stored on another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.
[0155] Furthermore, the business support program for executing the processes described in the embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product.
[0156] Here, any "portable physical medium" can be used as the "recording medium," such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical Disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.
[0157] Furthermore, "program" refers to a data processing method written in any language or writing method, regardless of whether it is source code or binary code.
[0158] Furthermore, the term "program" is not necessarily limited to a single, monolithic entity, but also includes those that are distributed as multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions.
[0159] Furthermore, for the specific configuration, reading procedure, and post-reading installation procedure for the business support device 1 of the embodiment, well-known configurations or procedures can be used.
[0160] The storage unit 2 is a storage means such as memory devices like RAM and ROM, fixed disk devices like hard disks, flexible disks, and optical disks, and stores various programs, tables, databases, and web page files used for various processing or website provision.
[0161] Furthermore, the business support device 1 may be composed of a known personal computer device or an information processing device such as a workstation, or it may be composed of an information processing device to which any peripheral devices are connected. In addition, the information processing device may be implemented by implementing software (including programs or data, etc.) that realizes the processing described in the embodiment.
[0162] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing or integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above can be selectively implemented by arbitrarily combining the embodiments described above. [Industrial applicability]
[0163] This invention is suitable for application to accounting operations in various industries. [Explanation of Symbols]
[0164] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input devices 7 Output device 11 Payment data storage unit 12. Proof Data Storage Unit 13. Document-associated data storage unit 14 Additional evidence data storage unit 15. Journal entry data storage unit 16 List Data Storage Unit 17 General Ledger Storage Unit 21 Data Generation Unit 22 Additional Proof Data Generation Unit 23 Discrimination part 24 Error Output Control Unit 25 Mode Switching Control Unit 26 Display Control Unit 27 Acquisition Department 28 Update Processing Unit 29. Data generation unit for supporting documents 30. Proof Data Generation Unit 31. Journal entry data generation unit 32 Unapproved List Display Control Unit 33 Inquiry screen display control unit 34 General Ledger Display Control Unit 50 Networks 51 Approver terminal device
Claims
1. An acquisition unit acquires journal entry data stored in the journal entry data storage unit with either approval status information (final approval, indicating that final approval by the approver has been completed) or approval pending, indicating that approval by the approver is pending, along with a unique voucher number, prescribed application details, and an application type indicating that it is journal entry data, to which the approval status information pending has been added. In addition, an acquisition unit acquires supporting document data stored in the supporting document data storage unit with either approval status information (final approval, indicating that final approval by the approver has been completed) or approval pending, indicating that approval by the approver is pending, along with a unique voucher number, and an application type indicating that it is supporting document data for which additional support is requested for the journal entry after final approval, to which the approval status information pending has been added. An unapproved list display control unit displays a list of unapproved list data via a display unit, which includes the application type, voucher number, and approval status information of the journal entry data and the supporting document data to which the acquired approval status information of the application has been added. An inquiry screen display control unit that displays, via the application content additional document inquiry screen, the application content of the journal entry data corresponding to the list data selected by the operator from the list data displayed in the list data, or the application content of the journal entry data for which the final approval has been given and which is the source of the application for the document data, as indicated by the document data corresponding to the list data selected by the operator, A business support device having the following features.
2. The document data includes information indicating the number of additional documents to be attached. The aforementioned unapproved list display control unit controls the display of the list data, including the additional attachment quantity information. The business support device according to claim 1, characterized by the following:
3. The system further includes an update processing unit that updates the approval status information of the journal entry data, which has been finally approved by the approver, and the approval status information of the supporting document data, which has been finally approved by the approver, to the final approved approval status information. A business support device according to claim 1 or claim 2, characterized by the above.
4. The system further includes a general ledger data display control unit that, when the display of general ledger data stored in the general ledger storage unit is specified, refers to the journal entry data storage unit and the document data storage unit based on the journal entry data and displays on the display unit the general ledger data corresponding to the journal entry data to which the final approved status information is attached, and the general ledger data corresponding to the document data to which the final approved status information is attached. The business support device according to claim 3, characterized by the following:
5. The acquisition step involves the acquisition unit acquiring journal entry data stored in the journal entry data storage unit, which includes either approval status information indicating that final approval by the approver has been completed, or approval pending, indicating that approval by the approver is pending, along with a unique voucher number, prescribed application details, and an application type indicating that it is journal entry data, to which the approval status information pending has been added. In addition, the acquisition step involves acquiring supporting document data stored in the supporting document data storage unit, which includes either approval status information indicating that final approval by the approver has been completed, or approval pending, indicating that approval by the approver is pending, along with a unique voucher number, and an application type indicating that it is supporting document data for which additional support is to be requested for the journal entry after final approval, to which the approval status information pending has been added. An unapproved list display control step involves an unapproved list display control unit displaying, via a display unit, list data including the application type, voucher number, and approval status information of the journal entry data and the document data to which the approval status information of the application obtained in the acquisition step has been added; An inquiry screen display control step in which the inquiry screen display control unit displays, via the application content additional document inquiry screen, the application content of the journal entry data corresponding to the list data selected by the operator from the list data displayed in the list, or the application content of the journal entry data for which the final approval has been given and which was the source of the application for the document data, as indicated by the document data corresponding to the list data selected by the operator. A business support method that has the following characteristics.
6. Computers, An acquisition unit acquires journal entry data stored in the journal entry data storage unit with either approval status information (final approval, indicating that final approval by the approver has been completed) or approval pending, indicating that approval by the approver is pending, along with a unique voucher number, prescribed application details, and an application type indicating that it is journal entry data, to which the approval status information pending has been added. In addition, an acquisition unit acquires supporting document data stored in the supporting document data storage unit with either approval status information (final approval, indicating that final approval by the approver has been completed) or approval pending, indicating that approval by the approver is pending, along with a unique voucher number, and an application type indicating that it is supporting document data for which additional support is requested for the journal entry after final approval, to which the approval status information pending has been added. An unapproved list display control unit displays a list of unapproved list data via a display unit, which includes the application type, voucher number, and approval status information of the journal entry data and the supporting document data to which the acquired approval status information of the application has been added. The inquiry screen display control unit displays, via the application content addition document inquiry screen, the application content of the journal entry data corresponding to the list data selected by the operator from the list data displayed in the list, or the application content of the journal entry data for which the final approval has been given and which is the source of the document data indicated by the document data corresponding to the list data selected by the operator, as shown in the document data. A business support program designed to function as such.