Business support apparatus, business support method, and business support program

Abstract

To provide cancellation rate of contracts.SOLUTION: An acquisition unit acquires contract data having the same cancellation timing, for each designated analysis item, from a storage unit which stores contract data including commercial transaction target information that specifies a commercial transaction target to be provided to a client, a predetermined analysis item which is a unit of aggregating the number of contracts, and cancellation timing of the contracts for the commercial transaction target. A detection unit detects, based on the acquired contract data for each analysis item, the number of contracts for each analysis item, which is the number of pieces of the contract data, and detects the number of cancellations for each analysis item, which is the number of pieces of the contract data having the same cancellation timing. A calculation unit calculates, for each analysis item, cancellation rate that indicates a ratio of the number of cancellations with respect to the detected number of contracts. An output control unit controls outputting a cancellation analysis list including the calculated cancellation rate for each analysis item.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a business support device, a business support method, and a business support program.

Background Art

[0002] Patent Document 1 (Japanese Patent Application Laid-Open No. 2023-139067) discloses an information processing apparatus capable of presenting the contract status of an organization based on the content of a contract. In this information processing apparatus, numerical information, contract information, organization information, and the display method of a graph can be selected in an analysis condition specification column on the screen. Further, based on the selected analysis information and display method, the presence or absence of early termination of the contract amount for each business unit is displayed in the analysis result display column on the screen.

[0003] In addition to the contract amount, the numerical information can also include the conclusion date, the number of contracts, the order quantity (of products, etc.). Further, as the condition information, the presence or absence of a damage compensation amount limit, the presence or absence of automatic update, the presence or absence of a non-compete obligation, etc. can be selected. Further, as the organization information, a company, a branch office, a department, a contractor, a business partner, the business type of the business partner, etc. can be selected.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Here, today, there are various contracts for commercial transactions targeting goods or services, but there is also a certain degree of contract termination. By calculating the termination rate of this termination, it can be used, for example, in subsequent product development and business strategies.

[0006] The present invention has been made in view of the above problems, and an object thereof is to provide a business support device, a business support method, and a business support program capable of providing a contract cancellation rate.

Means for Solving the Problems

[0007] In order to solve the above problems and achieve the object, a business support device according to the present invention includes, by contract, business transaction target information for specifying a business transaction target provided to a trading partner, a predetermined analysis item serving as an aggregation unit of the number of contracts, and a contract data including a cancellation timing of a contract for the business transaction target. From a storage unit in which the contract data is stored, an acquisition unit that acquires contract data having the same cancellation timing for each specified analysis item, a detection unit that detects the number of contracts for each analysis item, which is the number of contract data, and also detects the number of cancellations for each analysis item, which is the number of contract data having the same cancellation timing, a calculation unit that calculates a cancellation rate, which is a ratio of the number of cancellations to the detected number of contracts, for each analysis item, and an output control unit that performs output control of a cancellation analysis list including the calculated cancellation rate for each analysis item.

[0008] Further, in order to solve the above problems and achieve the object, a business support method according to the present invention includes an acquisition step in which an acquisition unit acquires contract data having the same cancellation timing for each specified analysis item from a storage unit in which business transaction target information for specifying a business transaction target provided to a trading partner, a predetermined analysis item serving as an aggregation unit of the number of contracts, and a contract data including a cancellation timing of a contract for the business transaction target are stored by contract, a detection step in which a detection unit detects the number of contracts for each analysis item, which is the number of contract data, and also detects the number of cancellations for each analysis item, which is the number of contract data having the same cancellation timing, based on the acquired contract data for each analysis item, a calculation step in which a calculation unit calculates a cancellation rate, which is a ratio of the number of cancellations to the detected number of contracts, for each analysis item, and an output control step in which an output control unit performs output control of a cancellation analysis list including the calculated cancellation rate for each analysis item.

[0009] Also, in order to solve the above-described problems and achieve the object, the business support program according to the present invention causes a computer to, from a storage unit storing business transaction target information for specifying a business transaction target provided to a business partner by contract, a predetermined analysis item serving as an aggregation unit of the number of contracts, and contract data including a contract cancellation timing for a business transaction target, acquire contract data having the same cancellation timing for each specified analysis item; detect the number of contracts for each analysis item, which is the number of contract data, and detect the number of cancellations for each analysis item, which is the number of contract data having the same cancellation timing, based on the contract data for each acquired analysis item; calculate a cancellation rate, which is a ratio of the number of cancellations to the number of detected contracts, for each analysis item; and function as an output control unit that outputs and controls a cancellation analysis list including the calculated cancellation rate for each analysis item.

Effect of the Invention

[0010] The present invention can provide a contract cancellation rate.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, a business support device according to an embodiment to which the present invention is applied will be described in detail with reference to the drawings. The business support device according to this embodiment is an example in which the present invention is applied to a business support device of a company that sells products such as electronic bulletin boards, posters, and carts to customers. Note that the present invention is also applicable to, for example, a business support device of a company that provides a predetermined service instead of a product, and is not limited to the following embodiments.

[0013] (Hardware Configuration) As shown in FIG. 1, the business support device 1 of the embodiment includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. As the output device 7, a display unit such as a monitor device (including a home TV), a printing device, or a speaker device corresponds. As the input device 6, in addition to a keyboard device, a mouse device, and a microphone device, a monitor device that realizes a pointing device function in cooperation with the mouse device can be used. The communication interface unit 4 is connected to a network such as a wide area network such as the Internet or a private network such as a LAN (Local Area Network).

[0014] As the storage unit 2, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), an HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be used. The storage unit 2 stores a business support program that enables providing, for example, the contract cancellation rate, etc. In addition, in this storage unit 2, a product master table 11, a customer master table 12, a department master table 13, a contract basic data table 14, a contract sales detail data table 15, a contract sales detailed data table 16, and a cancellation analysis list storage unit 17, which are storage areas, are provided respectively.

[0015] As shown in FIG. 2, the product master table 11 stores product data including the product code, product name, product category, location category, and location category (detail) of each product sold to each customer. In the case of this example, a product with the product name "Digital Signage A" whose product category is "Electronic Bulletin Device" indicates that it is installed at the "First Terminal" of the "Airport". Also, a product with the product name "Poster A" whose product category is "Poster" indicates that it is installed at "○○ Station" of the "Station (Ginza Line)". Also, a product with the product name "Cart A" whose product category is "Handcart" indicates that it is installed at the "First Terminal" of the "Airport".

[0016] As shown in FIG. 3, the customer master table 12 stores customer data including the customer code, customer name, address, telephone number, business type, etc. of each customer with whom a commodity sales contract has been made. In the case of this example, “Company ○○” with the customer code “T0001” has an address in Chiba Prefecture and a business type of “retail business”. Also, in the case of this example, “○○ Shosha Co., Ltd.” with the customer code “T0002” has an address in Tokyo and a business type of “construction business”. Also, in the case of this example, “×× Bank, Ltd.” with the customer code “T0003” has an address in Tokyo and a business type of “financial business”.

[0017] As shown in FIG. 4, the department master table 13 stores department data indicating the departments (and sections) of the company that owns the business support apparatus 1 of the embodiment, which has made contracts with each customer. Specifically, in the example of FIG. 4, it shows that the department code of the “Kanto Department” with the section of “System 1 Section” is “B0001”, and the department code of the “Kanto Department” with the section of “System 2 Section” is “B0002”. Also, it shows that the department code of the “Kansai Department” with the section of “Kansai System 1 Section” is “B0003”.

