Account settlement management device, account settlement management method, and account settlement 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 advance payments and return management of customer payments in the event of cancellation of advance payments. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-46237 Summary of the Invention [Problem to be solved by the invention]

[0004] In an installment contract, companies that handle installment business (hereinafter referred to as credit companies, etc.) pay advances and brokerage fees to affiliated stores associated with the sale of goods or 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 cooling-off periods or other reasons, the affiliated store must refund the advances to the credit companies, etc., and in some cases, additional cancellation fees may be required.

[0005] For affiliated stores, receiving advance payments, brokerage fees, etc. are positive elements, while refunds of advance payments and payments of cancellation fees are negative elements. When a user of an installment payment service cancels a purchase, etc., 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 offsetting advance payments are 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. This is a complicated process that places a heavy burden on the staff, and has led to uncollected advance payments, etc. due to errors.

[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 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 where 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, target categories where settled and carried over are defined as category values, transaction types, carryover settlement dates, carryover settlement dates, and affiliated stores, by linking the transaction data table with installment contracts and transaction types. a transaction extraction unit that extracts records relating to unsettled transactions from the settlement data table; a settlement detail extraction unit that extracts 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 combination of installment contract, transaction type, settlement amount and affiliated store contained in the records extracted by the settlement detail extraction unit and a combination of installment contract, transaction type, transaction amount and affiliated store contained in the records extracted by the transaction extraction unit are displayed on a predetermined screen as installment contract, transaction type, settlement amount and affiliated store in association with selectable target categories. a display processing unit that (1) generates a record including the settlement date displayed on the predetermined screen and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the predetermined 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 the transaction for which the target category has been carried over, the carryover settlement date has not been set, and the transaction for which the carryover settlement date has not been set and the affiliated store included in the generated record is cancelled. and a settlement management unit that extracts a record that matches the installment contract, transaction type, settlement amount, and affiliated store that are to be 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 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.

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

[0009] Furthermore, 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] Furthermore, in the settlement management method according to the present invention, the 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 where advance payment and cancellation are defined as type values, and affiliated stores, with a settlement details data table that manages settlement amounts by linking them with settlement dates, installment contracts, target categories where settled and carried over are defined as category values, transaction types, carryover settlement dates, carryover settlement dates, and affiliated stores, by combining the transaction data table with installment contracts and transaction types. a transaction extraction step of extracting records; a settlement detail extraction step in which a settlement detail extraction unit extracts from the settlement detail data table records 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, as installment contracts, transaction types, settlement amounts, and affiliated stores, combinations of installment contracts, transaction types, transaction amounts, and affiliated stores included in the records extracted in the settlement detail extraction step, and combinations of installment contracts, transaction types, transaction amounts, and affiliated stores, the installment contracts, transaction types, settlement amounts, and affiliated stores being associated with selectable target categories. a display processing step in which the settlement management unit (1) generates a record including the settlement date displayed on the predetermined screen and the target category, installment contract, transaction type, settlement amount, and affiliated store displayed on the predetermined 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 target category that has been carried over, the carryover settlement date that has not been set, and the generated record 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 in 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 in the extracted record.

