Deposit clearing device, deposit clearing method, and deposit clearing program

Abstract

To realize payment settlement with high accuracy and low workload even when the source of payment for receivables changes each time. [Solution] According to this embodiment, the deposit reconciliation device comprises: a deposit input means for creating deposit data including the deposit date, specific information, deposit amount, reconciled deposit amount, and customer classification obtained from the billing master using the specific information as a key; and a reconciliation means for aggregating the scheduled collection amounts of the collection schedule data by scheduled collection date in the receivables master, in order of customer granularity specified in the customer classification of the deposit data to customer granularity decreasing, excluding records other than the customer classification of the receivables origination reason master linked to the reason for the receivable of the collection schedule data, creating reconciliation candidate pattern list data, and comparing the scheduled collection amounts and deposit amounts in the reconciliation candidate pattern list data in order of customer granularity decreasing, and performing automatic reconciliation.

Description

[Technical Field]

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

[0002] For example, when a gaming manufacturer installs or replaces a gaming machine in a hall (store), it performs a payment reconciliation operation for the relevant receivable when a payment is received from the payment source. For example, Patent Document 1 is an example of a conventional payment reconciliation system. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-46887 Summary of the Invention [Problem to be solved by the invention]

[0004] However, while invoices are sent to each hall or to the address agreed upon at the time of the contract, the source of payment can change depending on the reason for establishment or replacement, such as the hall, corporation, or affiliated corporation. As the source of payment changes each time, there is an issue of increased workload and burden on the person in charge of reconciling payments.

[0005] The present invention has been made in consideration of the above, and aims to provide a deposit reconciliation device, a deposit reconciliation method, and a deposit reconciliation program that can achieve deposit reconciliation with high accuracy and low workload, even when the source of the deposit for the receivable changes each time. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a payment clearing device equipped with a control unit, wherein the control unit is configured to be able to access a billing destination master in which specific information for identifying a business partner from which a payment is made for a credit, one or more business partners, and a business partner classification for specifying the granularity of the business partners are associated and registered, a credit origination reason master in which the reason for the credit origination is associated and registered with the business partner classification, and collection schedule data including multiple business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for the credit origination, and the payment clearing device is configured to be able to access a billing destination master in which specific information for identifying a business partner from which a payment is made for a credit, one or more business partners, and a business partner classification for specifying the granularity of the business partners are associated and registered, and a payment schedule data including multiple business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for the credit origination, and the payment clearing device is configured to The system is characterized by comprising: a deposit input means for creating deposit data including the customer classification obtained from the customer request master; and a clearing means for aggregating, in the receivables master, the scheduled collection amounts of the collection schedule data by the scheduled collection date, in order from the customer with the highest granularity specified in the customer classification of the deposit data to the customer with the lowest granularity, excluding records other than the customer classification of the receivables origination reason master linked to the reason for the receivable origination of the collection schedule data, to create a list data of possible clearing patterns, and comparing the scheduled collection amounts of the clearing candidate pattern list data with the deposit amounts in order of the highest granularity of the customer, and performing automatic clearing.

[0007] According to another aspect of the present invention, the automatic clearing may update the collected amount in the collection schedule data and the cleared amount of the deposit data.

[0008] According to one aspect of the present invention, the business partners and business partner categories may include affiliated corporate groups, corporations, area groups, and stores, the granularity of the business partners may be in the order of affiliated corporate groups > corporations > area groups > stores, and the party to whom the receivables are billed may be the store.

[0009] According to another aspect of the present invention, the claim may be a claim relating to the installation or replacement of a gaming machine or a gaming table in the store.

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the object, the present invention provides a method of clearing a deposit executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a billing destination master in which specific information for identifying a business partner from which a deposit for a debt is made, one or more business partners, and a business partner classification for specifying a granularity of the business partners are associated and registered, a debt origination reason master in which a debt origination reason and a business partner classification are associated and registered, and collection schedule data including a plurality of business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for the debt, and the control unit executes a method of clearing a deposit by using the deposit date, the specific information, the deposit amount, and the cleared deposit amount. and a payment input process for creating payment data including the customer classification obtained from the invoice master using specific information as a key; and a reconciliation process for aggregating, in the invoice master, the scheduled payment amounts of the payment schedule data by the scheduled payment date, in order from the customer with the highest granularity specified in the customer classification of the payment data to the customer with the lowest granularity, excluding records other than the customer classification of the credit origination reason master linked to the credit origination reason of the payment schedule data, to create a list data of possible reconciliation patterns, and comparing the scheduled payment amounts of the payment schedule data and the payment amounts in the list data of possible reconciliation patterns in order of the customer granularity to perform automatic reconciliation.