[0018] As shown in FIG. 5(a), the contract basic data table 14 stores contract basic data including the responsible department code, customer code, customer name, contract period, contract cancellation classification, and contract cancellation month, associated with a unique contract number. The example of FIG. 5(a) shows that the customer code of “Company ○○” as the customer name is “T0001”, the System 1 Section of the Kanto Department with the responsible department code of “B0001” is in charge of the contract, and the contract period is from October 1, 2023 to March 31, 2024.

[0019] In the contract sales details data table 15, as shown in Fig. 5(b), contract sales details data including detail number (line number), product name, detail period, sales form, billing form, principal amount, consumption tax amount, and tax-included amount are stored in association with the above-mentioned unique contract number. The example in Fig. 5(b) shows that the product with contract number "PJ0001" and detail number "1" is a product named "Digital Signage A", and its contract period (detail period) is from "October 1, 2023 to March 31, 2024". Also, the example in Fig. 5(b) shows that the tax-included amount of this product is "1.98 million yen", the billing form is the "lump-sum start month" billing form where billing is done in a lump sum at the start month, and the sales form is the "monthly" sales form where the sales amount (tax-included amount) is equally divided over the contract period and recorded as sales every month.

[0020] In the contract sales detailed data table 16, as shown in Fig. 5(c), contract sales detailed data including detail number (line number), detailed number (detailed line number), sales month, principal amount, consumption tax amount, tax-included amount, sales completed status, and contract cancellation status are stored in association with the above-mentioned unique contract number. The example in Fig. 5(c) shows the monthly sales amounts during the contract period for the product "Digital Signage A" with contract number "PJ0001".

[0021] Specifically, in this example, for the period from "October 1, 2023 to March 31, 2024" which is a total of 6 months, the customer (contract party) has a contract to pay a principal amount of "1.8 million yen", a consumption tax amount of "180,000 yen", and a tax-included amount of "1.98 million yen". Therefore, as shown in Fig. 5(b), for the 6-month period from "October 1, 2023 to March 31, 2024", payments of a principal amount of "300,000 yen", a consumption tax amount of "30,000 yen", and a tax-included amount of "330,000 yen" are made every month.

[0022] Also, the example in Fig. 5(c) shows that, as indicated by the "sales completed status", payments for a total of 4 months from "October 2023 to April 2024" have been made (completed), while payments for a total of 2 months in "February 2024 and March 2024" have not been made (uncompleted).

[0023] (Functional Configuration of Business Support Device) Next, by executing the business support program stored in the storage unit 2, the control unit 3 functions as an acquisition unit 21, a calculation unit 22, a data generation unit 23, an output control unit 24, and a detection unit 25 as shown in FIG. 1.

[0024] As described above, in the storage unit (contract basic data table 14 to contract sales details data table 16), contract data (contract basic data, contract sales details data, and contract sales details data) including business transaction target information (products such as electronic bulletin boards: refer to FIG. 2) that identifies the business transaction target provided to the business partner by the contract, predetermined analysis items (business partner, department, product, etc.) that are the aggregation units of the contract quantity, and the contract cancellation timing for the business transaction target is stored. The acquisition unit 21 acquires the contract data with the same cancellation timing for each designated analysis item from this storage unit.

[0025] Based on the contract data for each analysis item acquired, the detection unit 25 detects the contract quantity (total number of cases such as in FIG. 11) for each analysis item, which is the number of contract data, and also detects the cancellation quantity (total cancellation number such as in FIG. 11) for each analysis item, which is the number of contract data with the same cancellation timing.

[0026] The calculation unit 22 calculates the cancellation rate, which is the ratio of the cancellation quantity to the detected contract quantity, for each analysis item ((cancellation quantity ÷ contract quantity) × 100). The output control unit 24 controls the output of the cancellation analysis list including the calculated cancellation rate for each analysis item to an external device (monitor device, printing device, or speaker device) such as the output device 7, an external storage device, a server device on the network, or the storage unit 2.

[0027] In addition, the contract data includes the contract amount for each business partner (tax-included amount in FIG. 6(b), tax-included amount for each month in FIG. 6(c)) based on the contract of the business transaction target. The calculation unit 22 calculates the unearned principal amount at the time of cancellation (the amount when the contract cancellation classification in FIG. 6 is "1 (cancellation)"), which is the contract amount corresponding from the cancellation timing to the contract expiration timing, for each analysis item. The output control unit 24 controls the output by including the unearned principal amount at the time of cancellation for each analysis item in the cancellation analysis list (refer to the cancellation analysis list such as in FIG. 11).

[0028] The contract data includes industry information indicating the industry type of each business partner (see Fig. 3). The output control unit 24 performs output control by including the industry information of the business partner for each analysis item in the cancellation analysis list (see Fig. 11, etc.).

[0029] In addition, the contract data includes contract basic data which is data of the contract unit for each business partner (see Fig. 5(a)), and contract sales detail data which is data of the contract sales detail unit for each commercial transaction target (see Fig. 5(b)). When the contract unit is specified, the acquisition unit 21 acquires the contract basic data for each specified analysis item, and when the contract sales detail unit is specified, the acquisition unit 21 acquires the contract sales detail data for each specified analysis item. Then, the output control unit 24 performs output control on a cancellation analysis list including the contract basic data of the specified contract unit (see Fig. 11 or Fig. 17), or a cancellation analysis list including the contract sales detail data of the specified contract sales detail unit (see Fig. 14, Fig. 20, or Fig. 23).

[0030] (Operation of generating cancellation analysis list) Next, the operation of generating the cancellation analysis list in the business support device 1 of the embodiment having such a configuration will be described.

[0031] (Outline of operation) First, when a contract for the product to be sold is concluded with a business partner, as shown in Fig. 5(a), the contract basic data indicating the contract number, the responsible department, the contract partner, the contract period, etc. is input by the operator and stored in the contract basic data table 14 shown in Fig. 1. Also, as shown in Fig. 5(b), the contract sales detail data indicating the contract number, the product name, the detail period (contract period), the sales form, the billing form, the principal amount, the consumption tax amount, and the tax-included amount, etc. is input by the operator and stored in the contract sales detail data table 15 shown in Fig. 1. Furthermore, as shown in Fig. 5(c), the contract sales detailed data including the sales amount (principal amount, consumption tax amount, and tax-included amount) for each month during the contract period of the contracted product, the settled status, and the contract cancellation status, etc. is input by the operator and stored in the contract sales detailed data table 16 shown in Fig. 1.

[0032] Also, during the contract period, the monthly sales amount obtained by dividing the total sales amount of the product by the number of contract months is recorded as shown in FIG. 5(c). Then, for the month in which the sales have been recorded, as shown in FIG. 5(c), the operator inputs the information of "completed" to the completed status section.

[0033] Here, at the beginning of the contract, it was a contract for a total of 6 months from "October 2023 to April 2024", but assume that this contract was terminated in "January 2023" with 2 months remaining. In this case, as shown in FIG. 6(a), the operator inputs the termination month of "January 2024" to the input field for the contract termination month in the contract basic data. Also, the contract termination classification of "1: (termination)" is input to the contract basic data.

[0034] The data generation unit 23 inputs the contract termination classification of "1 (termination)" to the contract sales details data for each month from the month following the input termination month to the contract expiration month, as shown in FIG. 6(c).

[0035] When the contract is terminated in this way, by inputting the contract termination classification of "1 (termination)" and the "contract termination month" to the contract basic data of the corresponding business partner, as shown in FIG. 7, the contract basic data indicating the contract status (contract or termination) for each business partner (and each responsible department) is stored in the contract basic data table 14. Note that the contract sales details data table 15 of the storage unit 2 stores the contract sales details data including the contract period (detail period) and sales amount for each product as shown in FIG. 8. The data generation unit 23 generates a termination analysis list corresponding to the analysis axis (analysis item) and output unit specified by the operator based on such contract basic data and contract sales details data.

