Dunning fee collection determination device, dunning fee collection determination method, and dunning fee collection determination program

Abstract

To provide a device and the like for determining collection of a demand fee that can determine whether the demand fee is subject to collection or not subject to collection according to a reason for failure of an account transfer, and control the creation of data for scheduled collection of the demand fee.SOLUTION: In this embodiment, a device performs the following: 1) determining whether a demand fee is subject to collection or not subject to collection for a transfer result code of debit request detail data based on a setting of a billing flag in a billing management master; 2) when it is determined that the demand fee is subject to collection, obtaining the amount of the demand fee from a product master; and 3) storing, in collection scheduled data, a guarantee number determined to be subject to collection of the demand fee in the debit request detail data and the obtained amount of the demand fee.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to a dunning fee collection determination device, a dunning fee collection determination method, and a dunning fee collection determination program. [Background technology]

[0002] Patent Document 1 discloses a guarantee contract management device that can appropriately make reminders and efficiently perform processes associated with guarantee contracts. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2016-177574 Summary of the Invention [Problem to be solved by the invention]

[0004] Until now, billing data for collection fees was created for all cases where direct debit transfers were not possible. Therefore, even in cases where direct debit transfers were not possible due to reasons such as the guarantor company's fault, billing data for collection fees was created and billed as is, raising concerns about the occurrence of complaints. Therefore, on an administrative basis (manually by administrative staff), the reasons for the non-account transfer failure in the billing data for collection fees were checked one by one, and for reasons not due to the contract holder's fault, the billing data for collection fees was deleted each time, which was both inefficient and cumbersome.

[0005] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a dunning fee collection determination device, a dunning fee collection determination method, and a dunning fee collection determination program that can determine whether a dunning fee is levied or not depending on the reason for the inability to perform an account transfer, and control the creation of scheduled collection data for the dunning fee. [Means for solving the problem]

[0006] In order to solve the above problems and achieve the object, there is provided a collection determination device for reminder fees that occurs when account transfers become impossible, the device comprising a control unit, which is accessible to product identification information assigned to a product that uses account transfer for payment of a fee, first data including the reminder fee amount of the reminder fee, account transfer result identification information for identifying the type of the account transfer result, second data including a reminder fee collection target classification for setting whether the reminder fee is subject to collection or not, the contract identification information of the product, a debit request amount which is the amount requested to debit the account from a financial institution, and third data including the account transfer result identification information corresponding to the type of the result as a result of the account transfer. The control unit includes: a determination means for determining whether the reminder fee is subject to collection or not based on the reminder fee collection target classification in the second data for the account transfer result identification information in the third data; a reminder fee amount acquisition means for acquiring the reminder fee amount from the first data when it is determined by the determination means that the reminder fee is subject to collection; and a reminder fee data generation means for storing, in the collection scheduled data, the contract identification information determined by the determination means to be subject to collection of the reminder fee in the third data and the reminder fee amount acquired by the reminder fee amount acquisition means. This is the gist of the invention.

[0007] Further, in the reminder fee collection determination device according to the present invention, the control unit further includes a master update means for changing whether the reminder fee is subject to collection or not in the reminder fee collection target classification in the second data. This is the gist of the invention.

[0008] In the reminder fee collection determination device according to the invention, the product is a product in rent debt guarantee, the fee is rent, and the reminder fee is a reminder fee collected together with the overdue rent when the account transfer of the rent fails. This is the gist of the invention.

[0009] Furthermore, the present invention provides a method for determining whether to collect a dunning fee, which is generated when an account transfer becomes impossible, and is executed by an information processing device having a control unit, the method determining whether to collect a dunning fee that occurs when an account transfer becomes impossible, wherein the information processing device includes: product identification information assigned to a product that uses account transfer for payment of fees; first data including a dunning fee amount of the dunning fee; account transfer result identification information for identifying the type of account transfer result; second data including a dunning fee collection target category for setting whether the dunning fee is subject to collection or not; contract identification information for the product; a debit request amount that is the amount for which a financial institution is requested to debit the account; the account transfer result; and the account transfer result identification corresponding to the type of result. and third data including other information, the third data being accessible to the control unit, and including a determination step executed by the control unit for determining whether the account transfer result identification information of the third data is subject to collection of the dunning fee or not based on the setting of the dunning fee collection target category of the second data, a dunning fee amount acquisition step for acquiring the dunning fee amount from the first data when it is determined in the determination step that the account transfer result identification information is subject to collection of the dunning fee, and a dunning fee data generation step for storing the contract identification information in the third data determined in the determination step to be subject to collection of the dunning fee and the dunning fee amount acquired in the dunning fee amount acquisition step in collection schedule data.

