Transaction management device, transaction management method, and transaction management program

The transaction management device addresses the challenge of inaccurate profit determination by comparing new and standard transaction data to provide cash flow insights, enhancing sales personnel's understanding and decision-making.

JP7584374B2Active Publication Date: 2024-11-15OBIC CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2021124244
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-07-29
Publication Date
2024-11-15
Estimated Expiration
2041-07-29

AI Technical Summary

Technical Problem

In trading companies and wholesale businesses, the determination of gross profit is inaccurate until the sales recording stage, making it difficult for sales personnel to grasp cash flow at the time of placing orders, leading to a lack of understanding of profit margins during transactions.

Method used

A transaction management device that compares new transaction data with standard transaction data to generate difference information, including payment site, net gross profit, and interest rate differences, and outputs error information if cash flow deteriorates, allowing users to understand cash flow dynamics during new transactions.

Benefits of technology

Enables sales personnel to easily obtain and consider cash flow information at the time of new transactions, facilitating informed decision-making to improve profit margins.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584374000001
    Figure 0007584374000001
  • Figure 0007584374000002
    Figure 0007584374000002
  • Figure 0007584374000003
    Figure 0007584374000003
Patent Text Reader

Abstract

To provide a transaction management apparatus which allows a user to acquire cashflow information at the time of a new transaction without time and effort, a transaction management method, and a transaction management program.SOLUTION: A transaction management apparatus is an information processing apparatus for managing transactions for ordering a commodity and delivering the ordered commodity. A control unit of the transaction management apparatus compares new transaction data input for a commodity with reference transaction data which is set in advance for the same commodity, to generate difference information on a difference on magnitude relationship or a difference between the reference transaction data and the new transaction data at the time of input of the new transaction data.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] Patent Document 1 discloses a system that manages the cost amount required for a product in a business where products are produced after receiving an order, and that displays warning information to alert the user if the managed cost amount exceeds a set planned cost amount (see, for example, claim 38). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2003 / 081492 Summary of the Invention [Problem to be solved by the invention]

[0004] Meanwhile, in trading companies, wholesale businesses, etc., there is a transaction form in which ordered goods are ordered and then delivered. Here, delivery is performed by purchasing and delivering, or by directly shipping the ordered goods. In such a transaction form, usually a person in charge (e.g. a sales person) determines the order amount by taking into account the order amount of the goods ordered from the first business partner and various expenses, and places an order with the second business partner. By conducting such transactions, trading companies, wholesale businesses, etc. can earn gross profits.

[0005] However, the gross profit cannot usually be accurately determined until the stage of recording sales, which is when the ordered goods are delivered to the first business partner. Therefore, salespeople and other personnel cannot know the gross profit at the stage of receiving the order and placing the order. In addition, since the gross profit is generally determined by someone other than the salespeople, such as an accounting person, the salespeople often do not try to understand the gross profit that is recognized after the sales are recorded.

[0006] Therefore, even in transactions where ordered goods are ordered and delivered, it is required to be able to grasp gross profit and other cash flows (hereinafter also written as "C / F") at the time of new transactions. If sales representatives are able to grasp cash flows at the time of new transactions, it is expected that they will be able to utilize this information in more sound transactions.

[0007] The present invention has been made in consideration of the above-mentioned problems (requirements), and aims to provide a transaction management device, a transaction management method, and a transaction management program that allow users to easily obtain information regarding cash flow when making a new transaction. [Means for solving the problem]

[0008] In order to solve the above-mentioned problems and achieve the objective, the transaction management device of the present invention is a transaction management device equipped with a control unit for managing transactions of ordering and delivering ordered goods, and is characterized in that the control unit has a difference information generation means for comparing new transaction data input for a certain product with reference transaction data that serves as a predetermined standard for the same product as the certain product, and generating difference information regarding the difference or magnitude relationship of the new transaction data relative to the reference transaction data at the time the new transaction data is input.

[0009] In addition, the transaction management device of the present invention is characterized in that the difference information includes information regarding the difference or magnitude relationship of the payment date, which indicates the period obtained by subtracting the scheduled purchase date of the ordered goods or the sales recording date of the transaction of the goods from the scheduled payment date to the supplier for the ordered goods.

[0010] In addition, the transaction management device according to the present invention is characterized in that the difference information includes information regarding the difference or magnitude relationship of net gross profit excluding various expenses.

[0011] In addition, the transaction management device according to the present invention is characterized in that the difference information includes information regarding the difference or magnitude relationship of interest rates per transaction.

[0012] In addition, the transaction management device of the present invention is characterized in that the control unit is equipped with an error information output means for outputting error information when the difference information is relative deterioration information indicating a relative deterioration of cash flow compared to the reference transaction data.

[0013] Furthermore, in the transaction management device according to the present invention, the error information output means outputs error information including information regarding other supplier when the difference information is the relative deterioration information.

[0014] In addition, the transaction management device according to the present invention is characterized in that the reference transaction data is the most recent transaction data among the readable transaction data.

