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

Abstract

To reduce business burdens on bi-directional transfer operations to a long-term claim and a short-term claim related to a claim, in a company conducting a claim management business.SOLUTION: A business support device comprises: a claim class determination unit that refers to claim data including a claim class for classifying whether a claim is long-term or short-term and the final payment date, and determines whether the claim class is a short-term claim or a long-term claim on the basis of a transfer reference date that is set by adding a certain period to an update execution date and the final payment date; a transfer claim data update unit that refers to the latest transaction data including the claim class, compares a determination result with the claim class, extracts the latest transaction data different from the determination result, and registers and updates the latest transaction data in the transfer claim data together with a transfer class for transferring from the long-term claim to the short-term claim or from the short-term claim to the long-term claim; a journal detail data update unit that registers and updates the journal for transferring the long-term claim and the short-term claim bi-directionally in journal detail data on the basis of the transfer claim data; and a claim data update unit that updates the claim class of the claim data on the basis of the transfer claim data.SELECTED DRAWING: Figure 4

Description

[Technical Field]

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

[0002] Today, when a debt that was managed as a guaranteed debt becomes a company debt through subrogation, the accounting management device is capable of not only changing the debt type before and after the subrogation, but also automatically switching the accounting management.

[0003] Patent Document 1 (JP 2020-166394 A) discloses, in paragraphs 0048 to 0051, etc., a technology for acquiring log data including transaction data for a receivable, determining whether or not subrogated payment of the receivable has been made, and if it is determined that subrogated payment has not been made, creating pre-subrogated payment journal entry data for the transaction data based on the journal entry pattern master and the log data, and if it is determined that subrogated payment has been made, creating post-subrogated payment journal entry data for the transaction data based on the journal entry pattern master and the log data. [Prior art documents] [Patent documents]

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

[0005] However, there is a demand for the development of a business support device that can reduce the workload of companies that perform credit management operations when transferring long-term and short-term credits.

[0006] The present invention has been made in consideration 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 workload involved in transferring long-term and short-term receivables in both directions. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the business support device of the present invention comprises a claim type determination unit that refers to claim data including at least claim identification information assigned to each claim, claim type classifying the claim as long-term or short-term, and final payment date, compares a transfer reference date set by adding a certain period from the update execution date with the final payment date of the claim data, and determines the claim type to be a short-term claim if the final payment date and the transfer reference date are the same day or the final payment date is a date earlier than the transfer reference date, and determines the claim type to be a long-term claim if the final payment date is a date later than the transfer reference date; and a device that compares at least the claim identification information, claim type, transaction date, and claim data including The system has a transfer receivable data update unit that refers to the latest transaction data including the receivable balance, compares the judgment result of the receivable type judgment unit with the receivable type, extracts the latest transaction data where the receivable type differs from the judgment result, registers the update execution date and the transfer type of transfer from long-term receivable to short-term receivable or from short-term receivable to long-term receivable in the transfer receivable data, and updates the transfer receivable data; a journal entry detail data update unit that registers an entry for transferring from long-term receivable to short-term receivable or from short-term receivable to long-term receivable in the journal entry detail data based on the transfer receivable data, and updates the journal entry detail data; and a receivable data update unit that updates the receivable type in the receivable data based on the transfer receivable data.

[0008] In order to solve the above-mentioned problems and achieve the object, the business support method according to the present invention includes a claim type determination step in which a claim type determination unit refers to claim data including at least claim identification information assigned to each claim, a claim type classifying the claim as long-term or short-term, and a final payment date, compares a transfer base date set by adding a certain period from the update execution date with the final payment date of the claim data, and determines the claim type to be a short-term claim if the final payment date and the transfer base date are the same day or the final payment date is a date earlier than the transfer base date, and determines the claim type to be a long-term claim if the final payment date is a date later than the transfer base date; and a transfer claim data update unit compares at least the claim identification information, claim type, transaction date, and claim balance with a transfer receivable data update step in which the latest transaction data including the receivables is referenced, the result of the receivable type determination step is compared with the receivable type, the latest transaction data in which the receivable type differs from the determination result is extracted, and the latest transaction data in which the receivable type differs from the determination result is registered in the transfer receivable data together with the update execution date and the transfer type of transfer from long-term receivable to short-term receivable or from short-term receivable to long-term receivable, thereby updating the transfer receivable data; a journal entry detail data update step in which the journal entry in which the long-term receivable is transferred from short-term receivable to long-term receivable or from short-term receivable to long-term receivable is registered in the journal entry detail data based on the transfer receivable data, thereby updating the journal entry detail data; and a receivable data update step in which the receivable data update unit updates the receivable type in the receivable data based on the transfer receivable data.

