Commercial transaction status management device, commercial transaction status management method, and commercial transaction status management program

Abstract

To provide a commercial transaction status management device, a commercial transaction status management method, and a commercial transaction status management program that enable confirmation of a commercial transaction status of a customer.SOLUTION: A comparison unit compares, when a transaction date when a commercial transaction is carried out with a customer is input, the transaction date with a last transaction date, which is a previous transaction date stored in a storage unit. An update unit updates, when the comparison unit obtains a comparison result in which the transaction date is a date after the last transaction date, the last transaction date in the storage unit to the transaction date. An output control unit controls an output of the updated last transaction date to an output apparatus. A user can check, on the basis of the last transaction date, a transaction status of a customer.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a commercial transaction status management device, a commercial transaction status management method, and a commercial transaction status management program. [Background technology]

[0002] The receivables and payables management device disclosed in Patent Document 1 (JP 2017-174389 A) displays the establishment data and department data included in the basic information corresponding to the customer data selected by the user in a changeable manner. When the user changes this basic information, it obtains receivables and payables management information including the changed establishment data of the receivables and payables management establishment and / or the changed department data of the receivables and payables management department, as well as the unchanged data of the basic information. It then controls the user to input transaction detail data including the amount, transaction date, and transaction method corresponding to the receivables and payables management information, and obtains and registers the transaction data including the receivables and payables management information and transaction detail data.

[0003] In this way, by setting the credit and debt management information on the system, even if the credit and debt management information is changed or added, it can be easily operated and managed. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2017-174389 Summary of the Invention [Problem to be solved by the invention]

[0005] Therefore, there is a need for the development of a device that can check the status of commercial transactions with business partners.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a commercial transaction status management device, a commercial transaction status management method, and a commercial transaction status management program that enable confirmation of the status of commercial transactions with trading partners. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the business transaction status management device of the present invention includes a comparison unit that, when a transaction date of a business transaction with a business partner is input, compares the input date with a last transaction date, which is the previous transaction date stored in a storage unit; an update unit that, when a comparison result indicating that the transaction date is a date after the last transaction date, updates the last transaction date stored in the storage unit to the transaction date; and an output control unit that controls output of the updated last transaction date to an output device. The storage unit stores, in addition to the final transaction date, a closing date which is the last day of each predetermined accounting period determined by the business partner, a collection month which is the number of months required from the closing date to payment determined by the business partner, and a collection date which is the date on which payment is made in the collection month, and the storage unit further comprises: a closing date generation unit which refers to the storage unit and generates, as the closing date corresponding to the commercial transaction on the transaction date, a closing date belonging to the collection month for collecting payment on the transaction date; a scheduled collection date generation unit which refers to the storage unit and generates a scheduled collection date by adding the collection month to the month to which the closing date belongs and the collection date; and a collection schedule generation unit which generates a collection schedule which includes the scheduled collection date, the final transaction date, the sales amount generated by the commercial transaction, and the amount received from the business partner in relation to the sales amount, and the output control unit controls output of the generated collection schedule to an output device.

[0008] In order to solve the above problems and achieve the object, the present invention provides The business transaction status management device The method for managing business transaction status includes a comparison step in which a comparison unit compares, when a transaction date of a business transaction with a business partner is input, the input date with a last transaction date, which is the previous transaction date stored in a storage unit; an update step in which, when a comparison result indicating that the transaction date is a date after the last transaction date is obtained from the comparison unit, an update step in which an update unit updates the last transaction date in the storage unit to the transaction date; and an output control step in which an output control unit controls output of the updated last transaction date to an output device. The storage unit stores, in addition to the final transaction date, a closing date which is the last day of each predetermined accounting period determined by the business partner, a collection month which is the number of months required from the closing date to payment determined by the business partner, and a collection date which is the date on which payment is made in the collection month, and the system further includes a closing date generation step in which a closing date generation unit refers to the storage unit and generates a closing date belonging to the collection month in which payment on the transaction date is collected as the closing date corresponding to the commercial transaction on the transaction date, a scheduled collection date generation step in which a planned collection date generation unit refers to the storage unit and generates a scheduled collection date which is a date by adding the collection month to the month to which the closing date belongs and the collection date, and a collection schedule generation step in which a collection schedule generation unit generates a collection schedule which includes the scheduled collection date, the final transaction date, the sales amount generated by the commercial transaction, and the amount received from the business partner in relation to the sales amount, and the output control step controls output of the generated collection schedule to an output device.

