Business support device, business support method, and business support program

Abstract

This makes it possible to recognize the data that forms the basis of the generated journal entries. [Solution] The journal entry data generation unit refers to a journal entry content master table that stores the journal entry content, including debit and credit accounts, corresponding to the source data on which the journal entry processing is performed, and generates journal entry data for the source data that includes the debit account, debit amount, credit account, credit amount, and creation date corresponding to the journal entry content of the source data. The trace information generation unit generates trace information that includes the name of the storage unit where the source data from which the journal entry data was generated is stored, a unique identification number attached to the source data, and journal entry content identification information to identify the journal entry content of the journal entry content master table used to generate the journal entry data, and adds it to the journal entry data. The output control unit outputs the journal entry data with the trace information attached to it to the output target device. Based on this trace information, the data that is the source of the journal entry data can be recognized.

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] The journal entry generation device disclosed in Patent Document 1 (Japanese Patent No. 7511098) sets, in an item setting unit, items of a digital invoice for determining a transaction type and items of a digital invoice for determining a department. The journal entry set unit sets an initial value of a journal entry using the value of the current digital invoice, the preset items of the digital invoice, the value of a past digital invoice, and the transaction type specified in the digital electronic invoice.

[0003] When the transaction type is changed, the modification reflection unit reflects the changed content on the rows where the values of the preset items of the digital invoice match the current changed row, for the rows after the next row of the currently changed row. Then, the journal entry generation unit generates a journal entry by adding up data of the electronic invoice specified for the same transaction type and department.

[0004] This enables easy generation of a journal entry based on the previously received pepol invoice and the content input at that time.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] Previously, while it was convenient to easily generate journal entry data, it was difficult to identify the source data from which that data originated. For example, if an error is found in the generated journal entry data, it becomes necessary to identify the source data. Also, even when accurate journal entry data is generated, there are times when it is necessary to verify the source data.

[0007] 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 enable recognition of the data that forms the basis of the generated journal entry data, thereby supporting journal entry operations. [Means for solving the problem]

[0008] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention includes: a journal entry data generation unit that references a journal entry content master table which stores journal entry content including debit accounts and credit accounts corresponding to the source data on which journal entry processing is performed, and generates journal entry data for the source data which includes debit accounts, debit amounts, credit accounts, credit amounts, and creation dates corresponding to the journal entry content of the source data; a trace information generation unit that generates trace information including the name of the storage unit where the source data on which the journal entry data was generated is stored, a unique identification number attached to the source data, and journal entry content identification information for identifying the journal entry content of the journal entry content master table used to generate the journal entry data, and adds it to the journal entry data; and an output control unit that outputs the journal entry data with the trace information attached to it to an output target device.

[0009] Furthermore, the business support method according to the present invention is a business support method for a business support device comprising a journal entry data generation unit, a trace information generation unit, and an output control unit, and in order to solve the above-mentioned problems and achieve the objective, the method comprises: a journal entry data generation step in which the journal entry data generation unit refers to a journal entry content master table in which journal entry content including debit accounts and credit accounts corresponding to the source journal entry data on which journal entry processing is performed, and generates journal entry data for the source journal entry data including debit accounts, debit amounts, credit accounts, credit amounts, and creation dates corresponding to the journal entry content of the source journal entry data; a trace information generation step in which the trace information generation unit generates trace information including the name of the storage unit in which the source journal entry data on which the journal entry data was generated is stored, a unique identification number attached to the source journal entry data, and journal entry content identification information for identifying the journal entry content of the journal entry content master table used to generate the journal entry data, and adds it to the journal entry data; and an output control step in which the output control unit outputs the journal entry data to which the trace information has been added to an output target device.

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support program according to the present invention functions as a computer that, by referring to a journal entry content master table which stores journal entry content including debit accounts and credit accounts corresponding to the source data on which journal entries are processed, generates journal entry data for the source data including debit accounts, debit amounts, credit accounts, credit amounts, and creation dates corresponding to the journal entry content of the source data; a trace information generation unit which generates trace information including the name of the storage unit where the source data on which the journal entry data was generated is stored, a unique identification number attached to the source data, and journal entry content identification information for identifying the journal entry content of the journal entry content master table used to generate the journal entry data, and adds it to the journal entry data; and an output control unit which outputs the journal entry data with the trace information attached to it to an output target device. [Effects of the Invention]

[0011] This invention makes it possible to recognize the data that forms the basis of the generated journal entry data. Therefore, it can support journal entry operations and reduce the workload of the person in charge. [Brief explanation of the drawing]