[0009] In order to solve the above-mentioned problems and achieve the object, the business support program of the present invention comprises a computer, a claim type determination unit that refers to claim data including at least claim identification information assigned to each claim, claim type classifying the claim as long-term or short-term, and final payment date, compares the transfer base date set by adding a certain period from the update execution date with the final payment date of the claim data, and determines the claim type to be a short-term claim if the final payment date and the transfer base date are the same day or the final payment date is a date earlier than the transfer base date, and determines the claim type to be a long-term claim if the final payment date is a date later than the transfer base date; and The transfer receivable data update unit refers to the latest transaction data including the settlement date and receivable balance, compares the judgment result of the receivable type judgment unit with the receivable type, extracts the latest transaction data where the judgment result and the receivable type differ, registers this in the transfer receivable data together with the update execution date and the transfer type of transfer from long-term receivable to short-term receivable or from short-term receivable to long-term receivable, and updates the transfer receivable data; the journal entry detail data update unit registers, based on the transfer receivable data, an entry to transfer from long-term receivable to short-term receivable or from short-term receivable to long-term receivable in the journal entry detail data, and updates the journal entry detail data; and the receivable data update unit updates the receivable type in the receivable data based on the transfer receivable data. [Effects of the Invention]

[0010] The present invention can reduce the work of transferring long-term and short-term receivables in both directions. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing an outline of the transfer bond data creation process executed by the business support device according to the embodiment. [Figure 2] FIG. 2 is a diagram showing an outline of the journal entry detail data creation and bond data update processing executed by the business support device according to the embodiment. [Figure 3] FIG. 3 is a diagram showing an outline of a journal entry detail data creation process executed by the business support device according to the embodiment. [Figure 4] FIG. 4 is a block diagram illustrating a hardware configuration of the task assistance device according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of the journal entry setting master table. [Figure 6] FIG. 6 is a diagram showing an example of bond data. [Figure 7] FIG. 7 is a diagram showing an example of the latest transaction data. [Figure 8] FIG. 8 is a diagram showing an example of the transfer bond data. [Figure 9] FIG. 9 is a diagram illustrating an example of the journal entry detail data. [Figure 10] FIG. 10 is a diagram showing an example of the transfer data creation processing screen. [Figure 11] FIG. 11 is a diagram showing an example of a process for creating transfer bond data from bond data and latest transaction data. [Figure 12] FIG. 12 is a diagram showing an example of the journalization linked data creation processing screen. [Figure 13] FIG. 13 is a diagram showing an example of the process of creating detailed journal entry data and updating bond data based on the transfer bond data. [Figure 14] FIG. 14 is a diagram showing an example of the bond data, latest transaction data, and journal entry setting master table that are the basis of the journal entry detail data creation process. [Figure 15] FIG. 15 is a diagram showing an example of journal entry detail data after the journal entry detail data creation process. DETAILED DESCRIPTION OF THE INVENTION

[0012] A business support device according to an embodiment of the present invention will be described in detail below with reference to the drawings. As an example, the business support device according to this embodiment is a business support device operated by personnel of a company that performs credit management operations in the financial industry (non-banks, financial institutions, etc.). A company that performs credit management operations needs to transfer credits from long-term to short-term and vice versa based on the remaining maturity of the credits, in addition to daily transactions. The business support device according to the embodiment automatically determines whether or not a receivable needs to be switched between long-term and short-term receivables, and, if a transfer is determined to be necessary, automatically executes a credit transfer process and journal entry creation process to support business operations. Note that the present invention is not limited to the following embodiment, which is described as an example.

[0013] (overview) In the financial industry, receivables are collected continuously over a long period of time. In such cases, the one-year rule is generally applied, and balance sheet accounts must be classified according to the remaining maturity of the receivable. For example, in the case of loans, receivables that will be repaid within one year, counting from the day after the closing date, are classified as short-term loans, and receivables that will be repaid in more than one year are classified as long-term loans.

[0014] Therefore, it is necessary to transfer long-term loans to short-term loans depending on the remaining period of the receivables. Also, as a characteristic of the financial industry, repayment periods may change midway due to changes in contracts, and in addition to cases where long-term loans are transferred to short-term loans, there are also cases where short-term loans are transferred to long-term loans.

[0015] However, this transfer was a change in account title that did not involve a transaction, and the settlement processing system was unable to determine the remaining period of the receivables as of the settlement date. As a result, the staff had to handle it manually, which was a heavy workload and prone to errors.

[0016] Therefore, by retaining information on the current status of receivables (long-term or short-term) and the final repayment date, companies that perform receivable management operations can determine whether to transfer receivables, not just from long-term to short-term, but also from short-term to long-term. Companies that perform receivable management operations create their own batch processing that runs periodically, separate from daily transactions, and determine whether or not receivables need to be transferred based on the data updated by this batch processing. This allows companies that perform receivable management operations to create journal entries to transfer accounts when a transfer is necessary, enabling receivable transfer operations to be carried out automatically. As a result, the workload of the person in charge is reduced.

[0017] As shown in Figure 1, the business support device of the embodiment extracts the receivables to be transferred based on the receivables data that holds information on the receivables and the latest transaction data that holds the latest information on the receivables, and creates transfer receivables data that holds information on the receivables to be transferred. Next, as shown in Figure 2, the business support device of the embodiment registers the transfer journal entry in the journal entry detail data based on the created transfer receivables data, creates the journal entry detail data, and executes the receivables data update process. After that, as shown in Figure 3, the business support device of the embodiment creates the latest transaction data that registers daily transactions based on the updated receivables data, and creates the journal entry detail data.

[0018] This makes it possible to automatically determine whether or not a receivable needs to be transferred and to process the receivables, reducing the workload of the person in charge and improving accuracy.