[0009] In order to solve the above-mentioned problems and achieve the object, a commercial transaction status management program according to the present invention includes a comparison unit that, when a transaction date on which a commercial transaction was conducted with a trading partner is input, compares the transaction date with a last transaction date, which is the previous transaction date stored in a storage unit; an update unit that, when a comparison result indicating that the transaction date is a date after the last transaction date is obtained from the comparison unit, updates the last transaction date stored in the storage unit to the transaction date; and an output control unit that controls output of the updated last transaction date to an output device. The memory unit stores, in addition to the final transaction date, a closing date which is the last day of each predetermined accounting period determined by the business partner, a collection month which is the number of months required from the closing date to payment determined by the business partner, and a collection date which is the date on which payment is made in the collection month, and the computer further functions as a closing date generation unit which refers to the memory unit and generates a closing date belonging to the collection month for collecting payment on the transaction date as a closing date corresponding to the commercial transaction on the transaction date, a scheduled collection date generation unit which refers to the memory unit and adds the collection month to the month to which the closing date belongs and the collection date to generate a scheduled collection date which is a date, and a collection schedule generation unit which generates a collection schedule which includes the scheduled collection date, the final transaction date, the sales amount generated by the commercial transaction, and the amount received from the business partner relative to the sales amount, and the output control unit controls output of the generated collection schedule to an output device. [Effects of the Invention]

[0010] The present invention makes it possible to check the status of commercial transactions with business partners. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing a hardware configuration of a business transaction status management device according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the customer master. [Figure 3] FIG. 3 is a diagram illustrating an example of the billing destination master. [Figure 4] FIG. 4 is a diagram for explaining an outline of the operation of the business transaction status management device according to the embodiment. [Figure 5] FIG. 5 is a diagram showing an example of the sales input screen. [Figure 6] FIG. 6 is a diagram illustrating an example of sales data. [Figure 7] FIG. 7 is a diagram for explaining the operation of updating the last transaction date of the billing destination master. [Figure 8] FIG. 8 is a diagram for explaining the operation of specifying the closing sales date. [Figure 9] FIG. 9 is a diagram for explaining the operation of resetting the scheduled collection date to a date that exists in the scheduled collection month when the identified scheduled collection date does not exist in the scheduled collection month. [Figure 10] FIG. 10 is a diagram showing an example of a collection schedule. [Figure 11] FIG. 11 is a diagram showing an example of sales data and deposit data. DETAILED DESCRIPTION OF THE INVENTION

[0012] A commercial transaction status management device according to an embodiment of the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the following embodiment.

[0013] (Hardware configuration) As shown in FIG. 1, the transaction status management device 1 of 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 corresponds to a display unit such as a monitor device (including a home television), a printing device, or a speaker device. The input device 6 may be a keyboard device, a mouse device, a microphone device, or a monitor device that cooperates with a mouse device to achieve a pointing device function. The communication interface unit 4 is connected to a network, for example, a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0014] The storage unit 2 may be, for example, a read-only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD). A transaction status management program for managing transaction status is stored in the storage unit 2. The storage unit 2 also stores a customer master 11, a billing destination master 12, collection schedule data, sales data, and deposit data.

[0015] As shown in Figure 2, the customer master 11 includes a customer code, customer name, and billing code. This customer master 11 associates customers with billing destinations. In the example of Figure 2, the customer code for customer A is "T001," and billing for this customer is performed using the billing destination code "S001."

[0016] The billing destination master 12 is composed of the billing destination code, billing destination name, last transaction date, closing date, collection month, and collection date, as shown in Figure 3. The "last transaction date" is the date on which no commercial transactions were conducted with the customer after the date on which no commercial transactions were conducted with the customer.

[0017] The "closing date" is the last day of each specified accounting period for that customer. The "collection month" is the number of months required from the "closing date" to payment. In other words, the "collection month" is the month to which a date after the "closing date" belongs, and is the number of months until the month in which the amount invoiced to that customer can be collected. The "collection date" is the date on which payment is made in the "collection month."