[0036] Specifically, in the case of the business support device 1 of the embodiment, as shown in FIG. 9, any one of the analysis axes of "business partner", "department", or "product" can be specified as the analysis axis (analysis item). Also, any one of the output units of "contract unit" or "contract sales details unit" can be specified.

[0037] When the "customer" is specified as the analysis axis, the detection unit 25 detects the industry type of the customer from the customer master table 12 shown in FIG. 3. The data generation unit 23 generates and outputs a cancellation analysis list in which the cancellation rates for each detected industry type are calculated. As a result, an operator or the like can grasp the industries with a high cancellation rate.

[0038] Also, when the "department" is specified as the analysis axis, the detection unit 25 detects the department in charge of the contract from the department master table 13 shown in FIG. 4. The data generation unit 23 generates and outputs a cancellation analysis list with the cancellation rate added for each detected department in charge. As a result, an operator or the like can grasp the departments or regions with a high cancellation rate.

[0039] Furthermore, when the "product" is specified as the analysis axis, the detection unit 25 detects the product classification and location classification of each product from the product master table 11 shown in FIG. 2. The data generation unit 23 generates and outputs a cancellation analysis list with the detected product classification and location classification added. As a result, an operator or the like can grasp the types of products or services with a high cancellation rate.

[0040] Also, when the "contract unit" is specified as the output unit, the detection unit 25 detects the contract basic data that corresponds to the specified analysis axis and has been cancelled from the contract basic data shown in FIG. 7. The data generation unit 23 generates a cancellation analysis list based on the contract basic data that corresponds to the specified analysis axis and has been cancelled. Also, when the "contract sales details unit" is specified as the output unit, the detection unit 25 detects the contract sales details data of the contract that corresponds to the specified analysis axis and has been cancelled from the contract sales details data shown in FIG. 8. The data generation unit 23 generates a cancellation analysis list based on the contract sales details data of the contract that corresponds to the specified analysis axis and has been cancelled.

[0041] (Detailed generation operation of the cancellation analysis list) Next, a detailed generation operation of the cancellation analysis list based on the specified analysis axis and output unit will be described.

[0042] First, when an operator designates the output of a cancellation analysis list, the output control unit 24 displays an extraction condition input screen via the output device 7. FIG. 10 is a diagram showing the main part of this extraction condition input screen. As shown in FIG. 10, the extraction condition input screen is provided with a selection column for the analysis axis and a selection column for the output unit, respectively. As described above, any one of "customer", "department", and "product" can be selected as the analysis axis. Also, as described above, either "contract unit" or "contract sales detail unit" can be selected as the output unit.

[0043] (When the analysis axis = "customer" and the output unit = "contract unit") The example in FIG. 10 is an example in which an operator selects the analysis axis of "customer" and the output unit of "contract unit" via the extraction condition input screen. When the analysis axis of "customer" and the output unit of "contract unit" are selected, the detection unit 25 detects each item from the aggregation conditions shown in FIG. 12(a), the extraction conditions shown in FIG. 12(b), and the transfer source shown in FIG. 12(c) set in the business support program.

[0044] Note that in this example, the detection unit 25 is set to detect the aggregation conditions, extraction conditions, and transfer source set in the business support program. However, the detection unit 25 may detect the aggregation conditions, extraction conditions, and transfer source from the aggregation condition storage unit, extraction condition storage unit, and transfer source storage unit provided in the storage unit 2, respectively. Even in this case, the same effect as the effect described later can be obtained.

[0045] The aggregation conditions shown in FIG. 12(a) are the aggregation conditions referred to when the analysis axis of "customer" and the output unit of "contract unit" are selected, and indicate that the contract basic data is aggregated for each contract number in the contract basic data table 14.

[0046] In addition, the extraction conditions shown in Fig. 12(b) indicate the data to be extracted when the analysis axis of "trading partner" and the output unit of "contract unit" are selected. In this case, it indicates that among the contract basic data of each contract number in the contract basic data table 14, the contract basic data with the contract cancellation classification of "1 (cancellation)" is to be extracted.

[0047] The transfer source shown in Fig. 12(c) indicates the table from which the data to be input to the input fields of each item in the cancellation analysis list is obtained and the data of the items to be obtained (transferred) when the analysis axis of "trading partner" and the output unit of "contract unit" are selected.

[0048] That is, in this case, as shown in Fig. 12(c), the acquisition unit 21 acquires the contract number, responsible department code, contract partner code, contract partner name, contract cancellation classification, and contract cancellation month for each contract of each trading partner from the contract basic data table 14, and the data generation unit 23 inputs them in contract units to the input fields of each item of the contract number, responsible department code, contract partner code, contract partner name, contract cancellation classification, and contract cancellation month of each trading partner in the cancellation analysis list. In addition, the acquisition unit 21 acquires the industry type of each trading partner for each contract from the trading partner master table 12, and the data generation unit 23 inputs them in contract units to the input field of the industry type item in the cancellation analysis list.

[0049] In addition, the acquisition unit 21 acquires the total sales principal amount of the contract basic data table 14 for each contract of each trading partner, and the data generation unit 23 inputs them in contract units to the input fields of the initial total sales principal amount items of each trading partner in the cancellation analysis list. In addition, the acquisition unit 21 and the calculation unit 22 acquire the contract sales detailed data with the contract cancellation classification = 1 (cancellation) from the contract sales detailed data table 16, and calculate the total unsold amount for each contract of each acquisition destination (for each contract number) to calculate the total unsold amount for each contract of each acquisition destination. The data generation unit 23 inputs the calculated total unsold amount of each trading partner in contract units to the input fields of the unsold principal amount items at the time of cancellation of each trading partner in the cancellation analysis list.

[0050] In addition, the data generation unit 23 inputs, for each contract of each business partner in the contract basic data table 14, the total number of contract basic data obtained by the acquisition unit 21 and calculated by the calculation unit 22, into the input fields of the item of the total number of each business partner in the cancellation analysis list, respectively in contract units.

[0051] In addition, the data generation unit 23 inputs, for each contract of each business partner in the contract basic data of the contract cancellation classification = 1 in the contract basic data table 14 obtained by the acquisition unit 21 and calculated by the calculation unit 22, into the input fields of the item of the total number of cancellations of each business partner in the cancellation analysis list, respectively in contract units.

[0052] In addition, the calculation unit calculates the cancellation rate for each contract by the arithmetic formula of the ratio of the total number of cancellations for each contract of each business partner to the total number of each contract of each business partner above ((total number of cancellations ÷ total number of contracts) × 100). The data generation unit 23 inputs the calculated cancellation rate for each contract of each business partner into the input fields of the item of the cancellation rate of each business partner in the cancellation analysis list, respectively in contract units.

[0053] Based on such aggregation conditions (Figure 12(a)), extraction conditions (Figure 12(b)), and transfer source (Figure 12(c)), the cancellation analysis list corresponding to the analysis axis of "business partner" and the output unit of "contract unit" obtained from each table and generated by the data generation unit 23 is displayed (or may be printed, etc.) by the output control unit 24 via the output device 7.

[0054] Figure 11 is an example of a cancellation analysis list generated by selecting the analysis axis of "business partner" and the output unit of "contract unit". As shown in Figure 11, in the cancellation analysis list, for each contract of each business partner, the contract cancellation month, total number of contracts, and total number of cancellations of the contracts that have been cancelled are respectively input and displayed.

