Data management device, data management method, and data management program

Abstract

The challenges include appropriately evaluating transactions and making the cash flow cycle more transparent. [Solution] In this embodiment, the data management device comprises a reception unit and a calculation unit. The reception unit is characterized by receiving input of payment data related to a transaction and deposit data related to the transaction. The calculation unit is characterized by calculating the amount equivalent to interest incurred from the payment to the deposit and calculating the valuation amount of the transaction based on the amount equivalent to interest.

Description

Technical Field

[0004] , , ,

[0006] , , , ,

[0005] , , ,

[0003] , , , ,

[0001] The present invention relates to a data management device, a data management method, and a data management program.

Background Art

[0002] Patent Document 1 discloses a financing management system capable of flexibly reorganizing repayment schedule data according to the circumstances of debtors.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In business in trading companies and the like, when evaluating a transaction, there is a practice of evaluating a series of transactions after considering the amount equivalent to interest generated from the payment of the price of the purchased goods to the receipt of the price of the sold goods.

[0005] If the amount equivalent to interest generated from the purchase to the receipt of goods is not considered when evaluating a transaction, simply because the amount of the transaction amount is large, even if the period from purchase to receipt is long, the transaction will be evaluated, so there may be a weak awareness of trying to shorten the period from payment to receipt. As a result, the period until receipt may become long, and the cash flow cycle may be prolonged.

[0006] The present invention has been made in view of the above problems, and in the present invention, in a transaction, by evaluating the transaction considering the amount equivalent to interest generated from payment to receipt, the cash flow cycle is made visible, and by evaluating the transaction considering interest, the purpose is to improve the business.

Means for Solving the Problems

[0007] To solve the above-mentioned problems and achieve the objective, the data management device according to the present invention is characterized by comprising: a reception unit that receives input of payment data related to a transaction and deposit data related to the transaction; and a calculation unit that calculates the amount equivalent to interest incurred from the payment to the deposit and calculates the value of the transaction based on the amount equivalent to interest.

[0008] Furthermore, in the data management device according to the present invention, the calculation unit may calculate the deposit and withdrawal amounts based on the payment data and the deposit data, and calculate the valuation amount based on the deposit and withdrawal amounts and the interest equivalent amount.

[0009] Furthermore, in the data management device according to the present invention, the calculation unit may calculate a provisional value of the interest equivalent amount related to the transaction on a predetermined date.

[0010] Furthermore, the data management device according to the present invention may further include a display control unit that displays a deposit and withdrawal statement in a list format showing the payment data, the deposit data, and the interest equivalent amount on the display unit.

[0011] Furthermore, the data management device according to the present invention may further include a display control unit that displays a deposit and withdrawal summary table showing the valuation amount for each transaction on the display unit.

[0012] Furthermore, in the data management device according to the present invention, the display control unit may further display the company's fund balance on the display unit.

[0013] Furthermore, the data management method according to the present invention is characterized by including a reception step in which a reception unit receives input of payment data related to a transaction and deposit data related to the transaction, and a calculation step in which a calculation unit calculates the amount equivalent to interest incurred from the payment to the deposit, and calculates the valuation amount of the transaction based on the amount equivalent to interest.

[0014] Furthermore, the data management program according to the present invention is characterized in that the information processing device functions as a receiving means for receiving input of payment data related to a transaction and deposit data related to the transaction, and as a calculation means for calculating the interest equivalent amount incurred from the payment to the deposit and calculating the valuation amount of the transaction based on the interest equivalent amount. [Effects of the Invention]

[0015] This invention visualizes the cash flow cycle by evaluating transactions while taking into account the amount equivalent to interest incurred from payment to receipt, and also has the effect of improving business by evaluating transactions while taking interest into account. [Brief explanation of the drawing]

[0016] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the data management device according to this embodiment. [Figure 2] Figure 2 shows an example of a deposit / withdrawal data table when a deposit occurs. [Figure 3] Figure 3 shows an example of a deposit / withdrawal data table when a payment occurs. [Figure 4] Figure 4 shows an example of a detailed data table. [Figure 5] Figure 5 shows an example of a summary table data table. [Figure 6] Figure 6 shows an overview of the processing performed by the data management device according to this embodiment. [Figure 7] Figure 7 is a flowchart showing the flow of interest calculation processing performed by the data management device according to the embodiment. [Figure 8] Figure 8 shows an example of the process for creating a detailed table data by the data management device according to the embodiment. [Figure 9] Figure 9 shows an example of the process for creating a detailed table data by the data management device according to the embodiment. [Figure 10]FIG. 10 is a diagram showing an example of a detailed list data table creation process performed by the data management device according to the embodiment. [Figure 11] FIG. 11 is a flowchart showing the flow of creating a statement of receipts and payments performed by the data management device according to the embodiment. [Figure 12] FIG. 12 is a diagram showing an example of a screen for receiving an instruction to create a statement of receipts and payments. [Figure 13] FIG. 13 is a diagram showing an example of a statement of receipts and payments. [Figure 14] FIG. 14 is a flowchart showing the flow of creating a summary statement of receipts and payments performed by the data management device according to the embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a screen for receiving an instruction to create a summary statement of receipts and payments. [Figure 16] FIG. 16 is a diagram showing an example of a summary statement of receipts and payments. [Figure 17] FIG. 17 is a diagram showing an example of an internal funds detailed list. [Figure 18] FIG. 18 is a diagram showing an example of the internal funds balance.