[0011] Furthermore, in order to solve the above-mentioned problems and achieve the object, the present invention provides a payment clearing program to be executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a billing destination master in which specific information for identifying a business partner from which a payment is made for a receivable, one or more business partners, and a business partner classification for specifying the granularity of the business partners are associated and registered, a receivable origination reason master in which the reason for the receivable origination is associated and registered with the business partner classification, and scheduled collection data including multiple business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for the receivable origination, and the control unit is configured to access a billing destination master in which the specific information for identifying a business partner from which a payment is made for a receivable, one or more business partners, and a business partner classification for specifying the granularity of the business partners are associated and registered, and and a reconciliation step of: aggregating, in the invoice master, the scheduled collection amounts of the collection schedule data by the scheduled collection date, from the customer with the highest granularity specified in the customer classification of the collection data to the customer with the lowest granularity, excluding records other than the customer classification of the credit origination reason master linked to the credit origination reason of the collection schedule data, to create reconciliation candidate pattern list data; and comparing the scheduled collection amounts of the reconciliation candidate pattern list data with the deposit amount in order of the customer granularity largest to smallest, and performing automatic reconciliation. [Effects of the Invention]

[0012] According to the present invention, it is possible to realize high-precision reconciliation of payments with low operational load, even when the source of payment for receivables changes each time. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a deposit clearing device according to this embodiment. [Figure 2] FIG. 2 is a flowchart illustrating the overall processing flow of the control unit of the deposit clearing device according to this embodiment. [Figure 3] FIG. 3 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 8] FIG. 8 is a flowchart illustrating the overall processing flow of the control unit of the deposit clearing device according to this embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the processing of the control unit of the deposit clearing device according to the present embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 12] FIG. 12 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to this embodiment. [Figure 13] FIG. 13 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 14] FIG. 14 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 15] FIG. 15 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 16] FIG. 16 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 17] FIG. 17 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 18]FIG. 18 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 19] FIG. 19 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 20] FIG. 20 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 21] FIG. 21 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 22] FIG. 22 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 23] FIG. 23 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. [Figure 24] FIG. 24 is a diagram for explaining a specific example of the process of the control unit of the deposit clearing device according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of a deposit clearing device, a deposit clearing method, and a deposit clearing program according to the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to these embodiments.

[0015] [1. Overview] The outline of the present invention will be explained in the order of "Background," "Problem," and "Solution."

[0016] [background] For example, when a gaming machine manufacturer installs or replaces gaming machines in a hall, there are various reasons for this, such as the store's decision, the corporation's decision, or the decision of an affiliated corporation. Depending on the reason for this installation or replacement, the source of payment after invoicing may change. Invoices are sent to each store or to an address agreed upon at the time of contract, but the source of payment will change depending on the reason for installation or replacement, such as the store, corporation, or affiliated corporation.

[0017] [assignment] When an invoice is sent and payment is received from the invoice recipient, it is possible to clear the amount of debt accrued to that invoice recipient. However, when payments are received from the recipient in any lump sum, such as from the hall alone, the corporation combined, or affiliated corporations combined, it is not possible to determine which debt the payment is for, which requires the person in charge to make a judgment, resulting in a heavy workload for the payment clearing process.

[0018] [Solution] Therefore, in this embodiment, the amount of receivables and the amount of receipts are checked in the order of the granularity (hierarchy) of the business partners (for example, in the order of affiliated corporation > corporation > area > store), and reconciliation is performed automatically.Furthermore, by focusing on the fact that the source of payment after the invoice is sent changes depending on the reason for the receivables, if the reason for the receivables is clear, the receivables are excluded from the candidates for reconciliation, and automatic reconciliation is possible, thereby improving reconciliation accuracy and reducing the workload of reconciliation work.

[0019] In the example below, we will explain a case where a gaming machine manufacturer notifies an invoice to a store and the payment is made from a different business partner (source of payment), but the present invention is not limited to this, and the source of payment after invoicing may change depending on the reason for installation or replacement for manufacturers of game machines installed in stores, ticket vending machines installed in stores, and payment machines installed in coin parking lots, etc., and the present invention can be applied to these cases as well, and can be widely applied to cases where the source of payment for receivables changes from time to time.

[0020] [2. Configuration] An example of the configuration of the deposit reconciliation device 100 according to this embodiment will be described with reference to FIG. 1. FIG. 1 is a block diagram showing an example of the configuration of the deposit reconciliation device 100. In the following, an example will be described in which the deposit reconciliation device 100 is applied to a gaming machine manufacturer. The example will be described in which the gaming machine manufacturer installs or replaces gaming machines in an arcade, notifies the arcade of an invoice, and receives payment from a different business partner (deposit source).

[0021] The reconciliation device 100 is, for example, a commercially available desktop personal computer or workstation.

[0022] The deposit reconciliation device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108. The units comprised in the deposit reconciliation device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0023] The communication interface unit 104 communicatively connects the deposit reconciliation 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 communicatively connecting the deposit reconciliation device 100 with the server 200 and a bank system (not shown), and is, for example, the Internet or a LAN (Local Area Network). Note that data such as various masters described below may be stored in the server 200, for example.

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

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

[0026] The storage unit (storage area) 106 stores, for example, a billing destination master 106a, a debt origination reason master 106b, collection schedule data, and deposit data.