[0015] In addition, the transaction management device according to the present invention is characterized in that the reference transaction data is transaction data relating to an average transaction calculated based on readable transaction data.

[0016] In addition, the transaction management device according to the present invention is characterized in that the reference transaction data is transaction data set as a default.

[0017] In addition, the transaction management method of the present invention is a transaction management method for managing transactions of ordering and delivering ordered goods, which is executed in a transaction management device equipped with a control unit, and is characterized in that it includes a difference information generation step executed in the control unit, which compares new transaction data input for a certain product with reference transaction data that serves as a predetermined standard for the same product as the certain product, and generates difference information regarding the difference or magnitude relationship of the new transaction data relative to the reference transaction data at the time the new transaction data is input.

[0018] In addition, the transaction management program of the present invention is a transaction management program executed in a transaction management device equipped with a control unit, for managing transactions of ordering and delivering received goods, and is characterized in that it includes a difference information generation step for comparing new transaction data input for a certain product with reference transaction data that serves as a predetermined standard for the same product as the certain product, to be executed in the control unit, and generating difference information regarding the difference or magnitude relationship of the new transaction data relative to the reference transaction data at the time the new transaction data is input. Effect of the Invention

[0019] According to the present invention, an effect is achieved in that a user can easily obtain information regarding cash flow when making a new transaction. [Brief description of the drawings]

[0020] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a transaction management system including a transaction management device according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a flowchart showing the processing steps of a transaction management method executed by transaction management device 100 in transaction management system 1000 of FIG. [Diagram 3] FIG. 3 is a diagram showing an example of the configuration of the check category master registered in step S201 of FIG. [Figure 4] FIG. 4 is a diagram showing a first example of a pair of order data and placement order data received in steps S203 to S204 in FIG. 2, where FIG. 4(a) shows an example of order data and FIG. 4(b) shows an example of placement order data. [Diagram 5] 5A and 5B are diagrams showing examples of transaction data tables referenced when reading out reference transaction data in step S205 of FIG. 2, where FIG. 5(a) shows an order data table and FIG. 5(b) shows an order data table. [Figure 6]Figure 6 is a diagram showing a schematic example of reference transaction data extracted as a result of step S205 in Figure 2, where Figure 6(a) shows order data included in the reference transaction data, and Figure 6(b) shows order data included in the reference transaction data. [Figure 7] FIG. 7 is a diagram useful in explaining an example of calculation logic for the interest rate and net gross profit used to obtain the difference information in step S206 of FIG. [Figure 8] FIG. 8 is a diagram used to explain the results when the calculation logic of FIG. 7 is applied to the reference transaction data shown in FIG. [Figure 9] FIG. 9 is a diagram used to explain the results when the calculation logic of FIG. 7 is applied to the new transaction data shown in FIG. [Figure 10] FIG. 10 is a diagram showing a schematic diagram of a second example of a pair of order data and placement order data received in steps S203 to S204 in FIG. 2, where FIG. 10(a) shows an example of order data and FIG. 10(b) shows an example of placement order data. [Figure 11] FIG. 11 is a diagram used to explain the results of calculating interest rates and net gross profits for the new transaction data shown in FIG. [Figure 12] Figure 12 is a diagram showing a schematic diagram of a third example of a pair of order data and purchase order data accepted in steps S203 to S204 in Figure 2, where Figure 12(a) shows an example of order data and Figure 12(b) shows an example of purchase order data. [Figure 13] FIG. 13 is a diagram used to explain the results of calculating interest rates and net gross profits for the new transaction data shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0021] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to the embodiment.

[0022] [1. Configuration] An example of the configuration of a transaction management system including a transaction management device according to the present embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of a transaction management system including a transaction management device according to the embodiment of the present invention.

[0023] The transaction management system 1000 shown in FIG. 1 includes a transaction management device 100 as an information processing device, a server 200, and a network 300 that communicatively connects transaction management device 100 and server 200.

[0024] The transaction management device 100 is an information processing device for managing transactions of ordering and delivering received goods, and is configured, for example, by a commercially available desktop personal computer. For example, one transaction management device 100 is installed in a department that manages transactions (for example, a sales department, an order receiving department, or an ordering department). Note that the transaction management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer. Furthermore, a plurality of transaction management devices 100 may be installed in the transaction management system 1000, and the plurality of transaction management devices 100 may function as a single transaction management device 100 by synchronizing them with each other.

[0025] Transaction management device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. Each unit included in transaction management device 100 is connected to each other so as to be able to communicate with each other via an arbitrary communication path.

[0026] The communication interface unit 104 communicatively connects the transaction 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 a function of communicating data with other devices via a communication line. Here, the network 300 has a function of connecting the transaction management device 100 and the server 200 to be able to communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Therefore, the communication interface unit 104 is configured to be able to accept information, etc. from other information processing devices (e.g., a trading partner's information processing device) via the network 300 or via the network 300 and the server 200, and is configured to be able to output predetermined information to a predetermined information processing device (e.g., a trading partner's information processing device).