[0010] Furthermore, the present invention provides a dunning fee collection judgment program for making an information processing device having a control unit execute the program, which judges whether to collect a dunning fee that occurs when an account transfer becomes impossible, and which judges whether to collect a dunning fee that occurs when an account transfer becomes impossible. The information processing device executes the program, which judges whether to collect a dunning fee that occurs when an account transfer becomes impossible, by accumulating product identification information assigned to a product that uses account transfer for payment of fees, first data including a dunning fee amount of the dunning fee, account transfer result identification information for identifying the type of account transfer result, second data including a dunning fee collection target category for setting whether the dunning fee is subject to collection or not, contract identification information of the product, a debit request amount that is an amount for which a financial institution is requested to debit the account, the result of the account transfer, and the account transfer result corresponding to the type of result. and third data including result identification information, and for execution by the control unit, the control unit is capable of accessing the third data and the third data including result identification information, and the control unit is characterized in that it includes: a determination step for determining whether or not the account transfer result identification information of the third data is subject to collection of the dunning fee based on the setting of the dunning fee collection target category of the second data; a dunning fee amount acquisition step for acquiring the dunning fee amount from the first data when it is determined in the determination step that the account transfer result identification information is subject to collection of the dunning fee; and a dunning fee data generation step for storing the contract identification information in the third data determined in the determination step to be subject to collection of the dunning fee and the dunning fee amount acquired in the dunning fee amount acquisition step in collection schedule data. [Effects of the Invention]

[0011] The present invention has been made in consideration of the above problems, and can determine whether or not a collection fee is due depending on the reason for the inability to perform an account transfer, and control the creation of collection schedule data for the collection fee. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram showing an example of a relationship according to this embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of the task assistance device according to this embodiment. [Figure 3]FIG. 3 is a diagram showing an example of the configuration of the reminder fee data creation process in the present embodiment. [Figure 4] FIG. 4 is a diagram showing an outline of the processing performed by the business support apparatus according to the present embodiment. [Figure 5] FIG. 5 is a diagram showing a specific example of the processing performed by the business support apparatus according to the present embodiment. [Figure 6] FIG. 6 is a diagram showing a specific example of the processing performed by the business support apparatus according to the present embodiment.

DETAILED DESCRIPTION OF THE INVENTION

[0013] [1. Overview] First, with reference to FIG. 1, the overview of the present embodiment will be described. FIG. 1 is a diagram showing an example of the relationship according to the present embodiment.

[0014] Currently, when an owner (who is a lessor), a real estate company, a management company, etc. and a lessee conclude a lease contract, the case of using a surety company is increasing. As rental debt guarantee products of surety companies, mainly, there are collection agency type products in which the surety company makes an advance remittance of rent to the owner (who is a lessor), a real estate company, a management company, etc., and accident report type products in which payment is made based on a delinquency report from the owner (who is a lessor), a real estate company, a management company, etc. In either case, when a lessee who is a contractor of the surety company defaults on rent, the surety company fulfills the guarantee and claims overdue rent, reminder fees, etc. from the lessee who is the contractor.

[0015] In the collection agency type products in the rental debt guarantee business of surety companies, rent claims to the lessee who is the contractor are made by bank transfer. When a bank transfer fails, the surety company fulfills the guarantee and claims overdue rent from the lessee who is the contractor. However, depending on the reason for the bank transfer failure, there are cases where the reminder fee collected together with the overdue rent is waived. The present embodiment relates to a function of determining whether or not to collect a reminder fee according to the reason for the bank transfer failure and controlling the creation of reminder fee claim data according to the strategy for each surety company.