[0019] (Hardware configuration) FIG. 4 is a block diagram showing the hardware configuration of a task assistance device 1 according to an embodiment. As shown in FIG. 4, the task assistance device 1 according to the 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 (including a home television), a printer, or a speaker. The input device 6 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to provide a pointing device function. The communication interface unit 4 is connected to a network, such as a wide area network (WLAN) or a private network such as a local area network (LAN).

[0020] For example, a storage device such as a ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used as the storage unit 2. The storage unit 2 stores a business support program that enables automatic determination of the need for a receivables transfer and processing of the receivables transfer, reducing the workload of the person in charge and improving accuracy.

[0021] The storage unit 2 also has storage areas, namely, a bond data storage unit 12, a latest transaction data storage unit 13, a transfer bond data storage unit 14, and a journal entry detail data storage unit 15. The storage unit 2 also has various master tables, such as a journal entry setting master table 11.

[0022] As shown in FIG. 5, in the journal entry setting master table 11, ID (Identification), type, transaction content, route, debit item, and credit item are registered (stored) in association with each other.

[0023] The type indicates the type of receivables to be journalized. Types include not only long-term and short-term receivables, but also transfer types such as from long-term to short-term receivables and from short-term to long-term receivables. For example, the type "long-term" indicates that the subject of journalization is a long-term receivable.

[0024] The transaction details indicate the details of the transaction to be journalized. The transaction details may include a partial advance of the repayment deadline or an extension of the repayment period. For example, "Deposit" indicates that a deposit has been made for the receivable to be journalized.

[0025] The route indicates the type of transaction. For example, the "cash" ID "1" in Figure 5 indicates that the transaction "deposit" was carried out using cash.

[0026] The debit and credit items indicate the debit and credit items corresponding to the type, transaction content, and route. If the type is a transfer from long-term to short-term receivables, the account item related to the short-term receivable is registered as the debit item, and the account item related to the long-term receivable is registered as the credit item. Also, if the type is a transfer from short-term to long-term receivables, the account item related to the long-term receivable is registered as the debit item, and the account item related to the short-term receivable is registered as the credit item. For example, ID "1" in Figure 5 indicates that when the receivable type is "long-term," the transaction content is "deposit," and the route is "cash," the debit item is "cash" and the credit item is "long-term loan." Also, the account item related to the short-term receivable is "short-term loan, etc.", and the account item related to the long-term receivable is "long-term loan, etc."

[0027] Furthermore, the claim data storage unit 12 stores claim data, and the latest transaction data storage unit 13 stores latest transaction data. The transfer claim data storage unit 14 stores transfer claim data, and the journal entry detail data storage unit 15 stores journal entry detail data.

[0028] The bond data holds basic information about the bond, as shown in Figure 6. The bond data includes the bond ID, loan amount, type, contract date, monthly repayment amount, number of repayments, and final payment date, all of which are registered in association with each other.

[0029] The latest transaction data holds the latest information on bond transactions, as shown in Figure 7. The latest transaction data registers the bond ID, SEQ (Sequence), type, transaction details, transaction date, transaction amount, and bond balance, each associated with the other.

[0030] The transfer bond data holds information on bonds that require transfer, as shown in Figure 8. The transfer bond data registers the transfer date, bond ID, transfer type, and bond balance, each associated with the other.

[0031] The journal entry detail data holds journal entry information, as shown in Figure 9. The journal entry detail data registers the bond ID, ID, date of occurrence, debit item, debit amount, credit item, and credit amount, each associated with the other.

[0032] (Functional configuration of business support device) Next, the control unit 3 executes the business support program stored in the memory unit 2, thereby functioning as a claim type determination unit 21, a transfer claim data update unit 22, a journal entry detail data update unit 23, a claim data update unit 24, a latest transaction data update unit 25, and an output control unit 26, as shown in Fig. 4. Note that although the claim type determination unit 21 to the output control unit 26 will be described as being realized by software using the business support program, some or all of the claim type determination unit 21 to the output control unit 26 may also be realized by hardware. In either case, the same effects as those described below can be obtained.

[0033] The bond type determination unit 21 sets the transfer base date by adding a certain period (for example, one year) to the specified batch processing execution date (update execution date). In the case of the update execution month instead of the update execution date, the bond type determination unit 21 adds a certain period to the update execution month and sets the last day of the relevant month as the transfer base date.

[0034] The bond type determination unit 21 refers to the bond data and compares the set transfer reference date with the final payment date of the bond data.

[0035] The claim type determination unit 21 determines a claim as a short-term claim if the comparison result shows that the final payment date and the transfer reference date are the same or the final payment date is a date prior to the transfer reference date.The claim type determination unit 21 determines a claim as a long-term claim if the comparison result shows that the final payment date is a date later than the transfer reference date.

[0036] The transfer bond data update unit 22 refers to the latest transaction data and compares the bond type determination result of the bond type determination unit 21 with the type of the latest transaction data.