Embodiments for Carrying Out the Invention

[0017] Hereinafter, embodiments of the data management device, data management method, and data management program according to the present invention will be described in detail based on the drawings. Note that the present invention is not limited by this embodiment.

[0018] [1. Configuration] An example of the configuration of the data management device 100 according to this embodiment will be described with reference to FIG. 1 and the like. FIG. 1 is a block diagram showing an example of the configuration of the data management device 100.

[0019] The data management device 100 is built on, for example, a commercially available desktop personal computer. However, the data management device 100 is not limited to being built on a stationary information processing device such as a desktop personal computer; it may also be built on a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0020] The data management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the data management device 100 is connected to communicate via any communication path.

[0021] The communication interface unit 104 connects the data management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the data management device 100 and the server 200 so that they can communicate with each other, and is, for example, the internet or a LAN (Local Area Network). The data stored in the storage unit 106 may be stored in, for example, the server 200.

[0022] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), as well as a speaker or a printer. The input device 112 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality.

[0023] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used.

[0024] The storage unit 106 stores data such as the deposit / withdrawal data table 1, the statement data table 2, and the summary data table 3.

[0025] Figures 2 and 3 show examples of information stored in deposit / withdrawal data table 1. Deposit / withdrawal data table 1a shown in Figure 2 is an example of a table that holds information related to deposits, and deposit / withdrawal data table 1b shown in Figure 3 is an example of a table that holds information related to withdrawals (payments).

[0026] The deposit and withdrawal data tables 1a and 1b are tables that hold information related to deposits and withdrawals related to transactions. Each row in the deposit and withdrawal data tables 1a and 1b holds information such as the "voucher number," which is the voucher number related to the transaction; the "data category," which indicates whether each data is related to a deposit or a withdrawal (payment); the "transaction number," which is a number used to link and manage the series of transactions from payment to deposit; the "deposit / withdrawal date," which is the date on which the deposit or withdrawal occurred; the "deposit / withdrawal amount," which is the amount of the deposit or withdrawal; the "department," which is the department in charge of the transaction; and the "person in charge," which is the person in charge of the transaction. The data management device 100 performs interest calculations based on the input / output data tables 1a and 1b, etc.

[0027] The "transaction number" is managed in conjunction with the entire process from payment to receipt for each transaction. For example, for a transaction involving a particular product, the same transaction number is assigned from the time the product is purchased until the sales proceeds are received. In contrast, the "voucher number" is assigned to each individual action in the payment-to-receipt process. For example, the voucher number for the purchase of the product will be different from the voucher number for the receipt of the sales proceeds after the product is sold. The voucher number and transaction number are assigned when the payment details or receipt details are registered in the data management device 100.

[0028] Figure 4 shows an example of the information stored in the details data table 2. The details data table is a table that holds information about deposits and withdrawals related to transactions and information about interest calculations. In addition to the deposit and withdrawal information held in the deposit and withdrawal data table 1, the details data table 2 holds information about the amount equivalent to interest incurred from payment to receipt.

[0029] Each row in the details table 2 holds information such as: a "transaction number," which is a number used to link and manage the entire flow of transactions from payment to receipt; a "data category," which indicates whether each data item relates to a receipt or a withdrawal (payment); a "original voucher number," which indicates the voucher number to which the data in each row corresponds; a "department," which is the department responsible for the transaction; a "person in charge," which is the person in charge of the transaction; a "deposit / withdrawal date," which is the date on which the deposit or withdrawal took place; a "deposit / withdrawal amount," which is the amount of the deposit or withdrawal; an "interest amount," which indicates the amount of interest incurred from payment to receipt; and an "interest calculation date," which is the date and time on which the interest amount was calculated.

[0030] In Figure 4, rows 10, 30, and 40 in the details data table 2 represent information about transactions in which an outflow (payment) occurred, such as the purchase of goods. In this example, rows 10, 30, and 40 of the details data table 2 are created by copying the contents of the corresponding rows in the deposit and withdrawal data table 1b in Figure 3, namely rows 510, 530, and 540, respectively. Row 20 represents information about transactions in which an inflow occurred, such as the receipt of payment for goods sold. Row 20 of the details data table 2 is created, for example, by copying row 520 of the deposit and withdrawal data table 1a in Figure 2.