[0011] Furthermore, the settlement management program of the present invention allows an information processing device to link a transaction data table that manages transaction amounts paid by a credit company to affiliated stores by linking them with installment contracts, transaction types where 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, target categories where settled and carried over are defined as category values, transaction types, carryover settlement dates, carryover 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 details 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 predetermined screen the combinations of installment contract, transaction type, settlement amount and affiliated store contained in the records extracted by the settlement details extraction means and the combinations of installment contract, transaction type, transaction amount and affiliated store contained in the records extracted by the transaction extraction means in association with selectable target categories as installment contract, transaction type, settlement amount and affiliated store. (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 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 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 in the generated record, stores the generated record after setting, and sets the settlement date included in the generated record as the carryover settlement date in the extracted record. [Effects of the Invention]

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

[0013] [Figure 1] FIG. 1 is a diagram showing an example of an outline of a contractual relationship. [Figure 2] FIG. 2 is a diagram showing an example of an outline of settlement between a credit company and an affiliated store. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of a task assistance device according to this embodiment. [Figure 4] FIG. 4 is a diagram showing an example of transaction data according to the present invention. [Figure 5] FIG. 5 is a diagram showing an example of detailed payment 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 INVENTION

[0014] Hereinafter, embodiments 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 accompanying drawings. Note that the present invention is not limited to these embodiments.

[0015] [1. Overview] Figure 1 is a diagram showing an example of an outline of a contractual relationship. A customer of a member 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 member store, at which time the customer offers to pay by installments. The customer then enters into an installment payment contract with a credit company with which the member store has an affiliated store contract, and pays the price of the purchased television in accordance with the installment payment contract concluded with the credit company. Meanwhile, the member store receives an advance (the price of the television) from the credit company in accordance with the affiliated store contract, etc., that it previously concluded (see Figure 1).

[0016] FIG. 2 is a diagram illustrating an example of an outline of settlement between a credit company and a member store. A customer may cancel a sales contract with a member store due to a cooling-off period or the like. In such a case, a settlement process for advance payments and the like occurs between the credit company and the member store. Regarding this settlement process, as shown in FIG. 2, if a 200,000 yen advance refund due to a customer's cancellation results in a new advance payment of 1,000,000 yen, these are usually offset, and the credit company completes the settlement process by remitting the offset settlement amount of 800,000 yen to the member store. However, as shown in FIG. 2, if only a 200,000 yen advance refund due to a customer's cancellation results in no new advance payment, settlement (remittance) processing due to a negative balance is not possible, and this is managed outside the system. Therefore, in this embodiment, even if a negative balance (uncollected or unpaid) occurs, it is possible to manage the balance within the system.

[0017] [2. Configuration] An example of the configuration of the business assistance 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 assistance device 100.

[0018] The business support device 100 is constructed based on a commercially available desktop personal computer. Note that 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 also 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 assistance 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 assistance 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 communicably connects the business 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 business 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). Note that 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 achieve 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 that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0023] The storage 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] Transaction data 106a is used to manage transactions between credit companies and affiliated stores. As shown in Fig. 4, transaction data 106a stores contract identification information (e.g., contract number), the type of transaction between credit companies and affiliated stores (e.g., transaction type), transaction amount, and affiliated store identification information (e.g., affiliated store code, affiliated store name), etc. Transaction data 106a manages transaction amounts paid by credit companies to affiliated stores by linking them to installment contracts, transaction types where advance payment and cancellation are defined as type values, and affiliated stores.