[0027] The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs (including the program of the present invention) for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes. 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 as the storage unit 106. In addition, the storage unit 106 stores various data used to implement the program of the present invention in a writable / readable manner.

[0028] An input device 112 and an output device 114 are connected to the input / output interface unit 108. In addition to a monitor (including a home television), a speaker and a printer can be used as the output device 114. In addition to a keyboard, a mouse and a microphone, the input device 112 can also be a monitor that cooperates with the mouse to realize a pointing device function.

[0029] The control unit 102 is a CPU or the like that performs overall control of the transaction management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs.

[0030] Further, the configuration of the storage unit 106 and the control unit 102 will be described in detail with reference to FIG.

[0031] 1, the storage unit 106 includes a check category master 106a, a transaction data storage area 106b, a difference information storage area 106c, and an error information storage area 106d. The storage unit 106 may also include other master and data storage areas.

[0032] The check category master 106a is a master in which information on the reference transaction data is registered for each check category, which will be described later. An example of the configuration of the check category master 106a will be described later with reference to FIG.

[0033] The transaction data storage area 106b, the difference information storage area 106c, and the error information storage area 106d are areas for storing transaction data, difference information, and error information, respectively, which will be described later, and hold each data so that it can be output as necessary. In the transaction data storage area 106b, the transaction data is preferably stored in the form of a table.

[0034] The control unit 102 includes a plurality of modules as shown in Fig. 1. In the example shown in Fig. 1, the control unit 102 includes a difference information generating unit 102a and an error information output unit 102b.

[0035] The difference information generating unit 102a is a module that functions as a difference information generating means for generating difference information, which will be described later. The error information output unit 102b is a module that functions as an error information output means for generating difference information, which will be described later. The functions of each unit include a function for realizing the processing contents, which will be described later.

[0036] [2. Processing] Next, an exemplary transaction management method executed in the transaction management system 1000 shown in FIG. 1 will be described.

[0037] Figure 2 is a flowchart showing the processing steps of a transaction management method executed by transaction management device 100 in transaction management system 1000 of Figure 1. The processing shown in Figure 2 is roughly as follows: when managing a transaction in which an ordered product is ordered and delivered, when new transaction data is input by a user, difference information from reference transaction data is automatically generated, and if the C / F relatively deteriorates, error information is output to the user, and most of this processing is executed by control unit 102 of transaction management device 100. Note that the following description will be given by taking as an example a case in which a sales representative of a trading company is the user of transaction management device 100 and inputs a pair of order data and order data as new transaction data.

[0038] In FIG. 2, first, in step S201, the necessary master settings are accepted. If the master has already been constructed, editing (maintenance) of the master may be accepted. If the master has been constructed and no maintenance is required, this step is skipped. Furthermore, the master settings and maintenance may be allowed only to specific users (e.g., administrators, service personnel).

[0039] An example of the master is the check category master, which will be described later with reference to FIG. 3. It is also preferable to prepare other masters as necessary (for example, a billing master in which an orderer (billing destination) as a first business partner is registered, a payment destination master in which an orderer (payee) as a second business partner is registered, a product master in which products are registered, etc.). The names of the masters are given for convenience, and any name can be adopted. Examples of the master configurations are not limited to those described later, and for example, the billing destination master and the check category master may be integrated, or the billing destination master and the payee master may be integrated. If an existing master exists, in step S201, the existing master may be set to be accessible (referenced).

[0040] FIG. 3 is a diagram showing an example of the configuration of the check category master registered in step S201 of FIG.

[0041] The check category master shown in FIG. 3 is a master in which information on reference transaction data that serves as a preset standard is registered. A plurality of check categories can be registered in the check category master, and in the example shown in FIG. 3, information on reference transaction data for three types of check categories is registered. In this case, in step S201 of FIG. 2, one check category is selectively set from the plurality of check categories. Here, the reference transaction data is transaction data that serves as a standard for obtaining difference information, which will be described later. Information on the reference transaction data is set for each product. However, the same reference transaction data may be adopted for different products for reasons such as the delivery date and payment pattern being the same even if the products are different.

[0042] The check category can be set arbitrarily as long as it is information that can identify the preset reference transaction data, but preferably includes a name that can determine how the reference transaction data was set or how the reference value of the cash flow described below was set.

[0043] In the example shown in FIG. 3, the check category "previous transaction" is a category indicating that the most recent transaction data among the readable transaction data is adopted as the reference transaction data. The readable transaction data is, for example, a table in which a pair of order data and order data is registered, and the order data table and the order data table may be readable separately as long as the pair of order data and order data can be identified. The most recent transaction data may be, for example, the transaction data with the most recent transaction date (e.g., the order date) among the readable transaction data, or the transaction data with a track record of a completed transaction and with the most recent transaction date (e.g., the sales forecast date, or the sales posting date in the track record). In the most recent transaction data, if a transaction is completed or is expected to be completed, the cash flow, specifically gross profit and interest rate, can be grasped for the transaction data. In other words, the check category "previous transaction" is selected when it is desired to obtain difference information from the previous transaction data. This check category "previous transaction" is considered to be set when the collection conditions and payment conditions change for each transaction but do not change significantly.

