Transaction support apparatus and transaction support method

Abstract

To optimize and smooth the price adjustment of a seller and a buyer by realizing both the business secrecy of cost data and the validity check of price calculation.SOLUTION: A server 10 (transaction support device) for supporting price adjustment in a transaction between a seller terminal and a buyer terminal through a network sets a price formula of the transaction by a setting part 12, registers the cost of a commodity handled in the transaction by a cost registration part 13, and calculates the price of the commodity including the cost registered by the cost registration part 13 by referring to the price formula set by the setting part 12 by a commodity price calculation part 21. A propriety determination part 23 compares the price of the commodity calculated by the commodity price calculation part 21 with the price when the same commodity is transacted in the past, and determines the propriety of the transaction based on the comparison result.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to, for example, a transaction assistance device and a transaction assistance method. [Background technology]

[0002] In supply chain pricing arrangements, sellers typically negotiate with buyers to quote prices based on undisclosed manufacturing costs and a desired profit margin.

[0003] In this case, the advantages include a small administrative burden as there is no need to disclose detailed costs, and the possibility of achieving a high profit margin depending on the negotiations. On the other hand, the disadvantage is that when costs suddenly rise, price negotiations must be requested each time, which takes time and effort to prepare, and there is a risk that the increase will not be fully passed on to the customer.

[0004] Furthermore, rising prices have made it necessary to review the prices of various goods, but price review negotiations are a huge burden for both sellers and buyers. Resource prices and the prices of materials made from resources fluctuate frequently, so there are already systems in place that automatically determine prices using price formulas that use the market price of resources as a parameter.

[0005] For example, there is a proposal to apply a price formula to a technology for efficiently managing the entire transaction of merchandise between a plurality of suppliers and a plurality of buyers (Patent Document 1). [Prior art documents] [Patent documents]

[0006] [Patent Document 1] International Publication No. 2021 / 100623 Summary of the Invention [Problem to be solved by the invention]

[0007] Traditionally, it has been possible to introduce price formulas for general-purpose products (mass-produced products) that are produced continuously from the perspective of ongoing transactions, but it is unclear whether this will lead to labor-saving and efficient price negotiations.

[0008] The prices here are different from the prices of resources and materials upstream in the supply chain. In other words, although cost items must take into account the supplier's raw material costs, fuel costs, transportation costs, etc. as parameters, these are essentially the supplier's trade secrets. For this reason, unless cost data is disclosed to the buyer, it will be difficult to calculate prices using price formulas or check the validity of the prices.

[0009] The present invention has been made in light of the above background, and aims to provide a transaction support device and a transaction support method that can achieve both trade confidentiality of cost data and validity checks of price calculations, thereby making it possible to optimize and facilitate price adjustments between sellers and buyers. [Means for solving the problem]

[0010] In order to solve the above-mentioned problems and achieve the above-mentioned objectives, one embodiment of the present invention is a transaction support device that supports price adjustments in transactions between seller terminals and buyer terminals via a network, and is characterized by comprising: a setting unit that sets a price formula for the transaction; a cost registration unit that registers the cost of the product handled in the transaction; a product price calculation unit that calculates the transaction amount based on the cost registered in the cost registration unit by referring to the price formula set in the setting unit; and an appropriateness judgment unit that compares the transaction amount calculated by the product price calculation unit with past transaction amounts and judges whether the transaction is appropriate based on the comparison result.

[0011] Another embodiment of the present invention is a transaction support method for a device that supports price adjustments in transactions between a seller terminal and a buyer terminal via a network, comprising: a setting step of setting a price formula for the transaction and storing it in memory; a cost registration step of registering the cost of the goods handled in the transaction after setting the price formula in the setting step; a transaction amount calculation step of calculating the transaction amount based on the cost registered in the cost registration step by referring to the price formula stored in the memory; and an appropriateness determination step of comparing the transaction amount calculated in the transaction amount calculation step with past transaction amounts and determining whether the transaction is appropriate based on the comparison result. [Effects of the Invention]