[0055] In addition, in this cancellation analysis list, the cancellation rate of each contract of each business partner calculated by the calculation unit 22 using the arithmetic expression of "(total number of cancellations ÷ total number of cases) × 100" is input and displayed respectively. Specifically, the cancellation rate for "January 2024" in "Company ○○" with contract number "PJ0001" is calculated by the calculation unit 22 as "(2 total cancellations ÷ 100 total cases) × 100 = 2%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0056] Similarly, the cancellation rate for "September 2023" in "○○ Shosha" with contract number "PJ0003" is calculated by the calculation unit 22 as "(1 total cancellation ÷ 55 total cases) × 100 = 1.8%", and is input and displayed in the cancellation analysis list by the data generation unit 23. Similarly, the cancellation rate for "October 2023" in "Bank ××" with contract number "PJ0005" is calculated by the calculation unit 22 as "(2 total cancellations ÷ 30 total cases) × 100 = 6.7%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0057] Goods or services with a high number of cancellations often have problems with those goods or services. Therefore, by automatically calculating the analysis rate corresponding to the analysis axis of "business partner" and the output unit of "contract unit" and including it in the cancellation analysis list for output, for example, the cancellation rate can be recognized by dividing it by enterprise scale or area, etc. Thus, potential problems in goods or services can be surfaced, which can also be connected to business improvement and future marketing activities, etc.

[0058] In addition, as shown in Figure 11, in this cancellation list, the amount of the principal of unsold sales at the time of cancellation for each contract of each business partner, which is the amount that becomes unprofitable after the cancellation month, is also input and displayed. Thereby, the amount that becomes unprofitable due to the cancellation of the contract can be recognized for each contract of each business partner and can be utilized for business plans, etc.

[0059] Also, when the analysis axis of "trading partner" and the output unit of "contract unit" are selected, as shown in Fig. 11, a cancellation list including the "industry type" of each trading partner (each contracting party) is output. As a result, the cancellation rate for each industry type can be recognized and utilized for business plans and the like.

[0060] (When the analysis axis = "trading partner" and the output unit = "contract sales details unit") Next, the example in Fig. 13 is an example where the analysis axis of "trading partner" and the output unit of "contract sales details unit" are selected by the operator via the extraction condition input screen. When this analysis axis of "trading partner" and the output unit of "contract sales details unit" are selected, the detection unit 25 detects each item from the aggregation conditions shown in Fig. 15(a), the extraction conditions shown in Fig. 15(b), and the transfer source shown in Fig. 15(c) set in the business support program.

[0061] Note that in this example, the detection unit 25 is set to detect the aggregation conditions, extraction conditions, and transfer source set in the business support program. However, the detection unit 25 may detect the aggregation conditions, extraction conditions, and transfer source from the aggregation condition storage unit, extraction condition storage unit, and transfer source storage unit provided in the storage unit 2, respectively. Even in this case, the same effects as those described later can be obtained.

[0062] The aggregation conditions shown in Fig. 15(a) are the aggregation conditions referred to when the analysis axis of "trading partner" and the output unit of "contract sales details unit" are selected, indicating that the contract basic data is aggregated for each contract number in the contract basic data table 14, and the contract sales details data is aggregated for each detail number (row number) in the contract sales details data table 15.

[0063] Also, the extraction conditions shown in Fig. 15(b) indicate the data to be extracted when the analysis axis of "trading partner" and the output unit of "contract sales details unit" are selected. In this case, it indicates that among the contract basic data of each contract number in the contract basic data table 14, the contract basic data with the contract cancellation classification of "1 (cancelled)" is to be extracted.

[0064] The transfer source shown in Fig. 15(c) indicates the table from which data is acquired for input to the input fields of each item in the cancellation analysis list and the data of the items to be acquired (transferred) when the analysis axis of "trading partner" and the output unit of "contract sales details unit" are selected.

[0065] That is, in this case, as shown in Fig. 15(c), the acquisition unit 21 acquires the contract number, detail number, contract partner code, contract partner name, product code, and product name of each trading partner from the contract sales details data table 15 in units of contract sales details, and the data generation unit 23 inputs them into the input fields of the contract number, detail number, contract partner code, contract partner name, product code, and product name items in the cancellation analysis list in units of contract sales details respectively. Also, the acquisition unit 21 acquires the business type of each trading partner in the trading partner master table 12 in detail units, and the data generation unit 23 inputs them into the input field of the business type item in the cancellation analysis list in units of contract sales details respectively.

[0066] In addition, the acquisition unit 21 acquires the person-in-charge department code of the contract basic data table 14 in units of contract sales details, and the data generation unit 23 inputs it into the input field of the person-in-charge department code item in the cancellation analysis list in units of contract sales details respectively. Also, the acquisition unit 21 acquires the principal amount of each contract sales detail from the contract sales details data table 15. The data generation unit 23 inputs the principal amount acquired from the contract sales details data table 15 into the input field of the initial sales total principal amount item of each contract sales detail in the cancellation analysis list in units of contract sales details respectively.

[0067] In addition, the acquisition unit 21 and the calculation unit 22 acquire the contract sales detail data with the contract cancellation classification = 1 (cancellation) from the contract sales detail data table 16, and calculate the total unsold amount of each trading partner in units of contract sales details. The data generation unit 23 inputs the total unsold amount calculated in units of contract sales details into the input field of the unsold principal amount at the time of cancellation item of each trading partner in the cancellation analysis list in units of contract sales details respectively.

[0068] In addition, the acquisition unit 21 acquires the contract cancellation month of each business partner from the contract basic data table 14 in units of contract sales details, and the data generation unit 23 inputs them into the input fields of the contract cancellation month items of each business partner in the cancellation analysis list, respectively, in units of contract sales details. Further, the data generation unit 23 inputs the total number of contract basic data of each business partner in the contract basic data table 14, which is acquired by the acquisition unit 21 and calculated by the calculation unit 22, into the input fields of the total number of items of each business partner in the cancellation analysis list, respectively, in units of contract sales details.

[0069] In addition, the data generation unit 23 inputs the total number of contract basic data with the contract cancellation classification = 1 (cancellation) in the contract basic data table 14, which is acquired by the acquisition unit 21 and calculated by the calculation unit 22 for each business partner (total cancellation count), into the input fields of the total number of cancellations of each business partner in the cancellation analysis list, respectively, in units of contract sales details.

[0070] In addition, the acquisition unit 21 acquires the total number of items in units of contract sales details and the total number of cancellations in units of contract sales details of each business partner from the contract basic data table 14. The calculation unit 22 calculates the cancellation rate in units of contract sales details for each business partner using the arithmetic formula of the ratio of the total number of cancellations in units of contract sales details to the total number of items in units of sales details for each business partner ((total number of cancellations ÷ total number of items) × 100). The data generation unit 23 inputs the calculated cancellation rates into the input fields of the cancellation rate items of each business partner in the cancellation analysis list, respectively, in units of contract sales details.

[0071] Based on such aggregation conditions (Figure 15(a)), extraction conditions (Figure 15(b)), and transfer source (Figure 15(c)), the cancellation analysis list corresponding to the analysis axis of "business partner" and the output unit of "contract sales details unit", which is acquired from each table and generated by the data generation unit 23, is displayed (or may be printed, etc.) by the output control unit 24 via the output device 7.

[0072] Figure 14 is an example of a cancellation analysis list generated by selecting the analysis axis of "business partner" and the output unit of "contract sales details unit". As shown in Figure 14, in the cancellation analysis list, for each contract number and each detail number (for each detail), the contract cancellation month, the total number of cases, and the total number of cancellations of the contract that has been cancelled are input and displayed.

