JP2023019485A - Transaction management apparatus, transaction management method, and transaction management program - Google Patents

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

Description

The present invention relates to a transaction management device, a transaction management method, and a transaction management program.

In Patent Document 1, in a business model in which a product is produced after receiving an order, the amount of cost required for the product is managed, and when the managed cost amount exceeds the set planned cost amount, warning information is displayed. A system capable of calling the user's attention is disclosed (see claim 38, for example).

WO2003/081492

By the way, in a trading company, a wholesale business, etc., there is a form of transaction in which ordered products are ordered and delivered. Here, the delivery is performed by purchasing and delivering the product or directly sending the ordered product. In such a form of transaction, the person in charge (for example, a sales person) usually determines the order amount by taking into consideration the order amount of the product ordered from the first business partner and the overhead expenses, and then the second transaction. order ahead. By conducting such transactions, a trading company, a wholesaler, or the like can obtain a gross profit.

However, the gross profit cannot be accurately grasped until the stage of recording sales, which is performed by delivering the ordered product to the first business partner. Therefore, a person in charge such as a sales person cannot grasp the gross profit at the stage of receiving an order and placing an order. In addition, since gross profit is generally understood by a person other than the salesperson, such as an accounting person, the salesperson often does not try to understand the gross profit after recording the sales. rice field.

Therefore, even in the transaction of ordering and delivering ordered products, it is required to be able to grasp the cash flow such as gross profit (hereinafter also referred to as "C/F") at the time of new transaction. If the sales staff can grasp the cash flow at the time of new transaction, it is expected that they will be able to utilize it for more sound transactions.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems (requirements), and provides a transaction management device, a transaction management method, and a transaction management method that enable a user to obtain information about cash flow at the time of a new transaction without trouble. The purpose is to provide a transaction management program.

In order to solve the above-described problems and achieve the object, a transaction management device according to the present invention is a transaction management device comprising a control unit for managing a transaction of ordering and delivering ordered products. The control unit compares 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 compares the new transaction data at the time of input of the new transaction data. It is characterized by comprising difference information generating means for generating difference information relating to the difference of the new transaction data with respect to the reference transaction data or the magnitude relationship.

In addition, the transaction management device according to the present invention, the difference information is the period obtained by subtracting the scheduled purchase date of the product or the sales recording date of the transaction of the product from the scheduled payment date to the orderer for the ordered product It is characterized by including information on the difference or magnitude relationship of the payment sites indicating the .

Moreover, the transaction management apparatus according to the present invention is characterized in that the difference information includes information about the difference or magnitude relationship of net gross profit excluding overhead expenses.

Further, the transaction management device according to the present invention is characterized in that the difference information includes information regarding the difference in interest rates per transaction or the magnitude relationship.

Further, in the transaction management device according to the present invention, the control unit outputs error information when the difference information is relative deterioration information indicating relative deterioration of cash flow compared to the reference transaction data. and error information output means for outputting the error information.

Further, in the transaction management apparatus according to the present invention, the error information output means outputs error information including information regarding other suppliers when the difference information is the relative deterioration information.

Further, 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.

Also, the transaction management apparatus according to the present invention is characterized in that the reference transaction data is transaction data relating to average transactions calculated based on readable transaction data.

Further, the transaction management device according to the present invention is characterized in that the reference transaction data is transaction data set by default.

Further, a transaction management method according to the present invention is a transaction management method for managing a transaction of ordering and delivering an ordered product, which is executed in a transaction management device having a control unit, wherein the control unit New transaction data to be executed, which is input for a certain product, is compared with reference transaction data, which is a preset standard for the same product as the certain product, to compare the new transaction data at the time of input of the new transaction data. It is characterized by including a difference information generation step of generating difference information relating to a difference or magnitude relationship of the transaction data with respect to the reference transaction data.

Further, a transaction management program according to the present invention is a transaction management program for managing a transaction of ordering and delivering an ordered product, which is executed in a transaction management device having a control unit, wherein the control unit New transaction data input for a certain product for execution is compared with reference transaction data, which is a preset reference for the same product as the certain product. It is characterized by including a difference information generation step of generating difference information relating to a difference or magnitude relationship between the new transaction data and the reference transaction data.