[0012] According to the present invention, it is possible to provide a transaction support device and a transaction support method that can achieve both trade confidentiality of cost data and validity checks of price calculations, thereby making it possible to optimize and facilitate price adjustments between sellers and buyers. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram showing the functions of a transaction assistance device according to an embodiment of the present invention. [Figure 2] 1 is a configuration diagram showing a hardware configuration of a transaction assistance device according to an embodiment of the present invention. [Figure 3] 1 is a flowchart illustrating price formula consensus according to one embodiment of the present invention. [Figure 4] 1 is a flowchart illustrating a process for determining a price formula according to one embodiment of the present invention. [Figure 5] FIG. 10 is an illustrative diagram showing an example screen for creating a price formula according to one embodiment of the present invention. [Figure 6] FIG. 10 is an explanatory diagram illustrating another example of a screen for creating a price formula according to an embodiment of the present invention. [Figure 7]FIG. 10 is an explanatory diagram showing another example of a screen for creating a price formula according to one embodiment of the present invention. [Figure 8] FIG. 10 is an explanatory diagram showing another example of a screen for creating a price formula according to one embodiment of the present invention. [Figure 9] FIG. 10 is an explanatory diagram illustrating another example of a screen for creating a price formula according to an embodiment of the present invention. [Figure 10] 10 is a flowchart illustrating a process for registering a formula template according to an embodiment of the present invention. [Figure 11] FIG. 10 is an explanatory diagram showing an example of a registration screen for a formula template according to an embodiment of the present invention. [Figure 12] FIG. 10 is an explanatory diagram showing another example of the registration screen for a calculation formula template according to an embodiment of the present invention. [Figure 13] FIG. 10 is an explanatory diagram illustrating a method of storing information between a calculation formula and a cost according to an embodiment of the present invention. [Figure 14] FIG. 2 is an explanatory diagram illustrating data relationships according to an embodiment of the present invention. [Figure 15] 10 is a flowchart illustrating a price review process according to an embodiment of the present invention. [Figure 16] 10 is a flowchart illustrating a process for cost registration according to an embodiment of the present invention. [Figure 17] FIG. 10 is an explanatory diagram showing an example of a screen related to cost registration according to an embodiment of the present invention. [Figure 18] 1 is a flowchart illustrating a manual price review process according to one embodiment of the present invention. [Figure 19] 1 is a flowchart illustrating a periodic price review process according to one embodiment of the present invention. [Figure 20] 10 is a flowchart illustrating a process related to order placement and receipt according to an embodiment of the present invention. [Figure 21] 10 is a flowchart illustrating a process for price lookup according to an embodiment of the present invention. [Figure 22]FIG. 10 is an explanatory diagram showing an example of a screen relating to a price search according to one embodiment of the present invention. [Figure 23] FIG. 10 is an explanatory diagram illustrating the relationship between a price formula and a coefficient according to an embodiment of the present invention. [Figure 24] FIG. 10 is an explanatory diagram illustrating the relationship between cost items and amounts for each product according to an embodiment of the present invention. [Figure 25] FIG. 10 is an explanatory diagram illustrating the relationship between cost items and amounts for each cost data item according to an embodiment of the present invention. [Figure 26] FIG. 1 is an explanatory diagram illustrating an example of a quotation according to an embodiment of the present invention. [Figure 27] FIG. 10 is an explanatory diagram showing another example of a quotation according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the following description and drawings are merely examples for explaining the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can also be implemented in various other forms. Furthermore, unless otherwise specified, each component may be singular or plural.

[0015] In the following description, identical or similar components may be designated by the same reference numerals, and redundant description may be omitted. Furthermore, in the following description, various types of information may be described using expressions such as "information" and "table," but the various types of information may also be expressed using other data structures. Furthermore, identification information may be expressed using expressions such as "identification information," "identifier," "name," "ID," and "number," but these are interchangeable. Furthermore, in the following description, "database" will be referred to as "DB," and "table" as "TBL."

[0016] First, the configuration will be described with reference to Figures 1 and 2. Figure 1 is a block diagram showing the functions of a transaction support device according to this embodiment, and Figure 2 is a configuration diagram showing the hardware configuration of the transaction support device according to this embodiment.

[0017] In the following explanation, costs refer to expenses incurred between a seller and its second-tier subcontractors, as well as expenses incurred within the seller. Prices refer to the cost of the product traded between the seller and buyer. A price formula is a formula associated with a product that is used to calculate the price. A formula template is a type or pattern of a formula used to generate a price formula.

[0018] The transaction support device (hereinafter referred to as "server") 10 of this embodiment is connected via a network 200 to a seller terminal (for example, seller terminal 40) on the seller's (distributor's) side and a buyer terminal (for example, buyer terminal 60 that executes transactions with seller terminal 40) on the buyer's (purchaser's) side, as shown in Figure 1, and is a system that realizes appropriate price adjustments in transactions at each stage from upstream to downstream in the supply chain.

[0019] 1, the server 10 is functionally configured with an input unit 11, a setting unit 12, a cost registration unit 13, a memory unit 14, a calculation formula template processing unit 19, a transaction history processing unit 20, a product price calculation unit 21, an anomaly detection unit 22, an appropriateness determination unit 23, an output unit 24, etc. The memory unit 14 is configured with a cost TBL 15 that registers (stores) costs, a price formula TBL 16 that registers (stores) price formulas, a calculation formula template TBL 17 that registers (stores) calculation formula templates, a transaction history DB 18 that registers (stores) invoices and quotations as transaction history, etc.

