Adjustment management device, adjustment management method, and adjustment management program

Abstract

To provide an adjustment management device, a method, and a program that contribute to improvement in efficiency of adjustment operation for affiliated stores in a credit loan company.SOLUTION: An adjustment management method generates a record that includes an adjustment date, a target category, an installment contract, a transaction type, an adjustment amount, and affiliated stores displayed on an adjustment data creation processing screen, stores the record in adjustment detail data when the transaction type included in the record is a substitutive payment, extracts the record in which the target category has been carried over, the carry-over adjustment date is unset, and which matches the installment contract, transaction type, adjustment amount, and affiliated stores included in the record from the adjustment detail data when the transaction type included in the record is cancellation, stores the record in the adjustment detail data when the record is not extracted, sets the adjustment date included in the record as the carry-over source adjustment date in the generated record when the record is extracted, stores the record after setting in the adjustment detail data, and sets the adjustment date included in the record as the carry-over adjustment date in the extracted record.SELECTED DRAWING: Figure 12

Description

[Technical field]

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

[0002] Patent Document 1 discloses a paid money return management device that enables efficient settlement of an advance payment when an advance payment is cancelled and efficient management of the return of a customer's paid money. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-46237 A Summary of the Invention [Problem to be solved by the invention]

[0004] In an installment contract, a company that handles installment business (hereinafter referred to as a credit company, etc.) pays to the affiliated store advances and brokerage fees associated with the sale of goods and provision of services to users of the installment service. In addition, if a user of the installment service cancels the sale of goods or provision of services due to a cooling-off period or other reason, the affiliated store must refund the advance to the credit company, etc., and in some cases, a cancellation fee must also be paid.

[0005] For affiliated stores, receiving advance payments, brokerage fees, etc. are positive elements, while refunds of advance payments and payments of cancellation fees, etc. are negative elements. When a purchase of goods, etc. is cancelled by a user of the installment payment service, the negative elements (settlement amounts such as refunds of advance payments) are offset by the positive elements (advance payments, etc.), and the settlement process is completed when the advance payment after offsetting is paid to the affiliated store. However, in cases where the affiliated store is small or there are many cancellations, the negative elements may exceed the positive elements. When such an event occurs, the credit company offsets the negative elements by having the affiliated store pay the difference, or carries over the negative elements until the positive elements exceed the negative elements, which is a complicated process and places a heavy burden on the staff, resulting in non-collection of advance payments, etc. due to mistakes.

[0006] The present invention has been made in consideration of the above, and aims to provide a settlement management device, a settlement management method, and a settlement management program that contribute to improving the efficiency of settlement operations for affiliated stores at credit card companies. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the settlement management device of the present invention has a transaction data table that manages transaction amounts paid by a credit sales company to affiliated stores by linking them with installment contracts, transaction types in which advance payment and cancellation are defined as type values, and affiliated stores, and a settlement details data table that manages settlement amounts by linking them with settlement dates, installment contracts, object categories in which settled and carried over are defined as category values, transaction types, carryover original settlement dates, carryover destination settlement dates, and affiliated stores, by combining the above-mentioned transaction data table with installment contracts and transaction types. a transaction extraction unit which extracts records relating to unsettled transactions from the settlement data table; a settlement detail extraction unit which extracts records for which the target category has been carried over and the carryover settlement date has not been set from the settlement detail data table; and a combination of the installment contract, transaction type, settlement amount, and affiliated store contained in the records extracted by the settlement detail extraction unit and a combination of the installment contract, transaction type, transaction amount, and affiliated store contained in the records extracted by the transaction extraction unit are displayed on a specified screen as the installment contract, transaction type, settlement amount, and affiliated store in association with the selectable target category. a display processing unit that displays the transaction details of the transaction in the specified screen; (1) generates a record including the settlement date displayed on the specified screen and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the specified screen; (2) if the transaction type included in the generated record is advance payment, stores the generated record in the settlement details data table; and (3) if the transaction type included in the generated record is cancellation, retrieves from the settlement details data table the transaction details for which the target category has been carried over, the carryover settlement date has not been set, and the affiliated store included in the generated record. and a settlement management unit that extracts a record that matches the installment contract, transaction type, settlement amount, and affiliated store that are generated, and if no record is extracted, stores the generated record in the settlement details data table, and if a record is extracted, sets the settlement date included in the extracted record as the carryover settlement date for the generated record, stores the generated record after the setting in the settlement details data table, and sets the settlement date included in the generated record as the carryover settlement date for the extracted record.

[0008] In addition, the settlement management unit may aggregate, from the settlement detail data table, the settlement amounts contained in records whose settlement date matches the settlement date displayed on the specified screen and whose target category is "settled," by settlement date and affiliated store, and store the aggregated results in a settlement data table that manages settlement amounts by settlement date and by affiliated store.

[0009] In addition, as a classification value of the target classification, "excluded" may be further defined, which means that the settlement amount has been excluded from settlement management.

