JP7736745B2 - Account settlement management device, account settlement management method, and account settlement management program - Google Patents

Description

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

Patent Document 1 discloses a prepaid money return management device that enables efficient settlement of advance payments and return management of customer payments in the event of a cancellation of an advance payment.

Japanese Patent Application Laid-Open No. 2019-46237

In an installment contract, companies that handle installment business (hereinafter referred to as credit companies, etc.) pay affiliated stores advances and brokerage fees associated with the sale of goods or the provision of services to users of the installment service. Furthermore, if an installment service user cancels the sale of goods or the 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, additional cancellation fees may also be required.

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 payment 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 carry over the negative elements until the positive elements exceed the negative elements. This is a complicated process, placing a heavy burden on staff, and has led to uncollected advance payments, etc. due to errors.

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

In order to solve the above-mentioned problems and achieve the objectives, the settlement management device of the present invention combines 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 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, by using 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 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 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 is not 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; 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.

The settlement management unit may also aggregate, from the settlement details data table, settlement amounts included 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 affiliated store.

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

In addition, the settlement management method of the present invention has a transaction extraction unit that links a transaction data table that manages transaction amounts paid by credit card companies to affiliated stores 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 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 combining these data by installment contract and transaction type. 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.

The settlement management program of the present invention also uses 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 (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, by linking the transaction data table by installment contract and transaction type. 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.

The present invention has the effect of contributing to the efficiency of credit card companies' settlement operations for affiliated stores.

FIG. 1 is a diagram showing an example of an outline of a contractual relationship. FIG. 2 is a diagram showing an example of an outline of settlement between a credit company and a member store. FIG. 3 is a diagram illustrating an example of the configuration of a task assistance device according to this embodiment. FIG. 4 is a diagram showing an example of transaction data according to the present invention. FIG. 5 is a diagram showing an example of detailed payment data according to the present invention. FIG. 6 is a diagram showing an example of settlement data according to the present invention. FIG. 7 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. 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. 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. 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. 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. FIG. 12 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. 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. 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. FIG. 15 is a diagram showing an example of data for explaining a specific example of processing in this embodiment. 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. FIG. 17 is a diagram showing an example of data for explaining a specific example of processing in this embodiment.

Embodiments of the settlement management device, settlement management method, and settlement management program according to the present invention are described in detail below with reference to the accompanying drawings. Note that the present invention is not limited to these embodiments.

[1. Overview]
Figure 1 shows 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 point the customer offers to pay by installments. The customer then enters into an installment 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 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 previously concluded affiliated store contract (see Figure 1).

Figure 2 is a diagram showing 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 other reason. In such cases, settlement work for advance payments and other payments occurs between the credit company and the member store. Regarding this settlement work, as shown in Figure 2, if a 200,000 yen advance payment 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 work by remitting the offset settlement amount of 800,000 yen to the member store. However, as shown in Figure 2, if a customer's cancellation results in only a 200,000 yen advance payment refund and no new advance payment is incurred, 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 can be managed within the system.

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.

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, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The business assistance device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the business assistance device 100 is connected to each other so that they can communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the business support 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 the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the business support 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 also be stored in the server 200, for example.

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 functions as a pointing device in conjunction with a mouse. Note that, below, 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.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. 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, or an optical disk.

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), and settlement data 106c (corresponding to the settlement data table of the present invention), etc.

Transaction data 106a is used to manage transactions between credit card companies and affiliated stores. As shown in Figure 4, transaction data 106a stores contract identification information (e.g., contract number), the type of transaction between credit card companies and affiliated stores (e.g., transaction type), transaction amount, and affiliated store identification information (e.g., affiliated store code, affiliated store name). Transaction data 106a manages transaction amounts paid by credit card companies to affiliated stores, linking them to installment contracts, transaction types where type values are defined as advance payment and cancellation, and affiliated stores.

Settlement statement data 106b is used to manage the settlement status of each transaction between a credit company and an affiliated store. As shown in Figure 5, settlement statement data 106b stores the settlement date, contract identification information, processing category (e.g., target category) for identifying the processing of the transaction, the type of transaction between the credit company and the affiliated store, carryover settlement date, carryover settlement date, affiliated store identification information, and settlement amount. Settlement statement data 106b manages settlement amounts by linking them to the settlement date, installment contract, target category (with defined category values of settled, carried over, and excluded (categorization value meaning that the settlement amount has been excluded from settlement management)), transaction type, carryover settlement date, carryover settlement date, and affiliated store.

Settlement data 106c is used to manage settlement amounts for each settlement date and affiliated store. As shown in Figure 6, settlement data 106c stores the settlement date, affiliated store identification information, settlement amounts, etc. Settlement data 106c manages settlement amounts for each settlement date and affiliated store.

Returning to Figure 3, the control unit 102 is a CPU or the like that provides overall control of the business assistance device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

In terms of functional concept, the control unit 102 includes 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).