[0027] The billing destination master 106a is a master for setting specific information for identifying the business partner from which the receivables are received, one or more business partners, and a business partner classification for specifying the granularity of the business partners. The billing destination master 106a can be configured from a table or the like that associates and registers specific information (store code, store name), affiliated corporation group code, affiliated corporation group name, corporation code, corporation name, area group code, area group name, and business partner classification (see Figure 3).

[0028] The debt origination reason master 106b is a master that sets the customer classification for each debt origination reason, and for that reason, only that customer classification will be the customer (source of payment). The debt origination reason master 106b can be configured as a table that associates and registers the debt origination reason (debt origination reason code, debt origination reason name) and transaction debt classification (debt origination reason code, debt origination reason name) (see Figure 4).

[0029] The collection schedule data may include the billing number, store (store code and / or store name), affiliated corporate group (affiliated corporate group code and / or legally affiliated group name), corporation (corporate code and / or corporation name), area group (area group code and / or area group name), scheduled collection date, amount scheduled to be collected, amount already collected, and reason for the debt (see Figure 5).

[0030] The deposit data may include the deposit number, deposit date, specific information (store code, store name), deposit method, deposit amount, cleared deposit amount, and customer classification (see FIG. 6).

[0031] The control unit 102 is a CPU or the like that performs overall control of the deposit clearing 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.

[0032] The control unit 102 is configured to be able to access the billing destination master 106a, the debt origination reason master 106b, collection schedule data, deposit data, etc. stored in the storage unit 106. The billing destination master 106a, the debt origination reason master 106b, the collection schedule data, the deposit data, etc. may be stored in another location (for example, the server 200) as long as the control unit 102 can access them.

[0033] The control unit 102 conceptually includes a master maintenance unit 102a, a collection schedule data creation unit 102b, a deposit processing unit 102c, a reconciliation processing unit 102d, and a screen display control unit 102e.

[0034] The master maintenance unit 102a performs editing such as inputting, adding, and changing data in the billing destination master 106a and the debt origination reason master 106b, for example, in response to operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

[0035] The collection schedule data creation unit 102b creates collection schedule data including multiple business partners, scheduled collection dates, scheduled collection amounts, already collected amounts, and reasons for the debt, for example, in response to operator operations on an input screen (not shown) displayed on the monitor 114, and stores the data in the memory unit 106.

[0036] The deposit processing unit 102c downloads and imports transfer data from a bank system (for example, an EB system or an Internet banking system), identifies the source of the deposit, and Using the source of the deposit (specific information) as a key, the customer classification is obtained from the billing master 106a, and deposit data including the deposit date, specific information (e.g., store), deposit amount, deposit reconciliation amount, and the obtained customer classification is created and stored in the memory unit 106.

[0037] The reconciliation processing unit 102d aggregates the scheduled collection amounts of the collection schedule data by scheduled collection date in the billing destination master 106a, starting from the customer with the granularity specified in the customer classification of the deposit data and ending with the smallest granularity, and creates a list of reconciliation candidate patterns by excluding records other than the customer classification in the debt origination reason master 106b linked to the debt origination reason of the collection schedule data, and performs automatic reconciliation by comparing the scheduled collection amounts and the deposit amounts in the reconciliation candidate pattern list data in descending order of customer granularity. During automatic reconciliation, the collected amounts of the collection schedule data and the reconciled deposit amounts of the deposit data are updated.

[0038] The screen display control unit 102e controls the display of various screens (for example, a master maintenance screen, a collection schedule data input screen, etc.) displayed on the monitor 114 and the reception of inputs.

[0039] [3. Specific Examples] A specific example of the processing by the control unit 102 of the deposit clearing device 100 in this embodiment will be described with reference to Figures 1 to 24. Figures 2 to 24 are diagrams for explaining a specific example of the processing by the control unit 102 of the deposit clearing device 100 in this embodiment.

[0040] [3-1. Processing flow] 2 is a diagram for explaining the overall processing flow of the control unit 102 of the deposit reconciliation device 100 in this embodiment. The overall processing flow of the control unit 102 of the deposit reconciliation device 100 in this embodiment will be described with reference to FIG.

[0041] The collection schedule data creation unit 102b creates collection schedule data including multiple business partners, scheduled collection dates, scheduled collection amounts, already collected amounts, and reasons for the debt, for example, in response to operator operations on an input screen (not shown) displayed on the monitor 114, and stores the data in the memory unit 106.

[0042] The deposit processing unit 102c downloads and imports transfer data from a bank system (for example, an EB system or an Internet banking system), identifies the source of the deposit, and Using the source of payment (specific information) as a key, the customer classification is obtained from the billing master 106a, and payment data including the payment date, specific information (e.g., store), payment amount, payment clearing amount, and the obtained customer classification is created and stored in the storage unit 106. For example, the customer classifications are 0: affiliated corporate group, 1: corporation, 2: area group, and 3: store.