[0018] The example in Figure 3 shows that the final transaction for the billing code "S001" and billing name "Billing A" will be "April 20, 2022," as indicated by the "Last Transaction Date." The example in Figure 3 also shows that the closing date for "Billing A" is the "31st (or last day)" of each month, and that the invoice amount can be collected "1" month after this closing date, with the collection date being the "31st (or last day)" of the month corresponding to the collection month.

[0019] (Functional configuration of the business transaction status management device) Next, the control unit 3 executes the transaction status management program stored in the memory unit 2, and thereby functions as a comparison unit 21, an update unit 22, a display control unit 23 (an example of an output control unit), a closing date generation unit 24, a scheduled collection date generation unit 25, and a collection schedule generation unit 26, as shown in FIG. 1.

[0020] The comparison unit 21 compares the transaction date of a business transaction with a business partner (customer, billing party) when it is entered, for example, by inputting an order or sales, with the last transaction date, which is the previous transaction date stored in the memory unit (billing party master 12).

[0021] When the comparison unit obtains a comparison result in which the transaction date is a date after the last transaction date, the update unit 22 updates the last transaction date in the storage unit (billing destination master 12) to the input transaction date. The output control unit (for example, the display control unit 23) controls the output of the updated last transaction date to an output device (such as a monitor, storage device, speaker, or printer).

[0022] In addition to the last transaction date, the storage unit (billing destination master 12) also stores the closing date, which is the last day of each predetermined accounting period determined by the business partner, the collection month, which is the number of months required from the closing date determined by the business partner to payment, and the collection date, which is the date on which payment is made in the collection month.The closing date generation unit 24 references the storage unit (billing destination master 12) and generates the closing date belonging to the collection month for collecting payment on the transaction date as the closing date corresponding to the commercial transaction on the transaction date.

[0023] The scheduled collection date generation unit 25 references the storage unit (billing destination master 12), adds the collection month to the month to which the closing date belongs, and adds the collection date to generate the scheduled collection date, which is a date. The collection schedule generation unit 26 generates a collection schedule that includes the scheduled collection date, the last transaction date, the sales amount generated by the commercial transaction, and the amount received from the business partner in relation to the sales amount. The output control unit (for example, the display control unit 23) controls the output of the generated collection schedule to an output device (such as a monitor, storage device, speaker, or printer).

[0024] Furthermore, if the generated scheduled collection date is a date that does not exist, the scheduled collection date generating unit 25 sets a date that exists in the month to which the generated scheduled collection date belongs as the scheduled collection date.

[0025] (Outline of operation of the commercial transaction status management device) Next, when a transaction input such as an order input or a sales input is received, the transaction status management device 1 according to the embodiment updates the most recent transaction date, which is the most recent date from among the past dates on which a transaction with a business partner (customer, billing partner) was performed and is stored in the billing partner master 12, to the input transaction date, as shown in Figure 4. This most recent transaction date is a date that indicates the status of the transaction with the business partner. In other words, if there is a period of time, such as two months or more, between the most recent transaction date and the current date, it is difficult to say that the transaction status is smooth, and measures such as a credit re-investigation can be taken.

[0026] Furthermore, the business transaction status management device 1 of the embodiment references the customer master 11 and the billing destination master 12 based on the input sales data, and generates a collection schedule including a receivables collection schedule for the customer. The "scheduled collection date" calculated based on the billing destination master 12 is input to this collection schedule. This makes it possible to check the collection schedule for uncollected receivables by referring to the collection schedule. (Last trading day update operation) First, we will explain the operation of updating the last transaction date of the billing destination master 12. This update operation is performed by the control unit 3 of the transaction status management device 1 functioning as the following units based on the transaction status management program stored in the storage unit 2.

[0027] First, when an operator receives an order for a commercial transaction, the operator operates the input device 6 to specify the display of an order entry screen in order to enter the order. Alternatively, when a commercial transaction is carried out, the operator operates the input device 6 to specify the display of a sales entry screen in order to enter sales. The following explanation will be given taking sales entry as an example.

[0028] When the operator specifies that the sales input screen be displayed, the display control unit 23 displays the sales input screen shown in Fig. 5 via the output device 7. As shown in Fig. 5, the sales input screen includes a display field for the order number, an input field for the business establishment code, an input field for the sales date, an input field for the customer code, an input field for the person in charge, an input field for the delivery destination, and an input field for the supplier.

[0029] The sales input screen also has input fields for the purchase date, the billing code, the expected collection date, the sales rate, the purchase rate, and the purchase rate.The sales input screen also has input fields for details such as the order type, product name, quantity, and unit price of the sold product.