[0031] Furthermore, rows 11, 12, 13, 21, 31, and 41 in the details data table 2 represent the "interest amount," which is the amount equivalent to the interest incurred from payment to receipt, and specifically the amount incurred on a predetermined date, such as the end of the month. For example, in the case of row 12, as shown in row 10, payment for the goods was made on July 31st, and approximately 100,000 yen of company funds was withdrawn. Therefore, it is assumed that interest is incurred on the funds equivalent to these withdrawn company funds at a predetermined interest rate, and the equivalent interest amount is calculated. Based on this calculated equivalent interest amount, the transaction valuation is then calculated. On August 31st, the end of the month, the calculation unit 102b holds the value of the equivalent interest amount incurred from August 1st to August 31st as the "interest amount." Note that in the cases of rows 11, 12, 13, 31, and 41, the person in charge is temporarily borrowing company funds, so the "interest amount" will be a negative value. For line 21, since interest is paid on the deposited funds, the "interest amount" will be a positive value.

[0032] Figure 5 shows an example of the information stored in the summary table data table 3. The summary table data table 3 is a table that holds information on deposit information, withdrawal information, the amount equivalent to interest incurred from payment to deposit, and the valuation of the transaction considering the equivalent amount of interest. The summary table data table 3 holds information such as the "transaction number," which is a number used to link and manage the series of transactions from payment to deposit; the "withdrawal amount," which shows the withdrawal (payment) amount; the "deposit amount," which shows the deposit amount; the "interest incurred amount," which shows the amount equivalent to interest incurred from payment to deposit; and the "valuation amount," which is the valuation of the transaction taking the equivalent amount of interest into account. In the example in Figure 5, goods are purchased for 100,000 yen and sold for 120,000 yen, so the profit is 20,000 yen. However, interest of 245 yen is incurred on the borrowed funds associated with purchasing the goods, so the actual valuation of this transaction, after deducting the interest incurred, is 19,755 yen.

[0033] Returning to Figure 1, the control unit 102 is a CPU or similar component that comprehensively controls the data management device 100. The control unit 102 has internal memory for storing control programs such as the OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs.

[0034] Functionally, the control unit 102 comprises a reception unit 102a, a calculation unit 102b, a display control unit 102c, and the like. The reception unit 102a receives payment and deposit information related to transactions from the user. The calculation unit 102b calculates the amount equivalent to interest incurred from payment to deposit, and calculates the valuation amount of the transaction taking interest into account. The display control unit 102c generates various table data such as deposit and withdrawal statements and deposit and withdrawal summary statements, and displays the generated data on the input device 112. Details of these functions will be described later.

[0035] [2. Overview] Next, using Figure 6, we will explain the overall process performed by the data management device 100 according to this embodiment.

[0036] Let me briefly explain the outline of the present invention. For example, in businesses such as trading companies, it is customary to charge interest in order to fairly evaluate the performance of field departments. That is, the amount equivalent to the interest that would have been incurred if the amount used to purchase the goods had been borrowed during the period from the purchase of the goods to the receipt of payment is calculated, and the transaction is evaluated by taking this equivalent amount of interest into account.

[0037] If transactions were evaluated without considering the interest rate, there was a business challenge: for example, a lack of awareness of the need to collect payments as quickly as possible, leading to a longer cash flow cycle from procurement to receipt of funds. Furthermore, in performance evaluation, there was a tendency to prioritize large transaction amounts over long periods between procurement and receipt of funds, which was another business challenge. From a system perspective, there was also the inability to grasp actual performance while considering the collection / payment cycle for each transaction, and the difficulty in conducting fair evaluations of departments and individuals, as well as considering areas for improvement.

[0038] Therefore, in the data management device 100 according to the present invention, the receiving unit 102a receives input of payment data and deposit data related to the transaction, the calculation unit 102b calculates the amount equivalent to interest incurred from payment to deposit, and calculates the valuation amount of the transaction based on the said amount equivalent to interest.

[0039] In other words, as shown in Figure 6, the data management device 100 according to the present invention performs interest calculation processing in addition to standard payment input processing and deposit input processing. Here, payment input processing is the process of inputting payment data related to a transaction and reflecting it in the deposit / withdrawal data table 1 and the statement data table 2. Deposit input processing is the process of inputting deposit data related to a transaction. This process updates the deposit / withdrawal data table 1 and the statement data table 2.

[0040] Furthermore, interest calculation processing involves, for example, calculating the amount of interest accrued during the period from payment to receipt, or calculating the amount of interest accrued during the current month on a predetermined date, such as the end of the month. In addition, the valuation of the transaction, taking into account the amount of interest, is also calculated.

[0041] Through payment entry processing, deposit entry processing, and interest calculation processing, data related to deposits and withdrawals, as well as interest amount data, are created for deposit and payment slips from the current month and earlier, and stored in the details data table 2. Each transaction stored in the deposit / withdrawal data table 1 and the details data table 2 is assigned a transaction number to enable tracking of the transaction flow, and the data from payment to entry is linked and managed together.