[0010] In addition, in the settlement management method according to the present invention, a transaction extraction unit links a transaction data table that manages transaction amounts paid by a credit company to affiliated stores with installment contracts, transaction types in which advance payment and cancellation are defined as type values, and affiliated stores, and a settlement details data table that manages settlement amounts in which settlement dates, installment contracts, object categories in which settled and carried over are defined as category values, transaction types, carryover original settlement dates, carryover destination settlement dates, and affiliated stores, by combining the above with the installment contracts and transaction types, thereby extracting unsettled transactions related to the above transaction data table. a transaction extraction step of extracting records; a settlement detail extraction step of extracting records from the settlement detail data table for which the target category has been carried over and the carryover settlement date has not been set; and a display processing unit displays, on a predetermined screen, a combination of an installment contract, transaction type, settlement amount, and affiliated store contained in the records extracted in the settlement detail extraction step, and a combination of an installment contract, transaction type, transaction amount, and affiliated store contained in the records extracted in the transaction extraction step, in association with a selectable target category as the installment contract, transaction type, settlement amount, and affiliated store. a display processing step in which a settlement management unit (1) generates a record including the settlement date displayed on the specified screen and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the specified screen, (2) stores the generated record in the settlement details data table if the transaction type included in the generated record is advance payment, and (3) retrieves from the settlement details data table a record in which the target category has been carried over, the carryover settlement date has not been set, and the generated record is a cancellation. and a settlement management step of extracting a record that matches the installment contract, transaction type, settlement amount, and affiliated store included in the data, and if no record is extracted, storing the generated record in the settlement details data table, and if a record is extracted, setting the settlement date included in the extracted record as the carryover settlement date for the generated record, storing the generated record after setting in the settlement details data table, and setting the settlement date included in the generated record as the carryover settlement date for the extracted record.

[0011] The settlement management program according to the present invention is a transaction data table that manages transaction amounts paid by a credit company to affiliated stores by linking them with installment contracts, transaction types in which advance payment and cancellation are defined as type values, and affiliated stores, and a settlement details data table that manages settlement amounts by linking them with settlement dates, installment contracts, object categories in which settled and carried over are defined as category values, transaction types, carryover original settlement dates, carryover destination settlement dates, and affiliated stores, by linking the transaction data table by installment contracts and transaction types. a transaction extraction means for extracting records relating to unsettled transactions from the settlement details data table; a settlement detail extraction means for extracting records for which the target category has been carried over and the carryover settlement date has not been set from the settlement details data table; and a display process for displaying on a specified screen, a combination of installment contract, transaction type, settlement amount, and affiliated store contained in the records extracted by the settlement detail extraction means, and a combination of installment contract, transaction type, transaction amount, and affiliated store contained in the records extracted by the transaction extraction means, in association with a selectable target category, as installment contract, transaction type, settlement amount, and affiliated store. and (3) if the transaction type included in the generated record is a cancellation, extracts from the settlement details data table a record in which the target category has been carried over, the carryover settlement date has not been set, and which matches the installment contract, transaction type, settlement amount, and affiliated store included in the generated record, and if no record is extracted, stores the generated record in the settlement details data table, and if a record is extracted, sets the settlement date included in the extracted record as the carryover source settlement date in the generated record, stores the generated record after the setting in the settlement details data table, and sets the settlement date included in the generated record as the carryover settlement date in the extracted record. Effect of the Invention

[0012] The present invention has an effect of contributing to the improvement of the efficiency of settlement operations for affiliated stores at credit card companies. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram showing an example of an outline of a contractual relationship. [Diagram 2] FIG. 2 is a diagram showing an example of an outline of settlement between a credit company and an affiliated store. [Diagram 3] FIG. 3 is a diagram illustrating an example of the configuration of the task support device according to the present embodiment. [Figure 4] FIG. 4 is a diagram showing an example of transaction data according to the present invention. [Diagram 5] FIG. 5 is a diagram showing an example of detailed billing data according to the present invention. [Figure 6] FIG. 6 is a diagram showing an example of settlement data according to the present invention. [Figure 7] FIG. 7 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a screen and an example of data for explaining a specific example of processing in this embodiment. [Figure 9] FIG. 9 is a diagram showing an example of a screen and an example of data for explaining a specific example of processing in this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of a screen and an example of data for explaining a specific example of processing in this embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a screen and an example of data for explaining a specific example of processing in this embodiment. [Figure 12] FIG. 12 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a screen and an example of data for explaining a specific example of processing in this embodiment. [Figure 14]FIG. 14 is a diagram showing an example of a screen and an example of data for explaining a specific example of processing in this embodiment. [Figure 15] FIG. 15 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. [Figure 16] FIG. 16 is a diagram showing an example of a screen and an example of data for explaining a specific example of processing in this embodiment. [Figure 17] FIG. 17 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Hereinafter, an embodiment of a settlement management device, a settlement management method, and a settlement management program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiment.

[0015] [1. Overview] Fig. 1 is a diagram showing an example of an outline of a contractual relationship. A customer of an affiliated store (a user of an installment payment service) decides to purchase, for example, a television and enters into a sales contract (buying and selling contract) with the affiliated store, at which point the customer offers to pay in installments. The customer then enters into an installment contract with a credit company with which the affiliated store has an affiliated store contract, and pays the price of the purchased television in accordance with the installment contract concluded with the credit company. Meanwhile, the affiliated store receives an advance (price of the television) from the credit company in accordance with the affiliated store contract previously concluded (see Fig. 1).

[0016] FIG. 2 is a diagram showing an example of an outline of settlement between a credit company and an affiliated store. A customer may cancel a sales contract with an affiliated store due to cooling off or the like. In that case, a settlement operation such as an advance payment occurs between the credit company and the affiliated store. As shown in FIG. 2, in the settlement operation, when a refund of an advance payment of 200,000 yen due to a customer's cancellation and a new advance payment of 1 million yen occurs, the two are usually offset, and the credit company completes the settlement operation by sending the offset settlement amount of 800,000 yen to the affiliated store. However, as shown in FIG. 2, in the case where only a refund of an advance payment of 200,000 yen due to a customer's cancellation and no new advance payment occurs, the settlement (remittance) process due to a negative balance cannot be performed, and therefore the system is managed outside the system. Therefore, in this embodiment, even if a negative balance (uncollected / unpaid) occurs, it is possible to manage the system.