The transaction data output unit 102a (1) extracts transaction records for 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, assembling them as installment contract, transaction type, settlement amount, and affiliated store with the selectable target category.

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 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) Compare the transaction data 106a and the settlement detail data 106b, extract data stored only in the transaction data 106a where 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.

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. If no record is extracted, the generated record is stored 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 this setting is stored in the settlement details data 106b, and the settlement date included in the generated record is set as the carryover settlement date in the extracted record; (6) from the settlement details 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.

The settlement data creation processing unit 102b selects and registers "Target," "Carryover," or "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 will not be performed on the set settlement date of MA11 and will be carried over to the next time, and "Exclude" is selected when settlement processing has been completed by another process (processing outside of the system).

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) 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 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.

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 the 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 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.

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) 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 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) has "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" of the settlement detail data 106b is not set, settlement data 106c is not created.

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

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 an advance payment 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, since an advance payment transaction has occurred, records of settlement detail data 106b and settlement data 106c have not yet been created.

2. Reimbursement of expenses (see Figure 8)
The advance payment settlement process for the advance payment transaction of the prerequisite items shown in FIG. 7 is carried out.

The person in charge will instruct the system to display the settlement data processing screen MA.

The transaction data output unit 102a displays the settlement data processing screen MA on the monitor 114.

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

The transaction data output unit 102a then compares 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 with the target category "1: Carryover" and the carryover settlement date set to "NULL" are not extracted from the settlement detail data 106b.

The person in charge selects "Target" as the target category in area MA21 for the data for 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, then presses the settlement button MA3.

The settlement data creation processing unit 102b then stores in the settlement detail data 106b, as a record for contract number "100", the settlement date "2022/10/11" set by the person in area MA11 in the item name "Settlement date", "0: Target" registered in the target category of area MA21 in the item name "Target category", "Advance payment executed" 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 on contract numbers "101" and "200" to create the settlement detail data 106b shown in Figure 8.

Next, the settlement data creation processing unit 102b references the settlement detail data 106b and extracts records for contract numbers "100," "101," and "200" where "Target category = Target." Since the settlement date is the same, "2022/10/11," the data is aggregated by affiliated store number "10001" and affiliated store number "10002." The settlement data creation processing unit 102b adds up the settlement amount of "200,000 yen" for contract number "100" with affiliated store number "10001" and the settlement amount of "300,000 yen" for contract number "101," and stores the settlement date of "2022/10/11," affiliated store "10001," and settlement amount of "500,000 yen" in the settlement data 106c (see Figure 8). Additionally, the settlement data creation processing unit 102b performs the same processing for member store "10002" as for member store "10001", but does not perform summation of settlement amounts because there is only one record (see Figure 8).

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

The person in charge will instruct the system to display the settlement data processing screen MA.

The transaction data output unit 102a displays the settlement data processing screen MA on the monitor 114.

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

The transaction data output unit 102a then compares the transaction data 106a and the settlement detail data 106b, extracts records for contract number "100" and transaction type "Cancellation" and contract number "300" and transaction type "Advance Execution", for which no records exist in the settlement detail data 106b, and displays these records in area MA2. Note that 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", no records are extracted from the settlement detail data 106b.

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

The settlement data creation processing unit 102b then stores, in the settlement statement data 106b, the following record for contract number "100": the settlement date "2022/11/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; "Cancellation" displayed in area MA23 in the "Transaction Type" 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 number "300" and creates the settlement statement data 106b shown in FIG. 9.

Next, the settlement data creation processing unit 102b references the settlement detail data 106b, extracts and aggregates records with contract numbers "100" and "300" that are in "target category = target," have the settlement date "2022/11/11" set by the person in charge in area MA11, and are common to member 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," member store "10001," and settlement amount "800,000 yen" in the settlement data 106c (see Figure 9).

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.

The person in charge will instruct the system to display the settlement data processing screen MA.

The transaction data output unit 102a displays the settlement data processing screen MA on the monitor 114.

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

The transaction data output unit 102a then compares the transaction data 106a and the settlement detail data 106b, extracts a record with contract number "300" and transaction type "Cancel", 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 with the target category set to "1: Carryover" and the carryover settlement date set to "NULL".

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

The settlement data creation processing unit 102b then 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 area MA11 in the "Settlement Date" field, "1: Carryover" registered in the target category of area MA21 in the "Target Category" field, "Cancellation" 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 "-1,000,000 yen" displayed in area MA24 in the "Settlement Amount" field (see Figure 10).

Next, the settlement data creation processing unit 102b references the settlement detail data 106b and, since there is no record with "Target Category = Target" and the settlement date "2022/12/11" currently set by the person in charge in area MA11, does not store the record in the settlement data 106c (see Figure 10).

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

The person in charge will instruct the system to display the settlement data processing screen MA.

The transaction data output unit 102a displays the settlement data processing screen MA on the monitor 114.

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

As shown on the settlement data creation processing screen MA in FIG. 11, the transaction data output unit 102a then references the settlement details data 106b, extracts records with a target category of "1: Carryover" and a carryover settlement date of "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 these in 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 "Advance payment execution," for which no record exists in the settlement details data 106b, and displays these in area MA2.

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