[0042] The data management device 100 according to this embodiment creates a deposit and withdrawal statement in the deposit and withdrawal statement creation process after the interest calculation process, and creates a deposit and withdrawal summary table in the deposit and withdrawal summary table creation process. In other words, the data management device 100 outputs two types of tables with different functions: a deposit and withdrawal statement and a deposit and withdrawal summary table. The deposit and withdrawal statement is a table that shows payment (withdrawal) data, deposit data, and interest equivalent amount in a list format, and is a table that shows when and how much payment, deposit, and interest occurred. The deposit and withdrawal statement allows users to check the history of payments and deposits with payments and deposits linked for each transaction. In contrast, the deposit and withdrawal summary table is a table that summarizes how much profit was made in each transaction, taking interest into account, and is a table that shows the profitability of transactions when interest is taken into account. The deposit and withdrawal summary table makes it possible to calculate summaries and valuations by, for example, month or department.

[0043] As described above, the data management device 100 according to this embodiment allows for the confirmation of transaction deposits and withdrawals by, for example, month, department, and transaction, and enables visualization of the payment collection status. Furthermore, by disseminating the aggregated results to the field departments, departments and transactions that need improvement can be made visible, leading to improvements in the cash flow cycle. In addition, by adding the interest amount based on the collection cycle to the evaluation criteria, not just the transaction amount, it is possible to fairly evaluate and improve the satisfaction of the field departments. Moreover, by conducting evaluations that take interest into account, it becomes possible to negotiate with customers regarding collection conditions and pricing based on the obtained evaluation amount, thereby improving the profitability of the business.

[0044] [3. Specific examples of processing] A specific example of the processing performed by the data management device 100 configured as described above will be explained with reference to Figures 7 and 8-16. Figure 7 is a flowchart showing the flow of the interest rate calculation processing performed by the data management device 100 according to the embodiment.

[0045] The reception unit 102a waits to receive input from the user regarding payment (withdrawal) related to a transaction (step S100). When the reception unit receives input from the user indicating that it will accept input regarding payment related to a transaction (step S100 Yes), the process proceeds to step S110. In step S110, the reception unit 102a receives input of payment data related to the transaction and records the payment data related to the transaction in the deposit / withdrawal data table 1. As an example, as shown in Figure 3, if on July 31st, a payment of 100,000 yen for goods with transaction number TB003001 and voucher number IKM000003001 is made, the reception unit 102a adds row 510 to the deposit / withdrawal data table 1. Furthermore, if on September 30th, a payment of 1,000,000 yen is made for the purchase of goods with invoice number IKM000003002 in transaction number TB003002, and a payment of 500,000 yen is made for the purchase of goods with invoice number IKM000003003 in transaction number TB003003, the reception unit 102a will add rows 530 and 540 to the deposit / withdrawal data table 1. Also, if on October 30th, a payment of 500,000 yen is made for the purchase of goods with invoice number IKM000003004 in transaction number TB003004, the reception unit 102a will add row 550 to the deposit / withdrawal data table 1.

[0046] Furthermore, when the deposit / withdrawal data table 1 is updated, the reception unit 102a transfers the updated information to the details data table 2 and updates the details data table 2. For example, as shown in Figure 8, if on July 31st, a payment of 100,000 yen was made for the purchase of goods with transaction number TB003001 and voucher number IKM000003001, and as shown in Figure 3, row 510 is added to the deposit / withdrawal data table 1, the reception unit 102a transfers the contents of row 510 in the deposit / withdrawal data table 1 to row 10 in the details data table 2 shown in Figure 8, and adds row 10 to the details data table 2. Furthermore, if, on October 30, a payment of 500,000 yen for goods with transaction number TB003004 (invoice number IKM000003004) is made, and row 550 is added to deposit / withdrawal data table 1 as shown in Figure 3, then, as shown in Figure 8, the reception unit 102a copies the contents of row 550 of deposit / withdrawal data table 1 to row 50 of detail data table 2, and adds row 50 to detail data table 2.

[0047] In step S120, the calculation unit 102b performs periodic interest calculations on a predetermined date, such as the end of the month, and calculates a provisional value of the amount equivalent to the interest related to the transaction.

[0048] The interest calculation process in step S120 will be explained using Figure 9. The formula for calculating the interest equivalent amount (interest amount) related to the transaction is: deposit / withdrawal amount × interest rate × (1 / 365) × number of days elapsed. Here, the number of days elapsed is the number of days elapsed from the deposit / withdrawal date to the interest calculation date. However, if the withdrawal date is earlier than the previous interest calculation date (the closing date for interest calculation), the interest incurred before the previous interest calculation date has already been calculated, so it becomes the number of days elapsed from the previous interest calculation date to the interest calculation date.