[0020] The input unit 11 communicates with external terminals such as the seller terminal 40 and the buyer terminal 60 via the network 200 to input information such as data and develop it internally. The setting unit 12 sets price formulas through communication with the seller terminal 40 etc. and registers them in the price formula TBL 16.

[0021] Cost registration unit 13 registers various costs involved in manufacturing a product in cost TBL 15 using invoices or manual operations through communication with seller terminal 40, etc. Calculation formula template processing unit 19 is responsible for processing to set new calculation formula templates and register them in calculation formula template TBL 17 through communication with seller terminal 40, etc., and processing to select a calculation formula template required to determine a price formula for a product from registered calculation formula templates.

[0022] The transaction history processing unit 20 registers invoices and estimates through communication with the seller terminal 40, etc. The product price calculation unit 21 calculates the price of the product to be traded based on the price formula before placing an order for the transaction.

[0023] The abnormality detection unit 22 determines whether the calculated price is appropriate or not by comparing it with past prices of the same product, referring to the transaction history DB 18, as a basis for determining whether the calculated price is appropriate or not, based on whether it is an abnormal value (described later). When the abnormality detection unit 22 detects an abnormality, the appropriateness determination unit 23 outputs the determination result to the output unit 24 and notifies the buyer terminal 60.

[0024] In addition to notifying the above-mentioned abnormality detection, the output unit 24 is responsible for creating the necessary screens and outputting data by referring to the memory unit 14 in procedures through communication with the seller terminal 40 and the buyer terminal 60 according to this embodiment.

[0025] 2, the server 10 of this embodiment is configured with a CPU 101 that controls the entire device, a memory 103 that stores programs 102 such as processes to be executed by the CPU 101 and stores various data during execution, an operation device 104 equipped with a keyboard and display device, an external storage device 105 that registers and stores various data in the form of a DB, TBL, etc., a communication IF 106 that is connected to the network 200 and controls communication with external devices, and a bus 107 that is connected to each unit within the device and controls communication of data, signals, etc. within the device. The seller terminal 40 and the buyer terminal 60 each have input / output units 41 and 61 that display on the screen and perform operation input.

[0026] Next, processing related to price formulas and calculation formula templates will be explained using Figures 3 to 14. Figure 3 is a flowchart explaining consensus building for price formulas according to this embodiment, Figure 4 is a flowchart explaining processing for determining price formulas according to this embodiment, and Figures 5 to 9 are explanatory diagrams showing example screens for creating price formulas according to this embodiment.

[0027] FIG. 10 is a flowchart explaining the process for registering a calculation formula template according to this embodiment, FIG. 11 is an explanatory diagram showing an example of a calculation formula template registration screen according to this embodiment, FIG. 12 is an explanatory diagram showing another example of a calculation formula template registration screen according to this embodiment, FIG. 13 is an explanatory diagram explaining a storage method between calculation formulas and costs according to this embodiment, and FIG. 14 is an explanatory diagram explaining data relationships according to this embodiment.

[0028] The procedure for introducing a price formula is carried out, for example, according to the process flow shown in Figure 3. First, a price formula (proposal) is determined by seller terminal 40 (step S32), and then seller terminal 40 and buyer terminal 60 discuss and reach an agreement on the price formula (proposal) (step S322).

[0029] Then, when the agreed-upon price formula is registered in the price formula TBL16 of the server 10 by the seller terminal 40 (step S322), a notification of the registration is sent from the server 10 to the buyer terminal 60, and the price formula is finalized when the buyer terminal 60 performs an approval operation (step S311).

[0030] The details of the registration of the price formula in step S323 above are shown in Fig. 4. Seller terminal 40, which acts as a client to server 10, first accesses server 10 (step S411), and when a screen for the procedure to search for a calculation formula template is received from server 10, the screen shown in Fig. 5 is displayed on input / output unit 41 of seller terminal 40.

[0031] First, you need to enter information about the product for which you are creating a price formula, as shown in Figure 5. Specifically, the product category and cost items (major category, medium category, minor category, and cost item name) are displayed so that you can select them using a pull-down menu.

[0032] As shown in Figure 13(B), cost items are assigned IDs, and data is linked to them in the following manner: cost item name indicating whether it is a material cost or labor cost, major category indicating whether it is a procured item or value-added, medium category indicating whether it is an item available on the general market or original, and minor category indicating whether it is a component or part, raw material, or assembled or processed product. For example, the cost item ID "C3301" is linked to the cost item name "Electronic Parts," major category "Procured Items," medium category "Non-Market Goods," and minor category "Components and Parts."

[0033] When the seller user inputs the product category and cost items on the seller terminal 40 (step S4112), the server 10 accepts the input operation, references the calculation formula template TBL17, and searches for the corresponding calculation formula template from the previously registered data (step S432).