[0016] The term "demand fee" refers to the additional administrative fee that the guarantee company charges when claiming overdue rent from the tenant. In the guarantee industry, this fee is referred to by various names, such as reclaim administrative fee or subrogation administrative fee.

[0017] For example, Figure 1 shows the relationship in the case of a collection agency product. The dotted lines indicate the contractual relationship, and the solid lines indicate the flow of money.

[0018] Let's explain the contractual relationship. First, as shown in Figure 1, the management company, which is the landlord, and the tenant enter into a lease agreement. At that time, the tenant does not appoint a guarantor, but instead asks the guarantor company to guarantee the rent and enters into a rent guarantee contract. Then, the management company, which is the landlord, enters into a guarantee contract with the guarantor company for the rent of the tenant. In the case of the collection agency type shown in Figure 1, the management company and the guarantor company enter into a service contract for the work related to rent collection.

[0019] Next, we will explain how money flows. When a tenant (contractor) and a guarantor company agree to pay rent by direct debit, the guarantor company (trustor) requests a collection agency (contractor) that handles the direct debit procedures and collection of the direct debit payments to collect the rent from the tenant ((1) collection request). The collection agency (contractor) then bills the rent to the tenant's account ((2) rent billing (direct debit)), and the rent is debited from the tenant's account ((3) payment (direct debit)). The collection agency (contractor) then remits the rent received from the tenant to the guarantor company (trustor) ((5) received rent remittance). Meanwhile, the guarantor company pays the rent to the management company on its behalf on a date determined in accordance with the outsourcing contract with the management company ((4) rent remittance (advance)).

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

[0021] Specifically, the business support device 100 can determine whether a collection target or non - collection target of a reminder fee according to the reason for the inability of account transfer, and control the creation of reminder fee collection schedule data, etc. 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 business support device such as a desktop personal computer, and may also be constructed based on a portable business support device such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer.

[0022] The business support device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the business support device 100 is communicably connected via an arbitrary communication path.

[0023] The communication interface unit 104 communicably 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 a function of communicating data with other devices via a communication line. Here, the network 300 has a function of communicably connecting the business support device 100 and the server 200 to each other, and is, for example, the Internet or a LAN (Local Area Network), etc. Note that the data stored in the storage unit 106 may be stored in the server 200, for example.

[0024] An input / output interface unit 108 is connected to an input device 112 and an output device 114. As the output device 114, in addition to a monitor (including a home TV), a speaker or a printer can be used. As the input device 112, in addition to a keyboard, a mouse, and a microphone, a monitor that cooperates with the mouse to realize a pointing device function can be used. Hereinafter, in some cases, the output device 114 may be described as the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

[0025] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 records a computer program for giving instructions to the CPU (Central Processing Unit) in cooperation with the OS (Operating System) to perform various processes. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory)·ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used.

[0026] The storage unit 106 stores a product master 106a (corresponding to the first data according to the present invention), an account transfer result master 106b, a billing management master 106c (corresponding to the second data according to the present invention), contract data 106d, a debit request detail data 106e (corresponding to the third data according to the present invention), a subrogation payment data 106f, a payment request data 106g, a collection schedule data 106h, and the like.

[0027] FIG. 3 and FIG. 6 show an example of the information stored in the product master 106a. As shown in FIGS. 3 and 6, the product master 106a stores information including a product code (corresponding to the product identification information according to the present invention) assigned to a rent debt guarantee plan, a rent debt guarantee plan name (product name), an automatic delinquency registration classification for setting whether to automatically create data related to a claim for which the debit result from the account is unavailable, the amount of the subrogation payment transaction fee (corresponding to the reminder fee amount according to the present invention), and the like.

[0028] An example of information stored in the account transfer result master 106b is shown in Figure 3. The account transfer result master 106b stores information including a transfer result code for identifying the type of account transfer result, as shown in Figure 3.