[0037] As a result of the comparison, the transfer claim data update unit 22 extracts the latest transaction data for which the claim type differs from the claim type determination result. The transfer claim data update unit 22 updates the transfer claim data by registering the specified batch processing execution date as the transfer date, the extracted claim ID as the claim ID, and the claim balance associated with the extracted claim ID in the transfer claim data. Furthermore, based on the comparison result, the transfer claim data update unit 22 registers the type of transfer (from long-term claim to short-term claim or from short-term claim to long-term claim) as the transfer type in the transfer claim data, thereby updating the transfer claim data. Note that if the comparison results in the claim type determination result and the claim type being the same, the transfer claim data update unit 22 terminates processing.

[0038] The journal entry detail data update unit 23 references the journal entry setting master table 11 and acquires debit and credit items based on the transfer type of the transfer credit data. The journal entry detail data update unit 23 registers the credit balance as the debit amount and credit amount in the journal entry detail data based on the transfer credit data, with the credit ID and the transfer date as the occurrence date, and updates the journal entry detail data. The journal entry detail data update unit 23 registers the acquired debit item and the acquired credit item in the journal entry detail data and updates the journal entry detail data.

[0039] The claim data update unit 24 refers to the transfer claim data and the claim data. The claim data update unit 24 changes the claim type of the claim data related to the claim ID of the transfer claim data to a claim type corresponding to the transfer type of the transfer claim data, registers it in the claim data, and updates the claim data.

[0040] The latest transaction data update unit 25 registers the latest bond information corresponding to the bond ID in the latest transaction data for each process such as a deposit process, and updates the latest transaction data.

[0041] When the transfer credit data creation process is executed manually, the output control unit 26 outputs a transfer data creation process screen to the output device 7. In addition, when the journal entry detail data creation and credit data update processes are executed manually, the output control unit 26 outputs a journal entry linkage data creation screen to the output device 7.

[0042] (Operation of the embodiment) Next, the transfer receivable data creation process (step S1) through the detailed journal entry data creation process (step S3) in the business support device 1 of this embodiment having the above configuration will be described. FIGS. 1 to 3 are diagrams showing the flow of the transfer receivable data creation process (step S1) through the detailed journal entry data creation process (step S3) for daily receivable transactions, which are executed by the business support device of this embodiment. The control unit 3 of the business support device 1 of this embodiment executes the business support program stored in the memory unit 2, thereby functioning as a receivable type determination unit 21, a transfer receivable data update unit 22, a detailed journal entry data update unit 23, a receivable data update unit 24, a latest transaction data update unit 25, and an output control unit 26, and executes the transfer receivable data creation process of step S1 shown in FIG. 1, the detailed journal entry data creation and receivable data update processes of step S2 shown in FIG. 2, and the detailed journal entry data creation process of step S3 shown in FIG. 3.

[0043] (Step S1: Transfer bond data creation process) The claim type determination unit 21 automatically starts the transfer claim data creation process in conjunction with the execution of a predetermined batch process. Alternatively, the output control unit 26 may display the transfer data creation process screen 7 as shown in Figure 10, and the transfer claim data creation process may be started by the person in charge operating it.

[0044] First, the claim type determination unit 21 sets the last day of the month obtained by adding one year to the predetermined batch processing execution month (update execution month) as the transfer reference date.

[0045] Next, the bond type determination unit 21 refers to the bond data and compares the set transfer reference date with the final payment date of the bond data.

[0046] The claim type determination unit 21 determines a claim as a short-term claim if the comparison result shows that the final payment date and the transfer reference date are the same or the final payment date is a date prior to the transfer reference date.The claim type determination unit 21 determines a claim as a long-term claim if the comparison result shows that the final payment date is a date later than the transfer reference date.

[0047] For example, as shown in Figure 11, the debt type determination unit 21 sets the transfer reference date to "March 31, 2025", which is the last day of "March 2025" obtained by adding one year to "March 2024", the batch processing execution month.

[0048] Next, the bond type determination unit 21 refers to the bond data in FIG. 11(a) and compares the set transfer reference date "March 31, 2025" with the final payment date of the bond data in FIG. 11(a).

[0049] In the example of Figure 11(a), "March 10, 2025" is the final payment date associated with the bond ID "100" in the bond data. The bond type determination unit 21 compares this final payment date, "March 10, 2025," with the transfer reference date, "March 31, 2025." In this case, because the final payment date is before the transfer reference date, the bond type determination unit 21 determines the bond type to be a "short-term bond."

[0050] In the example of Figure 11(a), "May 15, 2026" is the final payment date associated with the bond ID "101" in the bond data. The bond type determination unit 21 compares this final payment date, "May 15, 2026," with the transfer reference date, "March 31, 2025." In this case, because the final payment date is later than the transfer reference date, the bond type determination unit 21 determines the bond type to be a "long-term bond."

[0051] In the example of Figure 11(a), "March 15, 2025" is the final payment date associated with the bond ID "102" in the bond data. The bond type determination unit 21 compares this final payment date, "March 15, 2025," with the transfer reference date, "March 31, 2025." In this case, because the final payment date is before the transfer reference date, the bond type determination unit 21 determines the bond type to be a "short-term bond."

[0052] In the example of Figure 11(a), "June 20, 2025" is the final payment date associated with the bond ID "103" in the bond data. The bond type determination unit 21 compares this final payment date, "June 20, 2025," with the transfer reference date, "March 31, 2025." In this case, because the final payment date is later than the transfer reference date, the bond type determination unit 21 determines the bond type to be a "long-term bond."