ADVANTAGE OF THE INVENTION According to this invention, it is effective in the ability for a user to acquire the information regarding a cash flow at the time of a new transaction without time and effort.

FIG. 1 is a block diagram showing an example configuration of a transaction management system including a transaction management device according to an embodiment of the present invention. FIG. 2 is a flow chart showing a processing procedure of a transaction management method executed by transaction management apparatus 100 in transaction management system 1000 of FIG. FIG. 3 is a diagram schematically showing an example of the configuration of the check classification master registered in step S201 of FIG. FIG. 4 is a diagram schematically showing a first example of a pair of order data and order data received in steps S203 and S204 of FIG. FIG. 4B is a diagram showing an example of order data. 5A and 5B schematically show an example of a transaction data table referred to when reading the reference transaction data in step S205 of FIG. 2. FIG. ) is a diagram showing an order data table. 6A and 6B are diagrams schematically showing an example of the standard transaction data extracted as a result of step S205 in FIG. ) is a diagram showing order data included in the reference transaction data. FIG. 7 is a diagram used to explain an example of interest rate and net gross profit calculation logic used to acquire difference information in step S206 of FIG. FIG. 8 is a diagram used to explain the result of applying the calculation logic of FIG. 7 to the reference transaction data shown in FIG. FIG. 9 is a diagram used to explain the result of applying the calculation logic of FIG. 7 to the new transaction data shown in FIG. FIG. 10 is a diagram schematically showing a second example of a pair of order data and order data received in steps S203 and S204 of FIG. FIG. 10B is a diagram showing an example of order data. FIG. 11 is a diagram used to explain the results of calculating the interest rate and net gross profit for the new transaction data shown in FIG. FIG. 12 is a diagram schematically showing a third example of a pair of order data and order data received in steps S203 and S204 of FIG. FIG. 12B is a diagram showing an example of order data. FIG. 13 is a diagram used to explain the results of calculating the interest rate and net gross profit for the new transaction data shown in FIG.

An embodiment of the present invention will be described in detail based on the drawings. In addition, this invention is not limited by this embodiment.

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

Transaction management system 1000 shown in FIG. 1 includes transaction management device 100 as an information processing device, server 200, and network 300 connecting transaction management device 100 and server 200 in a communicable manner.

The transaction management device 100 is an information processing device for managing the transaction of ordering and delivering ordered products, and is composed of, for example, a commercially available desktop personal computer. One transaction management device 100 is installed, for example, in a department that manages transactions (for example, a sales department, an order reception department, or an order placement department). Note that the transaction management device 100 is not limited to a stationary information processing device such as a desktop personal computer, and may be a portable type such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), a smart phone, or a tablet personal computer. It may be an information processing device. Further, a plurality of transaction management apparatuses 100 may be installed in the transaction management system 1000, and the plurality of transaction management apparatuses 100 may function as a single transaction management apparatus 100 by synchronizing the transaction management apparatuses 100. good.

Transaction management device 100 includes control unit 102 , communication interface unit 104 , storage unit 106 , and input/output interface unit 108 . Each unit included in transaction management apparatus 100 is communicably connected via an arbitrary communication path.

The communication interface unit 104 communicably connects the transaction management apparatus 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 another device via a communication line. Here, the network 300 has a function of connecting the transaction management apparatus 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Therefore, the communication interface unit 104 is configured to be able to receive information or the like from another information processing device (for example, an information processing device of a business partner) via the network 300 or via the network 300 and the server 200. In addition, it is configured to be able to output predetermined information to a predetermined information processing device (for example, an information processing device of a business partner).

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores computer programs (including the program of the present invention) for performing various processes by giving commands to a CPU (Central Processing Unit) in cooperation with an OS (Operating System). As the storage unit 106, for example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used. Also, in this storage unit 106, various data used for executing the program of the present invention are stored in a writable/readable manner.

An input device 112 and an output device 114 are connected to the input/output interface unit 108 . The output device 114 can be a monitor (including a home television), a speaker, or a printer. The input device 112 can be a keyboard, a mouse, a microphone, or a monitor that realizes a pointing device function in cooperation with a mouse.

The control unit 102 is a CPU or the like that controls the transaction management apparatus 100 in an integrated manner. The control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, required data, and the like, and performs various information processing based on these stored programs. Execute.

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