[0017] [2. Configuration] An example of the configuration of the business support device 100 according to this embodiment (including the settlement management device of the present invention) will be described with reference to Fig. 3 etc. Fig. 3 is a block diagram showing an example of the configuration of the business support device 100.

[0018] The business support device 100 is constructed based on a commercially available desktop personal computer. The business support device 100 is not limited to being constructed based on a stationary information processing device such as a desktop personal computer, but may be constructed based on a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0019] The business support device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the business support device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0020] The communication interface unit 104 communicatively connects the task assistance device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the task assistance device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may be stored in the server 200, for example.

[0021] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that cooperates with a mouse to realize a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

[0022] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the storage unit 106.

[0023] The memory unit 106 stores transaction data 106a (corresponding to the transaction data table of the present invention), settlement detail data 106b (corresponding to the settlement detail data table of the present invention), settlement data 106c (corresponding to the settlement data table of the present invention), and the like.

[0024] The transaction data 106a is for managing transactions between credit companies and affiliated stores. As shown in Fig. 4, the transaction data 106a stores contract identification information (e.g., contract number), the type of transaction between the credit company and the affiliated store (e.g., transaction type), transaction amount, and affiliated store identification information (e.g., affiliated store code, affiliated store name), etc. The transaction data 106a manages the transaction amount paid by the credit company to the affiliated store by linking it to the installment contract, the transaction type where advance payment and cancellation are defined as type values, and the affiliated store.

[0025] The settlement details data 106b is for managing the settlement status of each transaction between a credit company etc. and an affiliated store. As shown in Fig. 5, the settlement details data 106b stores the settlement date, contract identification information, processing classification for identifying the processing of the transaction (e.g., target classification, etc.), transaction type between the credit company etc. and the affiliated store, carryover settlement date, carryover settlement date, affiliated store identification information, settlement amount, etc. The settlement details data 106b manages the settlement amount by linking it to the settlement date, installment contract, target classification with classification values ​​of settled, carried over, and excluded (classification values ​​meaning that the settlement amount has been excluded from settlement management), transaction type, carryover settlement date, carryover settlement date, and affiliated store.

[0026] The settlement data 106c is for managing settlement amounts for each settlement date and each affiliated store. As shown in Fig. 6, the settlement data 106c stores the settlement date, affiliated store identification information, settlement amounts, etc. The settlement data 106c manages settlement amounts for each settlement date and each affiliated store.

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

[0028] The control unit 102 conceptually comprises a transaction data output unit 102a (including a transaction extraction unit, a settlement details extraction unit, and a display processing unit of the present invention) and a settlement data creation processing unit 102b (including a settlement management unit of the present invention).

[0029] The transaction data output unit 102a (1) extracts transaction records relating to unsettled transactions from the transaction data 106a by combining the transaction data 106a and the settlement detail data 106b by installment contract and transaction type, (2) extracts settlement detail records for which the target category has been carried over and the carryover settlement date has not been set from the settlement detail data 106b, and (3) displays on the settlement data creation processing screen MA the combination of installment contract, transaction type, settlement amount, and affiliated store contained in the extracted settlement detail records and the combination of installment contract, transaction type, transaction amount, and affiliated store contained in the extracted transaction records, in correspondence with the selectable target categories as installment contract, transaction type, settlement amount, and affiliated store.

[0030] The transaction data output unit 102a executes the processes (11) to (13). (11) Display the settlement data creation processing screen MA on the monitor 114, and have the person in charge enter the settlement date in area MA11 and press the display button MA12. (12) With reference to the settlement detail data 106b, extract records in which the target category is "1: Carryover" and the carryover settlement date is "NULL" and display them in area MA2 of the settlement data creation processing screen MA. (13) Compare the transaction data 106a and the settlement detail data 106b, extract data stored only in the transaction data 106a in which the contract identification information and transaction type do not match, and display the data in area MA2 of the settlement data creation processing screen MA.

[0031] The settlement data creation processing unit 102b (1) generates a record including the settlement date displayed on the settlement data creation processing screen MA and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the settlement data creation processing screen MA, (2) if the transaction type included in the generated record is advance payment, stores the generated record in the settlement detail data 106b, (3) if the transaction type included in the generated record is cancellation, extracts from the settlement detail data 106b a record for which the target category has been carried over, the carryover settlement date has not been set, and which matches the installment contract, transaction type, settlement amount, and affiliated store included in the generated record, and (4) stores the record in the settlement detail data 106b. (5) if a record is extracted, the settlement date included in the extracted record is set as the carry-over settlement date for the generated record, and the generated record after setting is stored in the settlement detail data 106b, and the settlement date included in the generated record is set as the carry-over settlement date for the extracted record, and (6) the settlement amounts included in the records whose settlement date matches the settlement date displayed on the settlement data creation processing screen MA and whose target category is "settled" are aggregated by settlement date and affiliated store from the settlement detail data 106b, and the aggregated results are stored in the settlement data 106c.

[0032] The settlement data creation processing unit 102b selects and registers "Target," "Carryover," and "Exclude" in the target category of area MA21 of the settlement target data displayed in area MA2 of the settlement data creation processing screen MA, and causes the user to press the settlement button MA3. "Target" is selected when the data is to be processed on the set settlement date of MA11, "Carryover" is selected when the data is not to be processed on the set settlement date of MA11 but to be carried over to the next time, and "Exclude" is selected when the settlement process has been completed by another process (a process outside the system).