[0034] The search results are sent from the server 10 to the seller terminal 40 (step S433) and displayed on the input / output unit 41 (step S413), for example, as shown in Figure 6. In the example of Figure 6, only two calculation formula templates are displayed as search results. Selection is made by checking the use column.

[0035] The calculation formula shown in the calculation formula template is used by substituting the costs stored in the cost registration described below. In the example of No. 1, the calculation formula is parts / component cost x (1 + commission rate) + assembly labor cost x (1 + profit rate).

[0036] In this way, by selecting an available calculation formula template (step S414), seller terminal 40 can proceed to the procedure for setting a price formula from step S415 onwards. If there is no desired calculation formula template to use, the process proceeds to the flowchart in Figure 10.

[0037] When a calculation formula template is selected, that template becomes a candidate for the price formula, and each coefficient is also displayed, as shown in Figure 7. A seller user operating seller terminal 40 can provisionally register a price formula by operating the "provisional registration" button.

[0038] If the "End" button is pressed here without provisional registration, the price formula registration process ends, and if the "Back" button is pressed, the operation screen returns to the state shown in FIG.

[0039] As shown in Figure 7, reference values ​​are displayed for each coefficient for commissions and profit margins, indicating that they all meet the standard range. Ideally, the "calculation formula" and "coefficients" for a price formula should be determined based on the actual cost structure and pricing strategy. However, since not all small and medium-sized enterprises can easily create calculation formulas and coefficients, it is ultimately up to the seller to set them, but it would also be good to have the system display reference values.

[0040] One method of calculation is to use the least squares method, and the calculation is performed using actual past sales prices and cost data at that time. It is also possible to perform the calculation like a simulation using hypothetical cost data and desired prices, rather than just actual past data. Furthermore, there are cases where actual past sales prices and cost data at that time cannot be prepared. Therefore, it is possible to use the same coefficients in the same calculation template, and the average or median of the same coefficients can also be used. In this case, there is also the convenience of not having to prepare actual sales prices in the past or cost data at that time.

[0041] The standard range is set by statistically treating the same coefficients of the same calculation template. For example, a coefficient may be considered to meet the standard if it is within a range of 30% above or below the median (within 60% of the total).

[0042] To summarize the above, in step S415, if assistance is required for each coefficient, the server 10 will provide reference values. If an operation indicating that assistance is required is not performed on the seller terminal 40 (NO route in step S415), the process ends. On the other hand, if an operation indicating that assistance is required is performed (YES route in step S415), first, a calculation formula template to be used is selected, and the assisted calculation of the coefficients is performed (step S416).

[0043] 6, if the seller user has already considered the coefficient and wishes to input it directly, the "Register Coefficient" button is operated, the details of which are omitted. On the other hand, if the seller user wishes to consider the coefficient with the assistance of the server 10, the "Consider Coefficient" button is operated.

[0044] In this way, when the "Consider Coefficient" button is operated, the server 10 transmits a screen showing a registration field for the product price and cost data to the seller terminal 40 (step S434), and the registration field is displayed on the seller terminal 40 as shown in FIG. 9, and the product price and cost data are input (step S417). In the example of FIG. 9, past transaction dates (year and month), product prices, parts and component costs, and assembly labor costs can be input.

[0045] Once the input is complete, the server 10 calculates the reference coefficient value (step S435) and reads the standard range from the calculation formula template TBL17 (step S436).Then, the evaluation results of the reference coefficient value and standard range and the price formula registration field are sent to the seller terminal 40 (step S437).

[0046] 7, the seller terminal 40 displays the reference values ​​of the commission and profit margin coefficients along with the price formula, and also displays the evaluation result of the reference range (here, OK) (step S418). If an operation is performed indicating that the reference coefficient values ​​need to be reviewed (YES route in step S419), the process returns to step S416, and the same process is repeated.

[0047] If no review is required and the registration operation is performed (NO route in step S419), the screen in Fig. 8 is sent to seller terminal 40 for confirmation, and the price formula is registered in accordance with the registration instruction (step S420). At that time, server 10 registers (stores) the price formula in price formula TBL 16 in accordance with the operation of seller terminal 40 (step S438).

[0048] When this registration is completed, a price formula save completion screen is sent from the server 10 to the seller terminal 40 (step S439) and is displayed on the input / output unit 41 (step S421). If the end operation is performed, this process ends.

[0049] Here, we will also explain the case where a new calculation formula template is registered. Here, since a buyer may become a seller at a downstream level (stage) in the supply chain, the client in Figure 10 is not only seller terminal 40, but also buyer terminal 60, which executes the same process.

[0050] In registering a calculation formula template, the client accesses the server 10 to start the process (step S1111), and the server 10 sends the calculation formula template registration field to the client (step S1121). As shown in Fig. 11, the calculation formula template registration screen displays items to be entered or selected by pull-down menu, such as product unit price, applicable product category, and cost item (major category, medium category, minor category, cost item name).