[0073] In addition, in this cancellation analysis list, the cancellation rate calculated for each contract sales detail of each business partner by the calculation formula of "(total number of cancellations ÷ total number of cases) × 100" by the calculation unit 22 is input and displayed. Specifically, the cancellation rate for "January 2024" in "Company XX" with a contract number of "PJ0001" and a detail number of "1" is calculated by the calculation unit 22 as "(total number of cancellations 2 cases ÷ total number of cases 100 cases) × 100 = 2%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0074] Similarly, the cancellation rate for "September 2023" in "XX Trading Co., Ltd." with a contract number of "PJ0003" and a detail number of "1" is calculated by the calculation unit 22 as "(total number of cancellations 1 case ÷ total number of cases 55 cases) × 100 = 1.8%", and is input and displayed in the cancellation analysis list by the data generation unit 23. Similarly, the cancellation rate for "October 2023" in "XX Bank Co., Ltd." with a contract number of "PJ0005" and a detail number of "1" is calculated by the calculation unit 22 as "(total number of cancellations 2 cases ÷ total number of cases 30 cases) × 100 = 6.7%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0075] Goods or services with a high number of cancellations often have problems with those goods or services. Therefore, by automatically calculating the analysis rate corresponding to the analysis axis of "business partner" and the output unit of "contract sales details unit" and including it in the cancellation analysis list for output, for example, the cancellation rate can be recognized by dividing it into enterprise scale, goods, services, areas, etc. Therefore, the potential problems in goods or services can be surfaced, which can also lead to business improvement and future marketing activities, etc.

[0076] In addition, as shown in FIG. 14, the cancellation list also inputs and displays the amount of unsold principal at the time of cancellation for each contract sales statement of each customer, which is the amount that will not generate revenue after the cancellation month. This allows the amount of revenue that has not been generated due to contract cancellation to be recognized for each contract with each customer, and the issues can be analyzed in more detail and utilized in business plans and the like.

[0077] Also, when the analysis axis of "customer" is selected, as shown in FIG. 14, a cancellation list including the "industry type" of each customer is output. This allows the cancellation rate for each industry type to be recognized and utilized in business plans and the like.

[0078] (When the analysis axis = "department" and the output unit = "contract unit") Next, the example in FIG. 16 is an example where the operator selects the analysis axis of "department" and the output unit of "contract unit" via the extraction condition input screen. When the analysis axis of "department" and the output unit of "contract unit" are selected, the detection unit 25 detects each item from the aggregation conditions shown in FIG. 18(a), the extraction conditions shown in FIG. 18(b), and the transfer source shown in FIG. 18(c) set in the business support program.

[0079] In this example, the detection unit 25 is assumed to detect the aggregation conditions, extraction conditions, and transfer source set in the business support program. However, the detection unit 25 may detect the aggregation conditions, extraction conditions, and transfer source from the aggregation condition storage unit, extraction condition storage unit, and transfer source storage unit provided in the storage unit 2, respectively. Even in this case, the same effect as described later can be obtained.

[0080] The aggregation conditions shown in FIG. 18(a) are the aggregation conditions referred to when the analysis axis of "department" and the output unit of "contract unit" are selected, indicating that the contract basic data is aggregated for each contract number in the contract basic data table 14.

[0081] In addition, the extraction conditions shown in Fig. 18(b) indicate the data to be extracted when the analysis axis of "department" and the output unit of "contract unit" are selected. In this case, it indicates that among the contract basic data of each contract number in the contract basic data table 14, the contract basic data with the contract cancellation classification of "1 (cancellation)" is to be extracted.

[0082] The transfer source shown in Fig. 18(c) indicates the table from which the data to be input to the input fields of each item in the cancellation analysis list is obtained and the data of the items to be obtained (transferred) when the analysis axis of "department" and the output unit of "contract unit" are selected.

[0083] That is, in the case of the example in Fig. 18(c), the acquisition unit 21 acquires the contract number, the responsible department code, the contract partner code, the contract partner name, and the contract cancellation month from the contract basic data table 14 for each contract, and the data generation unit 23 inputs them in contract units to the input fields of the contract number, the responsible department code, the contract partner code, the contract partner name, and the contract cancellation month items in the cancellation analysis list respectively. In addition, the acquisition unit 21 acquires the department responsible for each contract from the department master table 13, and the data generation unit 23 inputs them to the input fields of the department items of each contract in the cancellation analysis list respectively.

[0084] In addition, the acquisition unit 21 acquires the total sales principal amount of the contract basic data table 14 for each contract, and the data generation unit 23 inputs them in contract units to the input field of the initial total sales principal amount item in the cancellation analysis list respectively. In addition, the acquisition unit 21 and the calculation unit 22 acquire the contract sales detailed data with the contract cancellation classification = 1 (cancellation) in the contract sales detailed data table 16 and perform an addition process to calculate the total unsold amount for each contract. The data generation unit 23 inputs the calculated total unsold amounts to the input field of the unsold principal amount at the time of cancellation item in the cancellation analysis list in contract units respectively.

[0085] In addition, the data generation unit 23 inputs the total number of contracts in contract units (in this case, department units) of the contract basic data in the contract basic data table 14 acquired by the acquisition unit 21 and calculated by the calculation unit 22 to the input field of the total number of items item in the cancellation analysis list respectively.

[0086] Also, the data generation unit 23 inputs, for each contract unit, the total number of cancellations of the contract basic data with the contract cancellation classification = 1 in the contract basic data table 14, which is obtained by the acquisition unit 21 and calculated by the calculation unit 22, into the input field of the total cancellation number item in the cancellation analysis list.

[0087] Also, the acquisition unit 21 acquires the total number of cases for each contract (= total number of cases by department) and the total number of cancellations for each contract (= total number of cancellations by department) obtained from the contract basic data table 14. The calculation unit 22 calculates the cancellation rate for each department using the arithmetic expression of the ratio of the total number of cancellations by department to the total number of cases by department ((total number of cancellations ÷ total number of cases) × 100). The data generation unit 23 inputs the calculated cancellation rate for each department into the input field of the cancellation rate item for each department in the cancellation analysis list.

[0088] Based on such aggregation conditions (Fig. 18(a)), extraction conditions (Fig. 18(b)), and transfer source (Fig. 18(c)), the cancellation analysis list corresponding to the analysis axis of "department" and the output unit of "contract unit", which is obtained from each table and generated by the data generation unit 23, is displayed (or may be printed, etc.) by the output control unit 24 via the output device 7.

[0089] Fig. 17 is an example of a cancellation analysis list generated by selecting the analysis axis of "department" and the output unit of "contract unit". As shown in Fig. 17, in the cancellation analysis list, for each contract number (for each contract), the contract cancellation month, total number of cases, and total number of cancellations of each contract destination that has been cancelled are input and displayed.

[0090] Also, in this cancellation analysis list, the cancellation rate for each department calculated for each contract destination by the calculation unit 22 using the arithmetic expression of "(total number of cancellations ÷ total number of cases) × 100" is input and displayed. Specifically, the cancellation rate of the "Kanto department" for the "January 2024" period with the contract number "PJ0001" is calculated by the calculation unit 22 as "(10 cancellations ÷ 100 cases) × 100 = 10%" and input and displayed in the cancellation analysis list by the data generation unit 23.

[0091] Similarly, the cancellation rate for the "Kansai Region" with contract number "PJ0002" in "February 2024" is calculated by the calculation unit 22 as "(1 total cancellation ÷ 20 total cases) × 100 = 5%", and is input and displayed in the cancellation analysis list by the data generation unit 23. Similarly, the cancellation rate for the "Kanto Region" with contract number "PJ0005" in "October 2023" is calculated by the calculation unit 22 as "(1 total cancellation ÷ 50 total cases) × 100 = 2.5%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0092] Goods or services with a high cancellation rate often have problems with those goods or services. Therefore, by automatically calculating the analysis rate corresponding to the analysis axis of "department" and the output unit of "contract unit" and including it in the cancellation analysis list for output, the cancellation rate can be recognized, for example, divided by department, product, service, or area. Thus, potential problems in goods or services can be surfaced and linked to business improvement and future marketing activities, etc.