[0029] 3 and 6 show examples of information stored in the billing management master 106c. As shown in FIGS. 3 and 6, the billing management master 106c stores information including a transfer result code (corresponding to the account transfer result identification information of the present invention) for identifying the type of account transfer result, a billing flag (corresponding to the dunning fee collection target category of the present invention) that is set to indicate whether or not a dunning fee is to be collected corresponding to the account transfer result code, and the like. The billing flag in the billing management master 106c can be set or changed to indicate whether or not a dunning fee is to be collected, depending on the strategy of the user of the business support device 100, such as a guarantor company (this corresponds to the processing executed by the master update means of the present invention).

[0030] An example of information stored in the contract data 106d is shown in Fig. 3. As shown in Fig. 3, the contract data 106d stores information including a guarantee number assigned by the guarantor company to the contracting party who is the lessee, a product code, rent, the name of the management company that is the lessor, etc.

[0031] 3, 5, and 6 show examples of information stored in the debit request detail data 106e. As shown in FIGS. 3, 5, and 6, the debit request detail data 106e stores information including the guarantee number (corresponding to the contract identification information of the present invention) assigned by the guarantor to the contractor (the lessee), the debit request amount, which is the amount requested to be debited from the account of the financial institution, the debit result (corresponding to the account transfer result of the present invention), and a transfer result code corresponding to the debit result (corresponding to the account transfer result identification information of the present invention). Note that the debit request detail data 106e1 in FIG. 5 shows the debit request detail data 106e to be sent to the contractor, and the debit result and the transfer result code corresponding to the debit result are left blank. Furthermore, the debit request detail data 106e2 shows the data created by importing the debit request detail data A created by the contractor and received from the contractor.

[0032] 3 and 5 show examples of information stored in the subrogation data 106f. As shown in Fig. 3 and Fig. 5, the subrogation data 106f stores information including the report date, guarantee number, management company name, subrogation amount, etc.

[0033] An example of information stored in the payment request data 106g is shown in Fig. 5. As shown in Fig. 5, the payment request data 106g stores information including the payment date, payee, guarantee number, payment amount, etc.

[0034] Examples of information stored in the collection schedule data 106h are shown in Figures 3, 5, and 6. As shown in Figures 3, 5, and 6, the collection schedule data 106h stores information including the billing year and month, billing destination, guarantee number (corresponding to the contract identification information according to the present invention), billing item, billing amount (including the amount corresponding to the dunning fee amount according to the present invention), etc.

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

[0036] Functionally conceptually, the control unit 102 includes a collection request data creation unit 102a, a collection result import processing unit 102b, and the like.

[0037] The collection request data creation unit 102a performs a creation process of the collection request detail data 106e to be transmitted to the collection agency (the consigned party) in the corresponding month, creates the collection request detail data 106e with blank fields for the collection result, transfer result code, etc., and transmits the created collection request detail data 106e1 to the collection agency (the consigned party).

[0038] The collection result import processing unit 102b imports the collection request detail data A created by the consigned party and checks the import result. Then, based on the product master 106a, the billing management master 106c, and the contract data 106d, the collection result import processing unit 102b creates the collection request detail data 106e, the subrogation payment data 106f, the payment request data 106g, and the collection schedule data 106h from the collection request detail data A created by the consigned party.

[0039] Furthermore, based on the billing management master 106c, the collection result import processing unit 102b determines whether the subrogation payment transaction fee is subject to collection or not from the collection result and transfer result code of the created collection request detail data 106e (corresponding to the process executed by the determination means according to the present invention), and acquires the amount of the subrogation payment transaction fee for the plan of the guarantee number subject to the collection of the subrogation payment transaction fee from the product master 106a (corresponding to the process executed by the reminder fee amount acquisition means according to the present invention). Then, the collection result import processing unit 102b stores the guarantee number and the amount of the subrogation payment transaction fee in the collection schedule data 106h to create the subrogation payment transaction fee data (corresponding to the process executed by the reminder fee data creation means according to the present invention).

[0040] FIG. 3 is a diagram showing an example of an outline of the reminder fee data creation process in the present embodiment. The business support apparatus 100 automatically registers delinquent payments (system processing) for subrogation payment data 106f and collection schedule data 106h including subrogation payment transaction fee data from the product master 106a, account transfer result master 106b, billing management master 106c, contract data 106d, and debit request detail data 106e.