[0012] [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 shows an example of a journal entry execution history data storage unit. [Figure 3] Figure 3 shows an example of a temporary receipt data storage unit. [Figure 4] Figure 4 shows an example of a transaction log data storage unit. [Figure 5] Figure 5 shows an example of a journal entry linkage data creation screen for manually specifying the temporary receipt data or transaction log data that will generate journal entry data. [Figure 6] Figure 6 illustrates an example of generating journal entry data based on the latest temporary receipt ID and temporary receipt data. [Figure 7] Figure 7 shows an example of journal entry data generated based on the latest temporary receipt ID temporary receipt data. [Figure 8] Figure 8 shows the journal entry execution history data storage unit to which journal entry execution history data of journal entries generated based on the latest temporary receipt ID temporary receipt data has been added. [Figure 9] Figure 9 illustrates an example of generating journal entry data based on transaction log data with the most recent transaction log ID. [Figure 10] Figure 10 shows an example of journal entry data generated based on transaction log data for the most recent transaction log ID. [Figure 11] Figure 11 shows the journal entry execution history data storage unit to which journal entry execution history data of journal entries generated based on transaction log data of the latest transaction log ID has been added. [Figure 12] Figure 12 shows an example of a journal entry linked data inquiry screen that includes account balances calculated based on accurate journal entries. [Figure 13] Figure 13 shows an example of a journal entry linkage data inquiry screen that includes account balances calculated based on erroneous journal entries. [Figure 14] FIG. 14 is a diagram showing a journal linking data creation screen in a state where the range of transaction log IDs and the range of provisional receipt IDs that are the sources of the journal data created on the specified creation date are displayed based on the journal execution history data. [Figure 15] FIG. 15 is a diagram showing a state where the journal data of the transaction log ID specified for deletion on the journal linking data creation screen is deleted from the journal data storage unit. [Figure 16] FIG. 16 is a diagram showing a state where the deletion flag of the journal execution history data of the transaction log ID specified for deletion on the journal linking data creation screen is updated to "1" indicating deletion of the journal data.

Embodiment for Carrying Out the Invention

[0013] Hereinafter, as an example, an embodiment in which the present invention is applied to a business support device for supporting journal operations in the financial industry will be described in detail based on the drawings. Note that the present invention is not limited to the following embodiments and can also be applied to journal operations in other industries.

[0014] (Overview) In the financial industry, financial businesses have diverse accounting processes depending on the product characteristics. Therefore, in many cases, a function for creating general-purpose accounting journals is constructed by setting up master tables and the like. However, if general-purpose and complex settings are possible, it becomes difficult to investigate when unintended results occur.

[0015] When the content of the generated journal is different from what is expected, since it directly affects the accounting figures, it is often necessary to respond urgently. However, the vendor has to investigate where the cause of the complex process lies, which takes time for the response.

[0016] Here, if not only the resulting journal entry data but also the data and master table from which that data was created can be uniquely identified, the cause can be quickly identified. For this reason, the business support device of this embodiment enables rapid identification of the cause by storing "trace information," which is key information for identifying the records in the data and master table from which the journal entry data was generated, as data.

[0017] Furthermore, the business support device of this embodiment aims to expedite the process from error detection to the re-creation of correct journal entries by deleting the erroneous journal entry data and creating correct journal entry data again if there is an error in the created journal entry data (assist function for detecting errors in journal entry data).

[0018] (Hardware configuration) As shown in Figure 1, the business support device 1 of this embodiment includes 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. The output device 7 may be a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that works in cooperation with a mouse device to realize a pointing device function.

[0019] 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). This network 50 is connected to the banking terminals 51 of banks whose bank accounts are held by creditors or business partners who are customers of the financial institution that owns the business support device 1 of this embodiment.

[0020] Each bank terminal device 51 transmits deposit data (temporary receipt data) from creditors' accounts via direct debit (bank transfer) or manual deposit (cash deposit) to the business support device 1. In addition, each bank terminal device 51 transmits deposit data (transaction log data) from accounts of customers of financial products such as deposit-based loans to the business support device 1.

[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 recognizes the data that forms the basis of the generated journal entry data and assists in the journal entry process.

[0022] Furthermore, this memory unit 2 is equipped with the following memory areas: the temporary receipt journal entry condition master table 11, the journal entry content master table 12, the temporary receipt data storage unit 13, the journal entry data storage unit 14, the journal entry execution history data storage unit 15, the transaction log data storage unit 16, and the transaction log journal entry condition master table 17. More details will be described later.

[0023] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the storage unit 2, and functions as a data generation unit 21, an output control unit 22, and a deletion processing unit 23, as shown in Figure 1. The data generation unit 21 includes a journal entry data generation unit 24, a trace information generation unit 25, and a journal entry execution history data generation unit 26.

[0024] In this example, the data generation unit 21 to the journal entry execution history data generation unit 26 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 journal entry execution history data generation unit 26 may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0025] The journal entry data generation unit 24 refers to the journal entry content master table 12 (Figure 6(c)), which stores the journal entry content including debit and credit accounts corresponding to the source data (temporary receipt data (Figure 3) or transaction log data (Figure 4)) on which the journal entry processing is performed, and generates journal entry data for the source data including the debit account, debit amount, credit account, credit amount, and creation date corresponding to the journal entry content of the source data (Figures 7 and 10).

[0026] The tracing information generation unit 25 generates tracing information that includes the name of the storage unit where the source data (temporary receipt data (Figure 3) or transaction log data (Figure 4)) that generated the journal entry data is stored, a unique identification number attached to the source data, and journal entry content identification information for identifying the journal entry content in the journal entry content master table 12 used to generate the journal entry data, and adds it to the journal entry data.

[0027] "Storage Unit Name" refers to the name of the temporary receipt data storage unit 13 shown in Figure 3 or the transaction log data storage unit 16 shown in Figure 4.

[0028] The "unique identification number attached to the source data for journal entries" corresponds to the "source data key" shown in Figure 7. Specifically, it is either the temporary receipt identification number (temporary receipt ID) shown in Figure 3 or the transaction log identification number (transaction log ID) shown in Figure 4.