[0049] First, let's explain the interest amount when the interest calculation date is July 31st, as shown in row 11 of Figure 9. In this case, as shown in row 10, a payment of 100,000 yen is made on July 31st. In this case, the deposit / withdrawal amount is -100,000 yen. The interest rate is, for example, 1.5%. Only one value for this interest rate can be set in the system, for example, and it is stored in the memory unit 106. Since the interest calculation date is July 31st and the deposit / withdrawal date is also July 31st, the number of elapsed days is 0, but we round up to 1 day if it is less than 1 day. Therefore, the amount of interest incurred is -100,000 × 0.015 × (1 / 365) × 1, which is rounded down to -4 yen if it is less than 1 yen.

[0050] The calculation unit 102b adds data to the details data table 2 based on the calculated interest rate. Specifically, the calculation unit 102b adds "July 31, 2024" to the "Interest Calculation Date" in row 11 of the details data table 2, and adds the value "-4" to the "Interest Amount". The calculation unit 102b also updates row 11 of the details data table 2 by transferring the values ​​from row 10 to the "Transaction Number", "Data Category", "Original Voucher Number", "Department", and "Person in Charge" fields. By performing these operations, the calculation unit 102b adds row 11 to the details data table 2. The calculation unit 102b updates the details data table 2 in the data format shown in row 600.

[0051] Next, we will explain the interest amount when the interest calculation date is August 31st, as shown in row 12 of Figure 9. In this case, as shown in row 10, a payment of 100,000 yen was made on July 31st. In this case, the balance of deposits and withdrawals is -100,000 yen. The interest rate is 1.5%. Regarding the number of days elapsed, since the withdrawal date is earlier than the previous interest calculation date (July 31st), the number of days elapsed for interest calculation is calculated from the previous interest calculation date, not the withdrawal date. Therefore, the number of days elapsed is from August 1st to August 31st, which is 31 days. Consequently, the amount of interest incurred is -100,000 × 0.015 × (1 / 365) × 31, which is rounded down to the nearest yen, resulting in -123 yen. Therefore, the calculation unit 102b adds "August 31, 2024" to the "Interest Calculation Date" in row 12 of the detailed statement data table 2, and adds the value "-123" to the "Interest Amount". In addition, the calculation unit 102b updates row 12 of the detailed statement data table 2 by transferring the values ​​from row 10 to the "Transaction Number", "Data Category", "Original Voucher Number", "Department", and "Person in Charge" fields. By performing these operations, the calculation unit 102b adds row 12 to the detailed statement data table 2.

[0052] Furthermore, as another example of interest calculation, we will explain the case shown in Figure 4. In Figure 4, rows 13, 31, and 41 show the interest amounts corresponding to transaction numbers TB003001, TB003002, and TB003003, respectively, when the interest calculation date is September 30th. In the case of row 13, transaction number TB003001 involves a payment of 100,000 yen on July 31st. In this case, the balance is -100,000 yen. The interest rate is 1.5%. The elapsed period is from September 1st to September 30th, which is 30 days. Therefore, the amount of interest incurred is given by -100,000 × 0.015 × (1 / 365) × 30.

[0053] Furthermore, in the case of row 31 and row 40, the resulting interest amounts are -1,000,000 × 0.015 × (1 / 365) × 1 and -500,000 × 0.015 × (1 / 365) × 1, respectively.

[0054] The calculation unit 102b performs this process periodically to calculate the interest equivalent amount. In this embodiment, the date on which the interest equivalent amount is calculated is described as the end of the month, but in this embodiment, the date on which the interest equivalent amount is calculated periodically may be a day other than the end of the month, and the interest equivalent amount may be calculated at intervals other than one month, such as quarterly. Furthermore, the calculation unit 102b can perform the process of calculating the interest equivalent amount at any time, allowing the interest amount to be checked in real time.

[0055] Returning to Figure 7, the processing when a deposit occurs will be explained next. The reception unit 102a waits to receive input from the user regarding the deposit related to the transaction (step S130). When the reception unit receives input from the user indicating that it will accept input from the user regarding the deposit related to the transaction (step S100 Yes), the process proceeds to step S140. In step S140, when the reception unit 102a receives input of the deposit data related to the transaction, the reception unit 102a records the deposit details.

[0056] For example, as shown in Figure 2, if on September 30th, a payment of 120,000 yen for the sale of goods with transaction number TB003001 and voucher number IKS000003001 is received, the reception unit 102a adds row 520 to the deposit / withdrawal data table 1. Also, when the deposit / withdrawal data table 1 is updated, the reception unit 102a transfers the updated information to the details data table 2 and updates the details data table 2. For example, as shown in Figure 10, if on September 30th, a payment of 120,000 yen for the sale of goods with voucher number IKS000003001 is received, the reception unit 102a transfers the contents of row 520 in the deposit / withdrawal data table 1 to row 20 in the details data table 2 shown in Figure 10 and adds row 20 to the details data table 2.