Storage unit 106, as shown in FIG. 1, includes check classification master 106a, transaction data storage area 106b, difference information storage area 106c, and error information storage area 106d. The storage unit 106 may also include other master and data storage areas.

The check classification master 106a is a master in which information on standard transaction data is registered for each check classification described later. A configuration example of the check classification master 106a will be described later with reference to FIG.

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

The control unit 102 comprises a plurality of modules, as shown in FIG. In the example shown in FIG. 1, the control unit 102 includes a difference information generation unit 102a and an error information output unit 102b.

The difference information generation unit 102a is a module that functions as difference information generation means for generating difference information described later. The error information output unit 102b is a module that functions as error information output means for generating difference information, which will be described later. The function of each part includes the function of realizing the processing contents to be described later.

[2. process]
Next, a transaction management method executed in the transaction management system 1000 shown in FIG. 1 will be exemplified.

FIG. 2 is a flow chart showing a processing procedure of a transaction management method executed by transaction management apparatus 100 in transaction management system 1000 of FIG. The process shown in FIG. 2 can be roughly described as follows: When new transaction data is input by a user when managing transactions for ordering and delivering ordered products, difference information from standard transaction data is automatically calculated. When the C/F is relatively degraded, error information is output to the user. In the following description, a sales representative of a trading company, who is a user of the transaction management apparatus 100, inputs a pair of order data and order data as new transaction data.

In FIG. 2, first, in step S201, necessary master settings are accepted. If a master has already been constructed, editing (maintenance) of such master may be accepted. If the master has been built and no maintenance is required, this step is skipped. Also, setting and maintenance of the master may be performed only by specific users (for example, administrators, service personnel).

The master includes a check classification master, which will be described later with reference to FIG. In addition, if necessary, other masters (for example, a billing master in which the ordering party (billing party) as the first business partner is registered, a payment destination in which the ordering party (paying party) as the second business partner is registered It is preferable to prepare a master, product master in which products are registered, etc.). Note that the name of the master is for convenience, and any name can be adopted. In addition, examples of the master configuration are not limited to those described later. good too. Also, if there is an existing master, access (reference) to the existing master may be enabled in step S201.

FIG. 3 is a diagram schematically showing an example of the configuration of the check classification master registered in step S201 of FIG.

The check classification master exemplified in FIG. 3 is a master in which information related to reference transaction data serving as a preset reference 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 standard transaction data relating to three types of check categories is registered. In this case, in step S201 of FIG. 2, one check category is selectively set from a plurality of check categories. Here, the reference transaction data is transaction data that serves as a reference for acquiring difference information, which will be described later. Information related to 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.

The check category can be set arbitrarily as long as it is information that can identify preset reference transaction data. It is preferable to include a name by which it can be determined whether or not it has been set.

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 a group of order data are registered. and may be individually readable. The most recent transaction data may be, for example, transaction data with the latest transaction date (for example, order date) among readable transaction data, or transaction data with a track record of completed transactions. (For example, the scheduled sales date, or in the case of actual results, the sales recording date) may be the most recent transaction data. In the latest transaction data, if the transaction has been completed or is expected to be completed, cash flow, specifically gross profit and interest rate can be grasped for the transaction data. That is, the check category "previous transaction" is selected when it is desired to acquire difference information from the previous transaction data. This check category "previous transaction" may be set when the collection terms and payment terms change for each transaction, but there are no major changes.

The check category "average value" is a category indicating that transaction data relating to average transactions calculated based on readable transaction data has been adopted as reference transaction data. As an average transaction, the average price of all transactions may be calculated, the average price of transactions in a preset period may be calculated, or the number of transactions set in advance from the most recent An average value may be calculated. Here, the average value preferably includes at least the site criteria described later. As the average value, the value calculated by the user may be registered, or the value automatically calculated by the transaction management apparatus 100 may be registered. The check section “average value” is selected when it is desired to obtain difference information from the average value of transaction data. It is conceivable that this check category "average value" is set when collection terms and payment terms vary for each transaction and the range of variation is large.