[0033] When "Target" is selected in the target category of area MA21, the settlement data creation processing unit 102b executes the processes (21) to (23). (21) The data registered as “target” in the target category of area MA21 is stored in the settlement detail data 106b based on the display information as “target category = target” on the settlement date set in area MA11, and settlement detail data 106b is created. (22) If the record in settlement detail data 106b that is the basis of a record registered as “target” in the target category of area MA21 in (21) (hereinafter referred to as the original record) is “target category = carryover”, the settlement date of the original record is stored in the item name “Carryover source settlement date” of the settlement detail data 106b, and the settlement date set in area MA11 of the settlement data creation processing screen MA is stored in the item name “Carryover destination settlement date” of the original record. (23) Based on the settlement detail data 106b for "subject category = subject" created in (21), the data is aggregated by settlement date and affiliated store identification information and stored in the settlement data 106c, thereby creating the settlement data 106c.

[0034] When "Carryover" is selected in the target category of area MA21, the settlement data creation processing unit 102b performs the processes (31) and (32). (31) The data registered as “Carryover” in the target category of area MA21 is stored in settlement detail data 106b based on the display information as “Target category = Carryover” on the settlement date set in area MA11, and settlement detail data 106b is created. (32) If the original record of the record registered as "Carryover" in the target category of area MA21 in (31) was "Target category = Carryover", the settlement date of the original record is stored in the item name "Carryover original settlement date" of the settlement detail data 106b, and the settlement date set in area MA11 of the settlement data creation processing screen MA is stored in the item name "Carryover settlement date" of the original record. Note that since the "Target category = Target" of the settlement detail data 106b is not set, settlement data 106c is not created.

[0035] When "exclusion" is selected in the target category of area MA21, the settlement data creation processing unit 102b carries out the processes of (41) and (42). (41) The data registered as “Excluded” in the target category of area MA21 is stored in settlement detail data 106b based on the display information as “Target category = Excluded” on the settlement date set in area MA11, and settlement detail data 106b is created. (42) If the original record of the record registered as "Excluded" in the target category of area MA21 in (41) was "Target category = Carryover", the settlement date of the original record is stored in the item name "Carryover settlement date from" of the settlement statement data 106b, and the settlement date set in area MA11 of the settlement data creation processing screen MA is stored in the item name "Carryover settlement date to" of the original record. Note that since the "Target category = Target" of the settlement statement data 106b is not set, settlement data 106c is not created.

[0036] [3. Specific examples of processing] A specific example of the process executed by the business support device 100 configured as described above will be described in detail with reference to Fig. 7 to Fig. 17. Note that the settlement data creation process screen MA shows a part of the settlement data creation process screen.

[0037] 1. Prerequisites (see Figure 7) First, a sales contract (buying and selling contract) is concluded between the affiliated store and the customer, the customer applies to use the installment service, an installment contract is concluded between the credit company etc. and the customer, and a payment on behalf of the credit company etc. and the affiliated store occurs. Then, as shown in Figure 7, the contract number, transaction type, transaction amount, affiliated store, etc. are stored in transaction data 106a. Note that since a payment on behalf of the credit company has occurred, records of settlement details data 106b and settlement data 106c have not yet been created.

[0038] 2. Payment of expenses (see Figure 8) The advance payment settlement process for the advance payment transaction based on the prerequisites shown in Figure 7 is carried out.

[0039] The person in charge issues an instruction to display the settlement data processing screen MA.

[0040] The transaction data output unit 102a causes the monitor 114 to display a settlement data processing screen MA.

[0041] The person in charge sets the settlement date "2022 / 10 / 11" in area MA11 of the settlement data processing screen MA and presses the display button MA12.

[0042] Then, the transaction data output unit 102a compares the transaction data 106a with the settlement detail data 106b, extracts the contract numbers "100," "101," and "200" and the transaction type "advance payment execution," for which there are no records in the settlement detail data 106b, and displays them in area MA2. Note that, since there are no records in the settlement detail data 106b, records with the target category "1: Carryover" and the carryover settlement date "NULL" are not extracted from the settlement detail data 106b.

[0043] The staff member selects "Target" as the target category in area MA21 for the data of contract numbers "100," "101," and "200" that are to be settled and are displayed in area MA2 of the settlement data processing screen MA, registers it, and then presses the settlement button MA3.

[0044] Then, the settlement data creation processing unit 102b stores the settlement date "2022 / 10 / 11" set by the person in charge in the area MA11 in the item name "settlement date", "0: target" registered in the target category of the area MA21 in the item name "target category", "payment execution" displayed in the area MA23 in the item name "transaction type", "NULL" in the item name "carryover settlement date", "NULL" in the item name "carryover settlement date", the affiliated store number "10001" displayed in the area MA25 in the item name "affiliated store", and "200,000 yen" displayed in the area MA24 in the item name "settlement amount" as a record of the contract number "100". The settlement data creation processing unit 102b performs the same process on the contract numbers "101" and "200" to create the settlement detail data 106b shown in FIG. 8.

[0045] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b, extracts records of contract numbers "100", "101" and "200" with "target category = target", and aggregates them by affiliated store number "10001" and affiliated store number "10002" because the settlement date is common to "2022 / 10 / 11". The settlement data creation processing unit 102b sums the settlement amount "200,000 yen" of contract number "100" with affiliated store number "10001" and the settlement amount "300,000 yen" of contract number "101", and stores the settlement date "2022 / 10 / 11", affiliated store "10001", and settlement amount "500,000 yen" in the settlement data 106c (see FIG. 8). Furthermore, the settlement data creation processing unit 102b performs the same process for the affiliated store "10002" as for the affiliated store "10001", but does not perform summation of the settlement amounts because there is only one record (see FIG. 8).