[0025] Settlement statement data 106b is used to manage the settlement status of each transaction between a credit company or the like and an affiliated store. As shown in Figure 5, settlement statement data 106b stores the settlement date, contract identification information, processing classification (e.g., target classification, etc.) for identifying the processing of the transaction, the type of transaction between the credit company or the like and the affiliated store, carryover settlement date, carryover settlement date, affiliated store identification information, and settlement amount, etc. Settlement statement data 106b manages settlement amounts by linking them to the settlement date, installment contract, target classification (with defined classification values ​​of settled, carried over, and excluded (classification value 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 used to manage settlement amounts for each settlement date and 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 for 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, etc., and executes various information processing operations based on these stored programs.

[0028] In terms of functional concept, the control unit 102 comprises a transaction data output unit 102a (including the transaction extraction unit, settlement detail extraction unit and display processing unit of the present invention) and a settlement data creation processing unit 102b (including the 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 from the settlement detail data 106b for which the target category has been carried over and the carryover settlement date has not been set, and (3) displays 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 on the settlement data creation processing screen MA, in association with the selectable target category as installment contract, transaction type, settlement amount, and affiliated store.

[0030] The transaction data output unit 102a executes the processes (11) to (13). (11) The settlement data creation processing screen MA is displayed on the monitor 114, and the person in charge sets the settlement date in the area MA11 and presses the display button MA12. (12) By referring to the settlement details data 106b, records in which the target category is "1: Carryover" and the carryover settlement date is "NULL" are extracted and displayed in area MA2 of the settlement data creation processing screen MA. (13) The transaction data 106a and the settlement detail data 106b are compared, and data stored only in the transaction data 106a in which the contract identification information and transaction type do not match is extracted and displayed 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 details data 106b, (3) if the transaction type included in the generated record is cancellation, extracts from the settlement details 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 details data 106b. (5) if a record is extracted, the settlement date included in the extracted record is set as the carryover settlement date in 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 carryover settlement date in the extracted record, and (6) from the settlement detail data 106b, the settlement amounts included in records whose settlement date matches the settlement date displayed on the settlement data creation processing screen MA and whose target category is set to "settled" are aggregated by settlement date and affiliated store, 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 processing is not performed on the set settlement date of MA11 and is carried over to the next time, and "Exclude" is selected when the settlement process has been completed by another process (processing outside the system).

[0033] When "target" is selected in the target category of the 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 details data 106b based on the display information as “target category = target” on the settlement date set in area MA11, and the settlement details data 106b is created. (22) If the record (hereinafter referred to as the original record) in the settlement detail data 106b that is the basis for the record registered as “target” in the target category of area MA21 in (21) is “target category = carryover”, the settlement date of the original record is stored in the item name “carryover 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. (23) Based on the settlement details data 106b for "target category = target" 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 the settlement details data 106b based on the display information as "Target category = Carryover" on the settlement date set in area MA11, and the settlement details data 106b is created. (32) If the original record of a record registered as "Carryover" in the target category of area MA21 in (31) has "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. Note that since the "Target category = Target" is not set in the settlement detail data 106b, 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 performs the processes (41) and (42). (41) The data registered as “Excluded” in the target category of area MA21 is stored in the settlement details data 106b based on the display information as “Target category = Excluded” on the settlement date set in area MA11, and the settlement details data 106b is created. (42) If the original record of the record registered as "Excluded" in the target category of area MA21 in (41) is "Target category = Carryover," the settlement date of the original record is stored in the item name "Carryover 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" is not set in the settlement detail data 106b, settlement data 106c is not created.

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

[0037] 1. Prerequisites (see Figure 7) First, a sales contract (purchase contract) is concluded between the affiliated store and the customer, the customer applies to use the installment payment service, an installment contract is concluded between the credit company etc. and the customer, and a reimbursement transaction between 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, because a reimbursement transaction has occurred, records of settlement detail data 106b and settlement data 106c have not yet been created.

[0038] 2. Reimbursement 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 instructs the display of the settlement data processing screen MA.

[0040] The transaction data output unit 102a causes the monitor 114 to display the 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] The transaction data output unit 102a then collates the transaction data 106a with the settlement detail data 106b, extracts the contract numbers "100," "101," and "200" and the transaction type "Advance Execution," for which no records exist in the settlement detail data 106b, and displays them in area MA2. Note that, because no records exist in the settlement detail data 106b, records for which the target category is "1: Carryover" and the carryover settlement date is "NULL" are not extracted from the settlement detail data 106b.

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

[0044] Then, in the settlement detail data 106b, the settlement data creation processing unit 102b stores, as a record for contract number "100," the settlement date "2022 / 10 / 11" set by the person in area MA11 in the "Settlement Date" field, "0: Target" registered in the target category in area MA21 in the "Target Category" field, "Advance Payment Execution" displayed in area MA23 in the "Transaction Type" field, "NULL" in the "Carryover Settlement Date" field, "NULL" in the "Carryover Settlement Date" field, the affiliated store number "10001" displayed in area MA25 in the "Affiliated Store" field, and "200,000 yen" displayed in area MA24 in the "Settlement Amount" field. The settlement data creation processing unit 102b performs similar processing for 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 references the settlement detail data 106b, extracts records for contract numbers "100," "101," and "200" where "target category = target," and aggregates them by affiliated store number "10001" and affiliated store number "10002" because they all have the same settlement date, "2022 / 10 / 11." The settlement data creation processing unit 102b adds up the settlement amount "200,000 yen" for contract number "100," which is affiliated store number "10001," and the settlement amount "300,000 yen" for 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 processing for the member store "10002" as for the member store "10001", but does not perform summation processing of the settlement amounts because there is only one record (see FIG. 8).

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

[0047] The person in charge instructs the display of the settlement data processing screen MA.

[0048] The transaction data output unit 102a causes the monitor 114 to display the 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 compares the transaction data 106a with the settlement detail data 106b, extracts records for contract number "100," transaction type "cancellation," and contract number "300," transaction type "advance payment execution," 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 for which the target category is "1: carryover" and the carryover settlement date is "NULL."

[0051] The person in charge 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, in the settlement detail data 106b, the settlement data creation processing unit 102b stores, as a record for contract number "100," the settlement date "2022 / 11 / 11" set by the person in charge in area MA11 in the item name "Settlement Date," "0: Target" registered in the target category in 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," "NULL" in the item name "Carryover Settlement Date," the affiliated store number "10001" displayed in area MA25 in the item name "Affiliated Store," and "-200,000 yen" displayed in area MA24 in the item name "Settlement Amount." The settlement data creation processing unit 102b performs similar processing for contract number "300" to create the settlement detail data 106b shown in Figure 9.

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

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

[0055] The person in charge instructs the display of the settlement data processing screen MA.

[0056] The transaction data output unit 102a causes the monitor 114 to display the 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 compares the transaction data 106a with the settlement detail data 106b, extracts a record with contract number "300" and transaction type "cancellation" for which no record exists in the settlement detail data 106b, and displays it in area MA2. Note that no record is extracted from the settlement detail data 106b because there is no record in the settlement detail data 106b for which the target category is "1: Carryover" and the carryover settlement date is "NULL."

[0059] The person in charge selects "Carryover" as the target category in area MA21 for the data of contract number "300" to be settled, displayed in area MA2 of the settlement data processing screen MA, registers it, 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 with "target category = target" and the settlement date "2022 / 12 / 11" set in area MA11 by the person in charge this time, does not store the record in the settlement data 106c (see Figure 10).

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

[0063] The person in charge instructs the display of the settlement data processing screen MA.

[0064] The transaction data output unit 102a causes the monitor 114 to display the 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] 11, the transaction data output unit 102a references the settlement detail data 106b, extracts records for 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 settlement date "NULL," carryover settlement date "NULL," affiliated store "10001," settlement amount "-1,000,000 yen"), and displays them in area MA2. Furthermore, the transaction data output unit 102a compares the transaction data 106a and the settlement detail data 106b, extracts the contract number "301" and transaction type "Advance payment execution," for which no record exists in the settlement detail data 106b, and displays them in area MA2.