[0043] The reconciliation processing unit 102d aggregates the scheduled collection amounts of the collection schedule data by scheduled collection date in the billing destination master 106a, starting with the customer with the granularity specified in the customer classification of the deposit data and then descending to the customer with the smallest granularity (hierarchy), and creates a list of reconciliation candidate patterns by excluding records other than the customer classification in the debt origination reason master 106b linked to the debt origination reason of the collection schedule data.The reconciliation processing unit 102d then compares the scheduled collection amounts and the deposit amounts in the reconciliation candidate pattern list data in descending order of customer granularity and performs automatic reconciliation. For example, the customer granularity is in the order of affiliated corporate group > corporation > area group > store. For example, if the customer classification is "0: Affiliated corporate group," the transaction will be settled in the order of affiliated corporate group > corporation > area group > store; if the customer classification is "1: Corporation," the transaction will be settled in the order of corporation > area group > store; if the customer classification is "2: Area group," the transaction will be settled in the order of area group > store; and if the customer classification is "3: Store" (when billing destination = payment source), the transaction will be settled for the store.

[0044] [3-2. Sample Data] 3 to 24 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the deposit clearing device 100 in this embodiment. A specific example of the processing by the control unit 102 of the deposit clearing device 100 in this embodiment will be described with reference to FIGS. 3 to 24.

[0045] (Prerequisite data) In the following description, it is assumed that the master and data shown in FIGS. 3 to 5 are stored in the storage unit 106 in advance.

[0046] FIG. 3 is a diagram showing an example of data in the billing destination master 106a. The billing destination master 106a is a master for setting specific information for identifying the business partner from which the receivables are received, one or more business partners, and a business partner classification for specifying the business partner granularity. The billing destination master 106a can be configured from a table or the like that associates and registers store codes, store names, affiliated corporate group codes, affiliated corporate group names, corporate codes, corporate names, area group codes, area group names, and business partner classifications. The "business partner classification" is used to specify the granularity (hierarchy) of business partners (billing destinations), and is 0: affiliated corporate group, 1: corporation, 2: area group, 3: store. The order of granularity is 0: affiliated corporate group > 1: corporation > 2: area group > 3: store.

[0047] In this example, rows 1 to 8 show the case where the source of the receivables is an affiliated corporate group, corporation, or area group, and the specific information for identifying the client from which the receivables are received is a hypothetical store (store = the affiliated corporate group, corporation, or area group from which the receivables are received). For example, row 1 has the store code "SE1000," store name "XX Holdings," affiliated corporate group code "SE1000," legal group name "XX Holdings," and client classification "0: Affiliated Corporate Group." The store is set to the affiliated corporate group. When creating the deposit data, if the source of the deposit is XX Holdings, an affiliated corporate group, the store is set to the XX Holdings Group (specific information), and the client classification "0: Affiliated Corporate Group" is retrieved from the billing master 106a.

[0048] Lines 9 to 17 indicate the case where the source of the deposit is the store (physical store) where the receivable actually occurs, and the affiliated corporate group, corporation, area group, and customer classification are set for the store. In this case, the customer category is set to "3: Store."

[0049] Figure 4 shows an example of data in the debt origination reason master 106b. The debt origination reason master 106b is a master that sets a customer classification for each debt origination reason. For a given reason, only that customer classification is the customer (source of payment). The debt origination reason master 106b can be configured as a table that associates and registers the debt origination reason (debt origination reason code, debt origination reason name) and transaction classification (customer classification code, customer classification name). In the example shown in the figure, for example, the third line has the debt origination reason code "300," the debt origination reason name "Newly established corporation," the customer classification code "1," and the customer classification name "corporation." In the case of a newly established corporation, "corporation" is the source of payment (customer). Similarly, the fifth line has the debt origination reason code "500," the debt origination reason name "Newly established area G," the customer classification code "2," and the customer classification name "Area Group." In the case of "Newly established area G," "Area Group" is the source of payment (customer).

[0050] 5 is a diagram showing an example of collection schedule data. The collection schedule data may include the billing number, store (store code and / or store name), affiliated corporate group (affiliated corporate group code and / or legally affiliated group name), corporation (corporate code and / or corporation name), area group (area group code and / or area group name), scheduled collection date, scheduled collection amount, amount already collected, and reason for debt. Collection schedule data is created each time a debt is incurred. It is created for each affiliated corporate group, corporation, area group, and store linked in the billing destination master 105a.

[0051] In the example shown in the figure, the first line contains the invoice number "SNO1000", store code "SE1111", store name "Sapporo store", affiliated corporate group code "SE1000", legal group name "XX Holdings", corporate code "SE1100", corporate name "□□ Co., Ltd.", area group code "SE1110", area group name "Hokkaido / Tohoku", expected collection date "5 / 31 / 2024", expected collection amount "¥12,000", amount already collected "¥0", and reason for the debt " ".

[0052] Next, examples of a case where a lump sum payment is made from an affiliated corporate group, a case where a lump sum payment is made from a corporation, and a case where a lump sum payment is made from an area group will be described in order.