[0030] Based on the input contents on the sales input screen, the data generation unit 27 generates sales data including the sales number, line number, sales category, business establishment code, sales date, person in charge code, customer code, billing destination code, delivery destination code, supplier code, product name, quantity (sales quantity), unit sales price, and amount (sales amount), as shown in Figure 6, and stores it in the memory unit 2.

[0031] The example of sales data shown in Figure 6 is an example of sales data for "direct sales," in which goods are delivered directly from a supplier's warehouse to a customer. Therefore, the sales category is "direct sales." The example in Figure 6 shows an example where the sales date is "July 24, 2022," and two cases of "ammonia" with product code "SH01" and ten cases of "nitric acid" with product code "SH02" were sold. The example in Figure 6 also shows an example where the sales price for two cases of "ammonia" was "1,300 yen," resulting in a sales amount of "2,600 yen." The sales price for ten cases of "nitric acid" was "950 yen," resulting in a sales amount of "9,500 yen."

[0032] On the other hand, when a customer code, a sales date, etc. are entered via the sales input screen, the comparison unit 21 refers to the customer master 11 shown in Fig. 2 based on the entered customer code and detects the billing code associated with the entered customer code. In the example of Fig. 5, since the customer code "T001" was entered via the sales input screen, the comparison unit 21 detects the billing code "S001" associated with the customer code "T001" from the customer master 11.

[0033] Furthermore, the comparison unit 21 references the billing destination master 12 shown in FIG. 3 based on the billing destination code "S001" detected from the customer master 11, and detects the last transaction date for "billing destination A" with the billing destination code "S001". The comparison unit 21 then compares the detected last transaction date with the sales date (an example of a transaction date) entered via the sales input screen. In the examples of FIGS. 3 and 5, the sales date for "billing destination A" entered via the sales input screen is "July 24, 2022", while the last transaction date for "billing destination A" stored in the billing destination master 12 is "April 20, 2022". Therefore, the comparison unit 21 outputs a comparison result in which the sales date is a date after the last transaction date.

[0034] When the comparison unit 21 returns a comparison result indicating that the sales date is a date after the last transaction date, the update unit 22 updates the last transaction date for that invoice destination in the invoice destination master data 12 to the date of the sales date. In the example described above, the sales date for "invoice destination A" is "July 24, 2022," and the last transaction date in the invoice destination master data 12 is "April 20, 2022." Therefore, the comparison unit 21 returns a comparison result indicating that the sales date is a date after the last transaction date, and the update unit 22 updates the last transaction date of "April 20, 2022" in the invoice destination master data 12 to the sales date of "July 24, 2022," as shown in FIG. 7. The display control unit 23 displays the invoice destination master data 12, including the last transaction date, via the output device 7 at a predetermined timing, such as a timing specified by the operator.

[0035] This last transaction date is the date that indicates the status of business transactions with the billing party. In other words, if there is a period of time, such as two months or more, in which no business transactions have been conducted between the last transaction date and the current date, it is difficult to say that business transactions are going smoothly, and therefore, a department that conducts credit investigations, such as the risk assessment department, can take measures such as conducting a credit re-investigation.

[0036] (Collection schedule generation operation) Next, by creating a collection schedule that includes the planned collection date, collection rate, etc. along with the final transaction date, it becomes possible to check collection work that cannot be covered by credit checks alone, even for regular business partners, from a perspective separate from credit management, such as when the collection rate is low despite the transaction date being recent.

[0037] That is, when the sales are entered as described above (or when an order is entered, etc.) (preferably after the last transaction date has been updated), the closing date generation unit 24 refers to the sales date entered on the sales input screen (see Figures 5 and 6) and the "closing date," "collection month," and "collection date" in the billing master 12 shown in Figure 3, and generates a closing date corresponding to the sales date, as shown in Figure 8.

[0038] That is, if the sales date is "September 25th" as in the example of Figure 8, the closing date generation unit 24 obtains the closing date of "the 31st" as the closing date that is the closest date after the 25th. However, since this closing date of "the 31st" belongs to the month before the "collection month," the closing date generation unit 24 detects the closing dates of "the 10th" and "the 20th" of the following month as closing dates after the 31st, and generates "October 20th (2009)," which is the closing date closest to the "collection date," "the 31st (last day)," as the closing date.