[0067] The person in charge 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 area MA11 to the carryover settlement date of the record containing the carryover source settlement date "2022 / 12 / 11" and target category "1: Carryover" of the settlement detail data 106b, and creates a new record with contract number "300", with the settlement date "2023 / 01 / 11" set in area MA11 by the person in charge in the item name "Settlement Date" and the "0: Target Category" registered in the target category of area MA21 in the item name "Target Category". " is stored in the field name "Transaction type", "Cancellation" displayed in area MA23 is stored in the field name "Original carryover settlement date", 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 field name "Original carryover settlement date", "NULL" is stored in the field name "Affiliated store", the affiliated store number "10001" displayed in area MA25 is stored in the field name "Affiliated store", and "-1,000,000 yen" displayed in area MA24 is stored in the field name "Settlement amount" (see Figure 12).

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

[0070] Next, the settlement data creation processing unit 102b references the settlement detail data 106b, extracts and aggregates records of contract numbers "300" and "301" that have "target category = target," have the settlement date "2023 / 01 / 11" set by the person in charge this time in area MA11, and are common to the affiliated store number "10001." The settlement data creation processing unit 102b adds up the settlement amount "-1,000,000 yen" for contract number "300" and the settlement amount "1,500,000 yen" for 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 Figure 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 carried out.