[0046] 3. Advance payments and cancellation fees (Fig. 9) As a premise, a cancellation has occurred for contract number "100", for which advance payment processing has already been performed, and a new advance payment processing has occurred for contract number "300".

[0047] The person in charge issues an instruction to display the settlement data processing screen MA.

[0048] The transaction data output unit 102a causes the monitor 114 to display a settlement data processing screen MA.

[0049] The person in charge sets the settlement date "2022 / 11 / 11" in area MA11 of the settlement data processing screen MA and presses the display button MA12.

[0050] The transaction data output unit 102a then collates the transaction data 106a and the settlement detail data 106b, extracts records of contract number "100", transaction type "cancellation" and contract number "300", transaction type "payment on behalf of" for which no records exist in the settlement detail data 106b, and displays them in area MA2. Note that no records are extracted from the settlement detail data 106b because there are no records in the settlement detail data 106b with the target category set to "1: carryover" and the carryover settlement date set to "NULL".

[0051] The staff member selects "Target" as the target category in area MA21 for the data of contract numbers "100" and "300" to be settled, displayed in area MA2 of the settlement data processing screen MA, registers it, and then presses the settlement button MA3.

[0052] Then, the settlement data creation processing unit 102b stores the settlement date "2022 / 11 / 11" set by the person in charge in the area MA11 in the item name "settlement date", "0: target" registered in the target category of the area MA21 in the item name "target category", "cancellation" displayed in the area MA23 in the item name "transaction type", "NULL" in the item name "carryover settlement date", "NULL" in the item name "carryover settlement date", the affiliated store number "10001" displayed in the area MA25 in the item name "affiliated store", and "-200,000 yen" displayed in the area MA24 in the item name "settlement amount" as a record of the contract number "100". The settlement data creation processing unit 102b performs the same process on the contract number "300" to create the settlement detail data 106b shown in FIG. 9.

[0053] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b, extracts and aggregates records of contract numbers "100" and "300" that are common to the affiliated store number "10001" and have "target category = target" and the settlement date "2022 / 11 / 11" set by the person in charge in the area MA11 this time. The settlement data creation processing unit 102b adds up the settlement amount "-200,000 yen" for the contract number "100" and the settlement amount "1,000,000 yen" for the contract number "100", and stores the settlement date "2022 / 11 / 11", the affiliated store "10001", and the settlement amount "800,000 yen" in the settlement data 106c (see FIG. 9).

[0054] 4. Carryover (Figure 10) As a premise, a cancellation has occurred for contract number "300" for which an advance payment has already been made. Since the settlement of the cancellation fee will result in a negative remittance, the amount will be carried over until the next remittance.

[0055] The person in charge issues an instruction to display the settlement data processing screen MA.

[0056] The transaction data output unit 102a causes the monitor 114 to display a settlement data processing screen MA.

[0057] The person in charge sets the settlement date "2022 / 12 / 11" in area MA11 of the settlement data processing screen MA and presses the display button MA12.

[0058] The transaction data output unit 102a then collates the transaction data 106a and the settlement statement data 106b, extracts records with contract number "300" and transaction type "cancellation" for which no records exist in the settlement statement data 106b, and displays them in area MA2. Note that no records are extracted from the settlement statement data 106b because no records exist in the settlement statement data 106b for which the target category is "1: Carryover" and the carryover settlement date is "NULL."

[0059] The person in charge selects and registers the data for contract number "300" to be settled, displayed in area MA2 of the settlement data processing screen MA, as the target category in area MA21 as "Carryover", and then presses the settlement button MA3.

[0060] Then, the settlement data creation processing unit 102b stores in the settlement detail data 106b, as a record for contract number "300", the settlement date "2022 / 12 / 11" set by the person in charge in area MA11 in the item name "Settlement date", "1: Carryover" registered in the target category of area MA21 in the item name "Target category", "Cancellation" displayed in area MA23 in the item name "Transaction type", "NULL" in the item name "Carryover settlement date from", "NULL" in the item name "Carryover settlement date to", the affiliated store number "10001" displayed in area MA25 in the item name "Affiliated store", and "-1,000,000 yen" displayed in area MA24 in the item name "Settlement amount" (see Figure 10).

[0061] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b and, since there is no record for the settlement date "2022 / 12 / 11" that is set in area MA11 by the person in charge this time where "Target category = Target", does not store the record in the settlement data 106c (see Figure 10).

[0062] 5. Settlement of carried-over details (Fig. 11, Fig. 12) As a premise, a new advance payment transaction has occurred for contract number "301."

[0063] The person in charge issues an instruction to display the settlement data processing screen MA.

[0064] The transaction data output unit 102a causes the monitor 114 to display a settlement data processing screen MA.

[0065] The person in charge sets the settlement date "2023 / 01 / 11" in area MA11 of the settlement data processing screen MA and presses the display button MA12.