[0041] [3. Process] [3-1. Outline of the process] An outline of the process performed by the business support apparatus 100 configured as described above will be described with reference to FIG. 4. FIG. 4 is a diagram showing an outline of the process performed by the business support apparatus 100 according to the present embodiment. In this description, it is assumed that the debit request data creation unit 102a has created the debit request detail data 106e1 for the corresponding month and transmitted it to the consignment destination.

[0042] The debit result import processing unit 102b receives the debit request detail data A created by the consignment destination. The debit result import processing unit 102b imports the debit request detail data A created by the consignment destination, and creates subrogation payment related data (debit request detail data 106e, subrogation payment data 106f, payment request data 106g, collection schedule data 106h) based on the debit request detail data A created by the consignment destination (step 1).

[0043] Thereafter, the debit result import processing unit 102b determines whether the subrogation payment transaction fee is subject to collection or not based on the debit result and transfer result code of the debit request detail data 106e created in step 1 based on the billing management master 106c, and obtains the amount of the subrogation payment transaction fee of the plan associated with the guarantee number determined to be the claim target of the subrogation payment transaction fee from the product master 106a, and stores the guarantee number determined to be the claim target of the subrogation payment transaction fee, the obtained amount of the subrogation payment transaction fee, etc. in the collection schedule data 106h to create subrogation payment transaction fee data (step 2).

[0044] [3-2. Specific example of the process] A specific example of the processing performed by the business support apparatus 100 configured as described above will be described in detail with reference to FIGS. 5 and 6. FIGS. 5 and 6 are diagrams showing specific examples of the processing performed by the business support apparatus 100 according to the present embodiment.

[0045] [Step 0: Creation of Withdrawal Request Data] Referring to FIG. 5, the creation of withdrawal request data will be described. The withdrawal request data creation unit 102a performs a withdrawal request data creation process for April from the product master 106a and the contract data 106d, creates withdrawal request detail data 106e1 in which the withdrawal result and the transfer result code are blank, and transmits the created withdrawal request detail data 106e1 in FIG. 5 to the consignment destination.

[0046] [Step 1: Withdrawal Result Import Process (Creation of Subrogation Payment Related Data)] Referring to FIG. 5, the creation of subrogation payment related data will be described. The withdrawal result import processing unit 102b receives the withdrawal request detail data A created by the consignment destination from the consignment destination. The received withdrawal request detail data A created by the consignment destination is imported and confirmed. Thereafter, the withdrawal result import processing unit 102b creates withdrawal request detail data 106e2 in which data is stored in the withdrawal result and the transfer result code from the product master 106a, the account transfer result master 106b, the contract data 106d, and the withdrawal request detail data A created by the consignment destination, and further creates subrogation payment data 106f, payment request data 106g, and collection schedule data 106h.

[0047] Regarding the subrogation payment data 106f, the debit result import processing unit 102b creates the subrogation payment data 106f for managing subrogation payments by storing information such as the guarantee numbers "0000000001" and "0000000003" of the data for which the debit result in the debit request detail data 106e2 is "unable", the debit request amount of "￥100,000" for the guarantee number "0000000001", the debit request amount of "￥120,000" for the guarantee number "0000000003", and from the contract data 106d, the management company name "A Agency" for the guarantee numbers "0000000001" and "0000000003", the customer name "Tanaka Tarou" for the guarantee number "0000000001", and the customer name "Yamada Jirou" for the guarantee number "0000000003".

[0048] Regarding the payment request data 106g, the debit result import processing unit 102b creates the payment request data 106g for managing payments by storing information such as the guarantee numbers "0000000001" and "0000000003" of the data for which the debit result in the debit request detail data 106e2 is "unable", the debit request amount of "￥100,000" for the guarantee number "0000000001", the debit request amount of "￥120,000" for the guarantee number "0000000003", and from the contract data 106d, the management company name "A Agency" for the guarantee numbers "0000000001" and "0000000003".