[0057] Next, in step S150, the calculation unit 102b calculates the interest amount. For example, let's explain the interest amount when the interest calculation date is September 30th, as shown in rows 13 and 21 of Figure 4. First, as shown in row 13, the interest on the payment amount is calculated. In this case, as shown in row 10, a payment of 100,000 yen was made on July 31st. In this case, the amount of income and expenses is -100,000 yen. The interest rate is 1.5%. As for the number of days elapsed, row 13 calculates the interest that has accrued since the previous interest calculation date (August 31st), so the number of days elapsed is the number of days from September 1st to September 31st, which is 31 days. Therefore, the amount of interest that will accrue is -100,000 × 0.015 × (1 / 365) × 31, which is -123 yen. Therefore, the calculation unit 102b adds "September 30, 2024" to the "Interest Calculation Date" in row 13 of the detailed statement data table 2, and adds the value "-123" to the "Interest Amount". In addition, the calculation unit 102b updates row 13 of the detailed statement data table 2 by copying the values ​​from row 10 to the "Transaction Number", "Data Category", "Original Voucher Number", "Department", and "Person in Charge" items in row 13.

[0058] Furthermore, the calculation unit 102b calculates the interest on the deposit amount in row 21. In this case, as shown in row 21, a payment of 120,000 yen was made on September 30. In this case, the deposit and withdrawal amounts will be +120,000 yen. The interest rate will be 1.5%. Regarding the number of days elapsed, the deposit date is September 30 and the interest calculation date is September 30, so the number of days elapsed is 0, but it is rounded up to 1 day. Therefore, the amount of interest incurred is 120,000 × 0.015 × (1 / 365) × 1, which is +5 yen. Accordingly, the calculation unit 102b adds "September 30, 2024" to "Interest Calculation Date" in row 21 of the details data table 2, and adds the value "5" to "Interest Amount". Furthermore, the calculation unit 102b updates row 21 of the details data table 2 by transferring the values ​​from row 20 to the items "Transaction Number," "Data Category," "Original Voucher Number," "Department," and "Person in Charge" in row 21. Through the above process, the details data table 2, which serves as the basic data for creating the deposit and withdrawal details statement, is created.

[0059] Next, in step S160, the calculation unit 102b calculates a valuation amount for each transaction that takes into account the interest amount incurred from payment to receipt. Specifically, for each transaction, the calculation unit 102b calculates the payment amount (withdrawal amount), the deposit amount, and the equivalent amount of interest incurred from payment to receipt based on the data obtained from the deposit / withdrawal data table 1 or the statement data table 2, calculates the valuation amount of the transaction based on the calculated equivalent amount of interest, and generates the summary data table 3.

[0060] As an example, consider the case where the calculation unit 102b creates the summary table data table 3 for transaction number TB003001, as shown in Figure 5. The calculation unit 102b obtains the withdrawal amount data from the deposit / withdrawal data table 1 or the details data table 2 and transfers it to the "withdrawal amount" column of the summary table data table 3. As an example, from row 510 of the deposit / withdrawal data table 1 shown in Figure 3, we can see that the withdrawal amount for transaction number TB003001 is 100,000 yen, so the calculation unit 102b transfers the deposit / withdrawal amount value from row 510 of the deposit / withdrawal data table 1 to the withdrawal amount column of the summary table data table 3. As another example, from row 10 of the details table data table 2 shown in Figure 4, we can see that the withdrawal amount for transaction number TB003001 is 100,000 yen. Therefore, the calculation unit 102b may transfer the value of the deposit / withdrawal amount from row 10 of the details table data table 2 to the withdrawal amount column of the summary table data table 3.

[0061] Furthermore, the calculation unit 102b obtains the deposit amount data from the deposit / withdrawal data table 1 or the details data table 2 and transfers it to the "Deposit Amount" column of the summary data table 3. For example, from row 520 of the deposit / withdrawal data table 1 shown in Figure 2, it can be seen that the deposit amount for transaction number TB003001 is 120,000 yen, so the calculation unit 102b transfers the deposit / withdrawal amount value from row 520 of the deposit / withdrawal data table 1 to the withdrawal amount column of the summary data table 3. As another example, from row 20 of the details data table 2 shown in Figure 4, it can be seen that the deposit amount for transaction number TB003001 is 120,000 yen, so the calculation unit 102b transfers the deposit / withdrawal amount value from row 20 of the details data table 2 to the deposit amount column of the summary data table 3.

[0062] Furthermore, the calculation unit 102b collects interest rate data for the target transaction from the details data table 2 and calculates the total amount. For example, in the details data table 2 shown in Figure 4, the interest rate data for transaction number TB003001 is in rows 11, 12, 13, and 21. The calculation unit 102b extracts these rows from the details data table 2. Subsequently, the calculation unit 102b calculates the total amount of these rows. That is, the interest rate amounts listed in rows 11, 12, 13, and 21 of the details data table 2 are -4, -123, -123, and +5, respectively, and the calculation unit 102b sums these up to calculate the total interest amount as -245 and transfers it to the interest amount column of the summary data table 3.