[0051] Cost items can be added by operating the add button. In addition, by operating the back button, the process may return to the process of Fig. 4 and end, or the process may return to step S414.

[0052] When the client completes input and selection in the registration fields and operates the "Next" button, the completed data is sent to the server 10 (step S1112). The server 10 checks the input content (step S1122), and if there is an error or omission in registration, it determines that there is a problem (YES route in step S1123), and sends a failure screen for the calculation formula template to the client (step S1125). In this case, the client considers it unsaved, returns to step S1112, and the same process is repeated.

[0053] On the other hand, if it is determined that there is no problem with the registration (NO route in step S1123), the new formula template is registered (stored) in formula template TBL 17 (step S1124). In this case, a screen indicating that the formula template has been saved is sent to the client (step S1125), and the client concludes that saving has been completed and ends the process (step S1113).

[0054] When registering the new calculation formula template, a process of uploading a file containing product unit prices and cost items prepared in advance by dragging and dropping may be applied, as shown in FIG.

[0055] The calculation formula template to be registered is then registered in the calculation formula template TBL17, as shown in Figure 13(A). That is, an ID is assigned to each calculation formula, and the details of the calculation formula and the applicable product category (assembly products, metal products, etc.) are linked and registered. For example, the calculation formula ID "F1101" is linked to the calculation formula "component cost x (1 + commission rate) + assembly labor cost x (1 + profit rate)" and the applicable product category "assembly products."

[0056] Furthermore, the calculation formula template TBL17 registers the association between the calculation formula ID and the cost item ID, as shown in Fig. 13(C). For example, the calculation formula ID "F1101" is associated with the cost item ID "C3301." When the overall association relationship is organized in this way, the storage unit 14 registers the calculation formula, applicable product category, cost item ID, cost item name, major category, medium category, and minor category, associated with the calculation formula ID, according to the correspondence relationships shown in Figs. 13(A), (B), and (C), as shown in Fig. 14.

[0057] Next, price review will be explained using Figures 15 to 19. Figure 15 is a flowchart explaining the price review process according to this embodiment, Figure 16 is a flowchart explaining the cost registration process according to this embodiment, Figure 17 is an explanatory diagram showing an example of a screen related to cost registration according to this embodiment, Figure 18 is a flowchart explaining the manual price review process according to this embodiment, and Figure 19 is a flowchart explaining the periodic price review process according to this embodiment.

[0058] In Figure 15, it is assumed that the client, as a seller, orders raw materials, components, parts, etc. from a second-tier subcontractor. Therefore, it is assumed that the seller and the second-tier subcontractor exchange cost data online using terminals (network 200) or offline without using terminals.

[0059] In the online case, as shown in Fig. 15, cost data is submitted from the secondary subcontractor terminal to seller terminal 40 (step S1521). Seller terminal 40 registers the submitted cost data in transaction history DB 18 (step S1511), and determines whether a price review is required immediately (step S1512).

[0060] If a price review is required immediately (YES route in step S1512), a price review calculation is performed manually (step S1513). On the other hand, if a price review calculation is not required immediately (NO route in step S1512), a price review calculation is performed periodically by the server 10 (step S1531). This periodic review is preferably performed monthly, quarterly, by first and second half of the year, or by fiscal year, but is not limited to these.

[0061] The cost registration in step S1511 will be described in detail with reference to Fig. 16. Seller terminal 40 accesses server 10 for cost registration (step S1611), and in response to this access, server 10 generates a cost data registration screen and transmits it to seller terminal 40 (step S1621).

[0062] As a result, a cost data registration screen is displayed on the input / output unit 41 of the seller terminal 40, and furthermore, cost data entry and uploading of invoices and estimates are executed (step S1612). Figure 17 shows the cost data registration screen. The registered contents are linked to cost items and include the date of transaction, amount, estimate / invoice classification, and evidence. Although items other than evidence can be set by manual input, it is also possible to enter cost items, transaction date, and amount by uploading an actual estimate or invoice by operating the reference button.

[0063] When the setting on the cost data registration screen is completed in step S1612 (by operating the "Next" button), the cost data is transmitted to server 10 and registered (stored) in transaction history DB 18 (step S1622). Then, server 10 transmits the registration result to seller terminal 40 (step S1623), and seller terminal 40 displays the registration result on input / output unit 41 (step S1613).

[0064] Here, we will explain how to determine abnormal values. The abnormality check for product price and cost data is a function to ensure safety and security for the price formula on the buyer's side and to detect possible fraud on the seller's side.

[0065] It is necessary to check whether the rate of price increase is statistically unnatural for the products that are the subject of the price formula (= the products procured by the buyer) and the products procured from the seller's primary supplier (= cost data).