[0072] The transaction data output unit 102a performs the same processing 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", "NULL" in the item name "Carryover Settlement Date", 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 finds that there is no record with "target category = target" and the settlement date "2023 / 02 / 11" set by the person in charge in area MA11 this time, so it does not create a record in the settlement data 106c (see Figure 13).

[0074] 7. Carrying forward carried-over details (Figures 14 and 15) Assuming that no new transactions have occurred, further carryover processing will be carried out.

[0075] The person in charge instructs the display of the settlement data processing screen MA.

[0076] The transaction data output unit 102a causes the monitor 114 to display the 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 in Figure 14, the transaction data output unit 102a refers to the settlement detail data 106b, extracts records where 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 person in charge selects "Carryover" as the target category in area MA21 for the data of contract number "301" to be settled, displayed in area MA2 of the settlement data processing screen MA, registers it, 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 as 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 creates a new record for contract number "301" by setting the settlement date "2023 / 03 / 11" set in the area MA11 by the person in charge in the item name "Settlement Date" and the "1: Carryover" registered in the target category of the area MA21 in the item name "Target Category". " is stored in the field name "Transaction type", "Cancellation" displayed in area MA23 is stored in the field name "Original carryover settlement date", 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 field name "Original carryover settlement date", "NULL" is stored in the field name "Affiliated store", the affiliated store number "10001" displayed in area MA25 is stored in the field name "Affiliated store", and "-1,500,000 yen" displayed in area MA24 is stored in the field name "Settlement amount" (see Figure 15).

[0081] Next, the settlement data creation processing unit 102b refers to the settlement detail data 106b and finds that there is no record with "target category = target" and the settlement date "2023 / 03 / 11" set by the person in charge in area MA11 this time, so it 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, an "exclusion" process will be implemented to prevent double settlements.

[0083] The person in charge instructs the display of the settlement data processing screen MA.

[0084] The transaction data output unit 102a causes the monitor 114 to display the 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 in 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 "Cancel", 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 "Exclude" as the target category in area MA21 for the data of contract number "301" to be settled, displayed in area MA2 of the settlement data processing screen MA, registers it, 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 as the carryover settlement date of the record containing the carryover source settlement date "2023 / 03 / 11" and target category "1: Carryover" of the settlement detail data 106b, and creates a new record for contract number "301" with the settlement date "2023 / 04 / 11" set in the area MA11 by the person in charge in the item name "Settlement Date" and the item name "Target Category" set to "2: Exclusion" registered in the target category of the area MA21. " is stored in the field name "Transaction type", "Cancellation" displayed in area MA23 is stored in the field name "Original carryover settlement date", 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 field name "Original carryover settlement date", "NULL" is stored in the field name "Affiliated store", the affiliated store number "10001" displayed in area MA25 is stored in the field name "Affiliated store", and "-1,500,000 yen" displayed in area MA24 is stored in the field name "Settlement amount" (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 the settlement details data 106b as an "exclusion" category, and will no longer be subject to settlement.

[0091] As described above, according to this embodiment, when calculating settlement amounts for advances, cancellations, etc., not only is the total settlement amount managed by offsetting advances and cancellations, but settlement detail data 106b also manages the settlement status history for each advance and cancellation, and references transaction data 106a that manages newly occurring transactions. This allows the system to manage settlement items (settled), carryovers (including multiple transactions), and exclusions based on the settings of the person in charge. This allows the system to manage carryovers and exclusions other than those to be settled (settled), preventing non-recovery and enabling rapid and efficient settlement operations. Furthermore, history management also makes it possible to confirm the history of settlement amounts. In other words, according to this embodiment, by managing the history of advance refunds and a wide variety of advance refund patterns on the system, settlement operations can be streamlined and advance refunds can be prevented.