The check category “reference value” is a category indicating that the transaction data set by default has been adopted as the reference transaction data. Transaction data that is set by default may be, for example, unique values obtained by converting transactions in which the cash flow is good or transactions that are assumed to be ideal based on past records. The transaction data set by default is preferably a unique value, but from among the readable transaction data, the transaction data for which the recovery site described later has the longest period is automatically extracted and updated as reference transaction data. It may be configured to Here, the eigenvalues preferably include at least site criteria, which will be described later. As the eigenvalue, a value arbitrarily set by the user may be registered. , and updated as reference transaction data. The check category “reference value” is selected when it is desired to obtain difference information from the average value of transaction data. This check category "reference value" is used when there are internal regulations (for example, when the payment period to the payee is predetermined by contract or when there is a provision prohibiting excessive delay in payment), or when there is an ideal transaction form is determined in advance.

In the check classification master, as illustrated in FIG. 3, for each check classification, information on billing destination (ordering party) (for example, billing company name), information on revision date (for example, revision month) , interest rate (annual interest rate) information (for example, a multiplication value or its percentage), information on site standards, information on payees (order recipients), and the like are registered. The billing destination (ordering party) is the billing destination (ordering party) of the product related to the order. The payment destination (order destination) is the payment destination (order destination) of the ordered product. The revision date is the date when the information on the reference transaction data corresponding to the check category is registered. If the transaction manager 100 is configured to identify reference transaction data, the revision date may be automatically updated. The interest rate (annual interest rate) generally refers to the period required to pay the order amount for the ordered product (hereinafter also referred to as "payment site") and the period required to collect the order amount for the ordered product. It is the interest rate per year (365 days) of the interest that can occur in the difference between the period (hereinafter also referred to as "collection site"), and if the payment site exceeds the collection site, the interest rate will be recorded as a negative Interest is reported positive if it falls below the collection site. Specifically, the payment site is a period calculated by subtracting the scheduled purchase date (scheduled sales date in the case of direct delivery) from the scheduled payment date. Specifically, the collection site is a period calculated by subtracting the scheduled sales date from the scheduled collection date. The scheduled payment date, scheduled purchase date, scheduled sales date, and scheduled collection date are managed as payment date, purchase date, sales date, and collection date, respectively, in past transactions. The site reference is the period indicated by the payment site in the reference transaction data.

As described above, the master setting or maintenance in step S201 is completed. In the following, a case where the check category "previous transaction" is selected in the check category master will be described as an example.

Next, in step S202, it waits for the input of new transaction data. The determination in step S202 is made, for example, by whether or not a transaction input screen (not shown) is activated. If no new transaction data is entered (No in step S202), the process returns to step S201 to wait for master setting or maintenance or entry of new transaction data.

If new transaction data is to be entered (Yes at step S202), a pair of received order data and order data is accepted (steps S203 and S204). The pair of order data is preferably configured such that the order data is received after the order data is received on the transaction input screen. The transaction data may be data obtained by integrating order data and order data.

FIG. 4 is a diagram schematically showing an example of a pair of order data and order data received in steps S203 and S204 of FIG. b) is a diagram showing an example of order data.

The order data shown in FIG. 4(a) includes information contained in normal order data such as product information, billing destination (orderer) information, order date information, and order amount information. Contains information. If the collection site is determined by agreement with the billing party, the number of days indicating the period is entered. On the other hand, collection sites may be configured to be automatically calculated. In this case, as shown in FIG. 4(a), the order data preferably includes information on the scheduled collection date and the scheduled sales date. The scheduled collection date is, for example, the scheduled payment date 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 order data, which will be described later, is automatically reflected as the scheduled sales date.

The order data shown in FIG. 4(b) includes information included in normal order data, such as product information, payment destination (ordering party) information, order date information, and order amount information. Contains information. If the payment site is determined by agreement with the payee, the number of days indicating the period is entered. On the other hand, the payment site may be configured to be calculated automatically. In this case, the order data preferably includes information on the scheduled payment date and the scheduled sales date, as shown in FIG. 4(b). The scheduled payment date is, for example, the scheduled payment date (scheduled withdrawal date for the company) of the order amount of the ordered product to the payee. The scheduled sales date is, for example, the scheduled purchase date of the ordered product, and may be the scheduled delivery date when the ordered product is shipped directly to the billing destination (orderer). It is preferable that the product information and order date information in the order data are configured to reflect the product information and order date information in the corresponding order data by default.