[0066] Please note that even if the price increase rate is determined to be abnormal using the logic below, it does not necessarily indicate any wrongdoing on the part of the seller or primary supplier, and appropriate communication from the seller to the buyer is required.

[0067] Therefore, a plurality of criteria may be set for determining whether a value is abnormal, as follows. (1) The price increase rate of the procured product in question is outside the standard range (e.g., 80% above and below the median) of the frequency distribution of the price increase rates of all products. (2) The price increase rate of the procured product in question is outside the standard range (e.g., 80% above and below the median) of the frequency distribution of the price increase rates of similar products. (3) When the price increase rate of the primary procurement item (= cost data) of the relevant procurement item falls outside the standard range for the frequency distribution of the price increase rates of all products. (4) When the price increase rate of the primary procurement item (= cost data) of the relevant procurement item falls outside the standard range for the frequency distribution of the price increase rates of similar products. Of course, all of the above four methods may be applied, or any one of them, or a combination of two or more of them may be applied. In determining abnormal values, the abnormality detection unit 22 and the suitability determination unit 23 mainly function.

[0068] Next, manual implementation of a price review will be described using the process of Fig. 18. Seller terminal 40 accesses server 10 to implement a manual price review (step S1821), and in response to this access, server 10 transmits a manual instruction screen for price review to seller terminal 40 (step S1831).

[0069] At seller terminal 40, the seller user operates to instruct the execution of a price review calculation (step S1822), and server 10 executes the price review calculation (step S1832). After the calculation is executed, server 10 sends a calculation completion screen to seller terminal 40 (step S1833), and at seller terminal 40, the calculation completion screen is displayed on input / output unit 41 (step S1823).

[0070] On the other hand, server 10 checks for abnormal values ​​(step S1834), and if it determines that the value is abnormal (YES route in step S1835), server 10 sends an alert to buyer terminal 60 instead of seller terminal 40, which is received by buyer terminal 60 and displayed on input / output unit 41 (step S1811). At this time, seller terminal 40 cannot obtain the result of whether the price is abnormal. Also, if it is determined in step S1835 that the value is not abnormal (NO route in step S1835), processing ends immediately (step S1835).

[0071] Furthermore, the periodic price review will be explained using the process in Fig. 19. The example in Fig. 19 shows the operation of a system in which an auxiliary server is newly linked to the server 10. It goes without saying that the functions of the auxiliary server may be provided in the server 10.

[0072] 19, the auxiliary server in charge of the job management function etc. monitors the schedule for the price review timing (step S1921). Then, when it is determined that the time for price review has arrived (YES route in step S1922), the auxiliary server instructs the server 10 to perform a price review calculation (step S1923).

[0073] The server 10 executes a calculation for reviewing the price based on the basis (step S1931), and sends a calculation completion notice to the auxiliary server (step S1932).

[0074] Next, the server 10 checks for abnormal values ​​(step S1933). If it is determined that the price is abnormal (YES route at step S1934), an alert is sent from the server 10 to the buyer terminal 60, which receives the alert and displays it on the input / output unit 41 (step S1911). If it is determined in step S1934 that the price is not abnormal (NO route at step S1934), the process ends (step S1934).

[0075] Next, ordering will be explained using Figure 20. Figure 20 is a flowchart explaining the processing related to ordering according to this embodiment. In ordering between a seller and a buyer, first, the buyer terminal 60 accesses the server 10 to confirm the price (step S2011) and then places an order (step S2012). The seller terminal 40 accepts the order request from the buyer terminal 60 (step S2021).

[0076] A specific example will be described with reference to Figures 21 and 22. Figure 21 is a flowchart illustrating processing related to a price search according to this embodiment, and Figure 22 is an explanatory diagram showing an example of a screen related to a price search according to this embodiment.

[0077] In step S2011 (FIG. 20) described above, the buyer terminal 60 accesses the server 10 to search for a price (step S2111), and the server 10 transmits a price search screen in response to the access (step S2121). The buyer terminal 60 receives the price search screen and displays it on the input / output unit 61, and the buyer inputs product information for which the price is to be searched (step S2112).

[0078] As shown in Figure 22, the price search screen requires the model name of the product for which the price is to be searched, but if the model name is unknown, the supplier name or product name can be entered. The search is executed by pressing the "Next" button. Note that if the "Back" button is pressed, the price search process ends.

[0079] The server 10 executes a price search on the price formula TBL 16 (step S2122), and the search result is sent to the buyer terminal 60 as a registration result (step S2123). Then, the buyer terminal 60 displays the registration result on the input / output unit 61 (step S2113).

[0080] Here, a supplementary explanation will be given on the method of storing various data using Figures 23, 24, and 25. Figure 23 is an explanatory diagram illustrating the relationship between the price formula and coefficients according to this embodiment, Figure 24 is an explanatory diagram illustrating the relationship between cost items and amounts for each product according to this embodiment, and Figure 25 is an explanatory diagram illustrating the relationship between cost items and amounts for each cost data according to this embodiment.