[0029] The "Journal Entry Specific Information" consists of the "Journal Entry Condition ID," "Journal Entry Item ID," and "Journal Entry Item Sequence Number (Journal Entry Item SEQ)" shown in Figure 7. As will be explained later using Figure 6, in the case of temporary receipt data, the "Journal Entry Condition ID" and "Journal Entry Item ID" are obtained by referring to the temporary receipt journal entry condition master table 11 shown in Figure 6(b) based on the payment route of the temporary receipt data. In addition, the "Journal Entry Item ID" is used to refer to the journal entry item master table 12 shown in Figure 6(c) to obtain the journal entry item and the "Journal Entry Item SEQ."

[0030] The tracing information generation unit 25 uses the "Journal Entry Condition ID," "Journal Entry Content ID," and "Journal Entry Content SEQ" obtained in this way, along with the name of the storage unit where the source journal entry data (temporary receipt data (Figure 3) or transaction log data (Figure 4)) is stored (temporary receipt data storage unit or transaction log data storage unit) and the unique identification number attached to the source journal entry data, as journal entry content identification information. Then, it generates tracing information including this journal entry content identification information and adds it to the journal entry data (see Figures 7 and 10).

[0031] The output control unit 22 outputs the journal entry data with this tracing information added to it to the output target device.

[0032] The output target device corresponds to, for example, the output device 7, and can be a display device, a printing device, or a speaker device. The output control unit 22 converts the journal entry data into display information, print information, or audio information and supplies it to the corresponding device. This makes it possible to obtain display output, print output, or audio output of the journal entry data. In addition, the output target device can be the storage unit 2, an external storage device, or a server device on a network, and the journal entry data may be output to or transmitted to these devices for storage.

[0033] Furthermore, the output control unit 22 displays the following on the display unit (output device 7): "journal entry data created on the specified creation date," "source journal entry data used when creating the journal entry data on the specified creation date," "journal entry data selected from the journal entry data created on the specified creation date," and "account balance data obtained from the account balance storage unit, including debit account, debit balance, credit account, and credit balance corresponding to the selected journal entry data" (see the journal entry linkage data inquiry screen in Figures 12 and 13).

[0034] Furthermore, the output control unit 22 adds or subtracts the debit amount of the debit account in the journal entry data selected by the person in charge to the balance of the same debit account or the balance of the same credit account in the journal entry data, depending on the account, and displays it (see Figures 12 and 13).

[0035] Furthermore, the output control unit 22 displays the credit amount of the credit account of the journal entry data selected by the person in charge, by adding or subtracting it from the balance of the same debit account or the balance of the same credit account, depending on the account (see Figures 12 and 13).

[0036] When a creation date is specified and the deletion of journal entry data is specified (see Figure 14), the deletion processing unit 23 deletes the journal entry data generated on the specified creation date from the journal entry data storage unit 14 where the generated journal entry data is stored (see Figure 15).

[0037] The journal entry execution history data generation unit 26 generates journal entry execution history data that includes a unique execution identification number assigned to the journal entry data generated by the journal entry data generation unit 24, source table information indicating the source data storage unit (temporary receipt data storage unit 13 or transaction log data storage unit 16) where the source data from which the journal entry data was generated is stored, the creation date on which the journal entry data was created (execution date in Figure 16), and deletion flag information indicating whether or not the journal entry data for each execution identification number (execution ID in Figure 16) has been deleted (see Figure 16).

[0038] The deletion processing unit 23 updates the deletion flag information of the journal entry execution history data (see deleted journal entry data in Figure 15) corresponding to the journal entry data deleted from the journal entry data storage unit 14 to deletion flag information indicating that it has been deleted (see the deletion flag information labeled "1" in Figure 16). The deletion flag information is "0" if the journal entry data has not been deleted, and updated to "1" if the journal entry data has been deleted.

[0039] (Journal entry data generation process) Next, the operation of generating journal entry data in the business support device 1 of the embodiment having the above configuration will be described.

[0040] First, Figure 2 shows the journal entry execution history data generated by the journal entry execution history data generation unit 26. This journal entry execution history data consists of the execution ID, source table name, execution date, range information (From, To), and deletion flag information.

[0041] The execution ID is a unique identification number assigned to each journal entry when the generation of journal entry data is executed. The source table name is the name of the table (storage unit name) where the temporary receipt data or transaction log data that was the source from which the journal entry data was generated was stored, and is the temporary receipt data storage unit 13 shown in Figure 3 or the transaction log data storage unit 16 shown in Figure 4.

[0042] The execution date is the date the journal entry data was generated. The range information is the range of temporary receipt IDs or transaction log IDs attached to the temporary receipt data or transaction log data that form the basis of the journal entry data generated on each execution date.

[0043] In other words, the example in Figure 2 shows that on August 19, 2024, journal entry data with execution ID 84 was generated based on temporary receipt data with temporary receipt IDs 101 to 105. The example in Figure 2 also shows that on August 19, 2024, journal entry data with execution IDs 85, 86, and 87 were generated based on temporary receipt data with transaction log IDs 142 to 149, temporary receipt data with transaction log IDs 150 to 160, and temporary receipt data with transaction log IDs 161 to 162, respectively.