[0039] Next, the scheduled collection date generation unit 25 refers to the billing destination master 12, adds the collection month to the month to which the closing date generated as described above belongs, and adds the collection date to this added date to generate the scheduled collection date.

[0040] That is, in the above example, for a sales date of "September 25th," the closing date generated by the closing date generation unit 24 is "October 20th, 2009." As stored in the billing destination master 12 shown in FIG. 3, the collection month is "1" and the collection date is "31st." Therefore, as shown in FIG. 9, the scheduled collection date generation unit 25 adds the collection month of "January" to October 2009 to obtain "November 2009," and then adds the collection date of "31st" to this "November 2009" to obtain "November 31st, 2009."

[0041] Here, the last day of November is not the "31st", but the "30th". In this way, if the generated scheduled collection date is a date that does not exist, "November 30th, 2009", which is a date that exists in the month to which the generated scheduled collection date belongs, is generated as the scheduled collection date. This allows the scheduled collection date to be corrected to the "28th (or 29th: leap year)" even in months that do not have a "31st" as their last day, such as February.

[0042] Next, the collection schedule generation unit 26 refers to the sales data shown in Figure 11(a) and the deposit data shown in Figure 11(b) and calculates "deposit amount / sales amount" to calculate the collection rate for that customer and sales. The deposit data is data entered by the operator using a deposit input screen (not shown) and stored in the memory unit 2 by the data generation unit 27. The deposit data and sales data may be obtained from the accounting server device via a network or the like, or may be obtained and used from data stored in external memory.

[0043] For example, the collection schedule generating unit 26 determines that the sales amount to the billing destination with the billing destination code "S001" in the first record in Fig. 11(a) is "2800 yen," while the amount received from the billing destination with the billing destination code "S001" is "2800 yen" as shown in the first record in Fig. 11(b). In this case, the collection rate is "2800 yen / 2800 yen = 100%."

[0044] However, as shown in Figure 11(a), there are sales amounts of "6,750 yen" and "12,100 yen" other than "2,800 yen" for the billing recipient with billing code "S001," but the deposits for these sales have not been received, as shown in Figure 11(b). In this case, the recovery rates are "0 yen (= amount received) / 6,750 yen" and "0 yen (= amount received) / 12,100 yen," and the recovery rates for each are "0%."

[0045] In other words, the billing recipient with the billing code "S001" deposited "2,800 yen" for sales of "2,800 yen," but deposited "0 yen" for sales of "6,750 yen" and "12,100 yen."

[0046] On the other hand, the record on the fourth line in Figure 11(a) shows a deposit for sales of "6,800 yen" to a billing recipient with billing code "S002", but as shown in Figure 11(b), the deposit is in a state of "0 yen". Therefore, it becomes "0 yen (= deposit amount) / 6,800 yen", and in this case too the recovery rate is "0%".

[0047] Also, the records on lines 5 to 8 in Figure 11(a) show deposits for sales of "2900 yen," "2900 yen," "7750 yen," and "5600 yen" to the billing recipient with billing code "S003," but as shown in Figure 11(b), deposits have been made in the same amount as the sales amount except for the deposit for the "5600 yen" sale. Therefore, the recovery rate for the "5600 yen" sale is "0%," and the recovery rate for other sales with billing code "S003" is "100%."

[0048] When each collection rate is calculated in this manner, the collection schedule generation unit 26 generates a collection schedule including the serial number (No.), business code, billing code, sales amount, scheduled collection date, final transaction date, deposit amount, and collection rate, as exemplified in Fig. 10, based on the sales data shown in Fig. 11(a), the deposit data shown in Fig. 11(b), the scheduled collection date generated by the scheduled collection date generation unit 25, and the calculated collection rate, and stores this collection schedule data in the storage unit 2. The display control unit 23 displays this collection schedule via the output device 7 at a predetermined timing, such as a timing specified by the operator.

[0049] For example, in the case of a billing recipient with billing code "S001" in Figure 10, the last transaction date for the transaction of "12,100 yen" in the record on the third line is "July 24, 2022," and the scheduled collection date is "August 31, 2022." Even though this transaction is a recent transaction, the sales amount of "6,700 yen" in the record on the second line has not yet been collected. The collection schedule can be used to examine whether there are any problems with this type of transaction situation.