[0044] The check category "average value" is a category indicating that the transaction data on the average transaction calculated based on the readable transaction data is adopted as the reference transaction data. As the average transaction, the average value of all transactions may be calculated, the average value of transactions in a preset period may be calculated, or the average value of a preset number of transactions from the most recent may be calculated. Here, it is preferable that the average value includes at least the site criteria described later. The average value may be calculated by the user and registered, or may be calculated automatically by the transaction management device 100, but the latter is preferable from the viewpoint of reducing the user's efforts. The check category "average value" is selected when it is desired to obtain difference information from the average value of the transaction data. This check category "average value" is considered to be set when the collection conditions and payment conditions vary for each transaction and the range of variation is large.

[0045] The check category "reference value" is a category indicating that the transaction data set by default is adopted as the reference transaction data. The transaction data set by default may be, for example, a unique value obtained by converting transactions that have a good cash flow or transactions that are assumed to be ideal based on past performance into digital data. The transaction data set by default is preferably a unique value, but the system may be configured so that transaction data with the longest collection site, which will be described later, is automatically extracted from the readable transaction data and updated as the reference transaction data. Here, the unique value preferably includes at least a site standard, which will be described later. The unique value may be registered as a unique value set by the user, or the transaction management device 100 may be configured so that transaction data with the longest collection site, which will be described later, is automatically extracted from the readable transaction data and updated as the reference transaction data. The check category "reference value" is selected when it is desired to obtain difference information from the average value of the transaction data. This check category "reference value" may be set when there is a company regulation (for example, when the payment period to the payee is predetermined by contract or when there is a regulation prohibiting excessive payment delays) or when an ideal transaction form is predetermined.

[0046] As illustrated in FIG. 3, the check category master stores, for each check category, information related to the billing destination (orderer) (e.g., the name of the billing destination company), information related to the revision date (e.g., the month of revision), information related to the interest rate (annual interest rate) (e.g., a numerical value for multiplication or its percentage), information related to site standards, information related to the payee (orderer), etc. The billing destination (orderer) is the billing destination (orderer) of the product related to the order. The payee (orderer) is the payee (orderer) of the product related to the order. The revision date is the date on which information related to the reference transaction data corresponding to the check category is registered. If the transaction management device 100 is configured to identify the reference transaction data, the revision date may be automatically updated. An interest rate (annual interest rate) is generally the interest rate per year (365 days) that may arise on the difference between the period required for payment of the order amount for the ordered product (hereinafter also referred to as the "payment site") and the period required for collection of the order amount for the ordered product (hereinafter also referred to as the "collection site"). If the payment site exceeds the collection site, the interest rate is recorded as a negative value, and if the payment site is lower than the collection site, the interest rate is recorded as a positive value. The payment site is specifically the period calculated by subtracting the planned purchase date (the planned sales date in the case of direct delivery delivery) from the planned payment date. The collection site is specifically the period calculated by subtracting the planned sales date from the planned collection date. In addition, the planned payment date, planned purchase date, planned sales date, and planned collection date are managed as the payment date, purchase date, sales date, and collection date, respectively, in past transactions. The site standard is the period indicated by the payment site in the standard transaction data.

[0047] As described above, the master setting or maintenance in step S201 is completed. In the following, an example will be described in which the check category "previous transaction" is selected in the check category master.

[0048] Next, in step S202, the input of new transaction data is awaited. The determination of step S202 is made, for example, based on whether a transaction input screen (not shown) is activated. If new transaction data is not input (No in step S202), the process returns to step S201 and awaits setting or maintenance of the master or input of new transaction data.

[0049] When new transaction data is to be input (Yes in step S202), a pair of received order data and order data is accepted (steps S203 and S204). It is preferable that the pair of received order data is configured so that the received order data is accepted first and then the order data is accepted on the transaction input screen. The transaction data may be data that is an integrated combination of received order data and order data.

[0050] 4A and 4B are schematic diagrams showing examples of a pair of order data and purchase order data received in steps S203 to S204 in FIG. 2, where FIG. 4A shows an example of the order data and FIG. 4B shows an example of the purchase order data.

[0051] The order data shown in FIG. 4(a) includes information included in normal order data, such as information about the product, information about the billing destination (order source), information about the order date, and information about the order amount, and further includes information about the collection site. When the collection site is determined by an agreement with the billing destination, the number of days indicating the period is input. On the other hand, the collection site may be configured to be calculated automatically. In this case, as shown in FIG. 4(a), it is preferable that the order data includes information about the scheduled collection date and the scheduled sales date. The scheduled collection date is, for example, the scheduled date of payment from the billing destination for the order amount of the product related to the order. The scheduled sales date is, for example, the scheduled delivery date of the product related to the order. It is preferable that the scheduled sales date included in the order data described later is automatically reflected as the scheduled sales date.