[0044] Furthermore, among the journal entry data in this transaction log, the journal entry data with execution ID 87 has its deletion flag updated to "1," indicating that it has been deleted from the journal entry data storage unit 14. An example of this deletion will be described later using Figures 14 to 16.

[0045] The journal entry data generation unit 24 detects the range of temporary receipt IDs or transaction log IDs of the source journal entry data (temporary receipt data or transaction log data) for which journal entry data has already been created by referring to the range information of the journal entry execution history data. In the example in Figure 2, it is shown that journal entry data has already been generated for temporary receipt data with temporary receipt IDs "101 to 105", and that journal entry data has already been generated for transaction log data with transaction log IDs "142 to 149" and "150 to 160".

[0046] Therefore, the journal entry data generation unit 24 can recognize (detect) that the temporary receipt ID of the temporary receipt data for which journal entry data will be generated next is "106", or that the transaction log ID of the transaction log data for which journal entry data will be generated next is "161", by referring to the range information of the journal entry execution history data.

[0047] In the example shown in Figure 2, the transaction log data with transaction log IDs "161" and "162" has been deleted in the past. Therefore, the journal entry data generation unit 24 recognizes (detects) that it is possible to create journal entry data again from the transaction log data with transaction log ID "161".

[0048] Next, the journal entry data generation unit 24 refers to the temporary receipt data storage unit 13 shown in Figure 3 based on the recognized temporary receipt ID and recognizes the temporary receipt data for which journal entry data will be generated. The example in Figure 3 shows an example where the temporary receipt data with temporary receipt ID "106" is recognized as the temporary receipt data (latest temporary receipt data) for which journal entry data will be generated.

[0049] Alternatively, the journal entry data generation unit 24 refers to the transaction log data storage unit 16 shown in Figure 4 based on the recognized temporary receipt ID and recognizes the transaction log data for which journal entry data is to be generated. The example in Figure 4 shows an example in which the transaction log data with temporary receipt ID "175" is recognized as the transaction log data (latest transaction log data) for which journal entry data is to be generated.

[0050] Up to this point, the explanation has described an example in which the journal entry data generation unit 24 automatically detects (recognizes) the temporary receipt data or transaction log data that generates the journal entry data. However, it is also possible for the person in charge to manually specify the temporary receipt data or transaction log data that generates the journal entry data.

[0051] In this case, the output control unit 22 displays the journal entry linkage data creation screen illustrated in Figure 5 on the output device 7, and displays the temporary receipt ID of the latest temporary receipt data or the transaction log ID of the latest transaction log data on this journal entry linkage data creation screen. The person in charge then selects the desired temporary receipt ID or transaction log ID for which to create journal entry data via the input device 6 and operates the execute button 60. As a result, journal entry data corresponding to the specified temporary receipt ID or transaction log ID is generated, as described below.

[0052] Next, the journal entry data generation unit 24 generates journal entry data based on the temporary receipt data of the latest recognized temporary receipt ID, or generates journal entry data based on the transaction log data of the latest recognized transaction log ID.

[0053] (Generation of journal entry data based on temporary receipt data) Specifically, Figure 6 shows an example of generating journal entry data based on the latest recognized temporary receipt ID's temporary receipt data. As shown in Figure 6(a), the journal entry data generation unit 24 detects the deposit route code for the temporary receipt data of the latest temporary receipt ID, "106". In this example, the deposit route code for the temporary receipt data of temporary receipt ID "106" is "2: Bank Transfer".

[0054] Next, the journal entry data generation unit 24, based on the deposit code for "2: Bank Transfer," refers to the temporary receipt journal entry condition master table 11 as shown in Figure 6(b) and detects the journal entry content ID of "HUK_HK" corresponding to the deposit code for "2: Bank Transfer."

[0055] Next, the journal entry data generation unit 24 refers to the journal entry master table 12 shown in Figure 6(c) based on the journal entry ID "HUK_HK". Then, it retrieves the journal entry sequence, debit account code, credit account code, and original table name corresponding to the journal entry ID "HUK_HK".

[0056] In the example shown in Figure 6(c), the journal entry data generation unit 24 obtains the journal entry content SEQ of "1" corresponding to the journal entry content ID of "HUK_HK", the debit account code of "1100: Current Account", the credit account code of "3511: Temporary Receipt", and the original table name of "Temporary Receipt Data".

[0057] Then, as shown in Figure 7, the journal entry data generation unit 24 generates journal entry data that includes, for example, the execution ID "88", the serial number "104", the occurrence date "August 20, 2024", the debit account code "1100: Current Account", the debit amount "2000 yen", the credit account code "3511: Temporary Receipt", and the credit amount "2000 yen".

[0058] (Generation of tracing information in journal entries for temporary receipt data) Here, as shown in Figure 7, the trace information generation unit 25 generates trace information including the original table name, original data key, journal entry condition ID, journal entry content ID, and journal entry content SEQ, and adds it to the journal entry data mentioned above.

[0059] The "original table name" is the "temporary receipt data" that the temporary receipt data storage unit 13 in Figure 6(a) is obtained by the journal entry data generation unit 24 from the journal entry content master table 12 shown in Figure 6(c). This allows information indicating the storage location of the temporary receipt data (=temporary receipt data storage unit 13) from which the journal entry data is created to be added to the journal entry data.