When a pair of order data and order data (new transaction data) is received, reference transaction data is read (step S205). The standard transaction data is standard transaction data for the same product as the product of the received new transaction data. In the check classification master, when the check classification "previous transaction" is selected, the most recent transaction data is extracted from the readable transaction data as the reference transaction data. Prior to extracting the most recent transaction data, the information on the site criteria and the information on the payee registered in the check classification master are read, and a part of the processing required to acquire the difference information in step S206, which will be described later, is executed in parallel. It is preferable to proceed

Extraction of the reference transaction data in step S205 will be described with reference to the drawings. 5A and 5B schematically show an example of a transaction data table referred to when reading the reference transaction data in step S205 of FIG. 2. FIG. ) is a diagram showing an order data table. 6A and 6B are diagrams schematically showing an example of the standard transaction data extracted as a result of step S205 in FIG. ) is a diagram showing order data included in the reference transaction data. In the process of step S205, first, the transaction data table as shown in FIG. 5 is read, and then the most recent transaction data is specified to obtain the reference transaction data (in the example shown in FIG. 6, the order date "YYYY/4 /15" and the order date "YYYY/4/15") are determined.

In subsequent step S206, difference information is acquired. Specifically, the difference information is acquired by comparing the new transaction data input in steps S203-S205 with the reference transaction data read out 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.

Here, the difference information preferably includes at least payment site difference information relating to differences or magnitude relationships between payment sites. The payment site difference information is acquired 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 acquired by comparing the site criteria registered in the check classification master with the payment site of the order data included in the new transaction data.

In addition, the difference information preferably includes net gross profit difference information relating to the difference in net gross profit (net gross profit) or magnitude relationship. Here, the net gross profit can be calculated by subtracting various expenses from the sales gross profit, which is usually calculated by subtracting the order amount from the order amount, and then subtracting the interest. However, there are many cases where it is difficult to estimate overhead costs at the stage of inputting new transaction data. Therefore, in the present embodiment, the net gross profit is estimated by subtracting the interest rate from the sales gross profit. That is, in the present embodiment, the net gross profit difference information is information relating to the difference or magnitude relationship of the net gross profit excluding overhead costs. The net gross profit difference information is acquired by comparing the net gross profit calculated from the reference transaction data and the net gross profit calculated from the new transaction data. Incidentally, when the overhead costs can be estimated, it is preferable to acquire the net gross profit difference information in consideration of the overhead costs.