[0053] In the example of Figure 11(a), "February 27, 2025" is the final payment date associated with the bond ID "104" in the bond data. The bond type determination unit 21 compares this final payment date, "February 27, 2025," with the transfer reference date, "March 31, 2025." In this case, because the final payment date is before the transfer reference date, the bond type determination unit 21 determines the bond type to be a "short-term bond."

[0054] Next, the transfer bond data update unit 22 refers to the latest transaction data and compares the bond type determination result of the bond type determination unit 21 with the type of the latest transaction data.

[0055] As a result of the comparison, the transfer claim data update unit 22 extracts the latest transaction data for which the claim type differs from the claim type determination result. The transfer claim data update unit 22 updates the transfer claim data by registering the specified batch processing execution date as the transfer date, the extracted claim ID as the claim ID, and the claim balance associated with the extracted claim ID in the transfer claim data. Furthermore, based on the comparison result, the transfer claim data update unit 22 registers the type of transfer (from long-term claim to short-term claim or from short-term claim to long-term claim) as the transfer type in the transfer claim data, thereby updating the transfer claim data.

[0056] For example, the transfer claim data update unit 22 compares the claim type "long-term" for claim ID "100" in the latest transaction data in Figure 11(b) with the judgment result of the claim type judgment unit 21 for claim ID "100," which is "short-term claim." As a result of the comparison, the transfer claim data update unit 22 determines that the claim types are different. Therefore, the transfer claim data update unit 22 extracts the claim ID "100" and the claim balance "1,200,000" associated with claim ID "100" from the latest transaction data in Figure 11(b).

[0057] The transfer claim data update unit 22 registers "March 31, 2024", which is the last day of the batch processing execution month, as the transfer date in the transfer claim data of Figure 11(c). The transfer claim data update unit 22 registers the extracted claim balance "1,200,000" in the claim balance associated with claim ID "100" in the transfer claim data of Figure 11(c).

[0058] 11(a) and (b), the bond with bond ID "100" will become a short-term bond with a period of less than one year until the final payment date in the batch processing execution month "2024 / 3", and will therefore change from a long-term bond to a short-term bond. Therefore, the transfer bond data update unit 22 registers "long (long-term) → short (short-term)" as the transfer type associated with bond ID "100" in the transfer bond data in Figure 11(c).

[0059] As a result of the transfer bond data update unit 22 registering each piece of data related to the bond ID "100" in the transfer bond data, the transfer bond data is updated to the transfer bond data shown in FIG. 11(c).

[0060] Next, the transfer claim data update unit 22 compares the claim type "long-term" for claim ID "101" in the latest transaction data in Figure 11(b) with the judgment result "long-term claim" for claim ID "101" by the claim type judgment unit 21. As a result of the comparison, the transfer claim data update unit 22 finds that both are long-term claims and therefore the same. Therefore, the transfer claim data update unit 22 ends processing for the claim with claim ID "101".

[0061] Next, the transfer claim data update unit 22 compares the claim type "long-term" for claim ID "102" in the latest transaction data in Figure 11(b) with the judgment result of the claim type judgment unit 21 for claim ID "102," which is "short-term claim." As a result of the comparison, the transfer claim data update unit 22 determines that the claim types are different. Therefore, the transfer claim data update unit 22 extracts the claim ID "102" and the claim balance "600,000" associated with claim ID "102" from the latest transaction data in Figure 11(b).

[0062] The transfer claim data update unit 22 registers "March 31, 2024", which is the last day of the batch processing execution month, as the transfer date in the transfer claim data of Figure 11(c), as shown in Figure 11. The transfer claim data update unit 22 registers the extracted claim balance "600,000" in the claim balance associated with claim ID "102" in the transfer claim data of Figure 11(c).

[0063] 11(a) and (b), the bond with bond ID "102" is partially advanced on transaction date "2024 / 3 / 22" and becomes a short-term bond with a period until the final payment date of less than one year, changing from a long-term bond to a short-term bond. Therefore, the transfer bond data update unit 22 registers "long (long-term) → short (short-term)" as the transfer type associated with bond ID "102" in the transfer bond data in FIG. 11(c).

[0064] As a result of the transfer bond data update unit 22 registering each piece of data related to the bond ID "102" in the transfer bond data, the transfer bond data is updated to the transfer bond data shown in FIG. 11(c).

[0065] Next, the transfer claim data update unit 22 compares the claim type "short-term" for claim ID "103" in the latest transaction data in Figure 11(b) with the judgment result of the claim type judgment unit 21 for claim ID "103," which is "long-term claim." As a result of the comparison, the transfer claim data update unit 22 determines that the claim types are different. Therefore, the transfer claim data update unit 22 extracts the claim ID "103" and the claim balance "1,500,000" associated with claim ID "103" from the latest transaction data in Figure 11(b).

[0066] The transfer claim data update unit 22 registers "March 31, 2024", which is the last day of the batch processing execution month, as the transfer date in the transfer claim data of Figure 11(c), as shown in Figure 11. The transfer claim data update unit 22 registers the extracted claim balance "1,500,000" in the claim balance associated with claim ID "103" in the transfer claim data of Figure 11(c).