[0060] The "source data key" is the temporary receipt ID (=106) uniquely assigned to the temporary receipt data that serves as the source for creating the journal entry. This allows information indicating the temporary receipt ID of the temporary receipt data that serves as the source for creating the journal entry to be added to the journal entry data.

[0061] The "Journal Entry Condition ID" is the journal entry condition ID (=KUK2) set in the temporary receipt journal entry condition master table 11 shown in Figure 6(b) for the deposit route of the temporary receipt data that is the source of the journal entry data. This allows information indicating the record in the temporary receipt journal entry condition master table 11 referenced based on the deposit route of the temporary receipt data that is the source of the journal entry data to be added to the journal entry data.

[0062] The "Journal Entry ID" is the journal entry ID (=HUK_HK) assigned to the journal entry that is referenced based on the deposit route of the temporary receipt data that is the source of the journal entry data, as set in the journal entry master table 12 shown in Figure 6(c). The "Journal Entry SEQ" is the identification number (="1") assigned to each different journal entry with the same journal entry ID, as shown in Figure 6(c).

[0063] The "Journal Entry ID" and "Journal Entry SEQ" fields allow information to be added to the journal entry data indicating the record in the Journal Entry Master Table 12 that was referenced when creating the journal entry data.

[0064] When journal entry data with such tracing information attached is generated, the journal entry execution history data generation unit 26 generates journal entry execution history data with, for example, an execution ID of "88", the original table name of "Temporary Receipt", the execution date of "August 20, 2024", range information of "106" (From, To), and a deletion flag of "0", and stores it in the journal entry execution history data storage unit 15, following the existing journal entry execution history data, as shown in Figure 8.

[0065] (Generation of journal entry data based on transaction log data) Next, Figure 9 shows an example of generating multiple journal entry data from a single transaction log data for the most recently recognized transaction log ID. In this case, multiple records will be set in the "Journal Entry SEQ" of the Journal Entry Master Table 12, so "Journal Entry SEQ" also becomes an important key.

[0066] In this case, as shown in Figure 9(a), the journal entry data generation unit 24 retrieves the "product code," "transaction content code," and "accounts receivable status code" of the temporary receipt data for the latest transaction log ID, "161," from the transaction log data storage unit 16. In this example, the "product code" of the transaction log data for transaction log ID "161" is "1000: ○○ Loan," the "transaction content code" is "1200: Payment Reconciliation," and the "accounts receivable status code" is "1: Transaction in Progress."

[0067] Next, the journal entry data generation unit 24 retrieves the journal entry IDs corresponding to the product code "1000: ○○ Loan", the transaction content code "1200: Payment Reconciliation", and the receivable status code "1: Transaction in Progress" from the transaction log journal entry condition master table 17 shown in Figure 9(b). In this case, the journal entry ID "LOG_NK" is retrieved.

[0068] Next, the journal entry data generation unit 24 refers to the journal entry master table 12 shown in Figure 9(c) based on the journal entry ID of "LOG_NK". Then, it retrieves the journal entry SEQ, debit account code, credit account code, and original table name corresponding to the journal entry ID of "LOG_NK".

[0069] In the example shown in Figure 9(c), the journal entry data generation unit 24 obtains journal entry sequence numbers "1" to "4" based on the journal entry ID "LOG_NK". The journal entry data generation unit 24 also obtains the debit account code for "3551: Temporary Receivables", the credit account code for "2030: Operating Loans", and the source table name for "Transaction Log Data" from the journal entry master table 12, which correspond to journal entry sequence number "1".

[0070] Similarly, the journal entry data generation unit 24 obtains the debit account code for "3551: Temporary Receipt", the credit account code for "8030: Interest on Operating Loans", and the source table name for "Transaction Log Data" from the journal entry master table 12, which correspond to the journal entry content SEQ of "2".

[0071] Furthermore, the journal entry data generation unit 24 obtains the debit account code for "3551: Temporary Receipt", the credit account code for "8040: Damages Revenue", and the source table name for "Transaction Log Data" from the journal entry content master table 12, which correspond to the journal entry content SEQ of "3".

[0072] Furthermore, the journal entry data generation unit 24 obtains the debit account code for "3551: Temporary Receipt", the credit account code for "3541: Deposit", and the source table name for "Transaction Log Data" from the journal entry master table 12, which correspond to the journal entry content SEQ of "4".

[0073] Then, as shown in Figure 10, the journal entry data generation unit 24 generates journal entry data that includes, for example, an execution ID of "89", sequential numbers from "105" to "108" corresponding to journal entry sequence values ​​from "1" to "4", the occurrence date of "August 19, 2024" corresponding to journal entry sequence values ​​from "1" to "4", the debit account code of "3511: Temporary Receipt" corresponding to journal entry sequence values ​​from "1" to "4", and debit amounts of "100,000 yen", "3,000 yen", "2,000 yen", and "1,000 yen" corresponding to journal entry sequence values ​​from "1" to "4".

[0074] Furthermore, the journal entry data generation unit 24 generates journal entry data that includes the credit account codes "2030: Operating Loans", "8030: Interest on Operating Loans", "8040: Damages Income", and "3514: Deposits Received", which correspond to the journal entry content SEQ "1" to "4", and the credit amounts "100,000 yen", "3,000 yen", "2,000 yen", and "1,000 yen", which correspond to the journal entry content SEQ "1" to "4".