[0049] Regarding the collection schedule data 106h, the debit result import processing unit 102b creates the collection schedule data 106h for managing the collection schedule by storing information such as the guarantee numbers "0000000001" and "0000000003" of the data for which the debit result in the debit request detail data 106e2 is "unable", the debit request amount of "￥100,000" for the guarantee number "0000000001", the debit request amount of "￥120,000" for the guarantee number "0000000003", the customer name "Tanaka Tarou" for the guarantee number 0000000001, the customer name "Yamada Jirou" for the guarantee number "0000000003", and from the contract data 106d, the billing item "rent" for the guarantee numbers "0000000001" and "0000000003".

[0050] [Step 2: Debit Result Import Process (Creation of Subrogation Payment Transaction Fee Data)] Referring to FIG. 6, the creation of subrogation payment transaction fee data will be described. The debit result import processing unit 102b creates subrogation payment transaction fee data from the product master 106a, the billing management master 106c, and the debit request detail data 106e.

[0051] The debit result import processing unit 102b: 1) determines, from the debit request detail data 106e, data (records) including a transfer result code for which the debit result is unavailable and the billing flag in the billing management master 106c is set to the collection target, as the target for creating subrogation payment transaction fee data; 2) obtains the amount of the subrogation payment transaction fee set in the product master 106a from the product code of the contract data 106d linked by the guarantee number; and 3) stores information such as the guarantee number and the amount of the subrogation payment transaction fee in the collection schedule data 106h to create subrogation payment transaction fee data.

[0052] Referring to FIG. 6, it will be specifically described. In the billing management master 106c of FIG. 6, for the transfer result codes of "1 Insufficient Funds" and "3 Depositor's Reason", the billing flag of "1: Target", which is the collection target for the subrogation payment transaction fee, is set.

[0053] The debit result import processing unit 102b 1) determines from the debit request detail data 106e of Figure 6 created in step 1 that the data (record) for guarantee number "0000000001" for which the debit result is "impossible" and the transfer result code is "1: insufficient funds" linked to the billing flag "1: applicable" (a flag indicating that the data is subject to collection) in the billing management master 106c is subject to collection of the subrogation administration fee, 2) obtains the amount of the subrogation administration fee "800" (excluding tax) from the product master 106a based on the product code "A" in the contract data 106d linked by the guarantee number "0000000001", and 3) stores the guarantee number "0000000001", the amount "800", as well as other information such as the customer name "Tanakatarou" and the billing item "subrogation administration fee" in the collection schedule data 106h, thereby creating subrogation administration fee data.

[0054] The debit result import processing unit 102b does not create subrogation administrative fee data if the debit result is not available but the billing flag in the billing management master 106c indicates that the fee is not subject to collection.

[0055] For example, the guarantee number "0000000003" in the debit request detail data 106e in Figure 6 has a debit result of "impossible," but the transfer result code is "8: Entrustor's Instance," which is a code for when billing is suspended due to the entrustor's instance, and the billing flag in the billing management master 106c is set to not be subject to collection of subrogation administrative fees. In this case, the debit result import processing unit 102b determines that subrogation administrative fee data is not subject to creation, and does not create data for the subrogation administrative fee. Therefore, subrogation administrative fee data for the guarantee number "0000000003" is not created in the collection schedule data 106h in Figure 6.

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

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

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

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

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

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

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

[0063] For example, regarding the processing functions provided by the business support device 100, especially each processing function performed by the control unit, all or any part thereof may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware by wired logic. Note that the program is recorded on a non-transitory computer-readable recording medium including programmed instructions for causing an information processing device to execute the processing described in the present embodiment, and is mechanically read by the business support device 100 as necessary. That is, in a storage unit such as a ROM or an HDD (Hard Disk Drive), a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded into the RAM, and constitutes the control unit in cooperation with the CPU.

[0064] Further, this computer program may be stored in an application program server connected to the business support device 100 via an arbitrary network, and all or part of it can be downloaded as necessary.

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

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

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

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

[0069] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0070] The present invention is useful in a variety of industries, such as retail or wholesale. [Explanation of symbols]