[0093] Also, as shown in Fig. 17, in this cancellation list, the amount of unsold principal at the time of cancellation for each contract sales detail of each customer, which is the amount that becomes unprofitable after the cancellation month, is also input and displayed. Thereby, the amount that becomes unprofitable due to the cancellation of the contract can be recognized for each department in charge of each customer, and the problem points can be analyzed in more detail and utilized for business plans, etc.

[0094] (When the analysis axis = "department" and the output unit = "contract sales detail unit") Next, the example in Fig. 19 is an example where the analysis axis of "department" and the output unit of "contract sales detail unit" are selected by the operator via the extraction condition input screen. When the analysis axis of "department" and the output unit of "contract sales detail unit" are selected, the detection unit 25 detects each item from the aggregation conditions shown in Fig. 21(a), the extraction conditions shown in Fig. 21(b), and the transfer source shown in Fig. 21(c) set in the business support program.

[0095] In this example, the detection unit 25 is configured to detect the aggregation conditions, extraction conditions, and transfer source set in the business support program. However, the detection unit 25 may detect the aggregation conditions, extraction conditions, and transfer source from the aggregation condition storage unit, extraction condition storage unit, and transfer source storage unit provided in the storage unit 2, respectively. Even in this case, the same effects as those described later can be obtained.

[0096] The aggregation condition shown in FIG. 21(a) is the aggregation condition referred to when the analysis axis of "department" and the output unit of "contract sales detail unit" are selected, and it indicates that the contract basic data is aggregated for each contract number in the contract basic data table 14.

[0097] Also, the extraction condition shown in FIG. 21(b) indicates the data to be extracted when the analysis axis of "department" and the output unit of "contract sales detail unit" are selected. In this case, it indicates that the contract basic data with the contract cancellation classification of "1 (cancelled)" is extracted from the contract basic data of each contract number in the contract basic data table 14.

[0098] The transfer source shown in FIG. 21(c) indicates the table that is the acquisition source of the data to be input to the input fields of each item in the cancellation analysis list and the data of the items to be acquired (transferred) when the analysis axis of "department" and the output unit of "contract sales detail unit" are selected.

[0099] That is, in the case of the example in FIG. 21(c), the acquisition unit 21 acquires the contract number, detail number, contract partner code, contract partner name, product code, and product name from the contract sales detail data table 15 in units of contract sales details, and the data generation unit 23 inputs them to the input fields of the contract number, detail responsible department code, contract partner code, contract partner name, product code, and product name items in the cancellation analysis list in units of contract sales details, respectively.

[0100] In addition, the acquisition unit 21 acquires the responsible department code from the contract basic data table 14 in units of contract sales details, and the data generation unit 23 inputs it into the input field of the responsible department code item of the cancellation analysis list in units of contract sales details. Also, the acquisition unit 21 acquires the department to which the person in charge of each contract sales detail belongs from the department master table 13, and the data generation unit 23 inputs it into the input field of the department item of the cancellation analysis list respectively in units of contract sales details.

[0101] In addition, the acquisition unit 21 acquires the principal amount of the contract sales detail data table 15 in units of departments, and the data generation unit 23 inputs it into the input field of the initial sales total principal amount item of each department of the cancellation analysis list respectively. Also, the acquisition unit 21 and the calculation unit 22 acquire the contract sales detail data with the contract cancellation classification = 1 (cancellation) from the contract sales detail data table 16 and perform an addition process to calculate the total amount of unsold sales in units of contract sales details. The data generation unit 23 inputs each calculated total amount of unsold sales into the input field of the unsold principal amount at the time of cancellation item of the cancellation analysis list respectively in units of contract sales details.

[0102] In addition, the acquisition unit 21 inputs the total number of contract basic data in units of departments in the contract basic data table 14 into the input field of the total number of items of the cancellation analysis list by the data generation unit 23 respectively in units of contract sales details.

[0103] Also, the data generation unit 23 inputs the total number of cancellations in units of contracts of the contract basic data with the contract cancellation classification = 1 in the contract basic data table 14, which is acquired by the acquisition unit 21 and calculated by the calculation unit 22, into the input field of the total number of cancellations item of the cancellation analysis list respectively in units of contract sales details.

[0104] In addition, the acquisition unit 21 acquires the total number of items in units of departments and the total number of cancellations in units of departments acquired from the contract basic data table 14. The calculation unit 22 calculates the cancellation rate for each department using the arithmetic formula of the ratio of the total number of cancellations in units of departments to the total number of items in units of departments ((total number of cancellations ÷ total number of items) × 100). The data generation unit 23 inputs the calculated cancellation rate for each department into the input field of the cancellation rate item of each department of the cancellation analysis list respectively.

[0105] The cancellation analysis list, which is obtained from each table based on such aggregation conditions (Fig. 21(a)), extraction conditions (Fig. 21(b)), and transfer source (Fig. 21(c)) and generated by the data generation unit 23, corresponding to the analysis axis of "department" and the output unit of "contract sales detail unit", is displayed (or may be printed, etc.) by the output control unit 24 via the output device 7.

[0106] Fig. 20 is an example of a cancellation analysis list generated by selecting the analysis axis of "department" and the output unit of "contract sales detail unit. As shown in Fig. 20, in the cancellation analysis list, for each contract number (for each contract sales detail), the department in charge of each customer who has cancelled the contract, the contract cancellation month, the total number of cases, and the total number of cancellations are input and displayed.

[0107] In addition, in this cancellation analysis list, the cancellation rate for each department calculated for each customer by the calculation unit 22 using the arithmetic expression "(total number of cancellations ÷ total number of cases) × 100" is input and displayed. Specifically, the cancellation rate for the "Kanto Department" in the "January 2024" period for contract number "PJ0001" is calculated by the calculation unit 22 as "(total number of cancellations 10 cases ÷ total number of cases 100 cases) × 100 = 10%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0108] Similarly, the cancellation rate for the "Kansai Department" in the "February 2024" period for contract number "PJ0002" is calculated by the calculation unit 22 as "(total number of cancellations 1 case ÷ total number of cases 20 cases) × 100 = 5%", and is input and displayed in the cancellation analysis list by the data generation unit 23. Similarly, the cancellation rate for the "Kanto Department" in the "October 2023" period for contract number "PJ0005" is calculated by the calculation unit 22 as "(total number of cancellations 1 case ÷ total number of cases 50 cases) × 100 = 2.5%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0109] Products or services with a high cancellation rate often have problems. Therefore, by automatically calculating the analysis rate corresponding to the analysis axis of "department" and the output unit of "contract sales details unit" and including it in the cancellation analysis list for output, the cancellation rate can be recognized by dividing it into, for example, departments, products, services, or areas. As a result, potential problems in products or services can be surfaced and linked to business improvement and future marketing activities, etc.

[0110] Also, as shown in Fig. 20, in this cancellation list, the amount of unsold principal at the time of cancellation for each contract sales detail of each customer, which is the amount that becomes unprofitable after the cancellation month, is input and displayed. Thereby, the amount that becomes unprofitable due to the cancellation of the contract can be recognized for each department in charge of each customer, and the problem points can be analyzed in more detail and utilized for business plans, etc.