[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 the achievement of SDGs Goals 8 and 9.

[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, which can contribute to the achievement of Goal 16 of the SDGs.

[0095] 5. Other Embodiments The present invention may be implemented 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] Furthermore, 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 can be changed as desired unless otherwise specified.

[0098] Furthermore, with regard to the task support device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0099] For example, all or any part of the processing functions of the business support device 100, particularly the processing functions performed by the control unit, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support device 100 as needed. That is, a computer program for providing 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). The computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0100] This computer program may be stored in an application program server connected to the business support device 100 via any network, and all or part of it may be downloaded as needed.

[0101] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "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] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. 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, can use well-known configurations and procedures.

[0103] The various databases 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 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 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, data, etc.) that causes the device to perform the processes 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 configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0106] The present invention is useful for companies in the financial industry that handle settlement operations for member 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 unit 106 Storage section 106a Transaction Data 106b Settlement details data 106c Settlement Data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. a transaction extraction unit that extracts records relating to unsettled transactions from the transaction data table by linking the installment contract and transaction type together with a transaction data table that manages transaction amounts paid by a credit company to affiliated stores by linking them with installment contracts, transaction types with type values ​​of advance payment and cancellation defined, and affiliated stores, and a settlement details data table that manages settlement amounts by linking them with settlement dates, installment contracts, target categories with category values ​​of settled and carried over defined, transaction types, carryover settlement dates, carryover settlement dates, and affiliated stores, using the installment contract and transaction type; a settlement details extraction unit that extracts, 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 unit that displays, on a predetermined 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) if the transaction type included in the generated record is advance payment, stores the generated record in the settlement details data table; (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 are included in the generated record; if no record is extracted, stores the generated record in the settlement details data table; if a record is extracted, sets the settlement date included in the extracted record as the carryover settlement date in the generated record, stores the generated record after 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 details data table, settlement amounts included in records whose settlement dates match the settlement date displayed on the predetermined 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; 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. The settlement management device according to claim 2,

4. An information processing device, a transaction extraction step for extracting records relating to unsettled transactions from the transaction data table by linking the 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" defined, and affiliated stores, and the settlement details data table, which manages settlement amounts by linking them with settlement dates, installment contracts, target categories with category values ​​of "settled" and "carried over," transaction types, carryover settlement dates, carryover settlement dates, and affiliated stores, by using installment contracts and transaction types; a settlement detail extraction step of extracting, from the settlement detail data table, records for which the target category has been carried over and the carryover settlement date has not been set; a display processing step of displaying on a predetermined screen the combination of installment contract, transaction type, settlement amount and affiliated store contained in the record extracted in the settlement detail extraction step and the combination of installment contract, transaction type, transaction amount and affiliated store contained in the record extracted in the transaction extraction step, in association with selectable target categories as installment contract, transaction type, settlement amount and affiliated store; a settlement management step of (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) if the transaction type included in the generated record is advance payment, storing the generated record in the settlement details data table; (3) if the transaction type included in the generated record is cancellation, extracting 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 are 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 settlement date in the generated record, and 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 in the extracted record; A settlement management method characterized by executing the above.

5. An information processing device a transaction extraction means for extracting records relating to unsettled transactions from the transaction data table by linking the transaction data table, which manages transaction amounts paid by a credit company to affiliated stores, by installment contract, transaction type (with type values ​​of advance payment and cancellation defined) and affiliated stores, with a settlement details data table, which manages settlement amounts by linking them with settlement dates, installment contracts, target categories (with category values ​​of settled and carried over defined), transaction types, carryover settlement dates, carryover settlement dates and affiliated stores, by using installment contracts and transaction types; a settlement details extraction means for extracting, from the settlement details data table, records for 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 the combination of installment contract, transaction type, settlement amount and affiliated store contained in the record extracted by said settlement details extraction means and the combination of installment contract, transaction type, transaction amount and affiliated store contained in the record extracted by said transaction extraction means, in association with selectable target categories as installment contract, transaction type, settlement amount and affiliated store; (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) if the transaction type included in the generated record is advance payment, storing the generated record in the settlement details data table; (3) if the transaction type included in the generated record is cancellation, extracting 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; 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 settlement date in 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 in the extracted record; A settlement management program that functions as a

Images