[0067] As shown in Figures 11(a) and (b), the bond with bond ID "103" will have its term extended on the transaction date "March 25, 2024," and will become a long-term bond with a period of more than one year until the final payment date, changing from a short-term bond to a long-term bond. Therefore, the transfer bond data update unit 22 registers "short (short-term) → long (long-term)" as the transfer type associated with bond ID "103" in the transfer bond data in Figure 11(c).

[0068] As a result of the transfer bond data update unit 22 registering each piece of data related to the bond ID "103" in the transfer bond data, the transfer bond data is updated to the transfer bond data shown in FIG. 11(c).

[0069] Next, the transfer claim data update unit 22 compares the claim type "short-term" for claim ID "104" in the latest transaction data in Figure 11(b) with the judgment result of the claim type judgment unit 21 for claim ID "104", which is "short-term claim". As a result of the comparison, the transfer claim data update unit 22 finds that both are short-term claims and therefore the same. Therefore, the transfer claim data update unit 22 ends processing for the claim with claim ID "104".

[0070] (Step S2: Journal entry detail data creation and credit data update processing) The journal entry detail data update unit 23 automatically starts the transfer credit data creation process in conjunction with the update of the transfer credit data. Note that the output control unit 26 may display the journal entry linked data creation process screen 7 as shown in Fig. 12, and the transfer credit data creation and credit data update process may be started by the person in charge operating it.

[0071] (Journal entry data creation) The journal entry detail data update unit 23 references the journal entry setting master table 11 and acquires debit and credit items based on the transfer type of the transfer credit data. The journal entry detail data update unit 23 registers the credit balance as the debit amount and credit amount in the journal entry detail data based on the transfer credit data, with the credit ID and the transfer date as the occurrence date, and updates the journal entry detail data. The journal entry detail data update unit 23 registers the acquired debit item and the acquired credit item in the journal entry detail data and updates the journal entry detail data.

[0072] For example, the journal entry detail data update unit 23 references the journal entry setting master table 11 and acquires the debit item "short-term loan" and the credit item "long-term loan" based on the transfer type "long-term to short-term" of the receivable ID "100" in the transfer receivable data in Figure 13(a). The journal entry detail data update unit 23 registers "100" as the receivable ID and "March 31, 2024", which is the last day of the batch processing execution month, as the occurrence date in the journal entry detail data.

[0073] The journal entry detail data update unit 23 registers the "short-term loan" acquired as the debit item and the "long-term loan" acquired as the credit item in the journal entry detail data related to the claim ID "100." The journal entry detail data update unit 23 registers the claim balance "1,200,000" for the claim ID "100" in the transfer claim data in Figure 13(a) as the debit amount and credit amount related to the claim ID "100" in the journal entry detail data.

[0074] As a result of the journal entry detail data update unit 23 registering each piece of data related to the bond ID "100" in the journal entry detail data, the journal entry detail data is updated to that shown in FIG. 13(b).

[0075] Next, the journal entry detail data update unit 23 references the journal entry setting master table 11 and acquires the debit item "short-term loan" and the credit item "long-term loan" based on the transfer type "long-term to short-term" of the receivable ID "102" in the transfer receivable data in Figure 13(a). The journal entry detail data update unit 23 registers "102" as the receivable ID and "March 31, 2024", which is the last day of the batch processing execution month, as the occurrence date in the journal entry detail data.

[0076] The journal entry detail data update unit 23 registers the "short-term loan" acquired as the debit item and the "long-term loan" acquired as the credit item in the journal entry detail data related to the claim ID "102." The journal entry detail data update unit 23 registers the claim balance "600,000" of the claim ID "102" in the transfer claim data of Figure 13(a) as the debit amount and credit amount in the journal entry detail data related to the claim ID "102."

[0077] As a result of the journal entry detail data update unit 23 registering each piece of data related to the bond ID "102" in the journal entry detail data, the journal entry detail data is updated to that shown in FIG. 13(b).

[0078] Next, the journal entry detail data update unit 23 references the journal entry setting master table 11 and acquires the debit item "long-term loan" and the credit item "short-term loan" based on the transfer type "short-term to long-term" of the receivable ID "103" in the transfer receivable data in Figure 13(a). The journal entry detail data update unit 23 registers "103" as the receivable ID and "March 31, 2024", which is the last day of the batch processing execution month, as the occurrence date in the journal entry detail data.

[0079] The journal entry detail data update unit 23 registers the "long-term loan" acquired as the debit item and the "short-term loan" acquired as the credit item in the journal entry detail data related to the claim ID "103." The journal entry detail data update unit 23 registers the claim balance "1,500,000" of the claim ID "100" in the transfer claim data in Figure 13(a) as the debit amount and credit amount in the journal entry detail data related to the claim ID "103."

[0080] As a result of the journal entry detail data update unit 23 registering each piece of data related to the bond ID "103" in the journal entry detail data, the journal entry detail data is updated to that shown in FIG. 13(b).