[0052] The order data shown in FIG. 4(b) includes information included in normal order data, such as information on the product, information on the payee (ordering party), information on the order date, and information on the order amount, and further includes information on the payment term. When the payment term is determined by an agreement with the payee, the number of days indicating the period is input. On the other hand, the payment term may be configured to be automatically calculated. In this case, as shown in FIG. 4(b), the order data preferably includes information on the scheduled payment date and the scheduled sales date. The scheduled payment date is, for example, the scheduled date of payment to the payee for the order amount of the product related to the order (the scheduled date of withdrawal for the company). The scheduled sales date is, for example, the scheduled date of purchase of the product related to the order, and may be the scheduled delivery date when the product related to the order is directly shipped to the billing party (ordering party). It is preferable that the information on the product and the information on the order date in the order data are configured so that the information on the product and the information on the order date in the corresponding order data are reflected by default.

[0053] Then, when a pair of order data and purchase order data (new transaction data) is accepted, the reference transaction data is read (step S205). The reference transaction data is for the same product as the product of the accepted new transaction data. If the check category "previous transaction" is selected in the check category master, the most recent transaction data is extracted as the reference transaction data from the readable transaction data. Prior to the extraction of the most recent transaction data, it is preferable to read information on site criteria and information on the payee registered in the check category master, and to proceed in parallel with some of the processing required to obtain the difference information in step S206, which will be described later.

[0054] The extraction of the reference transaction data in step S205 will be described with reference to the drawings. FIG. 5 is a diagram showing an example of a transaction data table referred to when reading out the reference transaction data in step S205 in FIG. 2, where FIG. 5(a) shows an order data table and FIG. 5(b) shows an order data table. FIG. 6 is a diagram showing an example of the reference transaction data extracted as a result of step S205 in FIG. 2, where FIG. 6(a) shows the order data included in the reference transaction data and FIG. 6(b) shows the order data included in the reference transaction data. In the process of step S205, first, the transaction data table shown in FIG. 5 is read out, and then the most recent transaction data is identified to determine the reference transaction data (in the example shown in FIG. 6, the order data with the order date of "YYYY / 4 / 15" and the order data with the order date of "YYYY / 4 / 15").

[0055] In the next step S206, difference information is acquired. Specifically, the difference information is acquired by comparing the new transaction data input in steps S203 to S205 with the reference transaction data read in step S205. Examples of difference information include payment site difference information, net gross profit difference information, and interest rate difference information, which will be described below.

[0056] Here, it is preferable that the difference information includes at least payment site difference information related to the difference or magnitude relationship of the payment sites. The payment site difference information is obtained by comparing the payment site included in the reference transaction data with the payment site of the order data included in the new transaction data. Alternatively, it may be obtained by comparing the site criteria registered in the check category master with the payment site of the order data included in the new transaction data.

[0057] In addition, the difference information preferably includes net gross profit difference information related to the difference or magnitude relationship of net gross profit (net gross profit). Here, the net gross profit can be calculated by subtracting various expenses and further subtracting interest from the gross profit on sales, which is usually calculated by subtracting the order amount from the order amount. However, it is often difficult to estimate the various expenses at the stage of inputting new transaction data. Therefore, in this embodiment, the net gross profit is estimated by subtracting interest from the gross profit on sales. That is, in this embodiment, the net gross profit difference information is information related to the difference or magnitude relationship of the net gross profit excluding the various expenses. The net gross profit difference information is obtained by comparing the net gross profit calculated from the reference transaction data with the net gross profit calculated from the new transaction data. Note that, when the various expenses can be estimated, it is preferable to obtain the net gross profit difference information taking the various expenses into consideration.

[0058] It is also preferable that the differential information includes interest rate differential information relating to the difference in interest rates per transaction or the magnitude relationship. Here, the interest rate is calculated by multiplying the transaction amount by the value indicated by the daily interest rate (annual interest rate) corresponding to the period. The period is calculated by subtracting the payment site from the collection site. The value indicated by the daily interest rate (annual interest rate) is the quotient of the value indicated by the interest rate (annual interest rate) for 365 days. If the collection site is lower than the payment site (i.e., if collection site - payment site > 0), the interest rate is recorded as a positive value using the purchase amount (i.e., order amount) as the transaction amount (it is recorded as a negative value when calculating net gross profit). In the calculation program, the case where the collection site is the same as the payment site (i.e., if collection site - payment site = 0) is also treated in the same way. On the other hand, if the collection date exceeds the payment date (i.e., if the collection date - payment date < 0), the sales amount (i.e., the order amount) is used as the transaction amount, and it is recorded as a negative value (it is recorded as a positive value when calculating net gross profit).