[0050] Furthermore, in the case of the billing recipient with billing code "S002" in Figure 10, the final transaction date for the "6,800 yen" transaction in the record on line 4 is "April 24, 2022," and the scheduled collection date is "April 30, 2023." Even though the final transaction date for this transaction is approximately one year before the scheduled collection date, the sales proceeds remain uncollected. It is possible to determine whether there are any problems with this type of transaction status, and whether the scheduled collection date is correct, based on the collection schedule.

[0051] The credit check is performed by the comparison unit 21 by calculating the amount calculated using the formula "uncollected receivables amount + backorder amount - backorder amount - unpaid debt balance" and determining whether this calculated amount exceeds the credit amount set by the operator for each customer in a credit master or the like (not shown).

[0052] Furthermore, such a credit check is performed, as an example, when an operator such as a field sales representative records the next commercial transaction by inputting an order or sales amount.

[0053] (Effects of the embodiment) As is clear from the above explanation, the commercial transaction status management device 1 of the embodiment stores the "last transaction date" in the billing destination master 12, and updates the "last transaction date" for the billing destination of the transaction when entering a transaction, such as when entering an order or a sale. This makes it possible to check billing destinations with uncollected receivables by focusing on the last transaction date. It also prevents the inconvenience of overlooking the collection status for each commercial transaction.

[0054] Specifically, since the "last transaction date" indicates the status of commercial transactions with the billing party, if there is a period of time between the last transaction date and the current date in which no commercial transactions have been conducted, such as two months or more, it is difficult to say that the commercial transaction status is smooth. For this reason, a department that conducts credit investigations, such as the risk assessment department, can take measures such as conducting a credit re-investigation.

[0055] Furthermore, the commercial transaction status management device 1 of the embodiment creates a collection schedule that includes the last transaction date, the scheduled collection date, the collection rate, etc., making it possible to check the commercial transaction status with a business partner with whom you regularly conduct commercial transactions from a perspective different from that of prior credit management. This makes it possible to check the collection status of receivables that cannot be covered by credit checks alone, such as when the collection rate is low despite the sales date being recent. Furthermore, a department that conducts credit investigations, such as a risk assessment department, can re-examine the credit and review the commercial transaction, etc.

[0056] For example, chemical trading companies often use "direct delivery" transactions, where products are delivered directly from the supplier's warehouse to the customer. Due to the large volume of transactions and the large number of stakeholders, it is difficult for the accounting department to handle receivables reconciliation work alone. It is also difficult for the accounting department to determine whether collection is delayed based solely on the scheduled collection date of the sales account that is the source of the receivable.

[0057] However, the business transaction status management device 1 of the embodiment can easily identify the billing destination, etc. based on the "last transaction date," so it is possible for the accounting department to perform the reconciliation work on its own. Also, by creating a collection schedule, it is possible for the accounting department to determine whether to delay collection based only on the scheduled collection date of the sales that are the source of the receivable.

[0058] Furthermore, in companies where the sales department is responsible for debt collection, the debt collection rate tends to be low. However, the commercial transaction status management device 1 of the embodiment can easily determine whether or not a collection delay will occur by referring to the scheduled collection date in the collection schedule, even in companies where the sales department is responsible for debt collection, thereby improving the debt collection rate.

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

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

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

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

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

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

[0065] Furthermore, with regard to the business transaction status management 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.

[0066] For example, all or any part of the processing functions of the transaction status management device 1, particularly the control unit 3 and the processing functions performed by the control unit 3, may be implemented by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the transaction status management device 1 as needed. That is, a storage unit such as a ROM or HDD stores a computer program for working 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 form the control unit 3.

[0067] In addition, the commercial transaction status management program of this commercial transaction status management device 1 may be stored in another server device connected to the commercial transaction status management device 1 via any network, and all or part of it may be downloaded as needed.

[0068] The transaction status management 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), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray Disc (Blu-ray Disc).

[0069] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in source code, binary code, or other format. Note that a "program" is not necessarily limited to a single program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by working together with other programs, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in the commercial transaction status management device 1 described in the embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

[0071] The transaction status management device 1 may be configured as an information processing device such as a known personal computer or 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.

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

[0073] The present invention can be applied to managing the trading status of various types of businesses, including, for example, managing the trading status of chemical trading companies that often conduct direct transactions. [Explanation of symbols]