[0053] (When a lump sum payment is made from a group of affiliated corporations) 6 to 12, we will explain the case where a lump sum payment is made from an affiliated corporate group. FIG. 6 is a diagram showing an example of payment data. The payment data may include the payment number, payment date, store code, store name, payment method, payment amount, reconciled payment amount, and customer classification. The customer classification is obtained from the billing master 106a using the payment source store as a key. In the example shown in the figure, the first line contains the payment number "N1000," payment date "6 / 30 / 2024," store code "SE1000," store name "XX Holdings," payment method "bank transfer," payment amount "¥54,000," reconciled payment amount "¥0," and customer classification "0: affiliated corporate group." The remaining receivables to be reconciled are tallied for the payment from the affiliated corporate group.

[0054] In the billing destination master 106a, the planned collection amounts of the collection schedule data are tallied by the planned collection date, starting from the customer with the smallest granularity specified in the customer classification of the deposit data (in the order of 0: affiliated corporate group > 1: corporation > 2: area group > 3: store), and records other than the customer classification in the receivables generation reason master 106b linked to the reason for the receivable generation of the collection schedule data are excluded to create a list of reconciliation candidate patterns, and the planned collection amounts of the reconciliation candidate pattern list data and the deposit amount are compared in order of largest granularity of the customer, and automatic reconciliation is performed.

[0055] The list of clearing candidate pattern data is created by the following processes (1) to (4).

[0056] Processing (1) As shown in Figure 7(A), the collection schedule data is aggregated by the affiliated corporate group > collection schedule date, and the amount of the receivable candidate is calculated by excluding items for which the reason for the receivable is not the affiliated corporate group (reason for the receivable occurrence "300" to "800" in the reason for the receivable occurrence master 106b).

[0057] In this example, for the affiliated corporate group code "SE1000" and the XX Holdings "XX Holdings", the expected collection date is "2024 / 5 / 31" and the expected collection amount is "¥12,000", and the expected collection date is "2024 / 6 / 30" and the expected collection amount is "¥54,000 (=13,000 + 17,000 + 3,000 + 21,000)".

[0058] Processing (2) As shown in Figure 7(B), the collection schedule data is aggregated by affiliated corporate group > corporation > collection schedule date, and the amount of the proposed repayment is calculated by excluding items for which the reason for the debt generation is not the corporation (debt generation reasons "100", "200", "500" to "800" in the debt generation reason master 106b).

[0059] Processing (3) As shown in Figure 7(C), the collection schedule data is aggregated by affiliated corporate group > corporation > area group > collection schedule date, and the amount of the proposed settlement is calculated by excluding items for which the reason for the debt generation is other than the area group (debt generation reasons "100" to "400", "700", "800" in the debt generation reason master 106b).

[0060] Processing (4) As shown in Figure 8, the collection schedule data is aggregated by affiliated corporate group > corporation > area group > store > scheduled collection date, and items for which the reason for the debt generation is not the store (debt generation reasons "100" to "600" in the debt generation reason master 106b) are excluded to calculate the amount of the candidate for reconciliation.

[0061] Processing (5) The above reconciliation candidate pattern list data created in processes (1) to (4) is checked for match or mismatch of amounts in order of granularity, and automatic reconciliation is performed. Figure 9(A) shows an example of deposit data (same as Figure 6), and Figure 9(B) shows an example of reconciliation candidate pattern list data (same as Figure 8). As shown in Figures 9(A) and (B), for the affiliated corporate group: SE1000 (XX Holdings), expected collection date: 2024 / 06 / 30, and expected collection amount: 54,000 yen, the amounts match the deposit amount and are subject to reconciliation.

[0062] Processing (6) For the reconciliation candidates identified in process (5), automatic reconciliation is performed, the collected amount in the collection schedule data is updated, and the reconciled amount in the deposit data is updated. Figure 10(A) shows an example of the recovery schedule data after automatic reconciliation, and Figure 10(B) shows an example of the deposit data after automatic reconciliation. As shown in Figure 10(A), for the affiliated corporate group: SE1000 (XX Holdings), scheduled collection date: 2024 / 06 / 30, and scheduled collection amount: ¥54,000, the collected amounts (¥13,000, ¥17,000, ¥3,000, ¥21,000) are updated in bulk and the amount is treated as collected. In addition, the reconciled amount in the deposit data is updated to "¥54,000."

[0063] Next, an example in which the deposit amount in the deposit data differs from the above example will be explained with reference to processes (5)' and (6)'.

[0064] Processing (5)' 11(A) shows another example of deposit data. As shown in FIG. 11(A), the deposit amount is "¥13,000," and the other items are the same as in FIG.

[0065] The above reconciliation candidate pattern list data created in processes (1) to (4) is checked for match or mismatch of amounts in order of granularity, and automatic reconciliation is performed. Figure 11(B) shows an example of reconciliation candidate pattern list data (same as Figure 8). As shown in Figures 11(A) and (B), for the affiliated corporate group: SE1000 (XX Holdings), expected collection date: 2024 / 06 / 30, and expected collection amount: 13,000 yen, the amount matches the deposit amount and is subject to reconciliation.