The settlement data creation processing unit 102b then sets the settlement date "2023/01/11" set in area MA11 as the carryover settlement date for the record containing the carryover source settlement date "2022/12/11" and target category "1: Carryover" in the settlement detail data 106b, and creates a new record with contract number "300" with the settlement date "2023/01/11" set by the person in charge in area MA11 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". ", the "Transaction Type" item name stores "Cancellation" displayed in area MA23, the "Carryover Settlement Date" item name stores the settlement date "2022/12/11" of the original record (a record with target category "1: Carryover" and a carryover settlement date of "NULL"), the "Carryover Settlement Date" item name stores "NULL", the "Affiliated Store" item name stores the affiliated store number "10001" displayed in area MA25, and the "Settlement Amount" item name stores "-1,000,000 yen" displayed in area MA24 (see Figure 12).

Next, for contract number "301," 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 (see Figure 12).

Next, the settlement data creation processing unit 102b references the settlement detail data 106b, extracts and aggregates records for contract numbers "300" and "301" that have "target category = target," have the settlement date "2023/01/11" set by the person in charge in area MA11, and share 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," affiliated store "10001," and settlement amount "500,000 yen" in the settlement data 106c (see Figure 12).

6. Carryover (Figure 13)
As a premise, a cancellation has occurred for the contract with contract number "301" for which advance payment processing has already been executed.

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 area MA11 in the "Settlement Date" field, "1: Carryover" registered in the target category of area MA21 in the "Target Category" field, "Cancellation" 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 "-1,500,000 yen" displayed in area MA24 in the "Settlement Amount" field (see Figure 13).

Next, the settlement data creation processing unit 102b references the settlement detail data 106b and, since there is no record with "Target Category = Target" and the settlement date "2023/02/11" currently set by the person in charge in area MA11, does not create a record in the settlement data 106c (see Figure 13).

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

The person in charge will instruct the system to display the settlement data processing screen MA.

The transaction data output unit 102a displays the settlement data processing screen MA on the monitor 114.

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

Then, as shown on the settlement data creation processing screen MA in Figure 14, the transaction data output unit 102a references 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 settlement date "NULL", carryover settlement date "NULL", affiliated store "10001", settlement amount "-1,500,000 yen"), and displays them in area MA2.

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

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

Next, the settlement data creation processing unit 102b references the settlement detail data 106b and, since there is no record with "Target Category = Target" and the settlement date "2023/03/11" currently set by the person in charge in area MA11, does not create a record in the settlement data 106c (see Figure 15).

8. Exclusion (Figures 16 and 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.

The person in charge will instruct the system to display the settlement data processing screen MA.

The transaction data output unit 102a displays the settlement data processing screen MA on the monitor 114.

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

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

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

The settlement data creation processing unit 102b then sets the settlement date "2023/04/11" set in area MA11 as the carryover settlement date for the record containing the carryover source settlement date "2023/03/11" and target category "1: Carryover" in the settlement detail data 106b, and creates a new record for contract number "301", with the settlement date "2023/04/11" set by the person in charge in area MA11 in the item name "Settlement Date" and the "2: Exclusion" registered in the target category of area MA21 in the item name "Target Category". " is stored in the "Transaction Type" field, "Cancellation" displayed in area MA23 is stored in the "Carryover Settlement Date" field, 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 "Carryover Settlement Date" field, "NULL" is stored in the "Carryover Store" field, the member store number "10001" displayed in area MA25 is stored in the "Affiliated Store" field, and "-1,500,000 yen" displayed in area MA24 is stored in the "Settlement Amount" field (see Figure 17).

Next, the settlement data creation processing unit 102b references the settlement detail data 106b and, since there is no record with "Target category = Target" in the record for the settlement date "2023/04/11" set by the person in charge in area MA11, no record is created in the settlement data 106c (see Figure 17).

As a result of this processing, contract number "301" is stored in the settlement details data 106b as an "excluded" category, and will no longer be subject to settlement.

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

[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.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

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.

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.

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

Furthermore, with regard to the business support device 100, the components shown in the figure are functional concepts and do not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the business support device 100, particularly the processing functions performed by the control unit, may be implemented in whole or in part by a CPU and a program interpreted and executed by the CPU, 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. In other words, a computer program that works in conjunction with the OS to issue commands to the CPU and perform 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 RAM, and works in conjunction with the CPU to form the control unit.

This computer program may also be stored on 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.

In addition, the program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure 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 structures and procedures.

The various databases stored in the memory unit are storage devices 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 website provision.

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 such an information processing device to which any peripheral device is connected. The business support device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

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

This invention is useful for companies in the financial industry that handle settlement operations for affiliated stores, such as credit card companies.

100 Business support device 102 Control unit
102a Transaction data output unit
102b settlement data creation processing unit 104 communication interface unit 106 storage unit
106a Transaction Data
106b Settlement details data
106c settlement data 108 input/output interface unit 112 input device 114 output device 200 server 300 network

Claims (5)

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: 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 . 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, The 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. 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;
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) 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 program that functions as a