[0081] Regarding coefficients, for example, as shown in Figure 23, the coefficient name of the commission or profit margin, calculation formula ID, price formula ID, and coefficient value are registered in price formula TBL16, linked to the coefficient ID. For example, the coefficient ID "222" is linked to the coefficient name "commission," calculation formula ID "F1111," price formula ID "A11111," and value "1.12." In the example of Figure 23, the coefficient ID, coefficient name, and calculation formula ID are common, and different values ​​are set for different price formula IDs.

[0082] Furthermore, the abnormal value check of the cost data will be explained using Figures 24 and 25. Figure 24 shows the contents of the cost TBL 15, in which the number of price updates, major category, medium category, minor category, cost item name, and amount are registered in association with the product ID.

[0083] Compare the past price of product ID "P1111" with the price after the price update. The past price was 1,000 yen, while the updated price was 1,100 yen, for a difference of 100 yen. In this case, we can see that the increase rate is 10%.

[0084] Also, compare the past price of product ID "P2222" with the price after the price update. The past price was 50,000 yen, while the updated price was 51,000 yen, a difference of 1,000 yen. In this case, we can see that the increase rate is 2.0%.

[0085] Also, compare the past price of product ID "P3333" with the price after the price update. The past price was 2,580 yen, while the updated price was 2,620 yen, a difference of 40 yen. In this case, we can see that the increase rate is 1.6%.

[0086] Also, compare the past price of product ID "P4444" with the price after the price update. The past price was 7,800 yen, while the updated price was 8,100 yen, a difference of 300 yen. In this case, we can see that the increase rate is 3.8%.

[0087] Also, compare the past price of product ID "P5555" with the price after the price update. The past price was 350 yen, while the updated price was 370 yen, a difference of 20 yen. In this case, we can see that the increase rate is 5.7%.

[0088] From the above, when extracting from the same cost item name, the average increase rate is 4.6%, and the median increase rate is 3.8%. By referring to these results and defining how far the increase rate must deviate before it is judged to be an abnormal value, it is possible to achieve appropriate price adjustments.

[0089] Similarly, it is possible to check for abnormal values ​​in cost data from the example in Figure 25. In this case, the same cost items will be extracted and checked. Figure 25 shows the contents of the cost TBL 15, which is linked to the cost data ID and registers the number of registrations, cost item name, major category, medium category, minor category, and amount.

[0090] Compare the past actual price of cost data ID "C1111" with the price after the price update. The past actual price was 1,000 yen, while the updated price was 1,100 yen, for a difference of 100 yen. In this case, we can see that the increase rate is 10%.

[0091] Also, compare the past price of product ID "C2222" with the price after the price update. The past price was 50,000 yen, while the updated price was 51,000 yen, a difference of 1,000 yen. In this case, we can see that the increase rate is 2.0%.

[0092] Also, compare the past price of product ID "C3333" with the price after the price update. The past price was 3,000 yen, while the updated price was 3,100 yen, a difference of 100 yen. In this case, we can see that the increase rate is 3.3%.

[0093] Also, compare the past price of product ID "C4444" with the price after the price update. The past price was 580 yen, while the updated price was 600 yen, a difference of 20 yen. In this case, we can see that the increase rate is 3.4%.

[0094] Also, compare the past price of product ID "C5555" with the price after the price update. The past price was 1,750 yen, while the updated price was 1,820 yen, a difference of 70 yen. In this case, we can see that the increase rate is 4.0%.

[0095] From the above, when extracting from the same cost item name, the average increase rate is 4.6%, and the median increase rate is 3.4%. By referring to these results and defining how far the increase rate must deviate before it is judged to be an abnormal value, it is possible to achieve appropriate price adjustments.

[0096] Next, an estimate will be described using Fig. 26 and Fig. 27. Fig. 26 and Fig. 27 are explanatory diagrams showing estimates according to this embodiment. As an example, when uploading an estimate, the contents that can be registered for costs must be filled in, as shown in Fig. 26 or Fig. 27.

[0097] As explained above, this embodiment makes it possible to balance trade confidentiality of cost data with validity checks of price calculations, thereby optimizing and facilitating price adjustments between sellers and buyers. In particular, by using the price formula as a processing algorithm for automatic price revisions and inputting market prices of raw materials and parts procurement prices that are affected by price fluctuations, it becomes possible to realize the operation of new transaction prices.

[0098] Furthermore, at each stage of transactions between sellers and buyers in the supply chain, since the buyer cannot see the seller's transactions with secondary subcontractors, it is possible to detect abnormalities in price fluctuations from a third-party perspective, making it possible to determine the appropriateness of prices before placing an order.