[0081] (Receivables data update) The claim data update unit 24 refers to the transfer claim data and the claim data, and updates the claim type of the claim data related to the claim ID of the transfer claim data to a claim type corresponding to the transfer type of the transfer claim data.

[0082] For example, the claim data update unit 24 refers to the transfer claim data and claim data in Figure 13(a) for the claim with claim ID "100." The claim data update unit 24 changes the claim type associated with claim ID "100" in the claim data to "short-term" in accordance with the transfer type "long to short" in the transfer claim data in Figure 13(a) and registers it. As a result, the claim data is updated to the claim data in Figure 13(c).

[0083] Next, the claim data update unit 24 refers to the transfer claim data and claim data in Figure 13(a) for the claim with claim ID "102". The claim data update unit 24 changes the claim type associated with claim ID "102" in the claim data to "short-term" in accordance with the "long-term to short-term" transfer type in the transfer claim data in Figure 13(a) and registers it. As a result, the claim data is updated to the claim data in Figure 13(c).

[0084] Next, the claim data update unit 24 refers to the transfer claim data and claim data in Figure 13(a) for the claim with claim ID "103". The claim data update unit 24 changes the claim type associated with claim ID "103" in the claim data to "long-term" in accordance with the transfer type "short to long" in the transfer claim data in Figure 13(a) and registers it. As a result, the claim data is updated to the claim data in Figure 13(c).

[0085] (Step S3: Journal entry detail data creation process) The latest transaction data update unit 25 registers each process, such as a deposit process, that occurs in daily bond transactions in the latest transaction data based on the bond ID of the bond data, and updates the latest transaction data.

[0086] For example, based on the bond data in Figure 14(a), if 100,000 yen is transferred on transaction date April 10, 2024 for a bond with bond ID "100," the latest transaction data update unit 25 registers and updates the data as bond ID "100" in the latest transaction data in Figure 14(b). The same registration is performed for bond IDs "101" to "104," and the latest transaction data is updated to the latest transaction data in Figure 14(b). Below, the bond with bond ID "100" will be explained, but the same applies to bond IDs "101" to "104."

[0087] Next, the journal entry detail data update unit 23 refers to the journal entry setting master table 11 in Figure 14(c) based on the type "short-term", transaction content "deposit", and route "transfer" of the bond ID "100" in the latest transaction data. The journal entry detail data update unit 23 obtains the debit item "deposit" and the credit item "short-term loan" from the journal entry setting master table 11 in Figure 14(c).

[0088] Next, the journal entry detail data update unit 23 registers "100" as the bond ID, the transaction date of the latest transaction data in Figure 14(b) "April 10, 2024" as the occurrence date, and the transaction amount of the latest transaction data in Figure 14(b) "100,000" as the debit amount and credit amount in the journal entry detail data. The journal entry detail data update unit 23 registers "deposit" acquired as the debit item and "short-term loan" acquired as the credit item related to the bond ID "100" in the journal entry detail data in the journal entry detail data, and updates it to the journal entry detail data shown in Figure 15.

[0089] (Effects of the embodiment) As is clear from the above description, the task support device 1 according to the embodiment can achieve the following effects.

[0090] (1) For companies that handle credit management, the system manages credit types (long-term or short-term) and final repayment dates as data, enabling automatic determination of whether or not credit transfers are necessary, and if transfers are necessary, generates a transfer journal entry and registers it in the data. This significantly reduces the workload of the person in charge.

[0091] (2) The system automatically processes the journal entry process and updates data related to receivables, from determining whether or not a transfer is necessary, thereby improving the accuracy of each data item.

[0092] (3) It is now possible to store data related to receivables and journal entries in the same system. This makes it easier to investigate data such as transfer history and transaction details, and improves the efficiency of investigations.

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

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

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

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

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

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

[0099] Furthermore, with regard to the task support device 1, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0100] For example, all or any part of the processing functions of the business support device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support device 1 as needed. That is, a storage unit such as a ROM or HDD stores a computer program for cooperating with the OS to issue instructions to the CPU and perform various processes. The computer program is executed by being loaded into RAM, and cooperates with the CPU to constitute the control unit 3.

[0101] In addition, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via any network, and all or part of it may be downloaded as needed.

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

[0103] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific structure and reading procedure for reading a recording medium in the business support device 1 described in the embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

[0104] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

[0105] The business support device 1 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as an information processing device connected to any peripheral device. The information processing device may be realized by installing software (including programs or data) that realizes the processing described in this embodiment.

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

[0107] The present invention is suitable for application to support operations in the financial industry as a whole, including financial institutions and non-banks that perform credit management operations. [Explanation of symbols]

[0108] 1 Business support equipment 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / output interface section 6 Input Devices 7 Output Devices 11 Journal entry setting master table 12. Bond data storage unit 13 Latest transaction data storage unit 14 Transferable Claims Data Storage Unit 15 Journal entry detail data storage section 21 Debt Classification Department 22 Transferable Credit Data Update Department 23 Journal entry detail data update section 24. Bond Data Update Department 25 Latest Transaction Data Update Section 26 Output control section

Claims