[0075] When the journal entry details for a single transaction log data are divided into multiple journal entry sequences, multiple journal entry data will be generated corresponding to the journal entry details of each sequence.

[0076] (Generation of tracing information in journal entry data of transaction log data) Here, as shown in Figure 10, the trace information generation unit 25 generates trace information including the original table name, original data key, journal entry condition ID, journal entry content ID, and journal entry content SEQ, and adds it to the journal entry data mentioned above.

[0077] The "original table name" is the "transaction log data" that indicates the transaction log data storage unit 16 in Figure 9(a), which is obtained by the journal entry data generation unit 24 from the journal entry content master table 12 shown in Figure 9(c). This makes it possible to add information to the journal entry data indicating the storage location (= transaction log data storage unit 16) of the transaction log data that is the source of the journal entry data.

[0078] The "source data key" is the transaction log ID (=161) uniquely assigned to the transaction log data from which the journal entry data is created. This allows information indicating the temporary receipt ID of the transaction log data from which the journal entry data is created to be added to the journal entry data.

[0079] The "Journal Entry Condition ID" is the journal entry condition ID (=LOG100018001) set in the transaction log journal entry condition master table 17 shown in Figure 9(b) for the combination of product code, transaction content code, and receivable status code of the transaction log data that serves as the source of the journal entry data. This allows information indicating the record in the transaction log journal entry condition master table 17 referenced based on the product code, transaction content code, and receivable status code of the transaction log data that serves as the source of the journal entry data to be added to the journal entry data.

[0080] The "Journal Entry ID" is the journal entry ID (=LOG_NK) assigned to the journal entry that is referenced based on the product code, transaction content code, and accounts receivable status code of the transaction log data that is the source of the journal entry data, as set in the journal entry master table 12 shown in Figure 9(c). The "Journal Entry SEQ" is an identification number (="1" to "4") assigned to each different journal entry with the same journal entry ID, as shown in Figure 9(c).

[0081] The "Journal Entry ID" and "Journal Entry SEQ" fields allow information to be added to the journal entry data indicating the record in the Journal Entry Master Table 12 that was referenced when creating the journal entry data.

[0082] When journal entry data with such tracing information attached is generated, the journal entry execution history data generation unit 26 generates journal entry execution history data with, for example, an execution ID of "89", the source table name of "Transaction Log", the execution date of "August 20, 2024", range information (From, To) of "161" and "175", and a deletion flag of "0", and stores it in the journal entry execution history data storage unit 15, following the existing journal entry execution history data, as shown in Figure 11.

[0083] (Awareness assistance and correction (deletion) actions when there is an error in the journal entry.) Next, we will explain the recognition assistance and correction (deletion) operations in the event of an error in the journal entry. First, we will explain the process leading up to the generation of journal entry data with an error in its content. As an example, let's explain the case where journal entry data corresponding to the transaction log data with transaction log ID "168" shown in Figure 9(a) is generated. In this case, the transaction log journal entry condition master table 17 shown in Figure 9(b) is referenced based on the combination of the product code "1000: ○○ Loan", the transaction content code "1800: Deposit Return", and the debt status code "2: Fully Paid". Then, the journal entry content ID "LOG_AZKH" is detected.

[0084] Next, based on the journal entry ID "LOG_AZKH", the journal entry master table 12 shown in Figure 9(c) is referenced, and the debit account code for "1000: Cash", the credit account code for "3507: Accounts Payable", etc. are obtained. Here, let's assume that the debit account code for "1000: Cash" is an incorrect debit account code. More accurately, let's assume that the debit account code should be set in the journal entry master table 12 as "3514: Deposits Received".

[0085] As shown in Figure 10, if there is an error in the account code set in the journal entry master table 12, the journal entry data generation unit 24 will generate a journal entry with the incorrect account code, such as "1000: Cash" as the debit account code, and store it in the journal entry data storage unit 14.

[0086] In this embodiment, the business support device 1 has a journal entry linkage data inquiry screen that displays a list of journal entry data for a specified date or period. When the person in charge specifies the display of the journal entry linkage data inquiry screen, the output control unit 22 reads the journal entry data corresponding to the date or period of creation entered by the person in charge from the journal entry data storage unit 14, as shown in Figure 12, and displays it in a list in the journal entry data display area. The example in Figure 12 is an example in which journal entry data of transaction log data created on August 20, 2024 is displayed in a list.

[0087] Furthermore, the output control unit 22 displays the storage location of the transaction log data that was used to create the journal entry data (transaction log data storage unit 16 → transaction log) and the original data key (161) in the display area of ​​the original data, based on the tracing information attached to the journal entry data.

[0088] Furthermore, when a user specifies a desired journal entry from the journal entry data displayed in the journal entry data display area, the output control unit 22 changes the display format of the specified journal entry data record, for example, by displaying it with high brightness or changing the display color. The example in Figure 12 is an example where the journal entry data with the serial number "108" is specified by the user.

[0089] The output control unit 22 reads the account balance data corresponding to the specified journal entry data from the account balance storage 18 shown in Figure 1, and displays the balance after reflecting the debit and credit amounts of the specified journal entry data.