[0066] Processing (6)' For the clearing candidates identified in process (5)', automatic clearing is performed, the collected amount in the collection schedule data is updated, and the cleared deposit amount in the deposit data is updated. Figure 12(A) shows an example of the recovery schedule data after automatic clearing, and Figure 12(B) shows an example of the deposit data after automatic clearing. As shown in Figure 12(A), for the affiliated corporate group: SE1000 (XX Holdings), scheduled collection date: 2024 / 06 / 30, and scheduled collection amount: ¥13,000, the collected amount: ¥13,000 is updated in one go and the amount is treated as cleared. In addition, the cleared deposit amount in the deposit data is updated to "¥13,000".

[0067] (When a lump sum payment is made from a corporation) With reference to Figures 13 to 18, we will explain the case where a lump sum deposit is made from a corporation. Figure 13 is a diagram showing an example of deposit data. In the example shown in the figure, the first line contains deposit number "N1000", deposit date "2024 / 6 / 30", store code "SE2100", store name "△△ Co., Ltd.", deposit method "bank transfer", deposit amount "¥17,000", reconciled deposit amount "¥0", and customer classification "1: corporation". For deposits from corporations, the remaining receivables to be reconciled are tallied.

[0068] Processing (1) As shown in Figure 14(A), the collection schedule data is aggregated by corporation > collection schedule date, and the amount of the proposed repayment is calculated by excluding items for which the reason for the debt generation is not a corporation (debt generation reasons "100", "200", "500" to "800" in the debt generation reason master 106b).

[0069] Processing (2) As shown in Figure 14(B), the collection schedule data is aggregated by corporation > area group > scheduled collection date, and the amount of the proposed settlement is calculated by excluding items for which the reason for the debt generation is other than the area group (debt generation reasons "100" to "400", "700", "800" in the debt generation reason master 106b).

[0070] Processing (3) As shown in Figure 14(C), the collection schedule data is aggregated by corporation > area group > store > scheduled collection date, and items for which the reason for the debt generation is not the store (debt generation reasons "100" to "600" in the debt generation reason master 106b) are excluded to calculate the amount of the debt candidate.

[0071] Processing (4) The above reconciliation candidate pattern list data created in processes (1) to (3) is checked for match or mismatch of amounts in order of granularity, and automatic reconciliation is performed. Figure 15(A) shows an example of deposit data (same as Figure 13), and Figure 15(B) shows an example of reconciliation candidate pattern list data (same as Figure 14(C)). As shown in Figures 15(A) and (B), for corporation: SE2100 (△△ Co., Ltd.), expected collection date: 2024 / 06 / 30, and expected collection amount: 17,000 yen, the amount matches the deposit amount and is subject to reconciliation.

[0072] Processing (5) For the clearing candidates identified in process (4), automatic clearing is performed, the cleared amount in the scheduled collection data is updated, and the cleared amount in the deposit data is updated. Figure 16(A) shows an example of the scheduled recovery data after automatic clearing, and Figure 16(B) shows an example of the deposit data after automatic clearing. As shown in Figure 16(A), for Corporation: SE2100 (△△ Holdings), Scheduled Collection Date: 2024 / 06 / 30, Scheduled Collection Amount: ¥17,000, the cleared amount: ¥17,000 is updated in one go and the item is treated as cleared. In addition, the cleared amount in the deposit data is updated to "¥17,000".

[0073] Next, an example in which the deposit amount in the deposit data differs from the above example will be explained with reference to processes (4)' and (5)'.

[0074] Processing (4)' 17(A) shows another example of deposit data. As shown in FIG. 17(A), the deposit amount is "¥31,000," and the other items are the same as in FIG.

[0075] The above reconciliation candidate pattern list data created in processes (1) to (3) is checked for match or mismatch of amounts in order of granularity, and automatic reconciliation is performed. Figure 17(B) shows an example of reconciliation candidate pattern list data (same as Figure 15(B)). As shown in Figures 17(A) and (B), for Corporation: SE2100 (△△ Co., Ltd.), Scheduled collection date: 2024 / 06 / 30, Scheduled collection amount: 31,000 yen, the amount matches the deposit amount and is subject to reconciliation.

[0076] Processing (5)' For the clearing candidates identified in process (4)', automatic clearing is performed, the recovered amount in the scheduled collection data is updated, and the cleared deposit amount in the deposit data is updated. Figure 18(A) shows an example of the recovery schedule data after automatic clearing, and Figure 18(B) shows an example of the deposit data after automatic clearing. As shown in Figure 18(A), for corporation: SE2100 (△△ Co., Ltd.), scheduled collection date: 2024 / 06 / 30, and scheduled collection amount: ¥31,000, the recovered amounts: ¥14,000 and ¥17,000 are updated in bulk and the amount is treated as cleared. In addition, the cleared deposit amount in the deposit data is updated to "¥31,000".