[0074] 1. Commercial transaction status management device 2 Storage section 3. Control Unit 4. Communication interface section 5 Input / output interface section 6 Input Devices 7 Output Devices 11 Customer Master 12 Billing Master 21 Comparison section 22 Update section 23 Display control unit 24 Closing Date Generation Unit 25 Collection date generation section 26 Collection schedule generation unit

Claims

1. a comparison unit that compares, when a transaction date with a business partner is input, the input date with the last transaction date, which is the previous transaction date stored in the storage unit; an update unit that updates the last trading date in the storage unit to the trading date when the comparison unit obtains a comparison result indicating that the trading date is a date after the last trading date; an output control unit that controls output of the updated last trading date to an output device; The storage unit stores, in addition to the final transaction date, a closing date which is the last day of each predetermined accounting period determined by the business partner, a collection month which is the number of months required from the closing date to payment determined by the business partner, and a collection date which is the date on which payment is made in the collection month, a closing date generating unit that references the storage unit and generates the closing date belonging to the collection month in which the payment on the transaction date is collected as the closing date corresponding to the commercial transaction on the transaction date; a scheduled collection date generating unit that references the storage unit, adds the collection month to the month to which the closing date belongs, and adds the collection date to generate a scheduled collection date, which is a date; a collection schedule generating unit that generates a collection schedule including the scheduled collection date, the final transaction date, the sales amount generated by the commercial transaction, and the amount of receipts from the business partner relative to the sales amount, the output control unit controls output of the generated collection schedule to the output device; A business transaction status management device comprising:

2. When the generated scheduled collection date is a date that does not exist, the scheduled collection date generation unit sets a date that exists in a month to which the generated scheduled collection date belongs as the scheduled collection date; 2. The business transaction status management device according to claim 1, wherein:

3. a comparison step in which the comparison unit compares, when the transaction date of a business transaction with a trading partner is input, the input date with the last transaction date, which is the previous transaction date stored in the storage unit; an updating step in which, when a comparison result indicating that the trading date is a date after the last trading date is obtained from the comparison unit, the updating unit updates the last trading date in the storage unit to the trading date; an output control step in which an output control unit controls an output of the updated last trading date to an output device; The storage unit stores, in addition to the final transaction date, a closing date which is the last day of each predetermined accounting period determined by the business partner, a collection month which is the number of months required from the closing date to payment determined by the business partner, and a collection date which is the date on which payment is made in the collection month, a closing date generation step in which a closing date generation unit references the storage unit and generates the closing date belonging to the collection month in which the payment for the transaction date is collected as the closing date corresponding to the commercial transaction for the transaction date; a scheduled collection date generation step in which a scheduled collection date generation unit references the storage unit, adds the collection month to the month to which the closing date belongs, and adds the collection date to generate a scheduled collection date, which is a date; a collection schedule generating step in which a collection schedule generating unit generates a collection schedule including the scheduled collection date, the final transaction date, the sales amount generated by the commercial transaction, and the amount of receipts from the business partner relative to the sales amount, In the output control step, the generated collection schedule is output to the output device. A commercial transaction status management method performed by a commercial transaction status management device.

4. Computer, a comparison unit that compares, when a transaction date with a business partner is input, the input date with the last transaction date, which is the previous transaction date stored in the storage unit; an update unit that updates the last trading date in the storage unit to the trading date when the comparison unit obtains a comparison result indicating that the trading date is a date after the last trading date; functioning as an output control unit that controls output of the updated last trading date to an output device; The storage unit stores, in addition to the final transaction date, a closing date which is the last day of each predetermined accounting period determined by the business partner, a collection month which is the number of months required from the closing date to payment determined by the business partner, and a collection date which is the date on which payment is made in the collection month, a closing date generating unit that references the storage unit and generates the closing date belonging to the collection month in which the payment on the transaction date is collected as the closing date corresponding to the commercial transaction on the transaction date; a scheduled collection date generating unit that references the storage unit, adds the collection month to the month to which the closing date belongs, and adds the collection date to generate a scheduled collection date, which is a date; causing the computer to further function as a collection schedule generating unit that generates a collection schedule including the scheduled collection date, the final transaction date, the sales amount generated by the commercial transaction, and the amount of receipts from the business partner relative to the sales amount; the output control unit controls output of the generated collection schedule to the output device; A business transaction status management program characterized by:

Images