[0066] Then, as shown in the settlement data creation processing screen MA of Fig. 11, the transaction data output unit 102a refers to the settlement details data 106b, extracts records in which the target category is "1: Carryover" and the carryover settlement date is "NULL" (settlement date "2022 / 12 / 11", contract number "300", target category "1: Carryover", transaction type "Cancel", carryover source settlement date "NULL", carryover destination settlement date "NULL", affiliated store "10001", settlement amount "-1,000,000 yen"), and displays them in the area MA2. Furthermore, the transaction data output unit 102a compares the transaction data 106a and the settlement details data 106b, extracts the contract number "301" and transaction type "payment on behalf of" for which there is no record in the settlement details data 106b, and displays them in the area MA2.

[0067] The staff member selects "Target" as the target category in area MA21 for the data of contract numbers "300" and "301" to be settled, displayed in area MA2 of the settlement data processing screen MA, registers it, and then presses the settlement button MA3.

[0068] Then, the settlement data creation processing unit 102b sets the settlement date "2023 / 01 / 11" set in the area MA11 to the carryover settlement date of the record including the carryover source settlement date "2022 / 12 / 11" and the target category "1: Carryover" in the settlement detail data 106b, and sets the settlement date "2023 / 01 / 11" set in the area MA11 by the person in charge to the item name "Settlement Date" as a new record for the contract number "300", and sets the settlement date "2023 / 01 / 11" set in the area MA11 by the person in charge to the item name "Target Category" as the target category "0: Target Category" registered in the area MA21. " is stored in the "Transaction type" item name, "Cancellation" displayed in area MA23 is stored in the "Original Carryover Settlement Date" item name, the settlement date "2022 / 12 / 11" of the original record (a record with target category "1: Carryover" and a carryover settlement date of "NULL") is stored in the "Original Carryover Settlement Date" item name, "NULL" is stored in the "Destination Carryover Settlement Date" item name, the affiliated store number "10001" displayed in area MA25 is stored in the "Affiliated Store" item name, and "-1,000,000 yen" displayed in area MA24 is stored in the "Settlement Amount" item name (see Figure 12).

[0069] Next, the settlement data creation processing unit 102b performs the same process as the record generation of the settlement detail data 106b of 2. Advance payment settlement for the contract number "301" (see FIG. 12).

[0070] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b, extracts and aggregates records of contract numbers "300" and "301" that are "target category = target" and have a common settlement date "2023 / 01 / 11" set by the person in charge in the area MA11 this time and are in common with the affiliated store number "10001". The settlement data creation processing unit 102b adds up the settlement amount "-1,000,000 yen" for the contract number "300" and the settlement amount "1,500,000 yen" for the contract number "301", and stores the settlement date "2023 / 01 / 11", the affiliated store "10001", and the settlement amount "500,000 yen" in the settlement data 106c (see FIG. 12).

[0071] 6. Carryover (Figure 13) As a premise, a cancellation has occurred for contract number "301," for which advance payment processing has already been performed.

[0072] The transaction data output unit 102a performs the same process as "4. Carryover" and stores in the settlement detail data 106b, as a record for contract number "301", the settlement date "2023 / 02 / 11" set by the person in charge in area MA11 in the item name "Settlement date", "1: Carryover" registered in the target category of area MA21 in the item name "Target category", "Cancellation" displayed in area MA23 in the item name "Transaction type", "NULL" in the item name "Carryover settlement date from", "NULL" in the item name "Carryover settlement date to", the affiliated store number "10001" displayed in area MA25 in the item name "Affiliated store", and "-1,500,000 yen" displayed in area MA24 in the item name "Settlement amount" (see Figure 13).

[0073] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b and, since there is no record for the settlement date "2023 / 02 / 11" that was set in area MA11 by the person in charge this time where "Target category = Target", does not create a record in the settlement data 106c (see Figure 13).

[0074] 7. Carrying forward carried-over details (Fig. 14, Fig. 15) As a premise, since no new transactions have occurred, further carryover processing will be carried out.

[0075] The person in charge issues an instruction to display the settlement data processing screen MA.

[0076] The transaction data output unit 102a causes the monitor 114 to display a settlement data processing screen MA.

[0077] The person in charge sets the settlement date "2023 / 03 / 11" in area MA11 of the settlement data processing screen MA and presses the display button MA12.

[0078] Then, as shown on the settlement data creation processing screen MA of Figure 14, the transaction data output unit 102a refers to the settlement detail data 106b, extracts records in which the target category is "1: Carryover" and the carryover settlement date is "NULL" (settlement date "2023 / 02 / 11", contract number "301", target category "1: Carryover", transaction type "Cancel", carryover source settlement date "NULL", carryover settlement date "NULL", affiliated store "10001", settlement amount "-1,500,000 yen") and displays them in area MA2.

[0079] The staff member selects and registers the data for contract number "301" to be settled, displayed in area MA2 of the settlement data processing screen MA, as the target category in area MA21 as "Carryover", and then presses the settlement button MA3.

[0080] Then, the settlement data creation processing unit 102b sets the settlement date "2023 / 03 / 11" set in the area MA11 to the carryover settlement date of the record including the carryover source settlement date "2023 / 02 / 11" and the target category "1: Carryover" in the settlement detail data 106b, and sets the settlement date "2023 / 03 / 11" set in the area MA11 by the person in charge to the item name "Settlement Date" as a new record of the contract number "301", and sets the settlement date "2023 / 03 / 11" set in the area MA11 by the person in charge to the item name "Target Category" as the target category "1: Carryover". " is stored in the "Transaction type" item name, "Cancellation" displayed in area MA23 is stored in the "Original Carryover Settlement Date" item name, the settlement date "2023 / 02 / 11" of the original record (a record with target category "1: Carryover" and a carryover settlement date of "NULL") is stored in the "Original Carryover Settlement Date" item name, "NULL" is stored in the "Destination Carryover Settlement Date" item name, the affiliated store number "10001" displayed in area MA25 is stored in the "Affiliated Store" item name, and "-1,500,000 yen" displayed in area MA24 is stored in the "Settlement Amount" item name (see Figure 15).