[0111] (When the analysis axis = "product" and the output unit = "contract sales details unit") Next, the example in Fig. 22 is an example where the analysis axis of "product" and the output unit of "contract sales details unit" are selected by the operator via the extraction condition input screen. When the analysis axis of "product" and the output unit of "contract sales details unit" are selected, the detection unit 25 detects each item from the aggregation conditions shown in Fig. 24(a), the extraction conditions shown in Fig. 24(b), and the transfer source shown in Fig. 24(c) set in the business support program.

[0112] Note that in this example, the detection unit 25 is assumed to detect the aggregation conditions, extraction conditions, and transfer source set in the business support program. However, the detection unit 25 may also detect the aggregation conditions, extraction conditions, and transfer source from the aggregation condition storage unit, extraction condition storage unit, and transfer source storage unit provided in the storage unit 2, respectively. Even in this case, the same effect as the effect described later can be obtained.

[0113] The aggregation conditions shown in FIG. 24(a) are the aggregation conditions referred to when the analysis axis of "product" and the output unit of "contract sales detail unit" are selected, indicating that the contract basic data is aggregated for each contract number and each detail number in the contract sales detail data table 15.

[0114] Also, the extraction conditions shown in FIG. 24(b) indicate the data to be extracted when the analysis axis of "product" and the output unit of "contract sales detail unit" are selected. In this case, it indicates that among the contract basic data of each contract number in the contract basic data table 14, the contract basic data with the contract cancellation classification of "1 (cancellation)" is extracted.

[0115] The transfer source shown in FIG. 24(c) indicates the table from which the data to be input to the input fields of each item in the cancellation analysis list is obtained and the data of the items to be obtained (transferred) when the analysis axis of "product" and the output unit of "contract sales detail unit" are selected.

[0116] That is, in the case of the example in FIG. 24(c), the acquisition unit 21 acquires the contract number, detail number, customer code, customer name, product code, and product name from the contract sales detail data table 15 in units of contract sales details (product units), and the data generation unit 23 inputs them in units of contract sales details (product units) to the input fields of the contract number, detail number, customer code, customer name, product code, and product name items in the cancellation analysis list, respectively.

[0117] Also, the acquisition unit 21 acquires the product classification, location classification, and location classification (details) of each product from the product master table 11, and the data generation unit 23 inputs them in units of contract sales details (product units) to the input fields of the product classification, location classification, and location classification (details) items in the cancellation analysis list, respectively.

[0118] In addition, the acquisition unit 21 acquires the responsible department code from the contract basic data table 14 in units of contract sales details, and the data generation unit 23 inputs it into the input field of the responsible department code item of the cancellation analysis list in units of contract sales details. Also, the acquisition unit 21 acquires the responsible department code for each contract from the contract basic data table 14, and the data generation unit 23 inputs it into the input field of the responsible department code item of the cancellation analysis list in units of contract sales details (product units) respectively.

[0119] In addition, the acquisition unit 21 acquires the principal amount of the contract sales details data table 15 in units of contract sales details (product units), and the data generation unit 23 inputs it into the input field of the initial total sales principal amount item of each contract sales detail of the cancellation analysis list respectively. Also, the acquisition unit 21 and the calculation unit 22 acquire the contract sales details data with the contract cancellation classification = 1 (cancellation) from the contract sales details data table 16 and perform an addition process to calculate the total unsold amount in units of contract sales details. The data generation unit 23 inputs each calculated total unsold amount into the input field of the unsold principal amount at the time of cancellation item of the cancellation analysis list in units of contract sales details (product units) respectively.

[0120] In addition, the acquisition unit 21 acquires the contract cancellation month of each contract from the contract basic data table 14, and the data generation unit 23 inputs the acquired contract cancellation month into the input field of the contract cancellation month item of the cancellation analysis list in units of contract sales details (product units) respectively.

[0121] Also, the acquisition unit 21 acquires the total number of contract units (in this case, product units) of the contract basic data in the contract basic data table 14, and the data generation unit 23 inputs it into the input field of the total number of items item of the cancellation analysis list in units of contract sales details (product units) respectively.

[0122] Also, the data generation unit 23 inputs the total number of cancellation items, which is the total number of contract sales detail items with the contract cancellation classification = 1 in the contract basic data table 14 acquired by the acquisition unit 21 and calculated by the calculation unit 22, into the input field of the total number of cancellations item of the cancellation analysis list in units of contract sales detail contract units (product units) respectively.

[0123] In addition, the acquisition unit 21 acquires the total number of items per product and the total number of cancellations per product. The calculation unit 22 calculates the cancellation rate for each product using the arithmetic formula of the ratio of the total number of cancellations per product to the total number of items per product ((total number of cancellations ÷ total number of items) × 100). The data generation unit 23 inputs the calculated cancellation rate for each product into the input field of the cancellation rate item in the cancellation analysis list in units of contract sales details (product units).

[0124] Based on such aggregation conditions (Fig. 24(a)), extraction conditions (Fig. 24(b)), and transfer source (Fig. 24(c)), the cancellation analysis list corresponding to the analysis axis of "product" and the output unit of "contract sales details unit" obtained from each table and generated by the data generation unit 23 is displayed (or may be printed, etc.) by the output control unit 24 via the output device 7.

[0125] Fig. 23 is an example of a cancellation analysis list generated by selecting the analysis axis of "product" and the output unit of "contract sales details unit". As shown in Fig. 23, in the cancellation analysis list, the cancellation month, total number of items, and total number of cancellations of each product that has been cancelled for each contract sales detail (for each product) are input and displayed.

[0126] In addition, in this cancellation analysis list, the cancellation rate for each product calculated for each contract partner by the calculation unit 22 using the arithmetic formula of "(total number of cancellations ÷ total number of items) × 100" is input and displayed. Specifically, for the product "Digital Signage A" with the contract number "PJ0001" in the "January 2024" period, the cancellation rate is calculated by the calculation unit 22 as "(total number of cancellations 8 ÷ total number of items 100) × 100 = 8%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0127] Similarly, for the product "Digital Signage B" with contract number "PJ0002" in "February 2024", the cancellation rate is calculated by the calculation unit 22 as "(1 total cancellation ÷ 30 total cases) × 100 = 3.3%", and is input and displayed in the cancellation analysis list by the data generation unit 23. Similarly, for the product "Cart A" with contract number "PJ0005" in "October 2023", the cancellation rate is calculated by the calculation unit 22 as "(1 total cancellation ÷ 2 total cases) × 100 = 50%", and is input and displayed in the cancellation analysis list by the data generation unit 23.

[0128] Products or services with a high cancellation rate often have problems with that product or service. Therefore, by automatically calculating the analysis rate corresponding to the analysis axis of "product" and the output unit of "contract sales details unit" and including it in the cancellation analysis list for output, the cancellation rate can be recognized, for example, by dividing it into products, services, or areas. Thus, potential problems in the product or service can be surfaced, which can also lead to business improvement and future marketing activities.

[0129] Also, in this cancellation list, as shown in FIG. 23, the unsold principal amount at the time of cancellation for each contract sales detail (for each product), which is the amount that becomes unprofitable after the cancellation month, is also input and displayed. Thereby, the amount that becomes unprofitable due to the cancellation of the contract can be recognized for each product, and the problem points can be analyzed in more detail and utilized for business plans and the like.

[0130] (Effects of the Embodiment) As is clear from the above description, the business support device 1 of the embodiment can calculate and present the cancellation rate and cancellation amount of the contract for each analysis item such as the business partner, product, and responsible department.

[0131] This makes it possible to calculate the cancellation rate by dividing, for example, by company, by product or service, by department, or by area, etc., and enables various simulations. Also, products or services with a high cancellation rate often have problems with that product or service. By providing the cancellation rate, it is possible to surface the problems latent in such products or services, which can also lead to business improvement and future marketing activities etc.