Further, the difference information preferably includes interest rate difference information relating to the interest rate difference or magnitude relationship per transaction. 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 duration is calculated by subtracting the payment site from the collection site. The value indicated by the interest rate per day (annual interest) is the quotient of the value indicated by the interest rate (annual interest) for 365 days. If the collection site is lower than the payment site (i.e. 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 (net gross profit is recorded as a negative value when calculating ). On the computing program, the case where the collection site is the same as the payment site (that is, collection site-payment site=0) is handled in the same way. On the other hand, if the number of collection sites exceeds the number of payment sites (i.e., collection site - payment site < 0), the sales amount (that is, order amount) is used as the transaction amount and recorded as a negative value (net gross profit are counted as positive in the calculation).

FIG. 7 is a diagram used to explain an example of interest rate and net gross profit calculation logic used to acquire difference information in step S206 of FIG. In FIG. 7, formula (1) is a formula used for calculating the period used for calculating the interest rate. Formulas (2) and (3) are formulas used to calculate the interest rate. formula is used. Formula (4) is a formula used to calculate gross profit on sales. Formula (5) is a formula used to calculate the net gross profit excluding overhead costs in this embodiment.

FIG. 8 is a diagram used to explain the result of applying the calculation logic of FIG. 7 to the reference transaction data (most recent transaction data) shown in FIG. FIG. 9 is a diagram used to explain the result of applying the calculation logic of FIG. 7 to the new transaction data shown in FIG. In step S206 of FIG. 2, the results shown in FIGS. 8 and 9 are obtained, and by comparing these results, net gross profit difference information and interest rate difference information can be obtained as difference information.

Subsequently, in step S207, it is determined whether or not the cash flow (C/F) deteriorates. Specifically, it is determined whether or not the difference information acquired in step S206 is relative deterioration information indicating relative deterioration of the cash flow compared to the reference transaction data. For example, if the payment site difference information indicates that the new transaction data has a smaller payment site than the reference transaction data, it can be determined to indicate a relative deterioration in cash flow. This is because it is expected that the payment site will be shortened in a relatively short period of time, requiring early payment of the order amount, which will lead to higher interest rates and lower net gross profit. Similarly, when the net gross profit information and the interest rate difference information indicate that the interest rate will increase and the net gross profit will decrease, respectively, it can be determined that the cash flow is relatively deteriorated.

As a result of the determination in step S207, when it is determined that the cash flow (C/F) does not deteriorate (No in step S207), the processing of steps S208 to S211 (processing related to error information output) described later is skipped. to complete this process. Therefore, based on the fact that the processing related to error information output was not performed, the user can easily obtain the fact that the cash flow has improved compared to the reference transaction data as information on the cash flow at the time of the new transaction. It will be possible.

On the other hand, if it is determined that the cash flow (C/F) deteriorates (Yes in step S207), it is further determined in step S208 whether or not the supplier (payee) is the same. Specifically, it is determined whether or not the supplier (payee) of the order data included in the new transaction data and the supplier (payee) of the order data included in the standard transaction data are the same. Alternatively, it may be determined whether or not the orderer (payee) of the order data included in the new transaction data is the same as the payee (orderer) registered in the check classification master.

Then, as a result of determination in step S208, if the orderer (payee) is the same (Yes in step S208), the process proceeds to step S209 to output error information. The error information output in step S209 includes the display of a warning message such as "The payment site is earlier than the previous transaction. Are you sure?" "Previous payment site: 90 days."), net gross profit information calculated from the reference transaction data (for example, "previous net gross profit: 200,205 yen."), or interest rate information (for example, "previous interest rate : It's 205 yen.") or a combination of these displays. This prompts the user to improve cash flow (C/F) at the stage of inputting new transaction data. Specific examples include negotiating with suppliers to lengthen the payment site (specifically, postponing payment), and shortening the collection site with the orderer (specifically, speeding up payment). Negotiations can be taken into consideration. Then, the process proceeds to step S210.

Further, as a result of determination in step S208, if the orderer (payee) is not the same (No in step S208), the process proceeds to step S211 to output error information. The error information output in step S211 includes information on other suppliers. Preferably, the error information output in step S211 includes the error information output in step S209 and information on other suppliers. Information on other suppliers may be obtained from the information on the payee (supplier) registered in the check classification master, or from the information on the payee (supplier) of the order data included in the standard transaction data. may be obtained. As information on other suppliers, for example, "Previous supplier: Company B.") is displayed. This prompts the user to improve cash flow (C/F) at the stage of inputting new transaction data. Specific examples include changing the supplier, negotiating to extend the payment site to the supplier (specifically, postponement of the scheduled payment date), shortening the collection site to the order supplier (specifically, , early payment) can be considered. Then, the process proceeds to step S210.

In step S210 after the error information is output, it is determined whether or not the transaction data has been updated. Specifically, it is determined whether or not the input items have been changed in either the order data or the order data input by the user in steps S205 and S206. If the transaction data has been updated (Yes in step S210), the process returns to step S205 to acquire the difference information again. On the other hand, if the transaction data is not updated, for example, if the cash flow is acceptable to the user (No in step S210), this process is completed.

Here, a specific example of the flow of processing in FIG. 2 will be described with reference to the drawings.

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

A second specific example is when new transaction data such as shown in FIG. 10 (data different from the new transaction data shown in FIG. 4) is input as new transaction data (steps S203 to S205). To acquire the payment site difference information, the payment site "90 days" of the reference transaction data and the payment site "60 days" of the new transaction data shown in FIG. 10 are compared. As a result, "-30 days" is obtained as the payment site difference information. This indicates that the payment site for the new transaction data is shortened compared to the payment site for the reference transaction data, and therefore cash flow (C/F) is expected to deteriorate. This is the result of calculating the interest rate and net gross profit for the standard transaction data (see FIG. 8) and the result of calculating the interest rate and net gross profit for the new transaction data shown in FIG. 10 (see FIG. 11). becomes clearer by comparing Therefore, error information output processing (steps S208 to S211) is executed.