[0090] In other words, the account balance storage 18 stores the debit account code, debit balance, credit account code, and credit balance, as shown in Figure 12, associated with the serial number of the journal entry data and / or the transaction log ID (or temporary receipt ID).

[0091] The output control unit 22 reflects the debit amount of the debit account code in the journal entry data into the balance of the same debit account code in the account balance data. The example shown in Figure 12 shows the state where the debit amount of "1,000 yen" from the journal entry data is reflected in the credit balance of "3511: Temporary Receipt" (-1,000 yen). The example also shows the state where the credit amount of "1,000 yen" from the journal entry data is reflected in the credit balance of "3514: Deposits Received" (+1,000 yen).

[0092] Next, the example in Figure 12 shows an example where journal entry data was generated based on accurate journal entry details. Therefore, the reflection of debit and credit amounts in the balance is also accurate. The output control unit 22 displays the changed account balances by changing the display format.

[0093] In contrast, if incorrect journal entry data is generated, as shown in Figure 10 for the sequence number "109", the reflection of the debit or credit amount to the account balance will also be incorrect, as shown in Figure 13.

[0094] In other words, the example in Figure 13 shows a journal entry where there was a setting error in the journal entry master table 12, and the debit account that should have been set to "3514: Deposits Received" was incorrectly set to "1000: Cash".

[0095] In this case, the output control unit 22 adds the debit amount of "1500 yen" for the incorrect debit account "1000: Cash" to the balance of "1000: Cash" in the account balance data, resulting in an incorrect debit balance. However, the credit amount for the accounts payable balance is reflected correctly.

[0096] By checking the reflection of debit and credit amounts for account balances displayed on the journal entry data inquiry screen, the person in charge can identify errors in the journal entry settings.

[0097] Next, if incorrect journal entry data is created, it is necessary to delete the incorrect journal entry data from the journal entry data storage unit 14, and also delete the journal entry execution history data stored in the journal entry execution history data storage unit 15.

[0098] Therefore, the person in charge specifies the display of the journal entry linkage data creation screen. As a result, the output control unit 22 displays the journal entry linkage data creation screen shown in Figure 14 via the output device 7. The person in charge selects the execution history tab on this journal entry linkage data creation screen and enters the date (or period) on which the incorrect journal entry data was created, such as "August 20, 2024," in the creation date input field.

[0099] The output control unit 22 refers to the journal entry data storage unit 14 and obtains the source, creation date, and ID range (linking range) of the journal entry data corresponding to the entered creation date, and displays them on the journal entry linking data creation screen. The "source" is obtained and used from the original table name of the journal entry data stored in the journal entry data storage unit 14 shown in Figure 10 (trace information: transaction log data storage unit 16). The creation date is obtained and used from the "occurrence date" attached to each journal entry data. The ID range (linking range) is obtained and used from the sequential number attached to the journal entry data created on the specified creation date.

[0100] The example in Figure 14 shows that the journal entry data created on August 20, 2024, includes journal entry data with transaction log IDs "161" to "175" stored in the transaction log data storage unit 16, and journal entry data with transaction log ID "106" stored in the temporary receipt data storage unit 13.

[0101] On this journal entry linkage data creation screen, the person in charge selects the incorrectly created journal entry data that they recognized via the journal entry linkage data inquiry screen as described above, and then operates the delete button 61. The example in Figure 14 shows an example where journal entry data with transaction log IDs "161" to "175" is selected by the person in charge. The output control unit 22 then changes the display format (display color, brightness, etc.) of the journal entry data selected on the journal entry linkage data creation screen and displays it.

[0102] As shown in Figure 15, when the delete button 61 is pressed, the delete processing unit 23 deletes the journal entry data (records with execution ID "89") that are assigned transaction log IDs (sequential numbers) "161" to "175" selected by the person in charge from the journal entry data storage unit 14 (they are erased from the journal entry data storage unit 14).

[0103] Furthermore, the journal entry execution history data generation unit 26 changes the deletion flag information of the journal entry execution history data for execution IDs "89" within the range of transaction log IDs "161" to "175" to a deletion flag information of "1" indicating that the corresponding journal entry data has been deleted from the journal entry data storage unit 14. Note that the deletion flag information for journal entry execution history data that has not been deleted is "0". When journal entry data is deleted, the journal entry execution history data generation unit 26 updates the deletion flag information of the journal entry execution history data corresponding to the deleted journal entry data from "0" to "1".

[0104] Furthermore, if the journal entry data for transaction log IDs "161" through "175" is deleted in this manner, the next time, it will be possible to generate journal entry data based on the transaction log data starting from transaction log ID "161".

[0105] In this way, when incorrect journal entry data and journal entry execution history data are deleted, the person in charge corrects the journal entry content master table 12 to the correct settings and creates the journal entry data again. As a result, journal entry data can be created with the correct settings in the journal entry content master table 12, and incorrect journal entry data can be corrected to correct journal entry data.

[0106] (Effects of the embodiment) As is clear from the above description, the business support device 1 of the embodiment can achieve the following effects through the assistance in detecting incorrect registrations, the retention of trace information, and the re-execution mechanism.

[0107] 1. Error detection assist → By providing a screen that shows the status of journal entries created in response to financial system processing and the resulting balances, it becomes possible to detect a significant amount of incorrect journal entry data.

[0108] 2. Rapid identification of the cause → By storing all the key information that formed the basis of the journal entry data, the data and master table records used when generating the problematic journal entry data can be quickly identified.