[0077] (When lump-sum payments are made from the area group) With reference to Figures 19 to 24, we will explain the case where a lump sum deposit is made from an area group. Figure 19 is a diagram showing an example of deposit data. In the example shown in the figure, the first line contains deposit number "N1000," deposit date "2024 / 6 / 30," store code "SE3110," store name "Chubu / Kansai region," deposit method "bank transfer," deposit amount "¥25,000," deposited amount cleared "¥0," and customer classification "2: Area group." For deposits from the area group, the remaining receivables to be cleared are tallied.

[0078] Processing (1) As shown in Figure 20(A), the scheduled collection data is aggregated by area group > scheduled collection date, and the amount of the debt candidate is calculated by excluding items for which the reason for debt generation is other than the area group (debt generation reasons "100" to "400", "700", "800" in the debt generation reason master 106b).

[0079] Processing (2) As shown in Figure 20(B), the scheduled collection data is aggregated by area group > store > scheduled collection date, and items for which the reason for the debt generation is not the store (debt generation reasons "100" to "600" in the debt generation reason master 106b) are excluded to calculate the candidate amount for reconciliation.

[0080] Processing (3) The above reconciliation candidate pattern list data created in processes (1) and (2) is checked for amount matches in order of granularity, and automatic reconciliation is performed. Figure 21(A) shows an example of deposit data (same as Figure 19), and Figure 21(B) shows an example of reconciliation candidate pattern list data (same as Figure 20(B)). As shown in Figures 21(A) and (B), for area group: SE3110 (Chubu / Kansai region), scheduled collection date: 2024 / 06 / 30, and scheduled collection amount: 25,000 yen, the amount matches the deposit amount and is subject to reconciliation.

[0081] Processing (4) For the clearing candidates identified in process (3), automatic clearing is performed, the cleared amount in the scheduled collection data is updated, and the cleared amount in the deposit data is updated. Figure 22(A) shows an example of the scheduled recovery data after automatic clearing, and Figure 22(B) shows an example of the deposit data after automatic clearing. As shown in Figure 22(A), for area group: SE3110 (Chubu / Kansai region), scheduled collection date: 2024 / 06 / 30, and scheduled collection amount: ¥25,000, the cleared amounts: ¥3,000 and ¥22,000 are updated in bulk, and the amount is treated as cleared. In addition, the cleared amount in the deposit data is updated to "¥25,000."

[0082] Next, an example in which the deposit amount in the deposit data differs from the above example will be explained with reference to processes (3)' and (4)'.

[0083] Processing (3)' 23(A) shows another example of deposit data. As shown in FIG. 23(A), the deposit amount is "¥3,000," and the other items are the same as in FIG.

[0084] The above reconciliation candidate pattern list data created in processes (1) and (2) is checked for amount matches or mismatches in order of granularity, and automatic reconciliation is performed. Figure 23(B) shows an example of reconciliation candidate pattern list data (the same as Figure 21(B)). As shown in Figures 23(A) and (B), for area group: SE3110 (Chubu / Kansai region), scheduled collection date: 2024 / 06 / 30, and scheduled collection amount: 3,000 yen, the amount matches the deposit amount and is subject to reconciliation.

[0085] Processing (4)' For the clearing candidates identified in process (3)', automatic clearing is performed, the cleared amount in the scheduled collection data is updated, and the cleared amount in the deposit data is updated. Figure 24(A) shows an example of the scheduled recovery data after automatic clearing, and Figure 24(B) shows an example of the deposit data after automatic clearing. As shown in Figure 24(A), for area group: SE3110 (Chubu / Kansai region), scheduled collection date: 2024 / 06 / 30, and scheduled collection amount: ¥3,000, the cleared amount: ¥3,000 is updated in one go, and the amount is treated as cleared. In addition, the cleared amount in the deposit data is updated to "¥3,000".

[0086] As described above, according to this embodiment, there are provided a billing destination master 106a that associates and registers specific information for identifying a business partner from which a debt is received, one or more business partners, and a business partner classification for specifying the granularity of the business partners; a debt origination reason master 106b that associates and registers a reason for debt generation with a business partner classification; a collection schedule data creation unit 102b that creates collection schedule data including multiple business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for debt generation; and a deposit processing unit that creates deposit data including a deposit date, specific information, a deposit amount, a cleared deposit amount, and a business partner classification obtained from the billing destination master 106a using the specific information as a key. 102c, and a reconciliation processing unit 102d which, in the billing destination master 106a, aggregates the scheduled collection amounts of the collection schedule data by the scheduled collection date, in order from the customer with the granularity specified in the customer classification of the deposit data to the customer with the smallest granularity, and in doing so excludes records other than the customer classification of the debt origination reason master 106b linked to the debt origination reason of the collection schedule data, creates reconciliation candidate pattern list data, and compares the scheduled collection amounts and the deposit amounts of the reconciliation candidate pattern list data in order of the largest granularity of the customer, and performs automatic reconciliation, thereby making it possible to achieve deposit reconciliation with high accuracy and low workload, even if the source of the deposit for the debt changes each time.

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

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