[0059] FIG. 7 is a diagram used to explain an example of calculation logic for interest and net gross profit used to obtain difference information in step S206 of FIG. 2. In FIG. 7, formula (1) is a formula used to calculate the period used to calculate interest. Formulas (2) and (3) are formulas used to calculate interest, and either formula is used depending on whether the period calculated by formula (1) indicates a positive value or a negative value. Formula (4) is a formula used to calculate gross profit on sales. Formula (5) is a formula used in this embodiment to calculate net gross profit excluding expenses.

[0060] Fig. 8 is a diagram used to explain the results when the calculation logic of Fig. 7 is applied to the reference transaction data (most recent transaction data) shown in Fig. 6. Fig. 9 is a diagram used to explain the results when the calculation logic of Fig. 7 is applied to the new transaction data shown in Fig. 4. In step S206 of Fig. 2, the results shown in Fig. 8 and Fig. 9 are obtained, and by comparing these results, net gross profit difference information and interest rate difference information as difference information can be obtained.

[0061] Next, in step S207, it is determined whether the cash flow (C / F) has deteriorated. Specifically, it is determined whether the difference information acquired in step S206 is relative deterioration information indicating a relative deterioration in the cash flow compared to the reference transaction data. For example, if the payment term difference information indicates that the payment term of the new transaction data is smaller than that of the reference transaction data, it can be determined that it indicates a relative deterioration in the cash flow. This is because, as the payment term becomes relatively shorter, it becomes necessary to pay the order amount early, and it is expected that interest rates will become higher and net gross profits will become lower. Similarly, if the net gross profit information and the interest rate difference information indicate that interest rates will become higher and net gross profits will become lower, respectively, it can be determined that it indicates a relative deterioration in the cash flow.

[0062] If it is determined in step S207 that the cash flow (C / F) will not worsen (No in step S207), the process in steps S208 to S211 (processing related to error information output) described below is skipped and this process is completed. Therefore, the user can easily obtain information about the cash flow at the time of a new transaction that the cash flow has improved compared to the reference transaction data, based on the fact that the processing related to error information output was not performed.

[0063] On the other hand, if it is determined that the cash flow (C / F) will worsen (Yes in step S207), then in step S208 it is determined whether the supplier (payee) is the same. Specifically, it is determined whether the supplier (payee) of the order data included in the new transaction data is the same as the supplier (payee) of the order data included in the reference transaction data. Alternatively, it may be determined whether the supplier (payee) of the order data included in the new transaction data is the same as the payee (supplier) registered in the check category master.

[0064] Then, if the result of the judgment in step S208 is that the supplier (payee) is the same (Yes in step S208), the process proceeds to step S209, where error information is output. Examples of error information output in step S209 include a warning message such as "The payment term has been accelerated since the previous transaction. Are you sure?", information on the payment term included in the information on the reference transaction data (e.g., "Last payment term: 90 days"), net gross profit information calculated from the reference transaction data (e.g., "Last net gross profit: 200,205 yen") or interest rate information (e.g., "Last interest rate: 205 yen"), or a combination of these. This encourages the user to improve cash flow (C / F) at the stage of inputting new transaction data. As a specific example, negotiations with the supplier to extend the payment term (specifically, to postpone payment) and negotiations with the order-receiving party to shorten the collection term (specifically, to make payment earlier) can be considered. Then, the process proceeds to step S210.

[0065] Also, if the result of the determination in step S208 is that the supplier (payment destination) is not the same (No in step S208), the process proceeds to step S211, where error information is output. The error information output in step S211 includes information about the other supplier. Preferably, the error information output in step S211 includes the error information output in step S209 and information about the other supplier. The information about the other supplier may be obtained from information about the payment destination (supplier) registered in the check category master, or from information about the payment destination (supplier) of the order data included in the reference transaction data. As information about the other supplier, for example, "Previous supplier: Company B" is displayed. This encourages the user to improve cash flow (C / F) at the stage of inputting new transaction data. To cite a specific example, the user can consider changing the supplier, negotiating to extend the payment term to the supplier (specifically, to postpone the scheduled payment date), and negotiating to shorten the collection term to the order source (specifically, to make payment earlier). Then, the process proceeds to step S210.

[0066] In step S210 after the error information is output, it is determined whether the transaction data has been updated. Specifically, it is determined whether the user has changed any of the received order data and order data entered in steps S205 to S206. If the transaction data has been updated (Yes in step S210), the process returns to step S205 to obtain difference information again. On the other hand, if the transaction data has not been updated, for example, if the cash flow is acceptable to the user (No in step S210), this process is completed.

[0067] Here, a specific example of the process flow in FIG. 2 will be described with reference to the drawings.