[0132] [Contribution to the Sustainable Development Goals (SDGs) led by the United Nations] The present invention can contribute to promoting business efficiency and appropriate management decisions of enterprises, and thus can contribute to the goals of "8" and "9" of the SDGs.

[0133] Also, the present invention can contribute to reducing waste loss and promoting paperless and digitization, and thus can contribute to the goals of "12", "13", and "15" of the SDGs.

[0134] Also, the present invention can contribute to strengthening control and governance, and thus can contribute to the goal of "16" of the SDGs.

[0135] [Other Embodiments] The present invention can be implemented in various different forms within the scope of the technical idea described in the claims even other than the above-described embodiments.

[0136] For example, among the respective processes described in the embodiments, all or part of the processes described as being automatically performed may be performed manually. Or, all or part of the processes described as being performed manually may be automatically performed by a known method or the like.

[0137] Also, regarding the processing procedures, control procedures, specific names, information including parameters such as registered data of each process, search conditions, etc., screen examples, and database configurations shown in the specification or drawings, they can be arbitrarily changed unless otherwise specified.

[0138] Regarding the business support device 1, each of the illustrated components is conceptually functional and does not necessarily have the physical configuration shown. For example, with respect to the processing functions provided by the business support device 1, particularly each processing function performed by the control unit 3, all or any part thereof may be realized by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or may be realized by hardware using wired logic.

[0139] Note that the program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing an information processing device to execute the processing described in the embodiment, and is mechanically read by the business support device 1 as needed. That is, in the storage unit 2 such as a ROM or HDD, a computer program for giving instructions to the control unit 3 (CPU) in cooperation with the OS (Operating System) to perform various processes is recorded. This computer program is loaded into the RAM and expanded, and is appropriately executed by the control unit 3.

[0140] Also, the business support program of this business support device 1 may be stored in another server device connected to the business support device 1 via an arbitrary network, and all or part of it may be downloaded and executed as needed.

[0141] Also, the business support program for executing the processing described in the embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product.

[0142] Here, as the "recording medium", any "portable physical medium" such as a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical Disk), a DVD (Digital Versatile Disk), and a Blu-ray (registered trademark) Disc can be used.

[0143] Also, the "program" is a data processing method described in any language or description method, and is not limited to forms such as source code or binary code.

[0144] Note that the "program" is not necessarily limited to being configured singularly, and includes those that are distributed as a plurality of modules or libraries and those that achieve their functions in cooperation with separate programs typified by an OS.

[0145] Also, for the specific configuration, reading procedure, and installation procedure after reading for the recording medium reading unit in the business support apparatus 1 of the embodiment, well-known configurations or procedures can be used.

[0146] The storage unit 2 is a storage means such as a memory device such as a RAM or a ROM, a fixed disk device such as a hard disk, a flexible disk, and an optical disk, and stores various programs, tables, databases, and web page files used for various processes or website provision.

[0147] Further, the business support device 1 may be configured by an information processing device such as a known personal computer device or a workstation, or may be configured by an information processing device to which an arbitrary peripheral device is connected. Further, the information processing device may be realized by implementing software (including programs or data, etc.) for realizing the processing described in the embodiment.

[0148] Furthermore, the specific forms of distribution and integration of the devices are not limited to those illustrated, and all or part of them can be functionally or physically distributed or integrated in arbitrary units according to various additions or according to the functional load. That is, by arbitrarily combining the above-described embodiments, the above-described embodiments may be selectively implemented.

Industrial Applicability

[0149] The present invention is applicable to various industries as long as it is an industry that conducts commercial transactions and provides commercial transaction targets (goods or services).

Explanation of Signs

[0150] 1 Business support device 2 Storage unit 3 Control unit 4 Communication interface unit 5 Input / output interface unit 6 Input device 7 Output device 11 Product master table 12 Customer master table 13 Department master table 14 Contract basic data table 15 Contract sales details data table 16 Contract sales detailed data table 17 Cancellation analysis list storage unit 21 Acquisition unit 22 Calculation unit 23 Data generation unit 24 Output control unit 25 Detection unit

Claims

1. From a storage unit storing contract data including business transaction target information for specifying a business transaction target provided to a trading partner by contract, a predetermined analysis item serving as an aggregation unit for the number of contracts, and a contract termination timing for the contract with respect to the business transaction target, for each of the specified analysis items, an acquisition unit that acquires the contract data having the same contract termination timing; A detection unit that detects the number of contracts for each of the analysis items, which is the number of the contract data, and detects the number of terminations for each of the analysis items, which is the number of the contract data having the same contract termination timing, based on the contract data for each of the acquired analysis items; A calculation unit that calculates, for each of the analysis items, a termination rate that is the ratio of the number of terminations to the number of detected contracts; An output control unit that performs output control of a termination analysis list including the calculated termination rate for each of the analysis items; A business support device having the above.

2. The contract data includes a contract amount for each trading partner based on the contract with the business transaction target. The calculation unit calculates, for each of the analysis items, an uncollected principal amount at the time of termination, which is the contract amount corresponding to the period from the contract termination timing to the contract expiration timing. The output control unit performs output control including the uncollected principal amount at the time of termination for each of the analysis items in the termination analysis list. The business support device according to claim 1, characterized by the above.

3. The contract data includes industry type information indicating the industry type of each trading partner. The output control unit performs output control including the industry type information of the trading partner for each of the analysis items in the termination analysis list. The business support device according to claim 2, characterized by the above.

4. The contract data includes contract basic data that is data for each contract unit for each trading partner and contract sales detail data that is data for each contract sales detail unit for each business transaction target. When the contract unit is specified, the acquisition unit acquires the contract basic data for each of the specified analysis items, and when the contract sales detail unit is specified, the acquisition unit acquires the contract sales detail data for each of the specified analysis items. The output control unit performs output control of the termination analysis list including the contract basic data of the specified contract unit or the termination analysis list including the contract sales detail data of the specified contract sales detail unit. The business support device according to any one of claims 1 to 3, characterized by the above.

5. An acquisition step in which, based on a contract, the acquisition unit acquires contract data having the same cancellation timing from a storage unit storing business transaction target information for specifying a business transaction target provided to a trading partner, a predetermined analysis item serving as an aggregation unit for the number of contracts, and a cancellation timing of a contract for the business transaction target, for each of the specified analysis items; A detection step in which the detection unit detects the number of contracts for each of the analysis items, which is the number of the contract data, and detects the number of cancellations for each of the analysis items, which is the number of the contract data having the same cancellation timing, based on the contract data for each of the analysis items acquired; A calculation step in which the calculation unit calculates, for each of the analysis items, a cancellation rate that is the ratio of the number of cancellations to the number of contracts detected; An output control step in which the output control unit performs output control on a cancellation analysis list including the cancellation rates for each of the analysis items calculated; A business support method having the above.

6. A computer, An acquisition unit that acquires, for each of the specified analysis items, contract data having the same cancellation timing from a storage unit storing business transaction target information for specifying a business transaction target provided to a trading partner, a predetermined analysis item serving as an aggregation unit for the number of contracts, and a cancellation timing of a contract for the business transaction target, based on a contract; A detection unit that detects the number of contracts for each of the analysis items, which is the number of the contract data, and detects the number of cancellations for each of the analysis items, which is the number of the contract data having the same cancellation timing, based on the contract data for each of the analysis items acquired; A calculation unit that calculates, for each of the analysis items, a cancellation rate that is the ratio of the number of cancellations to the number of contracts detected; An output control unit that performs output control on a cancellation analysis list including the cancellation rates for each of the analysis items calculated; A business support program that functions as the above.

Images