[0071] 100 Business support equipment 102 Control section 102a Withdrawal request data creation section 102b Withdrawal result import processing unit 104 Communication interface unit 106 Storage section 106a Product Master 106b Account transfer result master 106c Billing Management Master 106d Contract Data 106e Withdrawal request details data 106f Subrogation Data 106g Payment request data 106h Scheduled collection data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A collection judgment device for reminder fees, comprising a control unit, which determines the collection of reminder fees that occur when account transfers become impossible, product identification information assigned to a product that uses account transfer for payment of fees, first data including the reminder fee amount of the reminder fee, and account transfer result identification information for identifying the type of account transfer result, second data including a reminder fee collection target classification for setting whether the reminder fee is subject to collection or not subject to collection, and the contract identification information of the product, the debit request amount that is the amount requested to debit the account from the financial institution, the account transfer result, and third data including the account transfer result identification information corresponding to the type of the result, is accessible to, The control unit includes: determination means for determining whether the reminder fee is subject to collection or not subject to collection based on the reminder fee collection target classification in the second data for the account transfer result identification information in the third data; reminder fee amount acquisition means for acquiring the reminder fee amount from the first data when the reminder fee is determined to be subject to collection by the determination means; reminder fee data generation means for storing, in the collection schedule data, the contract identification information determined to be subject to collection of the reminder fee by the determination means in the third data and the reminder fee amount acquired by the reminder fee amount acquisition means; characterized by comprising A reminder fee collection judgment device.

2. The control unit further includes: master update means for changing whether the reminder fee is subject to collection or not subject to collection in the reminder fee collection target classification of the second data characterized by further comprising The reminder fee collection judgment device according to claim 1.

3. The product is a product in rental debt guarantee, The fee is rent, The reminder fee is a reminder fee collected together with the overdue rent when the account transfer of the rent is impossible, characterized by being the reminder fee collection judgment device according to claim 1 or 2.

4. A reminder fee collection judgment method executed by an information processing device comprising a control unit, which determines the collection of reminder fees that occur when account transfers become impossible, The information processing device includes: product identification information assigned to a product that uses account transfer for payment of fees, first data including the reminder fee amount of the reminder fee, and Second data including account transfer result identification information for identifying the type of account transfer result, and a collection target classification for the reminder fee for setting whether the reminder fee is subject to collection or not Third data including the contract identification information of the product, the amount requested for account debit to the financial institution (the debit request amount), the result of the account transfer, and the account transfer result identification information corresponding to the type of the result is accessible to executed by the control unit A determination step of determining whether the reminder fee is subject to collection or not for the account transfer result identification information of the third data based on the setting of the collection target classification of the reminder fee in the second data A reminder fee amount acquisition step of acquiring the reminder fee amount from the first data when it is determined in the determination step that the reminder fee is subject to collection A reminder fee data generation step of storing the contract identification information determined to be the collection target of the reminder fee in the determination step in the third data and the reminder fee amount acquired in the reminder fee amount acquisition step in the collection scheduled data including A reminder fee collection determination method characterized by

5. A reminder fee collection determination program for causing an information processing apparatus including a control unit to execute, for determining the collection of a reminder fee generated when an account transfer becomes impossible to transfer, the information processing apparatus Product identification information assigned to a product that uses account transfer for payment of fees, first data including the reminder fee amount of the reminder fee Second data including account transfer result identification information for identifying the type of account transfer result, and a collection target classification for the reminder fee for setting whether the reminder fee is subject to collection or not Third data including the contract identification information of the product, the amount requested for account debit to the financial institution (the debit request amount), the result of the account transfer, and the account transfer result identification information corresponding to the type of the result is accessible to for execution by the control unit A determination step of determining whether the reminder fee is subject to collection or not for the account transfer result identification information of the third data based on the setting of the collection target classification of the reminder fee in the second data An reminder fee amount acquisition step of acquiring the reminder fee amount from the first data when it is determined in the determination step that the reminder fee is subject to collection A reminder fee data generation step of storing, in the collection schedule data, the contract identification information determined to be a collection target of the reminder fee in the determination step in the third data and the reminder fee amount obtained in the reminder fee amount acquisition step; Including; A reminder fee collection determination program characterized by the above.

Images