[0068] The first specific example is a case where new transaction data as shown in FIG. 4 is input (steps S203 to S205). The new transaction data shown in FIG. 4 is compared with the reference transaction data shown in FIG. 6 to obtain difference information. To obtain the payment term difference information, the payment term "90 days" of the reference transaction data is compared with the payment term "120 days" of the new transaction data. As a result, "+30 days" is obtained as the payment term difference information. This indicates that the payment term of the new transaction data is longer than that of the reference transaction data, and therefore, no deterioration in cash flow (C / F) is expected. This becomes clearer by comparing the results of calculating the interest rate and net gross profit for the reference transaction data (see FIG. 8) with the results of calculating the interest rate and net gross profit for the new transaction data shown in FIG. 4 (see FIG. 9). Therefore, the error information output process (steps S208 to S211) is skipped.

[0069] The second specific example is a case where new transaction data as shown in FIG. 10 (different data from the new transaction data shown in FIG. 4) is input as new transaction data (steps S203 to S205). In order to obtain the payment term difference information, the payment term "90 days" of the reference transaction data is compared with the payment term "60 days" of the new transaction data shown in FIG. 10. As a result, "-30 days" is obtained as the payment term difference information. This indicates that the payment term of the new transaction data is shorter than that of the reference transaction data, and therefore, a deterioration in cash flow (C / F) is expected. This becomes clearer by comparing the result of calculating the interest rate and net gross profit for the reference transaction data (see FIG. 8) with the result of calculating the interest rate and net gross profit for the new transaction data shown in FIG. 10 (see FIG. 11). Therefore, the error information output process (steps S208 to S211) is executed.

[0070] The third specific example is a case where new transaction data as shown in FIG. 12 (data different from the new transaction data shown in FIG. 4 and FIG. 10) is input as new transaction data (steps S203 to S205). In order to obtain the payment term difference information, the payment term "90 days" of the reference transaction data is compared with the payment term "60 days" of the new transaction data shown in FIG. 12. As a result, "-30 days" is obtained as the payment term difference information. This indicates that the payment term of the new transaction data is shorter than that of the reference transaction data, and therefore, a deterioration in cash flow (C / F) is expected. This becomes clearer by comparing the results of calculating interest and net gross profit for the reference transaction data (see FIG. 8) with the results of calculating interest and net gross profit for the new transaction data shown in FIG. 12 (see FIG. 13). In addition, by comparing the payee "Company B" of the reference transaction data with the payee "Company C" of the new transaction data shown in FIG. 12, it can be seen that they are different. Therefore, in the error information output process, "Company B" from the reference transaction data is presented as another payee (supplier) in step S211. This enables the user to understand that a deterioration in cash flow can be prevented by placing an order with Company B, whose payment term is 90 days, rather than placing an order with Company C, whose payment term is 60 days, or by negotiating with Company C to have a longer payment term than that of Company B.

[0071] As explained in detail above, according to the processing procedure of the transaction management method shown in Fig. 2, when managing a transaction for ordering and delivering an ordered product, the transaction management device 100 compares new transaction data input for a certain product with reference transaction data that serves as a preset standard for the same product as the certain product, and generates difference information regarding the difference or magnitude relationship of the new transaction data relative to the reference transaction data at the time of inputting the new transaction data (step S206) (difference information generating means). This allows the user to easily obtain information regarding cash flow from the transaction management device 100 at the time of a new transaction. As a result, the user can consider whether or not to change the new transaction based on the information regarding cash flow.

[0072] Here, it is preferable that the difference information includes information on the difference or magnitude relationship of the payment terms indicating the period obtained by subtracting the planned purchase date of the ordered goods or the sales recording date of the transaction of the ordered goods from the planned payment date to the supplier for the ordered goods. This makes it possible to predict whether the cash flow will deteriorate relatively compared to the reference transaction data. It is also preferable that the difference information includes information on the difference or magnitude relationship of the net gross profit excluding various expenses. It is possible to more accurately grasp whether the cash flow will deteriorate relatively compared to the reference transaction data. It is also preferable that the difference information includes information on the difference or magnitude relationship of the interest rate per transaction. It is possible to more accurately grasp whether the cash flow will deteriorate relatively compared to the reference transaction data.

[0073] Moreover, according to the process of FIG. 2, if the difference information is relative deterioration information indicating a relative deterioration of the cash flow compared to the reference transaction data, error information is output (steps S209, S211) (error information output means). Furthermore, if the difference information is the relative deterioration information, error information including information on other suppliers is output. This allows the user to easily obtain information on the relative deterioration of the cash flow compared to the reference transaction data at the time of a new transaction. As a result, the user can consider changing the new transaction based on the information on the cash flow.

[0074] Furthermore, according to the process of Fig. 2, the reference transaction data can be changed by selecting a check category in the check category master. Here, the reference transaction data may be the most recent transaction data among the readable transaction data, or may be transaction data relating to an average transaction calculated based on the readable transaction data, or may be transaction data set as a default. Since the reference transaction data can be changed in this way, it is possible to set the reference transaction data according to the transaction status. Note that one reference transaction data may be set without setting a check category in the check category master.