[0089] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to Goal 16 of the SDGs.

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

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

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

[0093] Furthermore, with regard to the deposit clearing device 100, the components shown in the drawings are functional concepts, and the device does not necessarily have to be physically configured as shown in the drawings.

[0094] For example, all or any part of the processing functions of the deposit clearing 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 deposit clearing device 100 as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

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

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

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

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

[0099] The deposit reconciliation 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 connected to any peripheral device. The deposit reconciliation device 100 may also be realized by installing software (including programs or data, etc.) that causes the device to perform the processing described in this embodiment.

[0100] 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. [Explanation of symbols]

[0101] 100 Deposit Clearing Device 102 Control section 102a Master Maintenance Department 102b Collection Schedule Data Creation Department 102c Deposit Processing Unit 102d Reconciliation Processing Unit 102e Screen display control unit 104 Communication interface unit 106 Storage section 106a Billing Master 106b Reason for receivables master 108 Input / Output Interface Section 112 Input Device 114 Output Device 300 Network 400 terminals

Claims

1. A deposit clearing device equipped with a control unit, The control unit a billing master in which specific information for identifying a customer from which a receivable is received, one or more customers, and a customer classification for specifying the granularity of the customer are associated and registered; A receivables reason master that associates the receivables reason with the customer classification and registers it; collection schedule data including a plurality of business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for the occurrence of the receivable; It is configured to be accessible to a deposit input means for creating deposit data including a deposit date, specific information, a deposit amount, a cleared deposit amount, and a customer classification obtained from the billing master using the specific information as a key; a clearing means for aggregating, in the billing master, the scheduled collection amounts of the scheduled collection data by the scheduled collection date, in order from the customer with the granularity of the customer specified by the customer classification of the deposit data to the customer with the smallest granularity, excluding records other than the customer classification of the debt origination reason master linked to the debt origination reason of the scheduled collection data, to create clearing candidate pattern list data, and comparing the scheduled collection amounts and the deposit amounts of the clearing candidate pattern list data in order of the customer granularity to perform automatic clearing; A deposit clearing device comprising:

2. 2. The deposit clearing device according to claim 1, wherein the automatic clearing updates the collected amount in the collection schedule data and the cleared amount in the deposit data.

3. The business partners and business partner categories include affiliated corporate groups, corporations, area groups, and stores, The granularity of the business partners is in the order of affiliated corporate group > corporation > area group > store, 2. The payment clearing device according to claim 1, wherein the invoice destination of the claim is a store.

4. 4. The deposit clearing device according to claim 1, wherein the claim is a claim relating to the installation or replacement of a gaming machine or a game table in a store.

5. A deposit clearing method executed by an information processing device having a control unit, The control unit a billing master in which specific information for identifying a customer from which a receivable is received, one or more customers, and a customer classification for specifying the granularity of the customer are associated and registered; A receivables reason master that associates the receivables reason with the customer classification and registers it; collection schedule data including a plurality of business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for the occurrence of the receivable; It is configured to be accessible to Executed in the control unit: a deposit input process for creating deposit data including a deposit date, specific information, a deposit amount, a cleared deposit amount, and a customer classification obtained from the billing master using the specific information as a key; a clearing process in which, in the billing master, the scheduled collection amounts of the scheduled collection data are tallied by the scheduled collection date, in order from the customer with the largest granularity specified in the customer classification of the deposit data to the customer with the smallest granularity, and in this process, records other than the customer classification of the credit origination reason master linked to the credit origination reason of the scheduled collection data are excluded to create clearing candidate pattern list data, and the scheduled collection amounts and deposit amounts of the clearing candidate pattern list data are collated in order of the largest granularity of the customer, and automatic clearing is performed; A payment settlement method comprising:

6. A deposit clearing program to be executed by an information processing device having a control unit, The control unit a billing master in which specific information for identifying a customer from which a receivable is received, one or more customers, and a customer classification for specifying the granularity of the customer are associated and registered; A receivables reason master that associates the receivables reason with the customer classification and registers it; collection schedule data including a plurality of business partners, a scheduled collection date, a scheduled collection amount, a collected amount, and a reason for the occurrence of the receivable; It is configured to be accessible to The control unit a deposit input process for creating deposit data including a deposit date, specific information, a deposit amount, a cleared deposit amount, and a customer classification obtained from the billing master using the specific information as a key; a clearing process in which, in the billing master, the scheduled collection amounts of the scheduled collection data are tallied by the scheduled collection date, in order from the customer with the largest granularity specified in the customer classification of the deposit data to the customer with the smallest granularity, and in this process, records other than the customer classification of the credit origination reason master linked to the credit origination reason of the scheduled collection data are excluded to create clearing candidate pattern list data, and the scheduled collection amounts and deposit amounts of the clearing candidate pattern list data are collated in order of the largest granularity of the customer, and automatic clearing is performed; Run the Receipt Write-Off program.

Images