[0081] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b and, since there is no record for the settlement date "2023 / 03 / 11" that was set in area MA11 by the person in charge this time where "Target category = Target", does not create a record in the settlement data 106c (see Figure 15).

[0082] 8. Exclusion (Figure 16, Figure 17) As a premise, no new transactions have occurred, but individual transfer settlements have occurred from affiliated stores. Therefore, "exclusion" processing will be carried out to prevent double settlement.

[0083] The person in charge issues an instruction to display the settlement data processing screen MA.

[0084] The transaction data output unit 102a causes the monitor 114 to display a settlement data processing screen MA.

[0085] The person in charge sets the settlement date "2023 / 04 / 11" in area MA11 of the settlement data processing screen MA and presses the display button MA12.

[0086] Then, as shown on the settlement data creation processing screen MA of Figure 16, the transaction data output unit 102a refers to the settlement detail data 106b, extracts records in which the target category is "1: Carryover" and the carryover settlement date is "NULL" (settlement date "2023 / 03 / 11", contract number "301", target category "1: Carryover", transaction type "Cancellation", carryover source settlement date "2023 / 02 / 11", carryover settlement date "NULL", affiliated store "10001", settlement amount "-1,500,000 yen") and displays them in area MA2.

[0087] The person in charge selects and registers the data for contract number "301" to be settled, displayed in area MA2 of the settlement data processing screen MA, as the target category in area MA21 as "Exclude", and then presses the settlement button MA3 (see Figure 16).

[0088] Then, the settlement data creation processing unit 102b sets the settlement date "2023 / 04 / 11" set in the area MA11 to the carryover settlement date of the record including the carryover source settlement date "2023 / 03 / 11" and the target category "1: Carryover" in the settlement detail data 106b, and sets the settlement date "2023 / 04 / 11" set in the area MA11 by the person in charge to the item name "Settlement Date" as a new record of the contract number "301", and sets the settlement date "2023 / 04 / 11" set in the area MA11 by the person in charge to the item name "Target Category" as the target category "2: Exclusion". " is stored in the "Transaction type" item name, "Cancellation" displayed in area MA23 is stored in the "Original Carryover Settlement Date" item name, the settlement date "2023 / 03 / 11" of the original record (a record with target category "1: Carryover" and a carryover settlement date of "NULL") is stored in the "Original Carryover Settlement Date" item name, "NULL" is stored in the "Destination Carryover Settlement Date" item name, the affiliated store number "10001" displayed in area MA25 is stored in the "Affiliated Store" item name, and "-1,500,000 yen" displayed in area MA24 is stored in the "Settlement Amount" item name (see Figure 17).

[0089] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b and, since there is no "Target category = Target" in the record for the settlement date "2023 / 04 / 11" set by the person in charge in area MA11 this time, does not create a record in the settlement data 106c (see Figure 17).

[0090] As a result of this process, contract number "301" is stored in settlement detail data 106b as an "exclusion" target category, and is no longer subject to settlement.

[0091] As described above, according to this embodiment, when the advance payment, cancellation, etc. are totaled as the settlement amount, not only the advance payment and the cancellation are offset and the total settlement amount is managed, but the settlement details data 106b manages the history of the settlement status for each advance payment and each cancellation unit, and by referring to the transaction data 106a that manages newly generated transactions, the settlement target (settled), carryover (also compatible with multiple times), and exclusion can be managed by the person in charge. As a result, the system can also manage carryover and exclusion other than the settlement target (settled), preventing non-collection, etc., and enabling the settlement operation to be performed quickly and efficiently. Furthermore, by managing the history, it is also possible to check the history of the settlement amount. In other words, according to this embodiment, the system manages the history of the refund of the advance payment and a wide variety of refund patterns of the advance payment, thereby facilitating the settlement operation and preventing non-collection of the advance payment.