[0109] 3. Ensuring accuracy through correction → By deleting erroneous journal entry data that has already been created and generating correct journal entry data again, the accuracy of the journal entry data can be ensured.

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

[0111] Furthermore, this invention can contribute to reducing waste and promoting paperless and electronic processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0112] Furthermore, this invention can contribute to strengthening control and governance, and therefore can contribute to achieving the 16 goals of the SDGs.

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

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

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

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

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

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

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

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

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

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

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

[0124] The storage unit 2 is a storage means such as a memory device like RAM or ROM, a fixed disk device like a hard disk, a flexible disk, and an optical disk, and stores various programs, tables, databases, and web page files used for various processing or website provision.

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

[0126] 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]

[0127] This invention is suitable for application to the generation of accounting data in various fields. [Explanation of symbols]

[0128] 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. Temporary Receipt Journal Entry Conditions Master Table 12. Journal Entry Details Master Table 13. Temporary receipt data storage unit 14. Journal entry data storage unit 15. Journal entry execution history data storage unit 16 Transaction log data storage unit 17 Transaction Log Journal Entry Condition Master Table 21 Data Generation Unit 22 Output control unit 23 Deletion Processing Unit 24. Journal Entry Data Generation Unit 25. Tracing Information Generation Unit 26. Journal Entry Execution History Data Generation Unit 50 Networks 51 Bank terminal equipment

Claims

1. A journal entry data generation unit refers to a journal entry content master table that stores the journal entry content, including debit and credit accounts, corresponding to the source data from which the journal entry processing is performed, and generates journal entry data for the source data, including the debit account, debit amount, credit account, credit amount, and creation date, corresponding to the journal entry content of the source data. A trace information generation unit generates trace information including the name of the storage unit where the source data that generated the aforementioned journal entry data is stored, a unique identification number attached to the source data, and journal entry content identification information for identifying the journal entry content of the journal entry content master table used to generate the aforementioned journal entry data, and adds this trace information to the aforementioned journal entry data. An output control unit that outputs the journal entry data to the output target device, to which the aforementioned tracing information has been added, A business support device having the following features.

2. The output control unit, The aforementioned journal entry data created on the specified creation date, The source data of the journal entry used when creating the journal entry data on the specified creation date, The journal entry data selected from the journal entry data created on the specified creation date, and The account balance data, including the debit account, debit balance, credit account, and credit balance corresponding to the selected journal entry data, obtained from the account balance storage unit, is displayed on the display unit. The debit amount of the debit account in the selected journal entry data is added to or subtracted from the balance of the same debit account or the same credit account in the selected journal entry data, depending on the account, and displayed. The credit amount of the credit account in the selected journal entry data is displayed by adding or subtracting it, depending on the account, to the balance of the same debit account or the balance of the same credit account in the selected journal entry data. The business support device according to claim 1, characterized by the following:

3. The system further includes a deletion processing unit that deletes the journal entry data generated on the specified creation date from the journal entry data storage unit where the generated journal entry data is stored, when the creation date is specified and the deletion of the journal entry data is specified. A business support device according to claim 1 or claim 2, characterized by the above.

4. The system further comprises a journal entry execution history data generation unit that generates journal entry execution history data including a unique execution identification number assigned to the journal entry data generated by the journal entry data generation unit, source table information indicating the source data storage unit where the source data from which the journal entry data was generated is stored, the creation date on which the journal entry data was created, and deletion flag information indicating whether or not the journal entry data for each execution identification number has been deleted. The deletion processing unit updates the deletion flag information of the journal entry execution history data corresponding to the journal entry data deleted from the journal entry data storage unit to deletion flag information indicating that it has been deleted. The business support device according to claim 3, characterized by the following:

5. A business support method for a business support device comprising a journal entry data generation unit, a trace information generation unit, and an output control unit, The journal entry data generation unit refers to a journal entry content master table which stores the journal entry content, including debit and credit accounts, corresponding to the source data on which the journal entry processing is performed, and generates journal entry data for the source data, including the debit account, debit amount, credit account, credit amount, and creation date, corresponding to the journal entry content of the source data. Trace information generation step, wherein the trace information generation unit generates trace information including the name of the storage unit where the source data that generated the journal entry data is stored, a unique identification number attached to the source data, and journal entry content identification information for identifying the journal entry content of the journal entry content master table used to generate the journal entry data, and adds it to the journal entry data. The output control unit performs an output control step of outputting the journal entry data to the output target device, to which the tracing information has been added. A business support method that has the following characteristics.

6. Computers, A journal entry data generation unit refers to a journal entry content master table that stores the journal entry content, including debit and credit accounts, corresponding to the source data from which the journal entry processing is performed, and generates journal entry data for the source data, including the debit account, debit amount, credit account, credit amount, and creation date, corresponding to the journal entry content of the source data. A trace information generation unit generates trace information including the name of the storage unit where the source data that generated the aforementioned journal entry data is stored, a unique identification number attached to the source data, and journal entry content identification information for identifying the journal entry content of the journal entry content master table used to generate the aforementioned journal entry data, and adds this trace information to the aforementioned journal entry data. Output control unit outputs the journal entry data with the trace information added to it to the output target device. A business support program designed to function as such.

Images