[0075] In the above description, the transaction data is composed of a pair of order data and purchase order data, but the transaction data may be integrated with the order data to be sent or received. The order data may be divided into a plurality of pieces, and each piece of order data may be linked to a different purchase order data set.

[0076] In addition, in the above explanation, it is assumed that new transaction data is input in accordance with transactions that actually occur, but the present invention is also applicable to a case where new transaction data corresponding to a hypothetical transaction is input to perform a simulation.

[0077] [3. 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 goals 8 and 9 of the SDGs.

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

[0079] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0080] [4. Other embodiments] The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth 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 using known methods.

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

[0083] Furthermore, with regard to transaction management device 100 and transaction management system 1000, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.

[0084] For example, the processing functions of the transaction management device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that includes programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the transaction management device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into a RAM, and cooperates with the CPU to form the control unit.

[0085] In addition, this computer program may be stored in an application program server connected to the transaction management device 100 via any network (e.g., network 300), and it is also possible to download all or part of it as needed.

[0086] In addition, the program for executing the process described in this embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the "recording medium" includes any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc. Therefore, a recording medium storing a program for executing the process described in this specification also constitutes the present invention.

[0087] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration as multiple modules or libraries, and a program that works with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, may use well-known configurations and procedures.

[0088] The various databases etc. stored in the memory unit 106 are storage means such as 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, web page files, etc. used for various processes and providing websites.

[0089] Transaction management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Transaction management device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processes described in this specification.

[0090] 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 functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0091] The present invention is useful in managing transactions in which ordered merchandise is ordered and then delivered (for example, a form of transaction in trading companies or wholesale businesses). [Explanation of symbols]

[0092] 100 Transaction management device 102 Control section 102a Difference information generation section 102b Error information output section 104 Communication interface section 106 Storage section 106a Check Category Master 106b Transaction data storage area 106c Difference information storage area 106d Error information storage area 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network 1000 Transaction Management System

Claims

1. A transaction management device having a control unit for managing a transaction of ordering and delivering an ordered product, The control unit is a difference information generating means for comparing new transaction data input for a certain product with reference transaction data, which is a preset reference for the same product as the certain product, and generating difference information relating to a difference or a magnitude relationship between the new transaction data and the reference transaction data at the time of inputting the new transaction data; Equipped A transaction management device characterized by:

2. The difference information is Including information regarding the difference or magnitude relationship of the payment date, which indicates the period obtained by subtracting the scheduled purchase date of the ordered goods or the sales recording date of the transaction of the ordered goods from the scheduled payment date to the supplier for the ordered goods, 2. The transaction management device according to claim 1.

3. The difference information is Including information on the difference or magnitude relationship of net gross profit excluding various expenses, 3. A transaction management device according to claim 1 or 2.

4. The difference information is Including information on the difference or magnitude of interest rates per transaction, 4. The transaction management device according to claim 1, wherein the transaction management device is a transaction management system.

5. The control unit is an error information output means for outputting error information when the difference information is relative deterioration information indicating a relative deterioration of the cash flow compared to the reference transaction data; Equipped 5. The transaction management device according to claim 1, wherein the transaction management device is a transaction management system.

6. The error information output means When the difference information is the relative deterioration information, the error information including information on other suppliers is output.

6. A transaction management device according to claim 5.

7. The reference transaction data is Of all the transaction data that can be read, this is the most recent transaction data.

7. A transaction management device according to claim 1, wherein:

8. The reference transaction data is Transaction data for average transactions calculated based on readable transaction data 7. A transaction management device according to claim 1, wherein:

9. The reference transaction data is This is the default transaction data.

7. A transaction management device according to claim 1, wherein:

10. A transaction management method for managing a transaction of ordering and delivering an ordered product, the method being executed in a transaction management device having a control unit, comprising: Executed in the control unit, a difference information generating step of comparing new transaction data input for a certain product with reference transaction data serving as a preset reference for the same product as the certain product, and generating difference information relating to a difference or a magnitude relationship between the new transaction data and the reference transaction data at the time of inputting the new transaction data; Includes A transaction management method comprising:

11. A transaction management program for managing a transaction of ordering and delivering an ordered product, the transaction management program being executed in a transaction management device having a control unit, To be executed in the control unit, a difference information generating step of comparing new transaction data input for a certain product with reference transaction data serving as a preset reference for the same product as the certain product, and generating difference information relating to a difference or a magnitude relationship between the new transaction data and the reference transaction data at the time of inputting the new transaction data; Includes A transaction management program comprising:

Citation Information

Patent Citations

  • Credit sales collection managing device and method therefor and recording medium for recording credit sales collection management program

    JP1999149509A

  • Defined-contribution pension scheme application support system

    JP2002133123A

  • Transaction management device, transaction management method and program for realizing transaction management function on computer

    JP2003091664A

  • Credit management server, credit management method and program

    JP2004164245A

  • Project management device, project description output method and project description output program

    JP2019053583A