[0099] In this case, the results of this abnormality detection are not notified to the seller, which is expected to have the effect of preventing illegal collusion between the seller and its secondary subcontractors.

[0100] Furthermore, the actual costs of raw materials and other items are registered through invoices at each transaction stage in the supply chain, making it possible to achieve fair transaction prices without large discrepancies. This also helps to reflect the impact of price fluctuations in prices from an objective perspective, based on actual costs.

[0101] Furthermore, since calculation formula templates are prepared and reflected in the price formula, it becomes possible to create price formulas easily and efficiently. In particular, when continuously trading mass-produced products, it eliminates the need to create calculation formulas from scratch each time, which makes communication between sellers and buyers more efficient.

[0102] Furthermore, the above-described configurations, functional units, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), an IC card, an SD card, a DVD, or other recording media.

[0103] Furthermore, the above-described layout of the various functional units, processing units, and databases of the information collection system 10 is merely an example. The layout of the various functional units, processing units, and databases can be changed to an optimal layout in terms of the performance, processing efficiency, communication efficiency, etc. of the hardware and software provided in these devices.

[0104] Furthermore, the configuration (schema, etc.) of the database that stores the various types of data described above can be flexibly changed from the perspective of efficient use of resources, improved processing efficiency, improved access efficiency, improved search efficiency, and the like. [Explanation of symbols]

[0105] 10 Server (transaction support device) 11 Input section 12 Setting section 13 Cost Registration Department 14 Storage section 15 Cost TBL 16 Price Formula TBL 17 Calculation Formula Template TBL 18 Transaction History DB 19 Calculation formula template processing section 20 Transaction history processing section 21 Product Price Calculation Department 22 Abnormality detection unit 23 Appropriateness Division 24 Output section 40 Seller Terminal 41 Input / output section 60 Buyer Terminal 61 Input / output section 101 CPU 102 Programs 103 memory 104 Operating Devices 105 External storage device 106 Communication Interface 107 Bus 200 Network

Claims

1. A transaction support device that supports price adjustment in a transaction between a seller terminal and a buyer terminal via a network, comprising: a setting unit that sets a price formula for the transaction; a cost registration unit for registering the cost of the product handled in the transaction; a product price calculation unit that calculates the price of a product by referring to the price formula set by the setting unit and including the cost registered by the cost registration unit; an appropriateness determination unit that compares the price of the product calculated by the product price calculation unit with the price of the same product in a previous transaction and determines whether the transaction is appropriate based on the comparison result; A transaction support device comprising:

2. 2. A transaction support system according to claim 1, wherein said setting unit sets said price formula through an agreement procedure between a seller terminal and a buyer terminal via said network.

3. 2. A transaction support device according to claim 1, wherein the goods to be traded are mass-produced goods.

4. 4. A transaction support system according to claim 3, wherein said setting unit sets said price formula for continuous trading of said mass-produced product.

5. 2. A transaction support system according to claim 1, wherein said price adjustment is carried out at each transaction stage in a supply chain.

6. 2. A transaction support device according to claim 1, wherein said appropriateness determining unit determines that the transaction is not appropriate when the comparison result deviates by a certain amount or more.

7. 7. A transaction support device according to claim 6, further comprising an output unit for providing the buyer terminal with a result of the determination made by said appropriateness determination unit that the transaction is not appropriate.

8. 8. A transaction support device according to claim 7, further comprising an output unit for notifying the seller terminal of a review when the appropriateness determination unit determines that the transaction is not appropriate.

9. 9. A transaction support device according to claim 8, wherein the appropriateness determining unit periodically determines whether the transaction is appropriate.

10. 2. A transaction support system according to claim 1, wherein said setting unit sets a price formula using one or more pre-prepared calculation formula templates.

11. 11. A transaction support device according to claim 10, wherein said product price calculation unit takes into account manufacturing costs when calculating the price of said product.

12. 11. A transaction support device according to claim 10, wherein said product price calculation unit uses a weighting coefficient when calculating the price of said product.

13. 2. A transaction support system according to claim 1, wherein said setting unit assists in setting a price formula using a previously prepared standard.

14. 2. A transaction support device according to claim 1, wherein said setting unit sets a price formula for each product to be traded.

15. A transaction support method for a device that supports price adjustment in a transaction between a seller terminal and a buyer terminal via a network, comprising: a setting step of setting a price formula for the transaction and storing it in memory; a cost registration step of registering the cost of the product handled in the transaction in the memory; a product price calculation step of calculating the price of the product by referring to the price formula set in the setting step and including the cost registered in the cost registration step; an appropriateness determination step of comparing the price of the product calculated in the product price calculation step with the price of the same product traded in the past and determining whether the transaction is appropriate based on the comparison result; A transaction support method comprising:

Images