[0092] [4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby contributing to goals 8 and 9 of the SDGs.

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

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

[0095] 5. Other embodiments The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

[0096] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using known methods.

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

[0098] Moreover, with regard to the task support device 100, each of the components shown in the figures is a functional concept, and does not necessarily have to be physically configured as shown in the figures.

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

[0100] In addition, this computer program may be stored in an application program server connected to the task support device 100 via any network, and it is also possible to download all or a part of it as necessary.

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

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

[0103] The various databases etc. stored in the memory unit are storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files etc. used for various processes and providing websites.

[0104] The business support device 100 may be configured as an information processing device such as a known personal computer or a workstation, or may be configured as the information processing device to which any peripheral device is connected. The business support device 100 may be realized by installing software (including programs or data) that causes the device to realize the processing described in this embodiment.

[0105] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively. [Industrial Applicability]

[0106] The present invention is useful for companies in the financial industry that handle settlement operations for affiliated stores, such as credit companies. [Explanation of symbols]

[0107] 100 Business support equipment 102 Control section 102a Transaction data output section 102b Settlement data creation processing unit 104 Communication interface section 106 Storage section 106a Transaction Data 106b Payment details data 106c Settlement Data 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Servers 300 Network

Claims

1. a transaction extraction unit which extracts records relating to unsettled transactions from the transaction data table by linking the installment contract and transaction type to a transaction data table which manages transaction amounts paid by the credit company to affiliated stores by linking them with installment contracts, transaction types with type values ​​of "advance payment" and "cancellation" and affiliated stores, and a settlement details data table which manages settlement amounts by linking them with settlement dates, installment contracts, object categories with category values ​​of "settled" and "carried over", transaction types, carryover original settlement dates, carryover destination settlement dates and affiliated stores, using the installment contract and transaction type; A settlement details extraction unit that extracts records in which a target category has been carried over and a carryover settlement date has not been set from the settlement details data table; a display processing unit that displays, on a specified screen, the combination of installment contract, transaction type, settlement amount, and affiliated store contained in the record extracted by the settlement details extraction unit, and the combination of installment contract, transaction type, transaction amount, and affiliated store contained in the record extracted by the transaction extraction unit, in association with selectable target categories as installment contract, transaction type, settlement amount, and affiliated store; a settlement management unit that (1) generates a record including the settlement date displayed on the specified screen and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the specified screen, (2) stores the generated record in the settlement details data table if the transaction type included in the generated record is advance payment, and (3) extracts from the settlement details data table a record in which the target category has been carried over, the carryover settlement date has not been set, and which matches the installment contract, transaction type, settlement amount, and affiliated store included in the generated record if the record is not extracted, stores the generated record in the settlement details data table if the record is extracted, sets the settlement date included in the extracted record as the carryover source settlement date in the generated record, stores the generated record after the setting in the settlement details data table, and sets the settlement date included in the generated record as the carryover settlement date in the extracted record; A settlement management device comprising:

2. the settlement management unit aggregates, from the settlement detail data table, settlement amounts included in records whose settlement dates match the settlement date displayed on the specified screen and whose target category is "settled," by settlement date and by affiliated store, and stores the aggregated results in a settlement data table that manages settlement amounts by settlement date and by affiliated store; 2. The settlement management device according to claim 1 .

3. The classification value of the target classification is further defined as "Excluded," which means that the settlement amount has been excluded from settlement management.

3. The settlement management device according to claim 2,

4. a transaction extraction step in which a transaction extraction unit links a transaction data table that manages transaction amounts paid by credit companies to affiliated stores by linking them with installment contracts, transaction types with type values ​​of "payment on behalf of" and "cancellation" and affiliated stores, and a settlement details data table that manages settlement amounts by linking them with settlement dates, installment contracts, object categories with category values ​​of "settled" and "carried over", transaction types, carryover original settlement dates, carryover destination settlement dates and affiliated stores, by combining the above transaction data table with the installment contracts and transaction types, thereby extracting records relating to unsettled transactions from the transaction data table; A settlement detail extraction step in which a settlement detail extraction unit extracts, from the settlement detail data table, records in which a target category has been carried over and a carryover settlement date has not been set; a display processing step in which a display processing unit displays, on a specified screen, the combination of the installment contract, transaction type, settlement amount, and affiliated store contained in the record extracted in the settlement detail extraction step, and the combination of the installment contract, transaction type, transaction amount, and affiliated store contained in the record extracted in the transaction extraction step, in association with a selectable target category as the installment contract, transaction type, settlement amount, and affiliated store; a settlement management step in which a settlement management unit (1) generates a record including the settlement date displayed on the specified screen and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the specified screen, (2) if the transaction type included in the generated record is advance payment, stores the generated record in the settlement details data table, and (3) if the transaction type included in the generated record is cancellation, extracts from the settlement details data table a record whose target category has been carried over, whose carryover settlement date has not been set, and whose installment contract, transaction type, settlement amount, and affiliated store included in the generated record are matched, and if no record is extracted, stores the generated record in the settlement details data table, and if a record is extracted, sets the settlement date included in the extracted record as the carryover source settlement date in the generated record, stores the generated record after the setting in the settlement details data table, and sets the settlement date included in the generated record as the carryover settlement date in the extracted record; A settlement management method comprising:

5. An information processing device, a transaction extraction means for extracting records relating to unsettled transactions from the transaction data table by combining a transaction data table that manages transaction amounts paid by the credit company to affiliated stores by linking them with installment contracts, transaction types with type values ​​of "advance payment" and "cancellation" and affiliated stores, and a settlement details data table that manages settlement amounts by linking them with settlement dates, installment contracts, object categories with category values ​​of "settled" and "carried over", transaction types, carryover original settlement dates, carryover destination settlement dates and affiliated stores, using the installment contracts and transaction types; a settlement details extraction means for extracting, from the settlement details data table, records in which the target category has been carried over and the carryover settlement date has not been set; a display processing means for displaying, on a predetermined screen, a combination of an installment contract, a transaction type, a settlement amount, and an affiliated store contained in the record extracted by said settlement detail extraction means, and a combination of an installment contract, a transaction type, a transaction amount, and an affiliated store contained in the record extracted by said transaction extraction means, in association with a selectable target category as an installment contract, a transaction type, a settlement amount, and an affiliated store; a settlement management means for (1) generating a record including the settlement date displayed on the specified screen and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the specified screen, (2) storing the generated record in the settlement details data table if the transaction type included in the generated record is advance payment, and (3) extracting from the settlement details data table a record in which the target category has been carried over, the carryover settlement date has not been set, and which matches the installment contract, transaction type, settlement amount, and affiliated store included in the generated record if no record is extracted, storing the generated record in the settlement details data table if a record is extracted, setting the settlement date included in the extracted record as the carryover source settlement date in the generated record, storing the generated record after the setting in the settlement details data table, and setting the settlement date included in the generated record as the carryover settlement date in the extracted record; A settlement management program to function as a.

Images