A third specific example is when new transaction data such as shown in FIG. 12 (data different from the new transaction data shown in FIGS. 4 and 10) is input as new transaction data (steps S203 to S203). S205). To obtain the payment site difference information, the payment site "90 days" of the reference transaction data and the payment site "60 days" of the new transaction data shown in FIG. 12 are compared. As a result, "-30 days" is obtained as the payment site difference information. This indicates that the payment site for the new transaction data is shortened compared to the payment site for the reference transaction data, and therefore cash flow (C/F) is expected to deteriorate. This is the result of calculating the interest rate and net gross profit for the standard transaction data (see FIG. 8) and the result of calculating the interest rate and net gross profit for the new transaction data shown in FIG. 12 (see FIG. 13). becomes clearer by comparing Further, when the payee "Company B" of the reference transaction data and the payee "Company C" of the new transaction data shown in FIG. 12 are compared, it can be seen that they are different. Therefore, in the error information output process, in step S211, "Company B" of the reference transaction data is presented as another payee (place of order). As a result, the user can place an order to company B in 90 days rather than having the payment site place an order to company C in 60 days, or pay to company C for a longer period than to company B's payment site. By negotiating to become a site, it is possible to grasp that deterioration of cash flow can be prevented.

As explained in detail above, according to the processing procedure of the transaction management method shown in FIG. comparing new transaction data with reference transaction data that is a preset reference for the same product as the certain product, and comparing the new transaction data to the reference transaction data at the time of inputting the new transaction data, or Generating difference information about the size relationship (step S206) (difference information generating means). As a result, the user can obtain information about cash flow from the transaction management device 100 without any trouble at the time of new transaction. As a result, the user can consider whether or not to change the new transaction based on the information on the cash flow.

Here, the difference information indicates the difference or size of the payment site indicating the period obtained by subtracting the scheduled purchase date of the product or the sales recording date of the transaction of the product from the scheduled payment date to the ordering party for the ordered product It preferably contains information about relationships. This makes it possible to anticipate whether the cash flow will deteriorate relative to the reference transaction data. Moreover, it is preferable that the difference information includes information about the difference or magnitude relationship of the net gross profit excluding overhead expenses. It is possible to more accurately grasp whether or not the cash flow deteriorates relative to the reference transaction data. Moreover, it is also preferable that the difference information includes information regarding the difference in interest rates per transaction or the magnitude relationship. It is possible to more accurately grasp whether or not the cash flow deteriorates relative to the reference transaction data.

Further, according to the process of FIG. 2, when the difference information is relative deterioration information indicating relative deterioration of cash flow compared to the reference transaction data, error information is output (steps S209, S211) (error information output means). Further, when the difference information is the relative deterioration information, error information including information regarding other suppliers is output. As a result, the user can easily obtain information about the deterioration of cash flow relative to the reference transaction data at the time of new transaction. As a result, users can consider changing new transactions based on information about cash flow.

Furthermore, according to the process of FIG. 2, the reference transaction data can be changed by selecting the check classification in the check classification master. Here, the reference transaction data may be 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. However, it may be transaction data set by default. Since the standard transaction data can be changed in this way, it is possible to set the standard transaction data according to the transaction status. Note that one reference transaction data may be set without setting check categories in the check category master.

In the above description, the transaction data is composed of a pair of order data and order data. However, the order data and order data may be integrated. Also, the order data may be divided into a plurality of pieces, and order data in which a different supplier is set may be associated with each piece of order data.

In addition, in the above explanation, it is assumed that new transaction data is input according to actual transactions, but it can also be applied to simulations by inputting new transaction data according to virtual transactions. is.

[3. Contribution to the Sustainable Development Goals (SDGs) led by the United Nations]
Since this embodiment can contribute to improving operational efficiency and promoting appropriate management decisions of companies, it is possible to contribute to Goals 8 and 9 of the SDGs.

In addition, the present embodiment can contribute to the reduction of disposal loss and the promotion of paperless and computerization.

In addition, since this embodiment can contribute to strengthening control and governance, it is possible to contribute to Goal 16 of the SDGs.