[0063] Next, the calculation unit 102b calculates the valuation of the transaction by subtracting the withdrawal amount from the deposit amount and the interest accrued. That is, for transaction number TB003001 shown in Figure 5, the valuation is 120,000 - 100,000 - 245 = 19,755. In other words, the cost amount considering the interest paid is 100,000 + 245 = 100,245, and the valuation is 19,755, which is the value obtained by subtracting the cost amount of 100,245 from the deposit amount of 120,000. In this embodiment, if the period from payment to receipt is long, the cost amount increases due to the larger amount of interest accrued, and as a result, the valuation decreases. The data management device according to this embodiment can appropriately incorporate the amount equivalent to the interest incurred between payment and receipt into the valuation.

[0064] Next, using Figures 11 to 16, we will explain examples of reports output by the data management device 100 according to the embodiment. As mentioned earlier, the data management device 100 according to the embodiment outputs two types of tables with different functions: a deposit and withdrawal details table and a deposit and withdrawal summary table. The deposit and withdrawal details table, described in Figures 11 to 13, is a table that shows payment (withdrawal) data, deposit data, and interest equivalent amount in a list format, and is a table that shows when and how much payment, deposit, and interest occurred. In contrast, the deposit and withdrawal summary table, described in Figures 14 to 16, is a table that summarizes how much profit was made in each transaction, taking interest into account, and is a table that shows the profitability of the transaction when interest is taken into account.

[0065] First, let's explain how to display the deposit and withdrawal statement. Figure 11 is a flowchart showing the processing flow related to the display of the deposit and withdrawal statement.

[0066] The reception unit 102a waits to receive input from the user for instructions to create a deposit and withdrawal statement (step S200). When the user inputs an instruction to create a deposit and withdrawal statement (step S200 Yes), the process proceeds to step S210, and the display control unit 102c starts the process of creating the deposit and withdrawal statement.

[0067] Figure 12 shows a user interface 60 for the reception unit 102a to receive instructions from the user to create a deposit and withdrawal statement. When the user clicks the execute button 61, the reception unit 102a receives the instruction to create the deposit and withdrawal statement 62 shown in Figure 13. The reception unit 102a also accepts input of the transaction number 63a, which is the range of transaction numbers to be included in the creation of the deposit and withdrawal statement; the interest calculation date 63b, which is the range of dates and times for interest calculation; the department 63c, which is the department to which the deposit and withdrawal statement will be created; and the person in charge 63d. The transaction number 63a, interest calculation date 63b, department 63c, and person in charge 63d are optional items.

[0068] To illustrate the uses of each setting item, for example, by accepting the input of transaction number 63a from the user, it is possible to check the details of a specific transaction and the gross profit. Also, by accepting the input of interest calculation date 63b from the user, it is possible to check the interest incurred during a specific interest calculation period. Furthermore, by accepting the input of department 63c and person in charge 63d, it is possible to check the transaction amount by department and by person in charge.

[0069] In step S210, the display control unit 102c extracts data from the statement data table 2 that falls within the selected range of transaction number 63a, interest calculation date 63b, department 63c, and person in charge 63d, and for which payment has been completed. Based on the extracted data, it creates a deposit and withdrawal statement. In step S220, the display control unit 102c extracts data from the statement data table 2 that falls within the selected range of transaction number 63a, interest calculation date 63b, department 63c, and person in charge 63d, and for which payment has been completed. Based on the extracted data, it creates an input / output statement. In step S230, as shown in Figure 13, the display control unit 102c outputs the deposit and withdrawal statement 62, which is a table showing payment data, deposit data, and interest equivalent amount in list format, created in steps S210 and S220, to the output device 114, which acts as a display unit. Each line in the deposit and withdrawal statement 62 displays information such as the transaction number, interest calculation date, original slip number, deposit / withdrawal amount, interest amount, department, and person in charge, as well as whether each transaction is paid for or not.

[0070] In this way, the display control unit 102c can check the fund collection status for each sales representative, for example, by displaying the deposit and withdrawal statement. Furthermore, by displaying the deposit and withdrawal statement, the display control unit 102c can check deposit and withdrawal records for each transaction, for example.

[0071] Next, we will explain how to display the deposit and withdrawal summary report. Figure 14 is a flowchart illustrating the processing flow related to the display of the deposit and withdrawal summary report.

[0072] The reception unit 102a waits to receive input from the user for instructions to create a deposit and withdrawal summary table (step S300). When the user inputs an instruction to create a deposit and withdrawal summary table (step S300 Yes), the process proceeds to step S310, and the display control unit 102c starts the process of creating the deposit and withdrawal summary table.