1. a claim type determination unit that refers to claim data including at least claim identification information assigned to each claim, claim type classifying the claim as long-term or short-term, and final payment date, compares the transfer reference date set by adding a certain period from the update execution date with the final payment date of the claim data, and determines the claim type to be a short-term claim if the final payment date and the transfer reference date are the same day or if the final payment date is a date earlier than the transfer reference date, and determines the claim type to be a long-term claim if the final payment date is a date later than the transfer reference date; a transfer claim data update unit that refers to the latest transaction data including at least the claim identification information, the claim type, the transaction date, and the claim balance, compares the judgment result of the claim type judgment unit with the claim type, extracts the latest transaction data in which the judgment result and the claim type differ, registers the latest transaction data in the transfer claim data together with the update execution date and the transfer type of transfer from long-term claim to short-term claim or from short-term claim to long-term claim, and updates the transfer claim data; a journal entry detail data updating unit that registers a journal entry for transferring a long-term receivable to a short-term receivable or a short-term receivable to a long-term receivable in the journal entry detail data based on the transfer receivable data, and updates the journal entry detail data; a claim data updating unit that updates the claim type of the claim data based on the transfer claim data; A business support device comprising:

2. The business support device described in claim 1, characterized in that when transferring from long-term receivables to short-term receivables based on the transfer receivables data, the journal entry detail data update unit registers an account item related to short-term receivables as the debit item of the journal entry detail data and an account item related to long-term receivables as the credit item, and when transferring from short-term receivables to long-term receivables, registers an account item related to long-term receivables as the debit item of the journal entry detail data and an account item related to short-term receivables as the credit item, and updates the journal entry detail data.

3. 3. The business support device according to claim 2, wherein an account item related to short-term receivables is "short-term loans" and an account item related to long-term receivables is "long-term loans."

4. a latest transaction data update unit that updates the latest transaction data based on the updated bond data, The business support device of claim 1, characterized in that, based on the updated latest transaction data, the journal entry detail data update unit generates journal entry detail data with the debit item set to "cash" and the credit item set to "long-term loan" if the receivable type is "long-term", the transaction content is "deposit" and the route is "cash", generates journal entry detail data with the debit item set to "deposit" and the credit item set to "long-term loan" if the receivable type is "long-term", the transaction content is "deposit" and the route is "transfer", generates journal entry detail data with the debit item set to "deposit" and the credit item set to "long-term loan", generates journal entry detail data with the debit item set to "cash" and the credit item set to "short-term loan" if the receivable type is "short-term", the transaction content is "deposit" and the route is "cash", generates journal entry detail data with the debit item set to "deposit" and the credit item set to "short-term loan", and registers and updates the journal entry detail data.

5. The business support device described in claim 1, characterized in that the debt type judgment unit uses the update execution year and month instead of the update execution date, and sets the transfer reference date to one year after the update execution year and month and the last day of the corresponding update execution month.

6. a claim type determination step in which the claim type determination unit refers to claim data including at least claim identification information assigned to each claim, claim type classifying the claim as long-term or short-term, and final payment date, compares the transfer reference date set by adding a certain period from the update execution date with the final payment date of the claim data, and determines the claim type to be a short-term claim if the final payment date and the transfer reference date are the same day or if the final payment date is a date earlier than the transfer reference date, and determines the claim type to be a long-term claim if the final payment date is a date later than the transfer reference date; a transfer claim data update step in which the transfer claim data update unit refers to the latest transaction data including at least the claim identification information, the claim type, the transaction date, and the claim balance, compares the judgment result of the claim type judgment step with the claim type, extracts the latest transaction data in which the claim type differs from the judgment result, registers the latest transaction data in the transfer claim data together with the update execution date and the transfer type of transfer from long-term claim to short-term claim or from short-term claim to long-term claim, and updates the transfer claim data; a journal entry detail data update step in which a journal entry detail data update unit registers a journal entry for transferring a long-term receivable to a short-term receivable or a short-term receivable to a long-term receivable in the journal entry detail data based on the transfer receivable data, and updates the journal entry detail data; a claim data updating step in which a claim data updating unit updates the claim type of the claim data based on the transfer claim data; A business support method having the above.

7. Computer, a claim type determination unit that refers to claim data including at least claim identification information assigned to each claim, claim type classifying the claim as long-term or short-term, and final payment date, compares the transfer reference date set by adding a certain period from the update execution date with the final payment date of the claim data, and determines the claim type to be a short-term claim if the final payment date and the transfer reference date are the same day or if the final payment date is a date earlier than the transfer reference date, and determines the claim type to be a long-term claim if the final payment date is a date later than the transfer reference date; a transfer claim data update unit that refers to the latest transaction data including at least the claim identification information, the claim type, the transaction date, and the claim balance, compares the judgment result of the claim type judgment unit with the claim type, extracts the latest transaction data in which the judgment result and the claim type differ, registers the latest transaction data in the transfer claim data together with the update execution date and the transfer type of transfer from long-term claim to short-term claim or from short-term claim to long-term claim, and updates the transfer claim data; a journal entry detail data updating unit that registers a journal entry for transferring a long-term receivable to a short-term receivable or a short-term receivable to a long-term receivable in the journal entry detail data based on the transfer receivable data, and updates the journal entry detail data; a claim data updating unit that updates the claim type of the claim data based on the transfer claim data; A business support program that functions as a

Images