[4. Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Alternatively, some can be done automatically by known methods.

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

Further, regarding the transaction management device 100 and the transaction management system 1000, each illustrated component is functionally conceptual, and does not necessarily need to be physically configured as illustrated.

For example, the processing functions of the transaction management apparatus 100, particularly the processing functions performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, it may be implemented as hardware by wired logic. The program is recorded in a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in the present embodiment, and the transaction management device as necessary. 100 mechanically read. That is, a storage unit such as a ROM or HDD (Hard Disk Drive) stores a computer program for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM and constitutes a control section in cooperation with the CPU.

In addition, this computer program may be stored in an application program server connected to transaction management apparatus 100 via any network (for example, network 300), and may be downloaded in whole or in part as necessary. It is also possible to

Also, the program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" refers to memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered (trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), DVD (Digital Versatile Disk), and Disc (registered trademark) such as Blu- shall include any "portable physical medium". Therefore, a recording medium storing a program for executing the processing described in this specification also constitutes the present invention.

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single structure, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. It should be noted that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiments, the installation procedure after reading, and the like.

The various databases stored in the storage 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. programs, tables, databases, and files for web pages.

Further, transaction management apparatus 100 may be configured as an information processing apparatus such as a known personal computer or workstation, or may be configured as the information processing apparatus to which arbitrary peripheral devices are connected. Further, transaction management device 100 may be implemented by installing software (including programs, data, etc.) that causes the device to implement the processes described herein.

Furthermore, the specific forms of distribution and integration of devices are not limited to those shown in the figures, and all or part of them can be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be selectively implemented.

INDUSTRIAL APPLICABILITY The present invention is useful when managing a transaction (for example, a trading company or a wholesaler) in which ordered products are ordered and delivered.

100 transaction management device 102 control unit 102a difference information generation unit 102b error information output unit 104 communication interface unit 106 storage unit 106a check classification master 106b transaction data storage area 106c difference information storage area 106d error information storage area 108 input/output interface unit 112 input Device 114 Output device 200 Server 300 Network 1000 Transaction management system

Claims (11)

A transaction management device equipped with a control unit for managing the transaction of ordering and delivering ordered products,
The control unit
By comparing new transaction data entered for a certain product with reference transaction data, which is a preset reference for the same product as the certain product, the new transaction data at the time of input of the new transaction data 1. A transaction management apparatus comprising difference information generating means for generating difference information relating to a difference or magnitude relationship with respect to reference transaction data. The difference information is
Including information on the difference or size relationship of the payment site indicating the period after subtracting the scheduled purchase date of the product or the sales recording date of the transaction of the product from the scheduled payment date to the ordering party for the ordered product,
The transaction management device according to claim 1, characterized by: The difference information is
including information on the difference or magnitude of net gross profit excluding overhead costs;
3. The transaction management device according to claim 1 or 2, characterized in that: The difference information is
Including information about the difference or magnitude relationship of the interest rate per transaction,
The transaction management device according to any one of claims 1 to 3, characterized in that: The control unit
1, further comprising error information output means for outputting error information when the difference information is relative deterioration information indicating relative deterioration of cash flow compared to the reference transaction data. 5. The transaction management device according to any one of 4. The error information output means is
6. The transaction management apparatus according to claim 5, wherein when said difference information is said relative deterioration information, it outputs error information including information on other suppliers. the reference transaction data,
7. The transaction management device according to any one of claims 1 to 6, wherein the readable transaction data is the most recent transaction data. the reference transaction data,
7. The transaction management device according to any one of claims 1 to 6, wherein said transaction data is transaction data relating to an average transaction calculated based on readable transaction data. the reference transaction data,
7. The transaction management device according to any one of claims 1 to 6, wherein the transaction data are set by default. A transaction management method for managing a transaction of ordering and delivering an ordered product, which is executed in a transaction management device having a control unit, comprising:
Executed in the control unit,
New transaction data entered for a certain product is compared with reference transaction data, which is a preset reference for the same product as the certain product, and the 1. A transaction management method, comprising: a difference information generation step of generating difference information relating to a difference or magnitude relationship with respect to reference transaction data. A transaction management program for managing a transaction of ordering and delivering an ordered product, which is executed in a transaction management device having a control unit,
for execution in the control unit,
By comparing new transaction data entered for a certain product with reference transaction data, which is a preset reference for the same product as the certain product, the new transaction data at the time of input of the new transaction data A transaction management program characterized by comprising a difference information generation step of generating difference information relating to a difference or magnitude relationship with respect to reference transaction data.

Images