[0073] Figure 15 shows a user interface 70 for the reception unit 102a to receive instructions from a user to create a deposit and withdrawal summary table. When the user clicks the execute button 71, the reception unit 102a receives the instruction to create the deposit and withdrawal summary table 72 shown in Figure 16. The reception unit 102a also accepts input for the aggregation period 73a, which is the range of dates and times for which the aggregation will be performed, the department 73b for which the deposit and withdrawal summary table will be created, and the person in charge 73c. ​​Only the aggregation period 73a is a required input item; the department 73b and person in charge 73c are optional items. Possible uses of the deposit and withdrawal summary include checking the valuation of transactions by department or by person in charge of department for a specific period, taking interest rates into consideration. When aggregating the deposit and withdrawal summary table, transactions for which no deposit has been made are excluded from the aggregation.

[0074] In step S310, the display control unit 102c refers to the details data table 2 and the summary data table 3, and extracts data from the summary data table 3 for transaction numbers where the aggregation period 73a, department 73b, and person in charge 73c match, and for which payment has been completed. Based on the extracted data, it creates the deposit and withdrawal summary table 72 shown in Figure 16. Data where the aggregation period 73a, department 73b, and person in charge 73c do not match, or data for transactions for which payment has not been completed, are not included in the summary. In step S320, as shown in Figure 16, the display control unit 102c outputs the deposit and withdrawal summary table 72, which is a table showing the valuation amount for each transaction and was created in step S310, to the output device 114, which acts as a display unit. Each row of the deposit and withdrawal summary table 72 shows information such as the accounting period, department, person in charge, withdrawal amount, deposit amount, interest accrued, and valuation amount.

[0075] In this way, the display control unit 102c displays the deposit and withdrawal summary table, allowing the user to check the valuation of transactions, taking interest rates into account.

[0076] The embodiments are not limited to those shown. As shown in Figures 17 and 18, the display control unit 102c may display, instead of the deposit and withdrawal details table 62 or the deposit and withdrawal summary table 72, an internal fund details table 80 which adds information on the internal fund balance to the deposit and withdrawal details table 62, or an internal fund balance table 90 which adds information on the internal fund balance to the deposit and withdrawal summary table 72. In this case, the data management device 100 stores information on the internal fund balance for each day and time in an internal fund balance table (not shown) in the storage unit 106, and the display control unit 102c retrieves information from the internal fund balance table as needed to create the internal fund details table 80 or the internal fund balance table 90.

[0077] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions within companies, thereby enabling contributions to SDGs Goals 8 and 9.

[0078] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0079] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0080] [5. Other Embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims.

[0081] 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 by known methods.

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

[0083] Furthermore, with respect to the data management device 100, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0084] For example, the processing functions of the data management device 100, particularly those performed in the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for the information processing device to execute the processing described in this embodiment, and is mechanically read by the data management device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) records a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0085] Furthermore, this computer program may be stored on an application program server connected to the data management device 100 via any network, and it is possible to download all or part of it as needed.

[0086] Furthermore, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical 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.

[0087] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

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

[0089] Furthermore, the data management device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the data management device 100 may be implemented by installing software (including programs or data, etc.) on the device that enables the processing described in this embodiment.

[0090] 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 and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

[0091] This invention is useful in various situations, such as business management in trading companies. [Explanation of Symbols]

[0092] 100 Data Management Devices 102 Control Unit 102a Reception Desk 102b Calculation Unit 102c Display Control Unit 104 Communication Interface Section 106 Storage section 1. Deposit and Withdrawal Data Table 2. Detail Table 3 Summary Table Data Table 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

1. A reception unit that accepts input of payment data related to transactions and deposit data related to said transactions, A calculation unit that calculates the amount equivalent to the interest incurred from the payment to the deposit and calculates the value of the transaction based on the amount equivalent to the interest, A data management device characterized by being equipped with the following features.

2. The calculation unit calculates the deposit and withdrawal amounts based on the payment data and the deposit data. The data management device according to claim 1, which calculates the valuation amount based on the deposit and withdrawal amounts and the interest equivalent amount.

3. The data management device according to claim 1, wherein the calculation unit calculates a provisional value of the interest amount related to the transaction on a predetermined date.

4. The data management device according to claim 1, further comprising a display control unit that displays a deposit and withdrawal statement in a list format showing the payment data, the deposit data, and the interest equivalent amount on a display unit.

5. The data management device according to claim 1, further comprising a display control unit that displays a deposit and withdrawal summary table showing the valuation amount for each transaction on the display unit.

6. The data management device according to claim 4 or 5, wherein the display control unit further displays the company's fund balance on the display unit.

7. The reception department accepts payment data related to the transaction and deposit data related to the said transaction in a reception step, The calculation unit calculates the amount equivalent to the interest incurred from the payment to the receipt, and calculates the value of the transaction based on the amount equivalent to the interest, and A data management method characterized by including the following.

8. Information processing equipment, A receiving means for receiving input of payment data related to a transaction and deposit data related to the said transaction, A calculation means that calculates the amount equivalent to the interest incurred from the payment to the deposit, and calculates the value of the transaction based on the amount equivalent to the interest. A data management program designed to function as such.

Images